Re: [Ltib] using ./ltib -m release

[Stuart Hughes]

Hi Sergey,

Do you have any output from when the .md5 file was removed? maybe it's
in the wrong format.  It should have been downloaded when the toolchain
was installed from
bitshrine.org/gpp/tc-fsl-x86lnx-e300c3-4.1.78-1.i386.rpm.md5. but in any
case I've attached it so just drop this into /opt/freescale/pkgs.

Another thing, unless you have write access to the SCM repository, -m
release is not going to work for you.  Instead you should use -m
trelease.  This is for test releases (unofficial releases).

BTW: are you using a freescale BSP or one from ltib.org?

Regards, Stuart

On 15/11/13 11:14, Sergey Ablalimov wrote:
> I try to execute the command "tib-mpc83xx-ym160$ ./ltib -m release" for
> our custom board. And I get the output below.
> File tc-fsl-x86lnx-e300c3-4.1.78-1.i386.rpm is in /opt/freescale/pkgs/
> ltib can't find md5 summ for it. When I create this file it is removed
> by ltib.
> What i must to do?
> 
> 
> 
> commonsrv:~/ltib-mpc83xx/ltib-mpc83xx-ym160$ ./ltib -m  release
> You are about to create an iso image from this working project.
> This will include all sources and built rpms for the target platform,
> as well as the LTIB source code.
> 
> 
> 
> Before doing this, you should have done the following:
> 
>  1. Make sure you have committed any changes
>  2. Make sure your source code is up to date
>  3. Configured ltib for the target
>  4. Run ltib to build all the selected packages
> 
> Do you want to continue: Y|n ?
> Y
> Please enter the tag name for this release
> Giving the name 'HEAD' will use the head of the trunk, or current branch.
> 
> gathering a list of existing remote tags, pls wait:
> 
> Checking for unsaved config changes:
> Checking that the source tree is up to date:
> 
> 
> 
> Checking licensing and external availabity of sources
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> The following constraints/checks are enforced:
> 
> 1/ All source/patches in the default configuration must be distributable.
> 
> 2/ Any sources/patches not in the default configuration that are not
> distributable are not be copied to the ISO image.
> 
> 3/ Any content copied to the ISO image has it's md5 checksum verified by
> downloading a fresh copy of the md5sum file and using it to verify the
> content it checksums.
> 
> 4/ Files already present on local disk in the LPP will be used.  Any
> missing files will be downloaded from either the GPP staging area
> or the CPP (Clickthru) staging area.
> 
>                   ------------------------
> 
> 
> Copying content from default configuration (mandatory)
> ---------------------------------------------------------
> 
> checking: toolchain
> ====================
> Testing network connectivity
> OK GPP_STAGE:
> 
> OK GPP_STAGE: tc-fsl-x86lnx-e300c3-4.1.78-1.i386.rpm
> WARN: skipping md5sum check for
> /opt/freescale/pkgs/tc-fsl-x86lnx-e300c3-4.1.78-1.i386.rpm, md5 file was
> not found
> cp: cannot stat
> `/opt/freescale/pkgs/tc-fsl-x86lnx-e300c3-4.1.78-1.i386.rpm.md5': No
> such file or directory
> Died at /home/common/ltib-mpc83xx/ltib-mpc83xx-ym160/bin/Ltibrelease.pm
> line 57.
> traceback:
>  main::release_copy:57
>   main::release_copy_content:156
>    main::release_main:337
>     main::f_release:1234
>      main:560
> 
> Exiting on error or interrupt
> Please see | tee RELEASE_COPY_CONTENT for details
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/ltib
>

tc-fsl-x86lnx-e300c3-4.1.78-1.i386.rpm.md5
Description: Text document