Closed tfoote closed 6 years ago
I believe that this is an issue between the packaging toolchain for bionic and xenial.
I pushed 0.4.6 as a workaround and confirmed it's working to install.
Artifacts for future debugging. catkin_pkg_modules_0.4.5_artifacts.zip
Looks like https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1730627 . Someone at
aptly-dev/aptly/#655 traced it to dkpg-deb making --uniform-compression
the default. It looks like a fix was released to Trusty on 2018-03-14.
The .deb
from the zip archive appears to install fine in up-to-date trusty docker container.
$ sudo apt-get install python3-dateutil python3-docutils python3-pyparsing
# ... edited out ...
$ sudo dpkg -i python3-catkin-pkg-modules_0.4.5-1_all.deb
Selecting previously unselected package python3-catkin-pkg-modules.
(Reading database ... 26122 files and directories currently installed.)
Preparing to unpack python3-catkin-pkg-modules_0.4.5-1_all.deb ...
Unpacking python3-catkin-pkg-modules (0.4.5-1) ...
Setting up python3-catkin-pkg-modules (0.4.5-1) ...
$ python3
Python 3.4.3 (default, Nov 28 2017, 16:41:13)
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import catkin_pkg
>>>
If asking users to upgrade dpkg
on trusty is acceptable then I think this can be closed.
Since trusty is still supported and that's been available I think it's reasonable to do.
We'll also need to rebuild our base images for testing with the new version included. That explains why this passed for amd64, but not i386 and armhf since those are our slightly less updated targets.
@nuclearsandwich It looks like we should rebuild our base images.
@nuclearsandwich It looks like we should rebuild our base images.
New images have been pushed after testing that the i386 and armhf trusty images can install python3-catkin-pkg-modules successfully.
I will go ahead and close this ticket since it sounds like it has been addressed by updating the system.
Hi there, I have the same problem, but by reading the answers, i became more confused! would you please clear the final solution?! and my preference is to avoid installing python3!
Regards,
@elahia Please see the comment in the referenced ticket mentioning the exact steps to update dpkg
: https://github.com/ros-infrastructure/catkin_pkg/issues/230#issuecomment-408913341
I did:
1. apt-get update
2. apt-get install dpkg
but the output is look like this
then I tried for apt-get install python-catkin-pkg, the result is:
root@DESKTOP-IQU4A6G:/# apt-get install python-catkin-pkg
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
python-catkin-pkg : Depends: python-catkin-pkg-modules (>= 0.4.7) but it is not going to be installed
python-rosdistro-modules : Depends: python-catkin-pkg-modules but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
root@DESKTOP-IQU4A6G:/#
trying for apt-get -f install does not help!
Am I right?
I am not sure if you have seen the ROS support guidelines but we kindly ask to raise questions like this on answers.ros.org instead.
The rational for asking all kind of questions in a single place is:
Also this ticket is already closed so comments will likely not get much attention and the chance of them to be "lost" is rather high.
If you have asked your question on answers.ros.org please feel free to add a link to the question to this ticket so that future readers can find the related question. Also consider adding more information (e.g. the output when you do run the suggested command apt-get -f install
, the version of dpkg
you currently have installed).
@dirk-thomas Do you now what version of dpkg I should be running? I have version 1.17.5 on Ubuntu 14.04 arm. I have tried updating but dpkg seems to be "up to date".
@r1b4z01d https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1730627/comments/19 says it's fixed in 1.17.5ubuntu5.8
Following up https://github.com/ros-infrastructure/ros_buildfarm/issues/559
Here's a log of trying to install it in a clean docker container https://gist.github.com/tfoote/5d8c0fd497d2dbbdee19c26d083e11e1