Re: bookworm upgrade report: boring

[ce]

On 6/14/23 04:22, Andrew M.A. Cater wrote:

On Tue, Jun 13, 2023 at 09:08:05PM +0200, CL wrote:

I use Brave as browser and want to set here the dark mode.

But it seems that Brave doesn't remember the setting. After every switch off
/ switch on of the system the browser forget the dark setting.

Not a big issue but a little bit irritating.


Don't know if this is a problem of Bookworm or Brave.

Hi,

Unfortunately, Brave is not packaged by Debian: I'd suggest you go back to
Brendan and Brave software because it is possibly just an issue with the
Brave browser.


Maybe use the flatpak?

Re: bookworm upgrade report: boring

[Nate Bargmann]

* On 2023 14 Jun 03:24 -0500, Vincent Lefevre wrote:
> On 2023-06-13 13:41:23 -0500, Nate Bargmann wrote:
> > I have always chickened out on that option.  Looking at the ucf man page
> > and the description of the three-way merge it looks like the user would
> > have a yes or no option but no edit option.
> 
> One can always run an editor from a shell.

Sure, but one has to carefully note the available file names in case one
is a temp file as the ucf man page discusses.  I don't know enough about
dpkg's handling of such files to know if the correct one will be edited.
Much easier for the package manager/debconf to be extended to handle
this step.

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: bookworm upgrade report: boring

[Joe]

On Tue, 13 Jun 2023 16:32:51 +0200
Vincent Lefevre  wrote:

> On 2023-06-12 18:00:58 +0100, Joe wrote:
> > Yes. I run a fairly customised exim4, and during one upgrade, I
> > think either to or from etch, I kept my configuration, and it broke
> > the exim4 installation. Exim4 was unconfigured, so it wouldn't run,
> > but dpkg-reconfigure couldn't work either. Even a purge wouldn't
> > enable reinstallation, and I had to resort to manually deleting
> > files.  
> 
> What files? If these are files under directories like /etc or
> /usr/local (where the user can put his one things), this is not
> normal, and I suppose that a bug should be reported. Otherwise,
> this is not surprising.
> 

This is many years ago, and I can't recall. Certainly after purging
exim4 and reinstalling, it would not configure. I removed whatever
references to exim4 I could find, and it then installed correctly.

-- 
Joe

Re: bookworm upgrade report: boring

[Vincent Lefevre]

On 2023-06-13 13:41:23 -0500, Nate Bargmann wrote:
> I have always chickened out on that option.  Looking at the ucf man page
> and the description of the three-way merge it looks like the user would
> have a yes or no option but no edit option.

One can always run an editor from a shell.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: bookworm upgrade report: boring

[Andrew M.A. Cater]

On Tue, Jun 13, 2023 at 09:08:05PM +0200, CL wrote:
> Hello,
> 
> after two days usage I found a little issue.
> 
> I use Brave as browser and want to set here the dark mode.
> 
> But it seems that Brave doesn't remember the setting. After every switch off
> / switch on of the system the browser forget the dark setting.
> 
> Not a big issue but a little bit irritating.
> 
> 
> Don't know if this is a problem of Bookworm or Brave.
> 

Hi,

Unfortunately, Brave is not packaged by Debian: I'd suggest you go back to
Brendan and Brave software because it is possibly just an issue with the
Brave browser. I'm not sure there will be enough informed users on this
list who use Brave who can help you with third party software.

With every good wish, as ever,

Andy Cater
> ---
> mit freundlichen Grüßen / Best Regards
> 
> **Christian Lorenz**
> 
> mailto:cl.debian.mail...@t-online.de
> ---
> 
> Am 11.06.23 um 21:05 schrieb CL:
> > Hello,
> > 
> > can confirm the statement of Dan.
> > 
> > Just did an upgrade Bullseye -> Bookworm at two computer.
> > 
> > 1. Lenovo V340-17IWL
> > 
> > XFCE Desktop
> > 
> > used as daily driver
> > 
> > 
> > 2. NUC Kit DC53427HYE
> > 
> > XFCE Desktop
> > 
> > but used as server for a Nextcloud instance
> > 
> > general connetion via ssh
> > 
> > 
> > Both upgrades run smoothly and without any problems.
> > 
> > Only topic was the restart of the Nextcloud. They don't wanted the
> > standard PHP 8.2.
> > Solution was a downgrade to PHP8.0
> > 
> > Until now no problems
> > 
> > 
> 

Re: bookworm upgrade report: boring

[CL]

Hello,

after two days usage I found a little issue.

I use Brave as browser and want to set here the dark mode.

But it seems that Brave doesn't remember the setting. After every switch 
off / switch on of the system the browser forget the dark setting.


Not a big issue but a little bit irritating.


Don't know if this is a problem of Bookworm or Brave.

---
mit freundlichen Grüßen / Best Regards

**Christian Lorenz**

mailto:cl.debian.mail...@t-online.de
---

Am 11.06.23 um 21:05 schrieb CL:

Hello,

can confirm the statement of Dan.

Just did an upgrade Bullseye -> Bookworm at two computer.

1. Lenovo V340-17IWL

XFCE Desktop

used as daily driver


2. NUC Kit DC53427HYE

XFCE Desktop

but used as server for a Nextcloud instance

general connetion via ssh


Both upgrades run smoothly and without any problems.

Only topic was the restart of the Nextcloud. They don't wanted the 
standard PHP 8.2.

Solution was a downgrade to PHP8.0

Until now no problems

Re: bookworm upgrade report: boring

[CL]

Hello,

Docker might be different. I don't use it yet - Not enough knowledge and 
a little bit afraid ;-)


I use a direct installation. Therfore this issue.

But as I already said no problem after the "downgrade".


---
mit freundlichen Grüßen / Best Regards

**Christian Lorenz**

mailto:cl.debian.mail...@t-online.de
---

Am 12.06.23 um 19:52 schrieb Celejar:

On Sun, 11 Jun 2023 21:05:32 +0200
CL  wrote:


...


Only topic was the restart of the Nextcloud. They don't wanted the
standard PHP 8.2.
Solution was a downgrade to PHP8.0


That's unusual - Debian Stable having too *recent* software :|

FWIW, I upgraded my Debian Stable Nextcloud (26.02 via Docker) server
to Bookworm without trouble. Nextcloud is using PHP 8.2.6, but the
Docker containers seem to be providing their own PHP, since I haven't
installed any native PHP packages. This is one reason it can be nice to
run software not in the repositories via Docker.

Re: bookworm upgrade report: boring

[Nate Bargmann]

* On 2023 13 Jun 10:01 -0500, Vincent Lefevre wrote:
> On 2023-06-13 06:41:41 -0500, Nate Bargmann wrote:
> > I've been experimenting with Arch Linux for some time and one thing I
> > like about its pacman package management system is that it has a tool
> > available named 'pacdiff'.  The details are off topic but in a nutshell
> > what it does is identify a locally modified config and the corresponding
> > new config files and can open them in 'vimdiff' giving a nice display of
> > the diff using the vim editor.  Once the editing is complete there is a
> > final step to discard the new config file or replace the current one
> > with it.  I do like that Debian retains the new file with various file
> > name extensions for future reference.
> > 
> > I know that apt allows for viewing a unified diff of the files, but it
> > has been quite some time since I've been presented with that menu that I
> > don't recall if editing based on the diff is an option.  It certainly
> > seems that calling vimdiff in that situation would be quite easy but I
> > realize that not many are comfortable with vim and would want a more
> > universal editor that I might not like.
> 
> This is not apt, but dpkg, which is rather limited:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=32877
> 
> (yes, 1999).

Apparently no developer interest.

> Some packages offer a 3-way merge, which is very useful. I think that
> in this case, the configuration file handling is done via ucf (the
> possibility of a merge is mentioned in its man page).

I have always chickened out on that option.  Looking at the ucf man page
and the description of the three-way merge it looks like the user would
have a yes or no option but no edit option.

I just completed upgrading my Lenovo T-410 laptop to Bookworm and the
only issue was a broken neovim package (I forgot I even had it
installed).  It needed a new runtime package installed as a dependency
so I had to use 'apt --fix-broken install' for the first time ever in
the nearly 24 years of using Debian.  That's an impressive track record.
However, I don't have any system that has done an in-place upgrade
throughout that time.  This laptop was originally installed when Buster
was Testing in late 2018.

My only real concern was the upgrade of Gnu Cash and that appears to
have been flawless (yes, I have off-site backups).

I've already had experience with GNOME 43 from an Arch Linux
installation on another laptop so the changes aren't too massive for me.
I do wonder how things will work with my dual-head desktop as I use an
extension to have separate workspaces on each monitor.  One of these days
I'll feel brave...

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: bookworm upgrade report: boring

