tags 478821 +help thanks Hi,
I added the statoverride things because IIRC I had problems with the dir
premissions being reset somehow, but I'm not clear on why/how.
(You can tell I'm not that an experienced packager, can't you :-)
So removing the statoverride logic is fine by me, however I'm quite swamped
now and would be very happy for a patch (or NMU since this is apparently
RC.)
cheers
-- vbi
On Thursday 01 May 2008 11.56:47 Marcin Owsiany wrote:
> Package: postgrey
> Version: 1.27-4
> Severity: serious
>
> The following bit is not idempotent:
> | if [ ! -e "$DBDIR" ]; then
> | mkdir -p "$DBDIR"
> | dpkg-statoverride --update --add \
> | postgrey postgrey 0700 "$DBDIR"
> | fi
>
> This will not do the right thing if for any reason dpkg-statoverride
> fails to run on the first try. It also happens to make it hard to have
> $DBDIR bind-mounted from somewhere else.
>
> Please break this block into two parts, one to check directory exinstance
> and creation, and another to fix and register permissions. Actualy, why
> do you need the dpkg-statoverride call anyway? The directory does not
> seem to be included in the package.. Maybe just "install -d -o -g -m" it?
>
> -- System Information:
> Debian Release: 4.0
> APT prefers stable
> APT policy: (500, 'stable'), (100, 'proposed-updates'), (1,
> 'experimental') Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.18-6b-ovz-686
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
--
Compile with -wIngo.
-- tilladam in kmail's changelog
signature.asc
Description: This is a digitally signed message part.
