It seems you branched from the wrong base branch. Presumably you used ubuntu/noble-devel instead of ubuntu/devel.
As a general rule it's preferred to have an actual bug filed against the package on Launchpad rather than just having the MP, as the bug reference can (and should) be added to the changelog. In addition, given the branch issue I'm guessing you'd like to see this fixed in Noble rather than just in the upcoming Plucky. In that case, you'll need to follow the SRU guidelines as documented there: https://canonical-sru-docs.readthedocs-hosted.com/en/latest/
The general outline of the process is the following:
* File a LP bug against the package using the documented template
* Fix the bug in all supported releases down to the target release (here it'd be Plucky, Oracular and Noble). You'll need 3 separate sponsored uploads, but if you prepare all 3 uploads at the same time a single sponsor will usually process them all at once.
* Wait for the SRU team to review and accept your uploads
* Verify your upload using the test plan you provided
* Wait for the SRU team to move the package into the release pocket.
Feel free to ask a new review from ubuntu-sponsors once this MP is fixed.
Hi!
It seems you branched from the wrong base branch. Presumably you used ubuntu/noble-devel instead of ubuntu/devel.
As a general rule it's preferred to have an actual bug filed against the package on Launchpad rather than just having the MP, as the bug reference can (and should) be added to the changelog. In addition, given the branch issue I'm guessing you'd like to see this fixed in Noble rather than just in the upcoming Plucky. In that case, you'll need to follow the SRU guidelines as documented there: /canonical- sru-docs. readthedocs- hosted. com/en/ latest/
https:/
The general outline of the process is the following:
* File a LP bug against the package using the documented template
* Fix the bug in all supported releases down to the target release (here it'd be Plucky, Oracular and Noble). You'll need 3 separate sponsored uploads, but if you prepare all 3 uploads at the same time a single sponsor will usually process them all at once.
* Wait for the SRU team to review and accept your uploads
* Verify your upload using the test plan you provided
* Wait for the SRU team to move the package into the release pocket.
Feel free to ask a new review from ubuntu-sponsors once this MP is fixed.