Revision doesn't match upstream v2.0.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
musescore (Debian) |
Fix Released
|
Unknown
|
|||
musescore (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This bug applies to musescore (2.0.2+dfsg-1) [universe] in the Wily repo.
Go to Help -> About. The following is displayed in the dialog:
Version: 2.0.2
Revision: 3543170
But the revision should be: f51dc11
The revision number should correspond to the first 7 digits of git commit code corresponding to the v2.0.2 tagged release:
https:/
The revision number is specified in the code in the file mscore/revision.h. Simply change the number in this file to fix the bug.
Note to maintainer - updating the revision number automatically:
There is a Makefile target called "revision" (i.e. "make revision") that sets the revision number. Adding the appropriate command to debian/rules would set revision automatically. However, note the following:
- "make revision" only works in a git repository
- If using a downstream git repo you MUST use "make revision" BEFORE committing to a downstream repository. (i.e. "revision" should match the upstream git revision, not the downstream git revision).
I help maintain the MuseScore PPA on Launchpad (https:/
Changed in musescore (Debian): | |
status: | Unknown → New |
Changed in musescore (Debian): | |
status: | New → Fix Released |
Hi,
This is fixed in the Debian repository here (for 2.0.3): anonscm. debian. org/cgit/ pkg-multimedia/ musescore. git
http://
It'll be uploaded to Debian and should get into yakkety at some point.
Having said that I'm not really a fan of having upstream do this because it seems very fragile and requires manual steps which distributors must follow. It seems almost inevitable that someone will forget to do this again for a future release.
James