Uploaded sylpheed-claws 0.6.6claws23-2 (m68k) to non-us
-BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Fri, 28 Dec 2001 02:50:47 -0200 Source: sylpheed-claws Binary: sylpheed-claws Architecture: m68k Version: 0.6.6claws23-2 Distribution: unstable Urgency: low Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED] Changed-By: Gustavo Noronha Silva [EMAIL PROTECTED] Description: sylpheed-claws - Bleeding edge version of the Sylpheed mail client Closes: 126287 Changes: sylpheed-claws (0.6.6claws23-2) unstable; urgency=low . * Now really added libltdl3-dev! (Closes: #126287), sorry. Files: f305e26508f643a1d88d5bd7608bdddf 1014294 non-US extra sylpheed-claws_0.6.6claws23-2_m68k.deb -BEGIN PGP SIGNATURE- Version: 2.6.3i Charset: noconv iQCVAwUBPC8meW547I3m3eHJAQExKAQAp+w6WtMeZ3/z2I9mnQn9xht48wZjqVYE oT08GBPWWoFzPjWuLHAjX2jO7uFCr0TgPczOFxml+DkIMMups2dHYCZZ6rpPN+V6 5bvgUxpHEpHGuiT2+awkt8muOFYGdar+vslR85tniO8gzqxSc9Cfmnakf5g5e52x mbzXr48jOqU= =Dyfv -END PGP SIGNATURE-
Uploaded sword 1.5.2-4 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 11 Dec 2001 22:36:44 + Source: sword Binary: libsword1 libsword-dev Architecture: m68k Version: 1.5.2-4 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Daniel Glassey [EMAIL PROTECTED] Description: libsword-dev - Development files for libsword libsword1 - API/library for bible software Changes: sword (1.5.2-4) unstable; urgency=low . * Change maintainer to [EMAIL PROTECTED] * change shlibs to libsword1 = 1.5.2-4 (gnomesword bug 123418) by dh_makeshlibs -V 'libsword1 (= 1.5.2-4)' in debian/rules * remove reference to cheatah in package description Files: c0d956bf1d59541da4b2fa204127f0ac 231048 libs optional libsword1_1.5.2-4_m68k.deb a12eefbfe8a8c52e6d30ecc54ceb5d14 1247156 devel optional libsword-dev_1.5.2-4_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8JQcHWgZ1HEtaPf0RAvoYAJsH/Hl+M/SVMMNqTxrl9J6c66LUqACfW40s LZ689bK7NIlhMEjAvpa7Bu0= =L8Sh -END PGP SIGNATURE-
Uploaded libxode 1.2-2.1 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 9 Jul 2001 21:39:34 -0600 Source: libxode Binary: libxode1 libxode1-dev Architecture: m68k Version: 1.2-2.1 Distribution: unstable Urgency: low Maintainer: Bernd Eckenfels [EMAIL PROTECTED] Changed-By: LaMont Jones [EMAIL PROTECTED] Description: libxode1 - library of XML and string helper functions. libxode1-dev - library of XML and string helper functions. Closes: 95001 Changes: libxode (1.2-2.1) unstable; urgency=low . * Run libtoolize to get support for new architectures. Closes: #95001 Files: 4a63357c630f11b158cbc2fd157411a2 70620 devel optional libxode1-dev_1.2-2.1_m68k.deb f5a034a3b9ebe3e4fa32e01362927963 52094 devel optional libxode1_1.2-2.1_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7/WbcWgZ1HEtaPf0RAuevAJ91L+lmbrQHwcTCqKvkT5cecI+8nwCfR448 kNxdW85gFr0dI6oAMaYEGQ8= =8wq6 -END PGP SIGNATURE-
Uploaded gnustep-make 1.2.0-0.1 (m68k) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 9 Dec 2001 10:24:51 +0100 Source: gnustep-make Binary: gnustep-make Architecture: m68k Version: 1.2.0-0.1 Distribution: unstable Urgency: low Maintainer: Debian/m68k - bruno [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL PROTECTED] Description: gnustep-make - Basic GNUstep scripts and makefiles Closes: 115117 121452 Changes: gnustep-make (1.2.0-0.1) unstable; urgency=low . * NMU. New upstream release. * Fix error in postinst script (closes: #121452). * Include DESIGN document in binary package (closes: #115117). Files: ecfbb585becee8630349a3188aa90449 161294 libs optional gnustep-make_1.2.0-0.1_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Rick Younie [EMAIL PROTECTED] iEYEARECAAYFAjwvRawACgkQEycGpQPNsdK3uwCdFcorP5WIXV8ZdNeQd6Bg8Ey3 g90An21uIhYOyDpo1QGFBvzV2HplksmZ =ROV1 -END PGP SIGNATURE-
Uploaded kdegraphics 2.2.2-6 (m68k) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 23 Dec 2001 10:37:39 -0500 Source: kdegraphics Binary: kpaint kfract kview libkscan-dev kiconedit kcoloredit kghostview ksnapshot kamera libkscan1 kooka kruler Architecture: m68k Version: 4:2.2.2-6 Distribution: unstable Urgency: low Maintainer: Debian/m68k - bruno [EMAIL PROTECTED] Changed-By: Daniel Stone [EMAIL PROTECTED] Description: kamera - digital camera io_slave for Konqueror kcoloredit - An editor for palette files kfract - fractal generator for KDE kghostview - PostScript viewer for KDE. kiconedit - An icon editor for creating KDE icons kooka - Scanner program for KDE2 kpaint - A Simple Paint Program for KDE kruler - a screen ruler and color measurement tool for KDE ksnapshot - Screenshot application for KDE kview - A simple image viewer/converter for KDE. libkscan-dev - Scanner library for KDE (development files) libkscan1 - Scanner library for KDE Closes: 125871 125873 125956 Changes: kdegraphics (4:2.2.2-6) unstable; urgency=low . * The muzak-Christmas-carols-suck release. Alternately, the I'm-under-peer-pressure-to-give-this-a-name release, or the no-notice-NMUs-suck-donkey-balls release (hi lamont!). * Acknowledge lamont's NMU. (closes: #125871, #125956) * kamera/kioslave/kamera.cpp: - Apply patch to fix dodgy Canon camera drivers. (closes: #125873). * debian/rules: - Build with a different builddir to srcdir, thanks to Eray Ozkural. kdvi still doesn't build, though. - While I'm at it, make sure index.cache.bz2 and any other excess crap is removed. * Here's a few fixed bugs, merry Christmas. I could well be out of contact for some time, depending on my sister fixing my machine or not. If she doesn't, feel free to NMU my packages if *needed*. (Building on danish's machine now). Files: 6803357c1e14c8fc2a526505f2e352ff 140622 graphics optional kfract_2.2.2-6_m68k.deb 5e084dfe386627784488ab7ec2f2dbcf 45904 graphics optional kruler_2.2.2-6_m68k.deb 7ba741c070d2704a240f17e5d852cbe8 73978 graphics optional kcoloredit_2.2.2-6_m68k.deb 1fe792a7f5ea3ead4bec630eb374a202 90288 graphics optional kpaint_2.2.2-6_m68k.deb e70f81d45f2fa6e6cc10ba9aea8c9614 126718 graphics optional kiconedit_2.2.2-6_m68k.deb 619ba7dea495e51c93101ceec717faeb 140414 graphics optional kghostview_2.2.2-6_m68k.deb eb3fc96a2aed7fcfa24b02eb706597ec 56630 graphics optional ksnapshot_2.2.2-6_m68k.deb 49e5c303b210eafa90d9ad9b3bde899b 764436 graphics optional kview_2.2.2-6_m68k.deb 62b19473188559b0cb8b74cc120c6d3e 91736 graphics optional kamera_2.2.2-6_m68k.deb 3f22c2859bedead8789b90ee12ec2952 87412 libs optional libkscan1_2.2.2-6_m68k.deb 7b4493bc2d907826a710b1f0102ea3bd 22334 devel optional libkscan-dev_2.2.2-6_m68k.deb c61045d3642cd64373eef75899a29f45 89700 graphics optional kooka_2.2.2-6_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Rick Younie [EMAIL PROTECTED] iEYEARECAAYFAjwvuRMACgkQEycGpQPNsdKNdgCfRdUQe6/hSYgd8T3RJcj5+xlD LDMAoJ30eX9DUmFpF8PRG9wN1/VXXqDu =qcaG -END PGP SIGNATURE-
Uploaded pan 0.11.1-3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 30 Dec 2001 03:45:09 +0900 Source: pan Binary: pan Architecture: sparc Version: 0.11.1-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Takuo KITAME [EMAIL PROTECTED] Description: pan- A Newsreader uses GTK, looks like Forte Agent. Closes: 103290 Changes: pan (0.11.1-3) unstable; urgency=low . * pan/dialogs/dialog-newuser.c: - use EMAIL environment variable if it is. (closes: #103290) * po/ja.po - fix broken ja.po Files: 3d37a0b8f0473a7e9a86f65daa832da0 948058 news optional pan_0.11.1-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Luc3N2Dbz/1mRasRAglQAJ4lXo7RfcGepuCJmllq6Y6drbjAJACgvlZI o/XgMuGwdcyh6JX1bBRV6Ag= =xA30 -END PGP SIGNATURE-
Uploaded lout 3.25-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 15:01:38 +0100 Source: lout Binary: lout-doc lout Architecture: sparc Version: 3.25-1 Distribution: unstable Urgency: medium Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: J.H.M. Dassen (Ray) [EMAIL PROTECTED] Description: lout - Typesetting system, an alternative to (La)TeX. Changes: lout (3.25-1) unstable; urgency=medium . * New upstream release. Files: 47b061f5973efaec2cbf9f0dd2e202b2 1313494 text optional lout_3.25-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LucWN2Dbz/1mRasRAjMtAJ4sC1zjJxB9qacfAmFnG3nR1kPdZACcCxC0 5f7k4Y6pDBTI7jdyWdDTHq8= =imu5 -END PGP SIGNATURE-
Uploaded rus-ispell 0.99e6-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 19:26:21 +0300 Source: rus-ispell Binary: irussian Architecture: sparc Version: 0.99e6-1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Peter Novodvorsky [EMAIL PROTECTED] Description: irussian - Russian dictionary for ispell Closes: 124763 Changes: rus-ispell (0.99e6-1) unstable; urgency=low . * New upstream version. * Changed maintainer field, russian-devel list is dead it seams. * Fixed spelling error (Closes: #124763) Files: e178bd40abbac9d683402b5eb80923d7 1029684 text optional irussian_0.99e6-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD4DBQE8LudyN2Dbz/1mRasRAteCAKDy+/zgGDQHvFmfV/6KnkyLP+vwogCXf0hg 7dkMEyrkrvtRObZplnzUKw== =QVX4 -END PGP SIGNATURE-
Uploaded mp3kult 0.5-3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 20:26:41 -0200 Source: mp3kult Binary: mp3kult Architecture: sparc Version: 0.5-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Carlos Laviola [EMAIL PROTECTED] Description: mp3kult- Organizes your MP3 collection in a MySQL database Closes: 121670 125152 125641 Changes: mp3kult (0.5-3) unstable; urgency=low . * Fixed spelling mistake in the description (s/cdroms/CD-ROMs/). (Closes: #125152) * Applied a patch to make Mp3Kult build with gcc 3.0. Kudos to LaMont Jones [EMAIL PROTECTED]. (Closes: #125641) * Ok, I think I finally fixed up building on Alphas. Credits go to Steve Langasek [EMAIL PROTECTED] for that one :) (Closes: #121670) * Applied an upstream patch that fixes a bug when editing id3 tags. Files: 58e9ab45c69f6060913ed1fdded7ef9e 217166 sound optional mp3kult_0.5-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LucZN2Dbz/1mRasRAvWaAJ4+vzbtpGaeOwvrkG5oKkPYL4KcPwCff+Vb fMZXwPWD3ps/sM1WTtwN3rc= =TGYN -END PGP SIGNATURE-
Uploaded glade 0.6.2-12 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 18:25:49 -0500 Source: glade Binary: glade-gnome glade Architecture: sparc Version: 0.6.2-12 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Eric Dorland [EMAIL PROTECTED] Description: glade - GTK+ User Interface Builder glade-gnome - GTK+ User Interface Builder (with GNOME support) Closes: 126315 Changes: glade (0.6.2-12) unstable; urgency=low . * New Maintainer. (Closes: #126315) * Fix location in copyright file. * Fixed some weird formatting of depends in control file, spaces, etc. * Update the Standards-Version to 3.5.6.0. * Removed docs and added glade.docs and glade-gnome.docs, so docs will be installed in both packages. * Removed local variables from changelog. Files: e68ca57435aa4c94a12e7adc7672b3ef 1096044 devel extra glade_0.6.2-12_sparc.deb 2dbcb1c5e84ca797d2a7415486917133 1155158 devel optional glade-gnome_0.6.2-12_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Lua8N2Dbz/1mRasRAj3SAJ9eNZn0k/YqXUEk7++dfgAZan71VgCgpuS3 3f7rztl37n22eADzse0krpE= =rc9c -END PGP SIGNATURE-
Uploaded popa3d 0.5-9 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 25 Dec 2001 23:31:38 +0100 Source: popa3d Binary: popa3d Architecture: sparc Version: 0.5-9 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Description: popa3d - A tiny POP3 daemon, designed with security as the primary goal Changes: popa3d (0.5-9) unstable; urgency=low . * Support for debconf template was added (it's my first contact with debconf) so feel free raport _any_ bugs (even small) Files: 762f720fff93311498756c106bc96da8 23386 mail extra popa3d_0.5-9_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Luc6N2Dbz/1mRasRApKoAKCr2lQ9z2lyQTUX0YixL1elUPrgmACfd7+C tVX5uCBoghyuXoAGLC0RVok= =ftH2 -END PGP SIGNATURE-
Uploaded indent 2.2.7-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 19:10:04 +0100 Source: indent Binary: indent-doc indent Architecture: sparc Version: 2.2.7-1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Santiago Vila [EMAIL PROTECTED] Description: indent - C language source code formatting program Changes: indent (2.2.7-1) unstable; urgency=low . * New upstream release. * Added doc-base support. * Added support for DEB_BUILD_OPTIONS. Files: 41450056062f5272662d99767ebab33f 79362 devel optional indent_2.2.7-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LubaN2Dbz/1mRasRAghVAJwMy1rJ+C37dvo77Ohu6t1Hyhym7gCgvV+K Wa05HjIbtoa9RWP4HQXyhO4= =WBEy -END PGP SIGNATURE-
Uploaded ncbi-tools6 6.1.20011220-2 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 13:48:20 -0500 Source: ncbi-tools6 Binary: ncbi-tools6 ncbi-tools6-dbg vibrant-dev vibrant6 ncbi-tools-bin blast2 vibrant6-dbg ncbi-tools6-dev ncbi-tools-x11 Architecture: sparc Version: 6.1.20011220-2 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Aaron M. Ucko [EMAIL PROTECTED] Description: blast2 - Basic Local Alignment Search Tool ncbi-tools-bin - NCBI libraries for biology applications (text-based utilities) ncbi-tools-x11 - NCBI libraries for biology applications (X-based utilities) ncbi-tools6 - NCBI libraries for biology applications ncbi-tools6-dbg - NCBI libraries for biology applications (unstripped) ncbi-tools6-dev - NCBI libraries for biology applications (development files) vibrant-dev - NCBI libraries for graphic biology applications (development file vibrant6 - NCBI libraries for graphic biology applications vibrant6-dbg - NCBI libraries for graphic biology applications (unstripped) Changes: ncbi-tools6 (6.1.20011220-2) unstable; urgency=low . * Update manpages based on current help output. * Fix typo in description (ASN1 - ASN.1). * Use $(CC) rather than gcc in makeshlb.unx. * Build asn2asn. Files: ecf7c04f4ebdfefc83e40e92c4344984 3622342 libs optional ncbi-tools6_6.1.20011220-2_sparc.deb 0d3b827269f7a06417fac54df3a6b0be 4089330 devel optional ncbi-tools6-dev_6.1.20011220-2_sparc.deb e33e987a0ad333ec0635e5221d694c92 5688624 devel extra ncbi-tools6-dbg_6.1.20011220-2_sparc.deb 16fae7f907b5bbcfcb9123586f6b31da 176220 science optional ncbi-tools-bin_6.1.20011220-2_sparc.deb 8d78af6d8ec205d142bf9430a1352eb4 532508 science optional ncbi-tools-x11_6.1.20011220-2_sparc.deb 7b9fd2ff26b51cfe162d894b245854c5 337150 science optional blast2_6.1.20011220-2_sparc.deb 7852203442eb11f7a6c43009449a45ad 1501144 libs optional vibrant6_6.1.20011220-2_sparc.deb 4e614fe72254fc1a6eef645a083dd119 1941838 devel optional vibrant-dev_6.1.20011220-2_sparc.deb c431df6b9006c636b4765b429c0eae69 3771978 devel extra vibrant6-dbg_6.1.20011220-2_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LucgN2Dbz/1mRasRAmgHAJ0VDsKDt4bPe5TwOJhHLJiXjb90LACg27zC eofmjZDvqLpuLYhNdvnxMYw= =ZIkx -END PGP SIGNATURE-
Uploaded xfce 3.8.12b-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 00:42:25 +0300 Source: xfce Binary: xfce Architecture: sparc Version: 3.8.12b-1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Peter Novodvorsky [EMAIL PROTECTED] Description: xfce - The Cholesterol Free Desktop Environment Changes: xfce (3.8.12b-1) unstable; urgency=low . * New version. Files: 8ed7c28d2f6b47114357a979ac433d0a 3751806 x11 optional xfce_3.8.12b-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LueUN2Dbz/1mRasRAvH/AKDuEuzm4oWGizQpxpQbeJhhlLSRnACdFp/q LqZ/vjXR9WbavdKRrTOLiMA= =9pQ4 -END PGP SIGNATURE-
Uploaded sformat 3.4-3.2 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 25 Dec 2001 10:32:37 +0100 Source: sformat Binary: sformat Architecture: sparc Version: 3.4-3.2 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Gerhard Tonn [EMAIL PROTECTED] Description: sformat- SCSI disk format and repair tool Closes: 121420 Changes: sformat (3.4-3.2) unstable; urgency=low . * NMU * Add RULES/s390-linux-cc.rul and RULES/s390-linux-gcc.rul so that sformat can build on s390. (closes: Bug#121420) Files: 9448f57df88d62e7924be266fa607056 117974 utils optional sformat_3.4-3.2_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Lud/N2Dbz/1mRasRAkWUAJ91TmWAuxIU/ARGFkNdGNEKxqYH/ACfZbNd HCAeleV2awRMqQ6y0sDLsW0= =PlwP -END PGP SIGNATURE-
Uploaded xwrits 2.17-4 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 18:47:48 -0500 Source: xwrits Binary: xwrits Architecture: sparc Version: 2.17-4 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Hugo Haas [EMAIL PROTECTED] Description: xwrits - Reminds you to take a break from typing Changes: xwrits (2.17-4) unstable; urgency=low . * Moved the program out of /usr/X11R6. * Better clean rule for debian/rules. Files: 530eb6602e3766eaf5894d51ddbbac60 89612 x11 optional xwrits_2.17-4_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuedN2Dbz/1mRasRAj4YAJ4sWwLmlDNpi76zSeqtVt4dnHiQwACgolXZ U1KMPTFLgtlvkSDQZxiIOEs= =Uoga -END PGP SIGNATURE-
Uploaded gnumeric 0.99.1-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 14:15:36 +0100 Source: gnumeric Binary: gnumeric-python gnumeric gnumeric-doc Architecture: sparc Version: 0.99.1-1 Distribution: unstable Urgency: high Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: J.H.M. Dassen (Ray) [EMAIL PROTECTED] Description: gnumeric - A GNOME spreadsheet application gnumeric-python - Python plugins for the GNOME spreadsheet Closes: 126332 Changes: gnumeric (0.99.1-1) unstable; urgency=high . * New upstream release. * Python 2.2 has been released, so build against that. * Verified that links to images in the documentation are fine now that we build the docs again. (Closes: #126332) Files: 80896533b9322fa40ff851e43c30cba0 3553522 math optional gnumeric_0.99.1-1_sparc.deb e6acbeb2985fd5f5cb240d3f10274dc5 85550 math optional gnumeric-python_0.99.1-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LubJN2Dbz/1mRasRAnXcAJ0ccUTdbh5llfiZ2j5DNFBjnmgYzwCg+sU/ 9xtbVdw47ZHU86Ul0ieyaVo= =6c++ -END PGP SIGNATURE-
Uploaded hamlib 1.1.2-5 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 18:53:26 +1000 Source: hamlib Binary: hamlib1 hamlib-dev hamlib-doc hamlib-utils Architecture: sparc Version: 1.1.2-5 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Terry Dawson [EMAIL PROTECTED] Description: hamlib-dev - Development library to control radio transceivers and receivers. hamlib-doc - Documentation for the hamlib radio control library. hamlib-utils - Utilities to support the hamlib radio control library. hamlib1- Run-time library to control radio transceivers and receivers. Changes: hamlib (1.1.2-5) unstable; urgency=low . * Updated section details to prevents overrides message. Files: c2ceeb639879a58527680be8c04162e4 123074 devel optional hamlib-dev_1.1.2-5_sparc.deb fa5423c81043dade0f0e79f1b3fe0c64 136950 libs optional hamlib1_1.1.2-5_sparc.deb dc774385233574e01a07f5a920370d57 28618 hamradio optional hamlib-utils_1.1.2-5_sparc.deb 8b2a4b8332281c97f8a19ca96f472d13 54580 doc optional hamlib-doc_1.1.2-5_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LubSN2Dbz/1mRasRAjMFAKCNlcLOAj2eVaSNh37unfN8qWuF6QCg401E UVRKVYCSvTKeJ6F9PTN2LUg= =KpTN -END PGP SIGNATURE-
Uploaded netclient 0.3-OCaml3.04-2 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 08:44:07 +0100 Source: netclient Binary: ocaml-netclient Architecture: sparc Version: 0.3-OCaml3.04-2 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Stefano Zacchiroli [EMAIL PROTECTED] Description: ocaml-netclient - OCaml library that implement a HTTP/1.1 client Changes: netclient (0.3-OCaml3.04-2) unstable; urgency=low . * Bugfix: now build depends require that ocaml-xstr was compiled with ocaml 3.04 Files: 5205b8dedefcc26d6d224dc390c14ce3 181244 devel optional ocaml-netclient_0.3-OCaml3.04-2_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD4DBQE8LucoN2Dbz/1mRasRAkfQAJjGbEHEhiUi3fhq4zhDXCU0THVXAKDY6zo/ qOKPy+rTeYicPoF/F1cJ9g== =r3Z1 -END PGP SIGNATURE-
Uploaded cooledit 3.17.1-3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 14:25:27 + Source: cooledit Binary: cooledit coolicon libcw smalledit coolman libcw-dev Architecture: sparc Version: 3.17.1-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Mark Brown [EMAIL PROTECTED] Description: cooledit - A portable, fast X Window text editor with beautiful 3D widgets. coolicon - Displays pixmap (.XPM) files as icons on the desktop. coolman- Man page viewer using the Cool Widget library. libcw - The Cool widget library used by cooledit/coolicon/coolman. libcw-dev - The Cool widget library (header files) smalledit - Stripped down version of Cooledit. Closes: 123015 Changes: cooledit (3.17.1-3) unstable; urgency=low . * Apply patch from Aaron Schrab [EMAIL PROTECTED] fixing crash on startup on PowerPC (closes: #123015). * Change maintainer to [EMAIL PROTECTED] Files: b42bfd5bf9fa5bb68f20d6851e2b0ee6 588546 libs optional libcw_3.17.1-3_sparc.deb bd42f4b2b08a782cc0118cadc74ebbd1 32638 devel optional libcw-dev_3.17.1-3_sparc.deb 9f038399dd558ce1aadf65bf3085c479 366278 editors optional cooledit_3.17.1-3_sparc.deb 0687bd1e583e4ea324f82419a1b1d41e 98984 x11 optional coolicon_3.17.1-3_sparc.deb 9d503140c29391872f10756a44e18e8f 17640 doc optional coolman_3.17.1-3_sparc.deb eb4a8c7911b59fb3bcd53b43ec13f6cb 23850 editors optional smalledit_3.17.1-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuanN2Dbz/1mRasRAhtZAJ9kEfK9aYfrEC6EA2f5tJ4kDTHAngCfVS9N 8OR/D9DOd5o+xFetlxzTgBU= =gaGq -END PGP SIGNATURE-
Uploaded camserv 0.42-8 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 11:00:18 -0700 Source: camserv Binary: libcamserv-dev camserv-relay libcamserv0 camserv Architecture: sparc Version: 0.42-8 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Barak Pearlmutter [EMAIL PROTECTED] Description: camserv- stream video out onto the web camserv-relay - relay camserv streaming video libcamserv-dev - camserv libraries, development files libcamserv0 - camserv shared libraries Closes: 126680 126690 Changes: camserv (0.42-8) unstable; urgency=low . * Put limits on autobright brightness range (closes: #126690) * Mechanism to send log messages to stderr (closes: #126680) Files: 9e9f81f880773f3a6c83052fe7a088b2 50252 web extra camserv_0.42-8_sparc.deb 939b8436a0a6b2b4019633d619d82a88 26988 web extra camserv-relay_0.42-8_sparc.deb 0d1531f16338926277bc6e3ea8bd0248 43832 libs extra libcamserv0_0.42-8_sparc.deb de328f088c00f703920209ea549d9443 54364 devel extra libcamserv-dev_0.42-8_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuabN2Dbz/1mRasRAo6/AJ95wBc7p60r9IJXOLrcT2qce7u6zwCbBKxs kCUamdnX3iZ3E29MaVBv5j4= =+6/s -END PGP SIGNATURE-
Uploaded python-reportlab 1.11-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 13:02:48 +0100 Source: python-reportlab Binary: python-reportlab Architecture: sparc Version: 1.11-1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Gregor Hoffleit [EMAIL PROTECTED] Description: python-reportlab - ReportLab library to create PDF documents using Python Changes: python-reportlab (1.11-1) unstable; urgency=low . * New upstream version. * Correct a spelling mistake in package description (cloeses: #125284). Files: 2ac3053dea1fb0077e187f92e1a942fa 2058880 text optional python-reportlab_1.11-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LudSN2Dbz/1mRasRApRyAJ40lnrb1HwdpkHWSHDJ0nl0EJNJbACfQE47 eyMSXCeUFajOQcBfR51OZ5o= =en3Z -END PGP SIGNATURE-
Uploaded asclassic 1.1b-24 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 30 Dec 2001 01:06:15 +0900 Source: asclassic Binary: asclassic Architecture: sparc Version: 1.1b-24 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Taketoshi Sano [EMAIL PROTECTED] Description: asclassic - X11 window manager, AfterStep Classic (forked from v1.1) Closes: 118533 118535 Changes: asclassic (1.1b-24) unstable; urgency=low . * Fix a typo in sample.steprc. Thanks to the reporter, Bill Allombert. (Closes: #118535) * update sample.steprc and menu-methods. I don't know if this is right solution or not, but it seems to work. I planed to implement raw_include keyword into asclassic, but it might be overkill... (Closes: #118533) Files: cf21211b70f0fbf5848db6e1f7f1a4ec 543360 x11 optional asclassic_1.1b-24_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuaVN2Dbz/1mRasRAoqRAJ0aZ5Kyx7qtMKTZZaQlqj8pM/2QTgCfYNGX wFQVW67KWKtiT9RMH6Vgu/w= =X3yV -END PGP SIGNATURE-
Uploaded roy 1.0.1-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 12:16:55 -0800 Source: roy Binary: libroy-dev libroy0 Architecture: sparc Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Brian Bassett [EMAIL PROTECTED] Description: libroy-dev - Utility and data structure library (development files) libroy0- Utility and data structure library (runtime files) Closes: 126715 Changes: roy (1.0.1-1) unstable; urgency=low . * New upstream version. + Fixes problems with gcc3 compilation (closes: #126715) Files: 35097ce99cd5e707a0c7efa3cf90db0f 170386 devel optional libroy-dev_1.0.1-1_sparc.deb 674d75c2f4c6a9a416523e5f5c8a168b 24228 libs optional libroy0_1.0.1-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LudrN2Dbz/1mRasRAoxmAJ0dEEfjG/RQSJ+pEgOXJkmkxHpNawCgtSa+ wDB0IGjaopXXprs22sGoMzQ= =iJp1 -END PGP SIGNATURE-
Uploaded gnomeicu 0.98-3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 22:07:20 +0900 Source: gnomeicu Binary: gnomeicu Architecture: sparc Version: 0.98-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Takuo KITAME [EMAIL PROTECTED] Description: gnomeicu - Small, fast and functional clone of Mirabilis' ICQ Closes: 126838 Changes: gnomeicu (0.98-3) unstable; urgency=low . * src/v7send.c: convert kanji string to SJIS when option is enabled. (closes: #126838) Files: daf6059f58d49c0a030361178899882f 281038 net optional gnomeicu_0.98-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LubCN2Dbz/1mRasRAlnXAKC5CgyWmuqzFmkmiQr3wwFbuVJ/WgCgoYlH ehugetVhDQe11DF0Cm0Fidw= =ijpa -END PGP SIGNATURE-
Uploaded catdoc 0.91.4-7 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 18:59:41 +0300 Source: catdoc Binary: catdoc Architecture: sparc Version: 0.91.4-7 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Peter Novodvorsky [EMAIL PROTECTED] Description: catdoc - MS-Word to TeX or plain text converter Closes: 104103 124050 Changes: catdoc (0.91.4-7) unstable; urgency=low . * Fixed problem on powerpc (Closes: #104103) * Fixed package desctiption (Closes: #124050) Files: 2c483f86e790f094af0dac73407a0d6f 69148 text optional catdoc_0.91.4-7_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuaeN2Dbz/1mRasRAp48AJ90S+pdn5G7UhzN5IEZKsybmaY5DACfV39l PXZ4ELYsoSVHiuqVAj9232k= =FFal -END PGP SIGNATURE-
Uploaded qt-embedded-free 3.0.1-3 (all sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 00:40:00 -0700 Source: qt-embedded-free Binary: libqt3-emb-dev qt3-emb-doc libqt3-emb Architecture: all sparc Version: 3.0.1-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Ivan E. Moore II [EMAIL PROTECTED] Description: libqt3-emb - Qt-Embedded GUI Library (runtime version). libqt3-emb-dev - Qt-Embedded GUI development headers, static libraries qt3-emb-doc - Tutorial and reference documentation and examples for Qt-Embedded Closes: 126704 Changes: qt-embedded-free (3.0.1-3) unstable; urgency=low . * Build with -function-sections (Closes: #126704) Files: 3de7f7d89a9dcefc49c89f9e0ad13373 7177410 libs optional libqt3-emb_3.0.1-3_sparc.deb 18caa03c9c1e65778bedfe91b8c4a596 3634890 devel optional libqt3-emb-dev_3.0.1-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LudeN2Dbz/1mRasRAqcsAKC5HGtLAFwE+JbynEPiFn7e8pJosgCfepRB GKVdtqVYLGlLAYzHhHqgShY= =f+7c -END PGP SIGNATURE-
Uploaded qt-x11 2.3.1-18 (sparc all) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 27 Dec 2001 00:15:00 -0700 Source: qt-x11 Binary: uic libqt-gl-dev libqt2-gl libqutil1 libqt2-mt libqt2 qt-doc qt-designer libqt-dev qt-designer-doc libqt-mt-dev Architecture: sparc all Version: 3:2.3.1-18 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Ivan E. Moore II [EMAIL PROTECTED] Description: libqt-dev - Qt GUI development headers, static libraries libqt-gl-dev - Qt GUI development libraries for GL version libqt-mt-dev - Qt GUI development headers, static libraries (Threaded version) libqt2 - Qt GUI Library (runtime version). libqt2-gl - Qt GUI Library (GL version). libqt2-mt - Qt GUI Library (runtime threaded version). libqutil1 - Qt Util Library qt-designer - Qt GUI Designer qt-designer-doc - Tutorial and reference documentation for Qt Designer qt-doc - Tutorial and reference documentation and examples for Qt. uic- Qt ui compiler Changes: qt-x11 (3:2.3.1-18) unstable; urgency=low . * Build with new png libraries. * Update Build-Depends Files: a32c844c0089deb6692460fd390dd926 1920586 libs optional libqt2_2.3.1-18_sparc.deb 16ca8625fd0e6b340208f40fa4fe14dc 1926552 libs optional libqt2-mt_2.3.1-18_sparc.deb 1bae55802ed63e3471c08b117782f535 2550274 devel optional libqt-mt-dev_2.3.1-18_sparc.deb 44cb37ec91bfe2a1afec1bf5b8b0c816 1948004 libs optional libqt2-gl_2.3.1-18_sparc.deb 850775aaa8feb84362204ae8f48af8e3 2561102 devel optional libqt-gl-dev_2.3.1-18_sparc.deb 123c32d07ab863379722c176c03fe818 2951418 devel optional libqt-dev_2.3.1-18_sparc.deb cb0430915a9948d57d438872e7938e31 696826 devel optional qt-designer_2.3.1-18_sparc.deb b23579dc459248017217e57bc174971d 28048 libs optional libqutil1_2.3.1-18_sparc.deb cc2e162bd8fe35342ae4c8ed2d98af96 85730 devel optional uic_2.3.1-18_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LudiN2Dbz/1mRasRAvVqAJ0edgzmzDl7JMDfADp5BixmEO0wcwCgwDBF HDKGAsdIRWvfWcJYuNFlY/8= =LTFk -END PGP SIGNATURE-
Uploaded cvsgraph 1.1.2-3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 17 Dec 2001 23:29:51 + Source: cvsgraph Binary: cvsgraph Architecture: sparc Version: 1.1.2-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Jon Middleton [EMAIL PROTECTED] Description: cvsgraph - Create a tree of revisions/branches from a CVS/RCS file. Closes: 119646 124530 Changes: cvsgraph (1.1.2-3) unstable; urgency=low . * Fixed spelling error in Description. (Closes: #119646, #124530) Files: cdfdd4562a031fa93f492ed28aca252c 55152 devel optional cvsgraph_1.1.2-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD4DBQE8LuawN2Dbz/1mRasRAm8pAKDYxBcNml9Pi6LkKrsBTNPc+q5rcACTBrZm mmrT/QALyUzlVaCMc2hTjg== =XpxV -END PGP SIGNATURE-
Uploaded libregexx 0.96-3 (sparc all) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 23:19:27 -0500 Source: libregexx Binary: libregexx-examples libregexx0 libregexx-dev Architecture: sparc all Version: 0.96-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Benoit Joly [EMAIL PROTECTED] Description: libregexx-dev - C++ wrapper to the GNU regex functions libregexx-examples - C++ wrapper to the GNU regex functions libregexx0 - C++ wrapper to the GNU regex functions Closes: 81011 Changes: libregexx (0.96-3) unstable; urgency=low . * Headers removed from libregexx0. (closes: #81011). * Removed headers from /usr/include/regexx/* since they are in /usr/include/ . (closes #111034). Files: a8c6ce02f9af4ec36f2d650c82bc4cd9 33636 libs optional libregexx0_0.96-3_sparc.deb 0718aac41669080d2ea5c2e467ee16c7 28214 libs optional libregexx-dev_0.96-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LucKN2Dbz/1mRasRAmHQAJ49TqinhpeRxGvxh3pNMf4wYLRkjgCdG4gN 84fl2p3zEzXoAZ4e/wwAQgI= =QzTs -END PGP SIGNATURE-
Uploaded amphetamine 0.8.9-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 16:07:28 -0500 Source: amphetamine Binary: amphetamine Architecture: sparc Version: 0.8.9-1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: amphetamine - Exciting Jump'n run game that offers some unique visual effects Changes: amphetamine (0.8.9-1) unstable; urgency=low . * New upstream release. * Hacked File.hpp to probe for endianness sys/params.h. Pity this program does not use autoconf. * Look for data file in /usr/share, not /usr/lib Files: 2ce98b38bb303395de789f50513f676a 85896 games optional amphetamine_0.8.9-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuaMN2Dbz/1mRasRAnxMAKDzQaTF/I7CMpemTemZyE/jvQxBsgCfcKlA iE+j9JVf6O/LzUAY4K51isE= =HeHy -END PGP SIGNATURE-
Uploaded synaptic 0.16-5 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 23:16:42 +0100 Source: synaptic Binary: synaptic Architecture: sparc Version: 0.16-5 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Michael Vogt [EMAIL PROTECTED] Description: synaptic - GUI-frontend for APT Closes: 126771 Changes: synaptic (0.16-5) unstable; urgency=low . * applied patch from LaMont Jones [EMAIL PROTECTED] to make synaptic compile on hppa (g++-3.0) (closes: #126771) Files: 01fb3d29f4f68eaef08a35ff98094bba 225740 admin optional synaptic_0.16-5_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LueLN2Dbz/1mRasRAiqBAJ49p2ivelWmWjzwvCiJv7KuOs09uQCg4oAE rkS9ZGe9UwdlNDq6CcpM7mQ= =9MYA -END PGP SIGNATURE-
Uploaded bsdgames 2.13-1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 18:15:41 -0500 Source: bsdgames Binary: bsdgames Architecture: sparc Version: 2.13-1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Joey Hess [EMAIL PROTECTED] Description: bsdgames - collection of text games from BSD systems Changes: bsdgames (2.13-1) unstable; urgency=low . * New upstream release. * Patched sail/sync.c to build (lots of missing includes and other trivial mistakes). Files: f1d065694138eaa03755d272303b2d0a 860962 games optional bsdgames_2.13-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuaYN2Dbz/1mRasRAijTAKCcoHGPEl4kESMMgblspuUdFf8W7ACfbA7V FvhO3SgpQxw0wxXIME+Cze0= =t0gy -END PGP SIGNATURE-
Uploaded cdrtools 1.10-2.3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 20:42:14 -0500 Source: cdrtools Binary: cdrecord-dev cdrecord cdda2wav mkisofs Architecture: sparc Version: 4:1.10-2.3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Colin Walters [EMAIL PROTECTED] Description: cdda2wav - Creates WAV files from audio CDs cdrecord - A command line CD/DVD writing tool cdrecord-dev - The libschily SCSI user level transport library mkisofs- Creates ISO-9660 CD-ROM filesystem images. Closes: 108700 126266 126682 Changes: cdrtools (4:1.10-2.3) unstable; urgency=low . * NMU * debian/cdrecord.postinst: - Redirect output of dpkg-statoverride to /dev/null (Closes: #126682) * mkisofs/mkisofs.8: - Fix minor manpage error (Closes: #108700) * cdrecord/cdrecord.1: - Fix minor manpage error (Closes: #126266) Files: 3b03de75951f6a84b0fd0f196f372efa 312134 otherosfs optional cdrecord_1.10-2.3_sparc.deb e0a88efe3f95a112ce8f921295ec0174 141240 devel optional cdrecord-dev_1.10-2.3_sparc.deb 37e9556df1623f9bcef1c35ee9247b41 387920 otherosfs optional mkisofs_1.10-2.3_sparc.deb 45b441a1ef31c319841a7f454b01a468 118724 sound optional cdda2wav_1.10-2.3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LuaiN2Dbz/1mRasRAswcAJ443dS3Vi7eMlHD5k9BE3Bh6ncKrgCgtBbm XiePCrlAyMIPJ7pGuIBMRxc= =IdT/ -END PGP SIGNATURE-
Uploaded oaf 0.6.7-3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 30 Dec 2001 01:36:50 +0900 Source: oaf Binary: oaf liboaf0 liboaf-dev Architecture: sparc Version: 0.6.7-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Takuo KITAME [EMAIL PROTECTED] Description: liboaf-dev - The GNOME Object Activation Framework - development files. liboaf0- The GNOME Object Activation Framework. oaf- The GNOME Object Activation Framework. Closes: 112269 Changes: oaf (0.6.7-3) unstable; urgency=low . * oaf-config.in: remove -I/usr/include when prefix is '/usr' (closes: #112269) Files: e43a340350347143d1ddec15a6e71d5e 114544 libs optional oaf_0.6.7-3_sparc.deb 61eff9af3ae40480886441627524735e 65242 libs optional liboaf0_0.6.7-3_sparc.deb 52feb0efd24ae4f9510504b5767db9e2 85182 devel optional liboaf-dev_0.6.7-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LucvN2Dbz/1mRasRAjdrAKDM3AupTuBHr8xSwE+4SXU96pw1UwCg0+bh nEngBKQKb1vXFPb4aS2JTAo= =OWTc -END PGP SIGNATURE-
Uploaded sudo 1.6.3p7-5 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 11:21:43 -0700 Source: sudo Binary: sudo Architecture: sparc Version: 1.6.3p7-5 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Bdale Garbee [EMAIL PROTECTED] Description: sudo - Provides limited super user privileges to specific users. Closes: 126847 126872 Changes: sudo (1.6.3p7-5) unstable; urgency=low . * only touch /var/run/sudo/* if /var/run/sudo is there, closes: #126872 * fix spelling error in init.d, closes: #126847 Files: d1388746aae4daf9c02ff96fef1348fe 132334 admin optional sudo_1.6.3p7-5_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LueHN2Dbz/1mRasRAihDAJ0WZ56LSVQa0c1k0RbNmS7EprQXrACgqYeE aZJSdHcxZAwUrH9hMHrVYYw= =0fiO -END PGP SIGNATURE-
Uploaded lirc-xmms-plugin 1.2-3 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Dec 2001 15:07:16 +0100 Source: lirc-xmms-plugin Binary: xmms-lirc Architecture: sparc Version: 1.2-3 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: Christian Marillat [EMAIL PROTECTED] Description: xmms-lirc - Linux Infrared Remote Control for XMMS Changes: lirc-xmms-plugin (1.2-3) unstable; urgency=low . * debian/control Change my e-mail address by the debian address Files: 3c1f73f7ebcf2fa12a26c9ec401799d1 19922 sound extra xmms-lirc_1.2-3_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8LugqN2Dbz/1mRasRAkkSAJ94n78vj/iefCSLYPebGDb+p6ydDQCghBMU HoKaaXQ6guIGgXE+fQv0uAA= =aIqQ -END PGP SIGNATURE-
Uploaded gkrellm-reminder 0.3.4-1.1 (sparc) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Dec 2001 18:53:24 -0700 Source: gkrellm-reminder Binary: gkrellm-reminder Architecture: sparc Version: 0.3.4-1.1 Distribution: unstable Urgency: low Maintainer: Debian/sparc Build Daemon [EMAIL PROTECTED] Changed-By: LaMont Jones [EMAIL PROTECTED] Description: gkrellm-reminder - a useful reminder plugin for gkrellm Closes: 126020 Changes: gkrellm-reminder (0.3.4-1.1) unstable; urgency=low . * NMU * Fix missing build-depends: gkrellm. * Fix rules to install correctly. Closes: #126020 Files: 88d98d857f48c7d576cc91d53cee3456 30668 x11 optional gkrellm-reminder_0.3.4-1.1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8L2kaN2Dbz/1mRasRAnasAKCQaA5BA9+ohCw4Wpfays9XM/wuQwCfc52f xCeG3GdjZFXxWKNznVemoak= =0AJI -END PGP SIGNATURE-
Re: Bug#126967: ITP: pnet -- Portable .NET C# compiler runtime
On Sat, 2001-12-29 at 23:23, Andrew Mitchell wrote: * Package name: pnet Hmm. This is a rather undescriptive name. How about something like dotgnu-pnet, or dotgnu-dotnet, dotgnu-net, or even dotgnu-portable-net?
Bug#126989: ITP: filemenu-applet -- A directory navigation GNOME applet.
Package: wnpp Version: N/A; reported 2001-12-30 Severity: wishlist * Package name: filemenu-applet Version : 0.3 Upstream Author : Benjamin Kahn [EMAIL PROTECTED] * URL : http://www.zoned.net:8000/~xkahn/file_menu_applet/ * License : GPL Description : A directory navigation GNOME applet. I intent to package this program. I plan to do some work on enhancing it... adding gettext support and stuff here's my package's description: File Menu Applet is a small GNOME panel application which creates a file manager. File Menu Applet is not designed to replace your existing file manager, but instead work with it. It supports standard drag and drop, GNOME file types, and Nautilus icons. . One may use it for small tasks such a easily attaching files to emails in Evolution or Sylpheed by dragging them out of File Menu Applet into the composer window. It's also excellent for selecting songs to play from your MP3 or OGG collection. I'll put the work I've done so far on: deb http://people.debian.org/~kov/debian unstable/ deb-src http://people.debian.org/~kov/debian unstable/ Notice that the packages doesn't have build-deps and other stuff yet... I'm going to bed now and will finish the packages when I wake up... []s! -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux couve 2.4.16 #1 Qua Dez 26 23:53:25 BRST 2001 i586 Locale: LANG=pt_BR, LC_CTYPE=pt_BR
help with lftp
Hi, Could someone with experience with po file translation look at NMUing lftp? It is way behind in upstream versions (which will fix bug #116068). The maintainer added a lot of translations to the 2.4.1 release, and the Debian diff no longer applies cleanly at all. I think a lot of these translations have been updated upstream. The conflicts are primarily in es and pt_BR translations, so someone speaking those languages would be ideal for fixing this.
PUBLIC GPG KEY REVOCATION FOR DAVID DOWNEY
Hey folks, Forgive the email. I had an accident on my machine which wiped out my gpg keyring. Unfortuantely I had not had time to back up the ring, thus the gpg key I've been using is completely lost. I have since made a new key. the **correct** gpg key is as follows pub 1024D/42D8F306 2001-12-30 David D.W. Downey (pgpkeys) [EMAIL PROTECTED] sub 2048g/6A9DD29F 2001-12-30 [expires: 2002-12-30] -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDwux3MRBADny+tu35ShkaTTdUd/eIlrJNx3bhL+qIFz6M15yI4hyXiFnhXV s3E8yJH0Gkaafz3xLxNAOrQRyglwAiqjYey/RoB7uPR7y4D2iXv6P+GOvd4BRjfT uDZo4Qw4Vo6TzuQaY3ykdfFzUBj1BnkqoKpp6fMlowBLzNAhHRC3OkzyawCglBkf JgLKBy2YoSp6TCw8gTWpO28EAImWQkz9RTyoY7y+tLIubErQfdJPr7erGFciJTxA lvITihx9WDEESq7kCCRdQfoVttsDQU0mbOC+3wef2OcenIoTcEAgUEjGPeIlg+06 mTc9HFlcFc7mx2gpXBc1sEC+jU6xA1/Ynza/kh0rUF0JQ5UBBaftYGFLmgUmu4xf LiBWBACffcs1ktKhbkBu9e+SAS5gjNael8TNkIPqLZ98j9Dxbc21DQei9rrIYXFV eLVQkws0SB1VdEMCEJ+saE9rWxr4ceYawc4xrRLxcB6oUb0CX3+nxRkbdXoVrHsM w+yi6rVqlq9ifNBluF7IGOoZcMje+qPwzUUpQ3iu0kCEtkWlq7Q7RGF2aWQgRC5X LiBEb3duZXkgKCJwZ3BrZXlzIikgPGRhdmlkLWRvd25leUBjb2RlY2FzdGxlLmNv bT6IXQQTEQIAHQUCPC7HcwUJAeEzgAULBwoDBAMVAwIDFgIBAheAAAoJEOq17FpC 2PMGJxcAn1RYl2OM1KQbzwJkmvrordgdF3NwAJ9HTw54cwb2ARhq5PtRsJlxYkPa +7kCDQQ8LsfLEAgAkAa9MiVCb6nOp96zYvBNJXZghuDu4ZEEXGmLXJ+dn5dl3ORZ QtMKFh3KdKClu4kJIsishS+6bfykgHJZAsMcLxyeuXN4uNJOc05/Iew0m6C/OHF5 2HCJt5jJfPQcEYapzWi5q0GmuC1ZxnQ/weqvws9gAo3GDtQ2TPDbrl7Twt8ebBIj Za4GUtVHSLuwMMGwzsn0LTA4doGAduiZn5cgag12Wc5gx+MPacZYxT3WZsfxiWwr HsA9QL0Z8IZWNq4CWiifesykwoDQ3P10g6m3VG1jHLrMkb2DHWFVvKxdHx7Q3DHH o9ucitppsVIAgD+01pd50SGrcv23qcGi3lez9wADBwf/awCb6y6FHyS3sj7KeXtd 6o5h0gw4cFcH8a61yCzs53invS5GVavXICZj47AR3/fAMk6TTFZcKttJW9LAunss DphPstXxhovXAZ4yJNcL7Kxf2JO+xWwKUEmnmFfuSrtQryrfLZdrc8C84ZpmPeGm 4E1bKwpTYLPWoCa9a4UWWzJaIitBlwbByVvcVZICIq+A4u02SirkIi1JwKe192hw ztjlOxUtCpS3T6RhTSZg6TIMFVJ6BaDUiWkHRo5iXPM4tvIIM16YbkAlSd+xsVfw 4/Akq4pNMlgpO/ipkfkgoWhKzf2Dp6Wi19TKNNBmc+5vGeaCxbihOpsvd4yIRrHa j4hMBBgRAgAMBQI8LsfLBQkB4TOAAAoJEOq17FpC2PMG/asAnj7oWXfYYTAWsncs 6TYJry2HHNSHAJkBACXbG0uzEAc5SbrrS1Mde3zr9A== =ZVsY -END PGP PUBLIC KEY BLOCK- pgpE8M3wFu3RZ.pgp Description: PGP signature
Re: NMU sclient
On Sat, Dec 29, 2001 at 07:23:13PM -0800, Ian Eure wrote: hi there. i've prepared a NMU for sclient, which fixes it's two outstanding bugs. upstream seems to be dead, the last release was in 1999. maintainer seems to be mia. any objections? Last seen more than 1 year ago at people.d.o. Maybe a proposal of adoption could be done... He mntns that pkg only. -- Francesco P. Lovergine
Re: my.debian.org
On Sat, Dec 29, 2001 at 12:00:14PM +0100, Martin Michlmayr wrote: * Stefano Zacchiroli [EMAIL PROTECTED] [20011229 11:32]: BTW, why madison isn't packaged? We could package it and mention it in the developer reference. Because the tool requires the SQL database on pandora and auric. Cool, anyway I see that madison use postgresql, so just a few command line switch that specify the db host, the port and eventually username and password. In such a way it can be used by developers using ssh tunneling or something similar. Personally I have a slow connection (standard 56K modem) and I really prefer using it with ssh tunneling rather than on an interactive ssh session. Cheers. -- Stefano Zack Zacchiroli [EMAIL PROTECTED] ICQ# 33538863 Home Page: http://www.cs.unibo.it/~zacchiro Undergraduate student of Computer Science @ University of Bologna, Italy - Information wants to be Open - pgpelirFqk7ia.pgp Description: PGP signature
Re: WARNING: Jack Howarth is an agent of destruction
On Sat, Dec 29, 2001 at 22:40:07 +0100, Anders Jackson wrote: Michael Stone [EMAIL PROTECTED] writes: Aren't the brits complaining about the US wanting to execute terrorists, because of conflicts with EU declaration of human rights? (This is of toppic, isn't it) Quite, but still I like a chance to clean up some confusion. Isn't it UN declaration of human rights, not EUs. The Universal Declaration of Human Rights (1948) is the UN's. http://www.un.org/Overview/rights.html I guess Michael is referring to the Council of Rome's Convention for Protection of Human Rights and Fundamental Freedoms (1950 and later amended; protocol 6 dealing with the death penalty) http://www.echr.coe.int/Convention/webConvenENG.pdf which established the European Court of Human Rights http://www.echr.coe.int/ which isn't an EU institution, but a Council of Europe one and whose jurisdiction is therefore recognised by a lot more states than just EU members: http://www.coe.int/T/E/Communication_and_Research/Public_Relations/About_Council_of_Europe/CoE_Map__Members/ ) Ray -- Hacker and proud.
Re: Preparing a Proposal: 3 DD needed for every NEW package
Hi Raphael! You wrote: The basic goal is that someone still gets the bug reports if the main maintainer disappears. As those people would get the bug logs, they'd notice that the main maintainer never responds and could decide to take it over. Well, if that's all you want, there's a much easier (and less bureaucratic) solution: just keep an official list of MIA maintainers, based on replies to bug reports, uploads of packages, closing of bugs, etc, and post it to d-d-announce or d-private regularily. I even think such a list has already been made, but it would be nice if it could be done on a per-package basis. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: Preparing a Proposal: 3 DD needed for every NEW package
Add also that packages can reach their End-Of-Life time. Assuming the package has no real bugs (that is, it is still usable with the bugs it has), when will it reach its end-of-life time? I would say it only reaches it when no one uses it any more. As long as there is even a single user, the package is alive. This is again one of Debian's advantages: you still have that old good software packaged in the official distribution although it is no longer fancy and sexy. SuSE, for example, does not have, which is bad. (No offence to SuSE, but I have not touched any other distribution than Debian and SuSE for a couple of years.) I do not think there is any reason to remove such packages. We should, and I think this is what the original posting did, discuss packages which have important bugs AND are poorly maintained (i.e. important bugs not being fixed or upstream not followed) or abandoned (i.e. the maintainer is mia or upstream has abandoned it). If the package is still usable, there is no reason to remove it. Adding a field like Deprecated: Rather use package-X or putting them in Extra could help people to find alternatives if they do not want these oldies. So, no more upstream maintainer(s), no more active development and more valid alternatives to them. This is unfortunately true for so much pkgs. This is exactly what I want to oppose. If a package is no longer developed, what is wrong with it? I suppose ls or rm have not been developed for a while but are still very useful. (I admit, they are not packages, but they are valid examples: even though the programs are old and not very much developed lately, they are still being used! This is even more true for packages used in scientific research: they are very often developed for a single research group and packaged just in case someone else wants to use them, too. They do what they were designed to do, but are no longer developed. It would be a shame if these were dropped. Having a lot (of packages) to choose from is a priviledge of Debian users - let us stick to that. You do not need to install packages you do not intend to use - if you do not know what some old package is for, why install it at all? -- --- | Juha Jäykkä, [EMAIL PROTECTED]| | home: http://www.utu.fi/~juolja/ | ---
Re: Preparing a Proposal: 3 DD needed for every NEW package
This doesn't sound too bad to me, _but_ a better report might be to set up some sort of automatic system that sends out email to all maintainers at 1 month intervals [or something like that]. If someone doesn't respond to 2 or 3, then they are marked inactive and someone, preferable a human, verifies that the maintainer is not active anymore and orphans all of his/her packages... This would eliminate the unmaintained problem... This could be nice... I might even volunteer for setting up something like that - given the authority, of course: orphaning other people's packages must be done responsibly... This email that would be sent would be bug-list (or a subset thereof), right? A simple Are you alive? Would be quite annoying... Of course, a bug-list once a month would be annoying to active developers, too. Would it be possible to exclude from getting the email those maintainers who have uploaded a new version during the last, say, 3 months? This, of course, would still unnecessarily burden maintainers of packages which are more or less dead upstream and do not have any (important) bugs... We do not want to annoy maintainers, either... Of course, skipping maintainers of packages with no important bugs could help, too. This would be easy to implement, too. As for unused packages, it is a very subjective thing :) Something like iraf might now be used by many but it is still needed by some.. Removing stuff like this turns Debian into RedHat - no one wants that. I agree to that, 100%. -- --- | Juha Jäykkä, [EMAIL PROTECTED]| | home: http://www.utu.fi/~juolja/ | ---
Re: Preparing a Proposal: 3 DD needed for every NEW package
* Thomas Bushnell, BSG [EMAIL PROTECTED] [20011229 12:59]: We orphan ALL his packages, we get to know he is MIA and will not Oh, I think orphaning his packages can be a useful thing to do. But I just don't see why explicitly punting him helps. For the record, please note that while quite a few packages of inactive developers have been orphaned already, no one has been asked to leave the project for their inactivity (An inactive developer without any packages doesn't do any harm anyway, and he might become active again). -- Martin Michlmayr [EMAIL PROTECTED]
Re: Preparing a Proposal: 3 DD needed for every NEW package
maintainers' was: send him a notice that he'll be removed if he won't take care of his packages/other tasks for foo more days, if he does not answer or tell us he's giving up his key is removed from the keyring I agree to this. The obvious problem would be who does this... ;) I do not actually know, but it seems like it would need to be someone with the authority to remove keys from the keyring. Who are they? I suppose they are persons who are well known, respected by the community - and overworked... What I am really most afraid of, is lack of decision. This certainly looks like something that must be tackled but in too many cases in volunteer organisations, the decisions needed are never made. Sometimes because of lack of people who dare to make them, sometimes because of internal power struggles and sometimes because no one really knows who has the authority to make them. I really wish this does not happen here. I do not mean this happens with Debian - I do not have enough insight to know that but heck, it even happened in the firm I used to work at! And that was really stupid: everything should have gone smoothly. None of the problems I described existed but still nothing happened for 1.5 years (at which point I got tired and quit - I think nothing has happened even now, 1.5 years after I quit). -- --- | Juha Jäykkä, [EMAIL PROTECTED]| | home: http://www.utu.fi/~juolja/ | ---
Bug#127037: ITP: Scorched Island 3D - a 3d clone of scorched earth
Package: wnpp Severity: wishlist Package name : si3d Upstream Author: ANte Brkic. [EMAIL PROTECTED] URL: http://cvs.linux.hr/si3d/ License: GPL version 2 Scorched Island 3D is a clone of popular dos game called Scorched Earth, but this one is in three dimensions. It is a game where you try to shoot your opponent over the hill with different weapons and such (very similar to Worms too) (from the website) --
Counting potatoes: the size of Debian 2.2
Hi, Maybe some of you could be interested in having a look at a paper we have just made public: Counting potatoes: the size of Debian 2.2. This is an excerpt of the abstract: [...] we use David A. Wheeler's sloccount system to determine the number of physical source lines of code (SLOC) of Debian 2.2 (aka potato). We show that Debian 2.2 includes more than 55,000,000 physical SLOC (almost twice than Red Hat 7.1, released about 8 months later), showing that the Debian development model (based on the work of a large group of voluntary developers spread around the world) is at least as capable as other development methods [...] It is also shown that if Debian had been developed using traditional proprietary methods, the COCOMO model estimates that its cost would be close to $1.9 billion USD to develop Debian 2.2. In addition, we offer both an analysis of the programming languages used in the distribution (C amounts for about 70%, C++ for about 10%, LISP and Shell are around 5%, with many others to follow), and the largest packages (Mozilla, the Linux kernel, PM3, XFree86, etc.) The paper is available online at my Debian home page, http://people.debian.org/~jgb/debian-counting A sligthly older version has also been published online, in Upgrade Magazine, http://upgrade-cepis.org/issues/2001/6/up2-6Gonzalez.pdf There are also available translations into Spanish (see my Debian home page). I've also just uploaded SLOCCount to unstable. Of course, any comment or suggestion is more than welcome. Saludos, Jesus. -- Jesus M. Gonzalez Barahona| Grupo de Sistemas y Comunicaciones [EMAIL PROTECTED] / [EMAIL PROTECTED] | ESCET, Universidad Rey Juan Carlos tel: +34 91 664 74 67 | c/ Tulipan s/n fax: +34 91 664 74 90 | 28933 Mostoles, Spain pgpiTqaKVojAL.pgp Description: PGP signature
Re: Preparing a Proposal: 3 DD needed for every NEW package
On Sun, Dec 30, 2001 at 01:44:38PM +0200, Juha J?ykk? wrote: This doesn't sound too bad to me, _but_ a better report might be to set up some sort of automatic system that sends out email to all maintainers at 1 month intervals [or something like that]. If someone doesn't respond to 2 or 3, then they are marked inactive and someone, preferable a human, verifies that the maintainer is not active anymore and orphans all of his/her packages... This would eliminate the unmaintained problem... This could be nice... I might even volunteer for setting up something like that - given the authority, of course: orphaning other people's packages must be done responsibly... This email that would be sent would be bug-list (or a subset thereof), right? A simple Are you alive? Would be quite annoying... Of course, a bug-list once a month would be annoying to active developers, too. Would it be possible to exclude from getting the email those maintainers who have uploaded a new version during the last, say, 3 months? This, of course, would still unnecessarily burden maintainers of packages which are more or less dead upstream and do not have any (important) bugs... We do not want to annoy maintainers, either... Of course, skipping maintainers of packages with no important bugs could help, too. This would be easy to implement, too. This might actually work :) A script that checks: * not uploaded anything in last 3 months? * not bug free? I would say any bugs here that are not tagged and less than important should be included as well. * not uploaded anything in last year? These should be traversed in that order, like a C AND statement so bug free packages still get a reminder at least once a year -- manytimes these might be not very used packages so not too many people complain.
GNOME panel starts crashing after apt-get upgrade (SID)
Hi ! I am not sure if this message shouldn't go to debian-user list, but as the problem is in SID/unstable I think most of SID users is on devel. I also Cc: gnome-devel-list here, as I belive it is gnome-panel, not debian package problem (but not sure about it). The problem is I really like using GNOME. One of its strenghts for me is its panel that allows me to have my own sub menus (sub-panels) in it. My panel looks more-less this way: +\/+ |NN4.7/mail| |--+\/+ | Mozilla | TkCVS| |--|--| | Galeon | Glimmer | ...-+/\+/\+/\---+---/\---+ ... | W E B | D e v e l| Office | Shells | ... | Tools | Tools | Tools || ...-+--+--+-++ The problem is, that it happened for the second time in this month, that after apt-get update apt-get dist-upgrade my config causes panel to crash while GNOME starts ! Even if I have not change nothing and _Yesterday_ it worked well... It is very confusing... The only way around is to delete ~/.gnome/panel.d directory and re-create all my panel from scratch. I have reported it as a BUG, but no response till now: http://bugzilla.gnome.org/show_bug.cgi?id=67047 I really don't know what do. I'd like to know: - Am I the only affected person ? Or are here others having this problem as well ? - Is it a problem in panel or has it sth. to do with Debian packages upgrades ? - In my bugreport I included my panel.d content (compressed), strace and ltrace outputs. I think these info should be enough to squash the bug ? What else can I do ? (besides digging in code myself) I am NOT subscribed to @gnome.org lists so Cc: me Your answers please. I AM subscribed to debian-devel, no Cc: nessesary. I really'd like to use GNOME, but this panel problem desn't help me. I think there is just a bug somewhere, but nobody cares to squash it... If I can be anyhow usefull to You, please contact me at mailto:[EMAIL PROTECTED] Thanks in advance Grzegorz Prokopski PS: I am tired of asnwers: If you're running SID you should expect problems. IMHO it is not SID to blame here, but some BUG instead (in deb package or in panel code).
Re: Preparing a Proposal: 3 DD needed for every NEW package
On Sat, Dec 29, 2001 at 12:45:54PM -0800, Thomas Bushnell, BSG wrote: I can see how removing bad packages helps. How does removing an MIA maintainer make anything better? The distort the apparent size of our project and, more importantly, swamp our Standard Resolution Procedure by artificially inflating the value of Q. See the Debian Constitution. -- G. Branden Robinson| The only way to get rid of a Debian GNU/Linux | temptation is to yield to it. [EMAIL PROTECTED] | -- Oscar Wilde http://people.debian.org/~branden/ | pgp3KFoWCC98C.pgp Description: PGP signature
Re: Preparing a Proposal: 3 DD needed for every NEW package
On Sun, Dec 30, 2001 at 12:50:58PM +0100, Martin Michlmayr wrote: For the record, please note that while quite a few packages of inactive developers have been orphaned already, no one has been asked to leave the project for their inactivity (An inactive developer without any packages doesn't do any harm anyway, and he might become active again). See Message-ID: [EMAIL PROTECTED]. -- G. Branden Robinson| You could wire up a dead rat to a Debian GNU/Linux | DIMM socket and the PC BIOS memory [EMAIL PROTECTED] | test would pass it just fine. http://people.debian.org/~branden/ | -- Ethan Benson pgpqIxVa97Fc1.pgp Description: PGP signature
GNOME panel starts crashing after apt-get upgrade (SID)
Hi ! I am not sure if this message shouldn't go to debian-user list, but as the problem is in SID/unstable I think most of SID users is on devel. I also Cc: gnome-devel-list here, as I belive it is gnome-panel, not debian package problem (but not sure about it). The problem is I really like using GNOME. One of its strenghts for me is its panel that allows me to have my own sub menus (sub-panels) in it. My panel looks more-less this way: +\/+ |NN4.7/mail| |--+\/+ | Mozilla | TkCVS| |--|--| | Galeon | Glimmer | ...-+/\+/\+/\---+---/\---+ ... | W E B | D e v e l| Office | Shells | ... | Tools | Tools | Tools || ...-+--+--+-++ The problem is, that it happened for the second time in this month, that after apt-get update apt-get dist-upgrade my config causes panel to crash while GNOME starts ! Even if I have not change nothing and _Yesterday_ it worked well... It is very confusing... The only way around is to delete ~/.gnome/panel.d directory and re-create all my panel from scratch. I have reported it as a BUG, but no response till now: http://bugzilla.gnome.org/show_bug.cgi?id=67047 I really don't know what do. I'd like to know: - Am I the only affected person ? Or are here others having this problem as well ? - Is it a problem in panel or has it sth. to do with Debian packages upgrades ? - In my bugreport I included my panel.d content (compressed), strace and ltrace outputs. I think these info should be enough to squash the bug ? What else can I do ? (besides digging in code myself) I am NOT subscribed to @gnome.org lists so Cc: me Your answers please. I AM subscribed to debian-devel, no Cc: nessesary. I really'd like to use GNOME, but this panel problem desn't help me. I think there is just a bug somewhere, but nobody cares to squash it... If I can be anyhow usefull to You, please contact me at mailto:[EMAIL PROTECTED] Thanks in advance Grzegorz Prokopski PS: I am tired of asnwers: If you're running SID you should expect problems. IMHO it is not SID to blame here, but some BUG instead (in deb package or in panel code).
Re: Preparing a Proposal: 3 DD needed for every NEW package
Le Sun, Dec 30, 2001 at 11:54:50AM +0100, Bas Zoetekouw écrivait: maintainer disappears. As those people would get the bug logs, they'd notice that the main maintainer never responds and could decide to take it over. Well, if that's all you want, there's a much easier No, that's not all what I want. I want that because for many other reasons that I won't yet explain here but that you can easily imagine. :) Each time we have a structural problem, we try to solve it with little tweaks and tools, we're not able to have a global view of our way of working. We have many talented people but not many « visionaries ». We need more people able to lead us in the same direction. solution: just keep an official list of MIA maintainers, based on just ... that's the funny word. Just do it. :-) replies to bug reports, uploads of packages, closing of bugs, etc, and post it to d-d-announce or d-private regularily. I even think such a list has already been made, but it would be nice if it could be done on The only list is the (private) list of MIA maintainer based on echelon that is maintained by Nils Lohner (CQ on irc). May I also tell you that such a list is no solution ? The real problem are the orphaned packages, such a list would only help people to find orphaned packages, but that's not how things are supposed to go. We should never have to deal with such problems because a package should always have a maintainer and the only way for that is to have a backup maintainer ready. Furthermore it would help in many other conditions (vacation, busy month for the main maintainer, ...). Cheers, -- Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/ Le bouche à oreille du Net : http://www.beetell.com Naviguer sans se fatiguer à chercher : http://www.deenoo.com Formation Linux et logiciel libre : http://www.logidee.com
Re: Preparing a Proposal: 3 DD needed for every NEW package
Le Sat, Dec 29, 2001 at 11:11:17PM +0100, Bas Zoetekouw écrivait: Let me refrase my question: can you explictly point out some packages that have been ITP'ed lately and of which you think that they should not go into Debian because they aren't needed? I can't, so I don't think there's a problem here. Heh. There's not yet a problem. :) If you look carefully you'll find dozen of packages that were ITPed by several persons (that means that several developers are interested in the same package) that finally get packaged but not well maintained. If all the developers who were initially interested could have gotten backup maintainers, they could have noticed that the package is no more well maintained and they could take it over or help the main maintainer if he didn't totally disappear. think). Seriously though, it's not the new packages we should worry about (they are mostly well taken care of and not orphaned quickly), but the old ones. All the old ones were new one day ... the fact that they are more or less orphaned today is the proof that we don't have a good system to let interested developers follow the life of a package that they are interested in. Cheers, -- Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/ Le bouche à oreille du Net : http://www.beetell.com Naviguer sans se fatiguer à chercher : http://www.deenoo.com Formation Linux et logiciel libre : http://www.logidee.com
Re: Preparing a Proposal: 3 DD needed for every NEW package
Le Sun, Dec 30, 2001 at 01:44:38PM +0200, Juha Jäykkä écrivait: This could be nice... I might even volunteer for setting up something like that - given the authority, of course: orphaning other people's packages must be done responsibly... It's funny how people keep reinventing the wheel. :-) Martin Michlmayr (tbm) already does something like that although it's not really automated. When you think that someone is MIA (because you find a package has not been touched in ages or thing like that) you try to contact him but you CC mia-loginofthedeveloper@qa.debian.org and it gets logged on pandora.debian.org (of course you have to forward any response to that same adress) and Martin regularly checks if they responded. Sometimes, he decides to orphan their packages if they haven't responded. He may tell more (or correct me) if he wish. Still, yes we'd need to send summary mails regularly but not only to the main maintainer but although to the other people who are interested in the package (cf subscription mechanism explained somewhere else in this thread). Such a mail would include bug stats, lintian stats, policy conformance (standards version) although it's partly taken care by lintian, and any other information that could be needed to let people make their opinion about the quality of the package. Anyway, that's something to do as part of the Debian QA effort. Cheers, -- Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/ Le bouche à oreille du Net : http://www.beetell.com Naviguer sans se fatiguer à chercher : http://www.deenoo.com Formation Linux et logiciel libre : http://www.logidee.com
Re: Preparing a Proposal: 3 DD needed for every NEW package
On Sun, 30 Dec 2001 14:00:29 +0200 (EET) Juha Jäykkä [EMAIL PROTECTED] wrote: maintainers' was: send him a notice that he'll be removed if he won't take care of his packages/other tasks for foo more days, if he does not answer or tell us he's giving up his key is removed from the keyring I agree to this. The obvious problem would be who does this... ;) I do not actually know, but it seems like it would need to be someone with the authority to remove keys from the keyring. Who are they? I suppose they are persons who are well known, respected by the community - and overworked... another DAM... or someone appointed by the DAM and the Project's Leader is what I thought... What I am really most afraid of, is lack of decision. This certainly looks like something that must be tackled but in too many cases in volunteer organisations, the decisions needed are never made. yes... I see your point and I am sure this happens a lot, even in Debian... but that's why we're discussing now, to find a way of solving a problem []s! -- Gustavo Noronha Silva - kov http://www.metainfo.org/kov *-* -+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+-+ | .''`. | Debian GNU/Linux: http://www.debian.org | | : :' : + Debian BR...: http://debian-br.cipsga.org.br+ | `. `'` + Q: Why did the chicken cross the road? + | `-| A: Upstream's decision. -- hmh | *-* -+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+-+
Re: Preparing a Proposal: 3 DD needed for every NEW package
On Sun, 30 Dec 2001 17:12:44 +0100 Raphael Hertzog [EMAIL PROTECTED] wrote: Le Sun, Dec 30, 2001 at 01:44:38PM +0200, Juha Jäykkä écrivait: It's funny how people keep reinventing the wheel. :-) Martin Michlmayr (tbm) already does something like that although it's not really automated. When you think that someone is MIA (because you find a package has not been touched in ages or thing like that) you try to contact him but you CC mia-loginofthedeveloper@qa.debian.org it's quite funny, but I didn't see an announcement of this... I find this out months ago by diging qa.debian.org I think resources like these should be announced and documented in the developer's reference (I didn't see it there either), what do you think? []s! -- Gustavo Noronha Silva - kov http://www.metainfo.org/kov *-* -+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+-+ | .''`. | Debian GNU/Linux: http://www.debian.org | | : :' : + Debian BR...: http://debian-br.cipsga.org.br+ | `. `'` + Q: Why did the chicken cross the road? + | `-| A: Upstream's decision. -- hmh | *-* -+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+--+-+-+
Re: Preparing a Proposal: 3 DD needed for every NEW package
Hi Raphael! You wrote: The only list is the (private) list of MIA maintainer based on echelon that is maintained by Nils Lohner (CQ on irc). Yeah, that's what I meant. It could be easily extended. May I also tell you that such a list is no solution ? The real problem are the orphaned packages, such a list would only help people to find orphaned packages, but that's not how things are supposed to go. We should never have to deal with such problems because a package should always have a maintainer and the only way for that is to have a backup maintainer ready. I don't agree. In a perfect world, yes, we would have all available software packaged for debian and all packages maintained. But that's just not reality. It's not even necessary. There is no need for ``backup maintainers'': if a package is orphaned[1], then either somebody else adopts the package (in which case there is no problem), or the package should be dropped [2] (because apparently, it is ``unneeded''). I think that such a system would solve the problem of orphaned and unmaintained packages in a much easier way that your proposal. [1] There should indeed be a procedure to detect non-maintained packages and ophan them. This should probably be done by the QA team. But there should be policy about this, of course. [2] This should of course also be done in some structural manner. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: Preparing a Proposal: 3 DD needed for every NEW package
Hi Raphael! You wrote: If you look carefully you'll find dozen of packages that were ITPed by several persons (that means that several developers are interested in the same package) that finally get packaged but not well maintained. It's quite easy to say that you can find dozens of such packages. Please be specific, and post the name of those packages/maintainers (take it to -private, if you want) but I honestly don't believe that there are many badly maintained recent packages. If all the developers who were initially interested could have gotten backup maintainers, they could have noticed that the package is no more well maintained and they could take it over or help the main maintainer if he didn't totally disappear. They can do that now, too. And if they don't notice that the package is badly mainatined, then what is the problem? There are many packages that haven't been updated in ages, but work perfectly. think). Seriously though, it's not the new packages we should worry about (they are mostly well taken care of and not orphaned quickly), but the old ones. All the old ones were new one day ... the fact that they are more or less orphaned today is the proof that we don't have a good system to let interested developers follow the life of a package that they are interested in. OK, but giving all packages multiple maintainers I find a bit far fetched a solution. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Bug#127063: ITP: mird1 - Mird database library
Package: wnpp Severity: wishlist Package: mird-dev Description: Mird database library (developer files) Package: mird1 Description: Mird database library (runtime files) URL: http://www.mirar.org/mird/ Licence: The Mird database library may be freely distributed and used with these limits: * The database library may be distributed with or without source. * There is no promise that this software works. (But if you find any bugs, please let me know!) * You can use this software for whatever you want. You don't have to pay me. * You may not pretend that you wrote this software. If you use it in a program, you must acknowledge it somewhere in your documentation. From tutorial.txt: Mird is a database library, for operating on simple disk-based databases with the following features: * The database is key-value oriented, primarily - this is useful for most database operations, from inserting and removing lines in tables, and for object-oriented data, provided it's fast enough. (It should be.) The key can be either a 32-bit integer or a byte string of any size. (A integer-key table using 32 bit hash keys is used to store the string-key entries.) * The database consists of several tables or key-value mappings. On this level, the table is identified by a 32-bit integer. It is easy enough to implement a table name lookup table, when the need arises. * Changes to the database is made in the shell of transactions, where each transaction encapsulates any change to the database atomically. * More then one transaction could be in progress at any given moment, with resulting conflicts at the closing of the last transactions, if they operate on the same data. * Conflicts are either based on changes to a key:value pair, but a whole table could be locked to mark dependency conflicts. * The syncing against disk is normally done first when the database is closed or forced to sync; this is when any unused block is reused. This gives very high speed. (The database could of course be in a state where every transaction completion is synced to the disk.) * To make this non-syncing secure, the database uses a journal file. When something fatal happened to the process using the database (power loss, kill -9, whatever), this file is read back and the database is restored to the latest state possible. * The transaction order is guaranteed; any transaction following any failed (ie, broken, not cancelled) transaction will never be seen as valid. * The database is fast; it is normally no problem to write or read several thousand entries per second, if the I/O wait is slow enough. * The database is unfortunately low-level, there is no high-level replicating, memory-only or distributing schemes included. It was never inteded to solve these problems, only the speed and security. * The library is heavily tested by a testsuite, including tests simulating power loss and write failures (as in writing the wrong data to the database). Debianized source version you can find on ftp://ftp.cgs.pl/pub/debian/mird/ eloy -- [EMAIL PROTECTED] Moje oczy s oczami wariata Kiedy spotykaj si z twoimi oczami
Re: Preparing a Proposal: 3 DD needed for every NEW package
Martin Michlmayr [EMAIL PROTECTED] writes: * Thomas Bushnell, BSG [EMAIL PROTECTED] [20011229 12:59]: We orphan ALL his packages, we get to know he is MIA and will not Oh, I think orphaning his packages can be a useful thing to do. But I just don't see why explicitly punting him helps. For the record, please note that while quite a few packages of inactive developers have been orphaned already, no one has been asked to leave the project for their inactivity (An inactive developer without any packages doesn't do any harm anyway, and he might become active again). Quite right; that's as I think it should be, but I understood Gustavo Silva's message to suggest a change in that procedure.
Re: Preparing a Proposal: 3 DD needed for every NEW package
Branden Robinson [EMAIL PROTECTED] writes: On Sat, Dec 29, 2001 at 12:45:54PM -0800, Thomas Bushnell, BSG wrote: I can see how removing bad packages helps. How does removing an MIA maintainer make anything better? The distort the apparent size of our project and, more importantly, swamp our Standard Resolution Procedure by artificially inflating the value of Q. Ok, that's a compelling reason perhaps for having some kind of inactive status, which doesn't get a vote. I think I would have no objections to such a procedure.
Re: my.debian.org
On Sun, Dec 30, 2001 at 10:03:34AM +0100, Stefano Zacchiroli wrote: On Sat, Dec 29, 2001 at 12:00:14PM +0100, Martin Michlmayr wrote: * Stefano Zacchiroli [EMAIL PROTECTED] [20011229 11:32]: BTW, why madison isn't packaged? We could package it and mention it in the developer reference. Because the tool requires the SQL database on pandora and auric. Cool, anyway I see that madison use postgresql, so just a few command line switch that specify the db host, the port and eventually username and password. In such a way it can be used by developers using ssh tunneling or something similar. Personally I have a slow connection (standard 56K modem) and I really prefer using it with ssh tunneling rather than on an interactive ssh session. maybe you search: $ apt-show-versions -a -p bb bb 1.2-9 install ok installed bb 1.2-9 stable bb 1.3rc1-0.1 testing bb 1.3rc1-1unstable bb/stable uptodate 1.2-9 Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debsupport.de PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux Wer in Reih und Glied marschiert, hat bereits meine Verachtung verdient -- Albert Einstein... So let's install Linux! pgpH67igWifqV.pgp Description: PGP signature
Bug 99208
Please take a look at #99208 in the BTS, and give me some advice. The complaint is that there are a bunch of files in xpuzzles that needed to be marked conffiles, but were not. Then, when that was fixed, the result was that a whole bunch of files now got marked as conffiles, and the result was that a bunch of user verifications becomes necessary the first time someone upgrades. It seems to me that this is inherent in the task (as mentioned in the BTS log by the previous maintainer). Accordingly, I think I should just close the bug. But: is there a way to prevent the annoyance now? And: was there a way to prevent it in the first place (even if it's too late now)? Thomas
O: libsafe -- Protection against buffer overflow vulnerabilities
Package: wnpp Severity: normal The current maintainer of libsafe, Ron Rademaker [EMAIL PROTECTED], has orphaned this package. If you want to be the new maintainer, please take it -- retitle this bug from 'O:' to 'ITA:', fix the outstanding bugs and upload a new version with your name in the Maintainer: field and a * New maintainer (Closes: #thisbug) in the changelog so this bug is closed. Some information about this package: Package: libsafe Priority: optional Section: libs Installed-Size: 256 Maintainer: Ron Rademaker [EMAIL PROTECTED] Architecture: i386 Version: 1.3-6 Depends: libc6 (= 2.1.2), ldso (= 1.8.5) Suggests: ldso (= 1.9.0), ld.so.preload-manager (= 0.1) Filename: pool/main/libs/libsafe/libsafe_1.3-6_i386.deb Size: 147848 MD5sum: 5902ee9bca4d0d22b637a06f940e0ecc Description: Protection against buffer overflow vulnerabilities Libsafe is a library that works with any pre-compiled executable and can be used transparently. Libsafe intercepts calls to functions known as vulnerable, libsafe uses a substitute version of the function that implements the same functionality, but makes sure any buffer overflows are contained within the current stack frame. * Ron Rademaker [EMAIL PROTECTED] [20011227 14:17]: You're right that I haven't done anything about libsafe where I should have... I guess the best thing to do right now is put libsafe up for adoption. On Thu, 27 Dec 2001, Matthias Klose wrote: Yotam Rubin writes: Greetings, The last libsafe upload has been over a year ago. Since then, libsafe has accumulated a large number of bugs. The current Debian release doesn't seem to be very effective. I've packaged the latest libsafe and made it available at: http://192.117.130.34/Fendor/debian/libsafe/ Can someone NMU that? I've contacted the maintainer but received no reply. It's a shame that libsafe wouldn't be usable for Debian users. - the upload isn't marked as a NMU - the package does not build from source (calls ldconfig): - the package does not build a -dev package. Correct? - the package overwrites the old library? Correct, if it's an extension only. But then it needs to be marked in the shlibs file. Else you need to build a libsafe2 and libsafe-dev package. OTOH, no package depends on libsafe. So it seems, we don't gain much to replace one buggy version with the next buggy version. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Martin Michlmayr [EMAIL PROTECTED]
Re: Preparing a Proposal: 3 DD needed for every NEW package
* Gustavo Noronha Silva [EMAIL PROTECTED] [20011230 15:40]: it's quite funny, but I didn't see an announcement of this... I find this out months ago by diging qa.debian.org It was announced and discussed on the QA list (debian-qa). I think resources like these should be announced and documented in the developer's reference (I didn't see it there either), what do you think? No, the tool should not be used by everyone but only by a few selected people who actively look for inactive maintainers. There's a README though so it's easy to get started. (pandora:/org/qa.debian.org/mia). It should probably be documented on the QA web site, though. -- Martin Michlmayr [EMAIL PROTECTED]
Re: NMU sclient
* Ian Eure [EMAIL PROTECTED] [20011229 19:23]: maintainer seems to be mia. Have you actually mailed him and asked? -- Martin Michlmayr [EMAIL PROTECTED]
Re: at least 260 packages broken on arm, powerpc and s390 due to wrong assumption on char signedness
* Joey Hess [EMAIL PROTECTED] [20011227 21:24]: I also notice someone (you?) did a binary NMU of it for s390. Fixing this problem? AFAIK the binary NMU was done because s390 had toolchain problems at some point. -- Martin Michlmayr [EMAIL PROTECTED]
Re: my.debian.org
* Jeff Breidenbach | So the first question (as always) is -- does something like a | developer portal already exist, and if so, where? Afaik, no. It seems like robster and I are developing something which should be possible to get to work properly. If people have ideas, please send them to me. I'll try to get a version running as soon as possible. -- Tollef Fog Heen Unix _IS_ user friendly... It's just selective about who its friends are.
Re: Bug#126750: klogd should optionally be started from init(8)
On Sun, 30 Dec 2001, Dominik Kubla wrote: On Sat, Dec 29, 2001 at 11:02:39PM -0200, Henrique de Moraes Holschuh wrote: Such a table should not (and needs not) to benefit processes running by someone else than root, unless you wanted to do such a thing on purpose and coded it like that. Root processes already have a much lesser probability of being killed. If I want a table to fix the issue with the ordering on time of two or three processes, I would need to be quite stupid to do something that screwed up the OOM balancing so much that users would start naming their processes syslog or named to avoid them being killed. So you are proposing to run all kind of daemons as root to avoid them being hit by the OOM killer early? Did I say that? Please. I am not stupid. I NEVER said anything about all kind of daemons. I will end up getting insulted if you keep trying to read such things between my lines. I am very aware of the amount of danger on running stuff as root, especially when they do not need it. I want the LOGGING daemons (i.e. only syslog and klogd), which ALREADY run as root, to be restarted should they die. Due to OOM killer, due to segfaults. Whatever. Stop preaching to the choir. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh
Re: Bug#126750: klogd should optionally be started from init(8)
On Sun, 30 Dec 2001, Dominik Kubla wrote: On Sun, Dec 30, 2001 at 08:13:36PM -0200, Henrique de Moraes Holschuh wrote: I want the LOGGING daemons (i.e. only syslog and klogd), which ALREADY run as root, to be restarted should they die. Due to OOM killer, due to segfaults. Whatever. It could be argued that those need not be run as root. All they need are the necessary capabilities: Indeed. In which case just using init to keep them alive, and leaving the OOM killer alone might be best. The syscall aproach could still be used I suppose, but it gets a bit more complicated. daemons. If they fail, they fail. The system still works. But if they Well, the system still works, but logging stops. And sometimes that log information might have been very useful. are not killed by OOM because of an excemption the system might kill the nfs daemon or the sendmail process. So where do you draw the line? Good question. I would not bother with anything else other than ssh and logging (and the kernel threads, i suppose). And all that just to make them harder (not impossible) to get killed by the OOM killer. BTW, I consider tweaking with the OOM killer a very partial solution, and not a very good idea. Something that would restart a process the admin told it to (i.e. init, or something like it) is a better solution, as it does not touch the kernel, and it will restart services that got ill. Keep in mind that if the system is so resource starved that the OOM mechanism kicks in, the failing processes might not be able to log anything meaningful anyway. Yes, I know this quite well. I've been through an OOM killer rampage once or twice with an older 2.4.x kernel. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh
Re: O: libsafe -- Protection against buffer overflow vulnerabilities
Although I do not want to adopt it I have prepared an NMU based on Yotam's work. The changelog is: libsafe (2.0-9-1) unstable; urgency=low * New upstream release. Closes: Bug#118786 * Removed dependency on ldso. Closes: Bug#117339 * libsafe no longer maintains its own implementation of libc routines. Closes: Bug#122640, Bug#122706, Bug#77949, Bug#104116 * libsafe should now work properly with glibc: example exploits no longer work. Closes: Bug#92336 * Added libsafe wrapper. Closes: Bug#126421 * Example exploits are no longer executable by default. * All the above was done by Yotam Rubin [EMAIL PROTECTED] who is waiting for DAM approval. * s/\(DESTDIR[[:space:]]*= \)/\1`pwd`\/..\/debian\/tmp\// src/makefile. * s/\($(DESTDIR)\/usr\)/\1\/share/ src/makefile. * Added a Build-Depends: debhelper line. * Non-maintainer upload due to the long time this package has not been uploaded and the maintainer just orphaning it. -- Shaul Karl [EMAIL PROTECTED] Mon, 31 Dec 2001 00:42:21 +0200 Should I upload it? Package: wnpp Severity: normal The current maintainer of libsafe, Ron Rademaker [EMAIL PROTECTED], has orphaned this package. If you want to be the new maintainer, please take it -- retitle this bug from 'O:' to 'ITA:', fix the outstanding bugs and upload a new version with your name in the Maintainer: field and a * New maintainer (Closes: #thisbug) in the changelog so this bug is closed. Some information about this package: Package: libsafe Priority: optional Section: libs Installed-Size: 256 Maintainer: Ron Rademaker [EMAIL PROTECTED] Architecture: i386 Version: 1.3-6 Depends: libc6 (= 2.1.2), ldso (= 1.8.5) Suggests: ldso (= 1.9.0), ld.so.preload-manager (= 0.1) Filename: pool/main/libs/libsafe/libsafe_1.3-6_i386.deb Size: 147848 MD5sum: 5902ee9bca4d0d22b637a06f940e0ecc Description: Protection against buffer overflow vulnerabilities Libsafe is a library that works with any pre-compiled executable and can be used transparently. Libsafe intercepts calls to functions known as vulnerable, libsafe uses a substitute version of the function that implements the same functionality, but makes sure any buffer overflows are contained within the current stack frame. * Ron Rademaker [EMAIL PROTECTED] [20011227 14:17]: You're right that I haven't done anything about libsafe where I should have... I guess the best thing to do right now is put libsafe up for adoption. On Thu, 27 Dec 2001, Matthias Klose wrote: Yotam Rubin writes: Greetings, The last libsafe upload has been over a year ago. Since then, libsafe has accumulated a large number of bugs. The current Debian release doesn't seem to be very effective. I've packaged the latest libsafe and made it available at: http://192.117.130.34/Fendor/debian/libsafe/ Can someone NMU that? I've contacted the maintainer but received no reply. It's a shame that libsafe wouldn't be usable for Debian users. - the upload isn't marked as a NMU - the package does not build from source (calls ldconfig): - the package does not build a -dev package. Correct? - the package overwrites the old library? Correct, if it's an extension only. But then it needs to be marked in the shlibs file. Else you need to build a libsafe2 and libsafe-dev package. OTOH, no package depends on libsafe. So it seems, we don't gain much to replace one buggy version with the next buggy version. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl email: shaulka(at-no-spam)bezeqint.net Please replace (at-no-spam) with an at - @ - character. (at-no-spam) is meant for unsolicitate mail senders only.
Re: at least 260 packages broken on arm, powerpc and s390 due to wrong assumption on char signedness
On Thu, Dec 27, 2001 at 08:08:51PM +0100, Gerhard Tonn wrote: [...] Since in some cases this wrong assumption results in a warning comparison is always true due to limited range of data type or comparison is always false due to limited range of data type I grepped my archived build logs and found that all packages below have got this problem. Since I have currently not the time to write a bug report for each I would appreciate if the respective owner could look into the problem. sgb This package is correct as is, and the warning is harmless; the line of code involved is: return (c0||c255)? unexpected_char: icode[c]; where c is a char expected to be in the normal range (0=c=127). All the chars used in this code (AFAICT) are in this range. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Debian GNU/Linux Developer Queen Mary, Univ. of London see http://people.debian.org/~jdg/ http://www.maths.qmul.ac.uk/~jdg/ or http://www.debian.org/ Visit http://www.thehungersite.com/ to help feed the hungry Also: http://www.helpthehungry.org/
How to put files at a location determined at install-time.
Lo all, Actually, I'm new here; this is my first post. I used to be a Debian-user only, but lately, I started to do some package development. With that, I ran in trouble. I lurked a bit on this mailing list and searched at http://lists.debian.org/search.html; also, I tried to find some guru's at irc.debian.org/#debian, but with no success, so therefore I am asking here. Hopefully my question ain't stupid. ;-) What I am trying to build are a couple of packages (let's call one of these mydata.deb) containing just ordinary files, related to a specific application. All these packages Depend on a generic configuration package. This configuration package determines the final location of these ordinary files by asking the user via debconf. (note: the fact that I'm using a config-package for that is irrelevant; this info could also be within an /etc-file. It is just an idea.) So, to be more precise: debconf asks the user for that location, and puts it in the debconf-database at myapp/thelocation. Now, when installing mydata.deb, it should read the myapp/thelocation variable and install the files from within mydata.deb at that specific location. The main question is: is it possible and if so, how to do it? Thanks a lot, Marc.
Bug#127117: ITP: admuser -- Manage Squid or Web users using a Web browser
Package: wnpp Version: N/A; reported 2001-12-30 Severity: wishlist * Package name: admuser Version : 2.1 Upstream Author : Pedro Lineu Orso [EMAIL PROTECTED] * URL : http://web.onda.com.br/orso/admuser.html * License : GPL Description : Manage Squid or Web users using a Web browser This utility allows you to manage Squid or Web users using only a simple Web browser. . All the management tasks, including creating, changing, removing, enabling and disabling users can be performed through an easy-to-use Web interface. This package will be sponsored by a existing Debian Developer, Gustavo Noronha Silva ([EMAIL PROTECTED]). I'm going to apply to become a NM. An already debianized and apt-get enabled version can be obtained by adding the following line to your sources.list : deb http://www.utah.com.br/~andrelop/debian unstable optional So an apt-get update followed by an apt-get install admuser will take care of the rest. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux foobar 2.4.17 #1 Qua Dez 26 10:36:36 BRST 2001 i586 Locale: LANG=pt_BR, LC_CTYPE=pt_BR -- André Luís Lopes andrelop at ig dot com dot br Debian-BR Project http://debian-br.cipsga.org.br Public GPG KeyID : 9D1B82F6 Keyserver : wwwkeys.eu.pgp.net
L10n of Debconf templates
Hi, there are 2 ways for a package maintainer to deal with l10n-ed Debconf templates: either put all translations in a single file, or separate each language in its own template file. The former has a severe drawback, because when English text is modified, there is no flag to tell that translated text is outdated, and translators won't notice. So it would be really nice if package maintainers do follow the latter, and learn to play with Debconf goodies (debconf-getlang, debconf-mergetemplate, dh_installdebconf). If my figure are right, 258 source packages have translated Debconf templates, but only 71 in separate files. Denis
Re: Preparing a Proposal: 3 DD needed for every NEW package
On Sun, Dec 30, 2001 at 06:43:57PM +0100, Bas Zoetekouw wrote: I don't agree. In a perfect world, yes, we would have all available software packaged for debian and all packages maintained. But that's just not reality. It's not even necessary. There is no need for ``backup maintainers'': if a package is orphaned[1], then either somebody else adopts the package (in which case there is no problem), or the package should be dropped [2] (because apparently, it is ``unneeded''). This happens eventually, but it introduces a delay of weeks or months in which the package sits untended because no-one is sure what's going on. We can do without this delay, and having someone who feels allowed to fix up the package as necessary with minimal delay would be very useful. I have a backup for one of my packages in the base system, groff. Nobody who knows much about man-db has stepped forward yet. -- Colin Watson [EMAIL PROTECTED]
Re: How to put files at a location determined at install-time.
Marc L de Bruin [EMAIL PROTECTED] writes: MLdB What I am trying to build are a couple of packages (let's call one of MLdB these mydata.deb) containing just ordinary files, related to a MLdB specific application. All these packages Depend on a generic MLdB configuration package. This configuration package determines the final MLdB location of these ordinary files by asking the user via MLdB debconf. Why do these files not have a specified location? The two cases I can think of are (a) you're installing something that's system-wide, in which case you can just pick a location as the package maintainer, or (b) you're installing something that potentially multiple users would want to use. In the case of (a), I'd just unpack under /var/lib/genericpackage, and then use a symlink or Apache configuration or whatever to tell whatever it is that uses the files where they actually are. For something that multiple users could potentially want to use, really the best thing to do is provide a tarball in the package, and let the end-user be responsible for unpacking it where they feel is appropriate; this is the approach the various kernel module packages use. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Re: at least 260 packages broken on arm, powerpc and s390 due to wrong assumption on char signedness
On Sun, 2001-12-30 at 17:02, Julian Gilbey wrote: This package is correct as is, and the warning is harmless; the line of code involved is: return (c0||c255)? unexpected_char: icode[c]; where c is a char expected to be in the normal range (0=c=127). All the chars used in this code (AFAICT) are in this range. This still says to me there is likely a logic error in the code; if the authors thought it was possible for c to take on a negative value at some point, then it should be declared signed. Otherwise, why not just declare it unsigned and remove the test for c 0?
Re: How to put files at a location determined at install-time.
On Sun, Dec 30, 2001 at 11:03:15PM -0500, David Z Maze wrote: For something that multiple users could potentially want to use, really the best thing to do is provide a tarball in the package, and let the end-user be responsible for unpacking it where they feel is appropriate; this is the approach the various kernel module packages use. that _some_ of the various kernel module packages use. -john
Bug#127167: Python2.1 ceval.c error.
Package: General Version: 20011231 Severity: important After upgrading to Squishdot 1.3, Python and Zope were upgraded. When trying to post an article, I receive an error on server: /usr/lib/zope/lib/python/Products/Squishdot# python2.1: ../Python/ceval.c:687: eval_code2: Assertion `(stack_pointer - f-f_valuestack) = f-f_stacksize' failed. On client I get Connection Refused in browser. Other functionality within Zope/Squishdot are fine. Thank You, Chris Yeun -- System Information Debian Release: 3.0 Kernel Version: Linux cy-debian 2.4.17 #1 Wed Dec 26 18:14:27 PST 2001 i586 unknown Python 2.1.1-7 Zope 2.4.2-0.2 Squishdot 1.3.0-1
