Python setup.cfg wrongly applied to all python package dependencies
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
New
|
Undecided
|
Sergio Schvezov |
Bug Description
This is just a report of the problem discussed in [1] which I think is still present (or something similar).
The problem is that for rapid-photo-
I created a (stupid?) adaptation of the author's defunct snapcraft.yaml from [2] which I put at [3].
On a clean digital-ocean applet (Ubuntu 17.10 server) a "snapcraft" call (both with current HEAD and with current "snap install snapcraft --classic" results in an error while installing the first python package, in this case pip:
[1] https:/
[2] http://
[3] https:/
Related branches
Changed in snapcraft: | |
assignee: | nobody → Sergio Schvezov (sergiusens) |