Thanks, Actually, I fixed it ;)
Tracking bugs by revision number works very well for upstream, and if that interferes with Debian packaging then they would see that as Debian's problem. In any case, I was given commit access to the Debian repository recently, and made the fix in such a way that the revision will be set automatically each time new upstream code gets imported via uscan, so there is no chance of somebody forgetting to do it. Unfortunately I haven't been given access to the Debian archive so I can't upload the package into Debian, but hopefully the actual maintainer will get around to doing it soon. Peter -- You received this bug notification because you are a member of Ubuntu Studio Bugs, which is subscribed to musescore in Ubuntu. Matching subscriptions: Ubuntu Studio Bugs https://bugs.launchpad.net/bugs/1492623 Title: Revision doesn't match upstream v2.0.2 Status in musescore package in Ubuntu: Fix Committed 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://github.com/musescore/MuseScore/tree/2.0.2 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://launchpad.net /~mscore-ubuntu) and regularly contribute to the upstream code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1492623/+subscriptions -- Mailing list: https://launchpad.net/~ubuntustudio-bugs Post to : ubuntustudio-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntustudio-bugs More help : https://help.launchpad.net/ListHelp
