Path: csiph.com!tncsrv06.tnetconsulting.net!newsfeed.endofthelinebbs.com!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: James Addison Newsgroups: linux.debian.maint.python Subject: Re: Upload request: meson-python Date: Sat, 05 Oct 2024 16:30:01 +0200 Message-ID: References: X-Original-To: Simon McVittie X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Oct 5 14:21:49 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.2 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .jp-hosting. - helo: .mail-ed1-x52e.google. - helo-domain: .google.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5 X-Gm-Message-State: AOJu0YwxdTDyy0Hs0og9GbOcPUNWE4G0Af98JPUwQ1lEEnj1bw4Fik9i GN9kEsxJtV+XROIj1N1dftPZCZGbIbZ3FMqc/0vCZ027cpudAuy2g7L7XxAG6ZK/pA1T6rP7CbL auAs3zSPWnDiAW9zXb6JE1j3yz6w8TQNzt9kKyw8veV8Ndc7AAw== X-Google-SMTP-Source: AGHT+IEMWuqbN4IdlTjd4E8GgmFewaPULDk1ev8yiIa9l38M9uBErWIxsX2UEQYLF9qIIyMcoVoXyU8umT3SqD+C4SE= X-Received: by 2002:a05:6402:3553:b0:5c7:20a2:6b7e with SMTP id 4fb4d7f45d1cf-5c8d2e73b13mr5046525a12.22.1728138093860; Sat, 05 Oct 2024 07:21:33 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/22393 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CALDQ5Ny5W7i-Bua1XdppDigu1o87UA-pDCVoNpcBhxtjPnzPeg@mail.gmail.com Approved: robomod@news.nic.it Lines: 36 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Sat, 5 Oct 2024 14:21:23 +0000 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:16330 On Fri, 4 Oct 2024 at 12:58, Simon McVittie wrote: > > On Thu, 03 Oct 2024 at 15:54:16 +0000, James Addison wrote: > > I'd like to request an upload of the src:meson-python package, in > > particular to close bug #1076806, a reproducibility bug related to > > documentation copyright notices > > Done, but I'm curious why making this particular package reproducible > was a high enough priority for you that it needed to be called out > specifically? I don't normally prioritize uploading low-impact fixes like > this one, on the basis that each upload needs testing to make sure it > isn't going to regress other packages, and minor fixes can be included > next time there is a more important update to be done. Thank you for the upload - in this case, I'd been iterating through the list of Debian 'package sets'[1] displayed on the Reproducible Builds test result website, searching for any packages that could be encouraged along the path to building reproducibly. Core/popular package sets seem like good places to look for opportunities to improve Debian reproducibility for many users, although sometimes with associated risk because of the number of systems potentially affected. Although it doesn't appear there any more, I believe meson-python was listed in the 'build-essential-depends' set. After noticing that it was pending upload, and had been for a reasonable duration of time, I asked around in the RB IRC channel about a potential NMU (that I understand are generally considered not ideal, but sometimes acceptable), and then after some feedback there, decided that it might make more sense to ask directly on the bugreport and mailing list. If I'd felt that this was one of a category of similar possible uploads, I would have attempted to describe/list the relevant packages - in this case the package was a one-off. [1] - https://tests.reproducible-builds.org/debian/unstable/amd64/index_pkg_sets.html