Your mirror has not been updated in over a year, please switch to a
different one.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Your mirror has not been updated in over a year, please switch to a
different one.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
> Or do I have to back it up, uninstall Postgres and restore from the
backup?
This is the right approach, we can't guarantee a new Postgres version
will not cause data loss hence we blocked upgrading postgres versions
(aka removing old postgres)
** Changed in: ubuntu-release-upgrader (Ubuntu)
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
** This bug has been marked a duplicate of bug 2078589
fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
--
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
** This bug has been marked a duplicate of bug 2078589
fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
--
You received this bug notification because you are a member of Ubuntu
Bugs
This is missing the /var/log/dist-upgrade information, commonly
collected by ubuntu-bug ubuntu-release-upgrader
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Attaching monitors.xml and trying to debug this lead to 3 crashes:
https://bugs.launchpad.net/bugs/2078721
https://bugs.launchpad.net/bugs/2078722
https://bugs.launchpad.net/bugs/2078723
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 2078685 ***
https://bugs.launchpad.net/bugs/2078685
** This bug has been marked a duplicate of bug 2078685
upgrade 24.04 manger stopped and produced the following errors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Current monitors.xml attached
** Attachment added: "monitors.xml"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2078060/+attachment/5812408/+files/monitors.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You have marked grub-efi-amd64-signed as hold.
Package: grub-efi-amd64-signed
Status: hold ok installed
To upgrade to 24.04, you need to allow it to install a new grub by
removing the hold using apt-mark unhold grub-efi-amd64-signed
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status:
Note for libpcap0.8t64 a smaller reproducer can be found in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/2078579
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net
** Description changed:
- Ubuntu-release-upgrade fails because it won't ignore zoneminder which must
NOT be upgraded.
- I had already commented out that ppa because the release-upgrade wouldn't
even start with that ppa listed.
- I have zoneminder frozen at the last release that actually works.
+
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
Reassigning to snapd, scope is only the messages in the bug description.
** Package changed: ubuntu-release-upgrader (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078685
T
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
** This bug has been marked a duplicate of bug 2078589
fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
--
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
looks very much like a dupe of 2078589 although there may be other
factors at play too that I missed.
** This bug has been marked a duplicate of bug 2078589
fight: desktop-base vs kubuntu-settings-deskto
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078579
Title:
Holding Back libpcap0.8t64:amd64 rather than change libibverbs1:amd64
To manage notifications about this
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2078589
Title:
fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
To manage noti
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
This is the first broken behavior and it's quite awkward
Broken libatk1.0-0t64:amd64 Depends on at-spi2-common:amd64 < none |
2.52.0-1build1 @un umH >
Considering at-spi2-common:amd64 1 as a solution to libatk1.0-0t64:amd64 200
MarkKeep libatk1.0-0t64:amd64 < none -> 2.52.0-1build1 @un umN Ib
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
I do think php8.1 is being removed correctly, so it really is a
duplicate of bug 2078589
** This bug has been marked a duplicate of bug 2078589
fight: desktop-base vs kubuntu-settings-desktop vs fontconf
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
Marking as duplicate of 2078589, as it has the same main fight.
And as ppa-purge tells you in the message you quoted, it needs the PPA name as
an argument, albeit, I think you might not have a PPA problem
** Also affects: kubuntu-settings (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2078589
Title:
fight: desktop-base vs kubunt
Please remove postgresql-9.6 manually after backing up / exporting
databases before upgrading. It is so old, it doesn't even exist in the
archive anymore, the last release was artful 17.10.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug not
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
I can't say I have full insight into the Ubuntu studio failures yet, but
there's plenty wrong here where it fails to install pipewire to
Broken libgeos-c1t64:amd64 Depends on libgeos3.12.1t64:amd64 < none |
3.12.1-3build1 @un umH > (>= 3.12.1)
Considering libgeos3.12.1t64:amd64 0 as a solution
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
There may be more at play here but the final conflict trail is 2078589
** This bug has been marked a duplicate of bug 2078589
fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
--
Yo
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
The message is incomplete, and there is no /var/log/dist-
upgrade/main.log to analyse further.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
** Summary changed:
- Upgrade to 24.04 fails.
+ fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078589
Title:
fight: desktop-bas
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
Some overlap with 2078579
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078576
Title:
Upgrade to 24.04.1 impossible, but no ppa packages are in broken
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
Some differences but fairly similar overall to 2078589 with the same end
result.
** This bug has been marked a duplicate of bug 2078589
Upgrade to 24.04 fails.
--
You received this bug notification bec
This is pretty much a bug in ubuntu-release-upgrader which for some
reason fails to install libibverbs1 to satisfy the dependencies of
libpcap0.8t64:
Broken libpcap0.8t64:amd64 Depends on libibverbs1:amd64 < none | 50.0-2build2
@un umH > (>= 1.1.6)
Considering libibverbs1:amd64 0 as a solution
But please note that we cannot guarantee old versions of packages to
remain installable, holds and PPAs generally are not supportable. It
just seems that in this particularly case one can find a solution, as
APT itself happily upgrades everything.
** Changed in: ubuntu-release-upgrader (Ubuntu)
*** This bug is a duplicate of bug 2078589 ***
https://bugs.launchpad.net/bugs/2078589
Likely a duplicate of 2078589 (which also is a duplicate of some other
bug I cannot remember)
** This bug has been marked a duplicate of bug 2078589
Upgrade to 24.04 fails.
--
You received this bug not
Please backup your databases, remove postgresl-12 before upgrading.
postgresql-12 was only shipped in 20.04 (!), and it's dependencies are
no longer installable in 24.04. After the upgrade, install the main
postgresql package and restore the databases.
** Changed in: ubuntu-release-upgrader (Ubun
Broken nautilus:amd64 Breaks on nautilus-share:amd64 < 0.7.3-2ubuntu6 @ii umH >
(< 0.7.3-2ubuntu7~)
Considering nautilus-share:amd64 -3 as a solution to nautilus:amd64 10
Upgrading nautilus-share:amd64 due to Breaks field in nautilus:amd64
It seems you have marked the nautilus-share package
Due to the seeming lack of the actual failure in the main log for the Qt
frontend, it does seem to be the continuing fight desktop-base vs
kubuntu-settings-desktop vs fontconfig-common:
Investigating (19) fontconfig-config:amd64 < 2.13.1-4.2ubuntu5 ->
2.15.0-1.1ubuntu2 @ii umU Ib >
Broken fontcon
Please report any bugs you actually see using ubuntu-bug where
name is a package name, a program path, or the PID of a broken process.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I'm afraid we can't change the release archive once its published, I
think the best bet is shipping a backported awscli in noble-updates, but
I also don't know what else is missing.
Arguably we could come up with some mechanism to remove entries in an
overlay of the Commands file in -updates but w
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
Sorting out one chain, ubuntu-minimal is being removed due to netplan.io
being removed.
Broken netplan.io:amd64 Dépend on python3:amd64 < 3.10.6-1~22.04.1 |
3.12.3-0ubuntu2 @ii umR >
Considering python3:amd64 1406 as a solution to netplan.io:amd64 17
MarkKeep netplan.io:amd64 < 0.106.1-7ubunt
** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078676
Title:
wifi not remembering login password
To manage notificat
Various critical components have been replaced with versions from Pop!Os
and that is not something we can support.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I'm afraid I don't have the hours to investigate that particular upgrade
issue. I think I've seen it before, it's this 3-way battle:
Investigating (19) fontconfig-config:amd64 < 2.13.1-4.2ubuntu5 ->
2.15.0-1.1ubuntu2 @ii umU Ib >
Broken fontconfig-config:amd64 Breekt on kubuntu-settings-desktop:a
The upgrade issue seems to stem from the fact that you had installed a
backported PPA version of pipewire.
You may get lucky trying to resolve the issue by using:
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
The message is pretty much self-explanatory.
As for the inability to install postgresql after an upgrade, that issue
seemingly arises because you installed PostgreSQL 16 in jammy from a
PPA. We cannot provide support on that, please talk to your PPA provider
if upgrades don't work.
** Changed in:
I'm afraid this is a tough case to analyse. I'm not sure if there really
is an issue or if it just is so complex it just runs into the arbitrary
iteration limit of the solver.
It seems opencv stuff is quite complex, I don't know though if you can
safely remove all opencv stuff from the system. Tem
Your mirror has not been updated since May 2023, please pick a different
one.
@enr0n: We should try to change mirrors if the current one doesn't work!
** Tags added: rls-nn-incoming
** Summary changed:
- unable to upgrade to 24
+ stale mirror prevents upgrades
--
You received this bug notific
2024-09-02 14:02:10,358 ERROR Dist-upgrade failed: 'The package
'postgresql-10' is marked for removal but it is in the removal deny
list.'
You still have a PostgreSQL 10 database installed from 18.04, that is no
longer installable in 24.04 (it also wasn't shipped post 18.04), so it
needs to be rem
The dependencies of gnome-settings-daemon are:
Depends: libspa-0.2-bluetooth | pulseaudio-module-bluetooth, pipewire-audio |
pulseaudio,
Recommends: pipewire-audio
Because pulseaudio and pulseaudio-module-bluetooth are installed, APT
reorders those to the front, and this later on causes conflict
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
Bugs, which is subscr
You have PostgreSQL 12 installed. This version is no longer available
after 20.04 (!) and it must now be removed, however this can incur data
loss so for safety reasons we don't do that, so go take a backup of your
database, remove postgresql-12, upgrade and then restore your backup
into whatever v
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078653
Title:
"Upgrade now" suggestionpops up while already in dist upgra
So reconstructing that we can see a clear conflict here:
jak@jak-t14-g3:~/Downloads/xxx$ apt -o Dir=$PWD dist-upgrade -o
APT::Architectures::=i386 --solver internal kubuntu-settings-desktop -s
desktop-base
NOTE: This is only a simulation!
apt needs root privileges for real execution.
The log has a
MarkKeep desktop-base:amd64 < 11.0.3ubuntu1 -> 12.0.6+nmu1ubuntu1 @ii
umU > FU=0
and there does not appear to be a reason for it, but this is what is
breaking things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Description changed:
PPAs shipping a newer version of key system packages is a significant
problem and leads to long and complex to identify bugs such as
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078376
https://bugs.launchpad.net/ubuntu/+source/ubuntu-re
You are another one of the cases who have installed a newer version of
PipeWire from a PPA than is available in 24.04. Please don't go around
replacing core system packages with third-party repositories, this is
for very advanced users only.
You may get lucky by downgrading pipewire packages firs
You have installed Postgres from a PPA which in turn includes a newer
version of python3-psycopg2 than is available in 24.04. You will need to
downgrade python3-psycopg2 to the version in jammy and remove postgres
before upgrading.
--
You received this bug notification because you are a member of
I don't understand why desktop-base is being kept back and then removed
but it is a problem.
MarkKeep desktop-base:amd64 < 11.0.3ubuntu1 -> 12.0.6+nmu1ubuntu1 @ii umU >
FU=0
Delayed Removing: desktop-base:amd64 as upgrade is not an option for
kubuntu-settings-desktop:amd64 (1:24.04.12)
--
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078448
Title:
3rd party (PostgreSQL) package shouldn't be removed, upgrad
You may get lucky by downgrading pipewire packages first using one of
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
You may get lucky by downgrading pipewire packages first using one of
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
You may get lucky by downgrading pipewire packages first using one of
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Apologies, it should be
apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3'
apt install '?installed?source-package(^pipewire$)/jammy-updates'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
2 or 3 out of 15 bugs analysed today were packages being marked hold by
the user. I think the best cause of action is to abort the upgrade
attempt telling them to remove their holds and having the ability to
override that (but we don't just want to continue and then crash in t
** Tags removed: rls-oo-incoming
** Tags added: rls-nn-incoming
** Description changed:
PPAs shipping a newer version of key system packages is a significant
problem and leads to long and complex to identify bugs such as
- https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
- upgrade
It seems we failed to install libglib2.0-0t64 and only removed
libglib2.0. We had the bug multiple times before, neither snapd nor the
transitional packages depend on libglib2.0-0(t64) despite needing them
for the desktop hooks, but I do not recall what the outcome of that was
and why it is resurfa
2024-08-30 12:28:34,525 WARNING Can't mark 'ubuntu-desktop' for upgrade
(E:Error, pkgProblemResolver::Resolve generó cortes, esto puede deberse
a paquetes retenidos.)
Why?
You have installed Pipewire from a PPA in a much newer version than
24.04 has:
MarkKeep libspa-0.2-modules:amd64 < 1.2.3
2024-08-30 12:15:59,956 WARNING Can't mark 'ubuntu-desktop' for upgrade
(E:Unable to correct problems, you have held broken packages.)
Looking at the log
Broken libpipewire-0.3-0t64:amd64 Depends on libspa-0.2-modules:amd64 <
1.0.7-3~ubuntu22.04 @ii mK > (= 1.0.5-1ubuntu1)
This is the fourth or
** 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
You have configured various samba packages as hold, as evident by the H
in the log
MarkDelete samba:amd64 < 2:4.15.13+dfsg-0ubuntu1.6 @ii umH Ib > FU=0
MarkInstall python3-samba:amd64 < 2:4.15.13+dfsg-0ubuntu1.6 @ii umH Ib >
FU=0
Hence the upgrade to noble is unable to proceed.
** Chang
This is by design and not a bug, you will want to figure out a
transition strategy for your database first, remove postgres, upgrade to
noble and then install the new version of postgres, as you otherwise
risk data loss.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
** Summary changed:
- ubuntu-release-upgarder error
+ No mirror configured after sources.list rewriting
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Triaged
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Indeed, this is by design to prevent data loss during database version
upgrades so backing up the database, removing postgres, upgrading, and
installing the new version is the right approach
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug no
You have set the cups package to hold, hence it is refusing to upgrade
it, which is breaking the upgrade, as libcups2 is no longer supported in
noble, having been replaced by libcups2t64.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notif
You have installed PipeWire from a PPA in a newer version than supported
in noble, hence an upgrade is not possible. You could possibly try
downgrading all of pipewire first by removing the PPA and doing
apt install '?source-package(^pipewire)/jammy'
Broken libpipewire-0.3-0t64:amd64 Depends on l
This may be solvable in ffmpeg too, perhaps, I'm not entirely sure. I
can't quite come up with the correct dependencies in my head, but it
seems possible adding some Provides to libavcodec and then
Conflicts to those from the libavcodec-extra metapackage might do the
trick.
** Summary changed:
-
Let's debug.
We start with
2024-08-30 08:24:32,170 DEBUG The package 'ubuntustudio-desktop-core' is
marked for removal but it's in the removal deny list
Looking for this in apt log we see:
Investigating (1) ubuntustudio-desktop-core:amd64 < 0.210 @ii mK NPb Ib >
Broken ubuntustudio-desktop-core
You have installed a higher version of PipeWire from a PPA than what is
available in noble, and hence the upgrade is not possible.
Broken libpipewire-0.3-0t64:amd64 Depends on libspa-0.2-modules:amd64 <
1.0.7-3~ubuntu22.04 @ii mK > (= 1.0.5-1ubuntu1)
Considering libspa-0.2-modules:amd64 12 as a
You have installed a higher version of PipeWire from a PPA than what is
available in noble, and hence the upgrade is not possible.
Broken libpipewire-0.3-0t64:amd64 Hängt ab von on libspa-0.2-modules:amd64 <
1.0.7-3~ubuntu22.04 @ii mK > (= 1.0.5-1ubuntu1)
Considering libspa-0.2-modules:amd64 11
Public bug reported:
PPAs shipping a newer version of key system packages is a significant
problem and leads to long and complex to identify bugs such as
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/2078376
We should not upgrade systems that have replaced system packag
Looking at mainlog,
update-manager is marked for removal.
Looking at AptLog
Broken update-manager:amd64 Depends on update-notifier:amd64 < 3.192.54.8 |
3.192.68build3 @ii umR >
Considering update-notifier:amd64 6 as a solution to update-manager:amd64 6
MarkKeep update-manager:amd64 < 1:22.0
I'mconfused why the main log ends trying to find replacement packages
and doesn't show a solver issue; it's possible we're forgetting to log
something here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
You are trying to install base-files from Debian on an Ubuntu system;
this is not supported (for all packages, not just base-files).
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
** Tags removed: rls-jj-incoming
** Tags added: foundations-todo
** Changed in: os-prober (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987
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
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
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)
As in bug 2067254 please update the maintainer to use the mailing list,
and there are plenty of debian/copyright paragraphs that can be cleaned
up from some garbage lines and then merged together.
Also there is an erroneous space following `Rules-Requires-Root: no`
From the maintainability perspe
One thing to wonder: These packages are very very small, they seem to
follow a common release schedule, maybe it would make more sense to
bundle them together in one package, with multiple orig tarballs, it's
quite some overhead to package individual tiny programs like that.
--
You received this
Might just add grub2-unsigned/signed entries to the CVE tracker and mark
it as not affected? I think porting new zstd to grub may be significant
effort and it's not worth to work around third party tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
101 - 200 of 1437 matches
Mail list logo
