** Changed in: apt (Ubuntu Xenial)
Status: Confirmed => Won't Fix
** Changed in: apt (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.lau
** Changed in: apt (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: apt (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu X
That is a regression of sorts caused by a sleight of hand used to avoid
another bug. The commit in question would be
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=446551c8ffd2c9cb9dcd707c94590e73009f7dd9
although the involved code changed in the mean time the general idea
remains the same:
Tested precise, trusty, xenial, and yakkety. Looks like this bug was
introduced between precise and trusty (that is, it works correctly in
precise's 0.8.16~exp12ubuntu10, but not trusty's 1.0.1ubuntu2 or later).
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
**
(To test in older versions, change the copy:// to a file:/ because derp)
--
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/1589204
Title:
apt-get dist-upgrade and apt full-upgrad
Simple reproducer:
# cat /etc/apt/sources.list.d/test.list
deb [trusted=yes] copy://home/adconrad/apt-test ./
# cat /home/adconrad/apt-test/Packages
Package: apt
Priority: important
Section: admin
Architecture: amd64
Version: 99:1
Depends: test (>= 99:1)
# apt-get update
# apt-get dist-upgrade |
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
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/
Sorry, it is apt-get upgrade that shows 1 not to upgrade.
Description corrected.
** Description changed:
I have the situation where a package cannot be upgraded because of missing
dependencies. However
sudo apt-get dist-upgrade
and
sudo apt full-upgrade
and
sudo apt upgrade
all sh
Hi, thanks for your bug report. I'm not sure I understand it, though:
First you write that "sudo apt upgrade" shows 0 upgrades, then it's the
only one that shows 1.
Could you fix this please?
I myself have never seen this AFAIK.
--
You received this bug notification because you are a member of
9 matches
Mail list logo