Juju version cannot be set to 1.19.4
Bug #1325074 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Curtis Hovey | ||
Bug Description
1.19.3 is released, but the gobot fails my branch that sets the version to 1.19.4
https:/
This may related to the recent changes that added support for alpha/beta. We had to rollback the version because 1.18.0 throws a wobbly when the streams metadata contains a next stable with letters in the version.
Related branches
lp://qastaging/~sinzui/juju-core/inc-1.19.4
- Juju Engineering: Pending requested
-
Diff: 29 lines (+3/-3)2 files modifiedscripts/win-installer/setup.iss (+1/-1)
version/version.go (+2/-2)
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in juju-core: | |
| assignee: | nobody → Curtis Hovey (sinzui) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| importance: | Critical → High |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
the test suite knows we cannot replace a published version of juju. So when devel gets updates, 1.19.3 is built, it is rejected because 1.19.3 really exists. The unit tests are not affected by this, just the substrate and function test are using the release 1.19.3 juju and tools.