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

Bug#614159: upgrade-reports: [lenny->squeeze] Many issues/papercuts



On Sun, Feb 20, 2011 at 03:36:48PM +0100, Javier Fernández-Sanguino Peña wrote:
> On Sat, Feb 19, 2011 at 04:17:00PM -0800, Josh Triplett wrote:
> > - I started the upgrade within X.  Partway through the upgrade, dbus got
> (...)
> >   specific packages to upgrade first from a console.  Due to this issue,
> >   I did the rest of the upgrade from a console.
> 
> This is the recommended mechanism for upgrades, see:
> http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#upgrade-preparations

Good to know, but a release note just notes an issue that needs working
around; always better to fix the system so the release note no longer
applies. :)

> > - Restarting gdm (each time) switches to the gdm terminal, so I had to
> >   switch *back* to the console to finish the upgrade.
> 
> Described already in the Release Notes, see:
> http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#console-change

Good to know that the release notes document this bug, but it still
seems better to fix it than document it. :)

> > - udev renamed all network interfaces to new names after the upgrade,
> >   despite the MAC addresses and similar not changing.  I had to manually
> >   edit persistent-net.rules to fix them back to eth0 and wlan0.
> 
> This is not expected, device renumbering could happen (see
> http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#device-reorder).
> Did you have the proper rules defined in
> /etc/udev/rules.d/70-persistent-net.rules or did they change?

After upgrading, 70-persistent-net.rules contained multiple rules for
the same devices with the same MAC addresses.  I saw that the MAC
addresses matched, but I didn't compare the lines closely other than
that.  I probably should have recorded the exact contents before fixing
it by deleting the original lines and renumbering the new ones.

> > - I ended up grabbing 2.6.37 from unstable to get a better wireless
> >   driver.  When I installed 2.6.37, it warned about missing firmware
> >   from firmware-iwlwifi, but the system already had the latest version
> >   of firmware-iwlwifi installed.
> 
> Maybe this needs to be submitted as a separate bug report to the kernel
> maintainers.

Sure, done.  I wanted to include the full narrative of the upgrade in a
single report to note the issues that arose, but I can still help split
out individual reports as appropriate.

> Do you have a full log of the upgrade (as described in [1]) this could be
> helpful to review it.
[...]
> [1]
> http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#record-session

No, I don't have a script log of the upgrade.

- Josh Triplett



Reply to: