Hi,
To recap the current issue: The ia32-libs-tools package has been
removed from Debian, and I am uncertain of the technical reasons that
underlie this removal. While no such reasons have been communicated to
me, here are some of the speculations on them.
Possible reasons for its removal:
- ia32-libs-tools hinders implementing multiarch
While this was true in older versions the first steps to allow a
smooth transition for multiarch had already been taken. The multiarch
proposal is still slightly in flux, and as yet is unimplemented. But
going by the proposal as it stands so far there is a plan in place
that will allow a smooth transition. The ia32-* packages will be
replaced by multiarch packages as they become available or be removed
all in one go if the user chooses not to follow the upgrade path.
There is also a fall-back in place in case things don't work out where
all ia32-* will be removed when multiarch comes. That would do
automatically what users have to do manually now to undo their use of
ia32-libs-tools. So there is a smooth transition plan and a safety
net.
- we have ia32-libs, we don't need a second method for 32bit support
Ia32-libs does not and more importantly can not fully replace
ia32-libs-tools. It will always lack security fixes, have mismatched
versions of packages, lack unstable packages and lack libraries
altogether that users need to run their programs. It also provides no
way to install and upgrade binary packages like skye, biblepro and
many more. Ia32-libs-tools is not just another ia32-libs. It is
better, more flexible and it is more.
- nobody uses ia32-libs-tools and we want to prevent anyone from
starting now so they don't end up in a dead end when multiarch comes
Popcon showed nearly 500 users. People have been using ia32-libs-tools
for 1 1/2 years now and many ia32-* packages are already installed on
users systems. By removing ia32-libs-tools users are stuck in an
artificial dead end with no way back or forward. They now have to
purge all ia32-* packages and binaries that depend on them and then
use a completely different method to get them back (e.g. setup a
chroot). Ia32-libs-tools itself will provide the way forward and will
bring users back to "pure" Debian by transitioning into multiarch when
that becomes reality.
- the transformation in ia32-libs-tools breaks things
The transformation in ia32-libs-tools is a combination of what
ia32-libs does during build and dpkg-cross/apt-cross does during
installation. Both are well understood. On top of that ia32-libs-tools
has been in use for 1 1/2 years. The combination of both methods has
proven to work reliable for many uploads of new libraries and the
limitations and pitfalls are know well understood.
What did break was the maintainer scripts in version 18 and has been
fixed or reverted in subsequent uploads. That never affected the
transformation of packages and having been solved is no removal reason
either.
- maintainers have to support ia32-libs-tools as well as ia32-libs and
multiarch
Anything that works in ia32-libs or multiarch (as far as the proposed
specs say) works in ia32-libs-tools. Ia32-libs-tools also fixes
several issues ia32-libs has all without the need for any maintainer
to lift a finger. Ia32-libs-tools does not force extra work onto
maintainers. On the other hand ia32-libs-tools allows maintainers who
are interested to pitch in and provide a helper script where
necessary. Normally ia32-libs-tools provides all the necessary
helpers but if a maintainer wishes to opt-in and get a closer control
over the transformation of his package then ia32-libs-tools is
prepared for that.
- bug reports will go to the wrong place
Firstly that hasn't happened yet, in 1 1/2 years of use, in any
noticeable quantity. Overall I think 3 bugs were filed on the wrong
package during that time. But it is a valid point and to address the
issue I am prepared to set the Maintainer of converted packages to me
and add a /usr/share/reportbug/<package>/control file containing
"Submit-As: ia32-libs-tools" in every converted package.
If there is a technical reason for the removal of ia32-libs-tools, it
has not been communicated. I think people working on packages have the
right to be told why the packages are unfit for the project, if for no
other reason than for the mistake to be not repeated, and to ensure
that there is indeed a technical reason for removal.
I ask the technical Committee to ascertain that such a technical
reason exists, and to communicate this to the rest of the project, or,
failing such a technical reason, to overturn the ftp-masters decision
to remove it.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
