sending to guix-patches does not seem to show?

sending to guix-patches does not seem to show?

[Andy Tai]

Hi, I wonder if anyone notices that sending a patch to guix-patches
does not seem to result in the creation of a new debbugs issue?

Re: sending to guix-patches does not seem to show?

[Artyom V. Poptsov]

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]

Hello,

FWIW, I'm having the same issue since yesterday.  I've tried to send a
patch from Gmail twice but to no avail.

- avp

-- 
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
Home page: https://memory-heap.org/~avp/
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE  B57C E9C5 A2D9 0898 A02F

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]

Re: sending to guix-patches does not seem to show?

[Felix Lechner via]

Hi Andy,
Hi Artyom,

> sending a patch to guix-patches does not seem to result in the
> creation of a new debbugs issue

> I'm having the same issue

You are not alone. [1][2]

Please note that I do not maintain Debbugs.  I would like to, but lost
an internal appeals process, which was non-public. I wrote:

> The Debbugs system is unmaintainble. FSF is unable and unwilling (!)
> to publish a code base for the version deployed on
> debbugs.gnu.org. I'd call that a disaster for a free-software advocacy
> group.
>
> Without a code base, no one can propose patches. It's absurd for
> anyone working with free software. On a practical level, it is
> impossible to fix or discuss issues like these. [3]

To preserve at least some privacy and perhaps goodwill, I'll paraphrase
the response. I believe it correctly reflects the applicable GPL-2
license [4] yet somehow missed my point:

    FSF did not write Debbugs. FSF does not distribute any version of
    it. No one who uses a program and patches it has an obligation to
    release the private modified version.

I hope that publishing the information did not violate anyone's privacy
expectations.  The Guix community deserved to know.

To sum it up, there are capable people who work on Debbugs. It's just
not me.  Please direct comments about Debbugs to the help-debbugs
mailing list. [5] With some luck, your issue will be addressed shortly.
Maybe it was fixed already. Thank you!

Kind regards
Felix

[1] https://mail.gnu.org/archive/html/help-debbugs/2024-02/msg00028.html
[2] https://mail.gnu.org/archive/html/help-debbugs/2024-02/msg00030.html
[3] https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00187.html
[4] https://codeberg.org/lechner/debbugs-gnu/src/branch/history/COPYING
[5] https://lists.gnu.org/mailman/listinfo/help-debbugs

Re: sending to guix-patches does not seem to show?

[Andy Tai]

Hi, my patches now get acknowledged and multiple issues created... now
I will go to merge them,....

On Sun, Feb 18, 2024 at 9:42 AM Felix Lechner
<felix.lechner@lease-up.com> wrote:
>
> Hi Andy,
> Hi Artyom,
>
> > sending a patch to guix-patches does not seem to result in the
> > creation of a new debbugs issue
>
> > I'm having the same issue
>
> You are not alone. [1][2]

Re: sending to guix-patches does not seem to show?

[Felix Lechner via]

Hi Andy,

On Sun, Feb 18 2024, Andy Tai wrote:

> multiple issues created... now I will go to merge them,....

You can do so with "forcemerge" via the control server but if no one has
commented yet, I would instead close the duplicate bugs via messages to
XXX-done@debbugs.gnu.org that state:

  Duplicate of #YYY. Closing.

Kind regards
Felix