Bug 16873

Summary:	mgarepo sync tries to re-upload existing binaries
Product:	Mageia	Reporter:	David Walser <luigiwalser>
Component:	RPM Packages	Assignee:	papoteur <yvesbrungard>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	Normal	CC:	doktor5000, mageiatools, marja11, yvesbrungard
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	mgarepo-1.10.6-5.mga5.src.rpm	CVE:
Status comment:

Description David Walser 2015-10-01 20:14:26 CEST

When you run mgarepo sync and sha1.lst needs to be updated, but one of the binaries it's updating is already in the binrepo, it is supposed to notice this and just put the correct hash in sha1.lst, and up through Mageia 4, it did.

Now, on Mageia 5, it errors out in this situations after trying to re-upload it and failing, and it doesn't properly update sha1.lst.

Reproducible: 

Steps to Reproduce:

Comment 1 papoteur 2015-11-01 11:16:23 CET

Hello David,
Can you give an example to reproduce it?

CC: (none) => yves.brungard_mageia

Comment 2 David Walser 2015-11-01 13:29:29 CET

Update a package to a newer version in both Cauldron and Mageia 5, Cauldron first (of course).  mgarepo sync for the Cauldron checkout uploads to the binrepo and updates sha1.lst.  mgarepo sync in the Mageia 5 checkout should notice that that hash has already been uploaded and just update sha1.lst, and it used to.  Now it tries to upload it again, errors out, and does not properly update sha1.lst.

Comment 3 papoteur 2015-11-01 13:38:23 CET

Thanks.
I will have a look.

Florian Hubold 2015-12-19 14:01:16 CET

CC: (none) => doktor5000

Comment 4 Marja Van Waes 2018-04-18 11:47:04 CEST

Hi all,

Is this bug still valid in Mageia 6 and/or Cauldron?

CC: (none) => mageiatools, marja11
Assignee: thierry.vignaud => yves.brungard_mageia

Comment 5 David Walser 2018-04-22 18:34:17 CEST

I guess someone needs to test it.  I haven't seen anything about it being fixed.

Version: 5 => Cauldron