Bug#661472: typo in lib/exabgp/debug.py prevents exabgp to stop properly
Package: exabgp Version: 2.0.1-1 Severity: important When issuing a stop or restart of exabgp daemon (through initscript) a backtrace is displayed (this may be related to the default logging configuration). Traceback (most recent call last): File /usr/share/exabgp/exabgp/debug.py, line 57, in intercept bug_report(type, value, trace) File /usr/share/exabgp/exabgp/debug.py, line 17, in bug_report from proxy.log import Logger ImportError: No module named proxy.log Looks like this wrong import has been fixed upstream under commit id f177be2be4b1 and description 'fix a search and replace gone wrong'. http://code.google.com/p/exabgp/source/diff?spec=svnf177be2be4b1224a00fd4cb5fe8cee648c4478d8r=f177be2be4b1224a00fd4cb5fe8cee648c4478d8format=sidepath=/lib/exabgp/debug.py Upstream version tagged 2.0.2 doesn't contain the referenced bug. After mercurial checkout and building of a debian package version 2.0.2-1 with the upstream provided debian/control file the daemon start/stop/restart properly -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages exabgp depends on: ii adduser 3.112+nmu2 add and remove users and groups ii python2.7.2-10 interactive high-level object-orie exabgp recommends no packages. exabgp suggests no packages. -- Configuration Files: /etc/default/exabgp changed [not included] /etc/exabgp/exabgp.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656436: rdiff-backup: harmless option typo in bash-completion file
Package: rdiff-backup
Version: 1.2.8-6+b1
Severity: minor
Tags: patch
There is a minor error in the provided bash-completion file within the
rdiff-backup package
remote-schema is given instead of a simple --remote-schema
A straightforward patch is attached to this mail, I'm nearly ashamed to
post such a minor bug report
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rdiff-backup depends on:
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii librsync1 0.9.7-7rsync remote-delta algorithm libra
ii python2.7.2-9interactive high-level object-orie
ii python-support1.0.14 automated rebuilding support for P
Versions of packages rdiff-backup recommends:
ii python-pylibacl 0.5.0-3+b1 module for manipulating POSIX.1e A
ii python-pyxattr0.5.0-3+b1 module for manipulating filesystem
rdiff-backup suggests no packages.
-- no debconf information
--- bash-completion.orig2012-01-19 12:10:49.0 +0100
+++ bash-completion 2012-01-19 12:11:15.0 +0100
@@ -38,7 +38,7 @@
|--no-compression-regexp|-r|--restore-as-of|--remote-schema|
|--remove-older-than|--verify-at-time
- # Availible long options
+ # Available long options
longopts=--backup-mode --calculate-average --carbonfile
--check-destination-dir \
--compare --compare-at-time --compare-full
--compare-full-at-time \
--compare-hash --compare-hash-at-time --create-full-path
--current-time \
@@ -53,12 +53,12 @@
--no-carbonfile --no-compare-inode --no-compression
--no-compression-regexp --no-eas \
--no-file-statistics --no-hard-links --null-separator
--parsable-output \
--override-chars-to-quote --preserve-numerical-ids
--print-statistics --restore-as-of \
- remote-schema --remote-tempdir --remove-older-than
--restrict \
+ --remote-schema --remote-tempdir --remove-older-than --restrict
\
--restrict-read-only --restrict-update-only
--ssh-no-compression --tempdir \
--terminal-verbosity --test-server --user-mapping-file
--verbosity --verify \
--verify-at-time --version
- # Availible short options
+ # Available short options
shortopts=-b -l -r -v -V
options=${longopts} ${shortopts}
Bug#616579: [Pkg-haskell-maintainers] Bug#616579: libghc6-filestore-data: problems handling large files in runShellCommand function
* Joachim Breitner - 06-03-2011 à 11h54: Dear Remi, Am Samstag, den 05.03.2011, 19:30 +0100 schrieb Rémi Laurent: Would it be possible to package this new version of filestore and rebuild the other haskell packages relying on it ? An abstract of the related upstrem changelog Version 0.3.4.3 released 26 Sep 2010 * runShellCommand: reverted to older version with temp files. The new version caused lazy-IO related problems with large files. Thanks to Pavel Perikov diagnosing the problem. thanks for the bug report. As we are currently working on the ghc7 transition, we have to decide whether we want to upload this version right away, or wait until we have to touch it anyways when doing the transition. Would it help you to get a fix soon or do you not mind if the package is broken in unstable for a little longer. Hi and thanks for the quick answer. At the moment I'm happy using a custom rebuild of the package (and the gitit application), so for my specific case, no need to quickly fix this. I let you and your team decide which solution fits best. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: Digital signature
Bug#616579: libghc6-filestore-data: problems handling large files in runShellCommand function
Package: libghc6-filestore-data Version: 0.3.4.2-1 Severity: important As reported by the author of this Haskell package, looks like there are some errors when handling large files. This is particularly annoying for applications such as gitit (a wiki web engine), in which fetching any file that is bigger than 64kB will result in the application hanging. The problem has been solved in a new upstream release tagged version 0.3.4.3 available at http://hackage.haskell.org/package/filestore-0.3.4.3 . I've tried to rebuild the gitit package with this new version of filestore and the big file issue looks like fixed. This 0.3.4.3 version only fix this runShellCommand function and do not change anything else (which is not the case of the 0.4.x versions which include some API changes). Would it be possible to package this new version of filestore and rebuild the other haskell packages relying on it ? An abstract of the related upstrem changelog Version 0.3.4.3 released 26 Sep 2010 * runShellCommand: reverted to older version with temp files. The new version caused lazy-IO related problems with large files. Thanks to Pavel Perikov diagnosing the problem. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#572232: apache2.2-common: bash_completion script sed substition bug on file containing load or conf word
Package: apache2.2-common
Version: 2.2.9-10+lenny4
Severity: normal
Tags: patch
In the a2ensite helper for bash_completion, there is an unfortunate
substition expression that rips part of the completed filename when it
contains the 'load' or 'conf' string.
example with configuration files like
/etc/apache2/sites-available/testconf
/etc/apache2/sites-available/www.loaded.com
/etc/apache2/sites-available/www.reload.com
/etc/apache2/sites-available/www.reloaded.com
this would auto-complete with
$ a2ensite TAB
tes wwwed.comwww.r.comwww.red.com
with the proposed patch applied, we get
$ a2ensite TAB
testconf www.loaded.comwww.reload.com www.reloaded.com
--- /tmp/bash_completion.d/apache2.2-common.orig2010-03-02
15:18:05.0 +0100
+++ /etc/bash_completion.d/apache2.2-common 2010-03-02 15:18:40.0
+0100
@@ -4,7 +4,7 @@
_apache2_modsites()
{
COMPREPLY=( $( compgen -W '$( command ls /etc/apache2/$1 2/dev/null \
- | sed -e 's/\.load//' -e 's/\.conf//' )' -- $cur ) )
+ | sed -e 's/.load$//' -e 's/.conf$//' )' -- $cur ) )
}
_a2enmod()
-- Package-specific info:
List of enabled modules from 'apache2 -M':
alias auth_basic authn_file authz_default authz_groupfile
authz_host authz_user autoindex cgi deflate dir env mime
negotiation php5 setenvif status
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apache2.2-common depends on:
ii apache2-utils 2.2.9-10+lenny4 utility programs for webservers
ii libapr11.2.12-5 The Apache Portable Runtime Librar
ii libaprutil11.2.12+dfsg-8 The Apache Portable Runtime Utilit
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libmagic1 4.26-1File type determination library us
ii libssl0.9.80.9.8k-6 SSL shared libraries
ii lsb-base 3.2-20Linux Standard Base 3.2 init scrip
ii mime-support 3.44-1MIME files 'mime.types' 'mailcap
ii net-tools 1.60-22 The NET-3 networking toolkit
ii perl 5.10.0-19 Larry Wall's Practical Extraction
ii procps 1:3.2.7-11/proc file system utilities
ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime
Versions of packages apache2.2-common recommends:
ii ssl-cert 1.0.23 simple debconf wrapper for OpenSSL
Versions of packages apache2.2-common suggests:
pn apache2-doc none (no description available)
pn apache2-suexec | apache2-suex none (no description available)
ii iceweasel [www-browser] 3.5.5-1lightweight web browser based on M
ii midori [www-browser] 0.1.8-1fast, lightweight graphical web br
ii w3m [www-browser] 0.5.2-2+b1 WWW browsable pager with excellent
Versions of packages apache2.2-common is related to:
pn apache2-mpm-eventnone (no description available)
pn apache2-mpm-itk none (no description available)
ii apache2-mpm-prefork 2.2.9-10+lenny4 Apache HTTP Server - traditional n
pn apache2-mpm-worker none (no description available)
-- no debconf information
--
Rémi Laurent
Phone: +352 26 10 30 61
General Support: supp...@conostix.com
Managed Services Support: supp...@lcms.lu
GPG FP: 27F4 6810 2B0E 1AA0 CDAE 7C7B 3DC9 085A 0FA0 0601
signature.asc
Description: Digital signature
Bug#484022: Possible fix for #446793, #484022 and reopened #448524
I believe this patch could resolve issues linked to bugs #446793, #484022 and
#448524 .
Patched init script seems to be able to handle missing or wrong PIDFILE and
also already started/stopped daemon.
I'm not completly confident in the LSB log functions order/usage but the script
behaves well for all the issue found in the three bugs mentionned above.
Patch:
--- thttpd.orig 2009-06-13 01:04:03.0 +0200
+++ thttpd 2009-06-13 01:06:13.0 +0200
@@ -12,57 +12,105 @@
# Description: thttpd is a small, fast secure webserver.
### END INIT INFO
-PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
-DAEMON=/usr/sbin/thttpd
-DESC=web server
-NAME=thttpd
+set -e
+
+DAEMON='/usr/sbin/thttpd'
+DESC='web server'
+NAME=`basename $DAEMON`
-CONFFILE=/etc/thttpd/thttpd.conf
-PIDFILE=/var/run/thttpd.pid
+CONFFILE='/etc/thttpd/thttpd.conf'
+PIDFILE='/var/run/thttpd.pid'
OPTIONS=-C $CONFFILE -i $PIDFILE
-test -x $DAEMON || exit 0
-test -f $CONFFILE || exit 1
+test -x $DAEMON || exit 0
+test -f $CONFFILE || exit 1
-set -e
+. /lib/lsb/init-functions
+
+daemon_present() {
+ PID=$1
+ if [ $PID ]; then
+ start-stop-daemon -K -q -p $PID -x $DAEMON -s 0 -- $OPTIONS
+ else
+ start-stop-daemon -K -q -x $DAEMON -s 0 -- $OPTIONS
+ fi
+}
+
+do_start() {
+ PID_REMOVED=0
+ if [ -f $PIDFILE ]; then
+ if daemon_present $PIDFILE ; then
+ log_progress_msg already running
+ log_end_msg 0
+ return 0
+ fi
+ rm -f $PIDFILE
+ PID_REMOVED=1
+ fi
+ if daemon_present ; then
+ log_progress_msg already running
+ log_end_msg 0
+ else
+ set +e
+ start-stop-daemon -S -q -p $PIDFILE -x $DAEMON -- $OPTIONS
+ set -e
+ log_end_msg $? || true
+ fi
+ [ $PID_REMOVED -eq 1 ] log_warning_msg removed stale PID file
+}
+
+do_stop() {
+ SIGNAL=$1
+ SIGNAL=${SIGNAL:-'USR1'}
+ if [ -f $PIDFILE ]; then
+ if daemon_present $PIDFILE ; then
+ set +e
+ start-stop-daemon -K -q -p $PIDFILE -x $DAEMON
--signal $SIGNAL
+ set -e
+ log_end_msg $? || true
+ rm -f $PIDFILE
+ return 0
+ fi
+ fi
+ if daemon_present; then
+ set +e
+ start-stop-daemon -K -q -x $DAEMON --signal $SIGNAL
+ set -e
+ log_end_msg $? || true
+ else
+ log_progress_msg already stopped
+ log_end_msg 0
+ fi
+ if [ -f $PIDFILE ]; then
+ rm -f $PIDFILE
+ log_warning_msg removed stale PID file
+ fi
+}
case $1 in
start)
- echo -n Starting $DESC:
- start-stop-daemon -S -q -p $PIDFILE -x $DAEMON -- $OPTIONS
- echo $NAME.
+ log_daemon_msg Starting $NAME
+ do_start
;;
stop)
- echo -n Stopping $DESC:
-
- if ps ax | grep $(cat $PIDFILE) | grep -qv grep
- then
- start-stop-daemon -K -q -p $PIDFILE -x $DAEMON --signal
10
- fi
-
- echo $NAME.
+ log_daemon_msg Stopping $NAME
+ do_stop
;;
force-stop)
- echo -n Stopping $DESC:
- start-stop-daemon -K -q -p $PIDFILE -x $DAEMON
- echo $NAME.
+ log_daemon_msg Stopping (forced) $NAME
+ do_stop TERM
;;
force-reload)
- if start-stop-daemon -K -q -p $PIDFILE -x $DAEMON --test
- then
- $0 restart
- fi
+ $0 restart
;;
restart)
- echo -n Restarting $DESC:
- start-stop-daemon -K -q -p $PIDFILE -x $DAEMON --signal 10
+ $0 stop
sleep 1
- start-stop-daemon -S -q -p $PIDFILE -x $DAEMON -- $OPTIONS
- echo $NAME.
+ $0 start
;;
*)
Regards,
--
Rémi Laurent
GPG Key ID/Fingerprint:
1024D/0FA00601 27F4 6810 2B0E 1AA0 CDAE 7C7B 3DC9 085A 0FA0 0601
signature.asc
Description: Digital signature
Bug#528669: init script failing when specter already running or already stopped
Package: specter
Version: 1.4-3
Severity: normal
Tags: patch
Init script returns a non zero status when called to stop / start an
already stopped / started specter daemon.
This has unexcepted behaviour when trying to restart specter or to
uninstall it when daemon is already stopped.
An example output when trying to remove the package and specter daemon
is already stopped:
The following packages will be REMOVED:
specter*
0 upgraded, 0 newly installed, 1 to remove and 42 not upgraded.
After this operation, 401kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 141013 files and directories currently installed.)
Removing specter ...
Stopping Specter Logging Facility: invoke-rc.d: initscript specter,
action stop failed.
dpkg: error processing specter (--purge):
subprocess pre-removal script returned error exit status 1
Starting Specter Logging Facility: Specter.
Errors were encountered while processing:
specter
E: Sub-process /usr/bin/dpkg returned an error code (1)
A possible patch could be:
--- specter.orig2009-05-14 17:21:28.0 +0200
+++ specter 2009-05-14 17:26:54.0 +0200
@@ -1,4 +1,4 @@
-#! /bin/sh
+#! /bin/sh -e
### BEGIN INIT INFO
# Provides: specter
# Required-Start:$remote_fs $syslog
@@ -25,13 +25,23 @@
case $1 in
start)
echo -n Starting $DESC:
- start-stop-daemon --start --quiet --exec $DAEMON -- $DAEMON_OPTS
- echo $NAME.
+ if start-stop-daemon --stop --quiet --signal 0 --exec $DAEMON
+ then
+ echo [already running]
+ else
+ start-stop-daemon --start --quiet --exec $DAEMON -- $DAEMON_OPTS
+ echo $NAME.
+ fi
;;
stop)
echo -n Stopping $DESC:
- start-stop-daemon --stop --quiet --exec $DAEMON
- echo $NAME.
+ if start-stop-daemon --stop --quiet --signal 0 --exec $DAEMON
+ then
+ start-stop-daemon --stop --quiet --exec $DAEMON
+ echo $NAME.
+ else
+ echo [not running]
+ fi
;;
reload)
echo Reloading $DESC configuration files.
@@ -39,15 +49,17 @@
;;
restart|force-reload)
echo -n Restarting $DESC:
- start-stop-daemon --stop --quiet --exec $DAEMON
- sleep 1
+ if start-stop-daemon --stop --quiet --signal 0 --exec $DAEMON
+ then
+ start-stop-daemon --stop --quiet --exec $DAEMON
+ sleep 1
+ fi
start-stop-daemon --start --quiet --exec $DAEMON -- $DAEMON_OPTS
echo $NAME.
;;
*)
N=/etc/init.d/$NAME
echo Usage: $N {start|stop|restart|reload|force-reload} 2
- #echo Usage: $N {start|stop|restart|force-reload} 2
exit 1
;;
esac
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages specter depends on:
ii adduser 3.110 add and remove users and groups
ii iptables 1.4.2-6administration tools for packet fi
ii libc6 2.9-4 GNU C Library: Shared libraries
specter recommends no packages.
Versions of packages specter suggests:
pn specter-mysql none (no description available)
pn specter-pgsql none (no description available)
-- no debconf information
signature.asc
Description: Digital signature
Bug#519291: Overflow with large number of identical monitored processes
Package: restartd
Version: 0.2.2
When using restartd to monitor processes that fork a lot (apache, havp,
...), an incoherent behaviour happens. Typically syslog get filled with
lines of this type:
Mar 11 17:16:56 $HOSTNAME restartd: 19326 19328 19331 19334 19337 19340
19342 19345 19347 19349 19351 19353 19355 19357 19359 19362 19364 19366
19367 19369 19371 19373 19375 19380 19383 19385 19387 19389 19391 19393
19395 19397 19399 19402 19405 19407 19409 19411 19413 19415 19417 19419
19421 19423 19425 19427 19430 19432 19434 19436 19438 19440 19442 is NOT
running, executing ' 19399 19402 19405 19407 19409 19411 19413 19415
19417 19419 19421 19423 19425 19427 19430 19432 19434 19436 19438 19440
19442'
This seems to be related to a buffer overflow in restartd code. Overflow
could be exploited to crash restartd, or, although unlikely, call
arbitrary commands which names are PIDs, and present in restartd $PATH
(maybe code execution but I can't see how given the fact data is only
PIDs).
This can been seen on the line
executing ' 19399 19402 ...
as later, restartd uses this data as argument for a system(3) function call.
Relevant code is located in main.c file, line 246 to 257:
// Check process
for (i = 0; i config_process_number; i++)
{
regcomp (regc, config_process[i].regexp, REG_EXTENDED
|| REG_ICASE);
if (!regexec
(regc, proc_cmdline_str, r_nmatch, r_match, 0))
sprintf (config_process[i].processes, %s %s,
config_process[i].processes,
procdir_dirent-d_name);
regfree (regc);
}
for a large number of running monitored process (which match regular
expression specified in configuration file), PIDs keep being appended to
config_process[i].processes, without any check. 'config_process_type'
struct has its 'processes' member limited to 256 bytes, as defined in
config.h file, line 44 to 54.
It seems this quick ugly fix works with the test setup I used
(4 monitored processes forking 100 times each).
if (snprintf (config_process[i].processes, 256, %s %s,
config_process[i].processes,
procdir_dirent-d_name) = 256 )
{
config_process[i].processes[256-1] = '\0';
}
Sadfully this fix interferes with the /var/run/restartd status file
maintained by restartd as PIDs list gets truncated.
Note another sprintf use without error checking at main.c line 233
This has been tested on Debian GNU/Linux 5.0 (Lenny), kernel
2.6.26-1-686 and libc6 2.7-18 and reported on many other Debian Lenny
systems.
signature.asc
Description: Digital signature
Bug#439689: gnupg: loops endlessly with --refresh-keys and a particular key and keyserver
Subject: gnupg: loops endlessly with --refresh-keys and a particular key and keyserver Package: gnupg Version: 1.4.6-2 Severity: important *** Please type your report below this line *** I reproduced this bug on 3 different Debian (sarge, etch and testing). It seems Ubuntu has the same problem (tested on Dapper and Gutsy). This has been tested on i686 32-bits hardware only and from four different Internet connections (2 in Belgium, one in Germany and one in France by an Ubuntu user). Reproduced with gnupg Debian stable/testing 1.4.6-2 and 1.4.1-1.sarge7 and with Ubuntu Dapper 1.4.2.2-1ubuntu2.5 and Gutsy 1.4.6-2ubuntu3 $ gpg gpg: directory `/home/foobar/.gnupg' created gpg: keyring `/home/foobar/.gnupg/secring.gpg' created gpg: keyring `/home/foobar/.gnupg/pubring.gpg' created # Getting Peter Palfrader key $ gpg --keyserver pgp.surfnet.nl --recv-keys 94C09C7F # Refreshing pub keyring from pgp.mit.edu $ gpg --refresh-keys --keyserver pgp.mit.edu # after a few seconds CPU usage raises to 100% 9344 foobar25 0 6492 3140 1188 R 100 0.3 0:48.35 gpg # after 15 minutes, still the same, no timeout or any other error 9344 foobar25 0 6492 3140 1188 R 100 0.3 15:02.65 gpg # Using ltrace I can observe it is endlessly freeing memory and it seems sequential. free(0x81fdc18) = void free(0x81fddc8) = void free(0x81fdde0) = void free(0x81fdd80) = void free(0x81fdd70) = void free(0x81fdf58) = void free(0x81fdf38) = void free(0x81fdf70) = void free(0x81fdd50) = void free(0x81fdf00) = void free(0x81fdf18) = void free(0x81fdeb8) = void free(0x81fdea8) = void free(0x81fe090) = void free(0x81fe070) = void free(0x81fe0a8) = void free(0x81fde88) = void # Using another keyserver as source doesn't hurt, gpg behaves normally $ gpg --refresh-keys --keyserver pgp.surfnet.nl Hope this will help and sorry for my English. PS: it's been running for 25 minutes the time I finished this mail ;) PPS: apparently this has nothing to do with #72148, connection closes normaly as reported by netstat -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (990, 'stable'), (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Versions of packages gnupg depends on: ii gpgv1.4.6-2 GNU privacy guard - signature veri ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii libldap22.1.30-13.4 OpenLDAP libraries ii libreadline55.2-3GNU readline and history libraries ii libusb-0.1-42:0.1.12-5 userspace USB programming library ii makedev 2.3.1-83 creates device files in /dev ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime gnupg recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
