Package: sup-mail
Version: 0.12.1-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Updating ruby-gpgme to 2.0.0-1 (from the older libgpgme-ruby1.8 1.0.8-3 I had)
causes GPG signing of messages to throw an exception:
* What was the outcome of this action?
Exception thr
5 years since bug initially reported...
I had a look at the code and compared it with some real signed repositories and
it looks to me that:
1) The directory structure should be deeper. It looks like there should be a
real binary-i386 (or whatever) directory
2) The make_release_file() function
I believe this issue can be resolved/worked around in 8.4.3 which
includes a new configuration paramenter ssl_renegotiation_limit
which can be set to 0. See
http://www.postgresql.org/docs/8.4/static/release-8-4-3.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Possibly related to bug # 555829?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555829
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: postgresql-8.4
Version: 8.4.1-1
Severity: grave
Justification: renders package unusable
When ssl is turned on in postgresql.conf, performing a restore using pg_restore
fails with a message like:
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error fr
5 matches
Mail list logo