On 8/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
> Bruce Dubbs wrote:
> > M.Canales.es wrote:
> >> Hi,
> >>
> >> jhalfs has reported this when trying to build LFS-6.3:
> >>
> >> lfs-bootscripts-6.3.tar.bz2 does not match MD5SUMS value
> >> NEW MD5SUM: 4898129064e2edf93d52c9def3053ae1  lfs-bootscripts-6.3.tar.bz2
> >> udev-config-6.3.tar.bz2 does not match MD5SUMS value
> >> NEW MD5SUM: 154bb3fd0aa36506ffa57e88cc08910d  udev-config-6.3.tar.bz2
> >>
> >> Both packages has been downloaded from
> >> http://www.linuxfromscratch.org/lfs/downloads/6.3/
> >>
> >>
> >> That MD5SUM discrepancies need be verifyed and fixed on the XML sources to 
> >> can
> >> release both jhalfs-2.3.1 and the LFS LiveCD. An entry on the errata page
> >> don't solve the issue.
> >
> > The best fix is to replace the config files for 6.3 on quantum with the
> > ones that match the md5sums in the book if we can.  I'll investigate.
>
> OK, I copied the config files from development to 6.3 and renamed
> appropriately.  The md5sums match what is in the book. That should fix
> the jhalfs problem.

Except that the extracted directory name will not be
lfs-bootscripts-6.3, but lfs-bootscripts-2007****, which will probably
make jhalfs barf.

> If I get the time, I'll investigate why my build script changed the
> contents.

Since you're extracting the contents and rolling your own tarball, the
directory name and all the file metadata changes (e.g., your uid is
not the same as mine). It would be better if those tarballs were
manually generated or the releases just used the same dated tarball.

This was also the reason why we stopped having the lfs-bootscripts and
udev-config tarballs generated at commit time. Instead, someone (me or
Bryan or whoever) manually generates them and updates the book
version/md5sum.

I'll be happy to help fix up any issues, but it might help if I could
read your render script.

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to