lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 29 May 2019 14:06:03 +0200
From:   Lukas Czerner <>
Cc:     Jan Kara <>, Theodore Ts'o <>
Subject: How to package e2scrub

Hi guys,

I am about to release 1.45.2 for Fedora rawhide, but I was thinking
about how to package the e2scrub cron job/systemd service.

I really do not like the idea of installing cron job and/or the service as
a part of regular e2fsprogs package. This can potentially really surprise
people in a bad way.

Note that I've already heard some complaints from debian users about the
systemd service being installed on their system after the e2fsprogs

What I am going to do is to split the systemd service into a separate
package and I'd like to come to some agreement about the name of the
package so that we can have the same name across distributions (at least

I was thinking about e2scrub-service for systemd service or e2scrub-cron
for the cron job. What do you think ?

Also I decided not to package the cron job for now. But if I decide to
package it in the future I'd like to change the e2scrub cron
configuration so that it can run on the systems with systemd but make
the package conflict with the e2scrub-service so that users are free to
decide how they want to use it.

Thoughts ?


Powered by blists - more mailing lists