Your message dated Fri, 2 Jun 2017 11:30:24 +0200
with message-id <20170602093024.ga13...@fatal.se>
and subject line Re: Bug#863269: usrmerge is not yet ready for a stable release
has caused the Debian Bug report #863269,
regarding usrmerge is not yet ready for a stable release
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.)
--
863269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usrmerge
Version: 13
Severity: serious
Control: block -1 by 860523 810158 759410 837928
While merged /usr seems to be the future and will likely be the
default in buster, shipping the usrmerge package in stretch
wouldn't bring real benefits to users while creating situations
where the only proper solution for a user might be to reinstall.
Anyone explitely using "debootstrap --merged-usr" should be aware
that this is a non-default option, but just installing a package
shouldn't result in errors like the following in a stable release:
# apt-get install usrmerge
...
# apt-get install ksh
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libfile-find-rule-perl libnumber-compare-perl libtext-glob-perl
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
binfmt-support
The following packages will be REMOVED:
usrmerge
The following NEW packages will be installed:
binfmt-support ksh
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Need to get 950 kB of archives.
After this operation, 3521 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian stretch/main amd64 binfmt-support amd64
2.1.6-2 [59.5 kB]
Get:2 http://deb.debian.org/debian stretch/main amd64 ksh amd64
93u+20120801-2+b1 [890 kB]
Fetched 950 kB in 0s (1137 kB/s)
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or
directory)
(Reading database ... 10978 files and directories currently installed.)
Removing usrmerge (13) ...
Selecting previously unselected package binfmt-support.
(Reading database ... 10972 files and directories currently installed.)
Preparing to unpack .../binfmt-support_2.1.6-2_amd64.deb ...
Unpacking binfmt-support (2.1.6-2) ...
Selecting previously unselected package ksh.
Preparing to unpack .../ksh_93u+20120801-2+b1_amd64.deb ...
Unpacking ksh (93u+20120801-2+b1) ...
Setting up binfmt-support (2.1.6-2) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/binfmt-support.service ->
/lib/systemd/system/binfmt-support.service.
Running in chroot, ignoring request.
Setting up ksh (93u+20120801-2+b1) ...
update-alternatives: using /bin/ksh93 to provide /bin/ksh (ksh) in auto mode
update-alternatives: error: unable to install '/usr/bin/ksh.dpkg-tmp' as
'/usr/bin/ksh': No such file or directory
dpkg: error processing package ksh (--configure):
subprocess installed post-installation script returned error exit status 2
Processing triggers for systemd (232-23) ...
Errors were encountered while processing:
ksh
E: Sub-process /usr/bin/dpkg returned an error code (1)
#
Additionally, there is also an unknown number of runtime bugs
like #860523 where code makes path assumptions that break with
merged /usr. And there is no good way to find these automatically,
only a longer time of merged /usr as default in testing/unstable
would find them.
The worst part is that the merged /usr via "apt-get install usrmerge"
is irreversible, and having to tell users of stable that they have
to reinstall for reverting it would be a huge blow for the stable
reputation of Debian.
--- End Message ---
--- Begin Message ---
Hello Adrian,
On Wed, May 24, 2017 at 08:52:12PM +0300, Adrian Bunk wrote:
> If a member of the release team states that this is acceptable
> for a stable release, then that's how it is.
If the release team don't want something to be part of testing they
have the power to just remove it. No bug reports needed.
Also the release team decides if something is release critical or
not. Until they have spoken on it, the what the maintainer says
goes (which is also usually the response you'll get from the
release team).
(I think that at this point we will have to support merged-/usr
for stretch no matter what happens. There are already installed
systems which got merged-/usr from the start and other systems
that has already been converted with usrmerge. Removing one tool
to do further conversions will not change that fact.)
>
> Until then I prefer to keep this bug open.
Please explain how you got the power to override a maintainer decision
on your own. AFAIK the constitution says only the CTTE can do this
and even when they do a simple majority isn't enough.
I'm pretty sure you don't have that power, thus taking the liberty
of closing this report again. (Also, this is not a bug in usrmerge
but in the packages that hasn't been fixed yet. Feel free to argue
that those bug reports should be raised to RC instead, since those
are actual bugs.)
Regards,
Andreas Henriksson
--- End Message ---
