Ping?

Nobody provided a patch.

Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

a patch is welcome :)

CC: (none) => marja11

boklm leave Mageia

Assignee: boklm => bugsquad
Status: ASSIGNED => NEW

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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

This is still present and valid, please don't close it. Sorry, but "nobody provided a patch" was the only answer until now, which does not fix the issue.

Resolution: WONTFIX => (none)
Status: RESOLVED => REOPENED
CC: (none) => doktor5000
Version: 1 => 4

Apart from "mgarepo upload"ing all source files, the only workaround that I know of is to remove the changed files from the sha1.lst.

CC: (none) => remi

(In reply to Rémi Verschelde from comment #8)
> the only workaround that I
> know of is to remove the changed files from the sha1.lst.

Do you really expect me to create checksums for all source files, and manually compare them to sha1.lst and remove offending ones? That is exactly the purpose that mgarepo should fulfill, no?

> (In reply to Rémi Verschelde from comment #8)
> > the only workaround that I
> > know of is to remove the changed files from the sha1.lst.
> 
> Do you really expect me to create checksums for all source files, and
> manually compare them to sha1.lst and remove offending ones? That is exactly
> the purpose that mgarepo should fulfill, no?

Nope, I just considered that you knew which files changed (since comment 0 says "they had all changed contents"), and in such case you just have to remove all of them from sha1.lst to force their upload.

And I said "workaround", of course I'd like mgarepo sync to do the sync in a better way, checking for sha1 sums and uploading the changed files. But since I won't provide a patch for mgarepo myself, I'm sharing my workaround.

Assuming this bug is still valid, I didn't find anything in the git & svn logs that suggests it got fixed (but may have overlooked it).

@ papoteur

Feel free to re-assign if you don't want to be the assignee ;-)

Assignee: bugsquad => yves.brungard_mageia

I've implemented this feature in mgarepo. It's activated with the -u or --upload option. The next release of mgarepo will include it.

Status: REOPENED => RESOLVED
CC: (none) => dan
Resolution: (none) => FIXED