Ok. This seems to have been a local issue on my system. Package is
building fine now.
Sorry.
On 10/12/15 18:45, Bernhard Landauer wrote:
Can someone please advise how to adapt the PKGBUILD to the new c++ ABI ?
Thank you.
CMakeFiles/mscore.dir/importmidi/importmidi_beat.cpp.o: In
functi
Can someone please advise how to adapt the PKGBUILD to the new c++ ABI ?
Thank you.
CMakeFiles/mscore.dir/importmidi/importmidi_beat.cpp.o: In function
`Ms::MidiBeat::findBeatLocations(std::multimap,
std::allocator >
> const&, Ms::TimeSigMap*, double)':
/home/bernhard/local-build
Ok. Got it.
It's fixed now.
On 04/12/15 12:23, Joachim Schmitz wrote:
>>That would mean it's not correct.
>>$(git rev-parse --short HEAD) prints the commit hash, wich is 77e980d
>This is indeed what it should be showing. And does in the nightly builds for
Mac and Windows
And I think upthread
>>That would mean it's not correct.
>>$(git rev-parse --short HEAD) prints the commit hash, wich is 77e980d
>This is indeed what it should be showing. And does in the nightly builds
for Mac and Windows
And I think upthread you've been told that you apparently forgot to do the
'make revision' s
>That would mean it's not correct.
>$(git rev-parse --short HEAD) prints the commit hash, wich is 77e980d
This is indeed what it should be showing. And does in the nightly builds for
Mac and Windows
--
Go from Idea to M
That would mean it's not correct.
$(git rev-parse --short HEAD) prints the commit hash, wich is 77e980d
On 04/12/15 11:31, Joachim Schmitz wrote:
>The about says "Unstable Prerelease for Version: 2.1.0 / Revision: 3543170"
>Looks good to me. This Rev.Nr. is obvioiusly something different from
>The about says "Unstable Prerelease for Version: 2.1.0 / Revision: 3543170"
>Looks good to me. This Rev.Nr. is obvioiusly something different from
gitrev or gitcommit. It's a completely different format anyway.
The Rev number should match the output of
git rev-parse --short HEAD
Just updated the AUR:
SUFFIX="-git" LABEL="Git Build" works great, thank you!
conflicts-array removed so the git version is now installable alongside
the stable release.
New Install message reads:
This is NOT A STABLE RELEASE!
Scores created with this dev-build may be incompatible with other
Thank you Eric, I will look into your suggestions.
Feel free to edit the PKGBUILD locally and let me know about your findings, too!
I will also think about a more suggestive pkgdesc and add a warning to be
printed by the install script.
Am 04. Dezember 2015 05:31:14 MEZ, schrieb ericfontainejazz
I've installed your musescore-git package via yaourt on my arch machine. A
few sugestions:
1) After finish compiling, yaourt checks for conflicting packages and says
"musescore-git and musescore are in conflict. Remove musescore? [y/N]". I
would prefer if these two packages did not conflict, sin
Ok, great! Thanks for the clarification!
PS. and sorry for mis-spelling your name last time, @Lasconic ! ::)
On 04/12/15 03:56, Lasconic wrote:
Hi,
We make sure that from one (official) release to another compatibility
works but git master being our playground users can't assume anything
abou
Hi,
We make sure that from one (official) release to another compatibility
works but git master being our playground users can't assume anything about
compatibility (or stability). Also, we are currently working on two
branches, master which will be come MuseScore 2.1 (and files created with
this
https://aur4.archlinux.org/packages/musescore-git/?comments=all
On 03/12/15 23:22, Bernhard Landauer wrote:
I will post a comment to the package that will be visible when you
install it in the terminal at least.
Also you can assume that the typical AUR user is normally aware that
when you have
I will post a comment to the package that will be visible when you
install it in the terminal at least.
Also you can assume that the typical AUR user is normally aware that
when you have a choice between a regular package musescore-2.0.2 and an
alternative version musescore-git-r9850.77e980d ;)
Ah, sorry for the misunderstanding, @lasonic! ;)
My understanding is that one uses a build for a certain time - the AUR
git package will not update automatically unless I update pkgver
manually and I will only do that after I have verified that the current
version works (maybe it will be better
Well, I'm not talking as a user, more as a developer and support person who
will have to deal with people complains ;)
It's not manageable to save a copy of a version for each file and
futhermore, if you send a mscz file created with MuseScore-git to someone
else, she will not be able to open it...
I have replaced my stable 2.0.2 with the -git version yesterday and
everything works perfectly while some old and annoying issues are fixed
now. :)
There was some formatting stuff in individual parts that I had to re-do
an the preferences had to be set again, but apart from that no issues at
al
Thank you!
Is there any big warning that these versions of MuseScore are not meant for
daily usage and that files created with one version might not be editable
by the next one?
lasconic
2015-12-02 22:06 GMT+04:00 oberon :
> I am happy to inform you that I have now made available a package
> *mu
I am happy to inform you that I have now made available a package
*musescore-git *in the Arch User Repository.
The PKGBUILD uses branch 'master'.
Thank you for all your great work!
Cheers
oberon
--
View this message in context:
http://dev-list.musescore.org/musescore-git-tp7579555.html
Sent fro
19 matches
Mail list logo
