Package Details: bleachbit-cli 4.6.0-3

Git Clone URL: (read-only, click to copy)
Package Base: bleachbit-cli
Description: Deletes unneeded files to free disk space and maintain privacy. CLI version/no GUI.
Upstream URL:
Licenses: GPL3
Conflicts: bleachbit
Provides: bleachbit
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 20
Popularity: 0.53
First Submitted: 2011-11-18 19:35 (UTC)
Last Updated: 2024-05-16 14:10 (UTC)

Dependencies (2)

Required by (5)

Sources (1)

Latest Comments

1 2 3 Next › Last »

Speranskiy commented on 2021-07-02 08:49 (UTC)

maximize-infinite-loop.patch has been changed. New b2sum is d23ba8cc1d87b976922d64ead0a4a4812b4535accc85f42e284d8ecf8eb4010d56bdf8228c8089a17afef830a2d2f8d5c78a9195c49eb8330a753a99b62e30c1

graysky commented on 2020-06-17 19:36 (UTC)

@aramirez - Yes, I didn't see that upstream pushed a new release. Updated, thanks.

aramirez commented on 2020-06-17 17:54 (UTC) (edited on 2020-06-17 18:08 (UTC) by aramirez)

Would it be possible to get rid of the python2-* dependencies? Other bleachbit packages (see below) depend on python-gobject instead of python2-gobject and do not seem to depend on python2-scandir or any variant of it.

Also, bleachbit from community is version 4.0.0. Could this package be upgraded?


graysky commented on 2016-07-05 20:27 (UTC)

Bump to v1.12-1

ansatz commented on 2016-02-11 09:00 (UTC)

==> ERROR: conflicts should be an array ==> ERROR: the build failed -> Status failed (1): bleachbit-cli fix: -conflicts='bleachbit' +conflicts=('bleachbit')

graysky commented on 2015-12-25 15:52 (UTC)

Try building in a clean chroot. You can use clean-chroot-manager if you don't wanna mess with the Arch scripts.

cli-cker commented on 2015-12-25 15:02 (UTC)

Does anyone know why this error occurs where it fails to build? I've tried building on both "linux" and "linux-grsec" kernel with the same issue each time:

graysky commented on 2015-12-03 19:56 (UTC)

@JBecker - Actually 1.92 is beta...

graysky commented on 2015-02-01 12:03 (UTC)

Thanks for the detailed explanation. Timely discussion as the dev for another package I maintain, backintime, is doing the same to remove gksu from his code as well... although his .policy file looks a little different that your version[1]. I found your bug report against bleachbit[2], pity they haven't assigned it in over a year. In any case, I don't want deviate from upstream when packaging this since calling via sudo does actually work (but as you pointed out uses /root as the config dir) and since the PKGBUILD itself does not require gksu. I'd say let's wait and see but after a year of inactivity... 1. 2.

msx commented on 2015-02-01 00:07 (UTC)

Interesting discussion about the differences between pkexec and sudo: