Package Details: conan 2.2.2-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
Licenses: MIT
Conflicts: conan1
Submitter: suridaj
Maintainer: suridaj
Last Packager: suridaj
Votes: 67
Popularity: 0.008800
First Submitted: 2016-08-21 01:35 (UTC)
Last Updated: 2024-04-11 20:21 (UTC)

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

jkl commented on 2024-04-15 03:41 (UTC) (edited on 2024-04-15 03:45 (UTC) by jkl)

@evorster @suridaj Hmm weird because the PKGBUILD works fine for me with the original URL, perhaps it is hitting an anti-DDOS captcha in some cases and may be worth changing. That is however a different problem then the aforementioned issue with the broken git master branch. Do a clean git clone https://aur.archlinux.org/conan to see the error.

evorster commented on 2024-04-14 05:36 (UTC)

This package is not getting the proper source, and then not building. If you update the source to this, it downloads and builds properly:

source=("${pkgname}-${pkgver}.tar.gz::https://github.com/conan-io/conan/archive/refs/tags/${pkgver}.tar.gz")

evorster commented on 2024-04-13 11:53 (UTC)

Is this headless thing the reason I am getting this weird error?

[evert@Evert aur]$ rm -rf conan/
[evert@Evert aur]$ yay -S conan
AUR Explicit (1): conan-2.2.2-1
:: (1/1) Downloaded PKGBUILD: conan
 -> error merging /mnt/int/system/aur/conan: fatal: No current branch.

jkl commented on 2024-04-12 19:30 (UTC)

@suridaj The git repo master branch was not updated and still points to 9b9ad6c6d (2.1.0), hence a git pull in an existing repo does not work and a clone ends up with a detached HEAD.

vedranmiletic commented on 2024-03-26 10:19 (UTC)

@suridaj Just noticed that conan.io website download page is wrong, 2.1.0 is not the latest release, but 2.2.2 posted on GitHub releases: https://github.com/conan-io/conan/releases/tag/2.2.2

suridaj commented on 2023-09-06 14:41 (UTC) (edited on 2023-09-06 14:42 (UTC) by suridaj)

@ruabmbua Thank you for the suggestion. Most packages only specify a dependency version if they could not run without it, and not because they would need to be rebuilt when a dependency changes. This is why I will not fix Python version for Conan.

At most, I could bump the release number of Phyton packages to trigger a rebuild, but that would still help only those users who are updating their whole system at the same time. The current consensus is it is on the user to manage and build the packages installed from outside of Arch repos.

You may consider using rebuild-detector to see if anything needs to be rebuilt after an update.

ruabmbua commented on 2023-09-06 11:02 (UTC)

I wonder if that could be improved by explicitly requiring the specific python version as a dependency in the aur packages?

suridaj commented on 2023-09-06 11:00 (UTC)

@ruabmbua, glad you solved it. That kind of error may occur after Python gets a version bump. Then Python libraries from AUR need to be rebuilt because their installation directory needs to be changed from eg. /usr/lib/python3.10/site-packages to /usr/lib/python3.11/site-packages.

ruabmbua commented on 2023-09-06 09:15 (UTC)

Never mind, solved it by clean building the python-patch-ng package and reinstalling.

ruabmbua commented on 2023-09-06 09:13 (UTC)

Seems like there is a new dependency missing error:

ModuleNotFoundError: No module named 'patch_ng

Is this a problem just for me, or is anyone else hitting it?

1 2 3 4 5 6 .. 12 Next › Last »