Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: t...@mirbsd.de
Please unblock package musescore3
[ Reason ]
When merging the new README.Debian file the security team requested
to include from the musescore2 branch to the musescore3 branch, I
forgot to rename it, so it wasn’t installed in the binary package.
The upload simply renames the file in the source package.
[ Impact ]
The file, referenced from the debian-security-support package, is
not installed, possibly confusing the user.
[ Tests ]
I did a manual diff (diffoscope was too slow) between
musescore3_3.2.3+dfsg2-{18,19}_amd64.deb and only found expected
changes (even the recompiled /usr/bin/mscore3 binary differed by
a negligible amount in the data section, owing to timestamps and
the version bump).
[ Risks ]
Unless the mips64el or riscv64 buildd suddenly choke on it,
I see no risk.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[ ] attach debdiff against the package in testing
[ Other info ]
Instead of the debdiff, I state that the difference is just:
diff --git a/debian/changelog b/debian/changelog
index c990cf19..0a6a5522 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+musescore3 (3.2.3+dfsg2-19) unstable; urgency=high
+
+ * Do actually install README.Debian, too
+
+ -- Thorsten Glaser <t...@mirbsd.de> Mon, 12 May 2025 21:54:30 +0000
+
musescore3 (3.2.3+dfsg2-18) unstable; urgency=high
* Update 3.0.2+dfsg1-1 changelog entry with resolution
diff --git a/debian/musescore.README.Debian b/debian/musescore3.README.Debian
similarity index 100%
rename from debian/musescore.README.Debian
rename to debian/musescore3.README.Debian
unblock musescore3/3.2.3+dfsg2-19
