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: Mon, 27 Jun 2022 17:23:19 +0200 [thread overview]
Message-ID: <87h746w2oo.fsf@gmail.com> (raw)
In-Reply-To: <e411624944ba93bfbc7b31c629b5d60d9583d881.camel@telenet.be>
Hi,
On Mon, 27 Jun 2022 at 16:32, Maxime Devos <maximedevos@telenet.be> wrote:
>> Maybe I misunderstand the point. To me, the aim of the package
>> submission is the inclusion in Guix. AFAIK, the Guix project is not
>> applying any standard audit on the upstream code before inclusion.
>>
>> Therefore, if the upstream code is poor in some areas, then it is not
>> blocking for the package adoption in Guix…
>
> I think there should be some degree of standards (where I mean
> standards in the non-shodyness sense of the word, not in the sense of
> specs, though specs would be nice too) and of audit (bundling, malware,
> non-free, bugs) -- some of which are blocking (bundling, malware, non-
> free, some bugs), some of which aren't (some other bugs).
>
> E.g., see removal of unmaintained Python, of some old SSL libraries
You are mixing unrelated topics, IMHO.
We have policies, not standard.
«A policy is a set of ideas or plans that is used as a basis for making
decisions, especially in politics, economics, or business.»
«A standard is a level of quality or achievement, especially a level
that is thought to be acceptable.»
>> > My view is that such issues should be reported upstream but cannot
>> > alone
>> > block package adoption in Guix.
>>
>> I agree; we cannot fix the world. ;-) In the case of patch#55541, the
>> issues of cross-compilation can be reported directly to upstream
>
> Agreed -- I did not ask that explicitely in #55541, but the implied
> question was to report it upstream (or fix local, that could be done
> too). But my point is that this should have been done _before_ merging
> the patch.
So, what are you explicitly asking? :-)
>> and another Debbugs number could be open.
>
> Would be pointless. Standard policy seems to be to leave the debbugs
> issue unresolved forever, then someone does some cleanup in debbugs to
> close the debbugs number due to lack of activity or such. Things would
> be delayed forever.
Old unsolved bugs are still open. The cross-compilation of one package is
an issue for sure, but:
1. it is not an issue for inclusion in Guix
2. it has to be solved by people interested by cross-compilation
Other said, it cannot be asked to submitter to fix unrelated-to-Guix
issue on upstream code. Although cross-compilation issue is somehow
related to Guix. ;-)
Cheers,
simon
next prev parent reply other threads:[~2022-06-27 15:40 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
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 [this message]
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=87h746w2oo.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).