Please provide an clear Test Case and describe the possible Regression Potential for this bug in the bug description [1]. I see a possible test case in comment #1, but I'd like it to be made clear that this is what is expected to be performed to verify the upload.
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ** Also affects: autopkgtest (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: autopkgtest (Ubuntu Mantic) Status: New => Incomplete -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2009191 Title: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release Status in autopkgtest package in Ubuntu: Fix Released Status in autopkgtest source package in Mantic: Incomplete Status in autopkgtest package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1032314: Package: autopkgtest Severity: normal X-Debbugs-Cc: par...@debian.org Adding a pocket via --apt-pocket=<POCKET> causes the _get_default_release() function to be called. This is needed to construct the sources.list entry for the pocket, which will be in the form of: deb <mirror> <default_release>-<POCKET> ... The _get_default_release() function caches the detected default release in the default_release variable, which is the same variable used to store the --apt-default-release=<RELEASE> value. This has no effect when only one test is present in d/t/control, but when more than one test is present the tests after the first will have unwanted/wrong pinning (as if --apt-default-release was specified). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009191/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
