Bug 223

Summary:	"mgarepo sync" doesn't handle binaries added and removed before commit
Product:	Mageia	Reporter:	Anssi Hannula <anssi.hannula>
Component:	RPM Packages	Assignee:	Nicolas Vigier <boklm>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000, marja11, stormi-mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	mgarepo-1.99	CVE:
Status comment:

Description Anssi Hannula 2011-02-27 15:08:45 CET

If I add a tarball, and run "mgarepo sync", the tarball is handled correctly.
If I remove it before commit and run "mgarepo sync" again, the added tarball is not removed from SOURCES-bin/ and an error is printed:
error: svn: Use --force to override this restriction
svn: 'SOURCES-bin/test.bz2' has local modifications

Note that this works fine for non-binary SOURCES.

Nicolas Vigier 2011-03-01 00:26:31 CET

CC: (none) => boklm
Assignee: bugsquad => boklm

Comment 1 Samuel Verschelde 2011-08-25 22:49:42 CEST

Is this bug still valid with the new binrepo structure ?

CC: (none) => stormi

Comment 2 Marja Van Waes 2011-10-10 20:10:12 CEST

(In reply to comment #1)
> Is this bug still valid with the new binrepo structure ?

@ Anssi
Could you check, please?

CC: (none) => marja11

Comment 3 Anssi Hannula 2011-10-10 20:16:42 CEST

It is not.

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 4 Florian Hubold 2011-10-27 19:51:05 CEST

Well, from recent commit results, mgarepo sync still does not pick up changed binary files where only the content changed. Anssi, for reference, could you tell how you tested this?

CC: (none) => doktor5000

Comment 5 Anssi Hannula 2011-10-27 19:53:44 CEST

That is not what this bug was about, see the description.

Comment 6 Florian Hubold 2011-10-27 20:29:30 CEST

Uhmm, confused it with my similar report: https://bugs.mageia.org/show_bug.cgi?id=2868
Sorry for the noise.

Nicolas Vigier 2014-05-08 18:04:49 CEST

CC: boklm => (none)