Control: clone -1 -2 -3 Control: retitle -2 please update astroid to >= 2.2.0 Control: tags -2 + fixed-upstream Control: reassign -2 python3-astroid Control: retitle -3 please update lazy-object-proxy to >= 1.4.0 Control: tags -3 + fixed-upstream Control: reassign -3 python3-lazy-object-proxy Control: block -1 by -2 -3
Hi, On Wed, Nov 23, 2016 at 06:47:07PM +0100, Paolo Greppi wrote: > Until we find a better home for it, here is a git repo link: > https://gitlab.com/simevo/debian-conan This repository cannot be accessed without credentials. > Any help or suggestion are welcome. I also looked into this briefly for conan 1.20.3 and figured that we have the following dependency issues in unstable: Missing packages: * conan requires node-semver==0.6.1, but I couldn't find it in unstable. This one is bad. node-semver ships a module called "semver". This conflicts with the existing python3-semver, which contains a "semver" module with incompatible API. Options: * Make conan stop using node-semver. * Use a vendor copy of node-semver. (<- bad) * Declare conflicts with python3-semver. (<- very bad) * conan requires patch-ng==1.17.1, but I couldn't find it in unstable. This is a fork of https://github.com/techtonik/python-patch done by conan people. Neither is packaged for Debian. Thankfully, they renamed the Python module from "patch" to "patch_ng". Given that it is forked by conan, vendoring could be considered. Dependencies in need of new upstream releases: * conan requires astroid>=2.2.0, but unstable has 2.1.0-2. Cloned bug -2 for this. * conan requires lazy-object-proxy==1.4.*, but 1.3.1-2. Cloned bug -3 for this. Conan needs porting to newer dependencies: * conan requires distro<1.2.0, but unstable has 1.3.0-2. * conan requires pluginbase<1.0, but unstable has 1.0.0-2. * conan requires six<1.13.0, but unstable has 1.13.0-1. Hope this helps whomever tries to pick this up. Helmut
