Your message dated Tue, 28 Jul 2015 16:00:34 -0400
with message-id <a47fe6d08a11717b87f14bb57bbea...@riseup.net>
and subject line Patch accepted and fixed by upstream
has caused the Debian Bug report #789481,
regarding musescore: FTBFS on architectures with unsigned char
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.)
--
789481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: musescore
Version: 2.0.1+dfsg-2
Tags: patch
It is failing to build on several architectures with errors like:
/«BUILDDIR»/musescore-2.0.1+dfsg/libmscore/element.h:48:18: error: enumerator
value -1 is outside the range of underlying type 'char'
See https://buildd.debian.org/status/package.php?p=musescore&suite=sid
Here's a "patch":
perl -i -pe 's/char/signed char/ if /^enum class (Grip|NoteCaseType) : char/;' \
`find -name '*.h'`
One might want to change some other enums to signed char, for
consistency, but that "patch" is sufficient, it seems. Tested on
arm64.
((
I think there's another problem, not so easy to reproduce, some kind
of race condition that can occasionally result in:
Error copying file "[...]/musescore-2.0.1+dfsg/all.h" to
"[...]/musescore-2.0.1+dfsg/build.release/all.h".
But I doubt that's worth investigating. If it became a frequent
problem one could presumably just disable parallel building.
))
--- End Message ---
--- Begin Message ---
Details: https://github.com/musescore/MuseScore/pull/2110
--
tiago
--- End Message ---
