Your message dated Fri, 15 May 2020 17:33:44 +0000
with message-id <e1jzedq-000ckb...@fasolo.debian.org>
and subject line Bug#960689: fixed in lunar-date 2.4.0-8
has caused the Debian Bug report #960689,
regarding liblunar-date-dev: missing Breaks+Replaces: gir1.2-lunar-date-2.0 (<< 
2.4.0-7)
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.)


-- 
960689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblunar-date-dev
Version: 2.4.0-7
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 .../liblunar-date-dev_2.4.0-7_amd64.deb ...
  Unpacking liblunar-date-dev:amd64 (2.4.0-7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb (--unpack):
   trying to overwrite '/usr/share/gir-1.0/LunarDate-2.0.gir', which is also in 
package gir1.2-lunar-date-2.0 2.4.0-5
  Errors were encountered while processing:
   /var/cache/apt/archives/liblunar-date-dev_2.4.0-7_amd64.deb


cheers,

Andreas

Attachment: gir1.2-lunar-date-2.0=2.4.0-5_liblunar-date-dev=2.4.0-7.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: lunar-date
Source-Version: 2.4.0-8
Done: xiao sheng wen <atzli...@sina.com>

We believe that the bug you reported is fixed in the latest version of
lunar-date, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
xiao sheng wen <atzli...@sina.com> (supplier of updated lunar-date package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 15 May 2020 22:06:09 +0800
Source: lunar-date
Architecture: source
Version: 2.4.0-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Chinese Team <chinese-develop...@lists.alioth.debian.org>
Changed-By: xiao sheng wen <atzli...@sina.com>
Closes: 960689
Changes:
 lunar-date (2.4.0-8) unstable; urgency=medium
 .
   [ 肖盛文 ]
   * Fix for piuparts fails to upgrade from testing, closes: #960689
Checksums-Sha1:
 c63b38e60299a0f55abb6b65d4c86b5fc6eafb90 2403 lunar-date_2.4.0-8.dsc
 75fe33350fdfb7d790f77ebcfb47ee8f17ac2a42 3980 lunar-date_2.4.0-8.debian.tar.xz
Checksums-Sha256:
 58811407ab7be638919e56fdd45b412bbdb780edc33ecf1654d848f11ce3cb63 2403 
lunar-date_2.4.0-8.dsc
 2631f776ce9933f0345b74972c19bac079a244869fc8b4335deae7540933b310 3980 
lunar-date_2.4.0-8.debian.tar.xz
Files:
 6e68c43baea95c1e5c7de2369cf86f9b 2403 libs optional lunar-date_2.4.0-8.dsc
 32d14bdde1d98d6e50bd0e58db0a3ee0 3980 libs optional 
lunar-date_2.4.0-8.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAl6+0PkACgkQM1X01jtY
Icy5DhAAtGKcLdAECcvEsKFdC9+WrhoVGasdv8xjch68VmS2Ejzs4d5aMYOQOPQS
qNFcL30Qxobe/4jaVs60wHbwQjbT1JcPCUaUx5IZeYoCjKFZYT6dCoXzK5npmHRa
x4aal66jcncnWtFyBp0PfjgxuzhwR9bwwVdrsLF8ZX/rsRpzfYG1rrPvJ6QlqJ0h
t2J4M4RQ7IgMwQl3jPLhGz/roe5QwhPLzoQp4LkWrDDflSdmgW3owe2av5ioebfV
C0npUj2CyyG3zGqmcGKpkryhLmIy6vN90v7v804H6cBVTfNzDsf/VD+VwTFodowL
+eIlGCQMIpDdntTUh7JgbiK0ig2qRkhb2hg2QWQIhxhur789mfNwr0lOEl1bEBsQ
M1gGnEUGe3JidoqeurV09jlJTeV7D/ZjJIFWhOrNCyp/A3KqjNMxdkOoSZ7kMrrZ
0cf39JMSm3Pq/oeE7nm0UHkchyKdS2Qn1eGuvJJq3ku3/WwWRbmaTsrPrU+sV+zc
+YAivlLxZQbkpsBwVxJidEgz/zwDwoQtMexm47Kc+BLiXz9qOR6/wDkGpttE+Z9J
Z8TRcA7jyr7v9ysO626dKdeSdkiw9H8ptjCXulZ1W3D8l0Eg99TpFDxoSpSVHdfE
yR9eZ6n8xuVNw6jgTZ4XPafFUD0FSiQQOGSHYd5VCHJ0RVIKD7I=
=vRDF
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to