This is about upgrading from Debian 10 Buster to Debian 12 Bookworm via Debian 11 Bullseye (release notes) on a 64 bit (amd64) computer. 32 bit
Information about upgrading to a previous version can still be present

With a full-upgrade a new version of Debian is installed over the old version. This is very convenient since normally all applications work also in the new version. No new installation and configuring needs to be done

Debian information startpage on upgrading to the newest version of Debian on an AMD64 system can be found at Chapter 4. Upgrades from Debian (the current stable version). It is highly recommended to read this before upgrading

Also read the FAQ. Especially Chapter 9 - Keeping your Debian system up-to-date

Upgrading Debian from an archived version to the stable version

It might be usfull to install and use sosreport
Do as user: mkdir $HOME/logs If it does not exist
Do as root: mkdir $HOME/logs If it does not exist

• Make sure it /root/.bashrc contains

HISTCONTROL=ignoreboth,ignoredups,ignorespace,erasedups # ignoreboth = ignoredups,ignorespace
HISTSIZE=1000000
HISTFILESIZE=20000000
shopt -s histappend

• Make sure you do source /root/.bashrc when you added and / or changed something
  
• In the termial window do: Edit | Profile | Preferences | Scrolling | unlimited | OK or set to 1000000
• You can stop the scrolling with CTRL-S and continue with CTRL-Q
• Keep an eye on the output since important errors and warnings might occur wich need immediate action

• With aptitude check if lsb-release is installed and if not install it
• echo $(lsb_release --codename | cut -f 2; cat /etc/debian_version)

If there are multiple monitors on you computer disconnect all of them but the main monitor
For a notebook that means use the screen of the notebook itself without any other screens connected to the notebook

Debian 9 Stretch
For 32-bit PC support:
The 32-bit PC support (known as the Debian architecture i386) now no longer covers a plain i586 processor. The new baseline is the i686, although some i586 processors (e.g. the “AMD Geode“ (not after Bullseye)) will remain supported

See What can be removed from Debian

If Wicd is installed as network manager then replace it with network-manager since in Debian 11 Bullseye wicd is deprecated, the packages are not available any more. If omitting this replacement it can get hard to get the network working manually again

• Purge the packages in $HOME/logs/dpkg.selections.txt marked with “deinstall”, unless you want to keep the data / configuration files, with one of:
  • this script
  • manually with aptitude
  • the aptitude --purge-unused command. Warning: it can cause data loss Use it only when you know what you are doing and, or want to take a risk

With aptitude --purge-unused autoclean uninstall and purge all packages you do not need anymore. If necessary manually remove directory's and files aptitude was not able to remove but which can be removed

Clean up the apt cache ( /var/cache/apt/archives ):

• apt-get autoclean removes package files that can no longer be downloaded, and are largely useless
• apt-get autoremove remove packages that were automatically installed to satisfy dependencies for other packages and are now no longer needed

Use aptitude to install and update all packages. Update as much as you can before starting the upgrade process. Maybe you need to do in aptitude u U g g several times

Make sure mutt and dma or an other MTA like exim4 of your choice are installed by checking in aptitude

• If not installed, install, with aptitude, linux-image-amd64
• Check in aptitude and with uname -r
• Maybe you have to install a new kernel within aptitude or run aptitude install linux-image-theVersionYouWant
• Maybe you have to reboot, check again with uname -r until the desired kernel is active. At that point old kernels can be purged with aptitude
  

Also see the Debian page on HowToUpgradeKernel

We experienced that packages are unintentionally uninstalled during the upgrade. To be able to check the differences before and after the upgrade run both commands and save the list for after the upgrade

• dpkg --get-selections > $HOME/logs/dpkg.selections-bullseye.pre.txt (this is a long simple list). Already preformed above
• dpkg-query -l > $HOME/logs/dpkg.query-bullseye.pre.txt (this is a long list)

Create a backup or make an image off the whole drive. You can use Clonzilla for this

Run dpkg --get-selections > $HOME/logs/dpkg.selections.txt\\ Run dpkg --get-selections “*” > $HOME/logs/dpkg.selections.txt <del>(the quotes are important. They might be needed to be replaced after any sort of copy and pasting into a terminal)
Individual directories to backup:

• /etc so you can retrieve settings after a full-upgrade to the next version of Debian
• /home
• /root
• /usr/share/themes (Custom themes and notification appearances)
• /usr/share/twinkle/providers.csv
• /var/backups
• /var/lib/apt/extended_states
• /var/lib/aptitude/pkgstates
• /var/lib/dpkg
• /var/local
• /var/log
• /var/mail
• /var/spool
• /var/www

Check if there is enough disk space on the installation partition(s) with df -h | sort . Have at least 5 GB available in /, /usr and /var together if X windows is used, with a window manager. If X windows is not installed 1GB is sufficient. All this depending on the amount of disk space additionally installed pacakges require
If the disk space is not sufficient the partition sizes might be rearranged. For this a tool like Parted Magic can be used

• For this process do not use aptitude or an other package manager unless needed to fix problems
  • We use apt. apt-get worked fine until and including the upgrade to Buster. Thereafter a lot of packages were kept back and the issue arose
• To avoid issues do not use a terminal in a window manager. Use a real terminal instead: CTRL-ALT-F1 (F1-F6) are terminals. ALT-F7 is X Windows

• Messages can also be found in the local e-mail. mutt can be used to view them
• It is advisable to use tee so the output of the commands to follow is shown on the screen and saved in a file. See the textprocessing page for an example
• Also script -t 2> $HOME/logs/upgrade-bullseyestep.time -a $HOME/logs/upgrade-bullseyestep.script can be used at the same time. Exit when ready with exit at the prompt

If you encounter “dpkg: error: dpkg status database is locked by another process”

First have a look at the Debian “Q: What can be done when the dpkg lock is held?” page

Then check for processes which might have a lock on the database. Programs who can lock the database are

• apt
• apt-get
• aptitude
• dpkg

You can use top and or ps -e | grep dpkg; ps -e | grep apt; ps -e | grep aptitude for this
If one or more of these programs are running stop them and check again. If none of these programs is running check if one or more of

• /var/lib/dpkg/lock
• /run/lock/aptitude

exists.
If so:

• Reboot
• Check again
• If the lock files are gone continue. Otherwise
• Delete the lock file(s) and try again to start apt update (see next step)
  

Do as root:

1. Check if the system is up to date
   1. Show the current Debian version name: lsb_release --codename
   2. vi /etc/apt/sources.list
      1. Check if the current version name is in the sources.list file. If not, replace the version name with the current Debian version name (if not already there as can be expected)
      2. Save sources.list
   3. apt update | tee $HOME/logs/apt.update-bullseye.pre.log
   4. apt upgrade | tee $HOME/logs/apt.upgrade-bullseye.pre.log
   5. apt full-upgrade | tee $HOME/logs/apt.full-upgrade-bullseye.pre.log
2. Clean up leftover configuration files: find /etc -name '*.dpkg-*' -o -name '*.ucf-*' -o -name '*.merge-error'
   1. Delete with find /etc -name '*.dpkg-*' -delete -o -name '*.ucf-*' -delete -o -name '*.merge-error' -delete
3. Do the upgrade: vi /etc/apt/sources.list and replace the old version name with the new one with: :%s/oldversionname/newversionname/g . Close vi with :x. Or use sed: sed --in-place 's/stretch/buster/g' /etc/apt/sources.list
   1. The format of sources.list has changed from buster to bullseye
   2. See: sources.list
   3. Example: deb http://deb.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
      • For bullseye omit non-free-firmware
      • contrib packages contain DFSG-compliant software, but have dependencies not in main (possibly packaged for Debian in non-free)
      • non-free contains software that does not comply with the DFSG
4. Do the same for files in /etc/apt/sources.list.d/
5. apt update | tee $HOME/logs/apt.update-bullseye.post.log
   • Error

     E: The repository 'https://security.debian.org bullseye/updates Release' does not have a release file.

     • Solution: See above, omit non-free-firmware
   • Error

     The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information.
     Reading package lists... Done
     E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi'
     E: Sub-process returned an error code

     • We could not find the “verbose log for more information”. It was not in the apt history.log. When we ran apt update a second time no error was mentioned
6. apt upgrade | tee $HOME/logs/apt.upgrade-bullseye.post.log
   1. You have to answer some questions on the way so keep an eye on the screen
   2. apt-listchanges: comments on the changes can be found in the e-mail of the root account
   3. There can be a lot of held back packages. This is not always the case. The cause is mostly using apt-get in stead of apt
      • First run apt full-upgrade at the next step, step 7. If that does not resolve the issue
        • Goto the packages kept back section to try to resolve this issue. Continue here when done
        • Some packages will be uninstalled and maybe a fresh copy will be installed. All data related to those packages will probably get lost
        • It might be the case that config files are automatically overwritten by new ones without asking what to do with the old ones
   4. Err:101_ Hit CTRL-S at once and fix the issue before continuing. Hash Sum mismatch. A package is not correctly downloaded. libxt6 is an example package name.

      Get:101 http://mirror.nl.leaseweb.net/debian buster/main amd64 libxt6 amd64 1:1.1.5-1+b3 [190 kB]                                                                                            
      Err:101 http://mirror.nl.leaseweb.net/debian buster/main amd64 libxt6 amd64 1:1.1.5-1+b3                                                                                                     
      Hash Sum mismatch
      Hashes of expected file:
       - SHA256:5c474aa7c6bef9c8b0a4cf5cb9102c29ba8c5b2b19a59269ab6e2f0a47a5ec59
       - MD5Sum:797d80062fd67132abba078ebe861ca5 [weak]
       - Filesize:189960 [weak]
      Hashes of received file:
       - SHA256:bfaec7b61478dad07d1f58e2be3d10efbbf37eca41d2bcd50c3c06b3da2a42cf
       - MD5Sum:194c669c4b22e5f15647f34274c696ca [weak]
       - Filesize:19927 [weak]
      Last modification reported: Sun, 17 Mar 2019 09:13:44 +0000

      • You can continue with CTRL-Q and fix the issue when apt upgrade is finished by running apt upgrade --fix-missing or fix the issue now, manually, by executing the following steps
      • apt-cache show libxt6
      • If it exists, it should since it is intalled, search for it with find / -name libxt6*.deb.FAILED 2> /dev/null and to be sure also with find / -name libxt6* 2> /dev/null
      • cd /tmp
      • aptitude download libxt6
      • sha256sum libxt6_1%3a1.1.5-1+b3_amd64.deb
        • Compare the checksum with the checksum for the expected file in the Err:101 error message
        • If they are the same
          • cp /tmp/libxt6_1%3a1.1.5-1+b3_amd64.deb /var/cache/apt/archives
          • rm -f /var/cache/apt/archives/partial/libxt6_1%3a1.1.5-1+b3_amd64.deb.FAILED
      • Continue CTRL-Q
      • apt upgrade --fix-missing needs to be ran since apt upgrade did not continue because of the “Err:101” error
7. apt full-upgrade | tee $HOME/logs/apt.full-upgrade-bullseye.post.log
   1. You have to answer some questions on the way so keep an eye on the screen
   2. If you get “Locale: Cannot Set LC_ALL to default locale: No such file or directory” ignore it. Setting LC_ALL will destroy the other locale settings
8. Check the log by scrolling back with <Shift> + <Page up> and / or <Shift> + <Up> and take action or note the actions to be taken if applicable. Not applicable if ran in the ALT-CTRL-F3 terminal. In that case check the logfiles.
9. apt autoremove
10. apt autoclean
11. Check in the release-notes for actions to take before reboot. For 32 bit computers
12. If script is started stop it with exit in the terminal script is started
13. reboot
    • When there are more than one Linux installation on the PC (dual boot) start the installation from which grub is started. In that installation do as root update-grub. Now the new kernel, if any, of the installation you are updating will be used when you boot in the installation you are updating. This has only to be done once. If you do not do this the old kernel will be used when you boot the PC. Also you might boot from a different disk which may lead to problems in the future
14. Start aptitude and check the 'Obsolete and manually installed' section. Purge all packages which are not needed any more
15. apt update
16. apt upgrade
17. apt full-upgrade
18. Check the log by scrolling back with <Shift> + <Page up> and / or <Shift> + <Up> and take action of note the actions to be taken if applicable
19. Repeat the steps 13, 14, 15, 16, 17 until there are no more updates
20. apt autoremove
21. apt autoclean
22. Check with aptitude if there are still packages left to upgrade. In aptitude do u U g g. Keep checking until there are no more updates
23. cat /etc/issue; cat /etc/debian_version; lsb_release --all

This worked also on a Raspberry Pi 2B when upgrading from Wheezy to Jessie. It can take about 5 hours on a Raspberry Pi 2B mainly depending on the speed of the uSDcard or harddrive

• Check the Debian version echo $(lsb_release --codename | cut -f 2; cat /etc/debian_version)
• Check the local e-mail for apt-listchanges output of any comments regarding the new Debian version
• Check in /etc/default/grub if you need to activate the os prober, via the GRUB_DISABLE_OS_PROBER setting.
• Check the /etc/ntp.conf file if you have set other timeservers (not on Bullseye and newer)
• With aptitude check Obsolete and Locally Created Pacakges for any packages that can be deleted
• Run
  • dpkg --get-selections > $HOME/logs/dpkg.selections-bullseye.post.txt (this is a long simple list)
  • dpkg-query -l > $HOME/logs/dpkg.query-bullseye.post.txt (this is a long list)
  • Clean up pacakges marked deinstall
  • Take action on all issues mentioned in the terminal output of the apt commmands
    • grep dpkg $HOME/logs/apt.upgrade-bullseye.post.log and grep dpkg $HOME/logs/apt.full-upgrade-bullseye.post.log and check for uninstalled packages and other issues
      • Compare the list with the list made before the upgrade. Especialy check for packages that are uninstalled but should not be. Midnight Commander (mc) is a handy tool
    • grep 'Installing new version of' $HOME/logs/apt.upgrade-bullseye.post.log and check if any action is needed
    • grep 'configuration error' $HOME/logs/apt.upgrade-bullseye.post.log and check if any action is needed
    • grep 'not starting it' $HOME/logs/apt.upgrade-bullseye.post.log and check if any action is needed
    • grep 'Possible missing' $HOME/logs/apt.upgrade-bullseye.post.log and check if any action is needed. This is probably mostly about missing firmware
• Check the settings of
  • Start | Settings | Notifications
• Check if Clipman is still in the panel and if not restore it. If you can not see the Debian 10 Buster section
• Check the logrotate settings in /etc/logrotate.conf and in /etc/logrotate.d
• in What can be removed from Debian if previous uninstalled packages are reinstalled and need to be uninstalled again
• Check if any settings have to be changed for GTK2 and GTK3 with the gsettings command
• Check if the items in the /etc/xdg/autostart folder are still valid, needed. If not, remove them (or move them to a save place just in case)

The update kernel is not invoked on reboot. The old kernel is still active. Seen by bullseye and bookworm

• orage
• vlc

See also the packages kept back section
Try:

• 4.5.1. Dist-upgrade fails with “Could not perform immediate configuration”
• 4.5.3. Conflicts or Pre-Depends loops

# xscreensaver-command -restart
xscreensaver-command: warning: $DISPLAY is not set: defaulting to ":0.0".
Invalid MIT-MAGIC-COOKIE-1 keyxscreensaver-command: can't open display :0.0

Solution:

# ps -e | grep xscreensaver
 9589 ?        00:00:01 xscreensaver
# kill 9589
# ps -e | grep xlockmore
 9999 ?        00:00:01 xlockmore
# kill 9999

• Look in journalctl -xb for errors (in red)
• Reboot
• Make sure the new kernel is installed and running with uname -r. Remove the older kernel(s) with aptitude

This

/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_dmc_ver1_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_39.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver9_29.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915

is also what you can get when you run update-initramfs -u (-u stands for update)
The same can happen with amdgpu in stead of i915

• Run as root
  • aptitude install apt-file
  • apt-file update
  • for amdgpu:

grep amdgpu /root/logs/apt.full-upgrade-bookworm.post.log > /root/logs/firmware.txt
for i in $(cat /root/logs/firmware.txt | cut -d '/' -f 5 | cut -d '_' -f 1,2 | grep -v module | sort --unique); do echo i: $i; apt-file search $i; done

• for i915:

grep i915 /root/logs/apt.full-upgrade-bookworm.post.log > /root/logs/firmware.txt
for i in $(cat /root/logs/firmware.txt | cut -d '/' -f 5 | cut -d '_' -f 1,2 | grep -v module | sort --unique); do echo i: $i; apt-file search $i; done

• If there is a package found, install it with aptitude
• For other not found drivers goto the Intel i915 page and download the binfiles mentioned in the warnings above
• Copy the binfiles to /lib/firmware/i915/
• Run updatedb if it is installed on you computer. Otherwise you can skip this
• update-initramfs -uv (-u stands for update, -v for verbose) and check if the “W: Possible missing firmware” warnings are gone

Reference: Possible missing frmware lib firmware i915

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "nl_NL.UTF-8",
LC_MONETARY = "nl_NL.UTF-8",
LC_CTYPE = "nl_NL.UTF-8",
LC_RESPONSE = "en_US.UTF-8",
LC_COLLATE = "nl_NL.UTF-8",
LC_ADDRESS = "nl_NL.UTF-8",
LC_TELEPHONE = "nl_NL.UTF-8",
LC_MESSAGES = "en_US.UTF-8",
LC_MEASUREMENT = "nl_NL.UTF-8",
LC_IDENTIFICATION = "nl_NL.UTF-8",
LC_NUMERIC = "nl_NL.UTF-8",
LC_PAPER = "nl_NL.UTF-8",
LANG = "en_US.UTF-8"
  are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_ALL to default locale: No such file or directory

These warnings must be ignorded. Read Locale on the Debian Wiki. Setting the LC_ALL locale will unset all the others. As per Debian wiki - “Using LC_ALL is strongly discouraged as it overrides everything use it only when testing and never set it in a startup file”. See also for reference fix error locale cannot set lc_all to default locale no such file or directory

Restore in /etc/nanorc :

## Use the blank line below the titlebar as extra editing space.
set morespace
set mouse
set smarthome
set tabsize 2

Keepnote has been removed. The contents can be found in the directory you placed them in. Search for node.xml
A replacement is CherryTree which is in the repository. Keepnote data can easily being imported

If mutt has the error “could not create temporary file” check the ownership and permissions of /var/tmp

About apt, apt-get and aptitude¹⁾:

• apt update
• apt-get update
• aptitude update is equivalent to “apt-get update”
• apt upgrade will automatically install but not remove packages
• apt-get upgrade will not change what is installed. It changes only versions
• aptitude safe-upgrade
• apt full-upgrade will install or remove packages as necessary to complete the upgrade
• apt-get dist-upgrade does the same as apt full-upgrade
• aptitude full-upgrade

About the upgrade:
When running apt-get upgrade we encountered a lot of held back packages. Using apt upgrade reduced the number of kept back packages for bookworm from 322 to 17

After a reboot and checking with aptitude the held back packages were gone the upgrade was continued with aptitude. After aptitude was finished we ran apt-get upgrade and apt-get dist-upgrade. Neither of which yielded additional installs of any kind
Remarks:

• Some packages will be uninstalled and maybe a fresh copy will be installed. All data related to those packages will probably get lost
• It might be the case that config files are automatically overwritten by new ones without
• It might be the case that
  • several reboots resolves the kept back packages issue
  • waiting for a while can also resolve the issue
  • there are phased updates

Possible solutions:

• Adding --dry-run can be used for testing
• Run apt upgrade | tee $HOME/logs/packages.txt
  • Save the package list of the packages being kept back in $HOME/logs/packages.txt to $HOME/logs/keptback.txt

1. Run xargs apt upgrade < $HOME/logs/keptback.txt
2. Run xargs apt-get --with-new-pkgs upgrade < $HOME/logs/keptback.txt (packages are marked as not manually installed)
3. Run xargs apt install < $HOME/logs/keptback.txt (packages are marked as manually installed)
4. Run the previous ones with the -o APT::Get::Always-Include-Phased-Updates=true upgrade added
5. Run, as last resort, apt full-upgrade

If still no success, enable both the lines for the current and the new version in /etc/source.list and repeat the steps above

We encountered a partial update to Debian 11 Bullseye on a system that was not updated for a few years
When we ran the update in aptitude by doing uUgg kernel 5 was installed and thereby an upgrade to Debian 11 Bullseye initiated. Due to dependency issues the upgrade could not be finalized via aptitude. Also it was not possible to go back to Debian 10 Buster with aptitude.

Solution: T.b.d.
First step: Check /etc/apt/sources.list and /etc/apt/sources.list.d/*

• No login screen, you have to login into a terminal. startx crases when started by user. Works fine when started by root.
• Firefox 74 does not connect to websites. w3m works fine. Solution: Disable uMatrix, enable uBlockOrigin
• The second, floating, panel whith just the sensor data does not show all data as it did before the dist-upgrade. Text below top of the handles is not shown. Initially the panel was turned 90°. Solution: Put the panel in Deskbar mode
• dpkg: error processing archive /tmp/apt-dpkg-install-5RCIWX/277-libwebsocket-api-java_1.1-1_all.deb (--unpack): trying to overwrite '/usr/share/maven-repo/javax/websocket/javax.websocket-api/1.0/javax.websocket-api-1.0.pom', which is also in package libservlet3.1-java 8.5.50-0+deb9u1
• Open pip file /run/rpc_pipefs/nfs/blocklayout failed . If you do not need it uninstall nfs
  • 3 files. T.b.d.
• ACPI Error: AE_NOT_FOUND, While resloving a named reference package element . You can ignore this. It is a Microsoft generated issue. It might be solved by this guide. Some more
• Radeon driver firmware not found. Solution: aptitude install firmware-amd-graphics
• Errors were encountered while processing:

/tmp/apt-dpkg-install-5RCIWX/244-libel-api-java_3.0.0-2_all.deb
/tmp/apt-dpkg-install-5RCIWX/263-libjsp-api-java_2.3.4-2_all.deb
/tmp/apt-dpkg-install-5RCIWX/277-libwebsocket-api-java_1.1-1_all.deb

• Errors when installing

shim-signed-common
shim-signed:amd64

* Package with limited security support
  * adns - Advanced, easy to use, asynchronous-capable DNS client library and utilities
  * binutils - A GNU collection 19 of binary tools, including an assembler and a linker
  * qtwebkit-opensource-src
    * libqt5webkit5 - recommended by phantomje wich is recommended by youtube-dl
      * Uninstall phantomjs
      * Uninstall libqt5webkit5 
  * webkitgtk
    * libjavascriptcoregtk-1.0-0 - Dependency of libwebkitgtk-1.0-0. Uninstall it
    * libwebkitgtk-1.0-0 - No reason why it is installed, uninstall.

• Ignoring file 50-unattended-upgrades-ucftmp in derectory /etc/apt/apt.conf.d as it has an invalid filename extension
• No file name for libservlet3.1-java:amd64
• grub-install warning can not set efi variable Boot=0000 . Failed grub-install --target=x86_64-efi --force-extra-removable

GNU assembler, linker and binary utilities

Limited security support for one or more packages
Unfortunately, it has been necessary to limit security support for some packages.
The following packages found on this system are affected by this:
* Source:binutils                           
Details: Only suitable for trusted content;
  see https://lists.debian.org/msgid-search/87lfqsomtg.fsf@mid.deneb.enyo.de
 Affected binary packages:
 - binutils (installed version: 2.31.1-16)
 - binutils-common:amd64 (installed version: 2.31.1-16)
 - binutils-x86-64-linux-gnu (installed version: 2.31.1-16)
 - libbinutils:amd64 (installed version: 2.31.1-16)

Keep this package

After the reboot after apt-get dist-upgrade the windowmanager does not start. The mouse pointer appears a brief moment and disappears again. The windowsmanager seems to be in a loop. Also when in aptitude we found that a lot of packages were not prpperly installed or were not deleted. Do

• Goto a terminal window with CTRL-ALT-F1
• Login as root or as user and become root
• Again make sure there is enough disk space free
  • /boot should be at least 1 GB if it has its own partition (no exact check done) or part of /
• start aptitude and do u U g g
• Do b find broken packages. There will be no reaction if none are found
  • _ for pacakges that are not needed and can be removed
  • L for packages that are needed and thus need to be reinstalled
  • g g to execute
• Purge all Obsolete and Locally Created Pacakges that are not needed with _ U g g
• Allow all other packages that want to be installed to be installed
• Reboot
• If this does not solve it wait a time for new updates, install them and try again. That solved the issue for us.

Clipman is not present in the panel any more. When we reinstalled it we got

Plugin "Clipman" unexpectedly left the panel, do you wan to restart it?
The plugin restarted more than once in the last 60 seconds.
If you press Execute the panel will try to restart the plugin otherwise
it will be permanently removed from the panel.

Clicking on the Execute button yielded the same window. So nothing was left than clicking on the Remove button

Running from a terminal with xfce4-clipman yielded

Unable to init server: Could not connect: Connection refused
(xfce4-clipman:4868): Gtk-WARNING **: 20:35:39.439: cannot open display: 

To be investigated

insserv: FATAL: service udev has to be enabled to use service network-manager
update-initramfs: deferring update (trigger activated)

We did not investigate what to do wiht this message. The computer runs fine

We experienced that items the user should know about but is not made aware of can break or change to something unwanted. Some items to check

• The firewall
  • iptables -L
  • ufw status verbose
• $HOME/.bashrc seems to be replaced with a default file

From the Debian 9 Stretch upgrade comments in an edited form:

Check scripts for the use of net-tools (1.60+git20161116.90da8a0-1)
The output of many commands has changed, and it is sure to break scripts that relied on parsing it. If you have customs scripts that use any of these commands, please make sure they still work after this upgrade. Involved are:

netstat, ifconfig, ipmaddr, iptunnel, mii-tool, nameif, plipconfig, rarp, route, slattach, arp

Whith Debian 8 the new line option in the Xfce panel separator has been removed. This is very annoying since we used the second row for the Windows Buttons. If a second panel is made and placed just below the first panel, sort of locking to it, the title bar of full sized windows hide behind the second panel. So adding a second panel is not useful anymore

• Firefox does not restore the session anymore
• Terminal does not start automatically. When started the tabs from the previous session are lost

On the Raspberry Pi the group and owner of the files in home/user where changed to 1001 indiecity. The uid of user is 1000. User 1001 does not exitst. Group indiecity does. Solved by adding a group user with groupadd user and running chown -R user:user $HOME/

The following packages have been kept back, why and how do I solve it

Main subjects on this wiki: Linux, Debian, HTML, Microcontrollers, Privacy

RSS
Disclaimer
Privacy statement
Bugs statement
Cookies
Copyright © : 2014 - 2024 Webevaluation.nl and the authors
Changes reserved.