The apt update is from kinetic, the development release. What are you
doing?
The question is what installs them. Certainly it's not apt itself doing
that unless you have very weird pinning in place.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
In your libmysqlclient21 example everything seems to be working
correctly so I don't understand why you post that.
- you are eligible for 8.0.29-0ubuntu0.22.04.3
- you force downgrade to 8.0.29-0ubuntu0.22.04.2
- you upgrade once again to 8.0.29-0ubuntu0.22.04.3
- no higher version available in fi
** Changed in: apt (Ubuntu Jammy)
Status: Confirmed => In Progress
** Description changed:
- On an Ubuntu 22.04 desktop system created using the current installation
- image without enabling package updates over the network, installing the
- package libudev1 results in a large number of cr
** Changed in: apt (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1
--
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/1974196
Title:
Installing libudev1 on a new Jammy instal
** No longer affects: apt (Ubuntu Impish)
--
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/1978125
Title:
apt ignoring pin/block/hold files in preferences.d for snapd
Status in
Please note that this is not the test plan documented in the bug. But
glad this worked for you, I was not sure it was still reproducible,
hence why there's a solver dump based test case in the regression test
suite.
But your test is valid too, the test suite still needs to pass, but
failure to pas
*** This bug is a duplicate of bug 1979244 ***
https://bugs.launchpad.net/bugs/1979244
As you can see in your output a newer version of apt is available. It
fixes this bug.
** This bug has been marked a duplicate of bug 1979244
libssl-dev : Depends: libssl3 (= 3.0.2-0ubuntu1.1) but 3.0.2-0
Overloaded server is not a bug in apt. There are no mirrors for ddebs,
so the overload is not very surprising. You should not have any need to
download ddebs, and you certainly don't want to abuse the resources with
automatic repeated downloads.
** Changed in: apt (Ubuntu)
Status: Confirmed
Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.
--
You received th
** Changed in: apt (Ubuntu)
Status: In Progress => Incomplete
--
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/1981672
Title:
apt phased out broken code, missing document
It's documented in the discourse thread (Discourse is where Ubuntu
documentation lives) You have not provided evidence that it does not
work for you. APT itself has test cases that proof that *it does* work.
Note that newer apt versions (2.4.6, 2.5.1) will install more phased
updates
- as phasing
I recall/see again a mention of aptitude:
aptitude and aptitude-robot are not supported components. They are
packages provided by the community as part of the universe repository.
While the implementation of phased updates in apt versions prior to
2.4.6 would work there, the current version does
I have added an aptitude task and set the tasks accordingly to indicate
that this is a feature request for aptitude. The needed API will surface
at some point in APT due to some refactoring, likely in the 23.04 cycle.
aptitude could then consume that API in its resolver and make choices to
keep ba
To make it clear, my suggestion for a workaround for jammy would be to
have
_config->CndSet("APT::Get::Phase-Policy", true);
somewhere in the aptitude code. It is unclear to me if aptitude will
break then as phased versions get their pin limited to 1, apt certainly
does if there's a mismatch as i
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
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/1976233
Title:
"File has unexpected size" error on Focal ddebs r
** Package changed: apt (Ubuntu) => ddeb-retriever
** Changed in: ddeb-retriever
Status: Invalid => 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/1976233
Titl
This string does not exist in apt or any of the other Ubuntu code I have
checked out. If you can reproduce it, do check where it is coming from
and reassign it there.
** Package changed: apt (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notif
I assume this is for the new implementation in 2.4.6. This is
unfortunately not feasible as the code works the same way as upgrades
held back for other reasons.
Some hacks could be added that improve this in most situations but that
also requires significant refactoring and does not solve all the
Will have a look at the normal hold situation, but would like to know
where you see the disagreement in numbers - is it apt update and apt
full-upgrade?
What does motd / update-notifier say?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Verified.
For bionic I ran
mmdebstrap -v --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg
--aptopt='Acquire::http::proxy "http://localhost:8000/";;' bionic bionic-
proposed http://archive.ubuntu.com/ubuntu 'deb
http://archive.ubuntu.com/ubuntu/ bionic-proposed main'
to enable proposed an
Note for reader: The wrong version is in the list of packages to be
removed.
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Jarno, you do realize that you need to upgrade libapt-pkg6.0, not apt?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may rem
But I do believe it's simply the wrong package being upgraded here. The
new apt package removes the conffiles the old library version needs, so
it doesn't protect anything, so we need to make sure that apt Breaks
libapt-pkg6.0 (<< 1.6.15) [or Depends on >= 1.6.15, whatever ends up
nicer).
--
You
*** This bug is a duplicate of bug 1976233 ***
https://bugs.launchpad.net/bugs/1976233
** This bug has been marked a duplicate of bug 1976233
"File has unexpected size" error on Focal ddebs repository
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
Deleted the apt task instead so comments don't go apt subscribers for
all eternity.
** No longer affects: apt (Ubuntu)
** No longer affects: apt (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
h
@Jarno OK I was wrong, new apt pulls in new libapt-pkg5.0. What happens
instead is that the cache built by the old version does not include
information about available kernels, we essentially need to bump the
cache minor version, if we can do that, I don't know, I lost track of
what major version i
** Changed in: apt (Ubuntu)
Status: Incomplete => 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.launchpad.net/bugs/1983730
Title:
opt out of phased updates - still shown
Statu
So I held back fdroidserver and squid on my system. apt update tells me:
49 packages can be upgraded. Run 'apt list --upgradable' to see
them.
When I run dist-upgrade I get:
The following packages have been kept back:
fdroidserver python-apt-dev python3-apt squid
The following
Wondering where the symlink went
** Changed in: grub2 (Ubuntu)
Status: Incomplete => New
** Package changed: grub2 (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
Just to be clear: apt.conf(5) is not the definitive source, that is
(fsvo reference) in /use/share/doc/examples/configure-index. The manual
page only documents popular options whereas the index lists them all
(apt test suite type checks against it).
Phased updates are documented in apt_preferences
Yeah many options are not really for end users though so it's not all
encompassing.
--
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/1986660
Title:
Phased update configuration f
Reassigning to correct package, and confirmed. So while [arch=amd64]
works fine [signed-by=...] does not which is odd. Neither are *properly*
supported in software-properties: sources.list options are not exposed
at all; it's unclear what happens if you modify them.
** Package changed: update-mana
I can reproduce this on kinetic. I get sent a 2a02:908:2812:7d20::/64
prefix via RA with "valid lifetime" and ""preferred lifetime" set to 0,
every 3s. Instead of the prefix being deleted from the interface, it's
lifetime is set to 1s and then expires every second, causing regular
"connection chang
With systemd-networkd on the 20.04 server, the /64 prefix does not
bounce between 0s and 1s, but stays at 0s, but is not removed (nor is
the /128).
** Tags added: rls-kk-incoming
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Also affects: systemd (Ubuntu)
Importance
We believe the kernel handles RAs itself, adding a task for it.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launc
** Tags removed: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981109
Title:
server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
ev
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
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/1988145
Title:
Couldn't create temporary file /tmp/apt.conf.fsIutr for
Closing this as invalid. The analysis is flawed, the configuration file
is created by user _apt, not root, the call is literally just mkstemp()
with the path given in the error message, or rather a template, so there
is no bug in apt here.
It's more likely to be wrong permissions on /tmp preventin
Reverting the systemd SRU broke existing images.
** Package changed: apt (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988563
Title:
packag
We can't really store reasons for why something is kept back. And if we
managed to do that, we'd end up with an untranslated line in the middle
of the output for every non-English locale until it's translated and apt
updated (it does not use language packs).
--
You received this bug notification
** Description changed:
- I just do-release-upgraded from Jammy to Noble on a pretty minimal
- server.
+ [Impact]
+ Upgrades from jammy to noble sometimes end up without systemd-resolved being
installed, breaking networking as the system already migrated to resolved in
jammy and now it disappear
Public bug reported:
[Impact]
libraries become marked as manually installed after transitioning to t64
package names as we forgot to transition the automatically installed bit.
Before:
root@m:~# apt-mark showmanual
base-files
bash
bsdutils
cloud-init
dash
diffutils
eatmydata
findutils
grep
gzip
Fix committed in ubuntu/main
** Summary changed:
- Package wasn't installed on upgrade from Jammy to Noble
+ systemd-resolved wasn't installed on upgrade from Jammy to Noble
** No longer affects: systemd (Ubuntu)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Fix Committe
** Description changed:
- ⚠️ Only land this in the release pocket after PPAs have been resigned
+ ⚠️ Only land this in the release/updates pocket after PPAs have been
+ resigned
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development serie
The same caveat applies to -updates, but there is a question of whether
we should ship 2.8.0 as this or make 2.8.0 different, I did not push a
tag for it yet.
i.e. given that this is a stable release update that will break PPAs
users currently have warnings for, it might make sense to make it brea
** Changed in: apt (Ubuntu Oracular)
Status: New => Fix Committed
** Tags added: regression-proposed
--
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/2073126
Title:
More
** Description changed:
⚠️ Only land this in the release/updates pocket after PPAs have been
resigned
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development series for 2.8, and this is the
only change left for the 2.8 release, safe
** Description changed:
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning to an error, breaking them.
We also revoked additional ECC curves, which may
** Description changed:
+ (This is uploaded to noble as 2.8.1 per
+ https://wiki.ubuntu.com/AptUpdates)
+
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2075968
Title:
cannot login after upgrade from xubuntu 22.04 to
** Description changed:
⚠️ Only land this in the release/updates pocket after PPAs have been
resigned
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development series for 2.8, and this is the
only change left for the 2.8 release, save
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2036467
Title:
Resizing cloud-images occasionally fails due to superblock checksum
mis
Public bug reported:
I'm asking for a blanket FFe for the experimental 3.0 solver that can be
used with the --solver 3.0 argument. It's mostly really bug fixing
that's happening, I'm not sure what would constitute a feature at this
point*, but the changes are still fairly big as I'm refactoring it
** Description changed:
- I'm asking for a blanket FFe for the experimental 3.0 solver that can be
- used with the --solver 3.0 argument. It's mostly really bug fixing
- that's happening, I'm not sure what would constitute a feature at this
- point*, but the changes are still fairly big as I'm ref
** Summary changed:
- [FFe] APT 24.04 crypto policy update
+ APT 24.04 crypto policy update
--
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/2055193
Title:
APT 24.04 crypto pol
This should be fixed now, PPAs are signed with 4096 bit keys, existing
1024 ones have been dual signed now and the end point gives you 4096 bit
keys if you add them.
** Changed in: launchpad
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubun
** Description changed:
⚠️ Only land this in the release/updates pocket after PPAs have been
resigned
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development series for 2.8, and this is the
only change left for the 2.8 release, save
** Description changed:
(This is uploaded to noble as 2.8.1 per
https://wiki.ubuntu.com/AptUpdates)
[Impact]
We have received feedback from users that use NIST-P256 keys for their
repositories that are upset about receiving a warning. APT 2.8.0 in
noble-proposed would bump the warning
Public bug reported:
[Impact]
We want to provide an easy tool to allow users to refresh signing keys. This
feature works for deb822 sources, classic sources are TBD.
[Test plan]
We have multiple test cases:
1. Add a weak PPA, ensure its key is refreshed.
2. Add a weak private PPA and ensure th
Please consult https://code.launchpad.net/~juliank/software-
properties/+git/software-properties/+merge/471412 for the code changes.
I have not implemented any support for trusted.gpg.d so far.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
[Impact]
- We want to provide an easy tool to allow users to refresh signing keys. This
feature works for deb822 sources, classic sources are TBD.
+ We want to provide an easy tool to allow users to refresh signing keys. This
feature works for both deb822 sources and cl
** Description changed:
[Impact]
We want to provide an easy tool to allow users to refresh signing keys. This
feature works for both deb822 sources and classic sources.
[Test plan]
For all releases:
1. Add a weak PPA, ensure its key is refreshed.
2. Add a weak private PPA and
** Also affects: software-properties (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: software-properties (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: software-properties (Ubuntu Noble)
Importance: Undecided
Status: New
** Also
apt-daily-upgrade.service has no Before= ordering constraints, hence it
can't hold up the boot; the blame analysis is pretty much irrelevant -
yes it starts at boot but that doesn't mean it needs to finish before
you can login.
The question I have then is why run-snapd-ns-chromium.mnt.mount only
s
** Description changed:
[Impact]
We want to provide an easy tool to allow users to refresh signing keys. This
feature works for both deb822 sources and classic sources.
[Test plan]
- For all releases:
+ For all releases (using the default sources.list format, i.e. adding the
+ PPA usi
The software-properties-qt regressions are still the bugs in autopkgtest
by having a separate software-properties-qt package in the release
pocket, which wrongly gets triggered and then fails to download, this
package will be superseded again by this
--
You received this bug notification because
The software-properties-qt regressions are still the bugs in autopkgtest
by having a separate software-properties-qt package in the release
pocket, which wrongly gets triggered and then fails to download, this
package will be superseded again by this
--
You received this bug notification because
** Changed in: software-properties (Ubuntu Oracular)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2077162
Title:
[FFe
I have adjusted the test plan to say to diffoscope them, and run another
diffoscope vs the software-properties-qt 0.99.48.1 and the packages are
still the same, timestamps, versions and the obvious /usr/share/doc
deduplication difference aside (as expected), so I am marking this as
verified.
** De
** Description changed:
[Impact]
If you have Source Code enabled, and you change the pockets configuration to
"all pockets", it will add -backports without source code. The Source Code flag
will still be set in the UI, but after a reload, you can see it is in a mixed
state.
This is mor
** Changed in: apt (Ubuntu Noble)
Milestone: ubuntu-24.04.1 => None
--
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/2073126
Title:
More nuanced public key algorithm revocat
This is a time_t transition issue most likely, the symbols files was not
updated for 64-bit time_t, and hence all the time_t symbols will now
depend on the build version on armhf.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Noble)
St
Update verified.
root@55d22e9f8666:/# apt update
Hit:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
Get:2 http://ports.ubuntu.com/ubuntu-ports noble-updates InRelease [126 kB]
Hit:3 http://ports.ubuntu.com/ubuntu-ports noble-proposed InRelease
Get:4 http://ports.ubuntu.com/ubuntu-ports nob
The Pro client is responsible for setting the credentials, that said
this may be the correct behavior, it may also depend on the umask of
your root user.
As in, it makes sense to protect the credentials from non-root users,
you don't want e.g. some daemon to gain access to it and leak it.
** Pack
Going to close this invalid as there's clearly a broken disk and it's
failing to hash an mmaped file, hence the mmap()ed regions SIGBUSes when
the read fails.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: apt (Ubuntu)
Status: New => 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.launchpad.net/bugs/2076655
Title:
[FFe] APT 3.0 solver updates in August
Status in apt
This is a weird thing, new dh-python seemingly just removed running the
test instead of switching to python -m unittest discover which would
have been arguably the right fix?
** Also affects: dh-python (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: dh-python (Ubuntu)
If we can reproduce this with our icudata in some process we should work
around it in icudata perhaps, but it doesn't seem worth expending effort
on this for third-party binaries.
** Also affects: icu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification beca
pam_lastlog.so doesn't exist anymore. Suggest consulting the journal for
logins, or maybe wtmpdb is an alternative with libpam-wtmpdb?
** Changed in: shadow (Ubuntu)
Status: New => Won't Fix
** Tags removed: rls-nn-incoming
** Tags added: rls-nn-notfixing
--
You received this bug notific
we should just blocklist apport from trying to analyse teamviewer
crashes.
** Changed in: icu (Ubuntu)
Status: New => Invalid
** Tags removed: rls-nn-incoming
** Tags added: rls-nn-notfixing
** Tags removed: rls-nn-notfixing
** Also affects: apport (Ubuntu)
Importance: Undecided
** Package changed: software-properties (Ubuntu) => python-httplib2
(Ubuntu)
** Changed in: python-httplib2 (Ubuntu)
Status: New => Fix Released
** Also affects: python-httplib2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python-httplib2 (Ubuntu Jammy)
I
3. APT, when checking the InRelease file, trusts it (and it could only
become trusted with the strong key signature, the only it knows), but
also sees a second signature with a week algorithm. Emits a warning.
So, I only see a false warning for the user: the system is safe using
the stronger key,
Dual signing started back then but it finished in July and the default
key exposed was switched to the newest for August.
** Changed in: software-properties (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2078676
Title:
wifi not remembering
Tagging for discussion, but this may be the right behavior, to install
systemd-resolved.
Please run
ubuntu-bug 2078555
to attach relevant information
** Tags added: rls-nn-incoming
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug n
During configuration of python3,
/usr/share/python3/debpython/files.py fails to get the content of
packages-
error running python rtupdate hook rhythmbox-plugin-alternative-toolbar
Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in
main()
File "/usr/bin/py3clean",
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
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/2078720
Title:
Upgrading from jammy to noble results i
Turns out that yes this is a bug in the APT solver:
https://salsa.debian.org/apt-team/apt/-/merge_requests/373/diffs
It was not restoring/keeping obsolete (in its parlance, no longer
downloadable) packages that are marked for removal due to a false
optimization.
--
You received this bug notific
** Description changed:
+ [Impact]
+ Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
+
+
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 via the `do-release-upgrade` command. This issue was seen whilst test
apt/jammy SRU uploaded. The ones for noble and devel need a bit more
massaging due to test suite failures but are not relevant before
oracular is released (noble's apt is used for noble->oracular updates)
** Also affects: apt (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affe
ubuntu-release-upgrader SRU uploaded to noble and also uploaded to
oracular.
These reintroduce the slow path as a fallback, specifically for APT
versions prior to this SRU (and hence mantic); they also fix that code
to correctly consider running kernels (and KeepInstalledSection) in the
removal of
** Description changed:
+ (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates)
+
[Impact]
Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
-
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/2079810
Title:
unattended-upgrades d
This is the expected behavior, it will pick the highest version (well
highest priority version) from any allowed repository. You have not
disallowed installing the Ubuntu one, and you also did not allow it to
install the Mozilla one.
You have two options
1) Pin the Ubuntu version down instead:
I
** Description changed:
(For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates)
[Impact]
Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 vi
@sil2100 The regression in time is back to the old behavior prior to
24.04.20; actually it's a bit faster as there is just a single action
group now. But the reason for it was that we iterated over all packages
in the cache and recorded their selected state in case we needed to undo
a change (verif
Verifying the apt/jammy SRU:
I installed libapt-pkg6.0=2.4.13 from proposed, then run `do-release-
upgrade -p` (`-d` should work now too, but was broken before):
The headers for the running kernel are not being removed:
Remove (was auto installed) binutils binutils-common
binutils-x86-64-linu
Upgrading with ubuntu-release-upgrader from proposed also worked
correctly:
$ lxc list -c nft
+--+--+-+
| NAME | BASE IMAGE | TYPE |
+--+--+-+
| jammy-to-noble-p
How does it calculate that? The package is Priority: required for the
source in debian/control, which extends to Package: apt and accidentally
I suppose to Package: apt-utils as well
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
@aaronmfeld If you have an upgrade issue, please file a separate issue,
this particular one has been verified as fixed.
--
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/2078720
Ti
101 - 200 of 2528 matches
Mail list logo
