Package Details: conan 2.11.0-1

Git Clone URL: https://aur.archlinux.org/conan.git (read-only, click to copy)
Package Base: conan
Description: A distributed, open source, C/C++ package manager.
Upstream URL: https://conan.io
Keywords: conan
Licenses: MIT
Conflicts: conan1
Provides: conan
Submitter: suridaj
Maintainer: suridaj
Last Packager: suridaj
Votes: 76
Popularity: 1.49
First Submitted: 2016-08-21 01:35 (UTC)
Last Updated: 2025-01-12 23:08 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »

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/semver.py)

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/metadata.py", line 524, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.9/importlib/metadata.py", 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.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 13 Next › Last »