Bug#1040685: systemd-cron: the MAILTO variable in /etc/crontab is not applied to generated cron units environments

[Alexandre Detiste]

crontrol: tag -1 fixed-upstream

Dear,

Thanks for caring,

Your feature request has been implemented upstream:

https://github.com/systemd-cron/systemd-cron/commit/e47e557820636905945b4bf5ff920339e259fbd5

As the repository is in the middle of a major rewrite,
a new release won't be published right away.

Le dim. 9 juil. 2023 à 11:57,  a écrit :
> The /etc/crontab files allow to define environment variables (MAILTO among 
> others) as per the man page.
> This definition should be applied to all the cron definitions as a fallback.
>
> The generator from this package parses /etc/crontab to identify jobs for 
> generating the associated systemd units.
> When parsing files in cron.d, the MAILTO is inserted as Environment if 
> explicitly defined.
> But if it not defined, the generator does not include the fallback value from 
> the /etc/crontab file.
>
> The generator should parse /etc/crontab, retrieve MAILTO and maybe PATH or 
> other env variables,
> and pass this fallback to the parsing of each file in cron.d or user crontabs.

Bug#1040685: systemd-cron: the MAILTO variable in /etc/crontab is not applied to generated cron units environments

[info]

Package: systemd-cron
Version: 1.15.21-1
Severity: normal

Dear Maintainer,

The /etc/crontab files allow to define enviroment variables (MAILTO among 
others) as per the man page.
This definition should be applied to all the cron defintions as a fallback.

The generator form this package parses /etc/crontab to identify jobs for 
generating the associated sytemd units.
When parsing files in cron.d, the MAILTO is inserted as Environment if 
explicitly defined.
But if it not defined, the generator does not include the fallback value from 
the /etc/crontab file.

The generator should parse /etc/crontab, retrieve MAILTO and maybe PATH or 
other env variables, and pass this fallback to the parsing of each file in 
cron.d or user crontabs.


Regards,


-- Package-specific info:
-- output of systemd-delta

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'stable'), (500, 'stable-security'), 
(500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), 
(200, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-cron depends on:
ii  cron-daemon-common  3.0pl1-162
ii  libc6   2.37-3
ii  python3 3.11.2-1+b1
ii  systemd [systemd-sysusers]  252.11-1
ii  systemd-sysv252.11-1

systemd-cron recommends no packages.

Versions of packages systemd-cron suggests:
ii  exim4  4.96-16
ii  exim4-daemon-heavy [mail-transport-agent]  4.96-16

-- debconf-show failed