Your message dated Mon, 21 Mar 2016 13:23:10 +
with message-id
and subject line Bug#818698: fixed in systemd 229-3
has caused the Debian Bug report #818698,
regarding does not convert crontabs correctly
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Mon, 21 Mar 2016 13:23:10 +
with message-id
and subject line Bug#816767: fixed in systemd 229-3
has caused the Debian Bug report #816767,
regarding systemd-coredump: Failed to connect to coredump service: No such file
or directory
to be marked as done.
This means that you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 21 Mar 2016 14:11:44 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines
libnss-resolve libsystemd0 libs
systemd_229-3_source.changes uploaded successfully to localhost
along with the files:
systemd_229-3.dsc
systemd_229-3.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
___
Pkg-systemd-maintainers mailing
> Is this the real output from systemd-cron? Then it should be fixed:
Nope, it is not.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49e
Your message dated Mon, 21 Mar 2016 12:38:31 +
with message-id
and subject line Bug#766053: fixed in systemd-cron 1.5.4-1
has caused the Debian Bug report #766053,
regarding Cannot edit user crontabs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Mon, 21 Mar 2016 12:38:32 +
with message-id
and subject line Bug#780685: fixed in systemd-cron 1.5.4-1
has caused the Debian Bug report #780685,
regarding /usr/bin/crontab: Should display error message when crontab doesn't
exist yet
to be marked as done.
This means that yo
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 28 Jan 2016 09:44:29 +0100
Source: systemd-cron
Binary: systemd-cron
Architecture: source amd64
Version: 1.5.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Systemd Maintainers
Changed-By: Alexandre De
On 21 Mar 2016 09:23, "Alexandre Detiste"
wrote:
>
> 2016-03-21 12:54 GMT+01:00 Felipe Sateler :
> >
> > > [Service]
> > > Type=oneshot
> > > IgnoreSIGPIPE=false
> > > ExecStart=foo
> >
> > Is this the real output from systemd-cron?
>
>
> No
>
> >
> > Then it should be fixed:
> >
> > 1. Exec* need
2016-03-21 12:54 GMT+01:00 Felipe Sateler :
>
> > [Service]
> > Type=oneshot
> > IgnoreSIGPIPE=false
> > ExecStart=foo
>
> Is this the real output from systemd-cron?
No
>
> Then it should be fixed:
>
> 1. Exec* need their first argument to be a full path.
> 2. Exec* are not executed via a shell.
systemd-cron_1.5.4-1_amd64.changes uploaded successfully to localhost
along with the files:
systemd-cron_1.5.4-1.dsc
systemd-cron_1.5.4.orig.tar.gz
systemd-cron_1.5.4-1.debian.tar.xz
systemd-cron-dbgsym_1.5.4-1_amd64.deb
systemd-cron_1.5.4-1_amd64.deb
Greetings,
Your Debian queu
> It's hard to reproduce, some works some don't;
True, the same entry might works sometimes, and sometimes niot.
> Hum, it can replace cron, but only on explicit user request.
> All the cron job consumers depends on "cron | cron-daemon"
> and will always pull vixie cron first.
Right, it's the ad
Processing commands for cont...@bugs.debian.org:
> tags 805442 + pending
Bug #805442 [systemd] systemd: Automatic logout when changing the Target
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
805442: http://bugs.debian.org/cgi-bin/bugreport
> > > This fix is not even list in upstream v230 changelog
> > > not really serious.
> No wonder, as there is no v230 release yet there also is no NEWS for
> it yet :-)
I guess that explains it :)
> Yes, I do plan to do an upload this week.
Great, thanks Martin.
Michael
--
Michael Meskes
Micha
On 20 March 2016 at 08:44, Michael Meskes wrote:
> On Sat, Mar 19, 2016 at 09:29:21PM +0100, Alexandre Detiste wrote:
>> Have a look at the generated files under /run/systemd/generator/cron-*.timer
>> + cron-*.service
>> to have a proper comparaison basis.
>
> Here we go.
>
> timer:
>
> [Unit]
>
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/2457
Bug #818488 [systemd] another IPv6 regression
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/2457'.
> tag -1 fixed-upstream pending
Bug #818488 [systemd] another IPv6 regression
Control: forwarded -1 https://github.com/systemd/systemd/issues/2457
Control: tag -1 fixed-upstream pending
Hello Marc,
Marc Haber [2016-03-17 16:17 +0100]:
> Severity note: I think this is RC. But since 228-2 is already in
> testing, we cannot roll that back. Grave is wrong, because it doesn't
>
Michael Meskes [2016-03-21 11:59 +0100]:
> > This fix is not even list in upstream v230 changelog
> > not really serious.
No wonder, as there is no v230 release yet there also is no NEWS for
it yet :-)
> Anyway, with systemd-cron replacing cron it seems to be paramount to me
> that we get a fixed
2016-03-21 11:59 GMT+01:00 Michael Meskes :
> > > > > It may be only serious, but it definitely is not fit for a
> > > > > release.
> > > > Then systemd 229 is not fit for release.
> > > Indeed you're right imo.
> > This fix is not even list in upstream v230 changelog
> > not really serious.
>
> Th
> > > > It may be only serious, but it definitely is not fit for a
> > > > release.
> > > Then systemd 229 is not fit for release.
> > Indeed you're right imo.
> This fix is not even list in upstream v230 changelog
> not really serious.
This surprised me. Doesn't this bug mean that *all* timers a
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Mar 2016 08:37:02 +0100
Source: python-systemd
Binary: python-systemd python3-systemd
Architecture: source amd64
Version: 231-2~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Debian systemd Ma
> All I can think of is to try to add a low timeo= option (200?), and
> lower retry value (1). The first should cause mount to retry faster if
> the mount fails, and the second should cause it to exit with error
> (hopefully this causes systemd to notice the mount failed).
I tried with the values
On Thu, Mar 17, 2016 at 10:38 AM, Sandro Tosi wrote:
> Hey Felipe,
> thanks for keep looking into this!
>
> On Wed, Mar 16, 2016 at 1:23 PM, Felipe Sateler wrote:
>> On 4 March 2016 at 18:13, Sandro Tosi wrote:
Could you attach one? Or mail me privately if you prefer, and I can
take a
23 matches
Mail list logo
