Re: [Ltib] ./ltib -m release # externally distributable error

[Stuart Hughes]

Hi Aaron,

I re-read this again and there are a number of points/issues to comment on:

1/ You can release whatever the toolchain.  The problem you seem to have 
had in the first instance is that there was no network connection 
available and so the checks to see that the file to be copied is on the 
GPP failed.

2/ If your BSP is different from that in CVS and/or it contains content 
that is not on the GPP, then you can't make an 'official' release. 
There's a long story behind this to do with signing off approved 
content.  However, you have some options:

a) use ./ltib -m trelease
b) use the tag 'localdir' and a MANIFEST file

In the case of a), you still (may) need a network connection, but errors 
are not fatal.  The ISO image will be marked as 'non-distributable'

In the case of b) 'localdir' is a special tag that says read the
file called MANIFEST and use that to copy as the ltib source (not the 
packages).  You can generate a static manifest file from CVS using:
bin/cvsmanifest > MANIFEST.  However, I still think a network is needed 
to copy some of the package content if its missing from your LPP.  This 
is not really an option I want to support.

3/
>> Undefined subroutine &main::tag_repository called at
>> /var/backup/20091012-ltib/ltib/bin/Ltibrelease.pm line 353.
>> traceback:

This is a bug, at some point the export of tag_repository got removed 
from Ltibutils.pm.  I've put it back.  Note that if you use the tagname 
'HEAD' no CVS tagging is attempted.


Recommendations:  if it's possible/useful get your packages into LTIB 
and then you can simply run:  ./ltib -m release and use the tag HEAD, 
this is the best way.  Failing that I'd go with ./ltib -m trelease

Question: if you can say, what do you have in your LTIB tree that can't 
be put into the Savannah CVS?  Also why is making an ISO useful to you? 
 The problem with these is they can't be updated easily.

Regards, Stuart


Stuart Hughes wrote:
> Hi Aaron,
>
> I'll look into this and get back to you,  all the content on the GPP is 
> distributable so the problems you raise are bugs.
>
> Regards, Stuart
>
> address@hidden wrote:
> > At some point in my usage of the LTIB tool I switched from using the 
> > glibc
> > C library to uclibc to save space or because of compiler errors, I forget
> > which.
> >
> > Now I'm trying to bundle up my ltib tree into a binary release using:
> >
> > ./ltib -m release
> >
> > I'm getting the following error:
> >
> > checking: toolchain
> > ====================
> > Testing network connectivity
> > No network download connection available
> >
> > tc-fsl-x86lnx-ppc-uclibc-4.2.4-1.i386.rpm is not externally distributable
> > Error: tc-fsl-x86lnx-ppc-uclibc-4.2.4-1.i386.rpm  required by defconfig
> > traceback:
> >  main::release_copy_content:167
> >   main::release_main:353
> >    main::f_release:1198
> >     main:552
> >
> > If possible, I would like to create a binary iso release of my tree that
> > includes the packages in the local package pool that are required to
> > reproduce my images from source.  This iso file is not for distribution,
> > but for internal records.  Do I need to switch back to using the glibc
> > based cross-toolchain?  Also, it seems like this mode of ltib requires
> > contact with the remote CVS repository, but I would like to be able to
> > create this iso without network connectivity.
> >
> > In an attempt to produce any type of binary iso release, I started with a
> > fresh copy of the ltib today and did the following:
> >
> > $ ./ltib --preconfig config/platform/mpc8349itx/defconfig
> >
> > (here I had to get around two things that stopped the build, one being 
> > the
> > cuImage error, and the other de-selecting the samba package which had an
> > error in the configuration (attempted execution of cross-compiled test
> > code))
> >
> > $ cp config/platform/mpc8349itx/.config 
> > config/platform/mpc8349itx/defconfig
> > $ cp config/platform/mpc8349itx/nas_linux-2.6.13.4-mpc8349itx.config
> > config/platform/mpc8349itx/nas_linux-2.6.13.4-mpc8349itx.config.dev
> > $ ./ltib -m release
> >
> > This last command errors with:
> >
> > ...
> >
> > checking: sparse
> > ==================
> > License: Open Software License
> > OK GPP_STAGE: sparse-0.4.tar.gz
> > OK GPP_STAGE: sparse-0.4-array-fix.patch
> >
> > checking: git
> > ===============
> > License: GPL
> > OK GPP_STAGE: git-1.5.6.5.tar.gz
> > OK GPP_STAGE: git-1.5.6.5-no-perl-install.patch
> >
> > checking: tunctl
> > ==================
> > License: GPL
> > OK GPP_STAGE: tunctl-1.5.tar.gz
> >
> > checking: mux_server
> > ======================
> > License: LGPL
> > OK GPP_STAGE: mux_server.c
> > OK GPP_STAGE: mux_sever-1.0-fs-decl.patch
> > Undefined subroutine &main::tag_repository called at
> > /var/backup/20091012-ltib/ltib/bin/Ltibrelease.pm line 353.
> > traceback:
> >  main::release_main:353
> >   main::f_release:1235
> >    main:560
> >
> > I guess it would be nice if there were some method of producing the 
> > binary
> > iso file without having to contact the remote CVS repository.
> >
> >
> >
> > _______________________________________________
> > LTIB home page: http://ltib.org
> >
> > Ltib mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/ltib
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib