Bug 1001 - Wrong instructions to check that the signatures of ISO match
Summary: Wrong instructions to check that the signatures of ISO match
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: www.mageia.org (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://mageia.org/en/downloads/dl.php...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 00:32 CEST by Gerald
Modified: 2011-04-27 10:15 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Gerald 2011-04-27 00:32:05 CEST 
Description of problem:

The Mageia website suggests to check that the signatures match as soon as the download of the Mageia Beta2 ISO is complete. 

1. In the instructions the name of the ISO-file is not correct
   website: mageia-1-beta2-dvd-i586.iso
   mirror:  mageia-dvd-1-Beta2-i586.iso

2. The second check should be: sha1sum (not sha1) ?

Version-Release number of selected component (if applicable):

Beta2
Comment 1 Ahmad Samir 2011-04-27 03:01:25 CEST 
@Romain, maybe the file name of the ISO should be generic, so that it works for all ISO releases.

CC: (none) => rdalverny
Assignee: mageia-webteam => bugsquad

Comment 2 Romain d'Alverny 2011-04-27 10:15:21 CEST 
(In reply to comment #0)
> 1. In the instructions the name of the ISO-file is not correct
>    website: mageia-1-beta2-dvd-i586.iso
>    mirror:  mageia-dvd-1-Beta2-i586.iso

Fixed.

> 2. The second check should be: sha1sum (not sha1) ?

Fixed.

Thanks for the report.

(In reply to comment #1)
> @Romain, maybe the file name of the ISO should be generic, so that it works for
> all ISO releases.

Yep, but the nomenclature has to be specified and checked on ISO builds (the draft I posted on marcom didn't make it so far).

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.