Re: [tei-council] Update on build problems with P5

I'm proposing to do that in the master branch of the git repo today. There's no point in the git repo having svn as the default. I'm also going to send James a little script to update his Jenkins today. I'll check the new Jenkins configs into git in the master branch; again, there's no point in branching for this because if we go back to svn, the old ones are in svn, but if we stick with git, then new ones are the only ones that will work. Cheers, Martin On 15-09-01 02:44 AM, Lou Burnard wrote:

as I noted earlier I have changed the default value for VCS in the P5 makefile to git so when /if my branch ever gets merged this part of the problem should go away

Sent from Samsung Mobile

-------- Original message -------- From: Martin Holmes Date: 31/08/2015 23:05 (GMT+00:00) To: tei-council@lists.tei-c.org Subject: Re: [tei-council] Update on build problems with P5

It worked, apparently:

http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/P5/rel...

What I don't know is whether the deb packages successfully built or not; I think the only way to test them would be to try to install them into a fresh vm as debs (rather than using a repo), if that will actually work.

The next problem would be gnuify-changelog.pl.

Cheers, Martin

On 15-08-31 01:35 PM, Hugh Cayless wrote:

...

Ah, *that* makes sense. Using the local.mk solution, or just switching the Makefile over to VCS=git by default is probably the answer then.

...

On Aug 31, 2015, at 16:30 , Martin Holmes wrote:

On 15-08-31 01:21 PM, Hugh Cayless wrote:

...

I honestly don’t even know what they’re for. Do people use them?

This might be something else to ask in the survey. But I wonder if (for instance) OxGarage might have them installed. Everywhere we turn there are more mysteries.

However, I think I figured at least part of this one out. The deb build process uses "rules" files, which look very much like makefiles*; and each one of those (there are six) calls the original parent P5/Makefile* again. So I have to pass the VCS variable into the deb build commands, and then have each of those rules files pass it back to the parent Makefile* at the appropriate time.

When I did that, it didn't fail quite so quickly on my local machine, and it failed in a different way. Which is progress of a sort.

*I hate make.

Cheers, Martin

...

...

On Aug 31, 2015, at 16:04 , Martin Holmes wrote:

HI all,

Hugh and I have been wrestling with the very puzzling results of the P5 build on Jenkins: while TEIP5-Documentation works as expected, generating Guidelines based on the git version, TEIP5 seems to know nothing of git, and behaves as if we're still using svn.

I think I've figured out the cause. The Makefile* includes targets "debversion" and "deb" (the latter depends on the former), and the latter seems to be shot through with explicit references to svn:

@echo BUILD: make Debian tei-p5-database package (cd debian-tei-p5-database; debclean;debuild -eXSL=${XSL} -eINJENKINS=${INJENKINS} --no-lintian -nc -b -i.svn -I.svn -uc -us)

The Documentation build does not try to build the deb packages, but the full P5 build calls:

make* VCS=git clean deb dist

and in the process of that happening, VCS is set back to svn somehow. If I call

make* VCS=git clean dist

everything works OK.

I know nothing about building debian packages, so this is a mystery to me. I don't mind learning about it, and people assure me that it's not complicated, but it might be more than I can do in a couple of weeks, at least with any confidence. Does anyone else have familiarity with building deb packages?

*I hate make.

Cheers, Martin -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org mailto:tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived