Migration to 11 won't start : "libc6-dev : Breaks: libgcc-8-dev"

You’re right, it is not marked “to hold”.

But I have this when trying a normal apt upgrade :thinking:

Les paquets suivants ont été conservés :
gcc-8-base

Yup so can you share the output of apt policy gcc-8-base and apt install gcc-8-base ?

gcc-8-base:
Installé : 8.3.0-6+rpi1
Candidat : 8.4.0-7+rpi1
Table de version :
8.4.0-7+rpi1 500
500 Index of /raspbian bullseye/main armhf Packages
*** 8.3.0-6+rpi1 100
100 /var/lib/dpkg/status

and :

Les paquets suivants seront ENLEVÉS :
libgcc1
Les paquets suivants seront mis à jour :
gcc-8-base
1 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.

Then yeah, apt install gcc-8-base sounds okay to go ahead with ?

Done, I’ll see if anything goes wrong in the future :slight_smile:

Hi! Unfortunately have the same trouble. I followed all advice from the thread provided by @Aleks. I am worried that none of them worked though. Here are the results of each command I tried. I would love to provide more information if you need.

Raspberry Pi 2B (32-bits)
4.4.2.10 (stable).
Apps:
BicBucStriim
FreshRSS
HedgeDoc
Nitter
Teddit
Transmission
Wallabag

Commands:

dpkg -s $(dpkg --list | grep ynh-deps | awk ‘{print $2}’) | grep ‘Package:|Depends:’ | grep ‘build|gcc|g++’ -B1

nothing in response

apt policy libgcc-8-dev

libgcc-8-dev: Installed: 8.3.0-6+rpi1 Candidate: 8.4.0-7+rpi1 Version table: 8.4.0-7+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages *** 8.3.0-6+rpi1 100 100 /var/lib/dpkg/status

apt policy gcc-8-base

gcc-8-base: Installed: 8.3.0-6+rpi1 Candidate: 8.4.0-7+rpi1 Version table: 8.4.0-7+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages *** 8.3.0-6+rpi1 100 100 /var/lib/dpkg/status

sudo apt install gcc-8-base

`Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
yunohost : Depends: equivs but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.`

sudo cp /var/lib/dpkg/status /root/dpkg_status.bkp
sudo perl -i~ -0777 -pe ‘s/(Package: .-ynh-deps\n(.+:.+\n)+Depends:.)(build-essential, ?)(.*)/$1$4/g’ /var/lib/dpkg/status

no response

sudo apt remove build-essential gcc-8 libgcc-8-dev

`Package ‘build-essential’ is not installed, so not removed
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
yunohost : Depends: equivs but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.`

sudo apt remove build-essential
sudo apt autoremove
sudo apt remove gcc-8 libgcc-8-dev

`admin@pi:~ $ sudo apt remove build-essential
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package ‘build-essential’ is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 853 not upgraded.

admin@pi:~ $ sudo apt autoremove
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 853 not upgraded.

admin@pi:~ $ sudo apt remove gcc-8 libgcc-8-dev
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
yunohost : Depends: equivs but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.`

sudo cp /var/lib/dpkg/status /root/dpkg_status.bkp
sudo perl -i~ -0777 -pe ‘s/(Package: .-ynh-deps\n(.+:.+\n)+Depends:.)(build-essential, ?)(.*)/$1$4/g’ /var/lib/dpkg/status

no response

I’m unable to profit! :wink: After step 2, here’s the output (see below). The migration from 4 to 11 fails.

Any suggestions on what to try next?

admin@net:~ $ sudo apt remove gcc-8 libgcc-8-dev
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
borg-ynh-deps : Depends: python3-dev but it is not going to be installed
Depends: libacl1-dev but it is not going to be installed
Depends: libfuse-dev but it is not going to be installed
dh-autoreconf : Depends: libtool (>= 2.4.2) but it is not going to be installed
funkwhale-ynh-deps : Depends: libsasl2-dev but it is not going to be installed
Depends: zlib1g-dev but it is not going to be installed
Depends: libjpeg-dev
Depends: python3-dev but it is not going to be installed
libglib2.0-0 : Breaks: libgirepository-1.0-1 (< 1.62.0-4~) but 1.58.3-2 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I edited the previous answer : the instructions are obsolete because Yunohost now automatically tries to autopatch the issue.

If it didn’t, please share the full log of the migration

Thanks for the quick reply.
Ah - I tried the instructions above before attempting the migration, as I assumed it would still be an issue from reading this page:

So apparently I have hosed things up a bit. Any suggestions on what to do going forward?
Here is the migration log:
https://paste.yunohost.org/raw/iferogekig

Tried restoring “/root/dpkg_status.bkp” to /var/lib/dpkg/status, but it looks like when the migration runs, it also creates a backup in the exact same file, so it overwrote the backup I made when doing the fix before the migration as per instructions in post above.

Can’t find that file in my yunohost backup. I guess that means my only hope is to run a command that does the opposite of whatever this command does — yeesh. Is it time to start over, and try to restore from my yunohost 4x backup onto a fresh install of 11?

sudo perl -i~ -0777 -pe 's/(Package: .*-ynh-deps\n(.+:.+\n)+Depends:.*)(build-essential, ?)(.*)/$1$4/g' /var/lib/dpkg/status

Thanks everyone for support!

I have a question though - how can I make the migration when I skipped it in the past?

Back then, when migration failed because of the libc6-dev issue, I found out that the Debian 11 based Yunohost is available only for 64-bits Raspberry Pis (because there was no image for 32-bits RPis). I wrongly decided to Skip the migration from 4.4.2.10 in order to have following up-to-date iterations of Yunohost series 4.
Right now I am conscious it wasn’t true, and I wasn’t supposed to do it, but I am no longer able to make the migration.

Edit /etc/yunohost/migrations.json (i always forgot if it’s a json or yml or yaml …)

and remove the line corresponding to 0021_migrate_to_bullseye (and remove ONLY that line, not the others)

The file is called migrations.yaml. :slight_smile:
It allowed me to make migration once again, thanks!
The migration itself didn’t go so smooth, though.
I hope these logs will tell you more than I am able to.

https://paste.yunohost.org/raw/woxelavipa

I’m answering late, don’t know if you made some progress since then

Otherwise I would attempt this:

LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none sudo apt install --quiet -o=Dpkg::Use-Pty=0 --fix-broken --assume-yes gcc-8- libgcc-8-dev- debhelper dh-autoreconf
1 Like

Hi Aleks, your solution made the migration successful. Thanks for your patience!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.