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

Re: apt wants to remove bash



Wolfgang Mader wrote:
> Will this be fixed soon?

You misunderstand.  Things have been fixed.  That is actually the
problem you are now seeing.  You now need to bring your system in line
with the following command.

  apt-get install base-files=3.1.2

This is probably going to become a very FAQ among the old timer crowd
who have been running the Debian amd64 port since the beginning.
(Newcomers won't see the problem at all.)  It's great that you were
supporting amd64 for a long time.  However because the development of
the port needed some effort it has not been entirely a clean upgrade.
So now you need to do something relatively simple to fix your system.

There are two problems.  The first problem is that in order to develop
the original amd64 port it was necessary to create revised packages.
A base-files version 2.3.2.ds1-20.0.0.1.pure64 was created which only
differed from the standard version by having a Replaces: base-files
(<< 3.1.2-0.0.0.1.pure64).  This was done for upgrade purposes.  The
base-files and libc6 packages are related and one depends upon the
other.  There was also a similar issue with lib64 symlinks moving from
package to package.  Think of this as growing pains.

This was the way things were for a long time.  Meanwhile the fixes
went into the upstream packages.  So now there is no need for a
special version anymore.  The recent reorganization of the deb depot
structure from /pure64 to /debian-pure64 has converted to being in
sync with the main Debian archive.  This is a good thing because we
really want amd64 to be a mainstream Debian architecture.  But it now
means that long time users will need to do some fixes.  This is the
second problem.  The tweaked package has a later version than the
standard package.  So this upgrade can not happen automatically.  But
we want the standard version.

Run the above apt-get command to downgrade base-files to the standard
Debian version.

If you install from installation media that still contains the
2.3.2.ds1-20.0.0.1.pure64 version on the disk then you will see this
problem again every time you install from that older media.  Pull a
newer copy of the installation media.  Or just remember to manually
force a downgrade of the package.

Bob

Attachment: signature.asc
Description: Digital signature


Reply to: