RFS: php-simpletest
Hello, This is actaully in response to a bug fix for, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428013 The package already exists, http://packages.debian.org/lenny/php-simpletest, I have contacted the current maintainer, Charles, who stated that he doesn't have time to maintain this package any longer, so I offered to maintain it. Either way, I have built and tested a new version, (current upstream version) [dwri...@debian simpletest]$ tar zcv php-simpletest -f php-simpletest.tar.gz php-simpletest/ php-simpletest/php-simpletest_1.0.1_i386.changes php-simpletest/php-simpletest_1.0.1.dsc php-simpletest/php-simpletest_1.0.1.tar.gz php-simpletest/php-simpletest_1.0.1_all.deb you can find it here, http://dwright.us/misc/php-simpletest.tar.gz Thanks, David -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: mp3splt-gtk, mp3splt (updated package), and libmp3splt
Dear mentors, I am looking for a sponsor for my package "libmp3splt". * Package name: libmp3splt Version : 0.5.4-1 Upstream Author : Matteo Trotta and Alexandru Ionut Munteanu * URL : http://mp3splt.sourceforge.net/ * License : GPLv2+ Section : libs It builds these binary packages: libmp3splt-dev - development files for libmp3splt0 libmp3splt-mp3 - MP3 plugin for mp3splt libmp3splt-ogg - Ogg Vorbis plugin for mp3splt libmp3splt0 - library for splitting MP3 and Ogg Vorbis files The package appears to be lintian clean. The upload would fix these bugs: 515242 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libmp3splt - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libmp3splt/libmp3splt_0.5.4-1.dsc I am looking for a sponsor for the new version 2.2.3-1 of my package "mp3splt". It builds these binary packages: mp3splt- command line interface to split MP3 and Ogg Vorbis files without The package appears to be lintian clean. The upload would fix these bugs: 316046, 316050, 403463, 459510, 488931 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/mp3splt - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/mp3splt/mp3splt_2.2.3-1.dsc I am looking for a sponsor for my package "mp3splt-gtk". * Package name: mp3splt-gtk Version : 0.5.4-1 Upstream Author : Alexandru Munteanu * URL : http://mp3splt.sourceforge.net/ * License : GPLv2+ Section : sound It builds these binary packages: mp3splt-gtk - GTK interface to split MP3 and Ogg Vorbis files without reencodin The package appears to be lintian clean. The upload would fix these bugs: 500446, 515243 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/mp3splt-gtk - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/mp3splt-gtk/mp3splt-gtk_0.5.4-1.dsc NOTES ABOUT PACKAGING: mp3splt will need to be uploaded at a later time, once libmp3splt passed through NEW. I have some strict versioned (build-)dependencies used, this is because upstream has told me to make sure to keep the version of mp3splt(-gtk) installed with the version of libmp3splt that was released at the same time I have not used dpkg symbols control files. This is because of the strict versioned dependencies, and because upstream says that they won't pay attention to API compatibility, ABI compatibility, or changing the soname, so there's really no point. I've got a bit of weird stuff in the packaging (debian/rules.local, debian/control.base, debian/regenerate.sh, debian/generate, and debian/shlibs-string.sh), but this is just added complexity to make things easier for me, and automate some of the manual tasks. :) Also, all of the packages in the libmp3splt source package conflict with and replace the (non-existant) libmp3splt package. This is to support smooth upgrades from upstream's unofficial packages. I'm not sure if I used Replaces correctly, tho... Thanks, Ryan -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
debian/watch file
Hi, I've noticed that lintian produces a warning when a package has no debian/watch file (at least when run with the -iI flags). I read the uscan(1) manpage, as the warning suggests, but I still am not sure if I got the format of the debian/watch file right. The manpage has this example: ftp://ftp.tex.ac.uk/tex-archive/web/c_cpp/cweb/cweb-(.*)\.tar\.gz If I got it correct, it means that (.*) will match the version used for the orig.tar.gz archive? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: debian/watch file
On Tue, Mar 24, 2009 at 10:22:09AM +0200, Panagiotes [paggas] Mousikides wrote: > > If I got it correct, it means that (.*) will match the version used for the > orig.tar.gz archive? Correct. -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: debian/watch file
"Panagiotes [paggas] Mousikides" writes: > The manpage has this example: > > ftp://ftp.tex.ac.uk/tex-archive/web/c_cpp/cweb/cweb-(.*)\.tar\.gz > > If I got it correct, it means that (.*) will match the version used > for the orig.tar.gz archive? Yes. Unfortunately, I just noticed that it will also match *zero* characters in that position (since the ‘*’ matches zero or more of the preceding atom). This contradicts the common wisdom to make the regex as specific as possible. So, a better example would be: ftp://ftp.tex.ac.uk/tex-archive/web/c_cpp/cweb/cweb-(.+)\.tar\.gz which will match only when there are one or more characters in the version-string position. -- \ “The future always arrives too fast, and in the wrong order.” | `\—Alvin Toffler | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: stardata-common (updated package)
Hi all, Please, don't download this package by now, I'm making some improvements on it. I have removed it from mentors.d.n. I'll upload it when it is ready. Thanks. Regards, Francisco. El lun, 23-03-2009 a las 09:11 +0100, Francisco M. García Claramonte escribió: > Dear mentors, > > I am looking for a sponsor for the new version 0.6 > of my package "stardata-common". > > It builds these binary packages: > stardata-common - Common framework to manage astronomy packages > > This package allows the installation and removal of astronomy catalogues, > converting those catalogues to astronomy programs' data formats. > . > All stardata catalogues conforming to stardata-common policy are > converted automatically at installation time to the formats of > astronomy programs that support stardata-common. > . > The register-stardata program is transparent for the user; this program > is called automatically when any astronomy package conforming to the > stardata-common policy is installed, upgraded or removed. > > > The package appears to be lintian clean. > > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/s/stardata-common > - Source repository: deb-src http://mentors.debian.net/debian unstable main > contrib non-free > - dget > http://mentors.debian.net/debian/pool/main/s/stardata-common/stardata-common_0.6.dsc > > I would be glad if someone uploaded this package for me. > > > Kind regards > Francisco > signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: dpkg-shlibdeps: warning: dependency on.... (they use none of its symbols)
В Sat, 21 Mar 2009 14:00:41 -0430, Muammar El Khatib написа: > No, Debian is not BSD. But we have this > http://www.debian.org/ports/kfreebsd-gnu/: GNU/kFreeBSD is a GNU system. > Now, as you can see at #502083 and #320697 the use of the flag has > gotten problems before. The keyword here is "before". There were bugs in binutils exposed on some architectures, especially for C++ linking. Maybe new architectures like armel are still problematic in some cases. The problem Bernhard Link describes has been resolved upstream: http://sourceware.org/ml/binutils/2009-01/msg00413.html -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: dpkg-shlibdeps: warning: dependency on.... (they use none of its symbols)
* Yavor Doganov [090324 12:13]: > The keyword here is "before". There were bugs in binutils exposed on > some architectures, especially for C++ linking. Maybe new architectures > like armel are still problematic in some cases. The problem Bernhard > Link describes has been resolved upstream: > > http://sourceware.org/ml/binutils/2009-01/msg00413.html |(elf_link_add_object_symbols): Link in --as-needed libs if they | satisfy undefined symbols in other libs. I'm not into bfd enough to understand what it actually does, but both things I can imagine would be another argument against using it: 1) if it means to not remove libraries that suplies symbols that another library needs but that library is not linking to suplying library In this case it has nothing to do with the example I gave, because this only makes a difference if a library does not link to all the libraries it needs, which was not the case in my example. 2) if it means to not remove a library that is already needed by a library needed In this case --as-needed would still produce warnings in dpkg-shlibdeps for the harmless case (a program linking in dependencies of its libraries to support static linking), while it would silence warnings for the cases you would want to know about: linking against libraries not used at all. (Because in this case either something is very strange with the build-system or the "no used at all" is not really true). Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Build reproducibility
2009/3/24 Paul Wise : > In automake-based packages the recommended way to clean up after > autotools regeneration is 'make maintainer-clean'. Unfortunately > automake doesn't remove Makefile.in files in maintainer-clean by > default so you may have to delete them manually or with dh_clean. Actually I'm not running automake, do I need to? I just refresh configure after modifying configure.in to add some localization support; Makefile.am and Makefile.in work ok as they are, so I left them untouched... Thanks, Luca -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Build reproducibility
On Tue, Mar 24, 2009 at 11:37 PM, Luca Niccoli wrote: > Actually I'm not running automake, do I need to? Not unless you are patching Makefile.am -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Build reproducibility
Luca Niccoli wrote: > I just refresh configure after modifying configure.in to add some > localization support; Can you provide the patch you are applying to configure.in? It is often not necessary to touch this file. Sometimes you can easily patch configure or "fix" variable values during the `make' call. Regards, Daniel -- Aufgepasst: Sind Ihre Daten beim Online-Banking auch optimal geschützt? Jetzt absichern: https://homebanking.gmx.net/?mc=m...@footer.hb -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: CLAM, C++ library for audio and music
A new version of the following source packages is available at: http://clam-project.org/download/linux-debian-sid/svnsnapshots #493282 ITP: clam -- CLAM, C++ Library for Audio and Music #517910 ITP: clam-chordata -- CLAM Chordata, chord detection tool #518353 ITP: clam-plugins -- Extension plugins for the CLAM audio framework #517882 ITP: clam-networkeditor -- CLAM Network Editor, prototyping tool for CLAM Could someone review and eventually sponsor them? Please, ignore clam-annotator and clam-smstools source packages at that url and consider just the ones in the above list. Specially 'clam' which is the one other three packages depend on. Changes are as follows: * Updated to the latest svn version. * clam-plugins: now includes manpage for the ContinuousExcitationSynthesizer binary, * clam-plugins: the other two binaries are not compiled anymore as they were an old version of the synth (eBowSynthesizer) and a test binary (TestAudioDatabaseReader). * Added myself as Uploader and signed the package Still some issues and doubts someone in the list might help me to solve: * Should I split this RFS thread into several as i did for the ITP bugs? * The only lintian warning i get is: W: libclam13: package-name-doesnt-match-sonames libclam-audioio13 libclam- core13 libclam-processing13 As suggested by a debian developer and according to libpkg-guide we joined the library as the three libraries are going to change the soname at once on every release (i am also upstream release manager), but in some sponsoring guidelines i read that sponsored packages should be lintian clean including warnings. Should i ignore the warning or should i split the binary packages? -- David García Garzón (Work) dgarcia at iua dot upf anotherdot es http://www.iua.upf.edu/~dgarcia -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Build reproducibility
2009/3/24 Daniel Leidert : > Can you provide the patch you are applying to configure.in? It is often Of course: --- temp/grcm-0.1.6/configure.in2008-06-07 05:35:00.0 +0200 +++ grcm-0.1.6/configure.in 2009-03-24 00:32:09.0 +0100 @@ -22,7 +22,7 @@ AC_DEFINE_UNQUOTED(GETTEXT_PACKAGE,"$GETTEXT_PACKAGE") dnl Add the languages which your application supports here. -ALL_LINGUAS="" +ALL_LINGUAS="hu sv" AM_GLIB_GNU_GETTEXT AC_OUTPUT([ > not necessary to touch this file. Sometimes you can easily patch > configure or "fix" variable values during the `make' call. I had this feeling, but I then found the old packaging modified configure.in and thought it was right to do so > Regards, Daniel Thanks, Luca -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: sigx
Dear mentors, I am looking for a sponsor for my package "sigx". * Package name: sigx Version : 2.0.2-1 Upstream Author : kl...@triend.eu * URL : http://www.assembla.com/spaces/sigx * License : LGPL-2+ Section : devel It builds these binary packages: libsigx-2.0-2 - interthread communication library for C++ - runtime libsigx-2.0-dev - interthread communication for C++ - development files libsigx-2.0-doc - interthread communication for C++ - reference documentation The package appears to be lintian clean. The upload would fix these bugs: 492215 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/sigx - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/sigx/sigx_2.0.2-1.dsc The package can also be found in the collab-maint git repository: - git://git.debian.org/git/collab-maint/sigx.git -- for cloning (for rw access, use git+ssh://) - http://git.debian.org/?p=collab-maint/sigx.git -- for gitweb An earlier version of this package can also be found on Ubuntu: - https://launchpad.net/ubuntu/+source/sigx I would be glad if someone uploaded this package for me. Kind regards Chow Loong Jin signature.asc Description: This is a digitally signed message part
RFS: siege (updated package)
Dear mentors, I am looking for a sponsor for the new version 2.66-3 of my package "siege". It builds these binary packages: siege - Http regression testing and benchmarking utility The upload would fix these bugs: 521029, 521034 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/siege - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/siege/siege_2.66-3.dsc I would be glad if someone uploaded this package for me. I am taking over maintaining this package. Note that the lintian errors appear to be legacy, as I used quilt for the new patch I introduced. Comments very much welcome. Kind regards Tristan Greaves -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: siege (updated package)
On Tue, Mar 24, 2009 at 10:31:42PM +, Tristan Greaves wrote: > > Note that the lintian errors appear to be legacy, as I used quilt for > the new patch I introduced. You can still fix them, as a responsible maintainer :) The lintian on m.d.o lags a bit, in pedantic mode on my builder it reports: W: siege source: debhelper-but-no-misc-depends siege W: siege source: out-of-date-standards-version 3.7.3 (current is 3.8.1) I: siege source: quilt-patch-missing-description fix_cl_arguments.patch I: siege source: quilt-patch-missing-description fix_man_pages.patch I: siege source: quilt-patch-missing-description fix_bashism.patch W: siege source: patch-system-but-direct-changes-in-diff Makefile.in and 9 more W: siege source: ancient-libtool utils/ltconfig I: siege: hyphen-used-as-minus-sign usr/share/man/man1/bombardment.1.gz:40 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.1.gz:31 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.1.gz:63 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.1.gz:66 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.1.gz:81 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.1.gz:117 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.1.gz:139 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.1.gz:191 I: siege: hyphen-used-as-minus-sign usr/share/man/man1/siege.config.1.gz:24 I: siege: hyphen-used-as-minus-sign usr/share/man/man5/urls.txt.5.gz:26 I: siege: hyphen-used-as-minus-sign usr/share/man/man5/urls.txt.5.gz:29 P: siege: copyright-refers-to-symlink-license usr/share/common-licenses/GPL I: siege: copyright-with-old-dh-make-debian-copyright None of which are particularly troublesome to fix (except the ancient libtool, which you should co-ordinate with upstream if possible). -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Substituting the doc/ dir with a symlink
Policy 6.6.4 says that, when unpacking an upgraded package ... A directory will never be replaced by a symbolic link to a directory or vice versa; instead, the existing state (symlink or not) will be left alone and dpkg will follow the symlink if there is one. Which means that, when naively trying to replace the doc dir of a package with a symlink to my arch indep -data package I get bugs like #521047. Is the 'right' solution to that adding a postinst check that deletes a leftover empty dir and manually creates the symlink? Or will I get into a worse mess? What do I do if the dir is not empty (which could only happen if the dir was locally messed up with)? Do I just error out? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: siege (updated package)
Jonathan Wiltshire wrote: On Tue, Mar 24, 2009 at 10:31:42PM +, Tristan Greaves wrote: Note that the lintian errors appear to be legacy, as I used quilt for the new patch I introduced. You can still fix them, as a responsible maintainer :) The lintian on m.d.o lags a bit, in pedantic mode on my builder it reports: [snip] Many thanks. Please could you let me know which version of lintian you are using, and which command line arguments? I am just trying to reproduce the same pedantic behaviour at this end... Tris. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: siege (updated package)
On Tue, Mar 24, 2009 at 11:25:04PM +, Tristan Greaves wrote: > Many thanks. Please could you let me know which version of lintian you > are using, and which command line arguments? I am just trying to > reproduce the same pedantic behaviour at this end... 2.2.8 from sid, run with -I (+info tags), -E (+experimental tags) and --pedantic (speaks for itself). If you want the extended explanations, use -i as well. -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: RFS: siege (updated package)
Jonathan Wiltshire wrote: On Tue, Mar 24, 2009 at 11:25:04PM +, Tristan Greaves wrote: Many thanks. Please could you let me know which version of lintian you are using, and which command line arguments? I am just trying to reproduce the same pedantic behaviour at this end... 2.2.8 from sid, run with -I (+info tags), -E (+experimental tags) and --pedantic (speaks for itself). If you want the extended explanations, use -i as well. I'll probably shy away from sid for now. Is it sufficient for me to fix the standard lintian warnings thrown by my system? This will be easier said than done -- the direct changes seem pretty horrific (all sorts of changes made to the build system). It might be something I tackle more in the next step, which is to bring in the latest version of siege from upstream. Thanks, Tris. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: siege (updated package)
Le Wed, Mar 25, 2009 at 12:50:48AM +, Tristan Greaves a écrit : > Jonathan Wiltshire wrote: >> >> 2.2.8 from sid, run with -I (+info tags), -E (+experimental tags) and >> --pedantic (speaks for itself). If you want the extended explanations, >> use -i as well. > > I'll probably shy away from sid for now. Is it sufficient for me to fix > the standard lintian warnings thrown by my system? Dear Tristan, lintian is easy to backport. Just "debcheckout" lintian, "git checkout" the tag that corresponds to the latest release, and build the package. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: siege (updated package)
Tristan Greaves writes: > I'll probably shy away from sid for now. Is it sufficient for me to > fix the standard lintian warnings thrown by my system? No. If you're uploading the package targeted at Debian ‘sid’, you must build and test the package in a Debian ‘sid’ system. Note that this isn't the same thing as requiring you to run ‘sid’ as your *primary* operating system. Look at the ‘pbuilder’ package for a useful tool to build and test packages in an isolated environment. -- \ “Our products just aren't engineered for security.” —Brian | `\ Valentine, senior vice-president of Microsoft Windows | _o__)development, 2002 | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: CLAM, C++ library for audio and music
On Wed, Mar 25, 2009 at 12:25 AM, David García Garzón wrote: > * Should I split this RFS thread into several as i did for the ITP bugs? No need to. > * The only lintian warning i get is: > W: libclam13: package-name-doesnt-match-sonames libclam-audioio13 libclam- > core13 libclam-processing13 > As suggested by a debian developer and according to libpkg-guide we joined the > library as the three libraries are going to change the soname at once on every > release (i am also upstream release manager), but in some sponsoring > guidelines i read that sponsored packages should be lintian clean including > warnings. Should i ignore the warning or should i split the binary packages? It seems silly to have libclam-audioio, libclam-core and libclam-processing when you change the SONAME on all three at the same time. Why not just have libclam? Changing the SONAME at every release isn't the right thing to do either, it should only be changed when you break the ABI. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Build reproducibility
On Wed, Mar 25, 2009 at 1:56 AM, Luca Niccoli wrote: > -ALL_LINGUAS="" Ahhh, upstream should not be using this variable, please get them to switch to the po/LINGUAS file instead. This way it should not be nessecary to rebuild the configure & Makefiles in order to support and install a new language. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
