GNU bug report logs - #78431
Unclear patch submission address

Previous Next

Package: coreutils;

Reported by: Ville Skyttä <ville.skytta <at> iki.fi>

Date: Wed, 14 May 2025 19:41:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

To reply to this bug, email your comments to 78431 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-coreutils <at> gnu.org:
bug#78431; Package coreutils. (Wed, 14 May 2025 19:41:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Ville Skyttä <ville.skytta <at> iki.fi>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Wed, 14 May 2025 19:41:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ville Skyttä <ville.skytta <at> iki.fi>
To: bug-coreutils <at> gnu.org
Subject: Unclear patch submission address
Date: Wed, 14 May 2025 22:40:14 +0300
[Message part 1 (text/plain, inline)]
The HACKING and README-hacking files contain advice to send patches to the
email address in the respective program's --help output.

However, --help output might not contain any email addresses, such as for
example in the coreutils that ships with Ubuntu 25.04. Looks as if both
PACKAGE_PACKAGER and PACKAGE_PACKAGER_BUG_REPORTS need to be set in order
to have at least one address there.

Maybe some rephrasing of the hacking docs or adding fallback info there in
case of no other email address source would be in order.

Ville
[Message part 2 (text/html, inline)]

Information forwarded to bug-coreutils <at> gnu.org:
bug#78431; Package coreutils. (Wed, 14 May 2025 19:54:01 GMT) Full text and rfc822 format available.

Message #8 received at 78431 <at> debbugs.gnu.org (full text, mbox):

From: Collin Funk <collin.funk1 <at> gmail.com>
To: Ville Skyttä <ville.skytta <at> iki.fi>
Cc: 78431 <at> debbugs.gnu.org
Subject: Re: bug#78431: Unclear patch submission address
Date: Wed, 14 May 2025 12:53:42 -0700
Ville Skyttä <ville.skytta <at> iki.fi> writes:

> The HACKING and README-hacking files contain advice to send patches to the
> email address in the respective program's --help output.
>
> However, --help output might not contain any email addresses, such as for
> example in the coreutils that ships with Ubuntu 25.04. Looks as if both
> PACKAGE_PACKAGER and PACKAGE_PACKAGER_BUG_REPORTS need to be set in order
> to have at least one address there.
>
> Maybe some rephrasing of the hacking docs or adding fallback info there in
> case of no other email address source would be in order.

I think that adding an email regardless would be good seeing that Ubuntu
wants to change their coreutils commands to uutils eventually [1]. I
feel like that change will cause some confusion on where to report
bugs...

Plus the GNU coding standards say there should be an email [2]. On my
Fedora 42 machine:

    $ automake --help | grep @
    Report bugs to <bug-automake <at> gnu.org>.
    $ ln --help | grep @

Maybe I am missing some history behind why the bug report email is not
included though.

Collin

[1] https://discourse.ubuntu.com/t/carefully-but-purposefully-oxidising-ubuntu/56995
[2] https://www.gnu.org/prep/standards/standards.html#g_t_002d_002dhelp




Information forwarded to bug-coreutils <at> gnu.org:
bug#78431; Package coreutils. (Wed, 14 May 2025 20:42:01 GMT) Full text and rfc822 format available.

Message #11 received at 78431 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Collin Funk <collin.funk1 <at> gmail.com>
Cc: 78431 <at> debbugs.gnu.org, Ville Skyttä <ville.skytta <at> iki.fi>
Subject: Re: bug#78431: Unclear patch submission address
Date: Wed, 14 May 2025 13:40:54 -0700
[Message part 1 (text/plain, inline)]
On 2025-05-14 12:53, Collin Funk wrote:
> I think that adding an email regardless would be good

Yes, now's a good time to revisit the decision in 2013 to remove the 
bug-reporting email address[1]. Plus, the current code is confusing.

How about the attached coreutils patch? It simplifies the code and goes 
back to the old way of doing things, which includes outputting the bug 
reporting address.

If this doesn't generate the output we want, surely we should change 
Gnulib's emit_bug_reporting_address rather than try to reinvent it.

[1]: 
https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8b6d3c5700526f962b12cd5901b55961c5e18186
[0001-maint-help-now-outputs-bug-reporting-address.patch (text/x-patch, attachment)]

Information forwarded to bug-coreutils <at> gnu.org:
bug#78431; Package coreutils. (Wed, 14 May 2025 23:23:03 GMT) Full text and rfc822 format available.

Message #14 received at 78431 <at> debbugs.gnu.org (full text, mbox):

From: Collin Funk <collin.funk1 <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 78431 <at> debbugs.gnu.org, Ville Skyttä <ville.skytta <at> iki.fi>,
 P <at> draigBrady.com
Subject: Re: bug#78431: Unclear patch submission address
Date: Wed, 14 May 2025 16:22:17 -0700
Paul Eggert <eggert <at> cs.ucla.edu> writes:

> Yes, now's a good time to revisit the decision in 2013 to remove the
> bug-reporting email address[1]. Plus, the current code is confusing.
>
> How about the attached coreutils patch? It simplifies the code and
> goes back to the old way of doing things, which includes outputting
> the bug reporting address.
>
> If this doesn't generate the output we want, surely we should change
> Gnulib's emit_bug_reporting_address rather than try to reinvent it.

I think the change is good, but lets wait for Pádraig's thoughts since
he disliked this many lines in --help, which resulted in the current
output [1].

Collin

[1] https://lists.gnu.org/archive/html/coreutils/2013-02/msg00156.html




Information forwarded to bug-coreutils <at> gnu.org:
bug#78431; Package coreutils. (Thu, 15 May 2025 10:39:01 GMT) Full text and rfc822 format available.

Message #17 received at 78431 <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>, Collin Funk <collin.funk1 <at> gmail.com>
Cc: 78431 <at> debbugs.gnu.org, Ville Skyttä <ville.skytta <at> iki.fi>
Subject: Re: bug#78431: Unclear patch submission address
Date: Thu, 15 May 2025 11:38:15 +0100
On 14/05/2025 21:40, Paul Eggert wrote:
> On 2025-05-14 12:53, Collin Funk wrote:
>> I think that adding an email regardless would be good
> 
> Yes, now's a good time to revisit the decision in 2013 to remove the
> bug-reporting email address[1]. Plus, the current code is confusing.
> 
> How about the attached coreutils patch? It simplifies the code and goes
> back to the old way of doing things, which includes outputting the bug
> reporting address.
> 
> If this doesn't generate the output we want, surely we should change
> Gnulib's emit_bug_reporting_address rather than try to reinvent it.
> 
> [1]:
> https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8b6d3c5700526f962b12cd5901b55961c5e18186

Thanks for discussing this on list.
The main reason for the current instructions
was to avoid non bug reports on the bug-coreutils <at> gnu.org list,
but I haven't strong opinions on this,
so am happy to go with the proposed patch.

cheers,
Pádraig




Reply sent to Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility. (Thu, 15 May 2025 16:02:03 GMT) Full text and rfc822 format available.

Notification sent to Ville Skyttä <ville.skytta <at> iki.fi>:
bug acknowledged by developer. (Thu, 15 May 2025 16:02:03 GMT) Full text and rfc822 format available.

Message #22 received at 78431-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Pádraig Brady <P <at> draigBrady.com>,
 Collin Funk <collin.funk1 <at> gmail.com>
Cc: 78431-done <at> debbugs.gnu.org,
 Ville Skyttä <ville.skytta <at> iki.fi>
Subject: Re: bug#78431: Unclear patch submission address
Date: Thu, 15 May 2025 09:01:10 -0700
On 2025-05-15 03:38, Pádraig Brady wrote:
> I haven't strong opinions on this,
> so am happy to go with the proposed patch.

Thanks, I applied it and am closing the bug report.




This bug report was last modified today.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.