Bug#825890: systemd-cron: switch from Environment to EnvironmentFile

2023-07-30 Thread Paul Wise
On Sun, 2023-07-30 at 18:32 +0200, Alexandre Detiste wrote: > So this one would be denied as a Debian patch > and also as an upstream patch too. Thats unfortunate, since it means I will have to fork systemd-cron locally before I can use it to switch away from cron. -- bye, pabs https://wiki.de

Bug#825890: systemd-cron: switch from Environment to EnvironmentFile

2017-01-10 Thread Paul Wise
On Thu, 25 Aug 2016 09:31:29 +0200 Alexandre Detiste wrote: > This would break some assumptions & usage patterns; > where the same environment variable is redified each time, > this would break compatibility with vixie-cron. You could create one EnvironmentFile for each time a set of variables is

Bug#825890: systemd-cron: switch from Environment to EnvironmentFile

2016-08-25 Thread Alexandre Detiste
control: tag -1 wontfix Hi, This would break some assumptions & usage patterns; where the same environment variable is redified each time, this would break compatibility with vixie-cron. (BTW, the KDE cron editor tool always sort lines and is broken regarding this) Here's an example: > PERSISTE

Bug#825890: systemd-cron: switch from Environment to EnvironmentFile

2016-05-31 Thread Paul Wise
Package: systemd-cron Version: 1.5.4-2 Severity: wishlist With cron the environment variables are all placed in one place instead of being individually defined in each cron job. With systemd-cron, each generated service gets an individually generated Environment property instead of inheriting the