Bugzilla – Bug 300982
content file contains unknown tag 'HASH'
Last modified: 2007-08-29 08:35:41 UTC
HASH SHA1 cd7eedc573cf96be0b671b966e56eb0a193d8d0a license.tar.gz HASH SHA1 4aa8ded6302e6ec85690a51af6044dffe9b21923 control.xml HASH SHA1 68d9b548d61e31e82e8834690e884afa27751287 media.1/info.txt HASH SHA1 a3006fef1fd216739efbac02bae4261b66937133 boot/i386/root HASH SHA1 c91d052a4a2d476ea5112da8f2d83734e9f293b5 boot/ppc/root HASH SHA1 39d5441616a2c2fba7fc12ed550169bd448843ea boot/x86_64/root HASH SHA1 80b24a05a9a5612b1b574c1d736532297d624d35 boot/i386/root.fonts HASH SHA1 060ef792a764ed330d558679840f2e551a0b89c9 boot/ppc/root.fonts HASH SHA1 8c6ec8baaeb86cb288fc1ae76e8f8d042777f5cb boot/x86_64/root.fonts HASH SHA1 b8e7635b10951e2747a1a9473881ffb9877d2d1d boot/i386/rescue HASH SHA1 f04dc449d076c7b35c842b7e1aaae0ed09844e65 boot/ppc/rescue HASH SHA1 77767975336450141c7e2e3fe17d03fb55601f2b boot/x86_64/rescue This should be 'META'
no, this one is really new. for META, yast assumes the file is relative to DESCRDIR and yast looks there and complains if it doesn't find the file. That's why we had to introduce a new tag. HASH $TYPE $CHECKSUM $FILE where $FILE is relative to / on the CD (without a leading "/").
*** Bug 296497 has been marked as a duplicate of this bug. ***
fixed in svn
submited. Right now additional HASH files are downloaded too, I am not sure if this behaviour is desired, but I want to discuss it with Michael.
currently the files for HASH are: license.tar.gz control.xml installation.xml media.1/info.txt boot/*/root boot/*/root.fonts boot/*/rescue yast2 should either have all these files already or never need them (like the ones below boot/...)
cooment #4: Download of all files is certainly _NOT_ desired, just look at the file sizes: 107M boot/ppc 104M boot/x86_64 100M boot/i386 310M boot/ Reopening, raising to blocker. We probably have to extent 'content' syntax to denote mandatory vs. optional files. The boot and rescue images are certainly not needed during initial installation (running in ramdisk)
Rudi, lets discuss the content file syntax
I'm not really sure the file has any semantic in the sense of "download this file". the meaning always was: this is the checksum of file foo, and only the gpg-keys were special. ok, how to get out of this mess ? quick proposal, change as needed: HASH for check&download CKSM for check only if file present ?
This should be sufficient as a temporary workaround. Reassign to Michael for further investigation
Also file "*/root.fonts" (as */root) are downloaded by Linuxrc if needed. Is that true, snwint?
Fixed in svn. Backported for beta2
Lowering severity to normal.
fixed