575401 - Update metadata should be uploaded to candidates directory

Status: RESOLVED DUPLICATE of bug 578393

(Release Engineering :: General, defect, P5)

Description

[Chris AtLee [:catlee]]

It would make major update generation much faster if we could download a file that listed the hash and size of all the updates instead of having to download all the updates just in order to calculate the hash and size locally.

This could be done at the signing step.

We currently need the SHA512 hash and the file size to generate major update snippets.

Comment 1

[Chris AtLee [:catlee]]

Attachment: Untested WIP

Comment 2

[[e-mail] (:bhearsum)]

Where's the patch that contains generate-updates-metadata.py? ;-)

Also note that this would increase the set-up time for signing -- we don't have to download Linux and Mac MARs at the moment.

Comment 3

[[e-mail] (:bhearsum)]

Also, we'd get this for free in the existing MD5SUMS/SHA1SUMS if we started downloaded all of the MARs to the signing machine again. Would that work for this?

Comment 4

[Chris AtLee [:catlee]]

(In reply to comment #2)
> Where's the patch that contains generate-updates-metadata.py? ;-)

I see it in the attached patch.

(In reply to comment #3)
> Also, we'd get this for free in the existing MD5SUMS/SHA1SUMS if we started
> downloaded all of the MARs to the signing machine again. Would that work for
> this?

Not sure what you mean by this.

Comment 5

[[e-mail] (:bhearsum)]

Whoops, I didn't scroll all the way down.



We already upload MD5SUMS/SHA1SUMS files. But nevermind, because we use SHA512 for snippets.

Comment 6

[Chris AtLee [:catlee]]

Attachment: generated UPDATES.dat

Comment 7

[Chris AtLee [:catlee]]

Bug 578393 gives us the information we need.