[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1027836: marked as done (planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png)

Your message dated Mon, 09 Jan 2023 14:59:10 +0000
with message-id <E1pEtcE-00DN0H-5q@fasolo.debian.org>
and subject line Bug#1027836: fixed in planner 0.14.91-2
has caused the Debian Bug report #1027836,
regarding planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png
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 owner@bugs.debian.org
immediately.)


-- 
1027836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027836
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: planner,planner-data
Version: 0.14.91-1
Severity: serious
User: debian-qa@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages failed to install
because they tries to overwrite each others files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package planner.
  Preparing to unpack .../101-planner_0.14.91-1_amd64.deb ...
  Unpacking planner (0.14.91-1) ...
  dpkg: error processing archive /tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/planner/images/gnome-planner.png', which is also in package planner-data 0.14.91-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb


cheers,

Andreas

Attachment: planner=0.14.91-1_planner-data=0.14.91-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
Source: planner
Source-Version: 0.14.91-2
Done: Bastian Germann <bage@debian.org>

We believe that the bug you reported is fixed in the latest version of
planner, 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 1027836@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated planner 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Mon, 09 Jan 2023 14:33:11 +0100
Source: planner
Architecture: source
Version: 0.14.91-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1027836
Changes:
 planner (0.14.91-2) unstable; urgency=medium
 .
   * QA upload
   * Move /usr/share data to -data package (Closes: #1027836)
Checksums-Sha1:
 13df9bfdaf6c86f4cb977e496d2001ea84bf2792 1841 planner_0.14.91-2.dsc
 9d7663176d56f2d9ebfd375dd872f2f84a94ce25 12504 planner_0.14.91-2.debian.tar.xz
 bce0101b732e43a334bf7d706e0480a2d8e3f92b 15168 planner_0.14.91-2_source.buildinfo
Checksums-Sha256:
 bef887163a7299046424ffd91ed380a1b888727ad68c773b924cee2e2e2dd310 1841 planner_0.14.91-2.dsc
 e5e47df690ed5273112199fe5f6baea318e08418cead03dc4ddccc39577f4156 12504 planner_0.14.91-2.debian.tar.xz
 4ee84c069169b1fd51e6a91eb8c31832b6c444801f68a3b720696b86b6ec23b9 15168 planner_0.14.91-2_source.buildinfo
Files:
 a366ed37bb1950379332751d6b536b0f 1841 gnome optional planner_0.14.91-2.dsc
 a973329a16531151f5b0d814d1dd47c1 12504 gnome optional planner_0.14.91-2.debian.tar.xz
 a39951c5065134fc2f23c691dab11138 15168 gnome optional planner_0.14.91-2_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmO8HMUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFGO/C/4ocavWUnu7XkpKSJEq4b2JTZrrr/vVmht/
cis3uEAq9iLYexkpxeQfjxqseS+5NN91kHgvrgy9McVTEspzJZCcRKPJeS6YLeQp
XFHHM3Ni5EacphUnn5njGx/PRfsyRAvcYXYfXPUYT6ifDVIrKPP48eLCoJ6dNiUv
9Ms8seJOqufCv6xPZzREwbQ6lqb2V7RAfqpXKXScNn8OaiqPa8PZ1Vb+wWCoi+3y
xxJaHCzGML9ifzqq2pfKrOYYdsDA6hG1VG906a9gELQkl83VlTP/Ui8W4ORdy+ez
Jy8f4pc7Crrq1jKN8thgPyoqBVJHW4VYOzTSw6dM9fIq44Fo1AkdVt8lbrnFteBV
iNkf4Hzw+XnmyZxFjLHxrrRVdGDEjyopQ1odxeJuoIRpt6Ng6TZCtLX7sHz36VHo
AubRqyD8R3BFQ14vfoafLv8AELXmwwbjW06hEtOnUtfF035PwYay7LIWJoOHUIdi
CArWbTuIP7ZINKHgZNdQCxPE4tq4rCU=
=TnsP
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: