Your message dated Thu, 07 Apr 2022 13:23:59 +0200
with message-id <87bkxdcevj....@janja.pimeys.fr>
and subject line Re: python3-mistune0: missing Conflicts+Replaces:
python3-mistune or Breaks+Replaces: python3-mistune (<< 2.0.0-1+really2.0.0)
has caused the Debian Bug report #1006381,
regarding python3-mistune0: missing Conflicts+Replaces: python3-mistune or
Breaks+Replaces: python3-mistune (<< 2.0.0-1+really2.0.0)
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.)
--
1006381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-mistune0
Version: 0.8.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../python3-mistune0_0.8.4-1_all.deb ...
Unpacking python3-mistune0 (0.8.4-1) ...
dpkg: error processing archive
/var/cache/apt/archives/python3-mistune0_0.8.4-1_all.deb (--unpack):
trying to overwrite
'/usr/lib/python3/dist-packages/mistune-0.8.4.egg-info/PKG-INFO', which is also
in package python3-mistune 2.0.0-1+really0.8.4-1
Errors were encountered while processing:
/var/cache/apt/archives/python3-mistune0_0.8.4-1_all.deb
The following files are in conflict:
usr/lib/python3/dist-packages/mistune-0.8.4.egg-info/PKG-INFO
usr/lib/python3/dist-packages/mistune-0.8.4.egg-info/dependency_links.txt
usr/lib/python3/dist-packages/mistune-0.8.4.egg-info/not-zip-safe
usr/lib/python3/dist-packages/mistune-0.8.4.egg-info/top_level.txt
usr/lib/python3/dist-packages/mistune.py
If python3-mistune 2.* ships usr/lib/python3/dist-packages/mistune.py, too,
the two versions cannot be made co-installble and you should use
Conflicts+Replaces: python3-mistune
otherwise (i.e. the 0.8.4 and 2.0.0 are co-installable) use
Breaks+Replaces: python3-mistune (<< 2.0.0-1+really2.0.0)
cheers,
Andreas
python3-mistune=2.0.0-1+really0.8.4-1_python3-mistune0=0.8.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
fixed 1006381 0.8.4-2
thanks
Jonas Smedegaard <d...@jones.dk> wrote on 06/04/2022 at 16:19:41+0200:
> [[PGP Signed Part:No public key for 2C7C3146C1A00121 created at
> 2022-04-06T16:19:41+0200 using RSA]]
> Hi Pierre-Elliott,
>
> Here's a friendly notice in case you were unaware of this bug#1006381
> blocking mistune0 from entering testing.
>
>
> Kind regards,
mistune0 0.8.4-1 was a binary upload to pass new, it could not have gone
to testing, and I was planing since the beginning to supersede it with a
version not having any path conflict.
src:mistune0 0.8.4-2 is a sourceful upload which superseded 0.8.4-1 and has
no conflicting file with src:mistune.
This bug could just have been closed. (IDK why I did not receive a mail
when it got opened).
Regards,
--
PEB
signature.asc
Description: PGP signature
--- End Message ---
