Update to bug 54919 gone missing

Update to bug 54919 gone missing

[Brian Cully]

	I sent an email to 54919@debbugs.gnu.org to update it with more
specific information almost two days ago and I haven’t seen any changes
in https://issues.guix.gnu.org/54919 . I also never got a bounce or
other return communication saying what has happened; it’s as if my email
were silently sent to the bit bucket.

	Is there more to the procedure than sending an email to the
address at the bottom of the ticket?

	For the record, since it’s apparently lost: I tracked the issue
down to this line in my home.scm:

---[snip]---
(service home-shepherd-service-type (home-shepherd-configuration))
---[snip]---

	When I comment that out, everything runs correctly. It seems as
though the addition of this empty configuration caused the ’herd’
process to try to communicate with the shepherd process, and even though
it was able to connect, it never got a response to the version query.

	There were more details in the lost bug report, but the above is
the gist of it.

-bjc

Re: Update to bug 54919 gone missing

[Tobias Geerinckx-Rice]

Hi Brian,

On 16 April 2022 11:36:52 UTC, Brian Cully <bjc@spork.org> wrote:
>
>	I sent an email to 54919@debbugs.gnu.org to update it with more
>specific information almost two days ago and I haven’t seen any changes
>in https://issues.guix.gnu.org/54919 . I also never got a bounce or
>other return communication saying what has happened; it’s as if my email
>were silently sent to the bit bucket.

I can't say what happened here: it's not in the moderation queue (5 unfortunates who were have been freed) and even if it had been that shouldn't have resulted in what you report.

We don't have easy access to lower-level logs. Do you? You look like you might self-host.

Armed with a log snippet from you with a clear 250 'accepted' I'd feel less bothersome asking the gnu.org folks to investigate.

>	There were more details in the lost bug report, but the above is
>the gist of it.

Thanks for reporting both!


Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.

Re: Update to bug 54919 gone missing

[Brian Cully]

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> We don't have easy access to lower-level logs. Do you? You look like you might self-host.
>
> Armed with a log snippet from you with a clear 250 'accepted' I'd feel less bothersome asking the gnu.org folks to investigate.

	You know, I hadn’t even thought to check my mail queue. I can’t
remember the last time I had a delivery problem (or maybe I’ve been
having them the whole time and just not noticed 😉).

	I have my mail server set to require TLS, but it looks as though
debbugs.gnu.org doesn’t support it:

---[snip]---
Apr 16 08:26:10 mx0 postfix/smtp[68543]: 347053CCD: to=<54919@debbugs.gnu.org>, relay=debbugs.gnu.org[209.51.188.43]:25, delay=78497, delays=78497/0.06/0.27/0, dsn=4.7.4, status=deferred (TLS is required, but was not offered by host debbugs.gnu.org[209.51.188.43])
---[snip]---

	This wasn’t an issue for other reports, as I used the
bug-guix@gnu.org address, and eggs.gnu.org offers STARTTLS after the
EHLO.

	I’m not sure what to do here. I’m kind of loathe to remove the
TLS mandate on my server, and it seems to me like the debbugs MX should
offer it for all the standard reasons.

> Thanks for reporting both!

	Thanks for prodding me to dig further on my end. I honestly
thought the mail just disappeared.

-bjc