-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 27 Feb 2012 07:30:59 +0100
Source: postgresql-9.1
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3
postgresql-9.1 postgresql-9.1-dbg postgresql-client-9.1
postgresql-server-dev-9.1 postgresql-doc-9.1 postgresql-contrib-9.1
postgresql-plperl-9.1 postgresql-plpython-9.1 postgresql-plpython3-9.1
postgresql-pltcl-9.1
Architecture: source amd64 all
Version: 9.1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Pitt <mp...@debian.org>
Changed-By: Martin Pitt <mp...@debian.org>
Description:
libecpg-compat3 - older version of run-time library for ECPG programs
libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
libecpg6 - run-time library for ECPG programs
libpgtypes3 - shared library libpgtypes for PostgreSQL 9.1
libpq-dev - header files for libpq5 (PostgreSQL library)
libpq5 - PostgreSQL C client library
postgresql-9.1 - object-relational SQL database, version 9.1 server
postgresql-9.1-dbg - debug symbols for postgresql-9.1
postgresql-client-9.1 - front-end programs for PostgreSQL 9.1
postgresql-contrib-9.1 - additional facilities for PostgreSQL
postgresql-doc-9.1 - documentation for the PostgreSQL database management
system
postgresql-plperl-9.1 - PL/Perl procedural language for PostgreSQL 9.1
postgresql-plpython-9.1 - PL/Python procedural language for PostgreSQL 9.1
postgresql-plpython3-9.1 - PL/Python 3 procedural language for PostgreSQL 9.1
postgresql-pltcl-9.1 - PL/Tcl procedural language for PostgreSQL 9.1
postgresql-server-dev-9.1 - development files for PostgreSQL 9.1 server-side
programming
Closes: 656129
Changes:
postgresql-9.1 (9.1.3-1) unstable; urgency=medium
.
* Urgency medium due to security fixes.
* New upstream security/bug fix release:
- Require execute permission on the trigger function for "CREATE
TRIGGER".
This missing check could allow another user to execute a trigger
function with forged input data, by installing it on a table he
owns. This is only of significance for trigger functions marked
SECURITY DEFINER, since otherwise trigger functions run as the
table owner anyway. (CVE-2012-0866)
- Remove arbitrary limitation on length of common name in SSL
certificates.
Both libpq and the server truncated the common name extracted from
an SSL certificate at 32 bytes. Normally this would cause nothing
worse than an unexpected verification failure, but there are some
rather-implausible scenarios in which it might allow one
certificate holder to impersonate another. The victim would have to
have a common name exactly 32 bytes long, and the attacker would
have to persuade a trusted CA to issue a certificate in which the
common name has that string as a prefix. Impersonating a server
would also require some additional exploit to redirect client
connections. (CVE-2012-0867)
- Convert newlines to spaces in names written in pg_dump comments.
pg_dump was incautious about sanitizing object names that are
emitted within SQL comments in its output script. A name containing
a newline would at least render the script syntactically incorrect.
Maliciously crafted object names could present a SQL injection risk
when the script is reloaded. (CVE-2012-0868)
- Fix btree index corruption from insertions concurrent with
vacuuming.
An index page split caused by an insertion could sometimes cause a
concurrently-running "VACUUM" to miss removing index entries that
it should remove. After the corresponding table rows are removed,
the dangling index entries would cause errors (such as "could not
read block N in file ...") or worse, silently wrong query results
after unrelated rows are re-inserted at the now-free table
locations. This bug has been present since release 8.2, but occurs
so infrequently that it was not diagnosed until now. If you have
reason to suspect that it has happened in your database, reindexing
the affected index will fix things.
- Fix transient zeroing of shared buffers during WAL replay.
The replay logic would sometimes zero and refill a shared buffer,
so that the contents were transiently invalid. In hot standby mode
this can result in a query that's executing in parallel seeing
garbage data. Various symptoms could result from that, but the most
common one seems to be "invalid memory alloc request size".
- Fix handling of data-modifying WITH subplans in READ COMMITTED
rechecking.
A WITH clause containing "INSERT"/"UPDATE"/"DELETE" would crash if
the parent "UPDATE" or "DELETE" command needed to be re-evaluated
at one or more rows due to concurrent updates in READ COMMITTED
mode.
- Fix corner case in SSI transaction cleanup.
When finishing up a read-write serializable transaction, a crash
could occur if all remaining active serializable transactions are
read-only.
- Fix postmaster to attempt restart after a hot-standby crash.
A logic error caused the postmaster to terminate, rather than
attempt to restart the cluster, if any backend process crashed
while operating in hot standby mode.
- Fix "CLUSTER"/"VACUUM FULL" handling of toast values owned by
recently-updated rows.
This oversight could lead to "duplicate key value violates unique
constraint" errors being reported against the toast table's index
during one of these commands.
- Update per-column permissions, not only per-table permissions, when
changing table owner.
Failure to do this meant that any previously granted column
permissions were still shown as having been granted by the old
owner. This meant that neither the new owner nor a superuser could
revoke the now-untraceable-to-table-owner permissions.
- Support foreign data wrappers and foreign servers in "REASSIGN
OWNED".
This command failed with "unexpected classid" errors if it needed
to change the ownership of any such objects.
- Allow non-existent values for some settings in "ALTER USER/DATABASE
SET".
Allow default_text_search_config, default_tablespace, and
temp_tablespaces to be set to names that are not known. This is
because they might be known in another database where the setting
is intended to be used, or for the tablespace cases because the
tablespace might not be created yet. The same issue was previously
recognized for search_path, and these settings now act like that
one.
- Fix "unsupported node type" error caused by COLLATE in an "INSERT"
expression.
- Avoid crashing when we have problems deleting table files
post-commit.
Dropping a table should lead to deleting the underlying disk files
only after the transaction commits. In event of failure then (for
instance, because of wrong file permissions) the code is supposed
to just emit a warning message and go on, since it's too late to
abort the transaction. This logic got broken as of release 8.4,
causing such situations to result in a PANIC and an unrestartable
database.
- Recover from errors occurring during WAL replay of "DROP
TABLESPACE".
Replay will attempt to remove the tablespace's directories, but
there are various reasons why this might fail (for example,
incorrect ownership or permissions on those directories). Formerly
the replay code would panic, rendering the database unrestartable
without manual intervention. It seems better to log the problem and
continue, since the only consequence of failure to remove the
directories is some wasted disk space.
- Fix race condition in logging AccessExclusiveLocks for hot standby.
Sometimes a lock would be logged as being held by "transaction
zero". This is at least known to produce assertion failures on
slave servers, and might be the cause of more serious problems.
- Track the OID counter correctly during WAL replay, even when it
wraps around.
- Prevent emitting misleading "consistent recovery state reached" log
message at the beginning of crash recovery.
- Fix initial value of pg_stat_replication.replay_location.
- Fix regular expression back-references with - attached.
Rather than enforcing an exact string match, the code would
effectively accept any string that satisfies the pattern
sub-expression referenced by the back-reference symbol.
A similar problem still afflicts back-references that are embedded
in a larger quantified expression, rather than being the immediate
subject of the quantifier. This will be addressed in a future
PostgreSQL release.
- Fix recently-introduced memory leak in processing of inet/cidr
values.
- Fix planner's ability to push down index-expression restrictions
through UNION ALL.
- Fix planning of WITH clauses referenced in "UPDATE"/"DELETE" on an
inherited table.
This bug led to "could not find plan for CTE" failures.
- Fix GIN cost estimation to handle column IN (...) index conditions.
This oversight would usually lead to crashes if such a condition
could be used with a GIN index.
- Fix dangling pointer after "CREATE TABLE AS"/"SELECT INTO" in a
SQL-language function.
In most cases this only led to an assertion failure in
assert-enabled builds, but worse consequences seem possible.
- Fix I/O-conversion-related memory leaks in plpgsql.
- Work around bug in perl's SvPVutf8() function.
This function crashes when handed a typeglob or certain read-only
objects such as $^V. Make plperl avoid passing those to it.
- In pg_dump, don't dump contents of an extension's configuration
tables if the extension itself is not being dumped.
- Improve pg_dump's handling of inherited table columns.
pg_dump mishandled situations where a child column has a different
default expression than its parent column. If the default is
textually identical to the parent's default, but not actually the
same (for instance, because of schema search path differences) it
would not be recognized as different, so that after dump and
restore the child would be allowed to inherit the parent's default.
Child columns that are NOT NULL where their parent is not could
also be restored subtly incorrectly.
- Fix pg_restore's direct-to-database mode for INSERT-style table data.
Direct-to-database restores from archive files made with
"--inserts" or "--column-inserts" options fail when using
pg_restore from a release dated September or December 2011, as a
result of an oversight in a fix for another problem. The archive
file itself is not at fault, and text-mode output is okay.
- Teach pg_upgrade to handle renaming of plpython's shared library.
Upgrading a pre-9.1 database that included plpython would fail
because of this oversight.
- Allow pg_upgrade to process tables containing regclass columns.
Since pg_upgrade now takes care to preserve pg_class OIDs, there
was no longer any reason for this restriction.
- Make libpq ignore ENOTDIR errors when looking for an SSL client
certificate file.
This allows SSL connections to be established, though without a
certificate, even when the user's home directory is set to
something like /dev/null.
- Fix some more field alignment issues in ecpg's SQLDA area.
- Allow AT option in ecpg DEALLOCATE statements.
The infrastructure to support this has been there for awhile, but
through an oversight there was still an error check rejecting the
case.
- Do not use the variable name when defining a varchar structure in
ecpg.
- Fix "contrib/auto_explain"'s JSON output mode to produce valid JSON.
- Fix error in "contrib/intarray"'s int[] & int[] operator.
If the smallest integer the two input arrays have in common is 1,
and there are smaller values in either array, then 1 would be
incorrectly omitted from the result.
- Fix error detection in "contrib/pgcrypto"'s encrypt_iv() and
decrypt_iv().
These functions failed to report certain types of invalid-input
errors, and would instead return random garbage values for
incorrect input.
- Fix one-byte buffer overrun in "contrib/test_parser".
The code would try to read one more byte than it should, which
would crash in corner cases. Since "contrib/test_parser" is only
example code, this is not a security issue in itself, but bad
example code is still bad.
- Use __sync_lock_test_and_set() for spinlocks on ARM, if available.
This function replaces our previous use of the SWPB instruction,
which is deprecated and not available on ARMv6 and later. Reports
suggest that the old code doesn't fail in an obvious way on recent
ARM boards, but simply doesn't interlock concurrent accesses,
leading to bizarre failures in multiprocess operation.
- Use "-fexcess-precision=standard" option when building with gcc
versions that accept it.
This prevents assorted scenarios wherein recent versions of gcc
will produce creative results.
- Allow use of threaded Python on FreeBSD (Chris Rees)
Our configure script previously believed that this combination
wouldn't work; but FreeBSD fixed the problem, so remove that error
check.
* Drop 00git_inet_cidr_unpack.patch, 01-armel-tas.patch: Applied upstream.
* debian/watch: Use ftp for checking, thanks Peter Eisentraut.
(Closes: #656129)
* debian/control: Bump Standards-Version to 3.9.3. No changes necessary.
Checksums-Sha1:
c6c2ee7ad1822760d9f1cb92c5a6b0144e097f6a 3132 postgresql-9.1_9.1.3-1.dsc
1cf3044415df807c08bb8ad8e40e24e8d375cf34 15582454
postgresql-9.1_9.1.3.orig.tar.bz2
7e25ddbf8b793526762917674d25f41908349be8 29717
postgresql-9.1_9.1.3-1.debian.tar.gz
b8758a82ad4c32c051c41ea2413582e5612362a8 595572 libpq-dev_9.1.3-1_amd64.deb
543430320037c58545d6d064141c4776493373c4 512330 libpq5_9.1.3-1_amd64.deb
86149a945d52f6969955d900f909676c7504895c 459674 libecpg6_9.1.3-1_amd64.deb
b7c625a28aceef4974cf6a9340f5e8479a2282e8 631860 libecpg-dev_9.1.3-1_amd64.deb
8b3fc846cf269b35bd5830f236e3c8e2191fcd69 376832
libecpg-compat3_9.1.3-1_amd64.deb
7c5b085e69e8f19541216acd3a76d3b3dd92cc91 399414 libpgtypes3_9.1.3-1_amd64.deb
1083215eb6e46128c6e65cbb9589be90242c9811 6275724
postgresql-9.1_9.1.3-1_amd64.deb
9b3d97ef953cd893d2945e99257e9658f87364fe 6313662
postgresql-9.1-dbg_9.1.3-1_amd64.deb
f4a495041a34258f3389e0c8a212c7708eaf5793 1962446
postgresql-client-9.1_9.1.3-1_amd64.deb
ec298c0ab3035be9c974e5780a65faafc408404a 1045242
postgresql-server-dev-9.1_9.1.3-1_amd64.deb
38236aa6a587d9fe1a6565d491182635b637fd32 2903648
postgresql-doc-9.1_9.1.3-1_all.deb
6702696829c1f5bf241804f999607b6b4783fba5 825550
postgresql-contrib-9.1_9.1.3-1_amd64.deb
61fc6f4805ad2026a8e732eee95c09b4d7016512 420920
postgresql-plperl-9.1_9.1.3-1_amd64.deb
aa3374b1bf4232915414f32dd1c56709df3a83e7 406646
postgresql-plpython-9.1_9.1.3-1_amd64.deb
a8e64631de3117b38557ed0f3bbf4ceeda8a77cd 406454
postgresql-plpython3-9.1_9.1.3-1_amd64.deb
2b8513068c95d181e50e69fbe54dbe80e90c4608 394066
postgresql-pltcl-9.1_9.1.3-1_amd64.deb
Checksums-Sha256:
3c90f889c1837826803f28aebe94c44cdf9b743d98cef013593eeeeff24a05f1 3132
postgresql-9.1_9.1.3-1.dsc
7a79800a624031c1d9bc9cdce73cb40050100ac50a82050cbf7bbbd16ac4d5d5 15582454
postgresql-9.1_9.1.3.orig.tar.bz2
cb6b5b414e7713536ec15053346a7d774cf3d2d29e3f2b34c7b8f69cbb2d7149 29717
postgresql-9.1_9.1.3-1.debian.tar.gz
5f3589f404416c6ca5a1bf0266e5f1834078640ff72f9d2dce963cecf1ff0742 595572
libpq-dev_9.1.3-1_amd64.deb
1b3b4b8f68ca2be51b7f01ddcb512d9e76cff3bcfd77ea6311384e418dfbd551 512330
libpq5_9.1.3-1_amd64.deb
bb66dca2f0c9071e477d59cf8cd479d7803d814e302e8b22d532023c89a340e6 459674
libecpg6_9.1.3-1_amd64.deb
c2952f6ede6bd44d63e9c9d0e780cb671432afe4ac51c26b71fa95704ff22fc1 631860
libecpg-dev_9.1.3-1_amd64.deb
42fc5a112b55dab60fb2988a5b0615efe574437d254c0a7185c95c7964a70b9d 376832
libecpg-compat3_9.1.3-1_amd64.deb
286b98838016c1529dd576ff71ec4fbcbf518d6df1c7f46c5a355d2a60d0a309 399414
libpgtypes3_9.1.3-1_amd64.deb
8fe7430b344ad6fc3edc9036acf17a63e73d7ad49a14c5d5fd1fea340a6c98cb 6275724
postgresql-9.1_9.1.3-1_amd64.deb
94a6be5831238841e9351a93ffb1a96b13b2f1e7f1a3ffb238e33daa13a4d66d 6313662
postgresql-9.1-dbg_9.1.3-1_amd64.deb
44ad461cc71a7a7d8b2d9b96c96c26885cbd0a9ad81ff8e636d81075bfd73ecf 1962446
postgresql-client-9.1_9.1.3-1_amd64.deb
fd99cc3054eb15eea36fc6d4839280f6f82da66674a19c00aed423ca9d06fd76 1045242
postgresql-server-dev-9.1_9.1.3-1_amd64.deb
942afb866f00e7c321f85091a0becb574aaaae76c29d4d56f68eeb18f7695fdd 2903648
postgresql-doc-9.1_9.1.3-1_all.deb
ee67477a7ce71030550dc5419338c539c7e1b49d0a8987c0dbed40127b2def59 825550
postgresql-contrib-9.1_9.1.3-1_amd64.deb
12d9e2ee8add070f01a0f8d048d3dad2107528c585babf5dc8632eca468be6d7 420920
postgresql-plperl-9.1_9.1.3-1_amd64.deb
f286853d009c6b75742d954e3b236949a3bd8c5bba520d327c410f7c40e7a3b3 406646
postgresql-plpython-9.1_9.1.3-1_amd64.deb
2536bb95cc8df943dea2e8d1918f39622b2284598546ef84079dd856fd3e4d1b 406454
postgresql-plpython3-9.1_9.1.3-1_amd64.deb
9dc89129630a0f43e66e9cf725bef33b35dcb26881e2bf8f0d575143bc790c3f 394066
postgresql-pltcl-9.1_9.1.3-1_amd64.deb
Files:
5108219ee5982bbb5e2ab7141df31361 3132 database optional
postgresql-9.1_9.1.3-1.dsc
641e1915f7ebfdc9f138e4c55b6aec0e 15582454 database optional
postgresql-9.1_9.1.3.orig.tar.bz2
7188a5dab2cfb07583c1c3b4702a1cb4 29717 database optional
postgresql-9.1_9.1.3-1.debian.tar.gz
670f48a68531baac6b2c455ee3745b4f 595572 libdevel optional
libpq-dev_9.1.3-1_amd64.deb
6ed0c6392cc97afc6a59782c1edd2e78 512330 libs optional libpq5_9.1.3-1_amd64.deb
ceb98e902ff71b48bb8b03b4cbb6c123 459674 libs optional
libecpg6_9.1.3-1_amd64.deb
a4a6dd8399dea8fcc97f7329b643bda3 631860 libdevel optional
libecpg-dev_9.1.3-1_amd64.deb
be6f0cd74889d18426bab037a628f16a 376832 libs optional
libecpg-compat3_9.1.3-1_amd64.deb
f6d260bd933b7b2536e49a60fb9691ce 399414 libs optional
libpgtypes3_9.1.3-1_amd64.deb
64d39903b27ac8194b73de023a2626d5 6275724 database optional
postgresql-9.1_9.1.3-1_amd64.deb
fed179a8cb4476bae792cd48f3a27334 6313662 debug extra
postgresql-9.1-dbg_9.1.3-1_amd64.deb
5123f9b2a729a47225ec16a7c6b41d39 1962446 database optional
postgresql-client-9.1_9.1.3-1_amd64.deb
e1e8fb3e187428ea5735db85de3cbecb 1045242 libdevel optional
postgresql-server-dev-9.1_9.1.3-1_amd64.deb
56b48a8d878c3939b59dbff64976c3e1 2903648 doc optional
postgresql-doc-9.1_9.1.3-1_all.deb
e328e97e04755e1844bb088b466e7b25 825550 database optional
postgresql-contrib-9.1_9.1.3-1_amd64.deb
51bb9fe81e346f5ff30860db8c4a0eaa 420920 database optional
postgresql-plperl-9.1_9.1.3-1_amd64.deb
f2da7a7dee807d10af6d7fe4e5e666f8 406646 database optional
postgresql-plpython-9.1_9.1.3-1_amd64.deb
805fcc13914b72819d2f433ec660fece 406454 database optional
postgresql-plpython3-9.1_9.1.3-1_amd64.deb
c776f1ba370d980106e78df473e7c796 394066 database optional
postgresql-pltcl-9.1_9.1.3-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJPSyV3AAoJEPmIJawmtHufcIAP/RaQrq1c71IaNH8ySr6Lbm96
6v1+fyL476I+quoQLnGuw722U/ncwTqxxcP5SH+CVDr1OcGS2UC3nY4TrK+7ldS2
A0hYubjqUP49sWdvTQwiLj3ZSezwPh7vq35iRmwuHFZUUva88WsCKRDIPP8cK4rL
x1Ep0v0IkH+QHzcFa9GizRqMPg9dS290Ykp4GuETf9EOIu9ojp7g3KWoP5TUTTjQ
yS5NecmfHTIZHDKt6FBMkI5vMePZjRwqHWX8VYMvXLjc7qupqzee+aga2nrIqPdO
dsRTcwSwHYLAgLBzHnqPtSyXgzA4RY2WDMA2isads2VHlRpxF1Mjodlemiosxcit
kzUqfwmG4/QhsF+D6buJxW6voNGp24M++EvXuYJoVlfme026XjwEq83XZawsUgHt
GsAJU1eDUo1+LCUmYurhOiVKT89+p3g+vohJDRWyssYucYrJOsM/gGaPlx1d/B+B
DtvqeADgx1w9fern1P3KCaDor6+EP/zgevVHswo8ufbBWjesH9qvgZU0wYEAd3ga
EIXeOCbjWG8gLBjAIF9kb5g3FrzlCnAX17ZYKehVGz8YJAlUdW8/hwr9L5CD287I
Y84ecNvHHXootWRZgoKhYDvptUEIRO0bCsb1kdFJy2gkc2+gtpGFzIMJh/0uGycD
vuEUO77HWwHyrukiMmuY
=RuTz
-----END PGP SIGNATURE-----
Accepted:
libecpg-compat3_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/libecpg-compat3_9.1.3-1_amd64.deb
libecpg-dev_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/libecpg-dev_9.1.3-1_amd64.deb
libecpg6_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/libecpg6_9.1.3-1_amd64.deb
libpgtypes3_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/libpgtypes3_9.1.3-1_amd64.deb
libpq-dev_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/libpq-dev_9.1.3-1_amd64.deb
libpq5_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/libpq5_9.1.3-1_amd64.deb
postgresql-9.1-dbg_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-9.1-dbg_9.1.3-1_amd64.deb
postgresql-9.1_9.1.3-1.debian.tar.gz
to main/p/postgresql-9.1/postgresql-9.1_9.1.3-1.debian.tar.gz
postgresql-9.1_9.1.3-1.dsc
to main/p/postgresql-9.1/postgresql-9.1_9.1.3-1.dsc
postgresql-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-9.1_9.1.3-1_amd64.deb
postgresql-9.1_9.1.3.orig.tar.bz2
to main/p/postgresql-9.1/postgresql-9.1_9.1.3.orig.tar.bz2
postgresql-client-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-client-9.1_9.1.3-1_amd64.deb
postgresql-contrib-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-contrib-9.1_9.1.3-1_amd64.deb
postgresql-doc-9.1_9.1.3-1_all.deb
to main/p/postgresql-9.1/postgresql-doc-9.1_9.1.3-1_all.deb
postgresql-plperl-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-plperl-9.1_9.1.3-1_amd64.deb
postgresql-plpython-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-plpython-9.1_9.1.3-1_amd64.deb
postgresql-plpython3-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-plpython3-9.1_9.1.3-1_amd64.deb
postgresql-pltcl-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-pltcl-9.1_9.1.3-1_amd64.deb
postgresql-server-dev-9.1_9.1.3-1_amd64.deb
to main/p/postgresql-9.1/postgresql-server-dev-9.1_9.1.3-1_amd64.deb
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1s20wz-0000co...@franck.debian.org
