Your message dated Sun, 21 Oct 2007 15:17:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#446635: fixed in postgresql-common 80
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: postgresql-common
Version: 79
Severity: normal
Hi,
When I upgraded to 8.3 (although not via apt; I did dpkg -i of some
packages, and then dpkg -i of the rest when that failed),
postgresql-common threw up a debconf note that 8.3 was an outdated major
version. This probably shouldn't be there :-)
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages postgresql-common depends on:
ii adduser 3.105 add and remove users and groups
ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii postgresql-client-common 79 manager for multiple PostgreSQL cl
ii procps 1:3.2.7-4.1 /proc file system utilities
ii ssl-cert 1.0.14 Simple debconf wrapper for openssl
postgresql-common recommends no packages.
-- debconf information:
* postgresql-common/obsolete-major:
postgresql-common/untransitioned:
--- End Message ---
--- Begin Message ---
Source: postgresql-common
Source-Version: 80
We believe that the bug you reported is fixed in the latest version of
postgresql-common, which is due to be installed in the Debian FTP archive:
postgresql-client-common_80_all.deb
to pool/main/p/postgresql-common/postgresql-client-common_80_all.deb
postgresql-common_80.dsc
to pool/main/p/postgresql-common/postgresql-common_80.dsc
postgresql-common_80.tar.gz
to pool/main/p/postgresql-common/postgresql-common_80.tar.gz
postgresql-common_80_all.deb
to pool/main/p/postgresql-common/postgresql-common_80_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt <[EMAIL PROTECTED]> (supplier of updated postgresql-common package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 21 Oct 2007 16:01:08 +0200
Source: postgresql-common
Binary: postgresql-client-common postgresql-common
Architecture: source all
Version: 80
Distribution: unstable
Urgency: low
Maintainer: Martin Pitt <[EMAIL PROTECTED]>
Changed-By: Martin Pitt <[EMAIL PROTECTED]>
Description:
postgresql-client-common - manager for multiple PostgreSQL client versions
postgresql-common - manager for PostgreSQL database clusters
Closes: 444689 446635
Launchpad-Bugs-Fixed: 90036
Changes:
postgresql-common (80) unstable; urgency=low
.
* pg_upgradecluster: Fix locale error checking.
* pg_upgradecluster: Use cluster_exists() instead of
cluster_data_directory().
* PgCommon.pm: Fix cluster_data_directory() to consider the data_directory
setting in postgresql.conf, which should trump the /pgdata symbolic link.
* debian/init.d-functions: Check for 'postgresql.conf' instead of 'pgdata'
in the test for a valid cluster configuration directory, since 'pgdata' is
optional now.
* pg_createcluster: Do not create pgdata symlinks to the data directory in
/etc any more when configuring a >= 8.0 cluster. Use the data_directory
configuration option instead. (Part of #444689)
* t/020_create_sql_remove.t: Check that clusters still work when replacing
the data_directory setting with a pgdata symbolic link, and that
the data_directory setting trumps the symlink.
* pg_upgradecluster: Set correct data_directory config option after copying
over the old configuration files.
* t/060_obsolete_confparams.t: Restore data_directory setting after
scribbling over the configuration file with our template.
* PgCommon.pm, cluster_info(): Only return a value for 'logfile' when it is
not explicitly configured with log_directory and/or log_filename. The
previous guessing was wrong anyway, since PostgreSQL always appends a
pretty unpredictable timestamp.
* pg_ctlcluster: Only do log file checks and pass pg_ctl -l option when the
log file default is used. Otherwise let PostgreSQL do its logfile handling
and waive log file checks, since we don't know which file is used.
* pg_ctlcluster: Redirect pg_ctl's stdout and stderr to /dev/null, otherwise
it will hang forever when using a custom log file (and thus not passing
-l).
* pg_lsclusters: Print "custom" as log file location if a custom one was set
in postgresql.conf.
* pg_upgradecluster: Enable 'redirect_stderr' in the 7.4 -> 8.x migration of
'syslog' -> 'log_destination', so that the log output is actually
complete.
* t/060_obsolete_confparams.t: Enable 'redirect_stderr' in the template
postgresql.conf's, so that we actually capture log output.
* t/020_create_sql_remove.t: Check proper handling of logs when configuring
log file in postgresql.conf, using the log symlink, or having neither.
* PgCommon.pm, cluster_info(): Return default log file in 'logfile' if
neither postgresql.conf nor a 'log' symlink explicitly specify a log file.
* pg_createcluster: Do not create log symlink if using the default log file
(i. e. when not using -l). (Closes: #444689)
* t/020_create_sql_remove.t: Verify that log symlink is not created by
default.
* architecture.html: Update to current reality.
* debian/postgresql-common.config: Do not consider versions as obsolete if
they are newer than the latest officially supported version. This avoids
confusion when testing new betas in experimental or using backports.
(Closes: #446635)
* t/TestLib.pm: Make exec_as() work with user name 'root' (not just uid 0).
* Add t/130_nonroot_admin.t: Check that administrative pg_ tools work as
non-root, too, if the invoker has sufficient permissions on the
directories (test case for LP #90036).
* pg_{create,drop,upgrade}cluster: Small tweaks to make the scripts work for
non-root users with sufficient write permissions to
/etc/postgresql/<version>, /var/lib/postgresql/<version>, and
/var/log/postgresql. (LP: #90036)
Files:
da770d9e2158f1a2d31373362430ef4c 599 misc optional postgresql-common_80.dsc
a8add9a1c8fd182f8c2dc2eacc2551d1 100065 misc optional
postgresql-common_80.tar.gz
840dabf1d3a3209e9ca651e48fc5dfbc 80390 misc optional
postgresql-common_80_all.deb
db6aabbddf9f4799046ca624848a3f17 43244 misc optional
postgresql-client-common_80_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHG2qVDecnbV4Fd/IRAr3EAKCgVAMjgGSa1MUc4bpollZsC0SAQACfUJAM
Np5GVqPHuC9Ow50Z1MqbvXE=
=PKcs
-----END PGP SIGNATURE-----
--- End Message ---
