Your message dated Tue, 20 Nov 2018 17:40:25 +0100
with message-id <b2297a67-6704-6048-6750-2a013881c...@debian.org>
and subject line Re: Bug#914204: buildd.debian.org: buildd chroots should not
have merged /usr for now
has caused the Debian Bug report #914204,
regarding buildd.debian.org: buildd chroots should not have merged /usr for now
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
914204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: buildd.debian.org
Severity: serious
Tags: patch
Justification: likely to cause grave bugs in built binary packages
X-Debbugs-Cc: debian-ad...@lists.debian.org
As discussed in <https://bugs.debian.org/913229> and the debian-devel
thread starting at
<https://lists.debian.org/debian-devel/2018/11/msg00299.html>,
buildd chroots should not be generated with merged /usr. However, this
is now the default in stretch-backports' debootstrap.
Avoiding merged /usr for buildds mitigates a frequently-seen class of
bugs in which packages end up with wrong executable paths hard-coded,
for example /usr/bin/bash or /bin/apt-get (which would both work fine
on a merged-/usr system, but not on an unmerged-/usr system).
I attach an untested patch for the script in dsa-puppet that I think is
currently responsible for generating buildd chroots.
Several bugs involving wrong paths when a package
is built on a merged-/usr system are tracked in
<https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=m...@linux.it&tag=usrmerge>.
I'm also going to propose a patch for debootstrap to make --variant=buildd
disable merged /usr by default.
smcv
--- End Message ---
--- Begin Message ---
On 11/20/18 5:25 PM, Simon McVittie wrote:
> Package: buildd.debian.org
> Severity: serious
> Tags: patch
> Justification: likely to cause grave bugs in built binary packages
> X-Debbugs-Cc: debian-ad...@lists.debian.org
>
> As discussed in <https://bugs.debian.org/913229> and the debian-devel
> thread starting at
> <https://lists.debian.org/debian-devel/2018/11/msg00299.html>,
> buildd chroots should not be generated with merged /usr. However, this
> is now the default in stretch-backports' debootstrap.
>
> Avoiding merged /usr for buildds mitigates a frequently-seen class of
> bugs in which packages end up with wrong executable paths hard-coded,
> for example /usr/bin/bash or /bin/apt-get (which would both work fine
> on a merged-/usr system, but not on an unmerged-/usr system).
>
> I attach an untested patch for the script in dsa-puppet that I think is
> currently responsible for generating buildd chroots.
>
> Several bugs involving wrong paths when a package
> is built on a merged-/usr system are tracked in
> <https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=m...@linux.it&tag=usrmerge>.
>
> I'm also going to propose a patch for debootstrap to make --variant=buildd
> disable merged /usr by default.
>
https://salsa.debian.org/dsa-team/mirror/dsa-puppet/commit/b54f52d2899c5785923c804fdfbba0782c147da4
buildds will get new tarballs tomorrow.
Thanks,
Julien
--- End Message ---
