Your message dated Thu, 24 Apr 2025 12:12:06 +0200
with message-id <6abb9108-0ac6-4341-a724-682b7bdbe...@debian.org>
and subject line Re: Bug#1103382: unblock: rust-czkawka-cli/8.0.0-1
has caused the Debian Bug report #1103382,
regarding unblock: rust-czkawka-cli/8.0.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1103382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: rust-czkawka-...@packages.debian.org
Control: affects -1 + src:rust-czkawka-cli
Please unblock package rust-czkawka-cli
[ Reason ]
czkawka is an alternative to fslint which was in Debian until buster but had
to be removed because it depended on Python2. fslint was somewhat popular at
that time (nearly 2000 installs on popcon at its peak). czkawka has the same
UI design as fslint (for the czkawka-gui), while it also provides a cli
interface (czkawka-cli), czkawka reproduces various features of fslint
(although not all), and adds new features.
Having this in trixie would restore such a software again.
Adding czkawka to the archive took multiple months because it required to add
approx 80 new rust packages which are now all in trixie. So unblocking czkawka
(gui & cli) is the very final step of this long process to finally see it in
trixie.
BTW czkawka_gui and czkawka_cli depend on czkawka_core which entered trixie
because it was accepted just a few days before the 2 other ones. It would be
nice to have all 3 in trixie. Having just czkawka_core without the other is a
bit odd since all three go together.
[ Impact ]
This is an end user software (leaf-package), so no other package depends on it
and there is no risk it breaks other packages.
If not unblocked, user would have to wait for the next stable release to have
this kind of software, or else maybe there could be a backport, but given that
backporting rust packages is complex and nearly impossible at the moment that
could be a problem. Nevertheless, doing a backport immediately after the
release of trixie is feasible in this case because all required and correctly-
versioned dependencies are in trixie.
[ Tests ]
The tests suite (autopkgtest) is run in czkawka-core which is already in
trixie. So tests passed. There is no autopkgtest for the CLI package neither
for the GUI. But I made tests on a folder to check that the app works as
expected. I performed file analysis like finding duplicates, empty files,
empty dirs, big files, temporary files, similar images, and videos, broken
files, bad extensions. This check showed that it functions properly with the
folder I used.
[ Risks ]
I don't think there is any risk.
As far as I know there is no alternative in the archive which looks like
fslint and permits to do this kind of maintenance with a GUI.
[ Checklist ]
It's a new package, so the checkboxes below are not really relevant.
[n/a] all changes are documented in the d/changelog
[n/a] I reviewed all changes and I approve them
[n/a] attach debdiff against the package in testing
[ Other info ]
There is no debdiff towards testing as it is not in testing yet.
unblock rust-czkawka-cli/8.0.0-1
--- End Message ---
--- Begin Message ---
Hi,
On 16-04-2025 21:50, Fab Stz wrote:
BTW czkawka_gui and czkawka_cli depend on czkawka_core which entered trixie
because it was accepted just a few days before the 2 other ones. It would be
nice to have all 3 in trixie. Having just czkawka_core without the other is a
bit odd since all three go together.
Unblocked because of this last reason.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
