Re: dist-upgrade from buster fails badly
On Fri 12 Feb 2021 at 08:02:02 -0500, Greg Wooledge wrote: > On Fri, Feb 12, 2021 at 12:56:00PM +, pioruns2019 wrote: > > Why You want to upgrade from buster to sid? You have enabled both sid > > and buster-updates repositories. This won't work, unless you know what > > you're doing. > > I suggest to install sid from the scratch, if you want to have sid. If > > you don't want to have sid, revert back to buster. > > Also, sid doesn't have debian-security updates, this entry is invalid. > > Most of this is correct, except for the part about installing sid > from scratch. That's not a thing. If one wants to run unstable, one > installs the current stable release, and then upgrades to sid. That's probably the most common way to get sid and what I would recommend. However, sid may be installed directly from the archives using the mini.iso. -- Brian.
Re: dist-upgrade from buster fails badly
On 12/02/2021 13:02, Greg Wooledge wrote: On Fri, Feb 12, 2021 at 12:56:00PM +, pioruns2019 wrote: Why You want to upgrade from buster to sid? You have enabled both sid and buster-updates repositories. This won't work, unless you know what you're doing. I suggest to install sid from the scratch, if you want to have sid. If you don't want to have sid, revert back to buster. Also, sid doesn't have debian-security updates, this entry is invalid. Most of this is correct, except for the part about installing sid from scratch. That's not a thing. If one wants to run unstable, one installs the current stable release, and then upgrades to sid. That's what OP tried and failed already. The probem here is that the OP attempted to mix stable and unstable, cherry-picking packages from unstable. This WILL NOT WORK. Ever. Of course , agreed. If you want to cherry-pick higher-numbered packages from post-stable on a stable system, use backports. Never install a binary package from a future release. That's what I do - running Stable + backports on my server. Rock solid.
Re: dist-upgrade from buster fails badly
Greg Wooledge (12021-02-12): > If one wants to run unstable, one > installs the current stable release, and then upgrades to sid. That's never how I do it. And I have no problem with my method. > The probem here is that the OP attempted to mix stable and unstable, > cherry-picking packages from unstable. This WILL NOT WORK. Ever. I have done it a few times, and it worked more often than not. Consider your universal statement disproved. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: dist-upgrade from buster fails badly
On Fri, Feb 12, 2021 at 12:56:00PM +, pioruns2019 wrote: > Why You want to upgrade from buster to sid? You have enabled both sid > and buster-updates repositories. This won't work, unless you know what > you're doing. > I suggest to install sid from the scratch, if you want to have sid. If > you don't want to have sid, revert back to buster. > Also, sid doesn't have debian-security updates, this entry is invalid. Most of this is correct, except for the part about installing sid from scratch. That's not a thing. If one wants to run unstable, one installs the current stable release, and then upgrades to sid. The probem here is that the OP attempted to mix stable and unstable, cherry-picking packages from unstable. This WILL NOT WORK. Ever. If you want to cherry-pick higher-numbered packages from post-stable on a stable system, use backports. Never install a binary package from a future release.
Re: dist-upgrade from buster fails badly
On 2021-02-12 at 06:02, thah...@t-online.de wrote: > Hello, > I have installed 10.7 and then > apt upgrade > without any problems. > However the following > apt dist-upgrade > failed badly and cannot be repaired with > apt --fix-broken install > > Correcting dependencies... failed. > The following packages have unmet dependencies: > ffmpeg : Depends: libavcodec58 (= 7:4.1.6-1~deb10u1) > Depends: libavformat58 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > Depends: libavutil56 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > Depends: libswresample3 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > gimp : Depends: libc6 (>= 2.29) but 2.28-10 is installed > libaa1 : Depends: libc6 (>= 2.29) but 2.28-10 is installed > ... > > Any advice? What do the following commands give you? $ apt-cache policy ffmpeg libavcodec58 libavformat58 libavutil56 libswresample3 libc6 $ apt-mark showhold Also, do you have any package pins in /etc/apt/preferences or /etc/apt/preferences.d/* ? That said: dist-upgrade against sid is frequently a bad idea, and I am not at all surprised that you ran into issues. The usual comment about running sid is that "if anything breaks, you get to keep the pieces". The best recommendation as I understand matters is to have sources.list entries for both testing and sid, use /etc/apt/preferences to pin sid at a priority which will never be chosen by default, and then install items from sid selectively as needed. If this is a production system rather than primarily a test machine, you might be best served to reinstall, and this time not try to dist-upgrade against sid en masse. For myself, I have sources.list entries for stable and testing, and in the rare case that I need something from sid, modify sources.list long enough to 'apt-get update ; apt-get install [packagename]', then modify sources.list to its previous state and run 'apt-get update' again. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: dist-upgrade from buster fails badly
On Fri, Feb 12, 2021 at 12:02:51PM +0100, thah...@t-online.de wrote: > The following packages have unmet dependencies: > ffmpeg : Depends: libavcodec58 (= 7:4.1.6-1~deb10u1) > Depends: libavformat58 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > Depends: libavutil56 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > Depends: libswresample3 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > gimp : Depends: libc6 (>= 2.29) but 2.28-10 is installed > libaa1 : Depends: libc6 (>= 2.29) but 2.28-10 is installed You have installed some packages from outside of Debian stable. Your choices are: 1) Remove all of the packages that did not come from Debian stable. 2) Reinstall from scratch. 3) Attempt to upgrade to testing. In the future, do NOT mix releases of Debian, or mix Debian with other operating systems (e.g. Ubuntu PPAs). This includes "debian multimedia", which is notoriously bad. But I don't see "mmo" in your error list, so maybe you didn't fall into this particular trap. Or maybe they changed their version naming.
Re: dist-upgrade from buster fails badly
thah...@t-online.de wrote: > Hello, > I have installed 10.7 and then > apt upgrade > without any problems. > However the following > apt dist-upgrade > failed badly and cannot be repaired with > apt --fix-broken install > > Correcting dependencies... failed. > The following packages have unmet dependencies: > ffmpeg : Depends: libavcodec58 (= 7:4.1.6-1~deb10u1) > Depends: libavformat58 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > Depends: libavutil56 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > Depends: libswresample3 (= 7:4.1.6-1~deb10u1) but 7:4.3.1-8 is installed > gimp : Depends: libc6 (>= 2.29) but 2.28-10 is installed > libaa1 : Depends: libc6 (>= 2.29) but 2.28-10 is installed > ... > > Any advice? Show us the contents of /etc/apt/sources.list /etc/apt/sources.list.d/* -dsr-
