Your message dated Sun, 2 Mar 2025 18:51:31 -0500
with message-id
<cad+gyvzunhpbbnt9qpgjikqar1h8_vmcaaojyhbub+9qquv...@mail.gmail.com>
and subject line Re: Breaks/Replaces for appstream file move are too strict
has caused the Debian Bug report #975044,
regarding Breaks/Replaces for appstream file move are too strict
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 [email protected]
immediately.)
--
975044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975044
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gparted
Version: 1.0.0-0.1build1
Severity: normal
Tags: patch
Hiya,
I'm filing this from an Ubuntu system, but it's a fix I think we should
do in Debian, to help all derivatives.
When upgrading gparted just now, I got:
> Unpacking gparted (1.1.0-0.1) over (1.0.0-0.1build1) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-WEMwFJ/165-gparted_1.1.0-0.1_amd64.deb (--unpack):
> trying to overwrite '/usr/share/metainfo/gparted.appdata.xml', which is also
> in package gparted-common 1.0.0-0.1build1
It's because Ubuntu performed a no-change rebuild of gparted for a
library transition (we don't have binary uploads there).
Your Breaks/Replaces matches only the exact version of the file that
shipped the appdata in Debian, so any modified downstream versions will
not match. It would be nicer to either just use `<<` for all earlier
versions, or if you want add a lower bound too. I'm happy to supply and
upload a patch if you'd like.
Cheers,
--
Iain Lane [ [email protected] ]
Debian Developer [ [email protected] ]
Ubuntu Developer [ [email protected] ]
--- End Message ---
--- Begin Message ---
This bug is too ancient to keep open because the Breaks/Replaces could
be removed instead now.
Thank you,
Jeremy Bícha
--- End Message ---
