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

Bug#869849: marked as done (upgrade-reports: Successful upgrade (Jessie->Stretch) on a W550s)

Your message dated Tue, 9 Mar 2021 21:55:37 +0100
with message-id <43b04122-a47b-31d6-d220-2540e920dc6b@debian.org>
and subject line upgrade report for EOL Debian release
has caused the Debian Bug report #869849,
regarding upgrade-reports: Successful upgrade (Jessie->Stretch) on a W550s
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 owner@bugs.debian.org
immediately.)


-- 
869849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869849
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: normal

I just performed a reasonably smooth and successful upgrade from Jessie
to Stretch on a Lenovo W550. The system was previously mostly Jessie,
with some stuff from backports, some packages from unstable, one or two
from third party repositories, and perhaps some still left from
deb-multimedia.

The upgrade went smoothly. Deciding what to do about new configuration
files is always difficult, and one doesn't always have that much
patience during an upgrade, but I haven't seen any problems yet arising
out of my choices (generally keep mine when I know I've made significant
changes, otherwise allow installations of the new one).

My new Stretch system did suffer from a bad bug in the chrony package
that broke the whole ifupdown system:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868491

But this was easily fixed by manually downloading and installing the
fixed version from unstable.

I was a bit nonplussed when upon reboot I ended up in lightdm's login
screen, rather than my usual VT - this is apparently because
xfce4-session now recommends light-locker, which depends on lightdm. I
use xscreensaver, but I learned a while ago that for security, I
probably should be logging in via a dm rather than doing startx from a
console (since X crashing or being shutdown could leave an attacker with
a logged in console), so I decided to leave lightdm installed.

The system did lockup shortly after the actual installation (while I was
performing some post-installation housekeeping, purging removed
packages, IIRC), but the problem has not recurred.

I'm probably still in the process of finding kinks in the new system,
and I'll report them here as I do, but on the whole, the upgrade went
quite well. Thank you all for maintaing this great operating system!

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.38-lila (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Dear reporter,

Thanks for taking the time long ago to submit your upgrade report. I'm
closing these reports now because the Debian releases they were reported
against have reached their end-of-life (some long ago).

Unfortunately it's possible that the report I'm now closing may still
have relevant information for the current release (bullseye). If you
believe that's the case, don't hesitate to reopen the bug, retitle it
and provide further information and it will be seen during the current
freeze period of Debian.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: