Your message dated Thu, 6 Feb 2025 07:09:33 -0500
with message-id
<CAD+GYvwK2JZ=0iDgUyZ9feN+GkjLMp60MEJcSS9a=o-pxpb...@mail.gmail.com>
and subject line Re: Bug#1095287: gir1.2-gst-plugins-bad-1.0: Conflicting files
with pitivi on upgrade
has caused the Debian Bug report #1095287,
regarding gir1.2-gst-plugins-bad-1.0: Conflicting files with pitivi on upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1095287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gir1.2-gst-plugins-bad-1.0
Version: 1.18.4-3+deb11u4
Severity: serious
Dear Maintainer,
On upgrading a Buster machine to Bullseye with pitivi installed, I get
the following:
> Selecting previously unselected package gir1.2-gst-plugins-bad-1.0:amd64.
> Preparing to unpack
> .../042-gir1.2-gst-plugins-bad-1.0_1.18.4-3+deb11u4_amd64.deb ...
> Unpacking gir1.2-gst-plugins-bad-1.0:amd64 (1.18.4-3+deb11u4) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-GbL8DL/042-gir1.2-gst-plugins-bad-1.0_1.18.4-3+deb11u4_amd64.deb
> (--unpack):
> trying to overwrite
> '/usr/lib/x86_64-linux-gnu/girepository-1.0/GstTranscoder-1.0.typelib', which
> is also in package pitivi 0.999-1+b1
That is because Buster's version of pitivi (0.999-1+b1) indeed packages
this file for some reason, and there seem to be a missing relationship
between those packages for the upgrade to work properly.
I guess having gir1.2-gst-plugins-bad-1.0 break/replace pitivi << 2020
or so would work. I don't know if this can be solved in the pitivi
package side, but if so and you prefer that please reassign.
I know this is for old packages, but this is quite serious as it breaks
upgrading from Buster if the pitivi package is installed. FTR, this
was a two-part upgrade: upgrade followed by full-upgrade, and happened
on the second step.
Getting out of this is manageable as Apt ends up installing the new
pitivi before aborting, so a further `apt -f install` works, but it
expectedly leads to messy things removing unexpected packages that need
to be re-installed after Apt solved the inconsistent state.
Regards,
Colomban
-- System Information:
Debian Release: 11.11
APT prefers oldstable-security
APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
# This is irrelevant, it's from a Bookworm machine used to report the bug
#Kernel: Linux 6.1.0-29-amd64 (SMP w/4 CPU threads; PREEMPT)
#Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
#LSM: AppArmor: enabled
Versions of packages gir1.2-gst-plugins-bad-1.0 depends on:
ii gir1.2-glib-2.0 1.66.1-1+b1
ii gir1.2-gst-plugins-base-1.0 1.18.4-2+deb11u3
ii gir1.2-gstreamer-1.0 1.18.4-2.1+deb11u1
ii libgstreamer-plugins-bad1.0-0 1.18.4-3+deb11u4
gir1.2-gst-plugins-bad-1.0 recommends no packages.
gir1.2-gst-plugins-bad-1.0 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Feb 6, 2025 at 6:36 AM Colomban Wendling
<lists....@herbesfolles.org> wrote:
> I know this is for old packages, but this is quite serious as it breaks
> upgrading from Buster if the pitivi package is installed. FTR, this
> was a two-part upgrade: upgrade followed by full-upgrade, and happened
> on the second step.
Debian 11 "Bullseye" reached End of Life last year. I am closing this
bug since it is not possible for us to fix your issue.
https://www.debian.org/releases/
Thank you,
Jeremy Bícha
--- End Message ---
