On Thu, 23 Feb 2023 at 12:51, Van Snyder <van.sny...@sbcglobal.net> wrote: > On Thu, 2023-02-23 at 11:39 +1100, David wrote: > On Thu, 23 Feb 2023 at 09:21, Van Snyder <van.sny...@sbcglobal.net> wrote: > On Wed, 2023-02-22 at 16:13 -0500, Dan Ritter wrote: > Van Snyder wrote:
> You are mixing way too many things here. Better tell us the > contents of all your /etc/apt/sources.list and > /etc/apt/sources.list.d/* files. > opm-ubuntu-ppa-kinetic.list > opm-ubuntu-ppa-kinetic.list.save > skype-stable.list > skype-stable.list.save > > I have a line for > deb [arch=amd64,i386] https://apt.repos.intel.com/oneapi all main > > but there is also a file /etc/apt/sources.list/Intel/oneAPI.list that has > the same line. > > Moving everything from /etc/apt/sources.list.d to > /etc/apt/save.sources.list.d makes the update and dist-upgrade appear to > work without complaint. > What output do you see for this command: > aptitude search '~i' -F '%p %O#' | grep -v Debian > Output is attached. (sorry for the broken quotes above) I will attempt to comment on the results, but many people here are much more competent with apt* tools than I am, so I hope they will comment also. The command I suggested reports packages whose origin is unknown to the apt database. There's 118 of them in your output, including g++-9, many libs and 6 kernels, pythons 2.7 and 3.9 and perl 5. My understanding of the origin = (installed locally) tags in that output is that this means that the apt* tools are unable to manage updating of these packages because it cannot associate them with a repository. So anything in future that involves/requires a change to any of these packages will require you to do the dependency resolution yourself because apt* won't be able to do that for you. Another way to see what repositories have been used on that machine is to run: ls /var/lib/apt/lists/*Packages It would also be interesting to see the output of that command if you wish to share it.
