Hello,
Yesterday I did an "aptitude update" followd by "aptitude upgrade". The sw-update obviously was "huge" and included loads of components. Since then I get lots of warnings/errors when again trying to update my software. It seems to me that the files sources.list and the entries in sources.list.d are incorrect. Has anybody else the same experience?
Regards
H. Stoelllinger

The "aptitude update" warnings are loads of the following type ...

Code: Select all

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:46 and /etc/apt/sources.list.d/official-package-repositories.list:9


I suppose some of the sources.list and/or sources.list.d definitions should be removed. But which???

Here are the various sources.list files:
(1) sources.list after update:

Code: Select all

# deb cdrom:[neon userlts _Xenial_ - Build amd64 LIVE Binary 20171025-10:39]/ xenial main multiverse restricted universe

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://at.archive.ubuntu.com/ubuntu/ xenial main restricted
# deb-src http://at.archive.ubuntu.com/ubuntu/ xenial main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://at.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
# deb-src http://at.archive.ubuntu.com/ubuntu/ xenial-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://at.archive.ubuntu.com/ubuntu/ xenial universe
# deb-src http://at.archive.ubuntu.com/ubuntu/ xenial universe
deb http://at.archive.ubuntu.com/ubuntu/ xenial-updates universe
# deb-src http://at.archive.ubuntu.com/ubuntu/ xenial-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://at.archive.ubuntu.com/ubuntu/ xenial multiverse
# deb-src http://at.archive.ubuntu.com/ubuntu/ xenial multiverse
deb http://at.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
# deb-src http://at.archive.ubuntu.com/ubuntu/ xenial-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://at.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse
# deb-src http://at.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu xenial partner
# deb-src http://archive.canonical.com/ubuntu xenial partner

deb http://security.ubuntu.com/ubuntu xenial-security main restricted
# deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted
deb http://security.ubuntu.com/ubuntu xenial-security universe
# deb-src http://security.ubuntu.com/ubuntu xenial-security universe
deb http://security.ubuntu.com/ubuntu xenial-security multiverse


(2) sources.list.d files after update:

Code: Select all

aacebedo-fasd-xenial.list
aacebedo-ubuntu-fasd-xenial.list
aacebedo-ubuntu-fasd-xenial.list.save
additional-repositories.list
danielrichter2007-grub-customizer-xenial.list
danielrichter2007-ubuntu-grub-customizer-xenial.list
danielrichter2007-ubuntu-grub-customizer-xenial.list.save
draios.list
google-chrome.list
graphics-drivers-ppa-xenial.list
graphics-drivers-ubuntu-ppa-xenial.list
graphics-drivers-ubuntu-ppa-xenial.list.save
linuxenko-chkservice-xenial.list
mscore-ubuntu-ubuntu-mscore-stable-xenial.list
mscore-ubuntu-ubuntu-mscore-stable-xenial.list.save
neon.list
neon.list.save
official-package-repositories.list
skype-stable.list
skype-stable.list.save
spotify.list
ubuntu-defaults.list
vivaldi.list
vivaldi.list.save
vivaldi-snapshot.list
vivaldi-snapshot.list.save


I would say from the warning you posted, it is telling you which one is causing the duplication: /etc/apt/sources.list.d/official-package-repositories.list
Whatever that is, looking at the the name of the file, seems to be a duplication of your repos as defined in the /etc/apt/sources.list file. I would say that removing this would fix the issue......

.....but then, I see an ubuntu-defaults listed as well, which also seems to indicate another duplicate set of default sources.

What is additional-repositories.list from? This may also be a source of duplicates.
Where are you getting these sources from?

I would also look at these

aacebedo-fasd-xenial.list
aacebedo-ubuntu-fasd-xenial.list

and

danielrichter2007-grub-customizer-xenial.list
danielrichter2007-ubuntu-grub-customizer-xenial.list

and

graphics-drivers-ppa-xenial.list
graphics-drivers-ubuntu-ppa-xenial.list

to see if these have duplicate contents. I would guess that each one with a corresponding .save file is the correct one

Many thanks, claydoh!
I had a closer look myself and eliminated the duplicates. There are still a couple of "irregularities", such as some repositories not found (eg. http://archive.canonical.com/ubuntu/dis ... 4/Packages), some repositories not signed (eg. http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial InRelease), or no public key available (eg. http://packages.linuxmint.com sonya Release).
Having commented out the "culprit" repositories everything works o.k. now. One issue that bothers me is that through the "giant" update/upgrade mentioned, the repository entries got messed up. I myself didn't do ANYTHING else besides invoking an aptitude clean, update and then upgrade! Honestly! I can't help suspecting some "careless" chap at KDE Neon messed things up... Never mind!
Greeetings from Salzburg, Austria
H. Stoellinger

hstoellinger wrote:http://archive.canonical.com/ubuntu/dists/sonya/partner/binary-amd64/Packages

yes, this is an invalid repo url, as 'sonya' is not an Ubuntu name

some repositories not signed (eg. http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial InRelease), or no public key available (eg. http://packages.linuxmint.com sonya Release).

This all depends on how the repos were added, and why do you have Linux Mint repos on a Neon system? Or have you added Neon repos to a Mint system?? In any case, if you post the specific error message involving each each repo above, we can help get that fixed pretty easily.

Having commented out the "culprit" repositories everything works o.k. now. One issue that bothers me is that through the "giant" update/upgrade mentioned, the repository entries got messed up. I myself didn't do ANYTHING else besides invoking an aptitude clean, update and then upgrade! Honestly! I can't help suspecting some "careless" chap at KDE Neon messed things up... Never mind!
Greeetings from Salzburg, Austria
H. Stoellinger

Unless some package you installed or was updated added all these extraneous repos for some reason, running apt itself (or aptitude, or any other package manager or update utility) does not change your repositories. I have no idea where you would be getting all these added repos added from, as neither Ubuntu nor Neon would be doing this. Perhaps letting us know what ppas or other repos you have added yourself, and listing the contents of those entries in /etc/apt/sources.list.d you are not sure about might help as well

Greetings from Savannah, Georgia, USA!

Hi,
Thanks again for bothering - and so promptly!
Having corrected the situation myself I Unfortunately don't have the erroneous sources.list and sources.list.d files available anymore...
Again, I can only say the following: It has been my habit to update/upgrade my Linux-SW as a first thing every morning, as I know that this is a good thing to do for a number reasons (eg. security!), so as to close as many "holes" as possible...
This update procedure (aptitude update/aptitude uprade, NO OTHER command of any sort!) is represented by an alias "swu" - which is the only command I invoked. As I have already mentioned, this time loads of updated pieces of sw (packages) got updated!
Up to this incident there was NOT a single problem with my sources.list (and ....d) at all, no duplicates, no indexes missing, nothing!
So I have to assume that the problem was due to some error "on the other side" (i.e. NEON). I definitely did NOT add any Mint-repositories to NEON, neither of NEON repositories to Mint - which incidently is also installed on the laptop but of course was not active at the time...
As an "old" (literally!) IBM systems engineer I did of course experience customers maintaining that they hadn't "changed anything" -- which then turned out wrong!
Greetings from Austria (it's getting cold here!!)
H. Stoellinger