Arch Linux User Repository

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

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

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 =)

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.

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/build_py.py", line 127, in build_package_data srcfile in self.distribution.convert_2to3_doctests): AttributeError: 'Distribution' object has no attribute 'convert_2to3_doctests'

@silverhikari, generally, X-git packages should specify which version of X they provide, see https://wiki.archlinux.org/title/PKGBUILD#provides

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')

or

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

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?

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

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.

@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 :)

@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.

@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.

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?

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

@suridaj thanks for the help.

The problem fixed itself, the package got updated today.

@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: 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.

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?

@paragoumba thank you, I removed fakeroot from makedepends.

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

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

@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.

@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.

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/__init__.py", line 3252, in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3235, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pluginbase>=0.5' distribution was not found and is required by conan

Everything works perfectly now. Thanks for the quick response!

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

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.

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

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

The regression is solved, thanks!

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

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.

all ok now

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

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.

Please update conan to 1.15.1-2.

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

Pylint 2.3.1 has been released.

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: https://github.com/conan-io/conan/pull/4627 https://github.com/PyCQA/pylint/issues/2769

@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: https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages

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

ok... now ok

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

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

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

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

 pkgname=('conan')
-pkgver=1.2.1
+pkgver=1.2.3
 pkgrel=1
 pkgdesc="A distributed, open source, C/C++ package manager."
 arch=('any')
@@ -44,5 +44,5 @@ package() {
   install -m755 -d "${pkgdir}/usr/share/doc/conan"
   install -m644 contributors.txt "${pkgdir}/usr/share/doc/conan/"
 }
-md5sums=('1b51c1131a62b6c9d0bf718ae0c2e6a9'
+md5sums=('da83efce791546c14eaa4457969e0220'
          '07d5bb9453fc3bd90bb31f7c292983fd')

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!

Please do remove this upper limit.

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

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.

Yes, that worked. Thanks.

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

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

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 https://github.com/conan-io/conan/issues/2164 )

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?

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?

Conan 0.30.3 is out, however it does not work with python-astroid 1.6.0. Here is the bug: https://github.com/conan-io/conan/issues/2164

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.