Running 20.o4, up till now entirely updated.

My tale of woe (And apologies for it's length):

~$ sudo apt update
Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
Hit:3 http://ppa.launchpad.net/gerardpuig/ppa/ubuntu focal InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:5 http://deb.debian.org/debian-security buster/updates InRelease
Hit:6 http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu focal InRelease
Hit:7 http://ppa.launchpad.net/mkusb/unstable/ubuntu focal InRelease
Hit:8 http://ppa.launchpad.net/mozillateam/firefox-next/ubuntu focal InRelease
Fetched 56.6 kB in 1s (41.1 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
....
:~$ apt list --upgradable
Listing... Done
libjpeg-turbo-progs/oldstable 1:1.5.2-2+deb10u1 amd64 [upgradable from: 2.0.3-0ubuntu1.20.04.1]
N: There are 2 additional versions. Please use the '-a' switch to see them.
....

~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libjpeg-turbo-progs
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
....
~$ sudo apt install libjpeg-turbo-progs
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:
libjpeg-turbo-progs : Depends: libturbojpeg0 (>= 1.4.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
....
But:
~$ sudo apt install libturbojpeg0
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:
libjpeg8 : Depends: libjpeg-turbo8 (>= 1.1.90+svn722-1ubuntu6) but it is not going to be installed
libqt5svg5 : Depends: libqt5widgets5 (>= 5.12.8+dfsg~) but it is not going to be installed
qt5-gtk-platformtheme : Depends: libgtk-3-0 (>= 3.9.10) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
....
~$ sudo apt install libjpeg8
Reading package lists... Done
Building dependency tree
Reading state information... Done
libjpeg8 is already the newest version (8c-2ubuntu8).
libjpeg8 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Also, checking for held packages:
~$ apt-mark showhold
~$ <== nothing there

And checking in case libjpeg-turbo-progs is held in a partial phase:

apt-cache policy libjpeg-turbo-progs
libjpeg-turbo-progs:
Installed: 2.0.3-0ubuntu1.20.04.1
Candidate: 1:1.5.2-2+deb10u1
Version table:
1:1.5.2-2+deb10u1 300
300 http://deb.debian.org/debian buster/main amd64 Packages
*** 2.0.3-0ubuntu1.20.04.1 100
100 /var/lib/dpkg/status
2.0.3-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
(no % characters)

Apologies once again for the length of this post. All and any comments gratefully accepted,
And if I'm being an idiot, let me know.

Thanks,
Mike

On Fri, 2 Sep 2022 08:58:28 +0300
Henry Crun <mike@rechtman.com> wrote:

> ~$ sudo apt update
> Hit:1 http://deb.debian.org/debian buster InRelease
> Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]

You have Ubuntu, but you also have Debian's repos in your sources.list.
This will create a huge mess.
Reinstall with Ubuntu 22.04 and only use repositories that are mode for
your OS. Don't place repos from other operating systems in your
sources.list.

On 02/09/2022 9:55, Marco Moock wrote:
> On Fri, 2 Sep 2022 08:58:28 +0300
> Henry Crun <mike@rechtman.com> wrote:
>
>> ~$ sudo apt update
>> Hit:1 http://deb.debian.org/debian buster InRelease
>> Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
>
> You have Ubuntu, but you also have Debian's repos in your sources.list.
> This will create a huge mess.
> Reinstall with Ubuntu 22.04 and only use repositories that are mode for
> your OS. Don't place repos from other operating systems in your
> sources.list.
>

The debian repositories have been there since 2020, when I used them to install chromium without using snap.
They have never caused problems before, and are not in use currently.
I was planning on staying with 20.04 for another few months, as it is supported until 2025
Rather than upgrading now, I will grit my teeth and ignore the apt messages (The don't seem to hurt, just bother my
sense of cleanlines...)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Henry Crun wrote:
> On 02/09/2022 9:55, Marco Moock wrote:
>> On Fri, 2 Sep 2022 08:58:28 +0300
>> Henry Crun <mike@rechtman.com> wrote:
>>
>>> ~$ sudo apt update
>>> Hit:1 http://deb.debian.org/debian buster InRelease
>>> Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
>>
>> You have Ubuntu, but you also have Debian's repos in your sources.list.
>> This will create a huge mess.
>> Reinstall with Ubuntu 22.04 and only use repositories that are mode for
>> your OS. Don't place repos from other operating systems in your
>> sources.list.
>>
>
> The debian repositories have been there since 2020, when I used them
> to install chromium without using snap.
> They have never caused problems before, and are not in use
> currently.

They _are_ in use (as evidenced by being in your repo caches getting
updated), and are causing you trouble now; as Debian and Ubuntu's
version of the stuck application have diverged in requirements.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmMR8AwACgkQbWVw5Uzn
KGCEgQ/+LG9NSCOisZvTjHZXMcFLp4DcrGidtl5uPb08CHo7341SMzqn0FYbTVRs
TTPEweMI6D7ReXT07US+2fsjT5Mk8TSuECKpD7dWshKJ34I3wNsmsGl46TdpDw6A
LDQ3pfYa/STOOhZEe3BwDMmjyDrYE+e4HNhbywMhPrgCAfL/lXaUHCQbAwspleaE
hsenuSX2aGcoDQSHxiLSvj9HVpQ0tPfo23dN3XD0Gls7C0KAa2zeTv/6RfwkDeES
M7BFH1UfRxc1qVEW3QWr5Aj+y6RT2IQy9yugs19qHd6XvnmwBqvgthComf5Sa1HC
8nyjcgzcGQ7tMjyoE1xsbJrTRuUY55OdEvmu4eb2witZGiXj7Ew/X9IKUfM93otR
LcP907asal151X1jcun4p0p39SrWBzJgblkNuWcsuoj5f+3KGZVf+N+uoplpVbam
wcmjUdKNkzGSJHZKpDUpeAP1A3xfapNwKN6BMf9C82XNWSaSrq9HIS+2AK5FDWQ9
QVRj3xdnvm2K/ODrevfflph1GEGxXqCbTVFKemv+XJIkwntqWiddz7SLt/MxhpA5
VEO03dETicCmnwLsAfyBmB7PdS7OqXVHbRqHlpWehzbe3g6nRufV0CvE6R8AFfZh
HWFjIQXI/f8iVVwIkL22M85UP2B5rwILJFrxsTSP0r2N5LaYoLo=
=d5gO
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

On Fri, 2 Sep 2022 11:43:25 +0300
Henry Crun <mike@rechtman.com> wrote:

> The debian repositories have been there since 2020, when I used them
> to install chromium without using snap. They have never caused
> problems before, and are not in use currently. I was planning on
> staying with 20.04 for another few months, as it is supported until
> 2025 Rather than upgrading now, I will grit my teeth and ignore the
> apt messages (The don't seem to hurt, just bother my sense of
> cleanlines...)

You can't install updates in that state, your system will be outdated
soon.
You need to da clean install. If you don't like snap, but need software
from it, you can check if there is a special repo that only contains
the packages you need that is designed for you OS, but activating a
repo that is from another distribution will create a huge mess, you
already have that on your current system.

Henry Crun wrote:
> On 02/09/2022 9:55, Marco Moock wrote:
>> On Fri, 2 Sep 2022 08:58:28 +0300
>> Henry Crun <mike@rechtman.com> wrote:
>>
>>> ~$ sudo apt update
>>> Hit:1 http://deb.debian.org/debian buster InRelease
>>> Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
>>
>> You have Ubuntu, but you also have Debian's repos in your sources.list.
>> This will create a huge mess.
>> Reinstall with Ubuntu 22.04 and only use repositories that are mode for
>> your OS. Don't place repos from other operating systems in your
>> sources.list.
>>
>
> The debian repositories have been there since 2020, when I used them to
> install chromium without using snap.
> They have never caused problems before, and are not in use currently.
> I was planning on staying with 20.04 for another few months, as it is
> supported until 2025
> Rather than upgrading now, I will grit my teeth and ignore the apt
> messages (The don't seem to hurt, just bother my sense of cleanlines...)

or next time use a PPA over Debian repos as I did for deb version of
Firefox in 20.04. Here is what I found for Chromium

<https://ubuntuhandbook.org/index.php/2020/06/install-chromium-via-deb-ubuntu-20-04/>

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On 02/09/2022 9:55, Marco Moock wrote:
> On Fri, 2 Sep 2022 08:58:28 +0300
> Henry Crun <mike@rechtman.com> wrote:
>
>> ~$ sudo apt update
>> Hit:1 http://deb.debian.org/debian buster InRelease
>> Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
>
> You have Ubuntu, but you also have Debian's repos in your sources.list.
> This will create a huge mess.
> Reinstall with Ubuntu 22.04 and only use repositories that are mode for
> your OS. Don't place repos from other operating systems in your
> sources.list.
>

O.K. You were all right, and I was wrong. Mea culpa!!
Deleted all debian-related files from /etc/apt/sources.list.d/debian*
The original problem disappeared, and now apt update runs clean.
I hope I haven't broken anything serious,
Apologies once again - I should have been less obstinate!

Thanks to all who responded, I'll try to be more careful in future.
Mike

On 9/1/22 22:58, Henry Crun wrote:
> Running 20.o4, up till now entirely updated.
>
> My tale of woe (And apologies for it's length):
>
> ~$ sudo apt update
> Hit:1 http://deb.debian.org/debian buster InRelease
> Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
> Hit:3 http://ppa.launchpad.net/gerardpuig/ppa/ubuntu focal InRelease
> Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease
> Hit:5 http://deb.debian.org/debian-security buster/updates InRelease
> Hit:6 http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu focal InRelease
> Hit:7 http://ppa.launchpad.net/mkusb/unstable/ubuntu focal InRelease
> Hit:8 http://ppa.launchpad.net/mozillateam/firefox-next/ubuntu focal
> InRelease
> Fetched 56.6 kB in 1s (41.1 kB/s)
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 1 package can be upgraded. Run 'apt list --upgradable' to see it.
> ...
> :~$ apt list --upgradable
> Listing... Done
> libjpeg-turbo-progs/oldstable 1:1.5.2-2+deb10u1 amd64 [upgradable from:
> 2.0.3-0ubuntu1.20.04.1]
> N: There are 2 additional versions. Please use the '-a' switch to see them.
> ...
>
> ~$ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages have been kept back:
>   libjpeg-turbo-progs
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> ...
> ~$ sudo apt install libjpeg-turbo-progs
> 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:
>  libjpeg-turbo-progs : Depends: libturbojpeg0 (>= 1.4.0) but it is not
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> ...
> But:
> ~$ sudo apt install libturbojpeg0
> 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:
>  libjpeg8 : Depends: libjpeg-turbo8 (>= 1.1.90+svn722-1ubuntu6) but it
> is not going to be installed
>  libqt5svg5 : Depends: libqt5widgets5 (>= 5.12.8+dfsg~) but it is not
> going to be installed
>  qt5-gtk-platformtheme : Depends: libgtk-3-0 (>= 3.9.10) but it is not
> going to be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused by held packages.
> ...
> ~$ sudo apt install libjpeg8
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> libjpeg8 is already the newest version (8c-2ubuntu8).
> libjpeg8 set to manually installed.
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
>
>
> Also, checking for held packages:
> ~$ apt-mark showhold
> ~$                     <== nothing there
>
> And checking in case libjpeg-turbo-progs is held in a partial phase:
>
> apt-cache policy libjpeg-turbo-progs
> libjpeg-turbo-progs:
>   Installed: 2.0.3-0ubuntu1.20.04.1
>   Candidate: 1:1.5.2-2+deb10u1
>   Version table:
>      1:1.5.2-2+deb10u1 300
>         300 http://deb.debian.org/debian buster/main amd64 Packages
>  *** 2.0.3-0ubuntu1.20.04.1 100
>         100 /var/lib/dpkg/status
>      2.0.3-0ubuntu1 500
>         500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
> (no % characters)
>
> Apologies once again for the length of this post. All and any comments
> gratefully accepted,
> And if I'm being an idiot, let me know.
>
> Thanks,
> Mike

i think your problem is a system which depends on Snap or Flatpaks or
other such nonsense. Cannot Ubuntu package programs
as Debs?
Nearly everywhere I hear of problems with dependencies the
system are loaded with snaps or flatpaks and you have mixed in
Debian repositories as well. Not necessarily an idiot but overly
adventurous.

Sometime I go outside of the regular repositories of
the distribution I use to pull deprecated programs out of
archives. Not often and sometimes they do not work but
I seldom try to find an alien package format.

bliss - brought to you by the power and ease of PCLinuxOS
the Perfect Computer Linus Operating System(for me),
and a minor case of hypergraphia.
Linux 5.19.6

--
bliss dash SF 4 ever at dslextreme dot com

Am Samstag, 03. September 2022, um 06:45:23 Uhr schrieb Henry Crun:

> Deleted all debian-related files from /etc/apt/sources.list.d/debian*
> The original problem disappeared, and now apt update runs clean.
> I hope I haven't broken anything serious,

I don't think so if packages from Debian 10 were installed.
You should check which packages have no installation candidate anymore,
and therefore are local.

Run this to see them:
LANG=EN apt list |grep 'local\]'

Am Freitag, 02. September 2022, um 21:42:40 Uhr schrieb Bobbie Sellers:

> Nearly everywhere I hear of problems with dependencies the
> system are loaded with snaps or flatpaks and you have mixed in
> Debian repositories as well. Not necessarily an idiot but overly
> adventurous.

No, snap and flatpak are not the problem here. The problem is that
Debian repositories are in the sources.list of an Ubuntu system. This
will create a huge dependency mess. Installation scripts may also be
incompatible.

On 03/09/2022 7:42, Bobbie Sellers wrote:
> On 9/1/22 22:58, Henry Crun wrote:
>> Running 20.o4, up till now entirely updated.
>>
>> My tale of woe (And apologies for it's length):
>>
>> ~$ sudo apt update
>> Hit:1 http://deb.debian.org/debian buster InRelease
>> Get:2 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
>> Hit:3 http://ppa.launchpad.net/gerardpuig/ppa/ubuntu focal InRelease
>> Hit:4 http://archive.ubuntu.com/ubuntu focal InRelease
>> Hit:5 http://deb.debian.org/debian-security buster/updates InRelease
>> Hit:6 http://ppa.launchpad.net/kelebek333/kablosuz/ubuntu focal InRelease
>> Hit:7 http://ppa.launchpad.net/mkusb/unstable/ubuntu focal InRelease
>> Hit:8 http://ppa.launchpad.net/mozillateam/firefox-next/ubuntu focal InRelease
>> Fetched 56.6 kB in 1s (41.1 kB/s)
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> 1 package can be upgraded. Run 'apt list --upgradable' to see it.
>> ...
>> :~$ apt list --upgradable
>> Listing... Done
>> libjpeg-turbo-progs/oldstable 1:1.5.2-2+deb10u1 amd64 [upgradable from: 2.0.3-0ubuntu1.20.04.1]
>> N: There are 2 additional versions. Please use the '-a' switch to see them.
>> ...
>>
>> ~$ sudo apt upgrade
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Calculating upgrade... Done
>> The following packages have been kept back:
>>    libjpeg-turbo-progs
>> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
>> ...
>> ~$ sudo apt install libjpeg-turbo-progs
>> 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:
>>   libjpeg-turbo-progs : Depends: libturbojpeg0 (>= 1.4.0) but it is not going to be installed
>> E: Unable to correct problems, you have held broken packages.
>> ...
>> But:
>> ~$ sudo apt install libturbojpeg0
>> 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:
>>   libjpeg8 : Depends: libjpeg-turbo8 (>= 1.1.90+svn722-1ubuntu6) but it is not going to be installed
>>   libqt5svg5 : Depends: libqt5widgets5 (>= 5.12.8+dfsg~) but it is not going to be installed
>>   qt5-gtk-platformtheme : Depends: libgtk-3-0 (>= 3.9.10) but it is not going to be installed
>> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
>> ...
>> ~$ sudo apt install libjpeg8
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> libjpeg8 is already the newest version (8c-2ubuntu8).
>> libjpeg8 set to manually installed.
>> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
>>
>>
>> Also, checking for held packages:
>> ~$ apt-mark showhold
>> ~$                     <== nothing there
>>
>> And checking in case libjpeg-turbo-progs is held in a partial phase:
>>
>> apt-cache policy libjpeg-turbo-progs
>> libjpeg-turbo-progs:
>>    Installed: 2.0.3-0ubuntu1.20.04.1
>>    Candidate: 1:1.5.2-2+deb10u1
>>    Version table:
>>       1:1.5.2-2+deb10u1 300
>>          300 http://deb.debian.org/debian buster/main amd64 Packages
>>   *** 2.0.3-0ubuntu1.20.04.1 100
>>          100 /var/lib/dpkg/status
>>       2.0.3-0ubuntu1 500
>>          500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
>> (no % characters)
>>
>> Apologies once again for the length of this post. All and any comments gratefully accepted,
>> And if I'm being an idiot, let me know.
>>
>> Thanks,
>> Mike
>
>     i think your problem is a system which depends on Snap or Flatpaks or other such nonsense.  Cannot Ubuntu package
> programs
> as Debs?
>     Nearly everywhere I hear of problems with dependencies the
> system are loaded with snaps or flatpaks and you have mixed in
> Debian repositories as well.  Not necessarily an idiot but overly
> adventurous.
>
>     Sometime I go outside of the regular repositories of
> the distribution I use to pull deprecated programs out of
> archives.  Not often and sometimes they do not work but
> I seldom try to find an alien package format.
>
>  bliss - brought to you by the power and ease of PCLinuxOS
>        the Perfect Computer Linus Operating System(for me),
>           and a minor case of hypergraphia.
>         Linux 5.19.6
>

To reiterate my apology:

>O.K. You were all right, and I was wrong. Mea culpa!!
>Deleted all debian-related files from /etc/apt/sources.list.d/debian*
>The original problem disappeared, and now apt update runs clean.
>I hope I haven't broken anything serious,
>Apologies once again - I should have been less obstinate!
>
>Thanks to all who responded, I'll try to be more careful in future.
>Mike

On 09/02/2022 02:58 AM, Henry Crun wrote:
> Running 20.o4, up till now entirely updated.
>
> My tale of woe (And apologies for it's length):

Switch to MX-Linux :-D