Processing of python-socksipy_1.02-1_multi.changes

2014-10-13 Thread Debian FTP Masters
python-socksipy_1.02-1_multi.changes uploaded successfully to localhost along with the files: python-socksipy_1.02-1.dsc python-socksipy_1.02.orig.tar.xz python-socksipy_1.02-1.debian.tar.gz python-socksipy_1.02-1_all.deb Greetings, Your Debian queue daemon (running on host

python-socksipy_1.02-1_multi.changes ACCEPTED into unstable

2014-10-13 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 13 Oct 2014 12:26:15 +0100 Source: python-socksipy Binary: python-socksipy Architecture: all source Version: 1.02-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org

Bug#604836: marked as done (python-socksipy: new upstream version 1.02 available)

2014-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Oct 2014 12:19:12 + with message-id e1xdeam-0005oc...@franck.debian.org and subject line Bug#604836: fixed in python-socksipy 1.02-1 has caused the Debian Bug report #604836, regarding python-socksipy: new upstream version 1.02 available to be marked as done. This

Bug#664379: marked as done ([PATCH] python-socksipy: Helping to update to packaging format 3.0)

2014-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Oct 2014 12:19:12 + with message-id e1xdeam-0005oi...@franck.debian.org and subject line Bug#664379: fixed in python-socksipy 1.02-1 has caused the Debian Bug report #664379, regarding [PATCH] python-socksipy: Helping to update to packaging format 3.0 to be marked as

ALERTE : 32 médicaments désormais remboursables

2014-10-13 Thread LES ÉCO
Se désinscrire de la liste: http://link.email.wib.me/u/443/159bf02e855352fd99179b2b17cb050dc1117f11875b2e4b Avenue Abdelmoumen, Rue Calavon n 4, Casablanca, 2, Maroc

Bug#765168: capisuite: cs_helpers.py not registered in python

2014-10-13 Thread Wolfgang Streule
Package: capisuite Version: 0.4.5-12 Severity: important Tags: patch Dear Maintainer, in jessie, the capisuite package is not able to run some of its scripts as cs_helpers is not recognized by the python subsystem (2.6) after the service has been started. Possible fix: create a link to

Processing of libast_0.7-7_amd64.changes

2014-10-13 Thread Debian FTP Masters
libast_0.7-7_amd64.changes uploaded successfully to localhost along with the files: libast_0.7-7.dsc libast_0.7-7.debian.tar.xz libast2_0.7-7_amd64.deb libast2-dev_0.7-7_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email

libast_0.7-7_amd64.changes ACCEPTED into unstable

2014-10-13 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Oct 2014 20:49:15 +0200 Source: libast Binary: libast2 libast2-dev Architecture: source amd64 Version: 0.7-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group packa...@qa.debian.org Changed-By:

Bug#735214: marked as done (libast: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el)

2014-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Oct 2014 19:04:09 + with message-id e1xdkuf-00046i...@franck.debian.org and subject line Bug#735214: fixed in libast 0.7-7 has caused the Debian Bug report #735214, regarding libast: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el to be marked as

Bug#765284: htdig: FTBFS on kfreebsd-*: 'ETIME' undeclared

2014-10-13 Thread Sebastian Ramacher
Source: htdig Version: 1:3.2.0b6-13 Severity: serious Justification: fails to build from source (but built successfully in the past) htdig failed to build on kfreebsd-*: | libtool: compile: x86_64-kfreebsd-gnu-gcc -DHAVE_CONFIG_H -I. -I./../htlib -D_FORTIFY_SOURCE=2 -g -O2

Bug#765231: libwfut: run dh-autoreconf to update for new architectures

2014-10-13 Thread Wookey
Source: libwfut Version: 0.2.1-3 Severity: normal User: debian-...@lists.debian.org Usertag: arm64 This package failed to build on arm64. Here is the buildd log: https://buildd.debian.org/status/fetch.php?pkg=libwfutarch=arm64ver=0.2.1-3stamp=1408643663 The problem appears to be out of date