Package Details: conan 1.48.2-1

Git Clone URL: (read-only, click to copy)
Package Base: conan
Description: A distributed, open source, C/C++ package manager.
Upstream URL:
Licenses: MIT
Submitter: suridaj
Maintainer: suridaj
Last Packager: suridaj
Votes: 61
Popularity: 1.69
First Submitted: 2016-08-21 01:35 (UTC)
Last Updated: 2022-06-20 16:43 (UTC)

Latest Comments

suridaj commented on 2022-04-27 13:51 (UTC)

@FabioLolix: thank you for the suggestion, from now on the source file is renamed as $pkgname-$pkgver.

FabioLolix commented on 2022-04-24 12:17 (UTC)

You're welcome to rename the source as $pkgname-$pkgver

raeste commented on 2022-01-05 05:01 (UTC)

Thanks for the hint with the python version in .local and /usr. I removed the packages from the .local folder and after that the installation was successfull =)

carlosal1015 commented on 2022-01-04 17:03 (UTC) (edited on 2022-01-04 17:04 (UTC) by carlosal1015)

I do not have any error

==> Finished making: conan 1.44.0-1 (Tue 04 Jan 2022 12:01:45 PM -05)

Please could you please upload the logs.

Usually, mixing python versions ~/.local/lib/python3.10 with /usr/lib/python3.10 could generate errors.

raeste commented on 2022-01-04 16:41 (UTC) (edited on 2022-01-04 16:54 (UTC) by raeste)

I tried to build the current version of conan but i got an error:

File "/home/kev/.local/lib/python3.10/site-packages/setuptools/command/", line 127, in build_package_data srcfile in self.distribution.convert_2to3_doctests): AttributeError: 'Distribution' object has no attribute 'convert_2to3_doctests'

suridaj commented on 2021-12-02 11:26 (UTC) (edited on 2021-12-02 12:07 (UTC) by suridaj)

@silverhikari, generally, X-git packages should specify which version of X they provide, see

In this particular case, conan depends on python-fasteners>=0.14.1. python-fasteners-git does not declare which version of python-fasteners it provides, so pacman cannot guarantee python-fasteners-git can stand in for python-fasteners>=0.14.1.

You can work around your issue in one of the following ways:

  • edit python-fasteners-git's PKGBUILD and specify the provided version of python-fasteners, eg. provides=('python-fasteners=0.16.1')


  • edit conan's PKGBUILD and remove the required version of python-fasteners so that its depends line is just 'python-fasteners' without any version.

silverhikari commented on 2021-12-02 09:00 (UTC) (edited on 2021-12-02 09:01 (UTC) by silverhikari)

when trying to install conan i get a package conflict that tries to install python-fasteners though the reason i am running python-fasteners-git for a package that requires it. i do not know why this is happening as the pkgbuild seems to allow for both?

suridaj commented on 2021-08-10 23:02 (UTC)

@bazza: Which command exactly are you running? The quoted command runs for me on a clean, up-to-date system.

bazza commented on 2021-08-10 22:44 (UTC)

Errors occurred, no packages were upgraded. Command 'sudo pacman --color=always --sync --asdeps python-yaml>=3.11 python-tqdm>=4.28.1 python-pyjwt>=1.4.0 python-fasteners>=0.14.1 python-future>=0.16.0' failed to execute.

suridaj commented on 2021-02-08 10:21 (UTC) (edited on 2021-02-08 10:25 (UTC) by suridaj)

@stas, you're welcome and it was no bother.

There might be better ways to handle new Python versions than "reinstall all AUR packages manually", unfortunately I am not aware of them. If you guys have suggestions I would be happy to try them out :)

stas commented on 2021-02-08 10:10 (UTC)

@suridaj, thank you for your message. I think this was probably the case. Yes, I have updated python too, which was also the reason to update conan. However I am not at a level to recognise that the issue was with python. I should have tried that before reporting, considering the number of comments related to python version upgrade.

suridaj commented on 2021-02-08 09:40 (UTC) (edited on 2021-02-08 09:45 (UTC) by suridaj)

@stas, thanks for the report.

