07-28-2020, 10:50 AM
(This post was last modified: 07-28-2020, 10:58 AM by dancingqueen74.)
(07-28-2020, 09:48 AM)jed Wrote: Try changing releases again:
Code:sed -i 's/sid/bullseye/g' /etc/apt/sources.list
apt update
apt-get -y --allow-downgrades upgrade
sed -i 's/bullseye/sid/g' /etc/apt/sources.list
apt update
apt -y upgrade
While you're at it, it's worth reviewing the DontBreakDebian page, which covers why mixing releases is bad practice.
Hope this helps.
The Wiki instructions cause this conflict by mixing codename conventions. The below example works fine, and differentiates well.
Code:-n mobian
-n bullseye
-n sid
Thanks for your message and the information, but I don't want to upgrade to sid (that is your second sed command). Except for having fiddled with dpkg to install the already installed packages a second time (as I wrote, the versions are identical with the versions to be installed, so no downgrade here) and hoping to trigger a better error message, I did nothing that was not written in the official Mobian wiki.
I just loopmounted the Mobian image I used for the installation and looked inside the default sources.list to be on the safe side. There are clearly no mentions of sid inside (it's just "deb http://deb.debian.org/debian bullseye main"). Also I did the priority pinning recommended in the wiki to not mix distributions.
At least your first command fetched some other packages. Problem is still not solved though...
Edit: thanks for the update. Would it be possible to stay on the bullseye release?
Edit 2: I just looked inside the image again. The original priority file looks identical to my current priority file. The release is prefixed with o= both times, not n=. What I don't get is how everything should be fine again because I took back my modifications, but it isn't.