-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 26 May 2024 20:19:20 +
Source: python-crontab
Architecture: source
Version: 3.1.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Changes:
python-crontab (3.1.0-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Jan 2024 21:05:52 +
Source: python-crontab
Architecture: source
Version: 3.0.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Closes: 1060935
Changes:
python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 17 Nov 2023 17:57:36 +
Source: python-crontab
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Closes: 1054772
Changes:
python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 11 Aug 2023 20:21:50 +
Source: python-crontab
Architecture: source
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Changes:
python-crontab (3.0.0-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 06 Jan 2023 10:44:53 +
Source: python-crontab
Architecture: source
Version: 2.7.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Changes:
python-crontab (2.7.1-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 09 Nov 2022 20:49:39 +
Source: python-crontab
Architecture: source
Version: 2.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Jelmer Vernooij
Changes:
python-crontab (2.6.0-2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 22 Oct 2022 01:01:05 +0100
Source: libconfig-crontab-perl
Architecture: source
Version: 1.45-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: Jelmer Vernooij
Changes:
libconfig-crontab-perl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 11 Jun 2022 23:07:06 +0100
Source: libconfig-crontab-perl
Architecture: source
Version: 1.45-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: Jelmer Vernooij
Changes:
libconfig-crontab-perl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 01 Feb 2022 13:06:16 +
Source: python-crontab
Architecture: source
Version: 2.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Changes:
python-crontab (2.6.0-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 04 Jan 2021 15:18:56 +0100
Source: set-crontab-perl
Architecture: source
Version: 1.03-1.1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke)
Changed-By: Holger Levsen
Changes:
set-crontab-perl (1.03
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 25 Nov 2020 23:39:56 +0100
Source: python-crontab
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Team
Changed-By: Michael Fladischer
Closes: 972821
Changes:
python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 21 Feb 2020 09:05:51 +0100
Source: python-crontab
Architecture: source
Version: 1.9.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Jordan Metzmeier
Changed-By: Håvard Flaget Aasen
Closes: 937670 950207
Changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Jul 2019 01:34:59 +0200
Source: python-crontab
Architecture: source
Version: 1.9.3-3
Distribution: unstable
Urgency: medium
Maintainer: Jordan Metzmeier
Changed-By: Thomas Goirand
Closes: 932507
Changes:
python-crontab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 30 Nov 2018 10:29:09 +0100
Source: set-crontab-perl
Binary: libset-crontab-perl
Architecture: source all
Version: 1.03-1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke)
Changed-By: Stefan Hornburg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 01 Aug 2017 00:16:13 -0400
Source: libconfig-crontab-perl
Binary: libconfig-crontab-perl
Architecture: source
Version: 1.45-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 13 Jan 2017 20:37:14 +0100
Source: libconfig-crontab-perl
Binary: libconfig-crontab-perl
Architecture: source
Version: 1.42-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Sep 2016 22:50:53 +0300
Source: libconfig-crontab-perl
Binary: libconfig-crontab-perl
Architecture: source
Version: 1.41-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 17 Sep 2016 13:31:02 +0300
Source: libconfig-crontab-perl
Binary: libconfig-crontab-perl
Architecture: source
Version: 1.41-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 27 May 2016 13:09:40 +0100
Source: libconfig-crontab-perl
Binary: libconfig-crontab-perl
Architecture: source all
Version: 1.41-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group <pkg-perl-maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 05 Jan 2016 16:20:14 -0600
Source: python-crontab
Binary: python-crontab python3-crontab
Architecture: source
Version: 1.9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Jordan Metzmeier <jmetzmeie...@gmail.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 26 Aug 2015 18:41:01 +0200
Source: set-crontab-perl
Binary: libset-crontab-perl
Architecture: source
Version: 1.02-1.1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) <ra...@linuxia.de>
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 26 May 2015 14:44:11 -0500
Source: python-crontab
Binary: python-crontab python3-crontab
Architecture: source all
Version: 1.9.3-1
Distribution: unstable
Urgency: medium
Maintainer: Jordan Metzmeier jmetzmeie...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 13 Oct 2014 00:09:23 -0500
Source: python-crontab
Binary: python-crontab python3-crontab
Architecture: source all
Version: 1.8.1-2
Distribution: unstable
Urgency: low
Maintainer: Jordan Metzmeier jmetzmeie...@gmail.com
Changed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 05 Mar 2014 00:09:54 -0600
Source: python-crontab
Binary: python-crontab python3-crontab
Architecture: source all
Version: 1.8.1-1
Distribution: unstable
Urgency: low
Maintainer: Jordan Metzmeier jmetzmeie...@gmail.com
Changed
Package: wnpp
Severity: wishlist
Owner: Jordan Metzmeier jmetzmeie...@gmail.com
* Package name: python-crontab
Version : 1.7.2
Upstream Author : Martin Owens docto...@gmail.com
* URL : https://launchpad.net/python-crontab
* License : GPL-3
Programming Lang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 01 Nov 2009 19:24:22 +0100
Source: set-crontab-perl
Binary: libset-crontab-perl
Architecture: source all
Version: 1.02-1
Distribution: unstable
Urgency: low
Maintainer: Stefan Hornburg (Racke) ra...@linuxia.de
Changed-By: Stefan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 13 Mar 2006 09:30:41 +0100
Source: set-crontab-perl
Binary: libset-crontab-perl
Architecture: source all
Version: 1.00-2
Distribution: unstable
Urgency: low
Maintainer: Stefan Hornburg (Racke) [EMAIL PROTECTED]
Changed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 Sep 2005 11:26:51 +0200
Source: set-crontab-perl
Binary: libset-crontab-perl
Architecture: source i386
Version: 1.00-1
Distribution: unstable
Urgency: low
Maintainer: Stefan Hornburg (Racke) [EMAIL PROTECTED]
Changed
On 17-Aug-03, 17:11 (CDT), Steve Greenland [EMAIL PROTECTED] wrote:
I'd hoped to get the suggestions here and Solar Designer's work
incorporated tested, and uploaded before I left on a 2 week vacation,
but I'm not going to get it done. But it *is* in progess, will be my
priority after I
On Mon, Sep 01, 2003 at 07:32:45PM -0500, Steve Greenland wrote:
On 17-Aug-03, 17:11 (CDT), Steve Greenland [EMAIL PROTECTED] wrote:
I'd hoped to get the suggestions here and Solar Designer's work
incorporated tested, and uploaded before I left on a 2 week vacation,
but I'm not going to
* Russell Coker
| Also you don't want the main copy of cron to search auto-mounted user home
| directories. If you do that then a failure of the NFS server will put cron
| in D state...
Which is why you mount NFS shares with the intr flag set so that you
can at least kill it and restart it.
On Mon, 4 Aug 2003 16:10, Tollef Fog Heen wrote:
| Also you don't want the main copy of cron to search auto-mounted user
| home directories. If you do that then a failure of the NFS server will
| put cron in D state...
Which is why you mount NFS shares with the intr flag set so that you
can
On Mon, Aug 04, 2003 at 08:10:47AM +0200, Tollef Fog Heen wrote:
Which is why you mount NFS shares with the intr flag set so that you
can at least kill it and restart it.
Which is broken on most Linux Kernels. So is soft.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) [EMAIL
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
On Sat, Aug 02, 2003 at 02:51:03PM -0500, Steve Greenland wrote:
Under this setup, when cron opens a crontab file, it should fstat() it and
check that it is owned by the uid under which its contents will be executed
before trusting
On Mon, Aug 04, 2003 at 07:55:34PM -0700, Blars Blarson wrote:
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
On Sat, Aug 02, 2003 at 02:51:03PM -0500, Steve Greenland wrote:
Under this setup, when cron opens a crontab file, it should fstat() it and
check that it is owned by the uid
On Sat, Aug 02, 2003 at 09:19:23PM -0400, Matt Zimmerman wrote:
On Sat, Aug 02, 2003 at 02:51:03PM -0500, Steve Greenland wrote:
Apropos of the recent setuid/setgid thread, and also being prodded by
Stephen Frost, I've changed crontab to be setgid 'cron' rather than
setuid 'root'. Beyond
On Sun, Aug 03, 2003 at 12:17:27AM -0400, Daniel Jacobowitz wrote:
On Sat, Aug 02, 2003 at 09:19:23PM -0400, Matt Zimmerman wrote:
Under this setup, when cron opens a crontab file, it should fstat() it
and check that it is owned by the uid under which its contents will be
executed before
On 02-Aug-03, 23:36 (CDT), Matt Zimmerman [EMAIL PROTECTED] wrote:
So: open, fstat, stat, compare fstat.st_ino to stat.st_ino, check
fstat.st_uid. O_EXCL should also be used when writing to the directory.
That introduces a (possibly minor) race condition: if the user runs
crontab to replace
Steve Greenland wrote:
Apropos of the recent setuid/setgid thread, and also being prodded by
Stephen Frost, I've changed crontab to be setgid 'cron' rather than
setuid 'root'. Beyond the coding (which is mostly removing setuid()
calls), this involves the following changes:
add system group
On Sun, 3 Aug 2003 12:37:46 -0400, Joey Hess [EMAIL PROTECTED] said:
(As a user, what I really want is a .crontab file in my home
directory, so I can put it under revision control.)
Umm, as a work around, I have ~/etc/crontab, and at one time
had a cron job that tested the output
* Joey Hess
| (As a user, what I really want is a .crontab file in my home directory,
| so I can put it under revision control.)
have a .crontab in your ~ with a line similar to
@daily crontab $HOME/.crontab
?
(Naturally, you'd have to get that crontab initially installed,
though
On 03-Aug-03, 11:37 (CDT), Joey Hess [EMAIL PROTECTED] wrote:
One possible gotcha is that if crontab(1) does any sanity checks of the
crontab files, cron could expect them to be pre-sanitised, and might
behave badly if an unsanitised file is put into place by a user.
Crontab and cron check
On 03-Aug-03, 11:37 (CDT), Joey Hess [EMAIL PROTECTED] wrote:
(As a user, what I really want is a .crontab file in my home directory,
so I can put it under revision control.)
One potential problem (or issue) I see with this is automounted home
directories. A file that was there while the user
On Mon, 4 Aug 2003 08:25, Steve Greenland wrote:
On 03-Aug-03, 11:37 (CDT), Joey Hess [EMAIL PROTECTED] wrote:
(As a user, what I really want is a .crontab file in my home directory,
so I can put it under revision control.)
One potential problem (or issue) I see with this is automounted
Apropos of the recent setuid/setgid thread, and also being prodded by
Stephen Frost, I've changed crontab to be setgid 'cron' rather than
setuid 'root'. Beyond the coding (which is mostly removing setuid()
calls), this involves the following changes:
add system group 'cron'
change /var/spool
On Sat, Aug 02, 2003 at 02:51:03PM -0500, Steve Greenland wrote:
change /var/spool/cron/crontabs from 755 root.root to 775 root.cron
change crontab files in the spool directory from 600 root.root to 600
userid.cron
It would ne nice, if cron is checking file owner then. So that the file
user1
indicate
to the build daemons this requirement? Or should I just set the group
and mode of /usr/bin/crontab and the directories in the postinst? The
downside is that doing so would seem to override any local requirements
or dpkg-statoverrides that the admin might have set.
I did not find any
On Sat, Aug 02, 2003 at 03:53:00PM -0500, Steve Greenland wrote:
To ship the setgid program, I need to have the group 'cron' on the
build system.
i think this is covered by fakeroot.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) [EMAIL PROTECTED],linux.de,debian.org}
On Sun, 3 Aug 2003 05:51, Steve Greenland wrote:
Apropos of the recent setuid/setgid thread, and also being prodded by
Stephen Frost, I've changed crontab to be setgid 'cron' rather than
setuid 'root'. Beyond the coding (which is mostly removing setuid()
calls), this involves the following
On 02-Aug-03, 16:25 (CDT), Bernd Eckenfels [EMAIL PROTECTED] wrote:
On Sat, Aug 02, 2003 at 03:53:00PM -0500, Steve Greenland wrote:
To ship the setgid program, I need to have the group 'cron' on the
build system.
i think this is covered by fakeroot.
No, 'chgrp cron foo' fails if group
security idea as you then it's a good sign you're doing
the right thing).
I'd be flattered, except it wasn't my idea, I just finally got around to
doing it. :-) But I'll take a look at SD's version.
If a user is listed in /etc/cron.deny then crontab -l does not work for
them, so if you permit
'cron' on the
build system. Not a problem for me, of course, but how do I indicate
to the build daemons this requirement? Or should I just set the group
and mode of /usr/bin/crontab and the directories in the postinst? The
downside is that doing so would seem to override any local requirements
On Sun, 3 Aug 2003 09:03, Steve Greenland wrote:
It's easy enough to make the directory containing the files be mode 0775
to solve this.
I'll assume you meant 0770? 775 and 771 don't solve the problem, and I
don't see the point of 774 over 770...
Yes, I meant to say 0770.
I don't know
On Sat, Aug 02, 2003 at 02:51:03PM -0500, Steve Greenland wrote:
Apropos of the recent setuid/setgid thread, and also being prodded by
Stephen Frost, I've changed crontab to be setgid 'cron' rather than
setuid 'root'. Beyond the coding (which is mostly removing setuid()
calls), this involves
On Sat, Aug 02, 2003 at 11:25:47PM +0200, Bernd Eckenfels wrote:
On Sat, Aug 02, 2003 at 03:53:00PM -0500, Steve Greenland wrote:
To ship the setgid program, I need to have the group 'cron' on the
build system.
i think this is covered by fakeroot.
It is not, though doogie and asuffield
On 07-Dec-1997 01:39:39, Miquel van Smoorenburg [EMAIL PROTECTED] wrote:
[Re: crontab -l outputs extra header]
Especially since that line is usually used in the prerm script, so
an upgrade won't help.. It might be worth it to locate all the packages
that do this, and file a bug report against
In article [EMAIL PROTECTED],
Steve Greenland [EMAIL PROTECTED] wrote:
On 05-Dec-1997 10:32:37, Philip Hands [EMAIL PROTECTED] wrote:
The fact that the three lines added here ever get seen in the output of
crontab -l
is a bug IMO:
Actually, I got a better understanding of why and where
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Miquel van Smoorenburg) writes:
that do this, and file a bug report against them. You should mention that
tail +4 is dangerous since the behaviour of crontab -l might change , and
recommend something like:
crontab -l | sed -e
On 05-Dec-1997 10:32:37, Philip Hands [EMAIL PROTECTED] wrote:
The fact that the three lines added here ever get seen in the output of
crontab -l
is a bug IMO:
Actually, I got a better understanding of why and where that header
was being added, and I was going to make crontab -l
Brian C. White:
Could you write them to STDERR and the rest of the info to STDOUT?
An option to suppress them might be better.
I thought about this, but it requries my script to know about the
internals of crontab. If crontab ever changed, then a problem could
arise. I prefer to keep
Package: cron
Version: 3.0pl1-34
Running crontab -l has a bad habit of displaying header information
that is not actually part of the crontab.
For example:
$ crontab -l -u gnats
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Mon Jul 29 14:07:28 1996)
# (Cron version
Brian C. White wrote:
Package: cron
Version: 3.0pl1-34
Running crontab -l has a bad habit of displaying header information
that is not actually part of the crontab.
For example:
$ crontab -l -u gnats
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Mon Jul
Steve Greenland wrote:
Would you mind stripping these first three lines from the crontab -l
output?
Yes, because I think there is useful information there (primarily
the second line, with the file name (usually) and date).
Could you write them to STDERR and the rest of the info to STDOUT
63 matches
Mail list logo