I tried to reproduce the issue without success. Steps:

  1. I started from a clean updated Arch system with yay.
  2. I modified PKGBUILD from python-node-semver 0.8.0-2 to build and install 0.6.1.
  3. I installed conan 1.33.1-1 and verified python-node-semver is still 0.6.1.
  4. conan runs normally with python-node-semver 0.6.1.
  5. Inside python interpreter, "from semver import SemVer" works without error. This is the exact line Conan uses.

One thing that comes to mind: if you recently updated Python from 3.8 to 3.9, python-node-semver likely remained installed in /usr/lib/python3.8/site-packages.

If you need the version of python-node-semver to be specifically 0.6.1, please try installing it again.

stas commented on 2021-02-08 09:11 (UTC)

It looks like conan now requires newer version of the python-node-semver. I had version 0.6.1 installed and older version of conan worked fine. Today I have updated conan and it would not start anymore:

ImportError: cannot import name 'SemVer' from 'semver' (/usr/lib/python3.9/site-packages/

After updating python-node-semver to 0.8.0 conan works again.

Please consider updating requirements?

suridaj commented on 2020-12-04 14:23 (UTC)

Good to hear. I pushed updates to most AUR deps of Conan so it all got rebuilt.

ruabmbua commented on 2020-12-04 14:11 (UTC)

@suridaj thanks for the help.

The problem fixed itself, the package got updated today.

suridaj commented on 2020-12-04 10:14 (UTC)

@ruabmbua: This happens when Python gets a minor version bump. It recently got upgraded from python-3.8 to 3.9 so all the Python-based packages from AUR are now left in /usr/lib/python3.8/site-packages/

You should rebuild and reinstall all your Python-based packages from AUR including Conan and its dependencies. If you use an AUR helper, there might be an option to rebuild all.

suridaj commented on 2020-12-04 10:13 (UTC)

@ruabmbua: This happens when Python gets a minor version bump. It recently got upgraded from python-3.8 to 3.9 so all the Python-based packages from AUR are now left in /usr/lib/python3.8/site-packages/

You should rebuild and reinstall all your Python-based packages from AUR including Conan and its dependencies. If you use an AUR helper, there might be an option to rebuild all.

ruabmbua commented on 2020-12-04 09:22 (UTC)

I tried to use conan today, and I get the following error:

Traceback (most recent call last):
  File "/usr/bin/conan", line 33, in <module>
    sys.exit(load_entry_point('conan==1.31.0', 'console_scripts', 'conan')())
  File "/usr/bin/conan", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.9/importlib/", line 524, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.9/importlib/", line 187, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: conan

I can not remember, if I changed anything, probably not.

Maybe this is a problem with a package upgrade?

suridaj commented on 2020-10-07 10:14 (UTC)

@paragoumba thank you, I removed fakeroot from makedepends.

Paragoumba commented on 2020-10-05 13:55 (UTC)

Fakeroot should not be in the makedepends because it is part of base-devel and packages of this group are assumed to already be installed

suridaj commented on 2019-11-30 12:47 (UTC)

Good to hear! I'm going to bump pkgrels for the dependencies I package, hopefully that will reduce the scope of the issue.

Kuznetsss commented on 2019-11-30 12:06 (UTC)

@suridaj, thank you for quick response. Rebuilding only python-pluginbase doesn't helps. But everything works fine after reinstalling conan with all dependencies rebuilt. Thank you for help.

suridaj commented on 2019-11-30 11:58 (UTC) (edited on 2019-11-30 11:58 (UTC) by suridaj)

@Kuznetsss, after upgrading to Python 3.8 you should rebuild all packages from AUR. Please rebuild python-pluginbase and let me know if it helped.

Kuznetsss commented on 2019-11-30 11:53 (UTC) (edited on 2019-11-30 11:53 (UTC) by Kuznetsss)

I have error with latest version:

Traceback (most recent call last):
  File "/usr/bin/conan", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.8/site-packages/pkg_resources/", line 3252, in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.8/site-packages/pkg_resources/", line 3235, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/pkg_resources/", line 3264, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.8/site-packages/pkg_resources/", line 583, in _build_master
  File "/usr/lib/python3.8/site-packages/pkg_resources/", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.8/site-packages/pkg_resources/", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pluginbase>=0.5' distribution was not found and is required by conan

DaanDeMeyer commented on 2019-10-10 11:21 (UTC)

Everything works perfectly now. Thanks for the quick response!

suridaj commented on 2019-10-09 10:22 (UTC)

Thank you @DaanDeMeyer, please see if you can build it now.

DaanDeMeyer commented on 2019-10-07 17:27 (UTC)

With the removal of packages from base, building the package now fails because of several missing dependencies:

  • patch is no longer in base and should be added as a make dependency.
  • fakeroot is in base-devel but I didn't have it installed. I'd still prefer it to be added as a make dependency but I can understand if you don't want to add stuff from base-devel as a dependency.

suridaj commented on 2019-10-03 16:36 (UTC) (edited on 2019-10-03 16:38 (UTC) by suridaj)

I'm pushing further updates to Conan with an eye out for new python-urllib3.

suridaj commented on 2019-09-25 09:25 (UTC)

Conan 1.18.5 is out with a bugfix which bloxks the new urllib3, from release notes: "Bugfix: A bug ( in urllib3 caused bad encoded URLs causing failures when using any repository from Bintray, like conan-center. (#5801" I have decided not to update the PKGBUILD until we see what Arch does with the new python-urllib3 1.25.5.

libreliu commented on 2019-07-25 12:32 (UTC)

The regression is solved, thanks!

suridaj commented on 2019-07-25 10:02 (UTC)

@libreliu, thanks for the heads-up. 1.17.1 is up. Please see if the regression is solved.

libreliu commented on 2019-07-25 09:42 (UTC)

Conan is having a regression problem at 1.17.0, and they've released 1.17.1 to solve the problem. Thanks for packaging, better if the package can be updated soon.

simona commented on 2019-06-02 21:09 (UTC)

all ok now

suridaj commented on 2019-05-29 14:57 (UTC)

I've decided to reupload python-pluginbase and maintain it for the time being, so conan again has all the dependencies covered on AUR.

suridaj commented on 2019-05-28 11:19 (UTC)

python-pluginbase, a dependency of conan, seems to have disappeared from AUR. I am waiting for its maintaner to respond and will post an update.

suridaj commented on 2019-05-28 09:12 (UTC)

Please update conan to 1.15.1-2.

simona commented on 2019-05-28 08:25 (UTC)

:: installing python-pylint (2.3.1-1) breaks dependency 'python-pylint<2.3.0' required by conan

jochembroekhoff commented on 2019-05-28 06:23 (UTC)

Pylint 2.3.1 has been released.

suridaj commented on 2019-03-08 15:42 (UTC)

Due to a bug in pylint 2.3.0, there is a temporary dependency restriction to use python-pylint < 2.3.0. This restriction will be lifted with pythin-pylint 2.3.1.

For more information see:

suridaj commented on 2018-11-01 16:35 (UTC)

@YeeP, to upgrade Conan using pacman you should follow the same procedure you originally used to get the build files, make the package, and install it. See the ArchWiki:

YeeP commented on 2018-11-01 14:57 (UTC)

@suridaj I am having the same problem as simona, how do you upgrade/install a specific version of conan with pacman? Thank you

simona commented on 2018-10-30 10:28 (UTC)

ok... now ok

suridaj commented on 2018-10-29 21:58 (UTC)

@simona, thank you for the report. Please try conan-1.8.4-2 and let me know if there are still problems.

simona commented on 2018-10-29 19:14 (UTC)

!! While searching for solutions the following errors occurred: :: Not provided: python-future=0.16.0 but needed by conan-1.8.4-1

suridaj commented on 2018-04-12 20:51 (UTC)

@Eremiell, thank you for the heads-up, I slipped on 1.2.3!

Eremiell commented on 2018-04-12 16:13 (UTC) (edited on 2018-04-12 16:13 (UTC) by Eremiell)

diff --git a/PKGBUILD b/PKGBUILD
index 841981e..cf67a1e 100644
@@ -1,7 +1,7 @@
 # Maintainer: Tomislav Ivek <>

 pkgdesc="A distributed, open source, C/C++ package manager."
@@ -44,5 +44,5 @@ package() {
   install -m755 -d "${pkgdir}/usr/share/doc/conan"
   install -m644 contributors.txt "${pkgdir}/usr/share/doc/conan/"

suridaj commented on 2018-01-24 12:21 (UTC)

Since Conan 1.0.0 I have removed the upper version requirement on dependencies, let's see how that goes for a bit.

We are less strict now so there should be fewer conflicts during upgrades. Still, please keep an eye out for any possible bugs when updating the dependencies!

virtualdxs commented on 2018-01-24 06:38 (UTC)

Please do remove this upper limit.

greyltc commented on 2017-12-25 09:30 (UTC)

Yeah, I vote in favor of removing all the upper version limits for the deps.

suridaj commented on 2017-12-24 12:21 (UTC)

Great that it worked and I am sorry you had to work around this issue.

Again, I would like to hear from the users: would you prefer me to relax requirements on specific versions of conan's dependencies? This would make upgrades smoother but sometimes bugs could seep in when underlying libs break compatibility.

bowhuntr commented on 2017-12-24 12:14 (UTC)

Yes, that worked. Thanks.

suridaj commented on 2017-12-24 12:10 (UTC)

I understand python-pylint and conan cannot be upgraded. Please try removing conan, updating packages from the official repos, then installing conan again.

bowhuntr commented on 2017-12-24 11:40 (UTC)

Something has to change because neither conan nor python-pylint can be updated.

suridaj commented on 2017-12-24 09:29 (UTC)

I try to follow closely the requirements listed by the upstream. On the one hand, it is very rare that updating a dependency breaks Conan functionality - I test this quite often and submit patches to Conan so that Arch's fresh packages are accomodated. On the other hand, there are cases where serious bugs do occur and dependency versions really need to be constrained (such as the pylint 1.7.x + astroid 1.6 breaking bug )

That said, I am open for suggestions. Would Conan users be willing to suffer possible occasional bugs and breakage if I remove the high-version limit on dependencies?

greyltc commented on 2017-12-23 23:54 (UTC)

conan: installing python-pylint (1.8.1-1) breaks dependency 'python-pylint<=1.8.0'

Does this package really need all the very specific dependency version requirements it has? Maybe most of them could be removed?

suridaj commented on 2017-12-22 16:30 (UTC) (edited on 2017-12-22 16:30 (UTC) by suridaj)

Conan 0.30.3 is out, however it does not work with python-astroid 1.6.0. Here is the bug:

Until this issue is resolved, I am uncomfortable with pushing Conan 0.30.3 as it would conflict with python-astroid>=1.6.0 from mainline Arch.

suridaj commented on 2017-10-29 00:31 (UTC)

Glad you made it work. Because upstream re-release did not change the filename, at this time I think clearing the build cache is the only feasible workaround for users going from package ver 0.28.0-1 to 0.28.0-2.

JakeStanger commented on 2017-10-28 19:51 (UTC)

Clearing build cache fixed it, should have tried that before really. Thanks!

suridaj commented on 2017-10-28 11:11 (UTC)

@JakeStanger, the 0.28.0-2 package specifically fixes the hash because the upstream had to push a re-release: So, the current PKGBUILD should work ok. Could you please verify in a clean environment, ie., if you use an AUR helper please clean the build cache. Alternatively, download the PKGBUILD into an empty directory and makepkg there. Please report your steps and any errors here.

JakeStanger commented on 2017-10-28 10:49 (UTC)

The latest version is failing the validity check

denvit commented on 2017-05-22 16:11 (UTC)

:: conan: installing python-requests (2.14.2-1) breaks dependency 'python-requests<2.14.0' Had to remove it :(

paapereira commented on 2017-05-12 20:10 (UTC)

Worked like a charm :) Thanks

suridaj commented on 2017-05-12 09:53 (UTC)

@paapereira, the dependencies of your installed version of Conan conflict with the dependencies of the new one. First remove the old Conan, then try building the new version.

paapereira commented on 2017-05-11 19:41 (UTC) (edited on 2017-05-11 19:41 (UTC) by paapereira)

I'm having the error when trying to install conan :( $cower -u :: conan 0.22.2-2 -> 0.22.3-2 $ cower -ud :: conan downloaded to /tmp/cower $ cd /tmp/cower/conan $ makepkg -sri ==> Making package: conan 0.22.3-2 (Thu May 11 20:39:02 WEST 2017) ==> Checking runtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: conan: installing python-pylint (1.7.1-1) breaks dependency 'python-pylint<1.6.6' ==> ERROR: 'pacman' failed to install missing dependencies.

suridaj commented on 2017-05-11 12:23 (UTC)

@paapereira, first update conan and only then do pacman -Syu.

paapereira commented on 2017-05-10 20:44 (UTC)

:: conan: installing python-pylint (1.7.1-1) breaks dependency 'python-pylint<1.6.6'

suridaj commented on 2017-05-04 21:28 (UTC)

Thanks, fixed the PKGBUILD, tests pass with the new pylint:

zerophase commented on 2017-05-04 15:54 (UTC)

Python-pylint was just updated.

WiLLiE commented on 2017-04-21 12:07 (UTC)

Works great, thanks.

suridaj commented on 2017-04-21 11:27 (UTC)

Conan 0.22.2 seems to work ok with PyJWT 1.5.0, test run here: To solve the problem with updating to new PyJWT, first update (or remove) Conan and then do pacman -Syu.

suridaj commented on 2017-04-21 09:58 (UTC)

Will post a patch as soon as Conan's tests pass with the new PyJWT.

WiLLiE commented on 2017-04-21 09:13 (UTC) (edited on 2017-04-21 09:14 (UTC) by WiLLiE)

:: conan: installing python-pyjwt (1.5.0-1) breaks dependency 'python-pyjwt<1.5.0'

suridaj commented on 2017-04-18 15:11 (UTC)

Conan 0.22.0 passes all tests with pylint 1.6.4 instead of 1.6.5:

suridaj commented on 2017-02-27 11:10 (UTC)

0.19.3 is a new version in preparation with 0.20. It is important to upgrade: older versions will not be able to properly parse conaninfo.txt made with the coming 0.20 and later.

suridaj commented on 2017-01-29 00:52 (UTC)

I'm glad you fixed it. Please do keep reporting any conflicts you find in the future!

WiLLiE commented on 2017-01-28 21:39 (UTC) (edited on 2017-01-28 22:24 (UTC) by WiLLiE)

Edit: deleting Pacaur's cache of conan fixed it. conan: installing python-requests (2.13.0-1) breaks dependency 'python-requests<2.13.0'

suridaj commented on 2017-01-26 13:47 (UTC)

python-requests 2.13.0 is out. I patched conan 0.18.1 to install alongside. All conan 0.18.1 tests pass with the new python-requests:

suridaj commented on 2016-12-10 01:51 (UTC)

So, thanks to AUR users and the fast pace of Arch rolling release it has been found that conan does not really depend on boto and passlib anymore. The develop branch has been cleaned up so the next upstream release will officially not depend on these libraries. I have decided to patch the remaining mentions of boto and passlib out of 0.16.1 right now. All tests pass ok without them. In this way Arch users can immediately enjoy a smaller number of dependencies and I have an easier job of keeping the PKGBUILD up to date ;)

suridaj commented on 2016-12-09 08:22 (UTC)

I appreciate the report. The new PKGBUILD is up. All tests pass OK with the new boto: I have submitted a pull request to upstream:

zerophase commented on 2016-12-09 03:35 (UTC)

python-boto was just updated.

cguenther commented on 2016-12-06 13:21 (UTC)

Good work. Nice too see the hard versioned dependency list is now a little bit smaller :).

suridaj commented on 2016-12-05 13:58 (UTC)

@cguenther, it turns out conan does not use passlib anymore. 0.16.0 certainly does not reference passlib anywhere so it is safe to leave out from the PKGBUILD - the fewer dependencies the better. Upstream accepted my cleanup patch here:

cguenther commented on 2016-12-05 13:43 (UTC)

@suridaj why does not exist anymore the dependency to the python-passlib?

suridaj commented on 2016-12-01 12:40 (UTC)

@zerophase, thank you for reporting. Conan 0.16.0 passes all tests with the new passlib 1.7.0 as can be seen here: Please check the new PKGBUILD and let me know if there are any problems.

zerophase commented on 2016-12-01 12:11 (UTC)

python-passlib has been updated to 1.7.0 on arch.

suridaj commented on 2016-11-26 02:30 (UTC)

Conan 0.15.0 tests fine with python-requests 2.12.1. The new PKGBUILD is up and a pull request is sent upstream.

suridaj commented on 2016-11-25 16:18 (UTC)

@xaver, thank you for the report. I will test conan 0.15.0 with the most recent python-requests and upload a new PKGBUILD.

xaver commented on 2016-11-24 17:45 (UTC)

conan: installing python-requests (2.12.1-1) breaks dependency 'python-requests<2.12.0'

suridaj commented on 2016-10-18 06:12 (UTC)

Thanks for the heads-up. I ran conan's test suite agains boto 2.43 with no problems. The updated PKGBUILD is here and I've also submitted a pull request upstream.

zerophase commented on 2016-10-18 04:58 (UTC)

python-boto 2.43 just came out. Will this package work fine with the current version?

suridaj commented on 2016-10-06 11:33 (UTC)

Thanks @flisboac, the AUR dependency resolution should now work with yaourt.

suridaj commented on 2016-09-28 21:15 (UTC) (edited on 2016-09-28 21:15 (UTC) by suridaj)

Hi @flisboac. I am on the road until the end of the week and unable to test your suggestion. I would rather that python-fasteners depends on python-monothonic than pushing this dep up the chain to conan. Of course when I get to Arch machine I will be sure to test this. In the meantime it would be of great help if you could test whether just pulling the conan package from AUR as is using pacman works. Namely, there is a yaourt bug that prevents it to resolve AUR dependencies of AUR packages (see so we need to see which of the two possibilities is the culprit.

flisboac commented on 2016-09-23 10:48 (UTC)

@suridaj Please take a look at this output from Yaourt: Two required packages are not installed, even when using an AUR helper like Yaourt. pacman does not automatically look for packages on AUR, and depends on package() appears to be an after-makepkg dependency declaration applicable only to pacman. Also, for some reason, Yaourt cannot deduce AUR dependencies based on the dependencies on the package, and because of that it needs an external `depends` in the PKGBUILD. It seems `python-fasteners` would need the same fix, and add a `depends=('python-monotonic')` line somewhere in the PKGBUILD. This is my suggestion: Follows the last lines of the installation process: ==> Continue installing conan ? [Y/n] ==> [v]iew package contents [c]heck package with namcap ==> --------------------------------------------------- ==> loading packages... resolving dependencies... warning: cannot resolve "python-patch=1.16", a dependency of "conan" warning: cannot resolve "python-fasteners>=0.14.1", a dependency of "conan" :: The following package cannot be upgraded due to unresolvable dependencies: conan :: Do you want to skip the above package for this upgrade? [y/N] error: failed to prepare transaction (could not satisfy dependencies) :: conan: requires python-patch=1.16 :: conan: requires python-fasteners>=0.14.1 ==> WARNING: Your packages are saved in /var/lib/yaourt/tmp/yaourt-tmp-flisboac

suridaj commented on 2016-09-14 08:27 (UTC) (edited on 2016-09-14 08:29 (UTC) by suridaj)

Hi @zerophase, If you use pacman and makepkg on their own it is usually expected you are going to manage AUR dependencies manually (e.g. see conan depends on python-patch and python-fasteners, while python-fasteners in turn depends on python-monotonic, and you need to get and install them from AUR one way or another. AUR helpers such as pacaur can do this kind of busywork for you. Just make sure you understand what is going to happen before you let a helper install anything from AUR: review relevant PKGBUILDs etc.

zerophase commented on 2016-09-14 07:43 (UTC)

Had to manually install python-patch, python-fasteners, and python-monotonic before package would install.