snapcraft 3.9.7+ ignores the petname Python package when referred to as a requirement in my Python part
Bug #1860768 reported by
Pen Gale
This bug report is a duplicate of:
Bug #1860884: Python plugin: paths for from the snapcraft snap in sys.path break dependencies.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
One of the Python tools that we build as part of the MicroStack path specifies petname in its requirements.txt.
When building with snapcraft 3.9.7+, petname is not added to the built snap. The part in question (launch) has not changed, and other Python packages specified in other parts' requirements do get added.
This is kind of an odd one, because I'm able to build a much simpler snap that contains petname, and I know that the snapcraft snap uses petname. Per today's conversations, I am working on getting more logging and info on this, and will post it at my earliest opportunity.
Changed in snapcraft: | |
status: | New → Confirmed |
To post a comment you must log in.
This seems to be related to LP: #1860884 but nothing has changed in snapcraft for this to be triggered only now since our sitecustomize logic has remained static pretty much since 2017