Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44519 - [musescore] Revision listed via "mscore -v" is incorrect.
Attached to Project:
Community Packages
Opened by Lake (lake) - Thursday, 09 April 2015, 22:23 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 10 April 2015, 08:10 GMT
Opened by Lake (lake) - Thursday, 09 April 2015, 22:23 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 10 April 2015, 08:10 GMT
|
DetailsDescription:
The revision listed via "mscore -v" is outdated. The correct revision for the current tag (2.0.0) is 6e47f74 but what is being reported is 3543170. Possible fix: I believe there is a step missing within the PKGBUILD... I think we have to do a "make revision" in order to update the revision.h file so that the current revision is displayed correctly. |
This task depends upon
Comment by Maxime Gauduin (Alucryd) -
Friday, 10 April 2015, 08:10 GMT
"make revision" doesn't output 6e47f74, it outputs b6b3707, so even that is "wrong". Anyway, I'm not going to manually change revision.h each time there's a new release for something as unimportant as the revision given by a CLI command for a pure GUI software. Feel free to report this upstream if it bothers you though.