[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1041207: marked as done (debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE)



Your message dated Sat, 15 Jul 2023 22:22:00 +0000
with message-id <E1qKneK-007S67-KD@fasolo.debian.org>
and subject line Bug#1041207: fixed in debootstrap 1.0.128+nmu4
has caused the Debian Bug report #1041207,
regarding debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE
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 owner@bugs.debian.org
immediately.)


-- 
1041207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041207
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.128+nmu3
Severity: grave

bluca's NMU on 2023-07-15 makes debootstrap produce chroots using the
aliased-dirs scheme.  While it's currently the default scheme for non-buildd
systems, it is both not supported by dpkg (with no solution in sight), but
is also likely to produce packages that are explicitely forbidden by a
recent CTTE ruling that disallows moving files between directories aliased
by the current usrmerge scheme.

Quoting the still unsolving issues is pointless (you can read about them
in massive threads in a number of places) as bluca seems to be ignoring
them completely.

But, what matters here is the CTTE ruling in #1035831 -- for the time being,
packages must not move files between locations affected by the aliasing.

Packages built in an usrmerged chroot place such files under /usr while
built without usrmerge into whatever place they were installed to -- which
is a direct breach of the ruling.

Thus, that change needs to be reverted for now, and all packages built
with 1.0.128+nmu3 need to be either rebuilt or at least checked for such
a violation (as most are unaffected).


Meow!
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-rc1-00036-gc493f11e457d (SMP w/64 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debootstrap depends on:
ii  wget  1.21.3-1+b2

Versions of packages debootstrap recommends:
ii  arch-test               0.21-1
ii  debian-archive-keyring  2023.3
ii  gnupg                   2.2.40-1.1

Versions of packages debootstrap suggests:
ii  binutils                                 2.40.90.20230705-1
pn  squid-deb-proxy-client                   <none>
ii  ubuntu-archive-keyring                   2020.06.17.1-1
ii  ubuntu-keyring [ubuntu-archive-keyring]  2020.06.17.1-1
ii  xz-utils                                 5.4.1-0.2
ii  zstd                                     1.5.5+dfsg2-1

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.128+nmu4
Done: Adam Borowski <kilobyte@angband.pl>

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041207@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adam Borowski <kilobyte@angband.pl> (supplier of updated debootstrap package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 15 Jul 2023 23:32:31 +0200
Source: debootstrap
Architecture: source
Version: 1.0.128+nmu4
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Adam Borowski <kilobyte@angband.pl>
Closes: 1041207
Changes:
 debootstrap (1.0.128+nmu4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Revert defaulting buildds to usrmerge, as this makes packages move
     files in aliased dirs contrary to CTTE#1035831.  Closes: #1041207
     NB1: such a change was very very inappropriate for a NMU.
     NB2: looking for packages needing a rebuild due to this will be "fun".
Checksums-Sha1:
 78c9a3b0b7e1807e1332d03cefe1bba440a67cc6 1988 debootstrap_1.0.128+nmu4.dsc
 3512c3d632d410c1987da33eec11fa7a2f5722c0 85199 debootstrap_1.0.128+nmu4.tar.gz
 28183cf8d6b5a822364b5cf4685d5dc28dcbdf57 5794 debootstrap_1.0.128+nmu4_source.buildinfo
Checksums-Sha256:
 b6c3983dda30f237b6f1d259e2f55ae633e3036ca95b82c360b078e806b4826a 1988 debootstrap_1.0.128+nmu4.dsc
 659c4b5f93bec18fb9a7ca67dc98de484c0d14aea58db12e5f65e37563752223 85199 debootstrap_1.0.128+nmu4.tar.gz
 dce0a8896e65ef72a8d59c464e16e50c4b2c646ef7428c00580ded5c8959a5e2 5794 debootstrap_1.0.128+nmu4_source.buildinfo
Files:
 73f7eb8eeb376715995850f104be0113 1988 admin optional debootstrap_1.0.128+nmu4.dsc
 56a54be866664f24d8cea510a8071937 85199 admin optional debootstrap_1.0.128+nmu4.tar.gz
 281277b99e27cb94e0e047d251be86e1 5794 admin optional debootstrap_1.0.128+nmu4_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmSzFBkACgkQweDZLphv
fH4+xw//QsfijmIzs/hEWFkOZHGUxjgvgLTVflULWwpBs/5jz2ajQ4QQdnwTE8Yj
vOZJvuwyr7zgczrB1z2HQlxBkrYP8f9OR7aGjMB2BuK9IkaoA1znH85YaEUIBmXg
Nox+O6HJj+X0r3KsBisx3saZ1zt158egBwXoDRMVwcP+7M3xXWxZ0odDOYB04NIc
AUmmSr1oGvG3lj/JTsVmQIYgJGGkEPLhQ7bQgAw9YwJrKQDGcuX57jIuBAHxuRRG
q4ei2BieQrzoT8dJzEOZ7VtyZsJf5OaB+4qKV89EiEqBc2AafUBIKULEgzp8TNMp
enJIrW+RNmnCuxTbq2B0ZRZA7MSvmtps2vonWHZQzAujJm0nMsrycE1I5ltvTsnr
tD/1bg/dsVojusli0jv9AitQ2DDmCd1hVrfYGH/4rkcN/AZHIQmKDd5CidVT/Wd/
NL99CwQlF2inEnsqj+M62dM1vAkdAOTRKju80LcTCI9FOKoCzBT6xn5IEBg+mVj2
MPXThSYd9FPpbIFLcb+fL5bPWbVpOrJiANV+GwW5sB/hZdJOEf3ecpAF2uiqBMDI
XXRdhzdJpC15cHYT2royUL3c5V/cguni51kr3bfstYLC20PIWpd4jSTOWTxOO3gA
X4TrpRboyQiixi5medeE62gu5fmk7A68bg25H79z+ouptnZZif4=
=6ZNh
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: