Bug#1041911: fails to parse regular entries

Alexandre Detiste alexandre.detiste at gmail.com
Tue Jul 25 10:08:26 BST 2023


Hi,

>From the beginning systemd-cron was two other people half-project duck-taped
together to give what we have in Debian.

Since this started in 2014 I've got a bit better and I'm now reconsidering
the plan to have a C-only version as the default cron-daemon that
could be a good match for task:laptop for example.

The complete rewrite/untangling of the Python
version is a necessary step.

An other step is automated testing:
   https://github.com/systemd-cron/systemd-cron/issues/51

Which was simply not do-able with the previous codebase;
so I'm quite stuck in chicken & egg problem and need
to cut the knot somehow.

I never wrote any unit test before (even at work ...)
so this is my first attempt:
     https://github.com/systemd-cron/systemd-cron/blob/master/test/test.py

I will try to build a corpus of crontabs that triggers all the codepaths.

Your's will be included.

Greetings,

I'll certainly come back at this before version 1.16.x migrates to testing.

Le mar. 25 juil. 2023 à 10:51, Yuri D'Elia <wavexx at thregr.org> a écrit :
>
> Package: systemd-cron
> Version: 1.16.1-1
> Severity: important
>
> Unfortunately 1.16.1 doesn't accept my existing crontab, failing on the
> already on first line:
>
> crontab: unknown schedule in /tmp/crontab_o81kjgn_: */5 * * * * fetch-mail
>
> It seems that any entry with a '*' gets rejected
>



More information about the Pkg-systemd-maintainers mailing list