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

Re: don't match checksum in template data

Hello Nelson,

I'm not sure about the source of the problem - you are the first
person to report something like that. What version of jigdo-lite are
you using, and on what kernel?

On Fri, Aug 09, 2002 at 08:36:41PM -0400, Nelson Suniaga  wrote:
> Yes, I got a .iso.tmp image (why still it has a .tmp 
> extension?),

Because it isn't finished yet. Once all the data has been written to
it, it is renamed to just ".iso".

> `/mnt/iso/pool/main/g/gnome-libs/libgnome32_1.4.1.4-3_i386.deb'
> does not match checksum in template data

That is weird. It means that when jigdo read in that .deb for the
first time to find out its checksum, the checksum matched, but when it
later wanted to write the .deb to the .iso.tmp file, the checksum no
longer matched.

> Really I can't get it, can someone explain me this? ah...! almost I
> forget it: all those files with wrong checksums are differents
> everytime that I run jigdo-lite...

Very strange indeed. Are you sure the CD/harddisc containing /mnt/iso
does not have read errors?

> and other thing: if I run jigdo-lite like a "normal user" the
> .iso.tmp image is not generated completely (only 13 MB) but if I am
> root then I get a file of 678 MB

"Interesting." :-/

> This happen also with the US jigdo and template files, just the
> message it's different:
> Not downloading .template file - `woody-i386-1.template' 
> already present

This message means that the template data matches the checksum that is
listed in the .jigdo file...

> Found 375 of the 1352 files required by the
> template
> zstream.cc:282: Assertion failed, `dataUnc > 0 || (status 
> ==
> Z_STREAM_END || status == Z_OK)'

...but this indicates that the template data is corrupted.

I cannot imagine how this could possibly be a bug in jigdo - it may be
bad RAM, a broken HD... :-|

> Question 1 : I must or not use that image?

Whether you need CD 1 or CD 1_NONUS is your decision. Our
recommendation to end users is to use 1_NONUS. jigdo should be able to
download both.

> Question 2 : What happen with the DEBs with wrong md5sum after of
> the installation???

As long as there are .debs with wrong md5sums, the .iso.tmp will never
be finished; if you burn the .iso.tmp file instead of a final .iso
file to CD-R, then the installation will break in weird and wonderful

Sorry, I cannot really help you!


  __   _
  |_) /|  Richard Atterer     |  CS student at the Technische  |  GnuPG key:
  | \/¯|  http://atterer.net  |  Universität München, Germany  |  0x888354F7
  ¯ '` ¯

Reply to: