Bug#993574: python3-virtualsmartcard: Cannot import virtualsmartcard module
Hi Guinness, It is indeed an error in the rules file. If you already have the patch ready, your can upload a NMU release if you wish. If not, I can handle it during the current week. Keep me informed of what you prefer :-) Best regards, signature.asc Description: PGP signature
Bug#963500: ITP: smartleia -- A Python toolkit for LEIA board control
Package: wnpp Severity: wishlist Owner: phi...@debian.org * Package name: smartleia Version : 0.2.1 Upstream Author : D. El-Baze, R. Benadjila, M. Renard, P. Trebuchet, P. Thierry * URL : https://github.com/cw-leia/smartleia * License : LGPL2+ Programming Lang: Python Section : libs Description : A complete toolkit to interact with Leia board virtual smartcard driver Allows to use PCSC and OpenSC tools to communicate with Leia-connected Smartcards thanks, -- Philippe THIERRY signature.asc Description: PGP signature
Bug#962948: ITP: vsmartcard -- A virtual smartcard toolkit
Package: wnpp Severity: wishlist Owner: phi...@debian.org * Package name: vsmartcard Version : 3.3 Upstream Author : Frank Morgner * URL : https://frankmorgner.github.io/vsmartcard/ * License : GPL3+ Programming Lang: C Section : utils Description : A complete toolkit for virtual smartcards emulation and interaction thanks, -- Philippe THIERRY signature.asc Description: PGP signature
Bug#920998: ITP: python-intelhex -- python module for manipulating Intel Hex format
close 920998 thanks already packaged by someone else.
Bug#902812: wcc FTBFS
Hi Raphael, Le 18/07/2018 à 20:38, Raphael Hertzog a écrit : > Control: severity -1 important > Control: tag -1 + unreproducible > > Philippe, if you don't put Sylvestre and Axel in copy, they won't get > your mail sent only to 902...@bugs.debian.org. Sorry for that ! I've seen that when I sent it... :-| I sent the nessage again to them (but without the bug mail in copy to avoid duplication... maybe I should have). Cheers, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: F889 D7F7 85CA E380 DBDA D796 99C5 4C59 C22D 06D4 signature.asc Description: OpenPGP digital signature
Bug#902812: wcc FTBFS
Le 18/07/2018 à 11:46, Sylvestre Ledru a écrit : > On 18/07/2018 10:57, Axel Beckert wrote: >> Control: severity -1 serious >> Control: retitle -1 wcc: FTBFS, hence failed BinNMU and now uninstallable >> after binutils transition >> >> Hi Sylvestre, >> >> Sylvestre Ledru wrote on 1st of July 2018: >>> Package: wcc >>> Severity: important >> [...] >>> Looks like wcc fails to build from source: >>> >>> Hi Sylvestre, I take a look at the bug you reported and I didn't managed to reproduce it. I've rebuilt wcc in a newly updated sid pbuilder env and the package was built correctly. I took a look on the missing header you reported (diagnostics.h). This header is a part of the binutils-dev package in sid, which is in the build depends of the package. Does the build fail on a buildd host ? Can you confirm it is still failing ? I attach the package buildinfo to this mail in order to compare if needed. Cheers, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: F889 D7F7 85CA E380 DBDA D796 99C5 4C59 C22D 06D4 Format: 1.0 Source: wcc Binary: wcc Architecture: amd64 source Version: 0.0.2+dfsg-3 Checksums-Md5: 09b0e65a612aad5e458c725f2ce6c08c 1234 wcc_0.0.2+dfsg-3.dsc bbd03ddeeff91812eb3bfdfb44aee5cb 460172 wcc-dbgsym_0.0.2+dfsg-3_amd64.deb 179aacb1291d6a23ceed8de7546e12c6 156200 wcc_0.0.2+dfsg-3_amd64.deb Checksums-Sha1: df2d1de2604e8ce9a446bf6672ffae8805ab6e40 1234 wcc_0.0.2+dfsg-3.dsc 32877cf14c5f95c6702089f91696775b94c25ff6 460172 wcc-dbgsym_0.0.2+dfsg-3_amd64.deb d256b96f695a95eac83e0580a51496c1f1829f86 156200 wcc_0.0.2+dfsg-3_amd64.deb Checksums-Sha256: 20562cad642a31f53a18ab0abc583ac5f1055c5ee759d5e243480f82a00d7733 1234 wcc_0.0.2+dfsg-3.dsc 14a26d981d62ff7152523f620bafa8378539e8c7c3b8935511f223c3a6cf9810 460172 wcc-dbgsym_0.0.2+dfsg-3_amd64.deb e21d0ba0bdf7dd47bd8567f4980cdb78fbb92983621e7f41a0b2b41703009aa8 156200 wcc_0.0.2+dfsg-3_amd64.deb Build-Origin: Debian Build-Architecture: amd64 Build-Date: Wed, 18 Jul 2018 15:53:58 + Build-Path: /build/wcc-0.0.2+dfsg Installed-Build-Depends: autoconf (= 2.69-11), automake (= 1:1.15.1-3.1), autopoint (= 0.19.8.1-6), autotools-dev (= 20180224.1), base-files (= 10.1), base-passwd (= 3.5.45), bash (= 4.4.18-3.1), binutils (= 2.31-1), binutils-common (= 2.31-1), binutils-dev (= 2.31-1), binutils-x86-64-linux-gnu (= 2.31-1), bsdmainutils (= 11.1.2+b1), bsdutils (= 1:2.32-0.1), build-essential (= 12.5), bzip2 (= 1.0.6-8.1), clang (= 1:6.0-41), clang-6.0 (= 1:6.0.1-2), coreutils (= 8.28-1), cpp (= 4:7.3.0-3), cpp-6 (= 6.4.0-18), cpp-7 (= 7.3.0-26), dash (= 0.5.8-2.10), debconf (= 1.5.67), debhelper (= 11.3.5), debianutils (= 4.8.6), dh-autoreconf (= 19), dh-strip-nondeterminism (= 0.042-1), diffutils (= 1:3.6-1), dpkg (= 1.19.0.5+b1), dpkg-dev (= 1.19.0.5), dwz (= 0.12-2), fdisk (= 2.32-0.1), file (= 1:5.33-3), findutils (= 4.6.0+git+20171230-2), g++ (= 4:7.3.0-3), g++-7 (= 7.3.0-26), gcc (= 4:7.3.0-3), gcc-6 (= 6.4.0-18), gcc-6-base (= 6.4.0-18), gcc-7 (= 7.3.0-26), gcc-7-base (= 7.3.0-26), gcc-8-base (= 8.1.0-11), gettext (= 0.19.8.1-6+b1), gettext-base (= 0.19.8.1-6+b1), grep (= 3.1-2), groff-base (= 1.22.3-10), gzip (= 1.6-5+b1), hostname (= 3.20), init-system-helpers (= 1.51), intltool-debian (= 0.35.0+20060710.4), lib32gcc1 (= 1:8.1.0-11), lib32stdc++6 (= 8.1.0-11), libacl1 (= 2.2.52-3+b1), libarchive-zip-perl (= 1.60-1), libasan3 (= 6.4.0-18), libasan4 (= 7.3.0-26), libatomic1 (= 8.1.0-11), libattr1 (= 1:2.4.47-2+b2), libaudit-common (= 1:2.8.3-1), libaudit1 (= 1:2.8.3-1+b1), libbinutils (= 2.31-1), libblkid1 (= 2.32-0.1), libbsd0 (= 0.9.1-1), libbz2-1.0 (= 1.0.6-8.1), libc-bin (= 2.27-5), libc-dev-bin (= 2.27-5), libc6 (= 2.27-5), libc6-dev (= 2.27-5), libc6-i386 (= 2.27-5), libcap-ng0 (= 0.7.9-1), libcapstone-dev (= 3.0.4-5), libcapstone3 (= 3.0.4-5), libcc1-0 (= 8.1.0-11), libcilkrts5 (= 7.3.0-26), libclang-common-6.0-dev (= 1:6.0.1-2), libclang1-6.0 (= 1:6.0.1-2), libcroco3 (= 0.6.12-2), libdb5.3 (= 5.3.28-13.1+b1), libdebconfclient0 (= 0.243), libdpkg-perl (= 1.19.0.5), libedit2 (= 3.1-20180525-1), libelf-dev (= 0.170-0.5), libelf1 (= 0.170-0.5), libfdisk1 (= 2.32-0.1), libffi6 (= 3.2.1-8), libfile-stripnondeterminism-perl (= 0.042-1), libfreetype6 (= 2.8.1-2), libgc1c2 (= 1:7.4.2-8.3), libgcc-6-dev (= 6.4.0-18), libgcc-7-dev (= 7.3.0-26), libgcc1 (= 1:8.1.0-11), libgcrypt20 (= 1.8.3-1), libgdbm-compat4 (= 1.14.1-6+b1), libgdbm5 (= 1.14.1-6+b1), libglib2.0-0 (= 2.56.1-2), libgmp10 (= 2:6.1.2+dfsg-3), libgomp1 (= 8.1.0-11), libgpg-error0 (= 1.32-1), libgraphite2-3 (= 1.3.11-2), libgsl-dev (= 2.5+dfsg-4), libgsl23 (= 2.5+dfsg-4), libgslcblas0 (= 2.5+dfsg-4), libharfbuzz0b (= 1.8.3-1), libiberty-dev (= 20180614-1), libicu-le-hb0 (= 1.0.3+git161113-5), libicu60 (= 60.2-6), libisl19 (= 0.19-1), libitm1 (= 8.1.0
Bug#884733: dirb - request for features (patch included)
Package: dirb Version: 2.22+dfsg-2 Severity: wishlist Tags: patch See attached message for more info. Message d'origine De : Mathieu BAEUMLER Envoyé : 13 décembre 2017 10:26:59 GMT+01:00 À : "p...@reseau-libre.net" Objet : dirb - request for features (patch included) Hello, One of the tools I happen to use sometimes on Kali is dirb. In two specific cases, I needed two options from the libcurl: - CURLOPT_PATH_AS_IS : don't squash/merge /../ ./ sequences in the path, useful when there is a directory traversal vulnerability - CURLOPT_SSLCERT : use a client certificate I implemented the needed changes, with the resulting two quilt patches (path-as-is.patch to be applied before client_cert.patch). Could you include them in the debian/kali package? Regards, -- Mathieu Baeumler -- O Philippe Thierry. /Y\/ GPG: 7010 9a3c e210 763e 6341 4581 c257 b91b cdaf c1ea o#o client_cert.patch Description: Binary data path-as-is.patch Description: Binary data series Description: Binary data
Bug#880264: RFS: kconfig-frontends/4.11.0.1-1 [ITP] -- Standalone implementation of the Linux Kconfig parser and frontends
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "kconfig-frontends" * Package name : kconfig-frontends Version : 4.11.0.1-1 Upstream Author : Yann Morin * URL : http://ymorin.is-a-geek.org/projects/kconfig-frontends * License : GPL-2+ Programming Lang: C Section : devel Description : Standalone implementation of the Linux Kconfig parser and frontends It builds those binary packages: kconfig-greontds: Kconfig-frontends provides the kconfig parser, as well as all the frontends (dialog, ncurses, Qt and Gtk based) to configure and generate config files and config headers for various projects. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kconfig-frontends Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kconfig-frontends/kconfig-frontends_4.11.0.1-1.dsc This project aims to give an out of Linux tree support for Kconfig files, in order to use the same syntax and mechanisms for emedded (or any other) project configuration. This permits to highly simplify the configuration part and to help in the integration of the configuration as much in the project's production system as in the project's code itself (through autoconf.h support). Regards, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: F889 D7F7 85CA E380 DBDA D796 99C5 4C59 C22D 06D4 signature.asc Description: OpenPGP digital signature
Bug#880132: ITP: kconfig-frontends -- Standalone implementation of the Linux Kconfig parser and frontend
Package: wnpp Severity: wishlist Owner: p...@reseau-libre.net * Package name : kconfig-frontends Version : 4.11.0.1 Upstream Author : Yann Morin * URL : http://ymorin.is-a-geek.org/projects/kconfig-frontends * License : GPL2+ Programming Lang: C Section : devel Description : Standalone implementation of the Linux Kconfig parser and frontend thanks, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: F889 D7F7 85CA E380 DBDA D796 99C5 4C59 C22D 06D4 signature.asc Description: OpenPGP digital signature
Bug#878258: OVAL title field improvement
Package: security.debian.org The current Debian OVAL files title field contains the reference id, making it redundant with the reference ref_id field. As a consequence, the resulting report doesn't show the affected software. is it possible to show the software name in the title field, as CIS does in its OVALRepo for the DSA ? Thanks, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: 7010 9A3C E210 763E 6341 4581 C257 B91B CDAF C1EA
Bug#873783: wcc: FTBFS on non-amd64 architectures
Le 31/08/2017 à 21:58, Aaron M. Ucko a écrit : > Great, thanks for looking into all of these subissues! > Well... sorry for the false positive news but wsh needs big update to support other arches. It is based on a ldscript used to map relocated content which is arch specific. This ldscript has been made only for amd64. I can try to make one or two more, but not for all the arches ! I will push an issue to Jonathan in mainstream to discuss this with him. It would be great to have at least arm* & powerpc (personal choice of course :) ) In the meantime, I've updated to amd64 only. it should work on hurd/kfreebsd now. -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: 7010 9A3C E210 763E 6341 4581 C257 B91B CDAF C1EA signature.asc Description: OpenPGP digital signature
Bug#873821: wcc Depends: binutils (< 2.29) but 2.29-8 is to be installed
Le 31/08/2017 à 20:56, Adrian Bunk a écrit : > Sorry my bad, then a binNMU should be sufficient. Yes this is the case here :-) > > But since you anyway plan an upload for #873783 this will en passant > also fix this problem. > >> but if I update the package version (to 0.0.2+dfsg-2), the >> upgrade test of piupart will also fails, while the -1 version of the >> package is not rebuilt in the Debian ftp-master. > There won't be any problems with piuparts when you upload 0.0.2+dfsg-2 Ok, I thought that a binNMU was first required to make it work first. I'll then wait a little to finish the update to close #873783 in the same time. Thanks, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: 7010 9A3C E210 763E 6341 4581 C257 B91B CDAF C1EA signature.asc Description: OpenPGP digital signature
Bug#873783: wcc: FTBFS on non-amd64 architectures
Le 31/08/2017 à 05:10, Aaron M. Ucko a écrit : > Source: wcc > Version: 0.0.2+dfsg-1 > Severity: important > Tags: upstream > Justification: fails to build from source > > Builds of wcc for architectures other than (Linux) amd64 have been > failing. > > On non-x86 architectures, there are two considerations: the > embedded copy of openlibm under src/wsh generally has no > $(ARCH)/Make.files, and GCC doesn't support -masm=intel regardless. > You could sidestep the former by building against separately packaged > libopenlibm-dev (as called for by Policy 4.13), but the latter may be > more of a problem. Should be corrected by last update using libopenlibm-dev from Debian. For non-Linux, I've updated to Architecture: linux-any by now. I'll check for Freebsd & Hurd in the meantime. > > On non-Linux architectures (kFreeBSD and presumably also the Hurd if > and when clang becomes installable there), there's no > for arch.h to include. > > On i386, wsh somehow winds up compiled for the wrong architecture, > leading to link errors: > > /usr/bin/ld: skipping incompatible > /usr/lib/gcc/i686-linux-gnu/7/../../../i386-linux-gnu/libiberty.a when > searching for -liberty > /usr/bin/ld: skipping incompatible /usr/lib/i386-linux-gnu/libiberty.a when > searching for -liberty > /usr/bin/ld: cannot find -liberty > > On x32 (admittedly not a release architecture), wcc is still in the > Needs-Build queue; I'm not sure what will happen there. I will make some more tests on various arches including CI). If everything is okay I update the package. Cheers, -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: 7010 9A3C E210 763E 6341 4581 C257 B91B CDAF C1EA signature.asc Description: OpenPGP digital signature
Bug#873821: wcc Depends: binutils (< 2.29) but 2.29-8 is to be installed
Hello! Le 31/08/2017 à 16:01, Adrian Bunk a écrit : > Package: wcc > Version: 0.0.2+dfsg-1 > Severity: serious > > The following packages have unmet dependencies: > wcc : Depends: binutils (< 2.29) but 2.29-8 is to be installed Thanks for the report. I've check where the error comes from. This is the result of the version of binutils dependency (<2.29) generated by dpkg-buildpackage. The source package only has a build dependency on binutils-dev (without explicit version). When building again the package, the Depends list is updated: Depends: libbinutils (>= 2.29), libbinutils (<< 2.30), libc6 (>= 2.14), libcapstone3 (>= 3.0.0), libelf1 (>= 0.142), liblua5.3-0, libopenlibm2 (>= 0.4), lua5.2 This means that a simple rebuild of wcc with uptodate sid should correct the error, but if I update the package version (to 0.0.2+dfsg-2), the upgrade test of piupart will also fails, while the -1 version of the package is not rebuilt in the Debian ftp-master. -- OPhilippe Thierry. /Y\/ Hardened embedded systems o#o GPG: 7010 9A3C E210 763E 6341 4581 C257 B91B CDAF C1EA signature.asc Description: OpenPGP digital signature
Bug#873783: wcc: FTBFS on non-amd64 architectures
Le 31 août 2017 05:10:10 GMT+02:00, "Aaron M. Ucko" a écrit : >Source: wcc >Version: 0.0.2+dfsg-1 >Severity: important >Tags: upstream >Justification: fails to build from source > >Builds of wcc for architectures other than (Linux) amd64 have been >failing. > >On non-x86 architectures, there are two considerations: the >embedded copy of openlibm under src/wsh generally has no >$(ARCH)/Make.files, and GCC doesn't support -masm=intel regardless. >You could sidestep the former by building against separately packaged >libopenlibm-dev (as called for by Policy 4.13), but the latter may be >more of a problem. > >On non-Linux architectures (kFreeBSD and presumably also the Hurd if >and when clang becomes installable there), there's no >for arch.h to include. > >On i386, wsh somehow winds up compiled for the wrong architecture, >leading to link errors: > >/usr/bin/ld: skipping incompatible >/usr/lib/gcc/i686-linux-gnu/7/../../../i386-linux-gnu/libiberty.a when >searching for -liberty >/usr/bin/ld: skipping incompatible /usr/lib/i386-linux-gnu/libiberty.a >when searching for -liberty > /usr/bin/ld: cannot find -liberty > >On x32 (admittedly not a release architecture), wcc is still in the >Needs-Build queue; I'm not sure what will happen there. > >At any rate, I'm reporting this as a single bug because I suspect you >may just want to declare Architecture: amd64 (with the possible >addition of x32) and be done with it. That said, you're certainly >welcome to address any or all of these portability issues if feasible. > >Thanks! Hello Aaron, Thanks for the report ! I'll update the package to use the packaged libopenlibm-dev. For the elf-em.h, I'll check for the corresponding file in Freebsd and Hurd and add some preprocessing to support all of them. I'll test on arm, but I dunno if there is a debomatic for others arches than amd64. If you know if there is such testbed, it would be great. -- O Philippe Thierry. /Y\/ GPG: 7010 9a3c e210 763e 6341 4581 c257 b91b cdaf c1ea o#o (sent from my smartphone)
Bug#871353: scap-security-guide: FTBFS: unable to parse output/guide.xml
Le 7 août 2017 18:00:24 GMT+02:00, Lucas Nussbaum a écrit : >Source: scap-security-guide >Version: 0.1.31-4 >Severity: serious >Tags: buster sid >User: debian...@lists.debian.org >Usertags: qa-ftbfs-20170807 qa-ftbfs >Justification: FTBFS on amd64 > >Hi, > >During a rebuild of all packages in sid, your package failed to build >on >amd64. > >Relevant part (hopefully): >> make[3]: Entering directory '/<>/Fedora' >> /bin/sh: 1: Syntax error: Bad fd number >> mkdir -p output/ >> cp ../shared/xccdf/shared_guide.xml output/ >> xsltproc --stringparam SHARED_RP "/<>/shared" -o >output/shorthand.xml input/guide.xslt output/guide.xml >> warning: failed to load external entity "output/guide.xml" >> unable to parse output/guide.xml >> ../shared/product-make.include:65: recipe for target >'output/shorthand.xml' failed >> make[3]: *** [output/shorthand.xml] Error 6 > >The full build log is available from: >http://aws-logs.debian.net/2017/08/07/scap-security-guide_0.1.31-4_unstable.log > >A list of current common problems and possible solutions is available >at >http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to >contribute! > >About the archive rebuild: The rebuild was done on EC2 VM instances >from >Amazon Web Services, using a clean, minimal and up-to-date chroot. >Every >failed build was retried once to eliminate random failures. Hello Lucas, Ack. I'll take a look at this. I'm currently working on a major update of this package. -- O Philippe Thierry. /Y\/ GPG: 7010 9a3c e210 763e 6341 4581 c257 b91b cdaf c1ea o#o (sent from my smartphone)
Bug#865479: ITP: ruby-rubydns -- An easy to use DNS server and resolver for Ruby
Package: wnpp Severity: wishlist Owner: pkg-ruby-extras-maintain...@lists.alioth.debian.org * Package name: ruby-rubydns Version : 1.0.3 Upstream Author : Samuel G. D. Williams * URL : https://github.com/ioquatix/rubydns/ * License : MIT Programming Lang: ruby Section : net Description :An easy to use DNS server and resolver for Ruby thanks, -- Phil.
Bug#865352: RFP: em-proxy -- EventMachine Proxy DSL for writing high-performance transparent / intercepting proxies in Ruby
Package: wnpp Severity: wishlist Version: N/A; reported 2017-06-20 * Package name : em-proxy Upstream Author : Ilya Grigorik * URL: https://github.com/igrigorik/em-proxy * License: MIT Description: EventMachine Proxy DSL for writing high-performance transparent / intercepting proxies in Ruby Hi all, I'm currently looking forward to package bettercap[1][2] in Debian, yet this tool as multiple unsatistied dependencies on ruby libs: ruby-em-proxy (>= 0.1.8) ruby-net-dns (>= 0.8.0) ruby-network-interface (>= 0.0.1) ruby-rubydns (>= 1.0.3) I'm not a ruby specialist, so i ask for the help of the ruby team to package these libs. That's why i post four RFP, one for each. Best regards, -- Philippe. [1] https://bettercap.org/ [2] https://anonscm.debian.org/cgit/pkg-security/bettercap.git
Bug#865338: ITP: bettercap -- Complete, modular, portable and easily extensible MITM framework
Package: wnpp Severity: wishlist Owner: Debian Security Tools Packaging Team thanks Error in previous ITP (bug 865299) due to line return in the middle of the owner line -- Philippe.
Bug#864897: ITP: dhcpig - DHCP exhaustion script using scapy network library
Package: wnpp Severity: wishlist Owner: Debian Security Tools Packaging Team * Package name: dhcpig Version : 1.0 (waiting for version management or a tag from upstream, issue posted) Upstream Author : Kevin Amorin * URL : https://github.com/kamorin/DHCPig/issues * License : GPL-2+ Programming Lang: python Section : net Description :DHCP exhaustion script using scapy network library thanks, -- Phil.
Bug#864784: ITP: dirb - URL bruteforcing tool
Package: wnpp Severity: wishlist Owner: Philippe Thierry * Package name: dirb Version : 2.22+dfsg-1 Upstream Author : The Dark Raver * URL : https://sourceforge.net/projects/dirb/ * License : GPL-2+ Programming Lang: C Section : net Description :URL bruteforcing tool thanks, -- Phil.
Bug#862765: ITP: atomic -- Atomic Run Tool for installing/running/managing container images
Package: wnpp Severity: wishlist Owner: Philippe Thierry Dear mentors, I am looking for a sponsor for my package "atomic" * Package name: atomic Version : 1.7.1-1 Upstream Author : Atomic Project * URL : https://github.com/projectatomic/atomic * License : GPL-2+ Programming Lang: Python Section : admin Description : Atomic Run Tool for installing/running/managing container images It builds those binary packages: atomic: allows an image provider to specify how a container image expects to be run atomic-doc: various documentations and concepts behind atomic To access further information about this package, please visit the following URL: https://mentors.debian.net/package/atomic Alternatively, one can download the package with dget using this command: dget -x https//mentors.debian.net/debian/pool/main/a/atomic/atomic_1.7.1-1.dsc This project defines the entrypoint for Project Atomic hosts. On an Atomic Host, there are at least two distinct software delivery vehicles; Docker (often used in combination with the traditional RPM/yum/dnf), and rpm-ostree to provide atomic upgrades of the host system. The goal of Atomic is to provide a high level, coherent entrypoint to the system, and fill in gaps in Linux container implementations. For Docker, |atomic| can make it easier to interact with special kinds of containers, such as super-privileged debugging tools and the like. atomic host does not support Debian-based OS by now (limited to rpm-based OS). Yet it permit to easily install/uninstall docker container into the system. Regards, -- Philippe THIERRY
Bug#862763: atomic/1.17.1-1 [ITP] -- Atomic Run Tool for installing/running/managing container images
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "atomic" * Package name: atomic Version : 1.7.1-1 Upstream Author : Atomic Project * URL : https://github.com/projectatomic/atomic * License : GPL-2+ Programming Lang: Python Section : admin Description : Atomic Run Tool for installing/running/managing container images It builds those binary packages: atomic: allows an image provider to specify how a container image expects to be run atomic-doc: various documentations and concepts behind atomic To access further information about this package, please visit the following URL: https://mentors.debian.net/package/atomic Alternatively, one can download the package with dget using this command: dget -x https//mentors.debian.net/debian/pool/main/a/atomic/atomic_1.7.1-1.dsc This project defines the entrypoint for Project Atomic hosts. On an Atomic Host, there are at least two distinct software delivery vehicles; Docker (often used in combination with the traditional RPM/yum/dnf), and rpm-ostree to provide atomic upgrades of the host system. The goal of Atomic is to provide a high level, coherent entrypoint to the system, and fill in gaps in Linux container implementations. For Docker, |atomic| can make it easier to interact with special kinds of containers, such as super-privileged debugging tools and the like. atomic host does not support Debian-based OS by now (limited to rpm-based OS). Yet it permit to easily install/uninstall docker container into the system. Regards, -- Philippe THIERRY
Bug#861394: RFS: wcc/20170424-1 [ITP] -- a collection of compilation tools to perform binary black magic on the GNU/Linux and other
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "wcc" * Package name: wcc Version : 20170424-1 Upstream Author : Jonathan Brossard * URL : https://github.com/endrazine/wcc * License : MIT Section : utils It builds those binary packages: wcc - This tool permits one to manipulate binaries and shared liraries to reuse their API into an external usage, as a relocatable object that can be linked to a new project, or through an interpreter (wsh) to execute internal API directly. wcc-doc - All documentations including Doxygen output and various Howtos on how to use the Witchcraft Compiler Collection. This documentation also include various examples. This project is a set of tool to manipulate ELF, PE and COFF binaries to transform them into relocatable object (.o) file or to reuse their API directly through an interpreter. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wcc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wcc/wcc_20170424-1.dsc More information about hello can be obtained from https://github.com/endrazine/wcc Changes since the last upload: * Initial release (Closes: #861390). * Updated various spelling error. * Updated man pages. * Created two binary packages separating a complete documentation pkg. Regards, -- Philippe THIERRY
Bug#861390: ITP: wcc -- a collection of compilation tools to perform binary black magic on the GNU/Linux and other POSIX platforms
Package: wnpp Severity: wishlist Owner: Philippe Thierry * Package name: wcc Version : 20170424-1 Upstream Author : Jonathan Brossard * URL : https://github.com/endrazine/wcc * License : MIT Programming Lang: C Description : a collection of compilation tools to perform binary black magic on the GNU/Linux and other POSIX platforms This tool permits one to manipulate binaries and shared liraries to reuse their API into an external usage, as a relocatable object that can be linked to a new project, or through an interpreter (wsh) to execute internal API directly. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wcc -- P. Thierry.
Bug#860145: RFS: openscap-daemon/0.1.6-1 [ITP] -- SCAP security policy compliance daemon for a complete infrastructure
Le 26/04/2017 à 11:36, Gianfranco Costamagna a écrit : control: tags -1 moreinfo control: owner -1 ! I've updated the package with a lot of updates/corrections. missing copyrights, e.g. Copyright (C) 2015 Brent Baude Copyright (c) 2003-2005 by Peter Astrand Hi Gianfranco, Thank's for the review. Should be ok for copyright. Take some time to manage license-reconcile output. It still says that "LGPL (v2 or later)" is not equal to "LPGL-2+", but no more copyright error messages. -- Philippe.
Bug#860145: RFS: openscap-daemon/0.1.6-1 [ITP] -- SCAP security policy compliance daemon for a complete infrastructure
Le 17/04/2017 à 08:12, Paul Wise a écrit : I don't intend to sponsor this, but here is a quick review: [...] Thanks for this review ! I've updated the package with a lot of updates/corrections. The package is now based on python3 only and use pybuild -- Philippe Thierry.
Bug#860126: ITP: openscap-daemon -- SCAP security policy compliance daemon for a complete infrastructure
Package: wnpp Severity: wishlist Owner: Philippe Thierry * Package name : openscap-daemon Version : 0.1.6-1 Upstream Author : Martin Preisler * URL : https://www.open-scap.org/tools/openscap-daemon * License : LGPLv2+ Programming Lang: Python Section : admin Description : SCAP security policy compliance daemon for a complete infrastructure SCAP-security-guide works with the OpenSCAP tool, which is already packaged in Debian. It builds those binary packages: openscap-daemon - SCAP daemon and CLI to manage periodic checks on a complete infrastructure To access further information about this package, please visit the following URL: https://mentors.debian.net/package/openscap-daemon Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/openscap-daemon/openscap-daemon_0.1.6-1.dsc The package has been passed to debomatic: http://debomatic-amd64.debian.net/distribution#unstable/openscap-daemon/0.1.6-1 The openscap-daemon is a part of the SCAP ecosystem based on the OpenSCAP tool to support policy compliance check at infrastructure level. -- P. Thierry
Bug#673565: RFP: ftpsync -- Debian mirror scripts
retitle 673565 ITP: ftpsync -- Debian mirror scripts owner 673565 ! thanks Hello, I'm using ftpsync for some times now (working mostly offline, requiring local mirrors). I propose to try making a package for it. I've pushed a basic content on mentors.debian.net (clearly incomplete, just made a basic packaging). I will try to update the package regulary and test it on debomatic. Regards, -- P. Thierry.
Bug#856425: ITP: scap-security-guide -- security guides and conformity checks using SCAP standard
Package: wnpp Severity: wishlist Owner: Philippe Thierry * Package name: scap-security-guide Version : 0.1.31-10 Upstream Author : Watson Yuuma Sato * URL : https://www.open-scap.org/security-policies/scap-security- guide/ * License : Unlicenced Programming Lang: Python, XML, XSLT Section : admin Description : security guides and conformity checks using SCAP standard SCAP-security-guide works with the OpenSCAP tool, which is already packaged in Debian. It builds those binary packages: ssg-applications - SCAP Guides and benchmarks targeting applications such as ssg-base - SCAP Security guide base content and documentation ssg-debfamilly - SCAP Guides and benchmarks targeting all deb-based ssg-debian - SCAP Guides and benchmarks targeting Debian 8 ssg-otheros - SCAP Guides and benchmarks targeting other GNU/Linux To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scap-security-guide Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scap-security-guide /scap-security-guide_0.1.31-9.dsc The goal of this package is to deploy SCAP XCCDF Benchmarks and Guides for various targets not deployed by the OpenSCAP core package, but supported by the SCAP-security-guide community in which I work as contributor for Ubuntu, Debian and ANSSI best practices. Using these guides/benchmarks, it is possible to validate conformity of Debian-based deployment against standard security policies such as ANSSI Best-practices, PCI-DSS, NIST SP-800... and to launch remediation scripts when needed. Using the OpenSCAP ecosystem, it is possible to manage the security policy of a complete infrastructure, when launching OpenSCAP tool with the above benchmarks through ssh (for e.g.) or on VM or docker templates.
Bug#856404: RFS: scap-security-guide/0.1.31-9 ITP: security guides and conformity checks using SCAP standard
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "scap-security-guide" Package name: scap-security-guide Version : 0.1.31-9 Upstream Author : Watson Yuuma Sato (ws...@redhat.com) URL :https://www.open-scap.org/security-policies/scap-security-guide/ License : unlicenced (seehttps://github.com/OpenSCAP/scap-security-guide/blob/master/LICENSE) Section : admin It builds those binary packages: ssg-applications - SCAP Guides and benchmarks targeting applications such as ssg-base - SCAP Security guide base content and documentation ssg-debfamilly - SCAP Guides and benchmarks targeting all deb-based ssg-debian - SCAP Guides and benchmarks targeting Debian 8 ssg-otheros - SCAP Guides and benchmarks targeting other GNU/Linux To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scap-security-guide Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scap-security-guide/scap-security-guide_0.1.31-9.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * Updated binary packages name to simplify the structure * bin packages are familly-based, avoiding variation when updating About SCAP-security-guide: SCAP-security-guide works with the OpenSCAP tool, which is already packaged in Debian. The goal of this package is to deploy SCAP XCCDF Benchmarks and Guides for various targets not deployed by the OpenSCAP core package, but supported by the SCAP-security-guide community in which I work as contributor for Ubuntu, Debian and ANSSI best practices. Using these guides/benchmarks, it is possible to validate conformity of Debian-based deployment against standard security policies such as ANSSI Best-practices, PCI-DSS, NIST SP-800... and to launch remediation scripts when needed. Using the OpenSCAP ecosystem, it is possible to manage the security policy of a complete infrastructure, when launching OpenSCAP tool with the above benchmarks through ssh (for e.g.) or on VM or docker templates. Regards, Philippe Thierry
Bug#853903: RFS: scap-security-guide/0.1.31-6 [ITP] -- security guides and conformity checks using SCAP standard
Package: sponsorship-requests Severity: wishlist Dear mentors, First, thanks Tobi for your message ! I've corrected Warnings and Informational from lintian. Pedantic ones are harder to correct : - there is no explicit upstream changelog in sources, the scap-security-guide.spec is used as a changelog file. I deploy it through the ssg-base package - other binary packages don't deploy this file, ssg-base being a dependency of all other binary pacakges - there is not gpg check available on the github repository for uscan - the .svn control dir is voluntary in the upsteam sources, used as a "git submodule" like mechanism for the Red-Hat specific documentation - duplicated files is due to a current work on new PCIDSS derivative on which the RedHat team is working. When the 0.1.31 version has been released, the derivative was just a duplication of the PCIDSS content. To continue this mail in a standard way... I am looking for a sponsor for my package "scap-security-guide" Package name: scap-security-guide Version : 0.1.31-6 Upstream Author : Watson Yuuma Sato (ws...@redhat.com) URL :https://www.open-scap.org/security-policies/scap-security-guide/ License : unlicenced (seehttps://github.com/OpenSCAP/scap-security-guide/blob/master/LICENSE) Section : admin It builds those binary packages: ssg-base - SCAP Security guide base content and documentation ssg-debian8 - SCAP Guides and benchmarks targeting Debian 8 ssg-firefox - SCAP Guides and benchmarks targeting Firefox Browser ssg-jre- SCAP Guides and benchmarks targeting Java Runtime Environment ssg-rhel5 - SCAP Guides and benchmarks targeting Red-Hat Enterprise Linux 5 ssg-rhel6 - SCAP Guides and benchmarks targeting Red-Hat Enterprise Linux 6 ssg-rhel7 - SCAP Guides and benchmarks targeting Red-Hat Enterprise Linux 7 ssg-ubuntu1604 - SCAP Guides and benchmarks targeting Ubuntu 16.04 ssg-webmin - SCAP Guides and benchmarks targeting Webmin To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scap-security-guide Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scap-security-guide/scap-security-guide_0.1.31-6.dsc More information about scap-security-guide can be obtained fromhttps://www.open-scap.org/security-policies/scap-security-guide The repository is onhttps://github.com/OpenSCAP/scap-security-guide Changes since the last upload: * Various corrections for lintian conformity. Only pedantic and experimental are still present. About SCAP-security-guide: SCAP-security-guide works with the OpenSCAP tool, which is already packaged in Debian. The goal of this package is to deploy SCAP XCCDF Benchmarks and Guides for various targets not deployed by the OpenSCAP core package, but supported by the SCAP-security-guide community in which I work as contributor for Ubuntu, Debian and ANSSI best practices. Using these guides/benchmarks, it is possible to validate conformity of Debian-based deployment against standard security policies such as ANSSI Best-practices, PCI-DSS, NIST SP-800... and to launch remediation scripts when needed. Using the OpenSCAP ecosystem, it is possible to manage the security policy of a complete infrastructure, when launching OpenSCAP tool with the above benchmarks through ssh (for e.g.) or on VM or docker templates. Regards, Philippe Thierry
Bug#619178: help2man: does not catch 'usage' for the synopsis
Hi, Le jeudi 14 juin 2012, Jakub Wilk a écrit : While your patch is indeed an improvement, it's not sufficient for a decent > argparse support. Two other things that help2man doesn't handle well: > - usage can be spread across multiple lines; > - it's "optional arguments:" instead of "Options:". > > I must admit I haven't heavily tested it. Bad habit. I'll try to improve it this summer. Thanks for the feedback -- Jean-Philippe -- Jean-Philippe
Bug#619461: [Pkg-cups-devel] Bug#619461: Bug#619461: cups-pdf: PDFVer andGSCall keys not taken into account
I finally find some time to test. Removed 2.5.0 through aptitude, downloaded 2.5.1-3 from the testing repo and installed it. I still end up with a blank page. Hope this helps Le 21 avril 2011 21:29, Martin-Éric Racine a écrit : > 2011/4/1 : > > No clue I must admit. Looking at the log file on 2.5.1 everything seems > to run smoothly but I end up with a blank file. > > > > I can investigate further; I would just need some directions. > > Can you compare the results between upgrading from 2.5.0 to 2.5.1, > verus purging 2.5.0 first and then installing 2.5.1 after? Someone in > another bug report seems to have spotted the problem as being possible > related to upgrades failing to update the content of our PPD, which > might require handling by our package's maintainer script. > > Martin-Éric > -- Jean-Philippe
Bug#619461: [Pkg-cups-devel] Bug#619461: cups-pdf: PDFVer and GSCall keys not taken into account
Hi, 2011/3/24 Volker Behr > > > On Thu, 2011-03-24 at 17:54 +0100, Jean-Philippe Thierry wrote: > > Hi, > > > > Le 24 mars 2011 15:44, Martin-Éric Racine > > a écrit : > > 2011/3/24 Volker Behr : > > > The log-file you sent me contains the following line: > > > > > > Thu Mar 24 11:05:53 2011 [DEBUG] file already pdf, simply > > copying it > > > > > (cp /var/spool/cups-pdf/SPOOL/cups2pdf-12256 > /home/jpht/tmp/PDF/Bugs_in_package_cups-pdf_--_Debian_Bug_report_logs.pdf) > > > > > > This option to directly copy PDF instead of reprocessing it > > was > > > suggested to me some time back and I decided not to > > implement it since > > > it would disable all options set in cups-pdf.conf on the > > respective > > > files. This is exactly what happens to you here: the PDF is > > just passed > > > through instead of getting re-worked with all your desired > > options by > > > CUPS-PDF. > > > > > > So, speaking for upstream: no fix needed. > > > My advise to the distribution: remove this additional patch > > on CUPS-PDF > > > since it breaks basic functionality. > > > > > > The patch in question was removed in 2.5.1-1 as far as Debian > > and > > Ubuntu are concerned: > > > > * Dropped 70_cups-pdf_support-pdf-workflow.patch > >+ This patch has received more criticism than praises from > > the end-users, > > because it essentially renders the Ghostscript options in > > cups-pdf.conf > > useless, plus it no longer applies cleanly to the > > upstream code. > > > > From this perspective, I'd mark the issue as fixed since that > > version. Agreed? > > > > Martin-Éric > > > > just tried installing cups-pdf from sid on my squeeze. GSCall and > > PDFVer are taken into acount but... I am only getting 1 page empty > > documents; even failling back to the default settings > > in /etc/cups/cups-pdf.conf. Could it be due to a dependency issue even > > if not raised by the package? > > > > log file attached > > > Just as a note: > > might be related to issue #617468 > > > > I end up recompiling the package from source (squeeze version) removing patch 70_cups-pdf_support-pdf- workflow.patch and it works. Thanks folks for your help. -- Jean-Philippe
Bug#619461: [Pkg-cups-devel] Bug#619461: cups-pdf: PDFVer and GSCall keys not taken into account
Hi, Le 24 mars 2011 15:44, Martin-Éric Racine a écrit : > 2011/3/24 Volker Behr : > > The log-file you sent me contains the following line: > > > > Thu Mar 24 11:05:53 2011 [DEBUG] file already pdf, simply copying it > > (cp /var/spool/cups-pdf/SPOOL/cups2pdf-12256 > /home/jpht/tmp/PDF/Bugs_in_package_cups-pdf_--_Debian_Bug_report_logs.pdf) > > > > This option to directly copy PDF instead of reprocessing it was > > suggested to me some time back and I decided not to implement it since > > it would disable all options set in cups-pdf.conf on the respective > > files. This is exactly what happens to you here: the PDF is just passed > > through instead of getting re-worked with all your desired options by > > CUPS-PDF. > > > > So, speaking for upstream: no fix needed. > > My advise to the distribution: remove this additional patch on CUPS-PDF > > since it breaks basic functionality. > > The patch in question was removed in 2.5.1-1 as far as Debian and > Ubuntu are concerned: > > * Dropped 70_cups-pdf_support-pdf-workflow.patch >+ This patch has received more criticism than praises from the > end-users, > because it essentially renders the Ghostscript options in > cups-pdf.conf > useless, plus it no longer applies cleanly to the upstream code. > > From this perspective, I'd mark the issue as fixed since that version. > Agreed? > > Martin-Éric > just tried installing cups-pdf from sid on my squeeze. GSCall and PDFVer are taken into acount but... I am only getting 1 page empty documents; even failling back to the default settings in /etc/cups/cups-pdf.conf. Could it be due to a dependency issue even if not raised by the package? log file attached -- Jean-Philippe cups-pdf_log Description: Binary data
Bug#619461: cups-pdf: PDFVer and GSCall keys not taken into account
Package: cups-pdf Version: 2.5.0-16 Severity: normal Hi, I am trying to set up an encrypted pdf printer using cups-pdf. I find my way in identifying the right command-line options for encryption with ps2pdf and everything works fine. I then tuned the /etc/cups/cups-pdf.conf file changing the GSCall key but without any success so far :( PDF document is generated but is still a PDF 1.3 document (although I set the PDFVer key to 1.4) and encryption options are not taken into account. I looked at the logs (DEBUG level) but nothing there except that it says: found beginning of pdf code (%PDF-1.3). I tried -dCompatibilityLevel=%s, -dCompatibilityLevel=1.4, -dCompatibilityLevel=PDFVer; none of them worked. I am probably missing something straightforward but googling did not help me so... Thanks for your help Jean-Philippe -- System Information: Debian Release: 6.0.1 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups-pdf depends on: ii cups1.4.4-7 Common UNIX Printing System(tm) - ii cups-client 1.4.4-7 Common UNIX Printing System(tm) - ii ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libpaper-utils 1.1.24 library for handling paper charact cups-pdf recommends no packages. Versions of packages cups-pdf suggests: pn system-config-printer-gnome | (no description available) -- Configuration Files: /etc/cups/cups-pdf.conf changed: Out ${HOME}/tmp/PDF Label 0 Grp lpadmin LogType 1 PDFVer 1.4 GSCall %s -q -dCompatibilityLevel=PDFVer -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile="%s" -dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -sOwnerPassword=AjC -dEncryptionR=3 -dKeyLength=128 -dPermissions=-3904 -c .setpdfwrite -f %s -- 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#619178: help2man: does not catch 'usage' for the synopsis
Package: help2man Version: 1.38.2 Severity: wishlist Hi, I am a Python fan and argparse (optparse replacer) is printing 'usage: XXX' as a synopsis. Bad luck help2man is looking for 'Usage' only. It would be nice to have both accepted at least for me. Regards Jean-Philippe -- System Information: Debian Release: 6.0 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages help2man depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii liblocale-gettext-perl1.05-6 Using libc functions for internati ii perl 5.10.1-17 Larry Wall's Practical Extraction help2man recommends no packages. help2man suggests no packages. -- no debconf information 330c330 < my $PAT_USAGE = _('Usage'); --- > my $PAT_USAGE = _('Usage|usage');
Bug#550092: dia2code: Segmentation Fault into 64 bits systems
Hi all, I've just installed dia2code on my Lenny system (AMD64) and I get the same error. I attach the dia file I am using in ccase it can help. Jean-Philippe sechage_inverse-base_classes.dia Description: application/dia-diagram
Bug#308795: Solved
I have cleaned up my python module tree (it was a mess), reconfigured both numarray and Numeric and it's now working well. It seems I had troubles with different versions of Numeric. Perhaps python-tables uses a function that I don't in the NumPy packages, because all was working well since no calls were made to python-tables. Anyway, congratulations for this package that is really handy to use and so efficient. Jean-Philippe
Bug#308795: floating point exception
Package: python2.3-tables Version: 0.9.1-2 Severity: normal when I try to add a row to an enlargeable table column, I get a floating point exception error. After some more trials, it seems that this occurs only when a variable is modified inside the loop that appends data to the table (the code is attached). -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1) Versions of packages python2.3-tables depends on: ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libhdf5-serial-1.6.2-0 [lib 1.6.2-3 Hierarchical Data Format 5 (HDF5) ii liblzo1 1.08-1.2 A real-time data compression libra ii libucl1 1.03-2 Portable compression library - run ii python2.3 2.3.5-3 An interactive high-level object-o ii python2.3-numarray 1.1.1-3 An array processing package modell -- no debconf information FileTable.py Description: application/python