Your message dated Fri, 05 Mar 2021 17:18:25 +0000
with message-id <e1lie5p-0002cp...@fasolo.debian.org>
and subject line Bug#984592: fixed in musescore2 2.3.2+dfsg4-14
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: musescore2
Source-Version: 2.3.2+dfsg4-14
Done: Thorsten Glaser <t...@mirbsd.de>

We believe that the bug you reported is fixed in the latest version of
musescore2, 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 musescore2 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, 05 Mar 2021 17:57:30 +0100
Source: musescore2
Architecture: source
Version: 2.3.2+dfsg4-14
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser <t...@mirbsd.de>
Changed-By: Thorsten Glaser <t...@mirbsd.de>
Closes: 984592
Changes:
 musescore2 (2.3.2+dfsg4-14) unstable; urgency=medium
 .
   * Fix possible error cause in m-common.prerm (Closes: #984592)
Checksums-Sha1:
 5902c1ffb42d3d781139a9747f29b05152eb74f8 2714 musescore2_2.3.2+dfsg4-14.dsc
 b91aab316f9f391cbfb7ca32e7427f2740cc23ae 124792 
musescore2_2.3.2+dfsg4-14.debian.tar.xz
Checksums-Sha256:
 2bb8e560db09461c8790f8259f252a8e7fa84e9358a1e79257d7501975e70585 2714 
musescore2_2.3.2+dfsg4-14.dsc
 c2102006d9b91ea86ec228b166d9509ce795a2b379e5b1402aa478a812319058 124792 
musescore2_2.3.2+dfsg4-14.debian.tar.xz
Files:
 0983a0936afb13ecad1f11225b435355 2714 sound optional 
musescore2_2.3.2+dfsg4-14.dsc
 2e711b813be50a9c568fb27f14a6b25e 124792 sound optional 
musescore2_2.3.2+dfsg4-14.debian.tar.xz

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

iQIcBAEBCQAGBQJgQmRbAAoJEHa1NLLpkAfgIxMP/AnzDehNcs/tR3D79W8hG1ym
Wpm17eS+xfxZOAuieXKv0uW8Zds/O6W2HfKciNpJDFCVyI+NthScYU/syOnnHIKY
ft2+QROeGWQ3awLEMIXgq31wyyiUDjKo9JSWcNI2NKoP3wsYlatdkapIms3H/wJz
mBscFDP4ZPEvoOtpSaKpssoC4k8tllAsQkUfaon/5oPH5y9sTuaFXg5ZGZczmrmb
DZ1/AI+I2sJ9BAbHMNWqV7ufhyTkNJgGKxw+cVgObElWoe7Naa2LYQWt0BSTGqgv
uANDqyZnzCcvDCK7hCUQwBzZq4JG6dRWPr648z8mwBFZTHMHXO7xInp2+tRDI4Xs
qL9Znmu9HLVy1Fwq97YIeMEIN+dkoJ/XuvURpOgwjq5bl1NBiulbNx9skbxVcBQ4
P4UfprtR6m9WyuPhvMyAUXWfMTJC2bS0ff4cVyjwzhDMiYLoBgtYnGwTD4holjZ9
NVgoQ2W2XZU3rfe0MvL3F5ZCZ9SO3PstVjcFxA+WXMQrnezMsS62dtDYVbbs8nar
NC4Ym24Bdr2CY5BRbzpLM4FSvPhIj6rA5PwemNaVp5n3IDaNA6B3ZbAYKUrFRY8P
ZcezjqJfV4GCBkMzvfO/F8vYsSnNvKYTNzjuRsjqOfm+2R3XKj/JTW2NWCvBtjXS
T0wpugG6XiGOZ/DVA0T5
=/YoJ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to