On 10/12/06, Sam Hocevar (Debian packages) <[EMAIL PROTECTED]> wrote:
Hmm,
Did you actually manage to get to trigger these bugs, or did you find them by code checking?
While I agree these are bugs (and will fix them), I am having a hard time triggering them via upgrade, etc.:
I think the code paths are only followed if handling legacy directories that are no longer present in sarge,
ie. upgrading via an unsupported configuration. If you triggered them In Real Life, i'd like to see the
scenario so I could properly test it.
Regards
Alastair
Package: console-common
Version: 0.7.62
Severity: serious
Justification: Policy 9.1.2
Quoting policy 9.1.2:
Since `/usr/local' can be mounted read-only from a remote server,
these directories must be created and removed by the `postinst' and
`prerm' maintainer scripts and not be included in the `.deb' archive.
These scripts must not fail if either of these operations fail.
postinst is set -e and tries to move files in /usr/local without handling
errors.
Hmm,
Did you actually manage to get to trigger these bugs, or did you find them by code checking?
While I agree these are bugs (and will fix them), I am having a hard time triggering them via upgrade, etc.:
I think the code paths are only followed if handling legacy directories that are no longer present in sarge,
ie. upgrading via an unsupported configuration. If you triggered them In Real Life, i'd like to see the
scenario so I could properly test it.
Regards
Alastair
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.11
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
