Package Details: python-catkin_pkg 0.4.24-1

Git Clone URL: (read-only, click to copy)
Package Base: python-catkin_pkg
Description: Standalone Python library for the catkin package system
Upstream URL:
Licenses: BSD
Conflicts: python-catkin-pkg, python2-catkin_pkg
Provides: python-catkin-pkg
Submitter: kartikmohta
Maintainer: kartikmohta (bionade24)
Last Packager: kartikmohta
Votes: 8
Popularity: 0.000002
First Submitted: 2017-06-01 00:23
Last Updated: 2021-10-28 08:57

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

wbthomason commented on 2017-06-26 15:59

I strongly agree with @squirrel that this is a problem, and am also willing to help fix it.

squirrel commented on 2017-06-26 09:19

I think it's a problem, because it completely blocks using any automated way of installing packages, and unless it's easy to install nobody will update frequently.... and this approach is really bad considering we are speaking of ROS that has hundreds of packages, if each package would do that, you would definetly avoid using that mechanism....

What I described was 'simplest' approach - python2 version provides modules and binaries, python3 version provides only modules. That means that you _have_ to install python2 version and _can_ install python3 version.

If we want trully correct way, best approach is to split modules and scripts into separate packages for both versions, like it's done for debian packages as seen in this debian recipe:

what I have in mind is:

python{,2}-catkin_pkg_modules -> just the modules, no conflict with each other
python{,2}-catkin_pkg -> just the scripts, without modules, these depends on _modules version and conflicts with each other

this way we should be able to get one step closer to ros with python3 in case we are able to do this for every package.

P.S: I am more than willing to help with this

kartikmohta commented on 2017-06-25 16:31

@squirrel Yes agreed that an automated install (makepkg -i) doesn't work with the current PKGBUILD but you can choose to install any one of the two packages after building, right? Disabling the installation of the python scripts for the python3 package doesn't seem like the right solution since that requires you to install both versions to get the full functionality. I can just give in and create separate PKGBUILDs for the Python2 and Python3 version if the "manually choose the version to install" process is a big pain for people.

squirrel commented on 2017-06-25 15:19


I just realized that most of the packages are broken, which is current state: you wrote PKGBUILDs in way that two packages are builded, installed that conflict each other... why? that's wrong way of using AUR...

Most of the packages I encountered support SKIP_PYTHON_SCRIPTS=1 enviromental variable, which enforces installation only of modules of that package (which does not conflict between python versions).

I suggest setting that for every python3 version of package and getting rid of that god dam dependency confliction.

EDIT: sent patch via email to owner of the package

squirrel commented on 2017-06-25 13:33

Hmm, last version of PKGBUILD builds two packages that conflict with each other, is that intented?

kartikmohta commented on 2017-06-21 19:27

For ROS, you'll mostly want to install the python2 package. Making ROS work with Python 3 currently is a pain.

racko commented on 2017-06-21 18:04

@osjacky430: You only want to install one of both. Apparently you already have one installed. Try continuing to install ROS with the one you have. If your package manager tells you that you need the other, uninstall the one you have and install the other ;)

osjacky430 commented on 2017-06-19 02:36

Sorry, kartikmohta, I'm a newbie and accidentaly send the delete request, and don't know how to cancel the request. I'm so sorry about it. :(

However, during installation, error occurs as follow:

python-catkin_pkg and python2-catkin_pkg are in conflict

I could'nt find soultion so far, please help me with this, thanks in advance.

de-vries commented on 2016-03-16 19:37

It is currently not possible to install python 2 and 3 versions of catkin_pkg, which is somewhat annoying. It makes sense that you can only install the tools in /usr/bin once, but for the python library there is really no reason.

Would it be an idea to split this into python-libcatkin-pkg and python-catkin-pkg, and do the same for python2?

Alternative names could be:
python-caktin-pkg (libs only)
python-caktin-pkg-tools (tools)

Or, since it shouldn't matter which python version is used for the tools they might be left out entirely from the package(s) for one of the two python versions.

de-vries commented on 2015-12-30 12:21

great, thanks :)