Your message dated Fri, 12 Mar 2021 20:51:32 +0000
with message-id <e1lkoku-0000hq...@fasolo.debian.org>
and subject line Bug#984592: fixed in timgm6mb-soundfont 1.3-5
has caused the Debian Bug report #984592,
regarding musescore-common: fails to remove: rmdir: failed to remove 
'/usr/share/sounds/sf2': No such file or directory
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.)


-- 
984592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: musescore-common
Version: 2.3.2+dfsg4-12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Removing musescore-common (2.3.2+dfsg4-12) ...
  rmdir: failed to remove '/usr/share/sounds/sf2': No such file or directory
  dpkg: error processing package musescore-common (--remove):
   installed musescore-common package pre-removal script subprocess returned 
error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   musescore-common

This was caused by some package shipping a file in /usr/share/sounds/sf2
being removed earlier, resulting in dpkg emoving the directory as well.


Why don't you ship the three empty directories in the package?
Then dpkg will take care of creating and removing them and the
maintainer scripts can go away.


cheers,

Andreas

Attachment: multimedia-musiciantools_0.10.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: timgm6mb-soundfont
Source-Version: 1.3-5
Done: Thorsten Glaser <t...@mirbsd.de>

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

Debian distribution maintenance software
pp.
Thorsten Glaser <t...@mirbsd.de> (supplier of updated timgm6mb-soundfont 
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: SHA384

Format: 1.8
Date: Fri, 12 Mar 2021 20:43:31 +0100
Source: timgm6mb-soundfont
Architecture: source
Version: 1.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multime...@lists.debian.org>
Changed-By: Thorsten Glaser <t...@mirbsd.de>
Closes: 984592
Changes:
 timgm6mb-soundfont (1.3-5) unstable; urgency=medium
 .
   * Team upload.
   * Avoid rare error in prerm (Closes: #984592)
Checksums-Sha1:
 6991be7ac30d82596575e01f0cbd277f7a5fe56c 2111 timgm6mb-soundfont_1.3-5.dsc
 0ba1b23dc4679a2d758644c4430b01b929c7120f 12960 
timgm6mb-soundfont_1.3-5.debian.tar.xz
Checksums-Sha256:
 e5df6847285db192536358460d70d62963b58a278832b2d17f67b62293351e30 2111 
timgm6mb-soundfont_1.3-5.dsc
 993893c5b6265a3f7972a38d055d450d08873d097a2a2c41b010bd1858cc068c 12960 
timgm6mb-soundfont_1.3-5.debian.tar.xz
Files:
 57335a4c0338568fce650f8842f85ce1 2111 sound optional 
timgm6mb-soundfont_1.3-5.dsc
 f58976567efb3ae29580287c20192efc 12960 sound optional 
timgm6mb-soundfont_1.3-5.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—8 ☕☂☄

iQIcBAEBCQAGBQJgS83hAAoJEHa1NLLpkAfgWawQAMwltTc4qv/f2HggvB06iDnS
7G7kfNGUam+eURc35OYBBnc7NRbZqW3eZb+ajSxMNGWUq7AGh69wv1la/iLoOGaF
wHL1MJW4rOHFY7cPtP46s3B/KKsfkx+C2R+cBqzNnydFs/follBImeYsVBcszjSi
sTe6VwByogK47P7sZjHAalCXUz7fdAG8OstahONaWMSNrgwHHyeqf2g3uRJ2d7Ry
LsTb2B/TnceHSlVyfoS4lLnAcfgjv1XU6T/AlVptJ3sX81t53KHyODpSPP93t5oR
3NpJ/JB8yAhJT5nzPVQkJj+p91JD6Qbr8rO9ztl0u8CY5r87L6uWQ8yQBjpkdX7c
oF+00q9vbPrT0oLvhYlex2ThlYKtyXaim9rZXsZalMgD/oVqlKRqXeyBX7ofYG19
xO/r/j4m7lL1AASjn9TVfs/iPnTzCnsilP2mRdT+12cC7vgANMf1hD7OgdFgplEG
S7aBsghbPouCZE5xmV2+JUwWhYP7tOZBUaF2nyM77+Yyj07X8gM2MH3jXzlyVqB8
D+81cwkeZ/uvgyrgGVfVgeZuJ7J3k17Z/Yi6lwafdyjfg7PYtN6bdnux+MQSDhKK
tPszjEFNot+OB0Pe0tVBF0zSKf5xqOTSFaroawgYaUH8unrGmCO1Vyqg0Jh5ynKz
0OcTFu4vgFVGYNaDpi22
=PaZX
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to