@mathew-hodson It's in git, and will make it's way in in a future
release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1821308
Title:
apt-get upgrade ignores pinning
This bug was fixed in the package apt - 1.0.1ubuntu2.23
---
apt (1.0.1ubuntu2.23) trusty; urgency=medium
* Fix regression in pinning of local-only package versions (LP:
#1821308)
-- Julian Andres Klode Mon, 25 Mar 2019 11:22:42
+0100
** Changed in: apt (Ubuntu Trusty)
The "Check that local-only versions can be pinned correctly" test should
also be added to the development branch to make sure we don't regress
this behaviour again in the future.
I don't see an equivalent test there.
--
You received this bug notification because you are a member of Ubuntu
Touch
The test case also passed successfully on the autopkgtest for
1.0.1ubuntu2.23
Check that local-only versions can be pinned correctly (LP: #1821308)
Test for successful execution of apt-cache policy coolstuff … PASS
Test for correctness of file /tmp/tmp.PtSrwfN8WU/rootdir/tmp/testsuccess.output
…
> Well, the version of apt is irrelevant. The version of libapt-pkg4.12 is
> what matters - is that one upgraded too?
I didn't see a hint this package should be updated.
Have updated libapt-pkg4.12 now (to 1.0.1ubuntu2.23) and there is no false
downgrade anymore.
Thanks!
--
You received this
Well, the version of apt is irrelevant. The version of libapt-pkg4.12 is
what matters - is that one upgraded too?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1821308
Title:
I have enabled the "proposed" repository and installed apt
"1.0.1ubuntu2.23". Though, even after another "apt-get update", "apt-get
upgrade" still wants to downgrade my "burp" package.
It's noticeable that "policy's output" now contains a different
"Candidate" version number.
# dpkg -l apt
Hello larsen, or anyone else affected,
Accepted apt into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.23 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+ Pinning on local-only package versions is ignored, causing them to be
upgraded.
+
+ [Test case]
+ The integration tests include an automated test case that contains a package
called coolstuff in three versions. We are specifying a Pin for the installed
> (1) burp 2.0.54 is not in a repo, only locally installed
That is correct.
Output as requested:
# apt-cache policy burp
burp:
Installed: 2.0.54-1
Candidate: 2.0.54-1
Package pin: 2.0.54-1
Version table:
*** 2.0.54-1 1000
100 /var/lib/dpkg/status
1.3.48-4.1 1000
** Tags added: id-5c94c4fd0a7a583861e90c88
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1821308
Title:
apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22
FWIW, reading the code for trusty, I assume that
(1) burp 2.0.54 is not in a repo, only locally installed
(2) hence the code that checks whether the specified pin can be valid says "no"
and ignores it, because it does not find any source, and thus concludes that
the package only has available
Please provide apt-cache policy output, and there are probably other
pinnings in your preferences files.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
apt-cache policy burp, that is
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1821308
Title:
apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22
Status in apt
14 matches
Mail list logo
