>
> I understand the concern against "lock-in". I also like the fact that
> the build logs on the Launchpad servers are available to everyone.
> Before I "cut over" to pushing packages from my build server to the
> PPA rather than from the Launchpad packages to the build server, I
> will find a
If the team isn't opposed to me migrating away from the Launchpad
build servers to my own build server, I think I'm going to do that.
It ranges from difficult to impossible to run arbitrary commands on
the Launchpad build servers, but I'm certain there'd be a way to work
around it . On the Wayne
On 06/06/2013 10:41 AM, Dick Hollenbeck wrote:
>
> Hi Adam,
>
> Although I am not a user of the PPA nor of pre-packaged downloads for KiCad,
> I would
> consider this offer to be a *very generous* one from you. I think my fellow
> KiCad users
> would benefit from it.
>
>
> Is there any way
Hi Adam,
Although I am not a user of the PPA nor of pre-packaged downloads for KiCad, I
would
consider this offer to be a *very generous* one from you. I think my fellow
KiCad users
would benefit from it.
Is there any way we can have a substitute plan, on the shelf, should you ever
lose
in
I can't take a look at it before the weekend.
My personal builds on the Wayne and Layne build cluster have been
working fine. The PPA builds on the Launchpad box do not. I don't
have hardly any control over the Launchpad box, and I recently
confirmed that due to how the Launchpad box service wor
I checked several of the package logs. Lucid has its own problem but all
the other recipes are failing with the same bad md5sum. Maybe somebody
updated the boost tar at sourceforge? That would not be expected.
Lucid is failing because I wanted cmake 2.8.4 and it is providing only
2.8.0.
On Ju
This is from the ppa machine? Has it happened more than once? If so, is
the computed MD5 the same each time or random?
The download can be done using wget and md5sum program can be used to
recheck binary by hand. If still same, then I suggest on the ppa machine:
Put the tar in the ppa recipe,
It looks like to autobuilder is having trouble with the boost download.
Here is the snippet from the build log:
make[3]: Entering directory
`/build/buildd/kicad-0.201306052021+4192~24~raring1/build/kicad'
[ 0%] Creating directories for 'boost'
[ 0%] Performing download step (download, verify and
On 05/31/2013 04:47 PM, Dick Hollenbeck wrote:
> In revision 4183 the boost headers have been removed from the repo.
>
> The CMakeLists.txt build environment now downloads those one time and
> installs them in the
> source tree upon first build.
In revision 4190:
a) I made the download direc
In revision 4183 the boost headers have been removed from the repo.
The CMakeLists.txt build environment now downloads those one time and installs
them in the
source tree upon first build. Subsequent builds will work as before, that is
after boost
is downloaded, un-tarred, patched, and copied t
10 matches
Mail list logo
