From: zimoun <zimon.toutoune@gmail.com>
To: "Maxime Devos" <maximedevos@telenet.be>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: Tobias Kortkamp <tobias.kortkamp@gmail.com>, guix-devel@gnu.org
Subject: Re: Dealing with upstream issues
Date: Tue, 28 Jun 2022 18:21:41 +0200 [thread overview]
Message-ID: <86letgep2i.fsf@gmail.com> (raw)
In-Reply-To: <cdea9d182daa9bb0df7fb1291372fc515a90db4a.camel@telenet.be>
Hi,
On Tue, 28 Jun 2022 at 14:21, Maxime Devos <maximedevos@telenet.be> wrote:
> zimoun schreef op di 28-06-2022 om 13:01 [+0200]:
>> Well, from my understanding, the question is: should a perfectly working
>> and fine submission be delayed because unrelated-to-Guix issues are in
>> upstream code?
>
> This is not the question. The dispute is about:
>
> Maxime Devos: https://issues.guix.gnu.org/55541#3
>> AFAICT the issues have not been reported upstream yet, so I don't
>> think we can close this entry on debbugs yet.
>
> zimoun:
>> Ludo said these unrelated-to-Guix issues are not blocker, from my
>> understandings. And I agree. Do you disagree?
>
> I agree too. What I disagree with, is ignoring the bug. The blocker
> for me is: appropriate parties need to be at least informed of bug if
> it isn't fixed.
And… as I wrote [1]:
I agree; we cannot fix the world. ;-) In the case of patch#55541, the
issues of cross-compilation can be reported directly to upstream and
another Debbugs number could be open.
1: <https://yhetil.org/guix/87wnd2w9mm.fsf@gmail.com>
The bug is not ignored, to the contrary. But it is not a blocker for
patch inclusion and so patch#55541 can be closed.
You are free, as the reviewer, to open a report for Guix pointing the
issue of cross-compilation of ’azpainter’; bonus point for you if you
open an issue upstream. Extra point for the one who fixes the package.
Well, you and me spend more time in discussing that than in just
reporting the issue. ;-)
Cheers,
simon
next prev parent reply other threads:[~2022-06-28 16:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6d31ff958ec0c75cbba8324a275315d195a54902.1653045472.git.tobias.kortkamp@gmail.com>
[not found] ` <87sfntu6ft.fsf@gnu.org>
[not found] ` <b6d482002f7773e65e02dbbbf354e1c0178b823a.camel@telenet.be>
2022-06-27 10:10 ` Dealing with upstream issues Ludovic Courtès
2022-06-27 10:30 ` Maxime Devos
2022-06-27 10:37 ` Maxime Devos
2022-06-27 12:32 ` zimoun
2022-06-27 14:20 ` Maxime Devos
2022-06-27 15:06 ` zimoun
2022-06-27 15:41 ` Maxime Devos
2022-06-28 11:01 ` zimoun
2022-06-28 12:21 ` Maxime Devos
2022-06-28 16:21 ` zimoun [this message]
2022-06-28 16:47 ` Maxime Devos
2022-06-28 17:36 ` zimoun
2022-06-28 20:03 ` Maxime Devos
2022-06-28 12:22 ` Maxime Devos
2022-06-28 12:31 ` Maxime Devos
2022-06-28 16:25 ` zimoun
2022-06-28 16:47 ` Maxime Devos
2022-06-29 6:07 ` bokr
2022-06-29 7:29 ` Missing tags in Debbugs? zimoun
2022-06-29 13:45 ` Bengt Richter
2022-06-30 11:53 ` Dealing with upstream issues Ludovic Courtès
2022-06-27 12:53 ` zimoun
2022-06-27 14:32 ` Maxime Devos
2022-06-27 15:23 ` zimoun
2022-06-27 15:47 ` Maxime Devos
2022-06-27 16:03 ` Maxime Devos
2022-06-27 16:14 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86letgep2i.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
--cc=tobias.kortkamp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).