Assuming there's a new tarball in SOURCES-bin, executing mgarepo up deletes old tarball, gets new tarball, but the symlink to the old tarball in SOURCES/ isn't deleted. (and it keeps flashing... flashing... flasshing red when you do an ls SOURCES :)).
mgarepo up is there to upload a new binary, not to delete one i would say. magrepo sync -c is probably the best way to update a binary (because it's just about update until i misread) and it's going to take care about the symlinks in SOURCES :) Regards,
CC: (none) => balcaen.john
'mgarepo up' is not 'mgarepo upload', different functions.
Maybe a dupe of bug #463?
CC: (none) => thierry.vignaud
Not exactly the same I think. mgarepo sync now ignore incorrect symlinks (bug #463), but mgarepo up should still remove them.
I am closing this bugreport because we do not use symplinks anymore with new binrepo structure.
Status: NEW => RESOLVEDCC: (none) => dmorganecResolution: (none) => WONTFIX