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
Control: reopen -1
On Tue, 2016-12-20 at 19:55 -0300, Felipe Sateler wrote:
> Unfortunately, I think the ship to fix this has sailed, as jessie was
> released a while ago already. I'm therefore closing this bug.
There is still the possibility of fixing this in a jessie point release
so I think
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
Package: systemd-cron
Version: 1.5.4-2
Severity: wishlist
Please document the limitations compared to cron in the package
description. I tried systemd-cron today but quickly discovered that it
does not send mail on cron job success. I rely on that feature of cron
quite heavily. If I knew
Package: systemd-cron
Version: 1.5.4-2
Severity: normal
File: /usr/bin/crontab
When I try to edit my crontab I get the following error. It seems to be
confusing the 0 for minute/hour in the crontab with month/day.
pabs@chianamo ~ $ crontab -e
crontab: month and day can't be 0 in
Hi all,
I'm maintaining corekeeper, which is a simple package for storing core
dumps in a username-based directory tree on disk. It uses a Linux
core_pattern to run a script to securely store the dumps.
I noticed that apport also provides a core dump handler and that
systemd will soon also
On Sun, 2015-08-30 at 13:44 +0200, Michael Biebl wrote:
> thanks for your bug report. On a first glance it doesn't look like a
> distro/downstream specific issue, so would be great if you can file
> that upstream at https://github.com/systemd/systemd/issues.
I'd rather not interact with github
Is there a tool to list interfaces based on their characteristics?
Right now at $work our initial setup code does glob eth* in
/sys/class/net in order to setup a bond interface using all NICs, so
network works no matter which NIC one plugs a cable into. It sounds
like this proposal would break
On Tue, 2015-03-10 at 18:46 +0100, David Kalnischkies wrote:
My real problem with it is the message this is sending.
Very good point, thanks.
So, while I can accept if we do this to 'fix' aptitude (and I see also
a bit of semantic value in it) I have to highlight that this is not
a
On Mon, 2015-03-09 at 08:47 +0100, Axel Beckert wrote:
which is one reason why aptitude upgrade is deprecated in favour of
aptitude safe-upgrade.
aptitude safe-upgrade has the same behaviour in this case, it still
installs sysvinit-core instead of systemd-sysv.
But apt-get has a commandline
On Sun, 2015-03-08 at 19:35 +0100, Axel Beckert wrote:
Why in the world would someone use apt-get and aptitude alternately
during a dist-upgrade?
First apt-get upgrade does the easy upgrades.
Then aptitude upgrade does the slightly harder upgrades (new packages).
Then apt-get dist-upgrade does
Package: init
Version: 1.22
Severity: important
X-Debbugs-CC: debian-rele...@lists.debian.org, Ansgar Burchardt
ans...@debian.org, syst...@packages.debian.org
I found an upgrade[1][2] path where sysvinit-core is installed instead
of systemd-sysv, while with aptitude dist-upgrade systemd-sysv
Package: dnsmasq
Version: 2.71-1
Severity: important
User: syst...@packages.debian.org
Usertags: systemd-units dependencies
X-Debbugs-CC: syst...@packages.debian.org
When installing dnsmasq on a newly installed Debian jessie system from
the daily debian-installer netinst ISO, I get the error
On Thu, 2014-08-14 at 14:15 +0200, Michael Biebl wrote:
fwiw, we are using User:
pkg-systemd-maintainers@lists.alioth.debian.org since a while now.
Ah, there are still some bugs with the old user, sorry. BTW archived
bugs can now have their usertags altered so that could be fixed.
Hm, it
On Thu, 2014-08-14 at 14:57 +0200, Michael Biebl wrote:
Hm, right. It seems so use --enable-dbus when being run under systemd.
You've proposed: Depends: dbus | sysvinit-core | upstart
But even with sysvinit-core installed, one can boot using the
init=/bin/systemd command line.
So maybe a
Package: monopd
Version: 0.9.7-1
Severity: normal
X-Debbugs-CC: pkg-systemd-maintainers@lists.alioth.debian.org
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: systemd-socket-not-stopped
When upgrading monopd on a system running systemd, I get the message
below. I think the
Control: reassign -1 dh-systemd
Control: forcemerge 751741 751744
Control: retitle 751741 dh-systemd: postinst snippets should stop foo.socket
during upgrades too
Control: affects 751741 gpsd monopd cups-daemon
On Mon, 2014-06-16 at 17:30 +0800, Paul Wise wrote:
When upgrading gpsd on a system
17 matches
Mail list logo
