component mismatch with probert-network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
probert (Ubuntu) |
Fix Released
|
Low
|
Paride Legovini | ||
Focal |
Fix Released
|
Low
|
Unassigned | ||
Groovy |
Fix Released
|
Low
|
Paride Legovini |
Bug Description
[impact]
the binary probert package depends on probert-network, and while probert is in main, probert-network is in universe.
probert was MIR in bug 1830347
the probert-network package was promoted to main in Eoan at version 0.0.17:
https:/
however in focal, version 0.0.17build1 the probert-network package is in universe, and all versions after that have probert-network in universe
[test case]
check component of probert binary packages, e.g.:
$ rmadison -s focal probert probert-network
probert | 0.0.18 | focal | source, all
probert-network | 0.0.18 | focal/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x
reverse-depends -r focal probert-network
Reverse-Depends
* probert
* subiquitycore
[regression potential]
a no-change rebuild carries common regression potential, e.g. failure to build and/or behavior changes, due to changes in compiler, shared libs, etc.
[scope]
the probert-network binary package should be in main for focal and groovy.
[other info]
this was discussed during the MIR team mtg:
https:/
the no-change rebuild is needed as the current probert version is in focal-release, so a new version is needed in focal-updates to promote the probert-network binary package to main.
Related branches
- Ubuntu Core Development Team: Pending requested
-
Diff: 26 lines (+5/-1)2 files modifiedSTRUCTURE (+2/-1)
supported-installer-server (+3/-0)
- Christian Ehrhardt : Approve
-
Diff: 26 lines (+5/-1)2 files modifiedSTRUCTURE (+2/-1)
supported-installer-server (+3/-0)
probert no-change rebuild uploaded to focal queue as version 0.0.18build1