Is it safe full-upgrade (buster->bullseye)?

Hi guys!
I have debian buster on my good NSA325v2.
I've a lot of packages installed and configured for my purpose.
Is it safe to run a full-upgrade on this machine? I know the better way would be installDoozan bullseye image from scratch, but I don't want to spend much time on installing and configuring all of the packages I need.
Do you have suggestions?
Thank you in advance.
Kind regards.

Ivan

Ivan,

Yes it is safe to upgrade. But you should do a full rootfs backup before performing a major upgrade such as this dist-upgrade.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi!
It seems I've troubles with esekeyd...

Setting up esekeyd (1.2.7-2) ...
Restarting a multimedia keyboard daemon for Linux: esekeydinvoke-rc.d: initscript esekeyd, action "restart" failed.
dpkg: error processing package esekeyd (--configure):
 installed esekeyd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 esekeyd
E: Sub-process /usr/bin/dpkg returned an error code (1)

Do you have any suggestions?
Thanks you!

Ivan

Ivan,

> Setting up esekeyd (1.2.7-2) ...
> Restarting a multimedia keyboard daemon for Linux:
> esekeydinvoke-rc.d: initscript esekeyd, action
> "restart" failed.
> dpkg: error processing package esekeyd
> (--configure):
> installed esekeyd package post-installation
> script subprocess returned error exit status 1
> Errors were encountered while processing:
> esekeyd
> E: Sub-process /usr/bin/dpkg returned an error
> code (1)
>

esekeyd seems to have some problem during upgrade. Easiest way is removing it. If you had modified the esekeyd config file before, copy it to another folder to back it up. And remove it,

dpkg --purge esekeyd

And run the upgrade again to make sure you don't miss anything.

apt-get dist-upgrade

There is a problem with the key code currently (where KEY_POWER, KEY_RESTART... definition do not work properly), but it is another topic unrelated to the upgrade.

After the upgrade, you can try to reinstall esekeyd again, and we'll discuss what to do with the key codes.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi!
It worked! By removing and reinstalling esekeyd after system upgrade, esekeyd now is correctly configured.
I'm not using KEY_POWER or KEY_RESTART at the moment.
This is my esekeyd.conf:

KEY_133:/usr/bin/logger -s -i "COPY Button pushed"
KEY_116:/sbin/shutdown -h now

Now I have a small problem with minidlna. When I reboot the NAS it fails to start.
It works if

# minidlnad
# service minidlna status
minidlna is running.

How can I fix this last issue after system upgrade?
Thanks a lot.

Ivan

[EDIT]
Problem solved!
The directory for storing the log file was not writable from the minidlna user.
Now it works like a charm.
Thanks for help!



Edited 1 time(s). Last edit at 10/05/2022 05:14PM by krono.