© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi, all.
I wonder we'd have a test cases database. I think we can use the bug tracking systems come with code hosting services . People use different natural languages and have different compression preferences can all post sample archives. Maintainers mark new and essential test cases as confirmed, repeated test cases as duplicate, ...
This database, more specifically the confirmed part, can then be used as the verification tool of proposed solutions.
This bug points to several unzip packages in different distributions. It seems that info-zip people refused local encoding related patch and info-zip's board is down. We'd maintain the patch ourselves, which is not ideal. (I'm not very sure whether info-zip's license permits forking)
Is it possible to use p7zip, bsdtar or other promising projects, if any, as our foundation? if we have an CLI archiver with official supported encoding conversion capacity. The remaining work for file-roller and ark would be much easier. Changing main archiver may not be that dangerous, I believe, if we have enough test cases.