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

Re: buster and the release notes



Paul Gevers wrote:
> As we're getting closer to the buster release, I'd like to discuss some
> open items in the release notes. There are currently 12 items in the
> condition="fixme" state, of which 5 I need help with right now (I'll
> remove some of the other fixme's as they are either double or not
> "fixable").
> 
> 1) in issues.dbk there is a choice to be made about if there are actions
> to do after running $(apt full-upgrade) before the next reboot. I don't
> know of any issues, but I don't dare to choose yet without feedback.

My own test runs haven't needed anything special beyond re-customising
config-files.  There might be a crossreference for people switching
from legacy interface names, but I'd recommend finishing that switch
*before* the dist-upgrade.
 
> 2) in issues.dbk there is a list of removed packages. However, the
> instructions aren't clear to me of how to create such a list. The
> alternative lists too many packages that also weren't in the stretch, so
> that makes spotting the right ones rather tedious. And how to spot the
> "known and noteworthy" ones? Does anybody know "the proper way"?

Looking at that https://udd.debian.org/bapase.cgi?t=testing list and
sorting it by popcon offers a starting point.  Skipping the libraries,
virtual packages, and dummy transitional packages, the top few hits
are
 mysql-5.7 - wasn't in Stretch
 phpmyadmin - ?
 flashplugin-nonfree - long dead
 checkinstall - ?
 mongodb - ?
 mysql-connector-python - ?
 firefox - deprecated in favour of firefox-esr
 kdepim4 -?
 pyside - ?
 mysql-utilities - ?
 ssmtp - ?
 kernel-package - deprecated in favour of "make deb-pkg"?
 amarok - ?
 ...
 
> 3) in upgrading.dbk there is a section about aptitude. It feels really
> outdated as since 2010 we recommend updating with apt(-get). I never
> used aptitude, is this section still relevant and up-to-date?

I do my test dist-upgrades under aptitude; for Buster they've been
utterly uneventful, so on the one hand I can vouch for it being a
working option but on the other for it not needing special coverage.

> 4) in upgrading.dbk there was a note saying "need to be reviewed with
> information from
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571255"; in the section
> about kernel upgrades. That bug was about udev issues in squeeze. Does
> that bug still use interesting knowledge to improve the notes of that
> section?

What *is* the minimum Debian kernel required for the Testing versions
of udev/systemd?  Can we assume that if it isn't obvious from looking
in the udev/systemd changelogs etc, that they're saying it isn't
something we need to worry about?
 
> 5) in whats-new.dbk there isn't much exiting for buster. Don't we have
> nice new things?

The biggest recent change in Debian is probably the shift to Salsa,
but that's not something that users will notice.  I'm mainly looking
forward to Bash 5 and integrated apt-transport-https, but shouldn't
more normal users with less antiquated graphics hardware be expecting
benefits of some sort from Wayland?

There's no mention in the release-notes of usrmerge, which isn't a
problem unless we want to give people advance notice that it might be
coming in Bullseye.
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package


Reply to: