Failed attempt to upgrade to Buster

[ozgta]

Hi,
I recently attempted to upgrade to Buster however the last stage failed as there were too many errors.
The error here is just an example all of them mention dependency problems.

How can I correct this?

dpkg: error processing package libreoffice-help-common (--configure):
dependency problems - leaving unconfigured
Setting up locate (4.6.0+git+20190105-2) ...
Setting up libexempi8:amd64 (2.5.0-2) ...
Setting up libmypaint-common (1:1.3.0-dmo6) ...
Setting up libip4tc0:amd64 (1.8.2-3) ...
Setting up libpam-cap:amd64 (1:2.25-1.2) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
debconf: unable to initialize frontend: Gnome
debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151.)
debconf: falling back to frontend: Dialog
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Setting up ruby-xmlrpc (0.3.0-2) ...
Setting up im-config (0.38-1) ...
Setting up chromium-sandbox (72.0.3626.53-1) ...
Setting up libevent-core-2.1-6:amd64 (2.1.8-stable-4) ...
Setting up hddtemp (0.3-beta15-53) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
debconf: unable to initialize frontend: Gnome
debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151.)
debconf: falling back to frontend: Dialog
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline

[Bulkley]

Yes. I made three attempts to upgrade to Buster and all failed. It surprised me because I have done several previous Debian upgrades without incident. There is something about Buster . . . As a practical alternative, save anything you value (I assume you already have) and do a fresh install of Buster.

[ozgta]

@ Bulkley, I did test install on a second computer and all went well so I figured I could do it on my main computer. No so, the upgrade failed entirely and I now have to do a complete install. Oh joy...

[arochester]

What does your sources list and the contents of the directory sources.list.d say?

[dilberts_left_nut]

By the time it goes stable there will be a documented procedure for a successful upgrade.

[ozgta]

Thanks everyone, the system is totally corrupted. I am in the process of re-installing...

[CwF]

Take smaller bites. I think I tried 5 so far, duplicates of an amd64 and a i386. Every single sweep attempt failed. Piece meal hasn't failed yet, so I've nuked the failures and as of Monday both are fully updated. The amd64 was once 8.5, the i386 9.3. I've held back the kernel on both. now that things are settling down I have a few more to do, so maybe I'll find an issue, but have waited until now and don't expect one.

If a package causing issues can be removed and leave settings, it is a minor step to do so as to simplify upgrades and then reinstall. At this point 3-6 bites chewed well should work.

It helps to point to a single buster repository and then you intelligently figure out the objections.

[Bulkley]

The big problem for me was that the Buster upgrade knocked out my ability to connect to the Internet. Without that I was unable to fix without more trouble than I wanted. I always make a clone before trying an upgrade so it was easy to revert to Stretch.

[CwF]

I cheat and skip that chicken egg, I use a ww-drt router as my wifi 'dongle', wired of course. Configure it in a browser if need be. However, after the upgrades I did verify real wifi and bluetooth dongles and they did work. They worked before.

[kalle123]

Have a look here

https://www.linuxmaker.com//en/tutorial ... uster.html

Followed the steps and ... no issues.

And here is my actual sources.list

I know, that there are discussions, what belongs there and what should not be in, but for me, it is ok.

Code: Select all

deb http://security.debian.org/ buster/updates main contrib non-free
deb-src http://security.debian.org/ buster/updates main contrib non-free

deb http://ftp.de.debian.org/debian/ buster main contrib non-free
deb-src http://ftp.de.debian.org/debian/ buster main contrib non-free

deb http://ftp.us.debian.org/debian buster-proposed-updates main contrib non-free