[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pre-release Jigdo files appearing at cdimage.d.o, please test



Philip Hands <phil@hands.com> writes:

> I'm just running off some images, which are appearing here:
> 
>   http://cdimage.debian.org/pre-release-jigdo/

I pulled the files from rsync::debian-cd-test and used the .jigdo and
.template files locally. The i386 build was now successful, you seem
to have tweaked the files, and all but the 4th source CD were also
built successfully. The problem with the 4th CD seems to be caused by
a corrupted file.

Here are some notes:

The .jigdo files for source CDs are trying to use
http://cdimage.debian.org/cd-images/jigdo/templates/3.0BETA/source/ It
looks like the last component should be src, not source.

Jigdo is very good in finding out files that differ between
archives. While generating the 6th CD for i386 I found out I had a
corrupted file in my local archive. It would be helpful if jigdo-lite
told what files are missing or had a command lite option for doing
that.

It also looks that you have a corrupted source package in your
archive. The 4th source CD failed to build and this is what I found
out:

% zgrep pool/main/g/geomview/geomview_1.8.1.orig.tar.gz debian/indices/md5sums.gz
1cb0e07a6552e9fe122491af70171536 pool/main/g/geomview/geomview_1.8.1.orig.tar.gz

% md5sum pool/main/g/geomview/geomview_1.8.1.orig.tar.gz
1cb0e07a6552e9fe122491af70171536 pool/main/g/geomview/geomview_1.8.1.orig.tar.gz

% jigdo-file md5 pool/main/g/geomview/geomview_1.8.1.orig.tar.gz
HLDgemVS6f4SJJGvcBcVNg pool/main/g/geomview/geomview_1.8.1.orig.tar.gz

% grep pool/main/g/geomview/geomview_1.8.1.orig.tar.gz src/woody-src-4.jigdo
ZqEQbYYSbI5w_bce9C4dbw=Debian:pool/main/g/geomview/geomview_1.8.1.orig.tar.gz


-- 
Heikki Vatiainen                  * hessu@cs.tut.fi
Tampere University of Technology  * Tampere, Finland


-- 
To UNSUBSCRIBE, email to debian-cd-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: