| Summary: | freedups does not find any duplicate files between different directories passed on the cmdline | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | andré blais <andr999> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | stormi-mageia, thierry.vignaud |
| Version: | 2 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | freedups-0.6.14-6.mga1-noarch.rpm | CVE: | |
| Status comment: | |||
|
Description
andré blais
2013-03-05 08:56:03 CET
It was run with the options freedups -a -d -f -v directory1 directory2 The directories containing a set of identical files (size, date/time, permissions) Subsequently run without the -d and/or -f flags, always with the same results Without -v, it just didn't display the files being processed, but the same summary. freedups has no maintainer currently and never got a commit in our SVN since it was imported to Mageia. Also, upstream seems very quiet since 2003, so if there's a bug I don't know how it will be fixed. Thierry, you imported it and seem to know this tool well. Can you explain freedups' behaviour here? Keywords:
(none) =>
Triaged I never used freedups this way. I always use it on a single directory where it works fine. Looking at the code, it obviously treats each directory one after the other: it doesn't consider all of them for linking duplicates in different directories. The -h option is actually misleading...
Thierry Vignaud
2013-09-13 09:37:39 CEST
Summary:
freedups does not find any duplicate files =>
freedups does not find any duplicate files between different directories passed on the cmdline I tried in on a single directory and it does indeed work well for that. Useful in certain cases, although that isn't how I expected it to work. Working across different directories would be much more useful. This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 2'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 2 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. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED Since it doesn't seem that the application was intended to work that way, and alternatives exist, might as well close it. |