On 11/09/2023 09.25, Helmut Grohne wrote:
It also
is unclear how it affects reproducible builds since such builds depend
on the performance characteristics of the system performing the build.
It is worth noting that the performance (execution time) of a
build-system does not matter for profili
Control: block 1051371 by 1050001
Hi,
On Tue, 2023-09-12 at 20:48 -0700, Russ Allbery wrote:
> I think the root problem behind this bug is that it is revealing we have
> not made a decision about /bin and /usr/bin path references in Debian
> after /usr-merge. Various people, myself included, ma
Processing control commands:
> block 1051371 by 1050001
Bug #1051371 [debian-policy] Post-/usr-merge paths for script interpreters
1051371 was blocked by: 1050001
1051371 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1051371 to the same blocks
previously set
--
1051
Processing control commands:
> block 1051371 by 1050001
Bug #1051371 [debian-policy] Post-/usr-merge paths for script interpreters
1051371 was not blocked by any bugs.
1051371 was not blocking any bugs.
Added blocking bug(s) of 1051371: 1050001
--
1050001: https://bugs.debian.org/cgi-bin/bugrepo
Russ Allbery writes:
> Russ Allbery writes:
>> Maybe the right way to do this is just have two examples, one as the
>> default and another if you're using tmpfiles.d functionality added in a
>> specific version of systemd that's newer than the version shipped with
>> the stable version of Debian
Russ Allbery writes:
> Maybe the right way to do this is just have two examples, one as the
> default and another if you're using tmpfiles.d functionality added in a
> specific version of systemd that's newer than the version shipped with
> the stable version of Debian prior to the one you're tar
Control: retitle -1 Post-/usr-merge paths for script interpreters
Simon pointed out that this bug is not yet ready to act on, which was very
helpful. Thank you. However, presumably the buildds will be /usr-merged
at some point in the not-too-distant future, and we do need to decide what
to do af
Processing control commands:
> retitle -1 Post-/usr-merge paths for script interpreters
Bug #1051371 [debian-policy] debian-policy: stop referring to specific paths in
scripts shebang examples
Changed Bug title to 'Post-/usr-merge paths for script interpreters' from
'debian-policy: stop referrin
I'm going to take this reply out of the bug to just the Policy list, since
this really isn't part of the bug discussion and folks trying to
understand the bug shouldn't need to read through it. I should have done
that with my original message. I'm going to leave the subject line the
same so that
Processing commands for cont...@bugs.debian.org:
> user debian-pol...@packages.debian.org
Setting user to debian-pol...@packages.debian.org (was r...@debian.org).
> limit package debian-policy
Limiting to bugs with field 'package' containing at least one of 'debian-policy'
Limit currently set to '
Guillem Jover writes:
> How about the attached patch, based on the text in deb-substvars(5)?
This looks great, thank you. Seconded.
> From 024d94daeb0ab0e7c447868a1b8f9ff953850404 Mon Sep 17 00:00:00 2001
> From: Guillem Jover
> Date: Tue, 12 Sep 2023 22:47:27 +0200
> Subject: [PATCH] Update
Hi!
On Fri, 2015-07-24 at 18:04:41 +0200, Guillem Jover wrote:
> Package: debian-policy
> Version: 3.9.7.0
> Severity: wishlist
> As discussed in the debian-policy list, the Installed-Size algorithm
> as implemented in dpkg-gencontrol changed due to #650077. So the
> current wording is out-of-syn
On Mon, Sep 11, 2023 at 07:11:30PM +0100, Simon McVittie wrote:
> Games are often written for performance more than correctness, and
> frequently do non-ideal things or have unfixed security issues. If we
> separate them into /usr/games and avoid putting that directory in root's
> PATH, then tab co
Helmut Grohne writes:
> more and more packages implement a technique called profile guided
> optimization. The general idea is that it performs a build that is
> instrumented for profiling first. It then runs a reasonable workload to
> collect profiling data, which in turn is used to guide the op
On Tue, Sep 12, 2023 at 10:49:02AM -0700, Russ Allbery wrote:
> To take an example that I've been trying to get rid of for over a decade,
> many of the /usr/share/common-licenses/BSD references currently in the
> archive are incorrect. There are a few cases where the code is literally
> copyrighte
Package: debian-policy
Version: 4.6.2.0
Severity: wishlist
X-Debbugs-Cc:
debian-cr...@lists.debian.org,rb-gene...@lists.reproducible-builds.org
Hi,
more and more packages implement a technique called profile guided
optimization. The general idea is that it performs a build that is
instrumented f
Jonas Smedegaard writes:
> Strictly speaking it is not (as I was more narrowly focusing on) that
> the current debian/copyright spec leaves room for *ambiguity*, but
> instead that there is a real risk of making mistakes when replacing with
> centrally defined ones (e.g. redefining a local "Expat
Quoting Russ Allbery (2023-09-12 18:15:27)
> Jonas Smedegaard writes:
>
> > If you mean to say that ambiguous MIT declarations exist in
> > debian/copyright files written using the machine-readable format, then
> > please point to an example, as I cannot imagine how that would look.
>
> I can se
Jonas Smedegaard writes:
> If you mean to say that ambiguous MIT declarations exist in
> debian/copyright files written using the machine-readable format, then
> please point to an example, as I cannot imagine how that would look.
I can see it: people use License: Expat but then include some lic
Quoting Hideki Yamane (2023-09-12 09:27:12)
> On Sun, 10 Sep 2023 18:29:36 +0200
> Bill Allombert wrote:
> > Or we could generate DEBIAN/copyright from debian/copyright using data in
> > license-common-list at build time. So maintainers would not need to manage
> > the copying
> > themselves.
>
Hi,
On Sun, 10 Sep 2023 18:29:36 +0200
Bill Allombert wrote:
> Or we could generate DEBIAN/copyright from debian/copyright using data in
> license-common-list at build time. So maintainers would not need to manage
> the copying
> themselves.
One problem is, that some software declares that the
21 matches
Mail list logo
