can't resolve conflicts with apt
Hi,
i've got an open thread on ubuntuforums.org: https:/
[QUOTE=
[CODE]$ ls /usr/lib | grep python
$ ls -ld /usr/bin/python
$ ls -ld /usr/bin/python3
$ which python
$ python --version[/CODE]
To remove a package:
[CODE]sudo apt remove <package name>[/CODE]
I'm not sure if that will work on partially installed packages if not try.
[CODE]sudo apt purge <package name>[/CODE]
or combine the two
[CODE]sudo apt remove --purge <package name>[/CODE]
I'd be careful and remove them one at a time.
The command should include the version number the standard Ubuntu would be something like apt-python3.7
Python-minimal is a pretty important package breaking it could break all sorts of stuff.
This seems to me likely to be the most critical package holding up the works since the 3.7 version is already installed.
[/QOTE]
[code]
$ ls /usr/lib |grep python
python2.7
python3
python3.5
python3.7
python3.8
$ ls -ld /usr/bin/python
lrwxrwxrwx 1 root root 9 Nov 23 2017 /usr/bin/python -> python2.7
$ ls -ld /usr/bin/python3
lrwxrwxrwx 1 root root 9 Mar 26 03:25 /usr/bin/python3 -> python3.7
$ which python
/usr/bin/python
$ python --version
Python 2.7.12
[/code]
Let's see, just making sure that I understand. the Python3.8 library seems to be a bit out of place, why does Python3 not link to the 3.8, should it?
Now, I have not gone ahead and removed or purged anything else yet. I've also got the following:
[code]
$ ls -l /usr/bin/python*
lrwxrwxrwx 1 root root 9 Nov 23 2017 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root 9 Nov 23 2017 /usr/bin/python2 -> python2.7
lrwxrwxrwx 1 root root 15 Jul 25 09:29 /usr/bin/python2.5 -> /usr/bin/python
-rwxr-xr-x 1 root root 3492656 Aug 22 12:43 /usr/bin/python2.7
lrwxrwxrwx 1 root root 33 Aug 22 12:43 /usr/bin/
lrwxrwxrwx 1 root root 16 Nov 23 2017 /usr/bin/
lrwxrwxrwx 1 root root 9 Mar 26 03:25 /usr/bin/python3 -> python3.7
-rwxr-xr-x 2 root root 4460272 Aug 20 13:08 /usr/bin/python3.5
lrwxrwxrwx 1 root root 33 Aug 20 13:08 /usr/bin/
-rwxr-xr-x 2 root root 4460272 Aug 20 13:08 /usr/bin/python3.5m
lrwxrwxrwx 1 root root 34 Aug 20 13:08 /usr/bin/
-rwxr-xr-x 2 root root 4877888 Apr 2 22:39 /usr/bin/python3.7
lrwxrwxrwx 1 root root 33 Apr 2 22:39 /usr/bin/
-rwxr-xr-x 2 root root 4877888 Apr 2 22:39 /usr/bin/python3.7m
lrwxrwxrwx 1 root root 34 Apr 2 22:39 /usr/bin/
lrwxrwxrwx 1 root root 16 Mar 26 03:25 /usr/bin/
lrwxrwxrwx 1 root root 10 Mar 26 03:25 /usr/bin/python3m -> python3.7m
lrwxrwxrwx 1 root root 17 Mar 26 03:25 /usr/bin/
lrwxrwxrwx 1 root root 16 Nov 23 2017 /usr/bin/
[/code]
[QUOTE=
Before doing anything irreversible you might want to try:
[CODE]sudo apt install python3-minimal libpython3-stdlib --reinstall --simulate[/CODE]
This should run the command without actually doing anything but should also show you what the command would do without the --simulate
to make sure it will try to download and install 3.5.1-3 over the existing 3.7 packages.[/QUOTE] Cool, I didn't even know about the [b]--simulate[/b] option. Great, Thanks!
[QUOTE=
In fact you might want to download the debs for python3-minimal or get a Ubuntu 16.04 iso and add it to your sources before you attempt to remove anything so if apt breaks you will still have them available[/QUOTE]
Yes, I will download a 16.04 iso and mount it!
and then, the next reply says:
At least part of the problem is that python3 is linked to python3.7.
In 16.04 the default is to link to python3.5. Simply changing that link may fix it. Since Python is so important for many things you need to be sure before you do anything or at least be prepared for the concequences. You can really mess up your system.
If a reinstall of python3-minimal from the Ubuntu repositories fixes the python3 link you will probably be fine.
You could try renaming the python3 link (python3.7?) and create a new link python3 to python 3.5 and reboot.
If that doesn't work you could boot into a recovery shell or an iso and fix it. This option offers the possibility of returning the system to its current state.
You could also try removing python3.7
The real question is are you feeling lucky?
The problem is, I can't install python3-minimal:
$ sudo apt install python3-minimal --reinstall --simulate
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reinstallation of python3-minimal is not possible, since it cannot be downloaded.
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
apt-xapian-index : Depends: python3-xapian (>= 1.4.3-1)
cmake : Depends: cmake-data (= 3.5.1-1ubuntu3) but 3.13.4-1 is to be installed
libcairo2-dev:i386 : Depends: libfontconfig1-
libglib2.0-bin : Depends: libglib2.0-0 (= 2.60.0-1) but 2.48.2-0ubuntu4.4 is to be installed
libglib2.
python3 : PreDepends: python3-minimal (= 3.5.1-3) but 3.7.3-1 is to be installed
Depends: libpython3-stdlib (= 3.5.1-3) but 3.7.3-1 is to be installed
python3-apt : Depends: python3 (>= 3.7~) but 3.5.1-3 is to be installed
python3-brlapi : Depends: python3 (>= 3.7~) but 3.5.1-3 is to be installed
python3-dev : Depends: python3 (= 3.7.3-1) but 3.5.1-3 is to be installed
python3-distutils : Depends: python3 (>= 3.7.1-1~) but 3.5.1-3 is to be installed
python3-lib2to3 : Depends: python3 (>= 3.7.1-1~) but 3.5.1-3 is to be installed
python3-
python3-lxml : Depends: python3 (>= 3.7~) but 3.5.1-3 is to be installed
python3-pil : Depends: python3 (>= 3.7~) but 3.5.1-3 is to be installed
testdrive-common : Depends: qemu-kvm or
virtualbox-
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
What would you recommend I do?
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
For diagnostic purposes please provide the output of the following commands (even if that information partly is already available on ubuntuforums):
uname -a
lsb_release -crid
grep '^deb ' /etc/apt/
sudo dpkg --audit
apt-cache policy python3 python3-minimal libglib2.0-bin libglib2.0-0
My first conclusion: There are packages from other sources or for higher releases on your system.
Revision history for this message
|
#2 |
okay,
Here's the requested data:
ron@jpax-
Linux jpax-build07 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ron@jpax-
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
ron@jpax-
/etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
/etc/apt/
grep: /etc/apt/
ron@jpax-
[sudo] password for ron:
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
apt-xapian-index maintenance and search tools for a Xapian index of Debian
cmake-data CMake data files (modules, templates and documentation)
dwz DWARF compression tool
libcomerr2:i386 transitional package
libffi-dev:i386 Foreign Function Interface library (development files)
libglib2.0-bin Programs for the GLib library
libpsl5:amd64 Library for Public Suffix List (shared libraries)
python3-apt Python 3 interface to libapt-pkg
python3-
python3-dev header files and a static library for Python (default)
python3-distutils distutils package for Python 3.x
python3-lib2to3 Interactive high-level object-oriented language (2to3, ve
python3-
python3-lxml:amd64 pythonic binding for the libxml2 and libxslt libraries
python3-pil:amd64 Python Imaging Library (Python3)
uuid-dev:i386 Universally Unique ID library - headers and static librar
ron@jpax-
python3:
Installed: 3.5.1-3
Candidate: 3.5.1-3
Version table:
*** 3.5.1-3 500
500 http://
100 /var/lib/
python3-minimal:
Installed: 3.7.3-1
Candidate: 3.7.3-1
Version table:
*** 3.7.3-1 100
100 /var/lib/
3.5.1-3 500
500 http://
libglib2.0-bin:
Installed: 2.60.0-1
Candidate: 2.60.0-1
Version table:
*** 2.60.0-1 100
100 /var/lib/
2.
500 http://
500 http://
2.
500 http://
libglib2.0-0:
Installed: 2.48.2-0ubuntu4.4
Candidate: 2.48.2-0ubuntu4.4
Version table:
*** 2.48.2-0ubuntu4.4 500
500 http://
500 http://
100 /var/lib/
2.
500 http://
Yes, I realize that I somehow got other packages onto my system butI'm not sure how to resolve this mess. Hence I appreciate any help I might receive in these regards!
Thanks a lot!
Revision history for this message
|
#3 |
From your output:
$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
I do not really know what you have done, but it seems that your system has already (at least partly) been upgraded to Ubuntu 19.04 (Disco)!
If you do not have a specific requirement that your system stays on Ubuntu 16.04 (xenial), then I would like to suggest to try completing the release-upgrade to 19.04
If you want to do that, I recommend the following test for a try-run:
1. replace "xenial" by "disco" in /etc/apt/
2. run "sudo apt update"
3. run "apt --simulate install -f" -> the questions if that would work or fail
To revert that you must replace "disco" by "xenial" in sources.list again and run another "sudo apt update"
Revision history for this message
|
#4 |
yeah I'm seeing the output of lsb_release too. I have tried do-release-upgrade already but it wouldn't complete and hence ended up somewhere half way in the middle. I have no requirement to keep it on 12.04 hence, let's see:
I copied replaced xenial by disco in my sources.list:
sudo apt update
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
Get:6 http://
Get:7 http://
Get:8 http://
Get:9 http://
Get:10 http://
Get:11 http://
Get:12 http://
Get:13 http://
Get:14 http://
Get:15 http://
Get:16 http://
Get:17 http://
Get:18 http://
Get:19 http://
Get:20 http://
Get:21 http://
Get:22 http://
Get:23 http://
Get:24 http://
Get:25 http://
Get:26 http://
Get:27 http://
Get:28 http://
Get:29 http://
Get:30 http://
Get:31 http://
Get:32 http://
Get:33 http://
Get:34 http://
Get:35 http://
Get:36 http://
Get:37 http://
Get:38 http://
Get:39 http://
Get:40 http://
Get:41 http://
Get:42 http://
Get:43 http://
Get:44 http://
Get:45 http://
Get:46 http://
Get:47 http://
Get:48 http://
Get:49 http://
Get:50 http://
Get:51 http://
Get:52 http://
Get:53 http://
Get:54 http://
Get:55 http://
Get:56 http://
Get:57 http://
Get:58 http://
Get:59 http://
Get:60 http://
Get:61 http://
Get:62 http://
Get:63 http://
Get:64 http://
Get:65 http://
Get:66 http://
Get:67 http://
Get:68 http://
Get:69 http://
Get:70 http://
Get:71 http://
Get:72 http://
Get:73 http://
Get:74 http://
Get:75 http://
Get:76 http://
Fetched 57.9 MB in 1min 55s (505 kB/s)
(appstreamcli:
(appstreamcli:
AppStream cache update completed, but some metadata was ignored due to errors.
Reading package lists... Done
Building dependency tree
Reading state information... Done
2482 packages can be upgraded. Run 'apt list --upgradable' to see them.
$ sudo apt --simulate install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
apt-xapian-index : Depends: python3-xapian (>= 1.4.3-1)
cmake : Depends: cmake-data (= 3.5.1-1ubuntu3) but 3.13.4-1 is installed
libcairo2-dev:i386 : Depends: libfontconfig1-
libglib2.0-bin : Depends: libglib2.0-0 (= 2.60.0-1) but 2.48.2-0ubuntu4.4 is installed
libglib2.
python3 : PreDepends: python3-minimal (= 3.5.1-3) but 3.7.3-1 is installed
Depends: libpython3-stdlib (= 3.5.1-3) but 3.7.3-1 is installed
python3-apt : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-brlapi : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-dev : Depends: python3 (= 3.7.3-1) but 3.5.1-3 is installed
python3-distutils : Depends: python3 (>= 3.7.1-1~) but 3.5.1-3 is installed
python3-lib2to3 : Depends: python3 (>= 3.7.1-1~) but 3.5.1-3 is installed
python3-
python3-lxml : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-pil : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
testdrive-common : Depends: qemu-kvm or
virtualbox-
E: Error, pkgProblemResol
E: Unable to correct dependencies
Revision history for this message
|
#5 |
Ok. Apparently you have only a low number of packages already on "disco" level, and even when trying to use the repositories for disco, there are still similar broken dependencies.
It is necessary to get the broken dependencies (especially those with python3) solved. Without that a package installation or update is possible neither in xenial nor disco. Due to the fact that there seem more packages still on "xenial" level, I suggest to try the repair on "xenial".
If you want, these could be the next steps:
1. Change back from "disco" to "xenial" in /etc/apt/
2. Issue the command
sudo dpkg --remove virtualbox-ext-pack testdrive-common libcairo2-dev cmake apt-xapian-index
to remove some of the packages with broken dependencies. These packages should not be needed in the next steps and can be reinstalled when everything is fine again. Please report the results.
After that issue the command
sudo apt --simulate install -f
and show the output, it will hopefully be shorter.
3. Copy/paste the output of the commands
dpkg -l | grep 3.7.3-1
dpkg -l | grep 3.5.1-3
This should list the python3 packages in the different versions.
Based on that output it should be possible to identify the packages that have to be downgraded.
4. The same for the glib package
dpkg -l | grep 2.60.0-1
dpkg -l | grep 2.48.2-0ubu
Revision history for this message
|
#6 |
Okay,copied my old sources. list back into it's original position (xenial)
ran apt update
$ sudo dpkg --remove virtualbox-ext-pack testdrive-common libcairo2-dev cmake apt-xapian-index
(Reading database ... 367144 files and directories currently installed.)
Removing virtualbox-ext-pack (5.1.38-
/var/lib/
dpkg: error processing package virtualbox-ext-pack (--remove):
subprocess installed pre-removal script returned error exit status 127
dpkg: dependency problems prevent removal of testdrive-common:
testdrive-cli depends on testdrive-common (= 3.27-0ubuntu1).
dpkg: error processing package testdrive-common (--remove):
dependency problems - not removing
Removing libcairo2-dev:i386 (1.14.6-1) ...
Removing cmake (3.5.1-1ubuntu3) ...
dpkg: dependency problems prevent removal of apt-xapian-index:
libqapt3 depends on apt-xapian-index.
dpkg: error processing package apt-xapian-index (--remove):
dependency problems - not removing
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
virtualbox-
testdrive-common
apt-xapian-index
$ sudo apt --simulate install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
apt-xapian-index : Depends: python3-xapian (>= 1.4.3-1)
libglib2.0-bin : Depends: libglib2.0-0 (= 2.60.0-1) but 2.48.2-0ubuntu4.4 is installed
libglib2.
python3 : PreDepends: python3-minimal (= 3.5.1-3) but 3.7.3-1 is installed
Depends: libpython3-stdlib (= 3.5.1-3) but 3.7.3-1 is installed
python3-apt : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-brlapi : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-dev : Depends: python3 (= 3.7.3-1) but 3.5.1-3 is installed
python3-distutils : Depends: python3 (>= 3.7.1-1~) but 3.5.1-3 is installed
python3-lib2to3 : Depends: python3 (>= 3.7.1-1~) but 3.5.1-3 is installed
python3-
python3-lxml : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-pil : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
testdrive-common : Depends: qemu-kvm or
virtualbox-
E: Error, pkgProblemResol
E: Unable to correct dependencies
I then also went ahead and tried the following:
$ sudo dpkg --remove virtualbox-ext-pack
(Reading database ... 367089 files and directories currently installed.)
Removing virtualbox-ext-pack (5.1.38-
/var/lib/
dpkg: error processing package virtualbox-ext-pack (--remove):
subprocess installed pre-removal script returned error exit status 127
Errors were encountered while processing:
virtualbox-
ron@jpax-
dpkg: dependency problems prevent removal of testdrive-common:
testdrive-cli depends on testdrive-common (= 3.27-0ubuntu1).
dpkg: error processing package testdrive-common (--remove):
dependency problems - not removing
Errors were encountered while processing:
testdrive-common
ron@jpax-
(Reading database ... 367089 files and directories currently installed.)
Removing testdrive-cli (3.27-0ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
ron@jpax-
(Reading database ... 367084 files and directories currently installed.)
Removing testdrive-common (3.27-0ubuntu1) ...
ron@jpax-
dpkg: warning: ignoring request to remove libcairo2-dev which isn't installed
ron@jpax-
dpkg: warning: ignoring request to remove cmake, only the config
files of which are on the system; use --purge to remove them too
can I safey run sudo dpkg --purge cmake ?
ron@jpax-
dpkg: dependency problems prevent removal of apt-xapian-index:
libqapt3 depends on apt-xapian-index.
dpkg: error processing package apt-xapian-index (--remove):
dependency problems - not removing
Errors were encountered while processing:
apt-xapian-index
Revision history for this message
|
#7 |
Well done, some broken packages have been cleared.
Nevertheless the core problem with python3-* is open.
I still recommend to clean up the other packages as far as possible:
issue the command
sudo gedit /var/lib/
in the editor that opens put a comment indicator (#) in front of lines 4 and 5 (those starting with vboxmanage), save the file and close the editor.
then re-run
sudo dpkg --remove virtualbox-ext-pack
And finally (copied from above):
After that issue the command
sudo apt --simulate install -f
and show the output, it will hopefully be shorter.
3. Copy/paste the output of the commands
dpkg -l | grep 3.7.3-1
dpkg -l | grep 3.5.1-3
This should list the python3 packages in the different versions.
Based on that output it should be possible to identify the packages that have to be downgraded.
4. The same for the glib package
dpkg -l | grep 2.60.0-1
dpkg -l | grep 2.48.2-0ubu
Revision history for this message
|
#8 |
Okay yes,
looks like we're getting somewhere now
sudo apt --simulate instal -f actually spit out a really long list of packets that started with:
$ sudo apt --simulate install -f | less
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
cabextract cmake-data cpu-checker dwz gcc-5-base:i386 gir1.2-click-0.4
gir1.
gir1.
libcairo-
libcomerr2:i386 libexpat1-dev:i386 libffi-dev:i386 libfreetype6-
libgireposito
libjs-sphinxdoc liblzo2-2:i386 libmount1:i386 libmspack0 liborbit-2-0
libpixman-
libpython3.5-dev libpython3.7 libpython3.7-dev libsdl1.2debian
libsm-dev:i386 libsnapd-glib1 libvncserver1 libwebp6 libwebpdemux2
libwebpmux3 libxapian-1.3-5 libxcb-
libxrender-
python-apt python-sip-dev python-xdg python3.5-dev python3.7-dev sip-dev
uuid-dev:i386 x11proto-render-dev zsync
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
dleyna-server gnome-control-
gnome-icon-theme gnome-icon-
gnome-
libdleyna-
libgoa-
realmd
Suggested packages:
python-sip-doc
Recommended packages:
ibus system-
The following packages will be REMOVED:
aisleriot apparmor apparmor-easyprof apparmor-
apport-gtk apport-kde apt-xapian-index aptdaemon apturl apturl-common
apturl-kde click click-apparmor command-not-found compiz compiz-gnome
dh-python firefox foomatic-
gnome-menus gnome-orca gnome-software gnome-terminal gstreamer-qapt hplip
hplip-data ibus ibus-table kubuntu-
kubuntu-
libglib2.0-bin libgnome-2-0 libgnome2-common libgnomevfs2-0
libgnomevfs2-
lsb-release nautilus-share onboard onboard-data openprinting-ppds
plainbox-
...
...
...
The following NEW packages will be installed:
dleyna-server gnome-control-
gnome-icon-theme gnome-icon-
so I guess to clean it up I need to do an "autoremove" first
$ dpkg -l | grep 3.7.3-1
ii libpython3-
ii libpython3-
iU python3-dev 3.7.3-1 amd64 header files and a static library for Python (default)
iU python3-distutils 3.7.3-1ubuntu1 all distutils package for Python 3.x
iU python3-lib2to3 3.7.3-1ubuntu1 all Interactive high-level object-oriented language (2to3, version 3.6)
ii python3-minimal 3.7.3-1 amd64 minimal subset of the Python language (default python3 version)
$ dpkg -l | grep 3.5.1-3
ii python3 3.5.1-3 amd64 interactive high-level object-oriented language (default python3 version)
$ dpkg -l | grep 2.60.0-1
iU libglib2.0-bin 2.60.0-1 amd64 Programs for the GLib library
$ dpkg -l | grep 2.48.2-0ubu
ii libglib2.0-0:amd64 2.48.2-0ubuntu4.4 amd64 GLib library of C routines
ii libglib2.0-0:i386 2.48.2-0ubuntu4.4 i386 GLib library of C routines
ii libglib2.0-data 2.48.2-0ubuntu4.4 all Common files for GLib library
ii libglib2.0-dev:i386 2.48.2-0ubuntu4.4 i386 Development files for the GLib library
r
Revision history for this message
|
#9 |
Ok, the output of "apt install -f" is not too good, because as a solution for your problem the package management wants to uninstall lots of packages. I cannot imagine that this is what you want.
My suggestion to downgrade the python and glib packages to the correct version:
sudo dpkg --remove python3-dev
sudo dpkg --remove python3-distutils
sudo dpkg --remove python3-lib2to3
cd ~
mkdir tempwork
cd tempwork
wget https:/
wget https:/
wget https:/
wget https:/
sudo dpkg --force-downgrade --install *.deb
Maybe you should stop at the first error message (depending on its severity) and report the results that I can re-check my assumptions.
Maybe the dpkg command needs also --force-depends as additional option.
Revision history for this message
|
#10 |
Hm, I got an error from the get go:
$ sudo dpkg --remove python3-dev
[sudo] password for ron:
dpkg: dependency problems prevent removal of python3-dev:
python3-sip-dev depends on python3-dev.
dpkg: error processing package python3-dev (--remove):
dependency problems - not removing
Errors were encountered while processing:
python3-dev
I'm unsure if you wanted me to try:
sudo dpkg --remove --force python3-dev
instead but better safe than sorry.... so I just report the result...
Thanks Manfred for sticking with me until here and helping me out! Your assistance is greatly appreciated!
Revision history for this message
|
#11 |
You better wait with forcing, there should be other ways.
Try
sudo dpkg --remove python3-sip-dev python3-dev
and report the results.
Revision history for this message
|
#12 |
This gave me the following:
$ sudo dpkg --remove python3-sip-dev python3-dev
[sudo] password for ron:
dpkg: dependency problems prevent removal of python3-sip-dev:
pyqt5-dev depends on python3-sip-dev | python-sip-dev; however:
Package python3-sip-dev is to be removed.
Package python-sip-dev is not installed.
dpkg: error processing package python3-sip-dev (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of python3-dev:
python3-sip-dev depends on python3-dev.
dpkg: error processing package python3-dev (--remove):
dependency problems - not removing
Errors were encountered while processing:
python3-sip-dev
python3-dev
I'm confused, it first says " Package python3-sip-dev is to be removed." but then it still cannot remove it due to dependency problems with python3-dev ...hmm....
Revision history for this message
|
#13 |
The error message is a bit confusing, but correct - don't mix up python3-sip-dev and python-sip-dev.
General remark: the *-dev packages usually are optional and only needed when compliling software.
My current aim is removing all broken packages except important ones (python, glib).
Try
sudo dpkg --remove pyqt5-dev python3-sip-dev python3-dev
If this fails because of another dependency on a *-dev package, add this one as well, etc.
Revision history for this message
|
#14 |
Great,
This worked fine:
$ sudo dpkg --remove pyqt5-dev python3-sip-dev python3-dev
[sudo] password for ron:
(Reading database ... 367065 files and directories currently installed.)
Removing pyqt5-dev (5.5.1+
Removing python3-sip-dev (4.17+dfsg-1build1) ...
Removing python3-dev (3.7.3-1) ...
Processing triggers for man-db (2.7.5-1) ...
Revision history for this message
|
#15 |
Ok, the first packages with broken dependencies have been cleared (by removing them).
Now continue with
sudo dpkg --remove python3-distutils
sudo dpkg --remove python3-lib2to3
cd ~
mkdir tempwork
cd tempwork
wget https:/
wget https:/
wget https:/
wget https:/
sudo dpkg --force-downgrade --install *.deb
(Again: you probably better stop when you get an error message)
Revision history for this message
|
#16 |
Hi,
Okay, I gpt the following:
$ ls -l
total 80
-rw-rw-r-- 1 ron ron 39510 Aug 5 09:41 libglib2.
-rw-rw-r-- 1 ron ron 6868 Mar 23 2016 libpython3-
-rw-rw-r-- 1 ron ron 6818 Mar 23 2016 libpython3-
-rw-rw-r-- 1 ron ron 23300 Mar 23 2016 python3-
ron@jpax-
[sudo] password for ron:
dpkg: warning: downgrading libglib2.0-bin from 2.60.0-1 to 2.48.2-0ubuntu4.4
(Reading database ... 365988 files and directories currently installed.)
Preparing to unpack libglib2.
Unpacking libglib2.0-bin (2.48.2-0ubuntu4.4) over (2.60.0-1) ...
Selecting previously unselected package libpython3-
Preparing to unpack libpython3-
Unpacking libpython3-
dpkg: warning: downgrading libpython3-
Preparing to unpack libpython3-
Unpacking libpython3-
dpkg: warning: downgrading python3-minimal from 3.7.3-1 to 3.5.1-3
Preparing to unpack python3-
Unpacking python3-minimal (3.5.1-3) over (3.7.3-1) ...
Setting up libglib2.0-bin (2.48.2-0ubuntu4.4) ...
dpkg: dependency problems prevent configuration of libpython3-
libpython3-
Package libpython3.5-dbg is not installed.
dpkg: error processing package libpython3-
dependency problems - leaving unconfigured
Setting up libpython3-
Setting up python3-minimal (3.5.1-3) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
libpython3-
Revision history for this message
|
#17 |
This looks already quite good, but - sorry - I made an error and copied a wrong address (libpython3-dbg instead of libpython3-doc).
Now let's see what the output is of the following commands:
sudo dpkg --audit
sudo dpkg --configure -a
sudo dpkg --audit
apt --simulate install -f
Revision history for this message
|
#18 |
k$ sudo dpkg --audit
[sudo] password for ron:
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
apt-xapian-index maintenance and search tools for a Xapian index of Debian
cmake-data CMake data files (modules, templates and documentation)
dwz DWARF compression tool
libcomerr2:i386 transitional package
libffi-dev:i386 Foreign Function Interface library (development files)
libpsl5:amd64 Library for Public Suffix List (shared libraries)
libpython3-
python3-apt Python 3 interface to libapt-pkg
python3-
python3-
python3-lxml:amd64 pythonic binding for the libxml2 and libxslt libraries
python3-pil:amd64 Python Imaging Library (Python3)
uuid-dev:i386 Universally Unique ID library - headers and static librar
$ sudo dpkg --configure -a
dpkg: dependency problems prevent configuration of python3-pil:amd64:
python3-pil:amd64 depends on python3 (>= 3.7~); however:
Version of python3 on system is 3.5.1-3.
dpkg: error processing package python3-pil:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3-apt:
python3-apt depends on python3 (>= 3.7~); however:
Version of python3 on system is 3.5.1-3.
dpkg: error processing package python3-apt (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3-lxml:amd64:
python3-lxml:amd64 depends on python3 (>= 3.7~); however:
Version of python3 on system is 3.5.1-3.
dpkg: error processing package python3-lxml:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3-
python3-
Version of python3 on system is 3.5.1-3.
dpkg: error processing package python3-
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python3-
python3-
Version of python3 on system is 3.5.1-3.
dpkg: error processing package python3-libapparmor (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpython3-
libpython3-
Package libpython3.5-dbg is not installed.
dpkg: error processing package libpython3-
dependency problems - leaving unconfigured
Errors were encountered while processing:
python3-pil:amd64
python3-apt
python3-lxml:amd64
python3-
python3-
libpython3-
ron@jpax-
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
apt-xapian-index maintenance and search tools for a Xapian index of Debian
cmake-data CMake data files (modules, templates and documentation)
dwz DWARF compression tool
libcomerr2:i386 transitional package
libffi-dev:i386 Foreign Function Interface library (development files)
libpsl5:amd64 Library for Public Suffix List (shared libraries)
libpython3-
python3-apt Python 3 interface to libapt-pkg
python3-
python3-
python3-lxml:amd64 pythonic binding for the libxml2 and libxslt libraries
python3-pil:amd64 Python Imaging Library (Python3)
uuid-dev:i386 Universally Unique ID library - headers and static librar
$ sudo apt --simulate install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
apt-xapian-index : Depends: python3-xapian (>= 1.4.3-1)
libpython3-dbg : Depends: libpython3.5-dbg (>= 3.5.1-2~) but it is not installed
python3-apt : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-brlapi : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-
python3-lxml : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
python3-pil : Depends: python3 (>= 3.7~) but 3.5.1-3 is installed
E: Error, pkgProblemResol
E: Unable to correct dependencies
ron@jpax-
Revision history for this message
|
#19 |
It is going forward.
What is now the output of
sudo dpkg --remove libpython3-dbg
apt-cache policy apt-xapian-index python3-apt python3-brlapi python3-libapparmor python3-lxml python3-pil
Revision history for this message
|
#20 |
Yes, starts to feel good again! Thank you very much, I much appreciate your patience here!
$ sudo dpkg --remove libpython3-dbg
[sudo] password for ron:
(Reading database ... 365994 files and directories currently installed.)
Removing libpython3-
Processing triggers for man-db (2.7.5-1) ...
$ apt-cache policy apt-xapian-index python3-apt python3-brlapi python3-libapparmor python3-lxml
apt-xapian-index:
Installed: 0.47ubuntu13
Candidate: 0.47ubuntu13
Version table:
*** 0.47ubuntu13 100
100 /var/lib/
0.47ubuntu8.4 500
500 http://
500 http://
0.47ubuntu8 500
500 http://
500 http://
python3-apt:
Installed: 1.8.4
Candidate: 1.8.4
Version table:
*** 1.8.4 100
100 /var/lib/
1.
500 http://
1.
500 http://
python3-brlapi:
Installed: 5.6-10ubuntu1
Candidate: 5.6-10ubuntu1
Version table:
*** 5.6-10ubuntu1 100
100 /var/lib/
5.
500 http://
5.3.1-2ubuntu2 500
500 http://
python3-
Installed: 2.13.2-9ubuntu6
Candidate: 2.13.2-9ubuntu6
Version table:
*** 2.13.2-9ubuntu6 100
100 /var/lib/
2.
500 http://
500 http://
2.
500 http://
python3-lxml:
Installed: 4.3.3-1
Candidate: 4.3.3-1
Version table:
*** 4.3.3-1 100
100 /var/lib/
3.
500 http://
500 http://
3.5.0-1build1 500
500 http://
What does this now mean?
500 means installable, and it shows for each of these packages....
I've got to go carefully back through the whole process to understand what you had me doing throughout the whole process - then next time, should this happen again, I can fix it by myself...! (maybe)
Revision history for this message
|
#21 |
The numbers in apt cache show the priority. The version with the highest number is installed, unless there is a downgrade required.
Try the following command
apt --simulate install -f apt-xapian-
Note, this is one long command spanning two or three lines. Copy/paste the whole command at once.
Revision history for this message
|
#22 |
$ sudo apt --simulate install -f apt-xapian-
[sudo] password for ron:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '' for 'python3-brlapi' was not found
E: Unable to locate package 5.3.1-2ubuntu2.1
E: Couldn't find any package by glob '5.3.1-2ubuntu2.1'
E: Couldn't find any package by regex '5.3.1-2ubuntu2.1'
Revision history for this message
|
#23 |
Sorry, my fault, there is an extra space character where it shouldn't be.
Try again with
apt --simulate install -f apt-xapian-
Revision history for this message
|
#24 |
Okay, now I got this:
$ sudo apt --simulate install -f apt-xapian-
[sudo] password for ron:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '' for 'python3-brlapi' was not found
E: Unable to locate package 5.3.1-2ubuntu2.1
E: Couldn't find any package by glob '5.3.1-2ubuntu2.1'
E: Couldn't find any package by regex '5.3.1-2ubuntu2.1'
ron@jpax-
ron@jpax-
ron@jpax-
[sudo] password for ron:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
cmake-data cpu-checker dwz gcc-5-base:i386 gir1.2-
libffi-dev:i386 libfreetype6-
libpython3.7-dev libpython3.
msr-tools python-xdg python3.5-dev python3.7 python3.7-dev python3.7-minimal sip-dev uuid-dev:i386 x11proto-render-dev zsync
Use 'sudo apt autoremove' to remove them.
Suggested packages:
python3-apt-dbg python-apt-doc python3-lxml-dbg python-lxml-doc python-pil-doc python3-pil-dbg
The following packages will be DOWNGRADED:
apt-xapian-index python3-apt python3-brlapi python3-libapparmor python3-lxml python3-pil
0 upgraded, 0 newly installed, 6 downgraded, 0 to remove and 56 not upgraded.
12 not fully installed or removed.
Inst python3-apt [1.8.4] (1.1.0~
Inst apt-xapian-index [0.47ubuntu13] (0.47ubuntu8.4 Ubuntu:
Inst python3-lxml [4.3.3-1] (3.5.0-1ubuntu0.1 Ubuntu:
Inst python3-pil [5.4.1-1] (3.1.2-0ubuntu1.1 Ubuntu:
Inst python3-brlapi [5.6-10ubuntu1] (5.3.1-2ubuntu2.1 Ubuntu:
Inst python3-libapparmor [2.13.2-9ubuntu6] (2.10.95-
Conf python3-apt (1.1.0~
Conf apt-xapian-index (0.47ubuntu8.4 Ubuntu:
Conf python3-lxml (3.5.0-1ubuntu0.1 Ubuntu:
Conf python3-pil (3.1.2-0ubuntu1.1 Ubuntu:
Conf python3-brlapi (5.3.1-2ubuntu2.1 Ubuntu:
Conf python3-libapparmor (2.10.95-
Conf libcomerr2:i386 (1.44.6-1 [i386])
Conf libpsl5 (0.20.2-2 [amd64])
Conf libffi-dev:i386 (3.2.1-9 [i386])
Conf dwz (0.12-3 [amd64])
Conf cmake-data (3.13.4-1 [all])
Conf uuid-dev:i386 (2.33.1-0.1ubuntu2 [i386])
Revision history for this message
|
#25 |
The simulation does not show any error any more, now try the real execution:
sudo apt install -f apt-xapian-
Revision history for this message
|
#26 |
$ sudo apt install -f apt-xapian-
[sudo] password for ron:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
cmake-data cpu-checker dwz gcc-5-base:i386 gir1.2-
libffi-dev:i386 libfreetype6-
libpython3.7-dev libpython3.
msr-tools python-xdg python3.5-dev python3.7 python3.7-dev python3.7-minimal sip-dev uuid-dev:i386 x11proto-render-dev zsync
Use 'sudo apt autoremove' to remove them.
Suggested packages:
python3-apt-dbg python-apt-doc python3-lxml-dbg python-lxml-doc python-pil-doc python3-pil-dbg
The following packages will be DOWNGRADED:
apt-xapian-index python3-apt python3-brlapi python3-libapparmor python3-lxml python3-pil
0 upgraded, 0 newly installed, 6 downgraded, 0 to remove and 56 not upgraded.
12 not fully installed or removed.
Need to get 1,396 kB of archives.
After this operation, 1,499 kB disk space will be freed.
Do you want to continue? [Y/n]
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
Get:6 http://
Fetched 1,396 kB in 8s (186 kB/s)
dpkg: warning: downgrading python3-apt from 1.8.4 to 1.1.0~beta1ubun
(Reading database ... 365988 files and directories currently installed.)
Preparing to unpack .../python3-
Unpacking python3-apt (1.1.0~
dpkg: warning: downgrading apt-xapian-index from 0.47ubuntu13 to 0.47ubuntu8.4
Preparing to unpack .../apt-
Unpacking apt-xapian-index (0.47ubuntu8.4) over (0.47ubuntu13) ...
dpkg: warning: downgrading python3-lxml:amd64 from 4.3.3-1 to 3.5.0-1ubuntu0.1
Preparing to unpack .../python3-
Unpacking python3-lxml (3.5.0-1ubuntu0.1) over (4.3.3-1) ...
dpkg: warning: downgrading python3-pil:amd64 from 5.4.1-1 to 3.1.2-0ubuntu1.1
Preparing to unpack .../python3-
Unpacking python3-pil:amd64 (3.1.2-0ubuntu1.1) over (5.4.1-1) ...
dpkg: warning: downgrading python3-
Preparing to unpack .../python3-
Unpacking python3-brlapi (5.3.1-2ubuntu2.1) over (5.6-10ubuntu1) ...
dpkg: warning: downgrading python3-libapparmor from 2.13.2-9ubuntu6 to 2.10.95-0ubuntu2.11
Preparing to unpack .../python3-
Unpacking python3-libapparmor (2.10.95-
Setting up python3-pil:amd64 (3.1.2-0ubuntu1.1) ...
Setting up python3-apt (1.1.0~
Setting up python3-lxml (3.5.0-1ubuntu0.1) ...
Setting up python3-brlapi (5.3.1-2ubuntu2.1) ...
Setting up python3-libapparmor (2.10.95-
Setting up libpsl5:amd64 (0.20.2-2) ...
Setting up uuid-dev:i386 (2.33.1-0.1ubuntu2) ...
Setting up apt-xapian-index (0.47ubuntu8.4) ...
Setting up libffi-dev:i386 (3.2.1-9) ...
Setting up cmake-data (3.13.4-1) ...
Setting up dwz (0.12-3) ...
Setting up libcomerr2:i386 (1.44.6-1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.4) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
This worked like a charm! So I'm now ready to do
apt update;
Thank you very much Manfred!
Revision history for this message
|
#27 |
Yes! the package management seems to be in a consistent status again. "apt" commands should work.
Nevertheless, you have to be aware that there might still be some packages from the wrong distribution that might interfere with installation of packages for your current release.
And I assume that your system believes that it is already on 19.04 level (see lsb_release -crid). This may cause problems when trying to do a release upgrade to e.g. 18.04
I suggest that you do some consistency checks before you start big package management activities:
What is now the output of
uname -a
lsb_release -crid
apt list --upgradable
ubuntu-
ubuntu-
(if it says command not found for ubuntu-
Revision history for this message
|
#28 |
$ uname -a
Linux jpax-build07 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ron@jpax-
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
ron@jpax-
[sudo] password for ron:
Listing... Done
bind9-host/
dnsutils/
file-roller/
firefox-
firefox/
fonts-opensymbo
gir1.2-
ibus-gtk3/
ibus-gtk/
ibus/xenial-
libbind9-
libdns-
libdns162/
libfdisk1/
libibus-
libisc-
libisc160/
libisccc140/
libisccfg140/
libldap-
libldap2-
liblwres141/
libreoffice-
libreoffice-
libreoffice-
libreoffice-
libreoffice-
libruby2.
libsmartcols1/
libsnapd-
libsnmp-
libsnmp30/
libwireshark-
libwireshark11/
libwiretap8/
libwscodecs2/
libwsutil9/
linux-generic-
linux-headers-
linux-image-
linux-libc-
linux-libc-
mount/xenial-
psmisc/
ruby2.3/
snapd/xenial-
ubuntu-
uno-libs3/
ure/xenial-
util-linux/
uuid-runtime/
wireshark-
wireshark-
wireshark-
wireshark/
wpasupplicant/
I should be able to upgrade all these with no further issues, right? But why do they come from xenial-updates while it thinks it's on disco? Is this because my sources.list points to xenial? Should I change that to disco now?
Revision history for this message
|
#29 |
The available packages come from the repositories listed in the sources.list. The output og lsb_release is not taken into account there.
I advise against changing the sources.list from xenial to dingo, but to try a regular release upgrade.
Can you please provide the output of
ubuntu-
ubuntu-
Revision history for this message
|
#30 |
Sorry, I missed these two before... here we go:
$ ubuntu-
Support status summary of 'jpax-build07':
You have 29 packages (0.9%) supported until April 2024 (Community - 5y)
You have 18 packages (0.6%) supported until January 2020 (Community - 9m)
You have 2141 packages (68.0%) supported until April 2024 (Canonical - 5y)
You have 531 packages (16.9%) supported until April 2022 (Community - 3y)
You have 195 packages (6.2%) that can not/no longer be downloaded
You have 235 packages (7.5%) that are unsupported
Run with --show-unsupported, --show-supported or --show-all to see more details
ron@jpax-
Support status summary of 'jpax-build07':
You have 2141 packages (68.0%) supported until April 2024 (Canonical - 5y)
You have 29 packages (0.9%) supported until April 2024 (Community - 5y)
You have 531 packages (16.9%) supported until April 2022 (Community - 3y)
You have 18 packages (0.6%) supported until January 2020 (Community - 9m)
You have 195 packages (6.2%) that can not/no longer be downloaded
You have 235 packages (7.5%) that are unsupported
No longer downloadable:
apt apt-transport-https apt-utils aptitude aptitude-common autopoint
base-files bash bsdmainutils bsdutils cmake-data containerd.io
coreutils cpu-checker debianutils dh-python dkms docker-ce
docker-ce-cli dwz fontconfig-config gcc-9-base gcc-9-base:i386
gettext gpgv libapt-inst2.0 libapt-pkg5.0 libasprintf-dev
libasprintf0v5 libblkid1 libblkid1:i386 libboost-
libbsd0 libbsd0:i386 libc-bin libc-dev-bin libc6 libc6-dbg libc6-dev
libc6-dev-i386 libc6-dev-x32 libc6-dev:i386 libc6-i386 libc6-x32
libc6:i386 libcom-err2 libcom-err2:i386 libcomerr2 libcomerr2:i386
libcwidget3v5 libdb5.3 libepoxy0 libffi-dev libffi-dev:i386 libffi6
libffi6:i386 libfontconfig1 libfontconfig1:i386 libfreetype6
libfreetype6-
libgcrypt20 libgcrypt20-dev libgcrypt20:i386 libgettextpo-dev
libgettextpo0 libgnutls-openssl27 libgnutls30 libgnutls30:i386
libgpg-error-dev libgpg-error-l10n libgpg-error0 libgpg-error0:i386
libgssapi-krb5-2 libgssapi-
libidn2-0 libidn2-0:i386 libimagequant0 libk5crypto3
libk5crypto3:i386 libkrb5-3 libkrb5-3:i386 libkrb5support0
libkrb5support0
libncursesw6 libnettle6 libnettle6:i386 libnghttp2-14
libobasis6.0-base libobasis6.0-calc libobasis6.0-core
libobasis6.0-draw libobasis6.0-en-us
libobasis6.
libobasis6.
libobasis6.
libobasis6.
libobasis6.
libobasis6.
libobasis6.0-images libobasis6.
libobasis6.
libobasis6.
libobasis6.
libobasis6.
libobasis6.0-writer libobasis6.
libp11-kit0:i386 libpng16-16 libpng16-16:i386 libpsl5 libpython3-dev
libpython3.7 libpython3.7-dev libpython3.
libpython3.7-stdlib libreadline8 libreoffice6.0 libreoffice6.0-base
libreoffice6.0-calc libreoffice6.
libreoffice6.
libreoffice6.0-draw libreoffice6.
libreoffice6.0-math libreoffice6.0-ure libreoffice6.
libsdl1.2debian libselinux1 libselinux1:i386 libsigc++-2.0-0v5
libsqlite3-0 libsqlite3-0:i386 libssl1.1 libssl1.1:i386 libstdc++6
libstdc++6:i386 libtasn1-6 libtasn1-6:i386 libtinfo6 libunistring2
libunistring2:i386 libuuid1 libuuid1:i386 libvncserver1 libwebp6
libwebpdemux2 libwebpmux3 libxapian30 libzstd1 libzstd1:i386 locales
msr-tools p11-kit-modules python-apt python-apt-common
python-httplib2 python-xdg python3-asn1crypto python3-
python3-idna python3.7 python3.7-dev python3.7-minimal qemu uuid-dev
uuid-dev:i386 zlib1g zlib1g-dev zlib1g-dev:i386 zlib1g:i386 zsh
zsh-common zsync
Unsupported:
aglfn astyle aufs-tools autogen cabextract cgroupfs-mount clang
clang-3.8 colordiff cppcheck cppcheck-gui cscope debugedit dia
dia-common dia-libs dia-shapes dos2unix dsniff elinks elinks-data
gambas3-
gnuplot gnuplot-tex gnuplot5-data gnuplot5-qt gperf gsfonts-x11
haveged help2man htop inetutils-
jarwrapper java-wrappers kdesrc-build kdiff3 kdiff3-doc
libapache-pom-java libatk-wrapper-java libatk-
libautocomplete
libboost-all-dev libboost-atomic-dev libboost-chrono-dev
libboost-
libboost-
libboost-
libboost-
libboost-
libboost-graph-dev libboost-
libboost-
libboost-
libboost-
libboost-
libboost-log1.58.0 libboost-math-dev libboost-
libboost-math1.58.0 libboost-mpi-dev libboost-
libboost-
libboost-
libboost-
libboost-
libboost-
libboost-test-dev libboost-
libboost-timer-dev libboost-
libboost-tools-dev libboost-wave-dev libboost-
libboost-wave1.58.0 libbsf-java libcapture-
libclang-
libcommons-
libfop-java libfsplib0 libgnuinet-java libgnumail-java libgsoap8
libhavege1 libhwloc-dev libhwloc-plugins libhwloc5 libinotifytools0
libitext5-java libjavaparser-java libjlibeps-java libjline-java
libjsyntaxpane-java liblog4j1.2-java libmaxminddb0 libmsgpack3
libnids1.21 libopenmpi-dev libopenmpi1.10 librhino-java librpm3
librpmbuild3 librpmio3 librpmsign3 librsyntaxtexta
libsaxon-java libsvncpp3 libtext-
libtre5 libubuntu-
libuv1 libwireshark-data libwireshark11 libwiretap8 libwscodecs2
libwsutil9 libxmlgraphics-
meld mmv mpi-default-bin mpi-default-dev ncurses-hexedit nethogs
nodejs ofono openjdk-
openjdk-
putty-tools pyqt4-dev-tools pyqt5-dev-tools python-dulwich
python-fastimport python-gtkglext1 python-lz4 python-lzo
python-nautilus python-opengl python-pexpect python-pip
python-pip-whl python-ptyprocess python-rencode python-rpm
python-
python3-pluggy python3-py python3-virtualenv qt5-default
rabbitvcs-cli rabbitvcs-core rabbitvcs-gedit rabbitvcs-nautilus
rapidsvn rcs rhino rpm rpm-common rpm2cpio scons scsitools splint
splint-data ssh-askpass sshpass telepathy-ring texinfo tftp tlsdate
tmate tox ttf-mscorefonts
ubuntu-
virtualbox-
virtualbox-
wireshark-gtk wireshark-qt xfonts-100dpi xfonts-75dpi xpra xsel
yakuake yum
> but to try a regular release upgrade
is that the next step...?
Revision history for this message
|
#31 |
ok, my summary:
The package management system is back is a consistent state, but there are still some packages from disco installed. This should not do harm, but might interfere with installation of additional packages or a release upgrade. Eventually showing problems can probably be solved easily.
The question now is: What do you want to do with your system? Do you want to stay on Ubuntu xenial release, or do you want to upgrade (either to bionic or to disco)?
It is your decision.
By the way, have you already executed "sudo apt update" (or "sudo apt dist-upgrade", or the same with apt-get)?
This should be the proof that the package management is healthy and that updates work again.
Revision history for this message
|
#32 |
Okay, great!
Is I have tried apt update and even installed another package i required and that worked fine! Now as for going to bionic or disco, I would prefer bionic (due to LTS) but I'm wondering since you say "there are still some packages from disco installed" if it not might be lesser of a pain to go to disco instead of involving yet another version.
As for staying with Ubuntu: for the time being yes, I'm tied to it as there's some proprietary software that is cut ready to run on Ubuntu...
Revision history for this message
|
#33 |
Maybe a misunderstanding caused by the line break:
I did not ask whether you want to stay on Ubuntu (I took that for granted), but my intention was to ask if you want to stay on Ubuntu xenial.
For the possible version conflicts when installing additional packages:
I guess that the following may happen:
"libnelle6" is listed as "No longer downloadable".
I assume that you currently have libnettle6 from disco installed on your system.
If you now need to install nettle-dev, then you will probably receive the message that nettle-dev (from xenial) and the currently installed libnettle6 (from disco) do not fit together.
Solution probably would be to downgrade libnettle6 to the version from xenial.
To avoid these problems you probably should do the relase upgrade to disco, unless there is the need to stay on Ubuntu xenial.
Revision history for this message
|
#34 |
Thanks Manfred Hampl, that solved my question.
Revision history for this message
|
#35 |
HI Manfred,
I hadn't touched this anymore until now. If I do a do-release-upgrade i get No new release found presumable because it thinks it's on disco already:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
However, my repositories would still pointto xenial in /etc/apt/
when I change them from xenial to disco, run apt update , I get a huge list of packages that need to be updated.
Can I go ahead an run the disco updates now? I'm not sure - I ran the xenial updates previously and it would upgrade one or the other package.
vut now I want to install x2go server and wasn't sure If I should grab it for disco or xenial.... that's how I got here.
Thanks for your continued support and apologies for the premature believe that my problem was solved...
Ron
Revision history for this message
|
#36 |
I do not see what the relationship is between installing x2goserver and your problem. x2goserver is available for all current Ubuntu releases (for bionic and newer releases in the standard Ubuntu repositories, and for older releases including xenial it's available in a PPA).
My suggestion is the following:
Downgrade the package base-files to the version for xenial.
This should bring lsb_release to the correct status showing "xenial".
Then try a release upgrade to bionic.
For diagnostic purposes please provide the output that you currently receive for
uname -a
lsb_release -crid
apt-cache policy base-files
sudo apt-get update
sudo apt-get dist-upgrade
Revision history for this message
|
#37 |
For some reason I couldnot get x2goserver installed through the PPA but let's not worry about this for now.
This is what I have before the downgrade of base-files:
ron@jpax-build07:~$ uname -a
Linux jpax-build07 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ron@jpax-build07:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
ron@jpax-build07:~$ apt-cache policy base-files
base-files:
Installed: 10.1ubuntu9
Candidate: 10.1ubuntu9
Version table:
*** 10.1ubuntu9 100
100 /var/lib/
9.4ubuntu4.11 500
500 http://
9.4ubuntu4 500
500 http://
ron@jpax-build07:~$ sudo apt-get update
Hit:1 http://
Hit:2 http://
Hit:3 http://
Hit:4 http://
Reading package lists... Done
ron@jpax-build07:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ron@jpax-build07:~$
I then tried the following:
ron@jpax-build07:~$ sudo apt-get -t=xenial install base-files
Reading package lists... Done
Building dependency tree
Reading state information... Done
base-files is already the newest version (10.1ubuntu9).
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
ron@jpax-build07:~$ apt-cache showpkg base-files
Package: base-files
Versions:
10.1ubuntu9 (/var/lib/
Description Language:
Description Language:
Description Language: en_CA
Description Language: en
Description Language:
Description Language:
Description Language:
9.4ubuntu4.11 (/var/lib/
Description Language:
Description Language:
Description Language: en_CA
Description Language: en
Description Language:
Description Language:
Description Language:
9.4ubuntu4 (/var/lib/
Description Language:
Description Language:
Description Language: en_CA
Description Language: en
Description Language:
Description Language:
Description Language:
Reverse Depends:
rsync,base-files 4.0.1
bash,base-files 2.1.12
base-
rsync,base-files 4.0.1
dpkg-
bash,base-files 2.1.12
trn4,base-files 2.2.0
weechat-
speechd-
speechd-
s-nail,base-files 2.2.0
liblog4cxx-
kup-server,
base-
python-
libpam-
libnss-
dpkg-
dict-
bsd-mailx,
bash,base-files 2.1.12
Dependencies:
10.1ubuntu9 - awk (0 (null)) libc6 (2 2.3.4) initscripts (3 2.88dsf-13.3) initscripts:i386 (3 2.88dsf-13.3) sendfile (3 2.1b.20080616-5.2~) sendfile:i386 (3 2.1b.20080616-5.2~) base (0 (null)) dpkg (1 1.15.0) dpkg:i386 (1 1.15.0) miscutils (0 (null)) base-files:i386 (32 (null))
9.4ubuntu4.11 - awk (0 (null)) initscripts (3 2.88dsf-13.3) initscripts:i386 (3 2.88dsf-13.3) sendfile (3 2.1b.20080616-5.2~) sendfile:i386 (3 2.1b.20080616-5.2~) base (0 (null)) dpkg (1 1.15.0) dpkg:i386 (1 1.15.0) miscutils (0 (null)) base-files:i386 (32 (null))
9.4ubuntu4 - awk (0 (null)) initscripts (3 2.88dsf-13.3) sendfile (3 2.1b.20080616-5.2~) base (0 (null)) dpkg (1 1.15.0) miscutils (0 (null)) dpkg:i386 (1 1.15.0) base-files:i386 (32 (null)) initscripts:i386 (3 2.88dsf-13.3) sendfile:i386 (3 2.1b.20080616-5.2~)
Provides:
10.1ubuntu9 - base-files:i386 (= 10.1ubuntu9) base (= )
9.4ubuntu4.11 - base-files:i386 (= 9.4ubuntu4.11) base (= )
9.4ubuntu4 - base-files:i386 (= 9.4ubuntu4) base (= )
Reverse Provides:
base-files:i386 9.4ubuntu4.11 (= 9.4ubuntu4.11)
base-files:i386 9.4ubuntu4 (= 9.4ubuntu4)
ron@jpax-build07:~$
And as I wasn't so certain as to how to proceed with apt, I switched to aptitude and did the following:
ron@jpax-build07:~$ sudo aptitude versions base-files
Package base-files:
p 9.4ubuntu4 xenial 500
p 9.4ubuntu4.11 xenial-updates 500
i 10.1ubuntu9 100
ron@jpax-build07:~$ sudo aptitude install base-files=
The following packages will be DOWNGRADED:
base-files
0 packages upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Need to get 68.7 kB of archives. After unpacking 79.9 kB will be freed.
Get: 1 http://
Fetched 68.7 kB in 1s (78.6 kB/s)
dpkg: warning: downgrading base-files from 10.1ubuntu9 to 9.4ubuntu4
(Reading database ... 364532 files and directories currently installed.)
Preparing to unpack .../base-
Warning: Stopping motd-news.service, but it can still be activated by:
motd-news.timer
Unpacking base-files (9.4ubuntu4) over (10.1ubuntu9) ...
Setting up base-files (9.4ubuntu4) ...
Installing new version of config file /etc/debian_version ...
Installing new version of config file /etc/issue ...
Installing new version of config file /etc/issue.net ...
Installing new version of config file /etc/lsb-release ...
Installing new version of config file /etc/update-
Processing triggers for plymouth-
update-initramfs: deferring update (trigger activated)
Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for plymouth-
dpkg: warning: version '/etc/lsb-release' has bad syntax: version number does not start with digit
rmdir: failed to remove '/lib/plymouth/': No such file or directory
update-initramfs: deferring update (trigger activated)
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.16) ...
update-initramfs: Generating /boot/initrd.
/sbin/ldconfig.
/sbin/ldconfig.
/sbin/ldconfig.
/sbin/ldconfig.
Current status: 1 (+1) upgradable.
ron@jpax-build07:~$
and then I repeated the above commands
ron@jpax-build07:~$ uname -a
Linux jpax-build07 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ron@jpax-build07:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial
ron@jpax-build07:~$ apt-cache policy base-files
base-files:
Installed: 9.4ubuntu4
Candidate: 9.4ubuntu4.11
Version table:
9.4ubuntu4.11 500
500 http://
*** 9.4ubuntu4 500
500 http://
100 /var/lib/
ron@jpax-build07:~$ sudo apt-get update
Hit:1 http://
Hit:2 http://
Get:3 http://
Hit:4 http://
Fetched 109 kB in 2s (69.1 kB/s)
Reading package lists... Done
ron@jpax-build07:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
base-files
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 67.5 kB of archives.
After this operation, 14.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
ron@jpax-build07:~$
I didn't want to upgrade anything just yet though. Things look more in line now but I still get:
$ do-release-upgrade
Checking for a new Ubuntu release
No new release found.
ron@jpax-build07:~$
What else is missing? Is it just that I haven't called apt-get upgrade yet?
Thank you!
Revision history for this message
|
#38 |
As for installing x2go, IU tried:
ron@jpax-build07:~$ sudo apt-add-repository ppa:x2go/stable
Cannot add PPA: 'ppa:~x2go/
ERROR: '~x2go' user or team does not exist.
I searched and foudn that it maybe a proxy issue but I have configured the proxy settings in /etc/apt/apt.conf:
ron@jpax-build07:~$ cat /etc/apt/apt.conf
Acquire:
Acquire:
Acquire::ftp::proxy "ftp://10.
Acquire:
Revision history for this message
|
#39 |
I have also tried the following:
ron@jpax-build07:~$ sudo -E apt-add-repository ppa:x2go/stable
Cannot add PPA: 'ppa:~x2go/
ERROR: '~x2go' user or team does not exist.
ron@jpax-build07:~$ export HTTPS_PROXY=http://
ron@jpax-build07:~$ export HTTP_PROXY=http://
ron@jpax-build07:~$ export https_proxy=http://
ron@jpax-build07:~$ export http_proxy=http://
ron@jpax-build07:~$ sudo -E apt-add-repository ppa:x2go/stable
Cannot add PPA: 'ppa:~x2go/
ERROR: '~x2go' user or team does not exist.
ron@jpax-build07:~$ sudo apt-add-repository ppa:x2go/stable
Cannot add PPA: 'ppa:~x2go/
ERROR: '~x2go' user or team does not exist.
Revision history for this message
|
#40 |
I see some unexpected details in your output.
1. yes, you should update base-files to 9.4ubuntu4.11 from xenial-updates.
Running "sudo apt update" and confirming with "y" is ok and will not re-install the wrong version form disco, but will install the updated version for xenial.
2. Your kernel version (4.15.0-54-generic) is strange. This is an older version for bionic from Jun 24 2019
What is the output of
dpkg -l | grep ' linux-'
3. The output of the attempt to install the PPA is weird. the group 'x2go' definitely does exist, https:/
I suggest that we try getting everything else solved first. If your system can successfully be upgraded to bionic, then this PPA will not be needed anyhow.
Revision history for this message
|
#41 |
Yes okay, so I've upgraded the following packagges now:
base-files libvpx3 python3-
And I got:
rc linux-modules-
rc linux-modules-
rc linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-sound-base 1.0.25+
ii syslinux-common 3:6.03+
ii syslinux-legacy 2:3.63+
ron@jpax-build07:~$
dpkg -l | grep ' linux-'
ii linux-base 4.5ubuntu1~16.04.1 all Linux image base package
ii linux-firmware 1.157.22 all Firmware for Linux kernel drivers
ii linux-generic-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
ii linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
ii linux-image-
ii linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
rc linux-image-
ii linux-image-
ii linux-libc-
ii linux-libc-dev:i386 4.4.0-169.198 i386 Linux Kernel Headers for development
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
ii linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
ii linux-modules-
ii linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
ii linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
rc linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-sound-base 1.0.25+
ron@jpax-build07:~$
Revision history for this message
|
#42 |
Let's do a clean-up of the residual config files (not needed)
dpkg --list | grep "^rc" | cut -d " " -f 3 | xargs sudo dpkg --purge
and then please repeat
dpkg -l | grep ' linux-'
Revision history for this message
|
#43 |
Ok, yes this looks easier to investigate:
ron@jpax-build07:~$ dpkg -l |grep 'linux-'
ii linux-base 4.5ubuntu1~16.04.1 all Linux image base package
ii linux-firmware 1.157.22 all Firmware for Linux kernel drivers
ii linux-generic-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-headers-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-libc-
ii linux-libc-dev:i386 4.4.0-169.198 i386 Linux Kernel Headers for development
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-sound-base 1.0.25+
ii syslinux-common 3:6.03+
ii syslinux-legacy 2:3.63+
Revision history for this message
|
#44 |
Ok, the kernel version seems ok now; the latest update (4.15.0-70-generic) is installed.
For the release upgrade: I recommend that you try upgrading to bionic (18.04), and not to disco (19.04) first. In my opinion this makes more sense, and I expect better chances of success.
What is the output of
uname -a
cat /etc/update-
/usr/lib/
(For the last command: Do not yet start the upgrade!)
Revision history for this message
|
#45 |
ii linux-image-
ii linux-libc-
ii linux-libc-dev:i386 4.4.0-169.198 i386 Linux Kernel Headers for development
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-modules-
ii linux-sound-base 1.0.25+
ii syslinux-common 3:6.03+
ii syslinux-legacy 2:3.63+
ron@jpax-build07:~$ uname -a
Linux jpax-build07 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
release-upgrades release-upgrades.d/
ron@jpax-build07:~$ cat /etc/update-
# Default behavior for the release upgrader.
[DEFAULT]
# Default prompting behavior, valid options:
#
# never - Never check for a new release.
# normal - Check to see if a new release is available. If more than one new
# release is found, the release upgrader will attempt to upgrade to
# the release that immediately succeeds the currently-running
# release.
# lts - Check to see if a new LTS release is available. The upgrader
# will attempt to upgrade to the first LTS release available after
# the currently-running one. Note that this option should not be
# used if the currently-running release is not itself an LTS
# release, since in that case the upgrader won't be able to
# determine if a newer release is available.
Prompt=lts
ron@jpax-build07:~$
ron@jpax-build07:~$ uname -a
Linux jpax-build07 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
ron@jpax-build07:~$ cat /etc/update-
# Default behavior for the release upgrader.
[DEFAULT]
# Default prompting behavior, valid options:
#
# never - Never check for a new release.
# normal - Check to see if a new release is available. If more than one new
# release is found, the release upgrader will attempt to upgrade to
# the release that immediately succeeds the currently-running
# release.
# lts - Check to see if a new LTS release is available. The upgrader
# will attempt to upgrade to the first LTS release available after
# the currently-running one. Note that this option should not be
# used if the currently-running release is not itself an LTS
# release, since in that case the upgrader won't be able to
# determine if a newer release is available.
Prompt=lts
ron@jpax-build07:~$ /usr/lib/
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
/usr/lib/
from gi.repository import Gtk
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
WARNING:
ron@jpax-build07:~$ sudo apt update
[sudo] password for ron:
Hit:1 http://
Hit:2 http://
Hit:3 http://
Hit:4 http://
Reading package lists... Done
Building dependency tree
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
ron@jpax-build07:~$
ron@jpax-build07:~$ export HTTPS_PROXY=http://
ron@jpax-build07:~$ export HTTP_PROXY=http://
ron@jpax-build07:~$ export https_proxy=http://
ron@jpax-build07:~$ export http_proxy=http://
ron@jpax-build07:~$ /usr/lib/
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
/usr/lib/
from gi.repository import Gtk
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Revision history for this message
|
#46 |
My /etc/update-
already has
Prompt=lts
set i.e. it should uate automacigally to 18.04, right?
Revision history for this message
|
#47 |
Yes, with "Prompt=lts" the upgrade tool should do the upgrade to Ubuntu 18.04.
Try again with
export DISPLAY=:0
/usr/lib/
what do you get?
Revision history for this message
|
#48 |
interesting, I can't launch the gtk version but the text version still says:
/usr/lib/
Checking for a new Ubuntu release
No new release found.
ron@jpax-build07:~$ DISPLAY=:222 /usr/lib/
/usr/lib/
from gi.repository import Gtk
WARNING:
just verifying that my display works as expected!:
ron@jpax-build07:~$ DISPLAY=:222 xeyes - success!
This seems to be a common problem, installing python3-xlib should help....
/usr/lib/
Checking for a new Ubuntu release
No new release found.
ron@jpax-build07:~$ DISPLAY=:222 /usr/lib/
/usr/lib/
from gi.repository import Gtk
WARNING:
ron@jpax-build07:~$
ron@jpax-build07:~$ DISPLAY=:222 xeyes
ron@jpax-build07:~$
ron@jpax-build07:~$
ron@jpax-build07:~$ sudo apt-get install python3-xlib
[sudo] password for ron:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
python3-xlib
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 101 kB of archives.
After this operation, 758 kB of additional disk space will be used.
Get:1 http://
Fetched 101 kB in 1s (70.0 kB/s)
Selecting previously unselected package python3-xlib.
(Reading database ... 364399 files and directories currently installed.)
Preparing to unpack .../python3-
Unpacking python3-xlib (0.14+20091101-5) ...
Setting up python3-xlib (0.14+20091101-5) ...
ron@jpax-build07:~$ DISPLAY=:222 /usr/lib/
/usr/lib/
from gi.repository import Gtk
WARNING:
ron@jpax-build07:~$
hmm or maybe not.... (I did try with an apt update too but no go, ideas?)
Do you expect a different result from the GTK version vs. text version?
Revision history for this message
|
#49 |
I see several strange things:
running programs without setting DISPLAY doesn't work
"No new release found"
What is the output of the command
DEBUG_UPDATE_
Revision history for this message
|
#50 |
Sorry, I missed to paste the export
"DISPLAY=:222"
line, I did set the DISPLAY variable and I verified I've xeyes works fine even if called like:
ron@jpax-build07:~$ DISPLAY=:222 xeyes
ron@jpax-build07:~$ export DISPLAY=:222
ron@jpax-build07:~$ xeyes
executing the command with DEBUG_UPDATE_
ron@jpax-build07:~$ DEBUG_UPDATE_
Checking for a new Ubuntu release
MetaRelease.
/etc/update-
/etc/update-
/etc/update-
/etc/update-
metarelease-uri: https:/
MetaRelease.
result of meta-release download: '<urlopen error [SSL: CERTIFICATE_
NO self.metareleas
No new release found.
ron@jpax-build07:~$
I assume this is what's causing the problem:
<urlopen error [SSL: CERTIFICATE_
can the SSL check be circumvented (like --no-check-
The proxy env vars are still set:
ron@jpax-build07:~$ echo $http_proxy
http://
ron@jpax-build07:~$ echo $https_proxy
http://
ron@jpax-build07:~$ echo $HTTP_PROXY
http://
ron@jpax-build07:~$ echo $HTTPS_PROXY
http://
Revision history for this message
|
#51 |
I saw that the programs work if you set DISPLAY, but this is not normal. Setting a value for DISPLAY should not be necessary.
Also for me the "[SSL: CERTIFICATE_
What happens if you try opening https:/
Revision history for this message
|
#52 |
The firefox pulls up:
https:/
Dist: warty
Name: Warty Warthog
Version: 04.10
Date: Wed, 20 Oct 2004 07:28:17 UTC
Supported: 0
Description: This is the warty warthog release
Release-File: http://
Dist: hoary
Name: Hoary Hedgehog
Version: 05.04
Date: Fri, 08 Apr 2005 08:18:19 UTC
Supported: 0
Description: This is the Hoary Hedgehog release
Release-File: http://
Dist: breezy
Name: Breezy Badger
Version: 05.10
Date: Thu, 13 Oct 2005 19:34:42 UTC
Supported: 0
Description: This is the Breezy Badger release
Release-File: http://
Dist: dapper
Name: Dapper Drake
Version: 6.06 LTS
Date: Thu, 01 Jun 2006 9:00:00 UTC
Supported: 0
Description: This is the Dapper Drake release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: edgy
Name: Edgy Eft
Version: 6.10
Date: Thu, 26 Oct 2006 12:00:00 UTC
Supported: 0
Description: This is the Edgy Eft release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: feisty
Name: Feisty Fawn
Version: 7.04
Date: Thu, 19 Apr 2007 13:00:00 +0200
Supported: 0
Description: This is the 7.04 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: gutsy
Name: Gutsy Gibbon
Version: 7.10
Date: Thu, 18 Oct 2007 12:00:00 UTC
Supported: 0
Description: This is the 7.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: hardy
Name: Hardy Heron
Version: 8.04 LTS
Date: Thu, 24 Apr 2008 12:00:00 UTC
Supported: 0
Description: This is the 8.04 LTS release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: intrepid
Name: Intrepid Ibex
Version: 8.10
Date: Thu, 30 Oct 2008 12:00:00 UTC
Supported: 0
Description: This is the 8.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: jaunty
Name: Jaunty Jackalope
Version: 9.04
Date: Thu, 23 Apr 2009 12:00:00 UTC
Supported: 0
Description: This is the 9.04 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: karmic
Name: Karmic Koala
Version: 9.10
Date: Thu, 29 Oct 2009 12:00:00 UTC
Supported: 0
Description: This is the 9.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: lucid
Name: Lucid Lynx
Version: 10.04.4 LTS
Date: Thu, 29 Apr 2010 12:00:00 UTC
Supported: 0
Description: This is the 10.04.4 LTS release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: maverick
Name: Maverick Meerkat
Version: 10.10
Date: Sun, 10 Oct 2010 10:10:10 UTC
Supported: 0
Description: This is the 10.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: natty
Name: Natty Narwhal
Version: 11.04
Date: Thu, 28 Apr 2011 12:00:00 UTC
Supported: 0
Description: This is the 11.04 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: oneiric
Name: Oneiric Ocelot
Version: 11.10
Date: Thu, 13 Oct 2011 12:00:00 UTC
Supported: 0
Description: This is the 11.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: precise
Name: Precise Pangolin
Version: 12.04.5 LTS
Date: Thu, 26 Apr 2012 12:04:00 UTC
Supported: 1
Description: This is the 12.04.5 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: quantal
Name: Quantal Quetzal
Version: 12.10
Date: Thu, 18 Oct 2012 12:04:00 UTC
Supported: 0
Description: This is the 12.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: raring
Name: Raring Ringtail
Version: 13.04
Date: Thu, 25 Apr 2013 13:04:00 UTC
Supported: 0
Description: This is the 13.04 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: saucy
Name: Saucy Salamander
Version: 13.10
Date: Thu, 17 Oct 2013 13:10:00 UTC
Supported: 0
Description: This is the 13.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: trusty
Name: Trusty Tahr
Version: 14.04.6 LTS
Date: Thu, 17 Apr 2014 14:04:00 UTC
Supported: 1
Description: This is the 14.04.6 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: utopic
Name: Utopic Unicorn
Version: 14.10
Date: Thu, 23 Oct 2014 14:10:00 UTC
Supported: 0
Description: This is the 14.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: vivid
Name: Vivid Vervet
Version: 15.04
Date: Thu, 23 April 2015 15:04:00 UTC
Supported: 0
Description: This is the 15.04 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: wily
Name: Wily Werewolf
Version: 15.10
Date: Thu, 22 October 2015 15:10:00 UTC
Supported: 0
Description: This is the 15.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: xenial
Name: Xenial Xerus
Version: 16.04.6 LTS
Date: Thu, 21 April 2016 16:04:00 UTC
Supported: 1
Description: This is the 16.04.6 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: yakkety
Name: Yakkety Yak
Version: 16.10
Date: Thu, 13 October 2016 16:10:00 UTC
Supported: 0
Description: This is the 16.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: zesty
Name: Zesty Zapus
Version: 17.04
Date: Thu, 13 April 2017 17:04:00 UTC
Supported: 0
Description: This is the 17.04 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: artful
Name: Artful Aardvark
Version: 17.10
Date: Thu, 19 October 2017 17:10:00 UTC
Supported: 0
Description: This is the 17.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: bionic
Name: Bionic Beaver
Version: 18.04.3 LTS
Date: Thu, 26 April 2018 18:04:00 UTC
Supported: 1
Description: This is the 18.04.3 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: cosmic
Name: Cosmic Cuttlefish
Version: 18.10
Date: Thu, 18 October 2018 18:10:00 UTC
Supported: 0
Description: This is the 18.10 release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: disco
Name: Disco Dingo
Version: 19.04
Date: Thu, 18 April 2019 19:04:00 UTC
Supported: 1
Description: This is the 19.04 release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: eoan
Name: Eoan Ermine
Version: 19.10
Date: Thu, 17 October 2019 19:10:00 UTC
Supported: 1
Description: This is the 19.10 release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
https:/
Dist: dapper
Name: Dapper Drake
Version: 6.06 LTS
Date: Thu, 01 Jun 2006 9:00:00 UTC
Supported: 0
Description: This is the Dapper Drake release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: hardy
Name: Hardy Heron
Version: 8.04.1 LTS
Date: Thu, 24 Apr 2008 12:00:00 UTC
Supported: 0
Description: This is the 8.04.1 LTS release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: lucid
Name: Lucid Lynx
Version: 10.04.4 LTS
Date: Thu, 29 Apr 2010 12:00:00 UTC
Supported: 0
Description: This is the 10.04.4 LTS release
Release-File: http://
ReleaseNotes: http://
UpgradeTool: http://
UpgradeToolSign
Dist: precise
Name: Precise Pangolin
Version: 12.04.5 LTS
Date: Thu, 26 Apr 2012 12:04:00 UTC
Supported: 1
Description: This is the 12.04.5 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: trusty
Name: Trusty Tahr
Version: 14.04.6 LTS
Date: Thu, 17 Apr 2014 14:04:00 UTC
Supported: 1
Description: This is the 14.04.6 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: xenial
Name: Xenial Xerus
Version: 16.04.6 LTS
Date: Thu, 21 April 2016 16:04:00 UTC
Supported: 1
Description: This is the 16.04.6 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
Dist: bionic
Name: Bionic Beaver
Version: 18.04.3 LTS
Date: Thu, 26 April 2018 18:04:00 UTC
Supported: 1
Description: This is the 18.04.3 LTS release
Release-File: http://
ReleaseNotes: http://
ReleaseNotesHtml: http://
UpgradeTool: http://
UpgradeToolSign
and this is what I get when using wget:
ron@jpax-build07:~$ wget https:/
--2019-11-27 12:30:05-- https:/
Connecting to 10.1.215.250:80... connected.
ERROR: cannot verify changelogs.
Unable to locally verify the issuer's authority.
To connect to changelogs.
ron@jpax-build07:~$ wget --no-check-
--2019-11-27 12:30:16-- https:/
Connecting to 10.1.215.250:80... connected.
WARNING: cannot verify changelogs.
Unable to locally verify the issuer's authority.
Proxy request sent, awaiting response... 200 OK
Length: 16313 (16K)
Saving to: ‘meta-release’
meta-release 100%[==
2019-11-27 12:30:18 (133 MB/s) - ‘meta-release’ saved [16313/16313]
ron@jpax-build07:~$ wget https:/
--2019-11-27 12:30:27-- https:/
Connecting to 10.1.215.250:80... connected.
ERROR: cannot verify changelogs.
Unable to locally verify the issuer's authority.
To connect to changelogs.
ron@jpax-build07:~$ wget --no-check-
--2019-11-27 12:30:33-- https:/
Connecting to 10.1.215.250:80... connected.
WARNING: cannot verify changelogs.
Unable to locally verify the issuer's authority.
Proxy request sent, awaiting response... 200 OK
Length: 4386 (4.3K)
Saving to: ‘meta-release-lts’
meta-release-lts 100%[==
2019-11-27 12:30:34 (307 MB/s) - ‘meta-release-lts’ saved [4386/4386]
ron@jpax-build07:~$
Is there some way to manually popluate the table that do-release-upgrade checks?
Revision history for this message
|
#53 |
the man page doesn't indicate any external way to provide the above data to do-release-upgrade.
I just launched
update-manager
/usr/bin/
from gi.repository import Gtk
/usr/lib/
from gi.repository import Dbusmenu, Unity
/usr/lib/
from gi.repository import Dbusmenu, Unity
and got a popup dialog that reads "You are not allowed to perform tjhis saction" "You don't have the required priovileges to perform this action."
so i launch iot again with sudo:
sudo update-manager
[sudo] password for ron:
/usr/bin/
from gi.repository import Gtk
/usr/lib/
from gi.repository import Dbusmenu, Unity
/usr/lib/
from gi.repository import Dbusmenu, Unity
Ok I now got a dialog telling me that I have 1.2MB of pending Security Updates and it lists package U buntu base. I haven't gone ahead and installed them yet... I don't want to mess up things even more... When I click the settings button, under Updates, on the botttom the checkbox "Notify me of a new Ubutnu version:" is correctly set to "For long-term support versions"
Revision history for this message
|
#54 |
I am not aware of a possibility to circumvent the "<urlopen error [SSL: CERTIFICATE_
I want to suggest that you check your web proxy setup, because this seems to prevent the download.
You can expect the release upgrader to work only if also a wget command (without '--no-check-
The messages like "PyGIWarning: Gtk was imported without specifying a version first" are just warnings and should not prevent the program from running.
And for the proposed package update, I assume that this is a normal update from one version in xenial to another one (in xenial-updates or xenial-security).
To verify, what is the output of
apt list --upgradable
Revision history for this message
|
#55 |
The problem is, I don't have access to the web proxy setup or configuration. I'm working for a large corporation and all I'm given, is an IP of a VM that's humming away somewhere on a server, look at it as a regular VPS.
I'm wondering then why apt seems to work seamlessly and do-release-upgrade doesn't....that's klind of weird....
I see wjhat you're saying regarding the update but see the below:
ron@jpax-build07:~$ sudo apt update;
[sudo] password for ron:
Hit:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
Get:6 http://
Get:7 http://
Get:8 http://
Get:9 http://
Fetched 804 kB in 7s (115 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
ron@jpax-build07:~$ sudo apt list --upgradable
Listing... Done
I don't get the update thar update-manager shows me through apt.
Revision history for this message
|
#56 |
If you now start update-manager, so you still see a pending update?
There can be an automatic installation of security updates (to be configured in the settings of update-manager).
For the failure with wget (and do-release-
Do you have a wgetrc file?
Maybe you can configure wget to work without --no-check-
https:/
Revision history for this message
|
#57 |
Okay,
I appended check_certificate = off to /etc/wgetrc and can now use wget without the argument --no-cjheck-
ron@jpax-build07:~$ wget https:/
--2019-11-28 11:01:38-- https:/
Connecting to 10.1.215.250:80... connected.
WARNING: cannot verify changelogs.
Unable to locally verify the issuer's authority.
Proxy request sent, awaiting response... 200 OK
Length: 4386 (4.3K)
Saving to: ‘meta-release-
meta-release-lts.1 100%[==
2019-11-28 11:01:39 (329 MB/s) - ‘meta-release-
when I launch sudo update-manager -c
now, it tells me Please restart the computer to begin using your updated software - what updated software?
Security updates are set to "Download and install automatically"
but this still days:
ron@jpax-build07:~$ do-release-upgrade
Checking for a new Ubuntu release
No new release found. :(
and then:
ron@jpax-build07:~$ sudo apt update
Hit:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Fetched 325 kB in 2s (138 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
ron@jpax-build07:~$ sudo apt list --upgradable
Listing... Done
ron@jpax-build07:~$
as for rebooting - I could if really needed but prefer not to to be honest... it's been up for 132 days - I know to complete an upgrade I would need to reboot even just to load the updated kernel...
I guess I'll need to reboot in order to satisfy the update-manager, right?
Revision history for this message
|
#58 |
There are different aspects:
1. The release-upgrader always checks whether updates have been installed that require a reboot, and the system has not been rebooted since.
You can check for the presence (and the contents) of the files
/var/run/
2. What output do you now get for
DEBUG_UPDATE_
Revision history for this message
|
#59 |
hm yes, here I get:
ron@jpax-build07:~$ ls -l /var/run/
-rw-r--r-- 1 root root 32 Nov 18 13:49 /var/run/
ron@jpax-build07:~$ cat /var/run/
*** System restart required ***
ron@jpax-build07:~$ ls -l /var/run/
-rw-r--r-- 1 root root 89 Nov 18 13:49 /var/run/
ron@jpax-build07:~$ cat /var/run/
linux-base
linux-base
linux-base
libc6
libc6
linux-base
linux-base
linux-base
linux-base
and for:
ron@jpax-build07:~$ DEBUG_UPDATE_
Checking for a new Ubuntu release
MetaRelease.
/etc/update-
/etc/update-
/etc/update-
/etc/update-
metarelease-uri: https:/
MetaRelease.
result of meta-release download: '<urlopen error [SSL: CERTIFICATE_
NO self.metareleas
No new release found.
ron@jpax-build07:~$
I still get the certificate verification failure...
I shoudl probably reboot and see what I can do after that, right?
Revision history for this message
|
#60 |
I don't expect that a reboot will help for the certificate problem.
Can you help with this problem?
Provide an answer of your own, or ask cerr for more information if necessary.