Your message dated Thu, 23 Feb 2012 04:02:13 +
with message-id
and subject line Bug#609162: fixed in debian-policy 3.9.3.0
has caused the Debian Bug report #609162,
regarding package names with dots/periods ('.') and crontab files: packagers
beware
to be marked as done.
This mean
gml
+++ b/policy.sgml
@@ -7140,18 +7140,20 @@ Reloading description configuration...done.
-
+
Cron jobs
Packages must not modify the configuration file
/etc/crontab, and they must not modify the files in
- /var/spool/cron/crontabs.
+ /var/spool/cron/crontabs.
+
ease notice that there are some restrictions
to the file permissions of the files under /etc/cron.d (from cron's manpage:
"must be owned by root, and must not be group- or other-writable.").
Maybe those restrictions should be included there too?
> >>
> >> and a
kage (with a file name as specified in section
> >> 9.5.1)
This should presumably say "should install a file in /etc/cron.d (with
a file name...".
> >> and a new section:
> >>
> >> 9.5.1 File Names for Cron Jobs
> >>
> >&g
install a file
>> /etc/cron.d/package (with a file name as specified in section
>> 9.5.1)
>>
>> and a new section:
>>
>> 9.5.1 File Names for Cron Jobs
>>
>> File names representing cron jobs should generally be named
>> ac
File names representing cron jobs should generally be named
> according to the package from which it comes.
> If a package supplies multiple crontab files in the same
> directory, the file names should all start with the name of the
> package followed by a hyphen
great-package
> great.package
>
> Maybe we don't have to worry about such an insane case. In any event,
> it's easy to avoid that problem by substituting underscores for dots
> and P for plus signs.
That _would_ be an almost insane case, and I hope that the pack
Processing commands for cont...@bugs.debian.org:
> user debian-pol...@packages.debian.org
Setting user to debian-pol...@packages.debian.org (was jrnie...@gmail.com).
> usertags 609162 + normative discussion
Bug#609162: debian-policy: package names with dots/periods ('.') an
user debian-pol...@packages.debian.org
usertags 609162 + normative discussion
severity 609162 normal
quit
Hi Karl,
Karl E. Jorgensen wrote:
> The debian policy section 9.5 [1] suggests using the package name as a
> file name when creating files in /etc/cron.d, /etc/cron.hourly,
> /etc/cron.daily
Package: debian-policy
Severity: minor
The debian policy section 9.5 [1] suggests using the package name as a
file name when creating files in /etc/cron.d, /etc/cron.hourly,
/etc/cron.daily etc. This works well *unless* the package name
includes a dot ('.'), as this forces the file name to inclu
Philip Hands wrote:
>> Kevin Dalley wrote, referring to Bug#18118:
>> >It would be nice if postgresql upgrade would remove the lines from
>> >/etc/crontab which were added by previous version of postgresql.
>>
>> For a while, it did. Neverthe
> Kevin Dalley wrote, referring to Bug#18118:
> >It would be nice if postgresql upgrade would remove the lines from
> >/etc/crontab which were added by previous version of postgresql.
>
> For a while, it did. Nevertheless, it is a violation of policy to
> modify /etc
Joey Hess wrote:
>Oliver Elphick wrote:
>> For a while, it did. Nevertheless, it is a violation of policy to
>> modify /etc/crontab, which is why I have taken it out.
>
>I think it's allowable to violate policy to if you have to, to clean up past
>po
Oliver Elphick wrote:
> For a while, it did. Nevertheless, it is a violation of policy to
> modify /etc/crontab, which is why I have taken it out.
I think it's allowable to violate policy to if you have to, to clean up past
policy violations. If you do it right, it's as if
Kevin Dalley wrote, referring to Bug#18118:
>It would be nice if postgresql upgrade would remove the lines from
>/etc/crontab which were added by previous version of postgresql.
For a while, it did. Nevertheless, it is a violation of policy to
modify /etc/crontab, which is why I have
> > Try looking at how exim does it---it adds a crontab for the mail user, but
> > does correctly handle the mail user's existing crontab.
> >
> > To install it does this:
> >
> > # Install in crontab for user mail if not there
> >
> > I lookd at how smail currently does it: it uses the crontab command to add a
> > crontab for the mail user. However, it doesn't check to see if the mail user
> > already has a crontab. Seems very broken to me.
>
> Try looking at how exim does it---it adds a c
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Joey Hess) writes:
> I lookd at how smail currently does it: it uses the crontab command to add a
> crontab for the mail user. However, it doesn't check to see if the mail user
> already has a crontab. Seems ver
"Oliver Elphick" writes:
> So if the policy is as stated, it is being violated by the package
> building tools.
That's par for the course with debmake. If you use debmake don't
expect your packages to comply with policy; just the bits Christoph
decides he likes.
--
James
Joey Hess wrote:
>Policy says:
>
> 3.5. Cron jobs
> --
>
> Packages may not touch the configuration file `/etc/crontab', nor may
> they modify the files in `/var/spool/cron/crontabs'.
>
>And it goes on to say, use /etc
Policy says:
3.5. Cron jobs
--
Packages may not touch the configuration file `/etc/crontab', nor may
they modify the files in `/var/spool/cron/crontabs'.
And it goes on to say, use /etc/cron.{daily,weekly,monthly}. However, what
are we supposed to do if
21 matches
Mail list logo
