Bug 1737 - Wrong checksums of Dual-Arch-CD
Summary: Wrong checksums of Dual-Arch-CD
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: www.mageia.org (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Atelier Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-10 19:17 CEST by Fabian Wannenmacher
Modified: 2011-07-19 14:38 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Fabian Wannenmacher 2011-06-10 19:17:09 CEST
Description of problem:
When you like to download the Dual-Arch-CD, you get displayed thr md5 and sha1 Checksums at http://mageia.org/de/downloads/dl.php?product=mageia-1-cd-dualarch.
They are displayed wrong.
The have to be bedf0e4aed931d238c61b08ea5d6bb9d
and 416d8272a2423fe7a0816786f0189e2320e74958.
Not 7574f31cb8429614026a61c50578d863 
and 427e25a4c8aad56c0a19fae0bbbe085f1fc641ba.
The .md5.gpg and .sha1.gpg files on the mirrors are right.

Version-Release number of selected component (if applicable):
Mageia 1 Dual Arch
Comment 1 Sebastian Schroeer 2011-07-19 12:41:35 CEST
As of 2011-07-19 12:00 CEST this bug was still not resolved. :-(

Could a sysadmin check if the Dual Arch CD offered by mirror servers is a valid release of the Mageia 1 Linux OS, please? 

Then, should this CD.iso not include any security issues and if it is an official Mageia installation CD, could you ask the web developers to change the checksums at

http://www.mageia.org/en/downloads/dl.php?product=mageia-1-cd-dualarch

please?

Actually, this bug affects all language versions of this web site...

The .iso.md5 and .sha1.md5 files offered on the mirrors correlate with the respective mageia-dual-1.iso image offered on the mirror servers.

CC: (none) => sebixmag

Comment 2 Romain d'Alverny 2011-07-19 14:38:32 CEST
Fixed at last, sorry for the delay and thanks for refreshing the bug!

Status: NEW => RESOLVED
CC: (none) => rdalverny
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.