canonical-ubuntu-qa team mailing list archive
-
canonical-ubuntu-qa team
-
Mailing list archive
-
Message #00220
[Bug 2009191] [NEW] autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1032314:
Package: autopkgtest
Severity: normal
X-Debbugs-Cc: paride@xxxxxxxxxx
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).
** Affects: autopkgtest (Ubuntu)
Importance: Undecided
Assignee: Paride Legovini (paride)
Status: In Progress
** Affects: autopkgtest (Debian)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #1032314
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032314
** Changed in: autopkgtest (Debian)
Remote watch: None => Debian Bug tracker #1032314
--
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:
In Progress
Status in autopkgtest package in Debian:
New
Bug description:
Imported from Debian bug http://bugs.debian.org/1032314:
Package: autopkgtest
Severity: normal
X-Debbugs-Cc: paride@xxxxxxxxxx
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
Follow ups
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Brian Murray, 2024-07-16
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Łukasz Zemczak, 2024-02-12
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Bug Watch Updater, 2023-06-15
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Paride Legovini, 2023-04-20
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Paride Legovini, 2023-04-20
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Bug Watch Updater, 2023-03-29
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Launchpad Bug Tracker, 2023-03-20
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Launchpad Bug Tracker, 2023-03-14
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Launchpad Bug Tracker, 2023-03-14
-
[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release
From: Paride Legovini, 2023-03-03