Bug 116964 - Yast-trans-xx Fails to install in RC3 build
Summary: Yast-trans-xx Fails to install in RC3 build
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 3
Hardware: Other All
: P5 - None : Blocker
Target Milestone: ---
Assignee: Karl Eichwalder
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords: build, L10N
Depends on:
Blocks:
 
Reported: 2005-09-14 13:55 UTC by Craig Jeffares
Modified: 2005-09-14 14:59 UTC (History)
3 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Jeffares 2005-09-14 13:55:35 UTC
Retail build & CD version

Install in zh_TW or es or pt_BR, select KDE Desktop and proceed with install.

Its fine till I get an error for yast2-trans-xx-2.15.XX.noarch failed
and a message:
rpm output: 
"MD5 digest ; BAD Expected(" followed by a whole load of characters

Seems to be fine for French / German though

Having YaST language rpm's included is essential
Comment 1 Craig Jeffares 2005-09-14 13:58:09 UTC
it also fails.
Comment 2 Klaus Kämpf 2005-09-14 13:59:48 UTC
sounds more like an autobuild issue  
Comment 3 Karl Eichwalder 2005-09-14 14:05:44 UTC
I can run a test installation.  Looking for a RC3 boot medium...

Rudi, what do you think?
Comment 4 Andreas Jaeger 2005-09-14 14:16:14 UTC
Please run the following command 
$ rpm -q --checksig yast2-trans-zh_TW-2.12.4-2.noarch.rpm
yast2-trans-es-2.12.5-2.noarch.rpm yast2-trans-pt_BR-2.12.5-2.noarch.rpm

It reports for me:
yast2-trans-zh_TW-2.12.4-2.noarch.rpm: sha1 md5 gpg OK
yast2-trans-es-2.12.5-2.noarch.rpm: sha1 md5 gpg OK
yast2-trans-pt_BR-2.12.5-2.noarch.rpm: sha1 md5 gpg OK

Are you sure that your media is fine?  Please append the output of "dmesg" as well.
Comment 5 Craig Jeffares 2005-09-14 14:20:06 UTC

I'll re-burn media now. I'm retrying a number of languages and getting some
inconsistancies.

I'll re-burn cd and re-test and update bugzilla once completed.
Comment 6 Ruediger Oertel 2005-09-14 14:22:22 UTC
changed info provider setting 
Comment 7 Craig Jeffares 2005-09-14 14:25:33 UTC
cjeffares@DUB-Z10957-CJEF:~> rpm -q --checksig
/media/SU1000_001/suse/noarch/yast2-trans-pt_BR-2.12.5-2.noarch.rpm
/media/SU1000_001/suse/noarch/yast2-trans-es-2.12.5-2.noarch.rpm
/media/SU1000_001/suse/noarch/yast2-trans-zh_TW-2.12.4-2.noarch.rpm
/media/SU1000_001/suse/noarch/yast2-trans-pt_BR-2.12.5-2.noarch.rpm: sha1 md5 gpg OK
/media/SU1000_001/suse/noarch/yast2-trans-es-2.12.5-2.noarch.rpm: sha1 md5 gpg OK
/media/SU1000_001/suse/noarch/yast2-trans-zh_TW-2.12.4-2.noarch.rpm: sha1 md5 gpg OK

Still going to go ahead and re-burn and hope its only a CD issue.
Comment 8 Craig Jeffares 2005-09-14 14:59:37 UTC
It must have been a bad CD. It no longer seems to be an issue after the re-burn.
Its just odd that it kept giving and error for those files.

Sorry for any time wasted on this one.

Closing defect