Your message dated Fri, 30 Aug 2019 23:04:52 +0000 with message-id <e1i3pwq-000cbt...@fasolo.debian.org> and subject line Bug#935733: fixed in bladerf 0.2019.07-4 has caused the Debian Bug report #935733, regarding libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS 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.) -- 935733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libbladerf-doc Version: 0.2019.07-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libbladerf-doc_0.2019.07-1_all.deb ... Unpacking libbladerf-doc (0.2019.07-1) ... dpkg: error processing archive /var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/libbladerf-dev/CONTRIBUTORS', which is also in package libbladerf-dev:amd64 0.2017.12~rc1-2 Errors were encountered while processing: /var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb cheers, Andreas
libbladerf-dev=0.2017.12~rc1-2_libbladerf-doc=0.2019.07-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Source: bladerf Source-Version: 0.2019.07-4 We believe that the bug you reported is fixed in the latest version of bladerf, 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 935...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms <bott...@debian.org> (supplier of updated bladerf 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: SHA256 Format: 1.8 Date: Fri, 30 Aug 2019 18:20:01 -0400 Source: bladerf Architecture: source Version: 0.2019.07-4 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms <bott...@debian.org> Changed-By: A. Maitland Bottoms <bott...@debian.org> Closes: 935733 Changes: bladerf (0.2019.07-4) unstable; urgency=medium . * Correct Breaks:/Replaces: (Closes: #935733) Checksums-Sha1: 6760b456bbd998573f5fc69e405ee79f654eeb0a 3088 bladerf_0.2019.07-4.dsc e2a5d965d6c7c04cf7841f77e932ecc79be76da4 68316 bladerf_0.2019.07-4.debian.tar.xz fc774670f97dcdad9d9e8ec0e462fce7dbddb5dd 12554 bladerf_0.2019.07-4_amd64.buildinfo Checksums-Sha256: 59045847a74fbb9739cf1b8e1c4340d71dce3ff622950454a74b87370b58dce7 3088 bladerf_0.2019.07-4.dsc 16232ed4ffb24e849c63e7bb1d4b33d14eefa5b8c4b1303288cb1c8c3b04fb84 68316 bladerf_0.2019.07-4.debian.tar.xz aa8c27503fcef62eeb8683211db8bb54859416cc9ddb15c6d0667698ed4f72b2 12554 bladerf_0.2019.07-4_amd64.buildinfo Files: d118842169de953b71b046095e9abb11 3088 comm optional bladerf_0.2019.07-4.dsc b285c7eb9a138445a433cd5485c28d36 68316 comm optional bladerf_0.2019.07-4.debian.tar.xz 4017555b3c105b5b8ee7f256989ab142 12554 comm optional bladerf_0.2019.07-4_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl1ppD0ACgkQUEHxiR9E 4JAfaRAAz+xxnFGvEs3NQJNRexcXLFz2lZYMeSqnzb6pZusl0CAzSU9ONKr2g/Fo 23kiT7vPLu7nXUfV/anb9TKrJdt32km32x1OJmtiZ1zyAFNXogu5AtUW7l2gqcDQ hU1V3FH1Z/YrP+r1QWX6nuL3z9VNmoWJ0XDgaLfdIJZ7Yh1quLoXDetPfFhX+tWZ vG1tE1LaPwFBBxKHWd5+ZCHXHSEwmyin5e5mjIatvYhGBx5Cd6aWWx/miuSoxm24 121wGZ0tkkBtmRVGTai2n2G8cwCUw6lyf655x7IC56PiuQ9cG8uN7qGiLM/mNiic jVJbXzzf5Nf6nCpc7mNMK9akBofO7eU3EfCcWqPsiKa84tRJC+pRPW7EFKeoWoaL jZkv00jWl3RNV+UeS4E+yrvdgK0jk+hkLBPH+/CvcY/Un8SUxQzjG7DcvzoIt8Z+ tD95x8mGGj4yT6oM/2hE1XGdcgmzWvZjllRLB0oz1Lur5NJ2u/bnptvaCnTKoFvU KHoEmJVabwLTnYK+8yNpucD6vjEJLE3JjSY19pcpVVDfE6pFn2Rjma8bKy0FRasb U7G+k/zSHJJAsGk5ZFzielPqaueyvultIU1/4F/lrvB2MBBMZtbtDmWfkd7feaNN QuXyN2HZuX/mSJC//PdhvmaZ6Vg8NhN+oDtnhPSIrdP3BKuWlPY= =R4Qc -----END PGP SIGNATURE-----
--- End Message ---