Hi folks,
bitte ueberprueft die Power Management Settungs (Energy) auf Eurem
Linux Host. Die dpcls sollten *nicht* automatisch ausgehen, sonst ist
remote management nicht moeglich.
Vielen Dank
Harri
Package: wnpp
Severity: wishlist
Owner: Andrej Shadura
* Package name: pymdown-extensions
Version : 6.2.1
Upstream Author : Isaac Muse
* URL : http://www.example.org/
* License : Expat
Programming Lang: Python
Description : extension pack for Python Mar
Anatoly Pugachev writes ("[debian] git depency on git-man"):
> Gerrit, hello.
>
> Is it possible to close bugs related to git/git-man and dependency
> between them?
>
> As I understand, fix should be quite trivial (just move git-man from
> git depends to recommends or suggests).
>
> debian bug i
Package: wnpp
Severity: wishlist
Owner: Jonas Meurer
* Package name: vagrant-bindfs
Version : 1.1.5
Upstream Author : Gaël-Ian Havard
* URL : https://github.com/gael-ian/vagrant-bindfs
* License : MIT
Programming Lang: Ruby
Description : Vagrant plugin
Spamassassin has traditionally supplied a cron.daily script. I'd like
to provide the same functionality via a systemd timer, while still
providing cron as a fallback. For the most part, this is
straightforward, but there are a few details on which I'd like feedback.
Current the cron.daily script
On Jan 07, Noah Meyerhans wrote:
> is enabled by setting CRON=1 in /etc/default/spamassassin. For users
> running systemd, I'd expect to ship a timer unit that is disabled by
> default, and have them enable it with:
>
> $ systemctl enable spamassassin-daily-maintenance.timer
>
> Any issues wit
On 1/7/20 3:18 PM, Noah Meyerhans wrote:
> Current the cron.daily script is a no-op by default, and functionality
> is enabled by setting CRON=1 in /etc/default/spamassassin. For users
> running systemd, I'd expect to ship a timer unit that is disabled by
> default, and have them enable it with:
>
On Tue, Jan 07, 2020 at 05:32:47PM -0600, Richard Laager wrote:
> Could you check for local modifications and only enable the timer if
> there were NOT local modifications?
>
> [ -e /etc/default/spamassassin ] && . /etc/default/spamassassin
> if [ -d /run/systemd/system ] && [ "$CRON" = "1" ] &&
>
Am Dienstag, den 07.01.2020, 16:18 -0500 schrieb Noah Meyerhans:
[..]
> For upgrades from versions that did not include the timer, should I
> enable the systemd timer if the user has set CRON=1?
I disagree here. I don't want you to overrule my decision for a cron-script. If
a user has enabled a c
Package: wnpp
Severity: wishlist
Owner: James Valleroy
* Package name: php-pubsubhubbub-publisher
Version : 0.0.0~git.20181009
Upstream Author : Josh Fraser
* URL : https://github.com/pubsubhubbub/php-publisher
* License : Apache-2.0
Programming Lang: PHP
On Wed, Jan 08, 2020 at 02:43:08AM +0100, Daniel Leidert wrote:
> > For upgrades from versions that did not include the timer, should I
> > enable the systemd timer if the user has set CRON=1?
>
> I disagree here. I don't want you to overrule my decision for a cron-script.
> If
> a user has enabl
Noah Meyerhans writes:
> On Wed, Jan 08, 2020 at 02:43:08AM +0100, Daniel Leidert wrote:
>> I disagree here. I don't want you to overrule my decision for a
>> cron-script. If a user has enabled a cron-job you shouldn't change that
>> to a systemd timer unit without the user's explicit approval.
Daniel Leidert writes:
...
> Please ask during installation and give the question an appropriate priority.
> By choosing the priority you can even achieve a "silent" transition for
> "normal" users and let more advanced users decide.
This strikes me as clutter that will never be removed from debc
13 matches
Mail list logo