[Celejar]

On Tue, 13 Jun 2023 16:46:36 +0200
Vincent Lefevre  wrote:

> On 2023-06-12 13:33:02 -0400, Celejar wrote:
> > Often, but apparently not always. For example, on one of my upgrades,
> > the old sshd_config had:
> > 
> > **
> > # Change to yes to enable challenge-response passwords (beware issues with
> > # some PAM modules and threads)
> > ChallengeResponseAuthentication no
> > **
> > 
> > whereas the new one had:
> > 
> > **
> > # Change to yes to enable challenge-response passwords (beware issues with
> > # some PAM modules and threads)
> > KbdInteractiveAuthentication no
> > **
> 
> In the /usr/share/doc/openssh-server/changelog.Debian.gz file:
> 
> openssh (1:8.7p1-1) unstable; urgency=medium
> [...]
> - ssh(1)/sshd(8): remove references to ChallengeResponseAuthentication
>   in favour of KbdInteractiveAuthentication. The former is what was in
>   SSHv1, the latter is what is in SSHv2 (RFC4256) and they were treated
>   as somewhat but not entirely equivalent. We retain the old name as a
>   deprecated alias so configuration files continue to work as well as a
>   reference in the man page for people looking for it.

Thanks.

> > Is this important?
> 
> If the alias is still there, this is not important. Otherwise, either
> the option could be ignored (so you get the default), possibly with a
> warning, or there could be a fatal error (but you would have noticed
> it); I don't know how sshd behaves in case of an unknown option.
> 
> But in any case, I would recommend to update the config.

That's indeed what I did.

> > What would have happened had I left the old version,
> > as opposed to switching to the new version? Presumably nothing, since
> > I'm using the safer default setting in either case, and I suppose I
> > could have taken the time to track down the change and its
> > implications, but running into these types of situations while
> > upgrading can be disconcerting.
> > 
> > > and reject the package version offered. Less stressful and speeds up
> > > the installation. If necessary, I investigate afterwards.
> > 
> > This is probably the logical thing to do, but I'm always worried that
> > there may be new settings that should be set, and so on.
> 
> I always look at the diffs (I track all the config files I modify),
> and sometimes at the logs too. In general, I do some kind of merge.

This is of course the responsible thing to do - my point was that these
types of situations can make upgrading not quite as boring as the OP's
experience :)

-- 
Celejar

Re: bookworm upgrade report: boring

[Vincent Lefevre]

On 2023-06-13 06:41:41 -0500, Nate Bargmann wrote:
> I've been experimenting with Arch Linux for some time and one thing I
> like about its pacman package management system is that it has a tool
> available named 'pacdiff'.  The details are off topic but in a nutshell
> what it does is identify a locally modified config and the corresponding
> new config files and can open them in 'vimdiff' giving a nice display of
> the diff using the vim editor.  Once the editing is complete there is a
> final step to discard the new config file or replace the current one
> with it.  I do like that Debian retains the new file with various file
> name extensions for future reference.
> 
> I know that apt allows for viewing a unified diff of the files, but it
> has been quite some time since I've been presented with that menu that I
> don't recall if editing based on the diff is an option.  It certainly
> seems that calling vimdiff in that situation would be quite easy but I
> realize that not many are comfortable with vim and would want a more
> universal editor that I might not like.

This is not apt, but dpkg, which is rather limited:

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

(yes, 1999).

Some packages offer a 3-way merge, which is very useful. I think that
in this case, the configuration file handling is done via ucf (the
possibility of a merge is mentioned in its man page).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: bookworm upgrade report: boring

[Vincent Lefevre]

On 2023-06-12 13:33:02 -0400, Celejar wrote:
> Often, but apparently not always. For example, on one of my upgrades,
> the old sshd_config had:
> 
> **
> # Change to yes to enable challenge-response passwords (beware issues with
> # some PAM modules and threads)
> ChallengeResponseAuthentication no
> **
> 
> whereas the new one had:
> 
> **
> # Change to yes to enable challenge-response passwords (beware issues with
> # some PAM modules and threads)
> KbdInteractiveAuthentication no
> **

In the /usr/share/doc/openssh-server/changelog.Debian.gz file:

openssh (1:8.7p1-1) unstable; urgency=medium
[...]
- ssh(1)/sshd(8): remove references to ChallengeResponseAuthentication
  in favour of KbdInteractiveAuthentication. The former is what was in
  SSHv1, the latter is what is in SSHv2 (RFC4256) and they were treated
  as somewhat but not entirely equivalent. We retain the old name as a
  deprecated alias so configuration files continue to work as well as a
  reference in the man page for people looking for it.

> Is this important?

If the alias is still there, this is not important. Otherwise, either
the option could be ignored (so you get the default), possibly with a
warning, or there could be a fatal error (but you would have noticed
it); I don't know how sshd behaves in case of an unknown option.

But in any case, I would recommend to update the config.

> What would have happened had I left the old version,
> as opposed to switching to the new version? Presumably nothing, since
> I'm using the safer default setting in either case, and I suppose I
> could have taken the time to track down the change and its
> implications, but running into these types of situations while
> upgrading can be disconcerting.
> 
> > and reject the package version offered. Less stressful and speeds up
> > the installation. If necessary, I investigate afterwards.
> 
> This is probably the logical thing to do, but I'm always worried that
> there may be new settings that should be set, and so on.

I always look at the diffs (I track all the config files I modify),
and sometimes at the logs too. In general, I do some kind of merge.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: bookworm upgrade report: boring

[Vincent Lefevre]

On 2023-06-12 18:00:58 +0100, Joe wrote:
> Yes. I run a fairly customised exim4, and during one upgrade, I think
> either to or from etch, I kept my configuration, and it broke the exim4
> installation. Exim4 was unconfigured, so it wouldn't run, but
> dpkg-reconfigure couldn't work either. Even a purge wouldn't enable
> reinstallation, and I had to resort to manually deleting files.

What files? If these are files under directories like /etc or
/usr/local (where the user can put his one things), this is not
normal, and I suppose that a bug should be reported. Otherwise,
this is not surprising.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: bookworm upgrade report: boring

[Nate Bargmann]

* On 2023 12 Jun 07:51 -0500, Celejar wrote:
> On Sun, 11 Jun 2023 12:31:31 -0400
> Dan Ritter  wrote:
> > Everything's working. In the end, I didn't make any config
> > changes (left everything as "keep current config").
> 
> This is the part that always stresses me out; I often have changes in
> the default config files that I don't want to lose, but I'm also
> worried about not getting the latest versions of the config files. I
> usually try to accept the new files and manually bring in any important
> changes I've made to the old ones, but this takes time and patience to
> do right, and things can break if not done right :)

I've been experimenting with Arch Linux for some time and one thing I
like about its pacman package management system is that it has a tool
available named 'pacdiff'.  The details are off topic but in a nutshell
what it does is identify a locally modified config and the corresponding
new config files and can open them in 'vimdiff' giving a nice display of
the diff using the vim editor.  Once the editing is complete there is a
final step to discard the new config file or replace the current one
with it.  I do like that Debian retains the new file with various file
name extensions for future reference.

I know that apt allows for viewing a unified diff of the files, but it
has been quite some time since I've been presented with that menu that I
don't recall if editing based on the diff is an option.  It certainly
seems that calling vimdiff in that situation would be quite easy but I
realize that not many are comfortable with vim and would want a more
universal editor that I might not like.

Typically, if it appears that there are major changes to a config file
then I will install the maintainer's version, note it, and edit it for
needed local changes later.  I've been bitten by keeping all of my local
configs in the past so I don't do that any more.

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: bookworm upgrade report: boring

[Celejar]

On Sun, 11 Jun 2023 21:05:32 +0200
CL  wrote:


...

> Only topic was the restart of the Nextcloud. They don't wanted the 
> standard PHP 8.2.
> Solution was a downgrade to PHP8.0

That's unusual - Debian Stable having too *recent* software :|

FWIW, I upgraded my Debian Stable Nextcloud (26.02 via Docker) server
to Bookworm without trouble. Nextcloud is using PHP 8.2.6, but the
Docker containers seem to be providing their own PHP, since I haven't
installed any native PHP packages. This is one reason it can be nice to
run software not in the repositories via Docker.

-- 
Celejar

Re: bookworm upgrade report: boring

[Celejar]

On Mon, 12 Jun 2023 18:02:13 +0100
Brian  wrote:

> On Mon 12 Jun 2023 at 08:50:54 -0400, Celejar wrote:
> 
> > On Sun, 11 Jun 2023 12:31:31 -0400
> > Dan Ritter  wrote:
> > 
> > > 
> > > The machine I am typing on has been upgraded from bullseye to
> > > bookworm. TL;DR: boring, which is good.
> > 
> > ...
> > 
> > > I read the release notes.
> > > 
> > > Changed sources.list entries.
> > > 
> > > Ran apt update.
> > > 
> > > I ran apt upgrade --without-new-pkgs before apt full-upgrade.
> > > Then I rebooted.
> > > 
> > > Everything's working. In the end, I didn't make any config
> > > changes (left everything as "keep current config").
> > 
> > This is the part that always stresses me out; I often have changes in
> > the default config files that I don't want to lose, but I'm also
> > worried about not getting the latest versions of the config files. I
> > usually try to accept the new files and manually bring in any important
> > changes I've made to the old ones, but this takes time and patience to
> > do right, and things can break if not done right :)
> 
> I have taken to assuming that detected changes are due to my efforts

Often, but apparently not always. For example, on one of my upgrades,
the old sshd_config had:

**
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no
**

whereas the new one had:

**
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
KbdInteractiveAuthentication no
**

Is this important? What would have happened had I left the old version,
as opposed to switching to the new version? Presumably nothing, since
I'm using the safer default setting in either case, and I suppose I
could have taken the time to track down the change and its
implications, but running into these types of situations while
upgrading can be disconcerting.

> and reject the package version offered. Less stressful and speeds up
> the installation. If necessary, I investigate afterwards.

This is probably the logical thing to do, but I'm always worried that
there may be new settings that should be set, and so on.

-- 
Celejar

Re: bookworm upgrade report: boring

[Brian]

On Mon 12 Jun 2023 at 08:50:54 -0400, Celejar wrote:

> On Sun, 11 Jun 2023 12:31:31 -0400
> Dan Ritter  wrote:
> 
> > 
> > The machine I am typing on has been upgraded from bullseye to
> > bookworm. TL;DR: boring, which is good.
> 
> ...
> 
> > I read the release notes.
> > 
> > Changed sources.list entries.
> > 
> > Ran apt update.
> > 
> > I ran apt upgrade --without-new-pkgs before apt full-upgrade.
> > Then I rebooted.
> > 
> > Everything's working. In the end, I didn't make any config
> > changes (left everything as "keep current config").
> 
> This is the part that always stresses me out; I often have changes in
> the default config files that I don't want to lose, but I'm also
> worried about not getting the latest versions of the config files. I
> usually try to accept the new files and manually bring in any important
> changes I've made to the old ones, but this takes time and patience to
> do right, and things can break if not done right :)

I have taken to assuming that detected changes are due to my efforts
and reject the package version offered. Less stressful and speeds up
the installation. If necessary, I investigate afterwards.

-- 
Brian.

Re: bookworm upgrade report: boring

[Joe]

On Mon, 12 Jun 2023 08:50:54 -0400
Celejar  wrote:

> On Sun, 11 Jun 2023 12:31:31 -0400
> Dan Ritter  wrote:
> 
> > 
> > The machine I am typing on has been upgraded from bullseye to
> > bookworm. TL;DR: boring, which is good.  
> 
> ...
> 
> > I read the release notes.
> > 
> > Changed sources.list entries.
> > 
> > Ran apt update.
> > 
> > I ran apt upgrade --without-new-pkgs before apt full-upgrade.
> > Then I rebooted.
> > 
> > Everything's working. In the end, I didn't make any config
> > changes (left everything as "keep current config").  
> 
> This is the part that always stresses me out; I often have changes in
> the default config files that I don't want to lose, but I'm also
> worried about not getting the latest versions of the config files. I
> usually try to accept the new files and manually bring in any
> important changes I've made to the old ones, but this takes time and
> patience to do right, and things can break if not done right :)
> 
>
Yes. I run a fairly customised exim4, and during one upgrade, I think
either to or from etch, I kept my configuration, and it broke the exim4
installation. Exim4 was unconfigured, so it wouldn't run, but
dpkg-reconfigure couldn't work either. Even a purge wouldn't enable
reinstallation, and I had to resort to manually deleting files.

I've had more and more trouble with each version, so this time I'll be
fresh installing. I suppose it's less trouble with a workstation.

-- 
Joe

Re: bookworm upgrade report: boring

[Charles Curley]

On Mon, 12 Jun 2023 08:50:54 -0400
Celejar  wrote:

> This is the part that always stresses me out; I often have changes in
> the default config files that I don't want to lose, but I'm also
> worried about not getting the latest versions of the config files. I
> usually try to accept the new files and manually bring in any
> important changes I've made to the old ones, but this takes time and
> patience to do right, and things can break if not done right :)

