Not sure who all the upstream(s) involved might be, but from my personal
PoV at least you can add all the options you like… the topic gets harder
if we talk defaults & changing (e.g.) the lists completely (like that
tabular verbose-explosion thingy from apk or whatever it was). At some
point it
Geekley I personally agree and would go a lot further and hide even most
dependencies (you don't really care which libraries you are installing,
just about choices made, e.g. if there's an a | b dependency it should
tell you that it picked a).
So if you want to think about it that terse mode
In the proposed fix, will there be some sort of flag and/or
configuration for apt and apt-get to let me NOT see this list of
"deferred due to phasing" packages? I agree it's important to list them
for users who want to see it, but it's also important to not bloat the
output with a bunch of extra
This bug was fixed in the package apt - 2.7.11
---
apt (2.7.11) unstable; urgency=medium
[ David Kalnischkies ]
* Remove erroneous -a flag from apt-get synopsis in manpage
* Support -a for setting host architecture in apt-get source -b
[ Julian Andres Klode ]
* For
2.7.11 is in proposed now.
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Committed
--
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/1988819
Title:
When apt
Proposed fix in:
https://salsa.debian.org/apt-
team/apt/-/merge_requests/327/diffs?commit_id=483e3b5c49762306c0a9f54117fd70cff43af4be
The corner case with kept back packages not due to phasing ends up with
a notice before the prompt:
Reading package lists...
Building dependency tree...
One thing I just noticed is that if you have something like gnome-shell
and mutter where gnome-shell depends on the new mutter and only mutter
is "not for us" we end up with something like:
The following packages have been kept back:
gnome-shell gnome-shell-common mutter
with phasing specific
Generally for reproducing issues I set Phased-Update-Percentage to 0 on
the packages the user had phased so it's independent of machine-id, it's
not been a problem in my experience to reproduce issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@juliank Thanks for the tip about machine id. May I also ask, for
repeatability, is there an official/supported way to run (unit) tests on
the upgrade logic alone, say, by feeding `/var/lib/dpkg/status`, index
files and maybe some environment variables/APT::* preferences to `apt-
get` and then
I did not make any changes to the design when moving it from Update-
Manager in apt, it's been this way for 10 years now, it's a proven
concept.
The initial implementation used and md5 but the math gets complex when
dealing with 128 bit integers.
You can easily override the machine-id for apt by
To add a data point and save others from preventable headaches, I encountered a
related bug and reported it here:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2017399
If anyone cares, here are my two cents regarding phased updates:
My vote is to remove this "phased updates" feature until the UI can be
fixed. Right now I run `apt update` and it tells me "N packages can be
upgraded", then I run `apt upgrade` and it tells me no packages will be
upgraded because "N packages are held back". There is no mention of
"phased
After further investigation, I would say that "Discover" wants to
upgrade a package (libmm-glib0) notwithstanding the fact that it is
phased and that apt does not want to upgrade it.
Funny enough, Discover does not indicate the other phased packages (it
is up to 24!) as upgradable.
--
You
There is a further problem, I do not know if it should be a separate
issue.
The updates icon in the system tray now appears also when there are in
fact no updates that can be applied. Don't know if this actually depends
on the presence of updates that are phased out or on the presence of
Ubuntu
** Summary changed:
- When apt keeps back packages due to phased updates, it should say nothing
+ When apt keeps back packages due to phased updates, it should list them
separately
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
15 matches
Mail list logo
