XPost: linux.debian.bugs.dist, linux.debian.maint.boot
From: nabijaczleweli@nabijaczleweli.xyz

On Wed, Jul 02, 2025 at 11:24:59PM +0200, Alexandre Detiste wrote:

Le mer. 2 juil. 2025 à 17:35, Chris Hofstaedtler <zeha@debian.org> a écrit :

Without any particular hat: I would expect someone wanting to drop cron to come up with some analysis of what remains to be done and what is going to break if that were to be implemented.

I would like to note that (a) "drop cron" implies
"not having a cron daemon at all" which means an obviously broken system; sd-cron is an implementation of the cron daemon, which (b) I've been successfully using exclusively, entirely uneventfully in spite of my
best efforts, for, now, years, on every class of system.

I'd also argue that root mail is likewise a necessity for well-functioning systems but that's harder to sell in 2025; either way, sd-cron's Suggests: reflects reality ‒ it can send you mail if you want or it can not,
and you get the failures like any other service failures.
or it can send matrix messages. or whatever via apprise.

Best,

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfWlHToQCjFzAxEFjvP0LAY0mWPEFAmhlsM4ACgkQvP0LAY0m WPGkVxAAn1NN/ejc1SINOCIJ2GbDpgE8karlSCGjDIUKpwPMmjxQDOs/98+lIqHg qITuZstWBMkH8iIqSZYKI7Y4Ic6tc/bbtkC/ZG0+kq00sujO8UOhzq/Kb6vq8UKv +/r+YihkNZkHxhc9auQhtkFeLHrYgvpz95WxNf/RzShXyIAZjDBGZDoKnwPbjm/b 73bgsdfZRN3R+WbdP9yVTnAYA66mH7J2NtYvGqqZcV/LfVjttoBuaHpoItK0UxJr Q6JrjPyLXuYNjkvUpUEUqChlHHTppt0g4RKVwg4lzFPzfSaER68tAR7D+WmlSPaX qpS8ciZcudfLOr00EMbTRmUput2UI6LgC++Gw78Uxh3+1Qd2fc+E4zzlTXVRTOpE fCEjYCExtRcBUWcKyq8ngOuaeBuepnIb2Y64fPoqJRipQhLwVgYRzsg1tkSj6qHZ dtL+SkOiloei88Cn4U8/xI43TMN5MpAQ8FRbShuj1pI81h3fC3QHPK6k92rni8As /LNkFryhG4yWr64jyOxEKjk4e9h8Ti2I19/kwN6fsKv/O1Idr9rgRspMhx8SNhRD dio2gLWQE1b6qtL2f1GC0nAAxk21PTmkiMEZkoJsK81MOqPHyBSNuhuNxnlp1+hq Z2uo7I6lt7JIP5NC6dgFFp+QfoET3zWKCA66EBC7edtYvs6Rgbc=
=Xb/j
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist, linux.debian.maint.boot
From: alexandre.detiste@gmail.com

Le mer. 2 juil. 2025 à 17:35, Chris Hofstaedtler <zeha@debian.org> a écrit :

Without any particular hat: I would expect someone wanting to drop cron
to come up with some analysis of what remains to be done and what is
going to break if that were to be implemented.

Hi, this has been on the back burner for me for 10 years
and наб did a systematical analysis of all the /etc/cron.... files
shipped by every single package of the distribution.

The result are the two heuristics table listed here:
https://wiki.debian.org/systemd-cron

For the other cron jobs it is assumed that the bare name
matches the bare name of the timer.

To check one system in particular, one needs to do

# apt install systemd-cron -y; systemctl list-timers

This will list two families of .timers :
- the native ones.
very common examples:
* dpkg-db-backupt.timer,
* man-db.timer,
* apt-daily.timer,
* fstrim.timer
* e2scrub_all.timer
* ...
- the remaining generated one, from the /etc/cron* files:
they all live in the cron-xxxxx.timer namespace
and physicaly in /run/systemd/generator/
* cron-daily-aptitude.timer
* cron-daily-popularity-contest.timer
* cron-daily-google-chrome.timer
* cron-monthly-check-dfsg-status.timer
* ...

Here the non free google-chrome-stable package is the only thing expecting
a cron daemon to be there somehow and going to _break_ a little if
it's not there.

All the packages from the distribution seems to have
the proprer "Depends: cron | cron-daemon" and won't break.

I still think systemd-cron would be a better default for task-laptop;
because it is said that traditional cron or the one in Debian would wake up
the system every single minute to poll /etc
& /var/lip/spool/cron/crontabs which is bad. I don't have hard proof for this.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915370#101

Relatedly, cron Recommends: default-mta | mail-transport-agent,
which we kinda also no longer expect to be installed by default on a
default install anymore. Due to how debootstrap works today, the
Recommends: is very often not fulfilled. Nevertheless I doubt we
still expect an MTA to be part of the default install.

That's the reason why systemd-cron Suggests: a MTA
instead of Recommending one; so that people
doing the switch do not get an extra MTA they don't what.
If they wanted one they would have installed it already.

A pre-installed MTA is fully supported.

Greetings

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist, linux.debian.maint.boot
From: zeha@debian.org

On Wed, Jul 02, 2025 at 05:29:58PM +0200, Cyril Brulebois wrote:

Hi,

Chris Hofstädtler <zeha@debian.org> (2025-07-02):

in a discussion today on IRC #debian-devel, it was mentioned that
cron is "important". However during the trixie development cycle,
many more packages started installing systemd timer units.
On a default install, I would therefore argue that cron is no longer
very important.

Without any particular hat: I would expect someone wanting to drop cron
to come up with some analysis of what remains to be done and what is
going to break if that were to be implemented.

I pondered that, but packages have to depend on cron anyway if they
want it. cron is not Essential: yes.

Also, at this stage of the release cycle, really?

Seemed like reconsidering the cron prio was forgotten, but from my
PoV it doesn't matter if it happens for trixie or forky.

Cc-ing debian-devel@ so that this gets discussed there.

Thanks.

Chris

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist, linux.debian.maint.boot
From: kibi@debian.org

Hi,

Chris Hofstädtler <zeha@debian.org> (2025-07-02):

in a discussion today on IRC #debian-devel, it was mentioned that
cron is "important". However during the trixie development cycle,
many more packages started installing systemd timer units.
On a default install, I would therefore argue that cron is no longer
very important.

Without any particular hat: I would expect someone wanting to drop cron
to come up with some analysis of what remains to be done and what is
going to break if that were to be implemented.

Also, at this stage of the release cycle, really?

Cc-ing debian-devel@ so that this gets discussed there.


Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmhlUHIACgkQ/5FK8MKz VSCQ0BAArrQ8g6fAhUGkFU/pHLLvKgTzthCg0inHRq8EA0t/inquT9RLoTV4ca2F b/MZNMgM30WS0N1mTntWfcVG2SE9GsLelkfM2NJ0Ohd2EGVaeuEDjdzMGjQrpXZd Nibx2VRiIjJHjVIlOx139iTfGqJ/gXTugZsziamdhisHO2mupBZSBWshH3Lp9Jq9 b+6Xf3nGMPFF1ozZsUcFa0uOrmnI0+5e1a42Jl5Om/2fnJrYX7FOcDYKzmC5LYWd yd+pUqThSG3ifWX1tMFzD1TTrJMjnhcU72wShvfZ9y6uLKgKA5LZk1kBzAWmoCOU tQtX1idEWtCbR2YpB0Snc6FVix0rJFRM+iZlke40gh6Ft+NxRxySfM1EVC20obvX 8Gjifq7ekC8jV2E/9Oy1o+NONeTPUIB4kdXCxhPWl7UPUtsTWKb0pU9SJ1esmLaL dywQEBv65D66G8lxJT7z+U/hk/GADzB7wBWT4cTuONTRJm2y6ArEwe9fY9wHmitG LOQ99pUrX+Q+BKkYO7gjpsYh/ApFJRwtRo6qIt3vvQFSZSuSL9qshUeYlUpAsp2/ v8X7B5fgwHBbpuLS015wXjTRPdiaganjUZcpOlDTrDHqZFuxpzXPH4h+ATi9Aopa sAwJa8lQgVGn2kcVnAxdIAezOIxQ0+nWlifXeM2mr85gAKczmKg=
=x6R8
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

XPost: linux.debian.bugs.dist
From: zeha@debian.org

* Richard Lewis <richard.lewis.debian@googlemail.com> [250703 23:18]:

Cyril Brulebois <kibi@debian.org> writes:

Chris Hofstädtler <zeha@debian.org> (2025-07-02):

in a discussion today on IRC #debian-devel, it was mentioned that
cron is "important". However during the trixie development cycle,
many more packages started installing systemd timer units.

On a default install, I would therefore argue that cron is no longer
very important.

Without any particular hat: I would expect someone wanting to drop
cron

maybe its priority should be demoted to standard, rather than dropping it >entirely?

Nobody asked for removal from the archive. Please read the message
Subject: and actually the quoted context.

The point was lowering the Priority: from important to optional.

Chris

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: debian@vv221.fr

Le Thu, 03 Jul 2025 22:17:44 +0100,
Richard Lewis <richard.lewis.debian@googlemail.com> a écrit :

On a default install, I would therefore argue that cron is no longer
very important.

Without any particular hat: I would expect someone wanting to drop
cron

maybe its priority should be demoted to standard, rather than dropping it entirely?

I assume "to drop" here is meaning to drop from the "Priority: important" base packages set, to reduce the size of some setups.

Dropping cron from the Debian archive would cause a lot of problems, but I don’t think this is what is discussed here.

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSUsdxM90hewW6X7Jhja3j5HOuA2AUCaGb2GwAKCRBja3j5HOuA 2A7CAQDW0lkgvBHhIoWRmhvMHynjR9SObedyd4U2cWPk8t1stAD+MM5xvhm5naEf 5qgVoVidSwndfVC1TtuHoWxP6FBF1w4=
=lEFf
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: richard.lewis.debian@googlemail.com

Cyril Brulebois <kibi@debian.org> writes:

Chris Hofstädtler <zeha@debian.org> (2025-07-02):

in a discussion today on IRC #debian-devel, it was mentioned that
cron is "important". However during the trixie development cycle,
many more packages started installing systemd timer units.

perhaps because lintian issues this tag - https://udd.debian.org/lintian-tag/missing-systemd-timer-for-cron-script?affected=yes
if you don't

On a default install, I would therefore argue that cron is no longer
very important.

Without any particular hat: I would expect someone wanting to drop
cron

maybe its priority should be demoted to standard, rather than dropping it entirely?

to come up with some analysis of what remains to be done and what is
going to break if that were to be implemented.

One issue with systemd timer units is that it is surprisingly
difficult to reliably send email from them (see eg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105792)

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)