Jens Lody [2011-12-22 7:08 +0100]:
But I still do not understand, why it can not be done this way.
Please see
http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html#sE.1
I thought that this is exactly (one of) the purpose(s) triggers have
been implemented for.
On general file
Am Donnerstag, den 22.12.2011, 10:10 +0100 schrieb Martin Pitt:
Jens Lody [2011-12-22 7:08 +0100]:
But I still do not understand, why it can not be done this way.
Please see
http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html#sE.1
Thanks for clarifying this.
Jens
--
Jens
Hello Martin,
Am Dienstag, den 20.12.2011, 18:14 +0100 schrieb Martin Pitt:
Hello Jens,
Jens Lody [2011-11-21 10:13 +0100]:
diff -Nru postgresql-common-125.orig/debian/postgresql-common.postinst
postgresql-common-125/debian/postgresql-common.postinst
---
Hello Jens,
Jens Lody [2011-11-21 10:13 +0100]:
diff -Nru postgresql-common-125.orig/debian/postgresql-common.postinst
postgresql-common-125/debian/postgresql-common.postinst
--- postgresql-common-125.orig/debian/postgresql-common.postinst
2011-08-08 10:21:40.0 +0200
+++
Hello Jens,
Jens Lody [2011-10-25 15:09 +0200]:
What I meant is to add the su root root-line to the logrotate-conf
file for p-common dynamically in the postinst-script depending on the
version of logrotate.
That's not possible unfortunately as this file is (deliberately) a
dpkg-maintained
Hi Martin,
I did not here anything from you, so I created a patch to make clear
what I meant.
Weitergeleitete Nachricht
Von: Jens Lody deb...@jenslody.de
An: Martin Pitt mp...@debian.org
Kopie: 640...@bugs.debian.org
Betreff: Re: Bug#640493: postgresql-common: logrotate
Am Sonntag, den 25.09.2011, 17:34 +0200 schrieb Martin Pitt:
Hello Martin,
Hello Christoph,
Christoph Berg [2011-09-18 19:37 +0200]:
I think it is necessary, just because a logrotate version was
(un)available at build time doesn't mean that this will be the case at
run time.
Jens Lody [2011-10-25 13:44 +0200]:
Wouldn't it be possible to add the line in the postinst-step ?
No, you can't change dependencies in maintainer scripts. The point is
to stop apt from trying to install it in the first place.
This should work for all versions including the backports.
The
Am Dienstag, den 25.10.2011, 14:53 +0200 schrieb Martin Pitt:
Jens Lody [2011-10-25 13:44 +0200]:
Wouldn't it be possible to add the line in the postinst-step ?
No, you can't change dependencies in maintainer scripts. The point is
to stop apt from trying to install it in the first place.
Hello Christoph,
Christoph Berg [2011-09-18 19:37 +0200]:
I think it is necessary, just because a logrotate version was
(un)available at build time doesn't mean that this will be the case at
run time.
Actually, the problem exists both ways, so unless I forgot some
detail, p-common will
tag 640493 pending
thanks
Hello Paul,
Paul Martin [2011-09-05 10:46 +0100]:
logrotate 3.8.0 (currently in experimental) is more strict on directory
permissions, and produces the following error:
/etc/cron.daily/logrotate:
error: skipping /var/log/postgresql/postgresql-8.4-main.log
Re: Martin Pitt 2011-09-18 20110918111056.gf3...@piware.de
http://bazaar.launchpad.net/~pitti/postgresql/common/revision/1099
Of course it's a bit of a hack, but works with all logrotate versions
and keeps backportability.
Cool idea.
to logrotate, and hope that you will add a Depends:
On Mon, Sep 05, 2011 at 12:45:40PM +0200, Martin Pitt wrote:
su root root
What does logrotate 3.7.1 do if it encounters this? Just a warning, or
does it break?
If it breaks, I'd need to update the packaging to create a logrotate
config on the fly depending on the release you are
Re: Paul Martin 2011-09-06 20110906110426.ga2...@nowster.org.uk
It doesn't break, but root gets the following error emailed from cron.
/etc/cron.daily/logrotate:
error: postgresql-common:10 unknown option 'su' -- ignoring line
error: postgresql-common:10 unexpected text
Hmm. Would it be an
Package: postgresql-common
Version: 121
Severity: minor
Tags: patch
This is a heads-up for the moment, as the update hasn't been uploaded to
unstable yet.
logrotate 3.8.0 (currently in experimental) is more strict on directory
permissions, and produces the following error:
Hello Paul,
Paul Martin [2011-09-05 10:46 +0100]:
To fix this, I'm planning to add a Breaks: postgresql-common (= 121)
to logrotate
That seems fine.
and hope that you will add a Depends: logrotate (= 3.8)
Is there a way to make this work with 3.7.1 as well? I keep p-common
(and the server
16 matches
Mail list logo
