kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

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 works, the
longstanding issue of "build date is wrong in title bar" won't be
fixed without a complete rewrite of the debian/ubuntu packaging.

However, when talking to them about that, they let me know that I can
set up my build cluster to push packages into the PPA, and end users
won't see a difference.

If the dev team doesn't object, this would likely be the easiest way
for me to get this stuff working (and fix a longstanding issue with
the PPAs at the same time.)

Adam Wolf
Wayne and Layne, LLC

On Thu, Jun 6, 2013 at 4:35 AM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
> 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 Jun 6, 2013 3:54 AM, "Dick Hollenbeck" <dick@xxxxxxxxxxx> wrote:
>>
>>
>> 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, copy it into correct dir from there.  When
>> cmake sees file there, it will skip download and go  to md5sum step and
>> continue from there.
>>
>> The ppa machine may not be providing enough contiguous cpu time for the
>> cmake C++ code to work correctly in the download function.  We can
>> alternatively provide a time out argument to the cmake download step as an
>> experiment.
>>
>>
>>
>>
>>
>> On Jun 6, 2013 12:42 AM, "Hans Henry von Tresckow" <hvontres@xxxxxxxxx>
>> wrote:
>> >
>> > 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 extract) for
>> > 'boost'
>> > -- downloading...
>> >
>> > src='http://downloads.sourceforge.net/project/boost/boost/1.53.0/boost_1_53_0.tar.bz2'
>> >
>> > dst='/build/buildd/kicad-0.201306052021+4192~24~raring1/kicad/.downloads-by-cmake/boost_1_53_0.tar.bz2'
>> >      timeout='none'
>> > CMake Error at boost-stamp/download-boost.cmake:9 (file):
>> >   file DOWNLOAD HASH mismatch
>> >
>> >     for file:
>> > [/build/buildd/kicad-0.201306052021+4192~24~raring1/kicad/.downloads-by-cmake/boost_1_53_0.tar.bz2]
>> >       expected hash: [a00d22605d5dbcfb4c9936a9b35bc4c2]
>> >         actual hash: [d41d8cd98f00b204e9800998ecf8427e]
>> >
>> >
>> >
>> >
>> > On Wed, Jun 5, 2013 at 7:31 AM, Dick Hollenbeck <dick@xxxxxxxxxxx>
>> > wrote:
>> >>
>> >> 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 directory configurable,
>> >>
>> >> b) but it defaults now to ".downloads-by-cmake" rather than
>> >> downloads-by-cmake.
>> >>
>> >>
>> >> This period lets me skip this dir when grepping in tree.  If you want
>> >> to avoid
>> >> re-downloading, then checkout version 4190 and manually rename your
>> >> downloads-by-cmake
>> >> directory to .downloads-by-cmake immediately before your first build,
>> >> and the build will
>> >> skip the download step.  Otherwise you will end up with both
>> >> directories.
>> >>
>> >> Sorry, but I think we've got this bridge crossed now and the
>> >> disruptions are behind us.
>> >> The configure-ability of the directory also brings the benefit of
>> >> putting it in some out
>> >> of tree global place.
>> >>
>> >> Dick
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> > Subsequent builds will work as before, that is after boost
>> >> > is downloaded, un-tarred, patched, and copied to include/boost/*.
>> >> >
>> >> >
>> >> > (The PPA engine will however have to download them each time I
>> >> > suppose since it starts
>> >> > with a pristine bzr checkout each time.)
>> >> >
>> >> >
>> >> >
>> >> > ----< Revision Summary >--------------------------------------------
>> >> >
>> >> > This revision makes include/boost/* files into an "external project"
>> >> > according to CMake's
>> >> > ExternalProject_Add() function. The main advantages to this strategy
>> >> > are:
>> >> >
>> >> > 1) it is easier to track the totality of all patches made to the
>> >> > particular version of
>> >> > boost in use.
>> >> >
>> >> > 2) The procedure for the download and patching is extremely well
>> >> > documented and
>> >> > reproducable, unlike now, so therefore *easier to upgrade to new
>> >> > boost*.
>> >> >
>> >> > 3) You get the full set of boost headers.
>> >> >
>> >> > 4) The KiCad repo is smaller.
>> >> >
>> >> >
>> >> > The mechanism uses a new directory in the source tree called
>> >> > downloads-by-cmake to hold
>> >> > the boost*.tar.bz2 file. This download happens only one time, ever.
>> >> > Then the tar file is
>> >> > expanded, and it is put into a scratch bazaar repo so that changes
>> >> > can be tracked. Then it
>> >> > is patched. Then a portion of the patched boost, namely the header
>> >> > portion, is copied into
>> >> > the KiCad source tree at include/boost just as now. So the end result
>> >> > is the same by the
>> >> > time a build is undertaken.
>> >> >
>> >> > The scratch repo remains in downloads-by-cmake, so that patches can
>> >> > be re-generated from
>> >> > there at any time in the future for the ExternalProject_Add()
>> >> > mechanism. You can delete
>> >> > the directory downloads-by-cmake to get a fresh start at any time.
>> >> >
>> >>
>> >>
>> >> _______________________________________________
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>> >
>> >
>> >
>> >
>> > --
>> > Henry von Tresckow (hvontres)
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >