component mismatch with probert-network

Bug #1890301 reported by Dan Streetman
14
This bug affects 1 person
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://launchpad.net/ubuntu/eoan/amd64/probert-network/0.0.17

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://irclogs.ubuntu.com/2020/08/04/%23ubuntu-meeting.html#t14:59

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

Revision history for this message
Dan Streetman (ddstreet) wrote :

probert no-change rebuild uploaded to focal queue as version 0.0.18build1

Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Dan, or anyone else affected,

Accepted probert into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/probert/0.0.18build1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in probert (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed verification-needed-focal
Revision history for this message
Dan Streetman (ddstreet) wrote :

for focal, there is nothing to verify as this is just a rebuild for bookkeeping purposes, i.e. to move the package in -updates into the main component. So marking this as verified for focal.

@doko I'm not sure if you want to change the component while the version is still in -proposed or wait until it's in -updates.

tags: added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal
Changed in probert (Ubuntu Focal):
importance: Undecided → Low
Changed in probert (Ubuntu Groovy):
importance: Undecided → Low
Changed in probert (Ubuntu Focal):
assignee: nobody → Matthias Klose (doko)
Changed in probert (Ubuntu Groovy):
assignee: nobody → Matthias Klose (doko)
Revision history for this message
Dan Streetman (ddstreet) wrote :

@doko also I set the owner to you, for the archive-admin component change part of this, if that's ok. thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package probert - 0.0.18build1

---------------
probert (0.0.18build1) focal; urgency=medium

  * no-change rebuild to allow probert-network component change to main
    (LP: #1890301)

 -- Dan Streetman <email address hidden> Tue, 04 Aug 2020 11:30:19 -0400

Changed in probert (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for probert has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

After my recent debugging and proposal of fixes for Germinate today Paride got to me and we tracked down this case as well.

I'll explain in the MIR Team meeting for the curious.
For this particular case paride will prepare a seed change that will fix things.

Changed in probert (Ubuntu Groovy):
assignee: Matthias Klose (doko) → Paride Legovini (paride)
Changed in probert (Ubuntu Focal):
assignee: Matthias Klose (doko) → nobody
Revision history for this message
Paride Legovini (paride) wrote :
Revision history for this message
Paride Legovini (paride) wrote :
Changed in probert (Ubuntu Groovy):
status: New → Fix Committed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Both merged

Changed in probert (Ubuntu Groovy):
status: Fix Committed → Fix Released
Changed in probert (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.