Your message dated Mon, 31 Mar 2008 11:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#473405: fixed in postgresql-common 87
has caused the Debian Bug report #473405,
regarding postgresl-common: [INTL:es] Updated spanish po-debconf translation
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
473405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473405
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: postgresql-common
Version: 86
Priority: wishlist
Tags: l10n patch
Please find attached and updat of the po-debconf translation of this package
into Spanish.
Thanks for including it in your next package upload,
Javier
# postgresql-common po-debconf translation to spanish
# Copyright (C) 2006 Software in the Public Interest, SPI Inc.
# This file is distributed under the same license as the postgresql-common
# package.
#
# Changes:
# - Initial translation
# Javier Fernández-Sanguino , 2006
# - Updated
# Javier Fernández-Sanguino , 2007-2008
#
#
# Traductores, si no conoce el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Si tiene dudas o consultas sobre esta traducción consulte con el último
# traductor (campo Last-Translator) y ponga en copia a la lista de
# traducción de Debian al español (<[EMAIL PROTECTED]>)
#
msgid ""
msgstr ""
"Project-Id-Version: postgresql-common 68\n"
"Report-Msgid-Bugs-To: Source: [EMAIL PROTECTED]"
"POT-Creation-Date: 2008-02-03 13:01+0100\n"
"PO-Revision-Date: 2008-03-30 15:44+0200\n"
"Last-Translator: Javier Fernández-Sanguino <[EMAIL PROTECTED]>\n"
"Language-Team: Debian Spanish <[EMAIL PROTECTED]>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-15\n"
"Content-Transfer-Encoding: 8bit\n"
"X-POFile-SpellExtra: PostgreSQL oldversion clúster stop pgdropcluster\n"
"X-POFile-SpellExtra: client old main clústers pgupgradecluster latest\n"
"X-POFile-SpellExtra: postgresql\n"
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid "Obsolete major version ${old}"
msgstr "Versión principal ${old} obsoleta"
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid ""
"The PostgreSQL version ${old} is obsolete, but the server or client packages "
"are still installed. Please install the latest packages (postgresql-"
"${latest} and postgresql-client-${latest}) and upgrade the existing "
"${oldversion} clusters with pg_upgradecluster (see manpage)."
msgstr ""
"La versión de PostgreSQL ${old} está obsoleta, pero el paquete del cliente o "
"del servidor aún están instalados. Debe instalar las últimas versiones de "
"los paquetes (postgresql-${latest} y postgresql-client-${latest}) y "
"actualizar sus clústers ${oldversion} con la orden "
"«pg_upgradecluster» (consulte la página del manual)."
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid ""
"Please be aware that the installation of postgresql-${latest} will "
"automatically create a default cluster ${latest}/main. If you want to "
"upgrade the ${old}/main cluster, you need to remove the already existing "
"${latest} cluster (pg_dropcluster --stop ${latest} main, see manpage for "
"details)."
msgstr ""
"Tenga en cuenta que la instalación de postgresql-${latest} creará "
"automáticamente un clúster por omisión ${latest}/main. Tiene que borrar el "
"clúster ${latest} existente («pg_dropcluster --stop ${latest}) si desea "
"actualizar el clúster ${old}/main, consulte la página de manual para conocer "
"los detalles."
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid ""
"The old server and client packages are no longer supported. After the "
"existing clusters are upgraded, the postgresql-${old} and postgresql-client-"
"${old} packages should be removed."
msgstr ""
"Ya no se da soporte a los paquetes antiguos de cliente y servidor. Debería "
"eliminar los paquetes postgresql-${old} y postgresql-client-${old} después "
"de actualizar los clústers que tenga."
#. Type: error
#. Description
#: ../postgresql-common.templates:2001
msgid ""
"Please see /usr/share/doc/postgresql-common/README.Debian.gz for details."
msgstr "Para más información consulte
«/usr/share/doc/postgresql-common/README.Debian.gz»."
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: postgresql-common
Source-Version: 87
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_87_all.deb
to pool/main/p/postgresql-common/postgresql-client-common_87_all.deb
postgresql-common_87.dsc
to pool/main/p/postgresql-common/postgresql-common_87.dsc
postgresql-common_87.tar.gz
to pool/main/p/postgresql-common/postgresql-common_87.tar.gz
postgresql-common_87_all.deb
to pool/main/p/postgresql-common/postgresql-common_87_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: Mon, 31 Mar 2008 11:32:39 +0200
Source: postgresql-common
Binary: postgresql-common postgresql-client-common
Architecture: source all
Version: 87
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <[EMAIL PROTECTED]>
Changed-By: Martin Pitt <[EMAIL PROTECTED]>
Description:
postgresql-client-common - manager for multiple PostgreSQL client versions
postgresql-common - PostgreSQL database-cluster manager
Closes: 472930 473405
Changes:
postgresql-common (87) unstable; urgency=medium
.
* Urgency medium since #472930 is an important bug fix.
* debian/init.d-functions: If there are no clusters, exit with 4 (LSB-code
for "unknown status") instead of 0 (which means "service is running", but
it is debatable and confusing whether all clusters are running if there
are none at all). (LP: #203966)
* Update Spanish debconf translations, thanks Javier Fernández-Sanguino
Peña. (Closes: #473405)
* t/060_obsolete_confparams.t: Run upgrades under
default_transaction_read_only=on. t/040_upgrade.t still uses the default
"off", so both cases get tested. This replicates the problem report from
Karsten Hilbert.
* pg_upgradecluster: Work with default_transaction_read_only=on.
* debian/autovacuum.conf, architecture.html: Point out that this file is
only relevant for PostgreSQL versions earlier than 8.1. Thanks to Ross
Boylan for pointing this out.
* Add t/051_inconsistent_encoding_upgrade.t: Check that upgrades from
pre-8.3 to 8.3 succeed and have correct encodings if the old DB had a
database whose encoding did not match the server locale. This reproduces
#472930.
* pg_upgradecluster: Fix handling of database encodings on upgrade, since
8.3 now forces DB encodings and server locale to match:
- With C locale, keep encoding of DBs on upgrade, just as in previous
versions. (C is compatible with all encodings, and causes lots of string
functions not to work correctly, but people still use it deliberately.)
- With other locales, create the target DB manually with a compatible
encoding, and call pg_restore in a way to not create the target DB and
automatically convert encoding.
- Closes: #472930, LP: #207779
Files:
bea6888ba8e5963033a702d6604f4a81 599 misc optional postgresql-common_87.dsc
b0fddfcd7b126f20c6aeb8624cffbbaa 106527 misc optional
postgresql-common_87.tar.gz
116bd096f07d3b20c5cddcf85fbd7232 107128 misc optional
postgresql-common_87_all.deb
77a0a75fee34d3bc76c754b83f152866 44904 misc optional
postgresql-client-common_87_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH8MqtDecnbV4Fd/IRAjL4AKCuG38rU7uwnzbQyvMmPVv/XMJiDQCdGxll
T4WPfYH8lCWMdb2+z88BV70=
=sse5
-----END PGP SIGNATURE-----
--- End Message ---
