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.005627
First Submitted: 2016-08-21 01:35 (UTC)
Last Updated: 2024-04-11 20:21 (UTC)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12

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 https://bbs.archlinux.org/viewtopic.php?id=207502) 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: http://pastebin.com/XM27UDSz 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: http://pastebin.com/u9D3fXSK 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 https://bbs.archlinux.org/viewtopic.php?pid=1543884#p1543884). 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.