Package Details: conan 1.10.2-1

Git Clone URL: https://aur.archlinux.org/conan.git (read-only)
Package Base: conan
Description: A distributed, open source, C/C++ package manager.
Upstream URL: https://conan.io
Licenses: MIT
Submitter: suridaj
Maintainer: suridaj
Last Packager: suridaj
Votes: 27
Popularity: 0.988250
First Submitted: 2016-08-21 01:35
Last Updated: 2018-12-17 17:32

Latest Comments

1 2 3 4 5 6 Next › Last »

suridaj commented on 2018-11-01 16:35

@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

YeeP commented on 2018-11-01 14:57

@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

ok... now ok

suridaj commented on 2018-10-29 21:58

@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

!! 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

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

Eremiell commented on 2018-04-12 16:13

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

suridaj commented on 2018-01-24 12:21

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

Please do remove this upper limit.

greyltc commented on 2017-12-25 09:30

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