private snap builds lack manifest.txt
Bug #2030668 reported by
Dimitri John Ledkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpad-buildd |
New
|
Undecided
|
Unassigned |
Bug Description
https:/
builds private snaps without manifest.txt, which is quite annoying given one doesn't know any package versions of staged packages, breaking automatic rebuild notifications from snapstore for private snap builds that are published in the global store.
Is there a way to somehow turn on manifest.txt? especially when embargoed builds will later be made public elsehow (i.e. one can get staged .deb packages from Pro archives)
To post a comment you must log in.
This is very unfortunately, and makes me want to build private fips snaps outside of launchpad, such that i can generate snap with manifest.txt which has correct package versions that match Pro fips archive published versions.