Bug#1054142: cron-daemon-common: Cron now depends on systemd.

[Jerry Kaisler]

Package: cron-daemon-common
Severity: important
X-Debbugs-Cc: bugr...@ntlhelp.net

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation? cron should NOT depend on systemd.
* What exactly did you do (or not do) that was effective (or
ineffective)? tried to install a base system without systemd.
* What was the outcome of this action? It failed because systemd was not
installed.
* What outcome did you expect instead? the ability to install cron after
stripping out the hot steaming pile that is systemd.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.4-76060504-generic (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[Georges Khaznadar]

Control: tags 1054142 + moreinfo

Dear Jerry, please can you elaborate a little more about bug #1054142?

So far the only useful information is the title of the bug report.

Please can you check whether the file /etc/init.d/cron does exist in your
computer? It should contain the line
--------------------8<---------------------------
# Default-Start: 2 3 4 5
--------------------8<---------------------------

So, if your system is ruled by SYSV Init, I suppose that the file
/etc/init.d/cron is symlinked to the directories /etc/rc2.d, /etc/rc3.d,
/etc/rc3.d and /etc/rc5.d; do you find those symlinks?

Thank you for that additional information about your system.

Best regards, Georges.


Jerry Kaisler a écrit :

--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70

[Georges Khaznadar]

Hello again, Jerry,


Jerry Kaisler a écrit :

> * What led up to the situation? cron should NOT depend on systemd.
> * What exactly did you do (or not do) that was effective (or
> ineffective)? tried to install a base system without systemd.
> * What was the outcome of this action? It failed because systemd was not
> installed.
> * What outcome did you expect instead? the ability to install cron after
> stripping out the hot steaming pile that is systemd.

Your four lines of information give exactly the same information than
your bug report's title.

Please can you elaborate further?
I tried to undestand why there was a dependency on systemd.

cron depends on package init-system-helpers; when I run
`apt-cache showpkg init-system-helpers`, I can see that an old version
of init-system-helpers (version 1.56+nmu1) is depending on systemd.
Other versions do no depend on it.

Did you try to install a base system based on buster? This one is
currently old-old-stable. Please give a try with bullseye or bookworm.

As the dependency on systemd does not exist in distributions oldstable
and stable, I shall close this bug report shortly.

Best regards, Georges.

[Georges Khaznadar]

Hello again, Jerry,

one month has passed since the moreinfo query, so I close the bug report
as announced. Please reopen this bug report if you have given a try with
bullseye's or bookworm's releases of the package.

Best regards, Georges.

Georges Khaznadar a écrit :