Cannot test packages in proposed or other archives
Bug #1564500 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
cloud-init/jujud install packages from the the ubuntu archive, a mirror, or from cloud-tools. it is not possible to test the proposed pocket or other archives.
It is not possible to detect breaking packages changes in proposed.
It is not possible to test new mongodb packages that are in development
| affects: | juju-core → juju |
Revision history for this message
| Nicholas Skaggs (nskaggs) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.1.0 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #2 |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| importance: | High → Medium |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
A conversation with the core team came up with the following:
Running your own apt mirror -- it should be possible without any changes to juju. Add what you want and it should work
A better solution was to modify juju to allow adding a new apt source -- a ppa or proposed or your own archive, that juju would include in apt sources and thus could pull from at a higher priority.