Right.

I usually do upgrades with at least two terminals open on the subject
machine. One I use for the actual upgrade process. Another has Emacs
open and ready to use, and a third has a shell for general use.

During the upgrade, I select which configuration file to use, my edited
version or the maintainer's. I then use Emacs' ediff mode to compare
the two and update the config file. I have Emacs configured to preserve
the original file as a backup (foo~ for file foo). I do this as the
upgrade proceeds, which lets me concentrate on one file at a time.

It is usually fairly straightforward. Usually.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: bookworm upgrade report: boring

[Celejar]

On Sun, 11 Jun 2023 12:31:31 -0400
Dan Ritter  wrote:

> 
> The machine I am typing on has been upgraded from bullseye to
> bookworm. TL;DR: boring, which is good.

...

> I read the release notes.
> 
> Changed sources.list entries.
> 
> Ran apt update.
> 
> I ran apt upgrade --without-new-pkgs before apt full-upgrade.
> Then I rebooted.
> 
> Everything's working. In the end, I didn't make any config
> changes (left everything as "keep current config").

This is the part that always stresses me out; I often have changes in
the default config files that I don't want to lose, but I'm also
worried about not getting the latest versions of the config files. I
usually try to accept the new files and manually bring in any important
changes I've made to the old ones, but this takes time and patience to
do right, and things can break if not done right :)

So far I've upgraded two Stable systems:

* A bare metal install, with a somewhat robust set of packages and
configuration. I mostly kept the the current configs like Dan did.

* A more minimal cloud VM, which pretty much just runs Nextloud through
Docker. I accepted the new sshd_config, but I manually switched
PermitRootLogin back on. (Pretty much everything I do on this machine
is done is root, so I don't bother logging in as a user and switching
to root.)

Both upgrades went quite smoothly.

-- 
Celejar

Re: bookworm upgrade report: boring

[CL]

Hello,

can confirm the statement of Dan.

Just did an upgrade Bullseye -> Bookworm at two computer.

1. Lenovo V340-17IWL

XFCE Desktop

used as daily driver


2. NUC Kit DC53427HYE

XFCE Desktop

but used as server for a Nextcloud instance

general connetion via ssh


Both upgrades run smoothly and without any problems.

Only topic was the restart of the Nextcloud. They don't wanted the 
standard PHP 8.2.

Solution was a downgrade to PHP8.0

Until now no problems


--
---
mit freundlichen Grüßen / Best Regards

**Christian Lorenz**

mailto:cl.debian.mail...@t-online.de
---

Am 11.06.23 um 18:31 schrieb Dan Ritter:


The machine I am typing on has been upgraded from bullseye to
bookworm. TL;DR: boring, which is good.

Hardware:
AMD 5 3600 (6c12t)
32 GB RAM
one NVMe SSD, ext4
MSI MS-7C95 B550M PRO-VDH WIFI motherboard

Peripherals:
Blue Yeti microphone
X-Bows KNIGHT keyboard
Logitech C920 webcam
Logitech Unifying Receiver (trackball, mouse)
Apple USB-C 3.5mm headphone adapter
Apple MagicPad

Software choices:
XFCE desktop
X11
chrony (NTP)
bluetoothd

I read the release notes.

Changed sources.list entries.

Ran apt update.

I ran apt upgrade --without-new-pkgs before apt full-upgrade.
Then I rebooted.

Everything's working. In the end, I didn't make any config
changes (left everything as "keep current config").

-dsr-

bookworm upgrade report: boring

[Dan Ritter]

The machine I am typing on has been upgraded from bullseye to
bookworm. TL;DR: boring, which is good.

Hardware:
AMD 5 3600 (6c12t)
32 GB RAM
one NVMe SSD, ext4
MSI MS-7C95 B550M PRO-VDH WIFI motherboard

Peripherals:
Blue Yeti microphone
X-Bows KNIGHT keyboard
Logitech C920 webcam
Logitech Unifying Receiver (trackball, mouse)
Apple USB-C 3.5mm headphone adapter
Apple MagicPad

Software choices:
XFCE desktop
X11
chrony (NTP)
bluetoothd

I read the release notes.

Changed sources.list entries.

Ran apt update.

I ran apt upgrade --without-new-pkgs before apt full-upgrade.
Then I rebooted.

Everything's working. In the end, I didn't make any config
changes (left everything as "keep current config").

-dsr-