Re: GUB Build Success!
On 1/3/12 3:10 PM, "Graham Percival" wrote: >On Tue, Jan 03, 2012 at 10:44:57PM +0100, m...@apollinemike.com wrote: >> Ah, I missed it cuz of the layout - my eyes are attracted by things in >>boxes. >> So my lilypond development for the day is... > >heh, I've wondered about doing something like that. > >I'm not wild about the idea, since the command-line gives you a >clue about it anyway, and it's only relevant the very first time >you do this... but sure, go ahead and push to staging. Rather than doing it this way, let's put the original paragraph in an example, even though it's not one. @example If you do not have the previous released. @end example Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Tue, Jan 03, 2012 at 10:44:57PM +0100, m...@apollinemike.com wrote: > Ah, I missed it cuz of the layout - my eyes are attracted by things in boxes. > So my lilypond development for the day is... heh, I've wondered about doing something like that. I'm not wild about the idea, since the command-line gives you a clue about it anyway, and it's only relevant the very first time you do this... but sure, go ahead and push to staging. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Jan 3, 2012, at 10:35 PM, Graham Percival wrote:
> On Tue, Jan 03, 2012 at 10:00:01PM +0100, m...@apollinemike.com wrote:
>>
>> Any ideas as to why gub hates me so early?
>>
>
> GUB hates you because you skipped over point 3 under "pre-release"
> on:
> http://lilypond.org/doc/v2.15/Documentation/contributor/minor-release-checklist
>
Ah, I missed it cuz of the layout - my eyes are attracted by things in boxes.
So my lilypond development for the day is...
diff --git a/Documentation/contributor/release-work.itexi
b/Documentation/contributor/release-work.itexi
index a3b7e86..413fc83 100644
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -95,6 +95,12 @@ git push origin release/unstable
If you do not have the previous release test-output tarball, download
it and put it in @code{regtests/}
+@example
+This box has no reason for being here except to attract attention
+to the point above about downloading the previous release test-output
+tarball.
+@end example
+
@item Prepare GUB environment by running:
@example
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Tue, Jan 03, 2012 at 10:00:01PM +0100, m...@apollinemike.com wrote: > > Any ideas as to why gub hates me so early? > GUB hates you because you skipped over point 3 under "pre-release" on: http://lilypond.org/doc/v2.15/Documentation/contributor/minor-release-checklist Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On 1/3/12 2:00 PM, "m...@apollinemike.com" wrote: > >On Jan 3, 2012, at 9:35 PM, Graham Percival wrote: > >> On Tue, Jan 03, 2012 at 09:26:48PM +0100, m...@apollinemike.com wrote: >>> I slavishly follow the instructions in the "minor release" subsection or subsubsection. Every single devel release is created by me copy&pasting from those steps. If you follow those steps as well, you should have exactly the same 2.15.23 release as the official one. >>> >>> I'm afraid that if I did the whole prep release announcement thing, >>>I'll accidentally push stuff to master that shouldn't be there, no? >> >> hmm, yes, good point. Also, I wouldn't want to have stuff in >> release/unstable unless it's an actual release. >> >> Ok, skip over the git commands, and maybe other stuff if they're >> not relevant... but the basic idea of "look in the minor releases >> section to see how to use GUB" is still valid. :) > > >Sorry to pester - I promise to be as autonomous as possible so long as >GUB starts being as autonomous as possible. > >I got : > >make LILYPOND_BRANCH=release/unstable lilypond >make -f lilypond.make >make[1]: Entering directory `/home/mikesol/gub' >mkdir -p versiondb regtests uploads > > >** >CHECK: regression tests tarball (i.e. something like >lilypond-2.13.4-1.test-output.tar.bz2 >) should be placed in regtests/ > >When you have done this, disable this check by doing: >touch regtests/ignore >** > > >exit 1 >make[1]: *** [regtests/ignore] Error 1 >make[1]: Leaving directory `/home/mikesol/gub' >make: *** [lilypond] Error 2 > >Any ideas as to why gub hates me so early? It doesn't just download a regtest file from http://lilypond.org/download/binaries/test-output/lilypond-2.15.23-1.test-o utput.tar.bz2 and save it in regtests/ Then do touch regtests/ignore and you're on your way. Carl > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Jan 3, 2012, at 9:35 PM, Graham Percival wrote: > On Tue, Jan 03, 2012 at 09:26:48PM +0100, m...@apollinemike.com wrote: >> >>> I slavishly follow the instructions in the "minor release" >>> subsection or subsubsection. Every single devel release is >>> created by me copy&pasting from those steps. If you follow those >>> steps as well, you should have exactly the same 2.15.23 release as >>> the official one. >> >> I'm afraid that if I did the whole prep release announcement thing, I'll >> accidentally push stuff to master that shouldn't be there, no? > > hmm, yes, good point. Also, I wouldn't want to have stuff in > release/unstable unless it's an actual release. > > Ok, skip over the git commands, and maybe other stuff if they're > not relevant... but the basic idea of "look in the minor releases > section to see how to use GUB" is still valid. :) Sorry to pester - I promise to be as autonomous as possible so long as GUB starts being as autonomous as possible. I got : make LILYPOND_BRANCH=release/unstable lilypond make -f lilypond.make make[1]: Entering directory `/home/mikesol/gub' mkdir -p versiondb regtests uploads ** CHECK: regression tests tarball (i.e. something like lilypond-2.13.4-1.test-output.tar.bz2 ) should be placed in regtests/ When you have done this, disable this check by doing: touch regtests/ignore ** exit 1 make[1]: *** [regtests/ignore] Error 1 make[1]: Leaving directory `/home/mikesol/gub' make: *** [lilypond] Error 2 Any ideas as to why gub hates me so early? Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
"m...@apollinemike.com" writes: >> I slavishly follow the instructions in the "minor release" >> subsection or subsubsection. Every single devel release is >> created by me copy&pasting from those steps. If you follow those >> steps as well, you should have exactly the same 2.15.23 release as >> the official one. > > I'm afraid that if I did the whole prep release announcement thing, > I'll accidentally push stuff to master that shouldn't be there, no? You could work in a directory created with git clone, then you would likely "only" be pushing to your own repository (be sure to reset it before pushing anything upstream though, or create another clone or checkout for your "upstream" simulation). -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Tue, Jan 03, 2012 at 09:26:48PM +0100, m...@apollinemike.com wrote: > > > I slavishly follow the instructions in the "minor release" > > subsection or subsubsection. Every single devel release is > > created by me copy&pasting from those steps. If you follow those > > steps as well, you should have exactly the same 2.15.23 release as > > the official one. > > I'm afraid that if I did the whole prep release announcement thing, I'll > accidentally push stuff to master that shouldn't be there, no? hmm, yes, good point. Also, I wouldn't want to have stuff in release/unstable unless it's an actual release. Ok, skip over the git commands, and maybe other stuff if they're not relevant... but the basic idea of "look in the minor releases section to see how to use GUB" is still valid. :) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Jan 3, 2012, at 9:18 PM, Graham Percival wrote: > On Tue, Jan 03, 2012 at 08:09:10PM +0100, m...@apollinemike.com wrote: >> I decided to download GUB and I think I've compiled everything (it ran for >> several hours and did not complain). >> I have no clue how it works, though. Is there any documentation beside the >> README? The thing I understand least are the patches - are the patches in >> the patches file hand-written or auto-generated? > > There's the README and the materials in the CG. Umm, did you even > *look* in the CG for "release instructions" or "releases" or > whatever that chapter is called? Chapter 11 or 12, I think it is? This I did not... > > I slavishly follow the instructions in the "minor release" > subsection or subsubsection. Every single devel release is > created by me copy&pasting from those steps. If you follow those > steps as well, you should have exactly the same 2.15.23 release as > the official one. I'm afraid that if I did the whole prep release announcement thing, I'll accidentally push stuff to master that shouldn't be there, no? Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Tue, Jan 03, 2012 at 08:09:10PM +0100, m...@apollinemike.com wrote: > I decided to download GUB and I think I've compiled everything (it ran for > several hours and did not complain). > I have no clue how it works, though. Is there any documentation beside the > README? The thing I understand least are the patches - are the patches in > the patches file hand-written or auto-generated? There's the README and the materials in the CG. Umm, did you even *look* in the CG for "release instructions" or "releases" or whatever that chapter is called? Chapter 11 or 12, I think it is? I slavishly follow the instructions in the "minor release" subsection or subsubsection. Every single devel release is created by me copy&pasting from those steps. If you follow those steps as well, you should have exactly the same 2.15.23 release as the official one. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Jan 3, 2012, at 2:20 PM, Colin Campbell wrote: > On 12-01-02 09:15 PM, Carl Sorensen wrote: >> Graham Percival percival-music.ca> writes: >> >>> On Sun, Jan 01, 2012 at 08:43:05PM +, Carl Sorensen wrote: I have made one change to the spec files (the location of netpm on lilypond.org has changed), and I did a couple of manual downloads, so I'm not sure yet that GUB is ready to build out-of-the-box. But I have demonstrated that I can get all the way through it. >>> Eh? I regularly build GUB out-of-the-box on lilydev [*]. What >>> exactly do you think you need to do? >> Well, I tried building GUB on 11.04, unsuccessfully (I have a file that >> kept a record of everything I did, if anybody is interested). >> >> Then I tried on lilydev in a virtual machine, and was also unsuccessful. >> I didn't keep a good record of what happened at that time. >> >> So then I tried with a fresh copy of Ubuntu 10.04 LTS. I was able >> to work everything out and get it to build. I will probably try to >> summarize the efforts in the miscellaneous part of the CG. >> >>> In particular, what's this >>> netpbm thing? >> The source for netpbm on lilypon.org is >> http://lilypond.org/download/gub-sources/netpbm-patched/ >> netpbm-patched-10.35.tar.bz2. >> >> The source entry in gub/gub/specs/netpbm.py is >> http://lilypond.org/download/gub-sources/netpbm-patched-10.35.tar.bz2 >> >> When the download doesn't succeed, no error is thrown. So as long as you >> have the file when it comes time to extract it, you can go ahead. But if >> the file isn't there, you end up with an error. >> >> I've made a patch that fixes it and will send it to you. >> > I decided to download GUB and I think I've compiled everything (it ran for several hours and did not complain). I have no clue how it works, though. Is there any documentation beside the README? The thing I understand least are the patches - are the patches in the patches file hand-written or auto-generated? Cheers, MS ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On 12-01-02 09:15 PM, Carl Sorensen wrote: Graham Percival percival-music.ca> writes: On Sun, Jan 01, 2012 at 08:43:05PM +, Carl Sorensen wrote: I have made one change to the spec files (the location of netpm on lilypond.org has changed), and I did a couple of manual downloads, so I'm not sure yet that GUB is ready to build out-of-the-box. But I have demonstrated that I can get all the way through it. Eh? I regularly build GUB out-of-the-box on lilydev [*]. What exactly do you think you need to do? Well, I tried building GUB on 11.04, unsuccessfully (I have a file that kept a record of everything I did, if anybody is interested). Then I tried on lilydev in a virtual machine, and was also unsuccessful. I didn't keep a good record of what happened at that time. So then I tried with a fresh copy of Ubuntu 10.04 LTS. I was able to work everything out and get it to build. I will probably try to summarize the efforts in the miscellaneous part of the CG. In particular, what's this netpbm thing? The source for netpbm on lilypon.org is http://lilypond.org/download/gub-sources/netpbm-patched/ netpbm-patched-10.35.tar.bz2. The source entry in gub/gub/specs/netpbm.py is http://lilypond.org/download/gub-sources/netpbm-patched-10.35.tar.bz2 When the download doesn't succeed, no error is thrown. So as long as you have the file when it comes time to extract it, you can go ahead. But if the file isn't there, you end up with an error. I've made a patch that fixes it and will send it to you. It would be very useful if the build process *did* barf when, and as soon as, a download fails. It's painful to wait several hours into make lilypond, only to get a delayed error from a missing file. Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Tue, Jan 03, 2012 at 04:15:06AM +, Carl Sorensen wrote: > Graham Percival percival-music.ca> writes: > > [*] after installing libmpfr-dev, which is mentioned in the > > README. > > In looking at my notes, it appears that I may have failed on my lilydev > install because I didn't install libmpfr-dev. (BTW, the package name > libmpfr-dev is not in the README; I've made a patch to put it there, > and I'll send that to you too. Well, line 117 says - the libmpfr library (and development headers) Different distributions are going to call it different things; I wouldn't be surprised if (completely random made-up example) gentoo called it devel-mpfr-lib, for example. I'm not arguing against clarifying the library name for ubuntu in the README; ubuntu is a very widely used distribution, and lilydev is our official development environment, after all. oh, could you add a note to the "lilydev 2.0" tracker issue to ask for libmpfr-dev to be installed? I doubt that many people using lilydev will be playing with GUB, but that library is IIRC less than 100 Kb, so we might as well install it. The same goes for anything else you had to install. > It will then be interesting to see if lilydev has everything needed to > do make lilypond. On my vanilla 10.04 installation, there were some > additional things I needed to install in order to make lilypond, even > after completing make bootstrap. Hmm. GUB should auto-download&install anything else it needs -- although that said, I now recall that I have a lot of development packages that I automatically install whenever I install a new OS. So maybe my systems have these extra things already installed. > Anyway, it's been more learning than I expected, but I think I can now > learn to modify the installers on GUB for windows and OS/X. Great! - apparently the OSX thing is already solved. See the tracker issue, consult with Christian, and maybe look at my patches to GUB on the subject to see what you need to do. (hint: it's a 1-line patch) - no clue about the lilypond-book thing; if we keep on using msvrt, you'll need to wade into the vast murky waters of "how do we distribute python modules", which I know absolutely nothing about. It's probably going to end up being a 1-line patch again, but I wouldn't be at all surprised if it turns out to be a "15 more hours to change 1 line" thing. Oh, another hint off the top of my head: try searching (git grep) for the python modules we *are* distributing. Maybe you'll luck out and find a nice compact list of "add these modules to GUB" somewhere, in which case the whole thing could be solved in 2 minutes. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
Graham Percival percival-music.ca> writes: > > On Sun, Jan 01, 2012 at 08:43:05PM +, Carl Sorensen wrote: > > I have made one change to the spec files (the location of netpm > > on lilypond.org has changed), and I did a couple of manual > > downloads, so I'm not sure yet that GUB is ready to build > > out-of-the-box. But I have demonstrated that I can get all the > > way through it. > > Eh? I regularly build GUB out-of-the-box on lilydev [*]. What > exactly do you think you need to do? Well, I tried building GUB on 11.04, unsuccessfully (I have a file that kept a record of everything I did, if anybody is interested). Then I tried on lilydev in a virtual machine, and was also unsuccessful. I didn't keep a good record of what happened at that time. So then I tried with a fresh copy of Ubuntu 10.04 LTS. I was able to work everything out and get it to build. I will probably try to summarize the efforts in the miscellaneous part of the CG. > In particular, what's this > netpbm thing? The source for netpbm on lilypon.org is http://lilypond.org/download/gub-sources/netpbm-patched/ netpbm-patched-10.35.tar.bz2. The source entry in gub/gub/specs/netpbm.py is http://lilypond.org/download/gub-sources/netpbm-patched-10.35.tar.bz2 When the download doesn't succeed, no error is thrown. So as long as you have the file when it comes time to extract it, you can go ahead. But if the file isn't there, you end up with an error. I've made a patch that fixes it and will send it to you. > > [*] after installing libmpfr-dev, which is mentioned in the > README. In looking at my notes, it appears that I may have failed on my lilydev install because I didn't install libmpfr-dev. (BTW, the package name libmpfr-dev is not in the README; I've made a patch to put it there, and I'll send that to you too. I'm currently in the midst of make bootstrap on lilydev. I expect it to continue to completion. It will then be interesting to see if lilydev has everything needed to do make lilypond. On my vanilla 10.04 installation, there were some additional things I needed to install in order to make lilypond, even after completing make bootstrap. Anyway, it's been more learning than I expected, but I think I can now learn to modify the installers on GUB for windows and OS/X. I'll be running make lilypond overnight tonight. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On 12-01-01 03:17 PM, Graham Percival wrote: On Sun, Jan 01, 2012 at 08:43:05PM +, Carl Sorensen wrote: I have made one change to the spec files (the location of netpm on lilypond.org has changed), and I did a couple of manual downloads, so I'm not sure yet that GUB is ready to build out-of-the-box. But I have demonstrated that I can get all the way through it. Eh? I regularly build GUB out-of-the-box on lilydev [*]. What exactly do you think you need to do? In particular, what's this netpbm thing? [*] after installing libmpfr-dev, which is mentioned in the README. Are you using the latest GUB? IIRC there were a few updates some months ago, when Colin and/or Phil tested a few things. Cheers, - Graham ___ The change I made was updating the /spec file to bring curl up to 7.22 in early November. In checking the date, I see that I worked from https://github.com/janneke/gub and that the files in lilypond.org/download/gub-binaries and /gub-sources haven't been updated since March'11. Is it possible that the change to the various tools used to build GUB or by GUB to build liloypond, are looking in outdated places or incompatible places? Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB Build Success!
On Sun, Jan 01, 2012 at 08:43:05PM +, Carl Sorensen wrote: > I have made one change to the spec files (the location of netpm > on lilypond.org has changed), and I did a couple of manual > downloads, so I'm not sure yet that GUB is ready to build > out-of-the-box. But I have demonstrated that I can get all the > way through it. Eh? I regularly build GUB out-of-the-box on lilydev [*]. What exactly do you think you need to do? In particular, what's this netpbm thing? [*] after installing libmpfr-dev, which is mentioned in the README. Are you using the latest GUB? IIRC there were a few updates some months ago, when Colin and/or Phil tested a few things. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
GUB Build Success!
I have successfully built lilypond with GUB on Ubuntu 10.04 LTS. I have the following files in the uploads directories: carl@carl-MacBookPro:~/src/gub$ ls uploads lilypond-2.15.24-1.darwin-ppc.tar.bz2 lilypond-2.15.24-1.darwin-x86.tar.bz2 lilypond-2.15.24-1.documentation.tar.bz2 lilypond-2.15.24-1.freebsd-64.sh lilypond-2.15.24-1.freebsd-x86.sh lilypond-2.15.24-1.linux-64.sh lilypond-2.15.24-1.linux-ppc.sh lilypond-2.15.24-1.linux-x86.sh lilypond-2.15.24-1.mingw.execarl@carl-MacBookPro:~/src/gub$ ls uploads lilypond-2.15.24-1.darwin-ppc.tar.bz2 lilypond-2.15.24-1.darwin-x86.tar.bz2 lilypond-2.15.24-1.documentation.tar.bz2 lilypond-2.15.24-1.freebsd-64.sh lilypond-2.15.24-1.freebsd-x86.sh lilypond-2.15.24-1.linux-64.sh lilypond-2.15.24-1.linux-ppc.sh lilypond-2.15.24-1.linux-x86.sh lilypond-2.15.24-1.mingw.exe lilypond-2.15.24-1.test-output.tar.bz2 lilypond-2.15.24-1.webdoc.tar.bz2 lilypond-2.15.24.tar.gz localdoc signatures webdoc webtest lilypond-2.15.24-1.test-output.tar.bz2 lilypond-2.15.24-1.webdoc.tar.bz2 lilypond-2.15.24.tar.gz localdoc signatures webdoc webtest I have made one change to the spec files (the location of netpm on lilypond.org has changed), and I did a couple of manual downloads, so I'm not sure yet that GUB is ready to build out-of-the-box. But I have demonstrated that I can get all the way through it. Thanks for your help, Graham. In particular, the reminder to check the logfiles when the process hung was very helpful as I moved forward. Next step: do a clean install of Ubuntu 10.04 and start over again with my test instructions to make sure I've captured everything I did. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
