SOLVED: SERIOUS PROBLEM FOLLOWING UPDATES

I just updated my system, and one of the packages was apt-sources-stable from version 1.0.1-pclos to 1.0.2-pclos. I was a bit concerned that renewing the sources may have taken away a few sources which were added when I installed programs from a *.deb file. So I checked in Synaptic > Installed (local or obsolete), and most of the base packages from the operating system were there!

I went into /etc/apt/ and restored the old sources, and although there was a long error report when I clicked on Reload, the Installed (local or obsolete) list became a list of things I had installed from outside the repos (e.g. Brother printer drivers etc).

Here is the error report:

---------start-----------

Repository 'http://deb.debian.org/debian bookworm-updates InRelease' changed its 'Origin' value from 'Google LLC' to 'Debian'Repository 'http://deb.debian.org/debian bookworm-updates InRelease' changed its 'Label' value from 'Google' to 'Debian'Repository 'http://deb.debian.org/debian bookworm-updates InRelease' changed its 'Version' value from '1.0' to '12-updates'Repository 'http://deb.debian.org/debian bookworm-updates InRelease' changed its 'Suite' value from 'stable' to 'stable-updates'Repository 'http://deb.debian.org/debian bookworm-updates InRelease' changed its 'Codename' value from 'stable' to 'bookworm-updates'This must be accepted explicitly before updates for this repository can be applied. See apt-secure( manpage for details.Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Origin' value from 'Google LLC' to 'Debian'Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Label' value from 'Google' to 'Debian-Security'Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Version' value from '1.0' to '12'Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Suite' value from 'stable' to 'stable-security'Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Codename' value from 'stable' to 'bookworm-security'

------------end---------

Were you trying to fix this?

The repository pkgs for pclosdebian 1.0.1 repository should be the same pkgs in 1.0.2. The only change was moving to new repository as the apt.fury.io will become obsolete in the near future.  https://filedn.com/lKduLG9C0fw5CQsvoucKgV7/pclosdebian/ The debian official repositories should have not changed. I tested all that I know of and it works here?
The pclosdebian repo is in the /etc/apt/sources.list.d/pclosdebian.list. No need to have it in the /etc/apt/sources.list.

Code:

deb http://deb.debian.org/debian bookworm main contrib non-free-firmware
#deb-src http://deb.debian.org/debian bookworm main
deb http://deb.debian.org/debian bookworm-updates main
#deb-src http://deb.debian.org/debian bookworm-updates main
deb http://security.debian.org/debian-security/ bookworm-security main
#deb-src http://security.debian.org/debian-security/ bookworm-security main

I just copied the code above to /etc/apt/sources.list and the contents of the Installed (local or obsolete) section is as it should be. The file now reads exactly as the code in that comment. No idea why it was different when I updated the apt-sources-stable app.

However, there are a couple of strange things happening. I still get a huge error report as before when I "Reload". After I reload, xfce4-sound-changer and xfce4-sound-extra appear as "New in Repository", even though they are not new, and they are already installed. And the latest, orage wanted to "update" to exactly the same version. When I clicked Mark All Updates and Apply it resulted in an error — although no harm appears to have been done. Do I need to re-install afresh?

P.S. I just noticed that the PCLOS Debian repos is duplicated in /etc/apt/sources.list.d/ — could that cause a problem?

The pclosdebian repo is in the /etc/apt/sources.list.d/pclosdebian.list. So no need to have it in the /etc/apt/sources.list. Yes, you have to reload synaptic again.
so the already apps show installed. The updated apt-sources-stable deb adds it to /etc/apt/sources.list.d so the duplicate will show if it is in the /etc/apt/sources.list.
You need to remove the one in /etc/apt/sources.list .

I suspect that the long error report after clicking on "Reload" relates to what is going on at the actual repository address and as long as everything is working I can ignore that.

After correcting the repos as above, the other thing is that the xfce4-sound-changer and -extra keep reappearing as "New In Repository" every time I do an upgrade, even though they are not new and are already installed.

davecs wrote:I suspect that the long error report after clicking on "Reload" relates to what is going on at the actual repository address and as long as everything is working I can ignore that.

After correcting the repos as above, the other thing is that the xfce4-sound-changer and -extra keep reappearing as "New In Repository" every time I do an upgrade, even though they are not new and are already installed.

If you reload synaptic then xfce4-sound-changer and -extra should show as installed. You can check the https://filedn.com/lKduLG9C0fw5CQsvoucKgV7/pclosdebian/Packages.gz or the Release file. If it still shows not installed then reinstall them maybe?

Just to be clear, xfce4-sound-changer and -extra were not new, and were installed, but every time I did a Reload in synaptic, they showed up as new packages... but read on.

I have a feeling that there must have been a problem with the PCLOS-debian-XFCE iso dated 29/07/24, or in experimenting with the sound stuff, then installing the packages over them, once you had made them into packages. My KDE install on a separate partition is from an older iso (June) and doesn't have any of these problems relating to the packaging system. So last night I downloaded the XFCE version of August 13, and made a fresh installation, but using the old /home/username setup. And now everything seems to work perfectly. The xfce4-sound- packages are no longer showing up as new packages, and I'm not getting the long error report after every Reload.

Thanks for the clarification! I tested the xfce iso and no problems with it as with the other iso's when moving to the new repo so I figured the xfce4-sound-changer and -extra
on your install had something to do with the errors you were receiving as we were making changes there before the actually final pkgs. Glad you got it worked out.