snapcraft APT sources checking too strict
Bug #1583236 reported by
Chad Miller
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
APT exits with nonzero value for some insignificant reasons, like The Google archive for Chrome browser using an ancient hash function, or a post-upgrade PPA not supporting yakkety yet.
snapcraft should not fail for silly warnings from APT.
| Changed in snapcraft: | |
| status: | New → Confirmed |
Revision history for this message
| canis-merda (canis-merda) wrote | #1 |
To post a comment you must log in.
One way to get around this is to use an apt.conf file. You can point to it with the APT_CONFIG env var.
To get around the old hash problem, you might try putting "Acquire::ForceHash "sha1";" in said apt.conf file.