Re: missing files in .jigdo are not missing?
Richard Atterer (richard@2007.atterer.net) wrote on 11 April 2007 12:24:
>On Sun, Apr 08, 2007 at 07:16:18PM -0300, Carlos Carvalho wrote:
>> I'm still trying to create .iso using jigdo-mirror. Removing
>> --no-check-files from the default made it proceed, however some CDs
>> and DVDs don't build because it complains about missing files.
>>
>> How can one see which files are missing? I took the list from the
>> jigdo of one of the CDs that doesn't build, because it says there's
>> one missing, and verified that all do exist in the specified location.
>
>You can output a list of missing files using the "jigdo-file print-missing"
>command.
After posting I discovered it appears in the logs. Here's an example
for the source.dvd, I can send you the complete list if necessary:
Found 5935 of the 5943 files required by the template
Copied input files to temporary file `image.tmp' - repeat command and supply mor
e files to continue
2007-04-09 20:25:38: 8 parts still missing from image
20:25:41 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/a/ar
abtex/arabtex_3.11.orig.tar.gz [582121/582121] -> "arabtex_3.11.orig.tar.gz" [1]
20:25:46 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/g/gs
oap/gsoap_2.7.6d.orig.tar.gz [5866490/5866490] -> "gsoap_2.7.6d.orig.tar.gz" [1]
20:26:01 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/bo
s/bos_1.1.orig.tar.gz [20395114/20395114] -> "bos_1.1.orig.tar.gz" [1]
20:26:46 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/c/cm
-super/cm-super_0.3.3.orig.tar.gz [67064131/67064131] -> "cm-super_0.3.3.orig.ta
r.gz" [1]
20:26:57 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/bo
ost/boost_1.33.1.orig.tar.gz [14358143/14358143] -> "boost_1.33.1.orig.tar.gz" [
1]
20:26:57 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/a/ar
chzoom/archzoom_0.5.1-1.diff.gz [108481/108481] -> "archzoom_0.5.1-1.diff.gz" [1
]
20:28:00 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/be
neath-a-steel-sky/beneath-a-steel-sky_0.0372.orig.tar.gz [69379952/69379952] ->
"beneath-a-steel-sky_0.0372.orig.tar.gz" [1]
20:28:01 URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/b/ba
ycomepp/baycomepp_0.10.orig.tar.gz [474619/474619] -> "baycomepp_0.10.orig.tar.g
z"
>Since no-one else appears to have problems, it seems that the .jigdo file
>is OK. I'm not sure what the problem at your side could be.
Maybe it's just that no-one *notices* it. At first I put maxMissing=0,
on the assumption that we're a full mirror and so we should have
everything. However this breaks already for the first architecture,
because 2 out of 3 dvds and some cds don't complete for alpha.
>jigdo-file will calculate the md5sum of files before copying them to
>the image, so even if the file is there and its name appears to be
>correct, it will not be copied over if its content doesn't match.
I checked some of the filenames and size (not checksums) and what
comes from us.cdimage matches with what we have. Also, during the
build process at least two full updates of our mirror were done, so
it's not a problem of us being behind the latest version. Therefore,
if they differ there's a problem. We have testing and unstable also,
so there should be nothing that us.cdimage uses that we don't have.
I agree that the problem may not be in jigdo but in the iso image
itself using something different. How can we investigate the issue?
Reply to: