Bug#909643: closed by Ben Hutchings (Re: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system)

2019-02-03 Thread Ben Hutchings
On Mon, 2019-02-04 at 10:43 +0900, Stephane Tranchemer wrote:
> Hi,
> You are right Ben, this was the culprit.
> 
> The bottom line is, in a previous version of the debian distribution the
> busybox package was called "busybox-cvs-static".
> 
> But at a time it just gone to "busybox-static", so when doing the normal
> procedure of
> apt-update
> apt-upgrade
> apt-distupgrade
> 
> it is not replaced by the newer version...

Yes, and it obviously should have been.

> Quite a nasty pitfall.
> 
> Thanks for your time.

It appears that busybox-cvs was only uploaded once and only included in
the Debian 3.1 "sarge" release.  It was then obsoleted by newer
versions of busybox, but that didn't build the transitional packages
needed to cause an automatic upgrade.

But I think it is now much to late to do anything about this.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.




signature.asc
Description: This is a digitally signed message part


Bug#909643: closed by Ben Hutchings (Re: doing a dist-upgrade from debian7 to debian8 ended with a non bootable system)

2019-02-03 Thread Stephane Tranchemer
Hi,
You are right Ben, this was the culprit.

The bottom line is, in a previous version of the debian distribution the
busybox package was called "busybox-cvs-static".

But at a time it just gone to "busybox-static", so when doing the normal
procedure of
apt-update
apt-upgrade
apt-distupgrade

it is not replaced by the newer version...

Quite a nasty pitfall.

Thanks for your time.


> The screenshot shows:
>
> "busybox 20040623-1"
>
> You have an ancient version of busybox installed and you must upgrade
> it.
>
> Ben.
>
> --
> Ben Hutchings
> Horngren's Observation:
>   Among economists, the real world is often a special case.
>
>
>