Accepted shaper 2.2.12-0.7.3-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 22 May 2006 12:21:14 -0400 Source: shaper Binary: shapecfg shaper Architecture: source all i386 Version: 2.2.12-0.7.3-2 Distribution: unstable Urgency: low Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: shapecfg - Bandwidth limiter for virtual network interfaces shaper - Traffic shaper init script (cbq.init) for Linux Changes: shaper (2.2.12-0.7.3-2) unstable; urgency=low . * Modify last changelog entry (2.2.12-0.7.3-1) to remove erroneous unreleased tag. * Add '| debconf-2.0' to shaper Depends: to avoid blocking cdebconf * Update debian/copyright to note that Red Hat no longer maintains it Files: f6bf052e66b09844f035f07a5bc52b39 887 net extra shaper_2.2.12-0.7.3-2.dsc 2e418a9e99d88e22e1b3e7f9007c7510 12592 net extra shaper_2.2.12-0.7.3-2.diff.gz f3852d539529803f5a1a46d0ab52e1b2 101872 net extra shaper_2.2.12-0.7.3-2_all.deb c5d106a047237f5b2bbb6058cd464541 9366 net extra shapecfg_2.2.12-0.7.3-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iQEVAwUBRHHmxWdoLXfrvKobAQK6qwgAnR87CpV3XSdU+XYUGtuJW/Pz2nVqczeL T8Tp9w3YxbHfzG3WdQcoFqKkJqwE5h3SveNr/R0kJpBcel7y+Pej2jhcAApC2Z2/ YvYv9ab4BzYHehLDgeUET4zNMCW16nL1MIr88DpOL2mugzNHZAJS9kICSyJ22lPy BbQHSYhOsIxDK7TiGQFewRkWXFLMCiQs/EXSBQd2XqeM9RU8v7XHiEMW7uHc9roI W8ALV/Qad41gmMlon4FBXJGaWGB73mSHPvEdwZ7DWBVJpQWkiKEIgb/wxsUmDeqe X1HpvOx54/+ZJ/TlKbQUcBGJ9QqD7P1sYGLsPGwi5t2ruAiJ3hK1Hg== =ckKt -END PGP SIGNATURE- Accepted: shapecfg_2.2.12-0.7.3-2_i386.deb to pool/main/s/shaper/shapecfg_2.2.12-0.7.3-2_i386.deb shaper_2.2.12-0.7.3-2.diff.gz to pool/main/s/shaper/shaper_2.2.12-0.7.3-2.diff.gz shaper_2.2.12-0.7.3-2.dsc to pool/main/s/shaper/shaper_2.2.12-0.7.3-2.dsc shaper_2.2.12-0.7.3-2_all.deb to pool/main/s/shaper/shaper_2.2.12-0.7.3-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sopwith 1.7.1-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Feb 2006 12:15:55 -0500 Source: sopwith Binary: sopwith Architecture: source i386 Version: 1.7.1-3 Distribution: unstable Urgency: low Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: sopwith- port of the 1980's side-scrolling WWI dogfighting game Closes: 298413 Changes: sopwith (1.7.1-3) unstable; urgency=low . * Apply patch from Andreas Jochens [EMAIL PROTECTED] (thanks) to fix FTBFS on AMD64 (Closes: #298413) * Quote bits in debian/menu, thanks linda and lintian. * Update FSF address in debian/copyright, also thanks linda and lintian. * Update to standards-version 3.6.2.0, no changes required. * Change Maintainer: email address from my private address to [EMAIL PROTECTED] Files: dc85a1581311a0b88cae707669a8e78f 931 games optional sopwith_1.7.1-3.dsc ac23dfd2bdba2e605d278470b01b3b2d 26254 games optional sopwith_1.7.1-3.diff.gz 2a1e45481fad4598cf7cb933fce27004 52412 games optional sopwith_1.7.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBQ/ioGGdoLXfrvKobAQKgIgf+O6IMB0ILoNLXpt7Y/93DKEb1FQcYSzuK rgjBYGf11D0EJ9+rCorkTWgKrwmxuYVcCA2DdAmuWXWxWkl1gchhLiysvNjJxsVh fADqs1UxfnXo4QDiUBxQsXiOXjFYhUsfS96Nlw24F010D5mHy9wTjXa274sYNII2 q1Apee+Efk3/MP2p3MmlB9UxUPeMOtCiGp/D29EuZkV2PYhvta1qa2HtKHoFtaZz VGJln7W3RFZl7iB8ce+krWPsTfqFiKlKnuc3/vxjRZ75jBqzPXS2cYrsD37is+te aosL2mzCk9a6Jj8bRfG9IGmQ23peac7rQ2DaoG4W/oMPc6w40V3flQ== =pTyf -END PGP SIGNATURE- Accepted: sopwith_1.7.1-3.diff.gz to pool/main/s/sopwith/sopwith_1.7.1-3.diff.gz sopwith_1.7.1-3.dsc to pool/main/s/sopwith/sopwith_1.7.1-3.dsc sopwith_1.7.1-3_i386.deb to pool/main/s/sopwith/sopwith_1.7.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted snac 0.3-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Feb 2006 12:26:15 -0500 Source: snac Binary: snac Architecture: source i386 Version: 0.3-5 Distribution: unstable Urgency: low Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: snac - complete algebraic calculator for GNOME Closes: 311499 Changes: snac (0.3-5) unstable; urgency=low . * Apply patch from RISKO Gergely [EMAIL PROTECTED] (thanks) to fix erroneous initial trig calculation pref (Closes: #311499) * Update standards-version to 3.6.2.0, no changes required. * Quote some bits in debian/menu, thanks linda and lintian. * Update FSF address in debian/copyright, thanks linda and lintian. * Update to debhelper v4 * Change Maintainer: email address from my private address to [EMAIL PROTECTED] Files: a5d7a78dd52fb270b0b6662966d8bb8a 875 gnome optional snac_0.3-5.dsc bd1923656410e0b6a41d7d578cf0c0a4 298675 gnome optional snac_0.3-5.diff.gz fc1cbaa753adbaa882e197a3e6d698e6 27540 gnome optional snac_0.3-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBQ/isyWdoLXfrvKobAQJDOggAxiNJOMvsgAhRmyiiOrqoiBvtr9f/HVpk 9OynFNkjtqfojLkC3JiNGPuIryvt5bz3HKAgqMFrlvsr7jgLJeiKCcR2rulyT6MS wow+8RrCp0k2lZKIYeS7zkWz0rBI96LCJmZyzrX4tzH35v93aWKF3NpvbC6Coq/c uy9nLO1b01zC2VzzREu/tGublKqAYcmkOy9clni9TSTcfpV0+o9164gyRV3qOzPn txJ0mgFeEWAmfVWwMhxrTjB0viTmjDFAMM4ncOIqcypxuE44nXKQFSD5gmGWTMPt weofZ8FFypfjXxpny6e+zEcaXFokTnrn+SDYvOq/iOfkJ01t4cCf1w== =o0W1 -END PGP SIGNATURE- Accepted: snac_0.3-5.diff.gz to pool/main/s/snac/snac_0.3-5.diff.gz snac_0.3-5.dsc to pool/main/s/snac/snac_0.3-5.dsc snac_0.3-5_i386.deb to pool/main/s/snac/snac_0.3-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gmrun 0.9.1-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Feb 2006 13:35:47 -0500 Source: gmrun Binary: gmrun Architecture: source i386 Version: 0.9.1-2 Distribution: unstable Urgency: low Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: gmrun - Featureful CLI-like GTK+ application launcher Closes: 353537 Changes: gmrun (0.9.1-2) unstable; urgency=low . * Enhance default /etc/gmrunrc an new URL handler; URL_term which launches the given command with 'sh -c', in an x-terminal-emulator, and waits for input when the command finishes. (Thanks to martin f krafft [EMAIL PROTECTED] for the initial patch.) * Enhance default /etc/gmrunrc by adjusting the default file handlers to take into account various desktop environments, and attempt to use the most appropriate application (Thanks again to Madduck) * Also add a bunch of apps to AlwaysInTerm (thanks Madduck). This and the two above should (Closes: #353537) * Quote 'needs' and 'section' values in debian/menu, thanks linda and lintian. * Updated FSF address in debian/copyright, thanks linda and lintian. * Update standards-version to 3.6.2.0, no changes required. * Change Maintainer: email address from my private address to [EMAIL PROTECTED] Files: 004c272f75b4653b597a1326cd57c2d5 866 x11 optional gmrun_0.9.1-2.dsc c9e79d5528f10522513badef415e7c89 28328 x11 optional gmrun_0.9.1-2.diff.gz 9acb9ca5ccc6c31eadf00be2b8545225 46116 x11 optional gmrun_0.9.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBQ/i6vGdoLXfrvKobAQL67Af/Z14JOF4kaIuIi8UEOeZjujJuR0y5aKLa umD4UDP6SLsbDKlFSMDBpgoaTw3KFtWtB2eKC1PZdeMPJttzVCQEV6MkYCI54WYn dsQ9LYx9SvUgFwobCaBkOKaeg1GOuAPjHqUFZ61zgqMvDB5RJmZhfiJ3CkBISoPP YJ1fKbH2b0QylEpPXfKtBUlVK2D4F1UCQT4KHTciGqU6ZY1c4YdYZonPmcA3bcM7 1kslncz5S8THEZaOVJxiimddXGceDyIs6PsWaPiT4/O5RO+FSaH70BbC8AOxMR/F ZXHc/OBzQfF2DEUyRIFW177sQ9bcZmk7cVb+fD2GcRPBBslL3XF5jw== =WDbQ -END PGP SIGNATURE- Accepted: gmrun_0.9.1-2.diff.gz to pool/main/g/gmrun/gmrun_0.9.1-2.diff.gz gmrun_0.9.1-2.dsc to pool/main/g/gmrun/gmrun_0.9.1-2.dsc gmrun_0.9.1-2_i386.deb to pool/main/g/gmrun/gmrun_0.9.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-driver 1.0.5a-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 9 Jun 2004 19:37:25 -0400 Source: alsa-driver Binary: alsa-source alsa-headers alsa-base Architecture: source all Version: 1.0.5a-1 Distribution: unstable Urgency: low Maintainer: Debian ALSA Maintainers [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: alsa-base - ALSA sound driver common files alsa-headers - ALSA sound driver header files alsa-source - ALSA sound driver source Closes: 247109 251678 253347 Changes: alsa-driver (1.0.5a-1) unstable; urgency=low . * New upstream release. * Steve Kowalik: - fuser may exit non-zero. Fix the apm event script. (Closes: #247109) - Update the Czech debconf translation. (Closes: #251678) * Jordi Mallach: - debian/po/da.po: Add Danish translation (thanks, Michael Kristensen; closes: #253347). Files: 4f9c3016fbe18e6e067217ed571dceea 1100 sound optional alsa-driver_1.0.5a-1.dsc 2cfe864b423d4ae00930161b79453573 2237029 sound optional alsa-driver_1.0.5a.orig.tar.gz 1cb70a9000cbd1e5a9048c0aa60de405 134482 sound optional alsa-driver_1.0.5a-1.diff.gz 371ce5ba870158e40b0728e618fd2bf8 46612 sound optional alsa-base_1.0.5a-1_all.deb 254dd331facba008ec6fb1319cf64c94 1833830 sound optional alsa-source_1.0.5a-1_all.deb 1d5ad8f328fc88c71b6ee77583f0dd6b 56324 sound optional alsa-headers_1.0.5a-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQMefvGdoLXfrvKobAQKYtQf/cVOpkC6XeqfbYf35LggK8X1bPTViBY9X Pw4za7pr0mJzAcKwf9RT63K+rewBvbwj0XnKXdrXVcJ4oOXBODoq4vlBLcjUf7uY DvJkM3gXOfW0t7dqXUSGtASB/AkBZeqDWqX8eyGH4oLeomlFTNzrxuk3PS2Jzwnm wnLtiL5qhP61grmnX4+C9ZdTY6qkm2KBV1G+qz5WbmGVO/neO31+T527FmRyhLS8 9reGvrfZpnknajF7gm6aJr2NoR/BmhGsDRAteIeDwSvOldxIE2N7GkNSZcyepcaJ rvAaepZcddZ/W7fPycBTMlM9U3OxUlknYrXTNlWDg1XxrJ5IuUpJzQ== =6x5h -END PGP SIGNATURE- Accepted: alsa-base_1.0.5a-1_all.deb to pool/main/a/alsa-driver/alsa-base_1.0.5a-1_all.deb alsa-driver_1.0.5a-1.diff.gz to pool/main/a/alsa-driver/alsa-driver_1.0.5a-1.diff.gz alsa-driver_1.0.5a-1.dsc to pool/main/a/alsa-driver/alsa-driver_1.0.5a-1.dsc alsa-driver_1.0.5a.orig.tar.gz to pool/main/a/alsa-driver/alsa-driver_1.0.5a.orig.tar.gz alsa-headers_1.0.5a-1_all.deb to pool/main/a/alsa-driver/alsa-headers_1.0.5a-1_all.deb alsa-source_1.0.5a-1_all.deb to pool/main/a/alsa-driver/alsa-source_1.0.5a-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gqmpeg 0.90.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 23 Mar 2004 22:56:07 -0500 Source: gqmpeg Binary: gqmpeg Architecture: source i386 Version: 0.90.0-2 Distribution: unstable Urgency: low Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: gqmpeg - a GTK+ front end to mpg321/mpg123 and ogg123 Closes: 239727 Changes: gqmpeg (0.90.0-2) unstable; urgency=low . * I forgot to update the Build-Depends in the last upload to reflect the migration of this package to GTK2. Rectify this oversight. (Closes: #239727) Files: 6c1b8ea2bdd7d1ec3e782e20af272bd6 875 sound optional gqmpeg_0.90.0-2.dsc 1fa149610be955ebe09b20260e282fac 23789 sound optional gqmpeg_0.90.0-2.diff.gz 739c7dc7db574e49f86d9df526dfdde9 667528 sound optional gqmpeg_0.90.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQGEHzGdoLXfrvKobAQJ+mgf8CVk75JL3S+oO+2xWCX54gVJCMO+JiOg3 hUhxgYMqXKo1TwfJNMDx8EzmKYpYTYE4uUcR+KCMOjEgbpiH4gVZcxEhwS/L8Oz7 r39tBfloGMV7LrkWKKz/aCyXmmE672PiJBoTJ6D+B69MVLGHB2PNJaiMytiv3BZw s51laz/IZQEVS65U2u5jEjB07XsWBvEKkoqFzt3uEmKTIGNPkTSjBCzkEfYi+dgZ F8DfNc7V2oMpnNvRKZzsh/SlwLNzeK0CpkbrqqmokuuHvTnHfVE3YU3oXxMj7hjl avH2k0K7nosf3SJAQkiK+nhddCrwVtVOGPSG184R8IrnVRpUAudAWg== =e/KT -END PGP SIGNATURE- Accepted: gqmpeg_0.90.0-2.diff.gz to pool/main/g/gqmpeg/gqmpeg_0.90.0-2.diff.gz gqmpeg_0.90.0-2.dsc to pool/main/g/gqmpeg/gqmpeg_0.90.0-2.dsc gqmpeg_0.90.0-2_i386.deb to pool/main/g/gqmpeg/gqmpeg_0.90.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian Project Leader IRC debate cancelled
Hey everybody. Just as a bit of background, Manoj Srivastava (the Debian Project Secretary) has for the last couple of years delegated the task of running the Debian Project Leader realtime/IRC debate to myself. This year we've seen an amazing amount of email traffic to debian-vote@lists.debian.org, including excellent participation both on the part of the candidates as well as on the part of the electorate. Almost every conceivable question relevant to the elections and the candidates' platforms have been asked and answered (in a few cases, multiple times ;). With this in mind, and given the time constraints of all people involved, this year's IRC debate will not take place. After discussion with the candidates and those who most actively participated in last year's debate, it was decided that a debate this year would be of little benefit to the electorate. If there are still questions you want the candidates to answer and debate over (I've received only one in the past few weeks), I'd encourage you to send a message to [EMAIL PROTECTED] Please, though, make at least a cursory check of the archives[1] (if you have a Debian account, you can download the list archives in mbox format from master.debian.org[2]). Specifically, those messages which are typically entitled as questions for the candidates and those messages which start threads. Thanks, David B. Harris [1] http://lists.debian.org/debian-vote/2004/debian-vote-200403/threads.html [2] master.debian.org:~debian/lists/debian-vote/debian-vote.200403 pgpl36QPIEyXU.pgp Description: PGP signature
Accepted alsa-lib 1.0.3b-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 17 Mar 2004 12:40:44 -0500 Source: alsa-lib Binary: libasound2-dev libasound2-plugins libasound2-doc libasound2 Architecture: source all i386 Version: 1.0.3b-1 Distribution: unstable Urgency: medium Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: libasound2 - Advanced Linux Sound Architecture (libraries) libasound2-dev - Advanced Linux Sound Architecture (development) libasound2-doc - Advanced Linux Sound Architecture (developer's documentation) libasound2-plugins - Advanced Linux Sound Architecture (additional plugins) Closes: 236294 236394 238212 Changes: alsa-lib (1.0.3b-1) unstable; urgency=medium . * New upstream release + Various and sundry dmix problems fixed (Closes: #236394) + snd_pcm_mmap_commit fixed (Closes: #238212) + Urgency set to 'medium' as these bugs caused problems for a lot of people. * Don't distribute ancient and non-updated changelog.gz (Closes: #236294) Files: 95856208d1372c6d6f3ee5b3f0e7893b 1179 libs optional alsa-lib_1.0.3b-1.dsc 4b69544480f0f15a06e10881c49472f5 789254 libs optional alsa-lib_1.0.3b.orig.tar.gz 257310b990412cf7297c1b163f997dd1 8664 libs optional alsa-lib_1.0.3b-1.diff.gz d225dc67358085a96e10eff8c7129bf9 292530 libs optional libasound2_1.0.3b-1_i386.deb e9e7ffc38fd67d130be63f8950273ed9 419810 libdevel optional libasound2-dev_1.0.3b-1_i386.deb c645701d27ed9c0d73a2c18c11593689 15558 libs optional libasound2-plugins_1.0.3b-1_i386.deb 0c4708dbec29cd45e92f7a37fb66e043 367798 libdevel optional libasound2-doc_1.0.3b-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQFiSZGdoLXfrvKobAQLlSQgAw9e54jJ43Hf9FP5B82owf8CRzPylhEgl M22KiUYLCOiAZwMXtwhuOqx2NKsFeXXNN1A5dOZxN6YFi7H5aXEFd7oUll8MIS4e BvqCmhbOIqaezHDPEwsZ7Q9n288chxrlAUUpKVBnuiyaTvnfmsIQOTyTMJvn9QaG cz4kMcJrdz5ADiWtqgWeKApJ2YX6OVuiptVJokc9Vx4cl1jFnAwFMOiNuM0V6uX/ lD7UpbBfTSlEjSITKaZGADcJzRvorPMOCLgD1uZK/RiBRy2q57tK1saSynnt0o/q x9kxtWiBGN0PuMpve20eaJqSZ8C82ieQAOpwYuZFRP2bLwXCxIi+6A== =7Tlz -END PGP SIGNATURE- Accepted: alsa-lib_1.0.3b-1.diff.gz to pool/main/a/alsa-lib/alsa-lib_1.0.3b-1.diff.gz alsa-lib_1.0.3b-1.dsc to pool/main/a/alsa-lib/alsa-lib_1.0.3b-1.dsc alsa-lib_1.0.3b.orig.tar.gz to pool/main/a/alsa-lib/alsa-lib_1.0.3b.orig.tar.gz libasound2-dev_1.0.3b-1_i386.deb to pool/main/a/alsa-lib/libasound2-dev_1.0.3b-1_i386.deb libasound2-doc_1.0.3b-1_all.deb to pool/main/a/alsa-lib/libasound2-doc_1.0.3b-1_all.deb libasound2-plugins_1.0.3b-1_i386.deb to pool/main/a/alsa-lib/libasound2-plugins_1.0.3b-1_i386.deb libasound2_1.0.3b-1_i386.deb to pool/main/a/alsa-lib/libasound2_1.0.3b-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gqmpeg 0.90.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 16 Mar 2004 09:38:07 -0500
Source: gqmpeg
Binary: gqmpeg
Architecture: source i386
Version: 0.90.0-1
Distribution: unstable
Urgency: medium
Maintainer: David B. Harris [EMAIL PROTECTED]
Changed-By: David B. Harris [EMAIL PROTECTED]
Description:
gqmpeg - a GTK+ front end to mpg321/mpg123 and ogg123
Changes:
gqmpeg (0.90.0-1) unstable; urgency=medium
.
* New upstream release
* Urgency set to medium as this new upstream version uses GTK2 instead of
GTK1, and ideally I'd like to see this one in Sarge if at all possible.
* config.{sub,guess}, configure: Port changes to new version
Files:
3d3114253ea05f01224264d32d07cdaa 909 sound optional gqmpeg_0.90.0-1.dsc
922c6825b31ade665e52ecd57497ef91 1070593 sound optional gqmpeg_0.90.0.orig.tar.gz
c21e41f61bc405774b7132c95cf1d3d5 23724 sound optional gqmpeg_0.90.0-1.diff.gz
1c1cb71d2e4ed76b5d371f9e676786ac 667452 sound optional gqmpeg_0.90.0-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
iQEVAwUBQFcSE2doLXfrvKobAQKlRwgApI/3+eXxSP98W1QtotqnnNLuqbacrays
wYbFK5DO+OwdSbibtXDXcKb72XivcWh6Wq1WEOrLNSMjhobYFnCZizfTeKTBYHRH
fPYMM9SSf1icH07awSi92x1J+xqXoEqkgNpHPkfcHiikA74aMwA2TATCYYr9Kv14
GR2NMkJd7Fomg+yXcSBc/pWQ8Kgxkxb4ROcmvMOL9mxSlxU/EPnLzpiPAECNupS6
4J9sDtD/TXIw5wmIIIlwIO6ACMG92YscJ2gsUf/AieT/JKU64U8mR5C387js8R8W
2kPj7Urtvp9oE1VIglTgb4tQggz8qHRhDRCuik5a22wqOP1d/TiSxw==
=BUUS
-END PGP SIGNATURE-
Accepted:
gqmpeg_0.90.0-1.diff.gz
to pool/main/g/gqmpeg/gqmpeg_0.90.0-1.diff.gz
gqmpeg_0.90.0-1.dsc
to pool/main/g/gqmpeg/gqmpeg_0.90.0-1.dsc
gqmpeg_0.90.0-1_i386.deb
to pool/main/g/gqmpeg/gqmpeg_0.90.0-1_i386.deb
gqmpeg_0.90.0.orig.tar.gz
to pool/main/g/gqmpeg/gqmpeg_0.90.0.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-utils 1.0.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 5 Mar 2004 14:40:31 -0500
Source: alsa-utils
Binary: alsa-utils
Architecture: source i386
Version: 1.0.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED]
Changed-By: David B. Harris [EMAIL PROTECTED]
Description:
alsa-utils - Advanced Linux Sound Architecture (utilities)
Closes: 106244 222431 235203
Changes:
alsa-utils (1.0.3-1) unstable; urgency=low
.
* New upstream release
* Jordi Mallach:
- debian/control: sync description with alsa-lib's.
* David B. Harris:
- debian/control:
+ Change my Uploaders: email address from my private address to
[EMAIL PROTECTED]
+ Add pciutils to Depends, alsaconf uses lspci (Closes: #235203)
- Move /etc/asound.state to /var/lib/alsa/asound.state:
+ alsaconf/alsaconf.in, alsactl/alsactl.{1,c} via
patches/10_move_asound_state_to_var.dpatch: Move the default
asound.state from /etc/ to /var/lib/alsa/ (Closes: #106244)
+ debian/postinst: If /etc/asound.state exists, copy it to
/var/lib/alsa. alsa-base will require a versioned Depends: on this
package so that restarting ALSA in its postinst will get the state
from the right place.
+ debian/postrm: Add abort-{upgrade,install} support so that
/var/lib/alsa/asound.state is moved back to /etc/ on a failed upgrade.
+ debian/prerm: New, support downgrading to versions of alsa-utils which
store state in /etc/asound.state
- alsamixer/alsamixer.1 via debian/patches/15_alsamixer_docfixes.dpatch:
Fix documentation - the space key in alsamixer doesn't add or remove
channels from the recording stream, it simply turns on recording for
that channel and turns it off everywhere else. (Closes: #222431)
- debian/menu: Use full path to /usr/sbin/su-to-root, as per lintian's
suggestion.
- debian/postinst: Call update-menus, thanks again to lintian for pointing
that oversight out.
Files:
5a6fa57dce764bd4cea724cf6836258d 1080 sound optional alsa-utils_1.0.3-1.dsc
25340be9ac46aab95ce929ebcd67b0ba 200621 sound optional alsa-utils_1.0.3.orig.tar.gz
1ff84fc78290afdaafb4f49eee86d09b 8982 sound optional alsa-utils_1.0.3-1.diff.gz
cdf30dca8a7b7a141ab67812d3c2c65f 128302 sound optional alsa-utils_1.0.3-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
iQEVAwUBQEjYemdoLXfrvKobAQKbQwgAiMucH5XEMk7K/QQiFH5hc0Hx9YcMzRhA
3bdpJt32cvYBjqrExAwqOFRGZ76/fZOKLUX3lPXgNtb/6UsNyEQHmWF7ytf6Ud1H
HtzheOSIGFlKT33JTDieZQYfndgdBfEpNs1nuBiFqWw7rgnEvL2q8iQfR3oZCmDI
EPj8QlcZlRhDUZi0rK2iPXeTzffFGE3EV2YWATYJ9b33luOAx0e4zTdE8FcQf3f1
dNtdSJRBX+5j8iOkMHU9ihEo+7xfxo9klLXsOBQ+RQbDiBM+a2/H7jOHvsTCiwvv
HvfqJ6b2tufU3HqcxfoaPV42GC/nq55QZNwVyPHi0mH5h8MGVvRExw==
=Hlhp
-END PGP SIGNATURE-
Accepted:
alsa-utils_1.0.3-1.diff.gz
to pool/main/a/alsa-utils/alsa-utils_1.0.3-1.diff.gz
alsa-utils_1.0.3-1.dsc
to pool/main/a/alsa-utils/alsa-utils_1.0.3-1.dsc
alsa-utils_1.0.3-1_i386.deb
to pool/main/a/alsa-utils/alsa-utils_1.0.3-1_i386.deb
alsa-utils_1.0.3.orig.tar.gz
to pool/main/a/alsa-utils/alsa-utils_1.0.3.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-oss 1.0.3a-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 25 Feb 2004 22:41:55 -0500 Source: alsa-oss Binary: alsa-oss Architecture: source i386 Version: 1.0.3a-1 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: alsa-oss - Advanced Linux Sound Architecture (OSS compatibility library) Changes: alsa-oss (1.0.3a-1) unstable; urgency=low . * New upstream version * David B. Harris: - Change my Uploaders: email address from my private address to [EMAIL PROTECTED] - debian/rules: Change location of aoss.1 to alsa/aoss.1 Files: 62ea694dc24552e1a4873dbac0e3aac2 1036 sound optional alsa-oss_1.0.3a-1.dsc 7f5989645c6e71c46f8376ccc4fa3e21 216942 sound optional alsa-oss_1.0.3a.orig.tar.gz 7bfb0211d7d2ec976baa458e629bddc8 15076 sound optional alsa-oss_1.0.3a-1.diff.gz d4eabcc1aa6a36d65c58ebae3e4e9a8f 42848 sound optional alsa-oss_1.0.3a-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQEjYOmdoLXfrvKobAQL3Sgf8DpbSFkjHeYi4GL3PYDlLj61WBAsPOirP creo++pB8iPQXuePiGyNg1Yne57UKiTHbfHlYe4BKwxnLUq9e8XvOSlJSOY6CSgh 2rGlilnVRuhXXDaxVNZBEV9fZw1b8ZLjGs6iIYYilKFloV8NL6hHjyQMcGkD+LaT qCwwJR2GbwKan4ktyGwZaBpwePF//Qm678+SE6cXIdO7svCccQXdN+CJDiKjP7jY ZcFRWXx+sNVvCSRdSahM1nBuBABYoEx9UbtgCaPGGg+2Ciz6yZ6A8EUB2kyA1Zic J0c7VeRLpfuTbEYKljFVeHScHvN9wzPkYNbQqYTSBmTz5eWJhA8srQ== =rRiX -END PGP SIGNATURE- Accepted: alsa-oss_1.0.3a-1.diff.gz to pool/main/a/alsa-oss/alsa-oss_1.0.3a-1.diff.gz alsa-oss_1.0.3a-1.dsc to pool/main/a/alsa-oss/alsa-oss_1.0.3a-1.dsc alsa-oss_1.0.3a-1_i386.deb to pool/main/a/alsa-oss/alsa-oss_1.0.3a-1_i386.deb alsa-oss_1.0.3a.orig.tar.gz to pool/main/a/alsa-oss/alsa-oss_1.0.3a.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-lib 1.0.3-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 25 Feb 2004 22:40:10 -0500 Source: alsa-lib Binary: libasound2-dev libasound2-plugins libasound2-doc libasound2 Architecture: source all i386 Version: 1.0.3-1 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: libasound2 - Advanced Linux Sound Architecture (libraries) libasound2-dev - Advanced Linux Sound Architecture (development) libasound2-doc - Advanced Linux Sound Architecture (developer's documentation) libasound2-plugins - Advanced Linux Sound Architecture (additional plugins) Closes: 235954 Changes: alsa-lib (1.0.3-1) unstable; urgency=low . * New upstream release + works on exec-shield enabled kernels (Closes: #235954) * David B. Harris: + Change Maintainer: email address from my private address to [EMAIL PROTECTED] Files: 57331db83dc7dfff3ce6005dd216bc14 1176 libs optional alsa-lib_1.0.3-1.dsc 3645c8b64775e31b0ec7a93877ad2ec0 786860 libs optional alsa-lib_1.0.3.orig.tar.gz c8d3063e849cd9446f16741125727a5a 8538 libs optional alsa-lib_1.0.3-1.diff.gz 8b1036e05e0b6c5829da2148f8367dd9 291908 libs optional libasound2_1.0.3-1_i386.deb e762da7526b97747ca5df3830760e3f0 417436 libdevel optional libasound2-dev_1.0.3-1_i386.deb d5e890ed1db55b49c784105fd126667a 15418 libs optional libasound2-plugins_1.0.3-1_i386.deb bf46612c9dc3d7284d6d6b12245e 368718 libdevel optional libasound2-doc_1.0.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQEjY0mdoLXfrvKobAQJvLAf/dW2KFQYK9i8lT4+YPomIzW3JiGyaJ4gC BefIEp1VOzMTribIEvI0cYuO5j64o9SPvlyPsUVI2/TAqsqvEfipz/lM6JRnGXUu Pv774jbRFHdPFbBI7KDIao6VHhWXZqyIdJpDnUOJBB1OI2C6f/LtbGuB3PzbsgcK IYFiXmbaaKqcnYrqHWntjiFGvuNoJgrAff4NVZQlm8cFVgTHUzablKZXXNvU77z/ bGVpBZmW2SXn00/wtM5ajCnnFd+hw1d5rJU3pbsJ2QVvcMLJHmjy5fUMdsxa2+X4 lj4tdEV1ZHfmZzn12jtFU+1Q4CFMXziBb2fMGF0yt3gqDVUruZPxlA== =ikmo -END PGP SIGNATURE- Accepted: alsa-lib_1.0.3-1.diff.gz to pool/main/a/alsa-lib/alsa-lib_1.0.3-1.diff.gz alsa-lib_1.0.3-1.dsc to pool/main/a/alsa-lib/alsa-lib_1.0.3-1.dsc alsa-lib_1.0.3.orig.tar.gz to pool/main/a/alsa-lib/alsa-lib_1.0.3.orig.tar.gz libasound2-dev_1.0.3-1_i386.deb to pool/main/a/alsa-lib/libasound2-dev_1.0.3-1_i386.deb libasound2-doc_1.0.3-1_all.deb to pool/main/a/alsa-lib/libasound2-doc_1.0.3-1_all.deb libasound2-plugins_1.0.3-1_i386.deb to pool/main/a/alsa-lib/libasound2-plugins_1.0.3-1_i386.deb libasound2_1.0.3-1_i386.deb to pool/main/a/alsa-lib/libasound2_1.0.3-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-driver 1.0.3-1 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 28 Feb 2004 12:49:38 -0500
Source: alsa-driver
Binary: alsa-source alsa-headers alsa-base
Architecture: source all
Version: 1.0.3-1
Distribution: unstable
Urgency: high
Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED]
Changed-By: David B. Harris [EMAIL PROTECTED]
Description:
alsa-base - ALSA sound driver common files
alsa-headers - ALSA sound driver header files
alsa-source - ALSA sound driver source
Closes: 233752 233974 234225 234233
Changes:
alsa-driver (1.0.3-1) unstable; urgency=high
.
* New upstream release
* Jordi Mallach:
- debian/control, debian/alsa-source.control: sync descriptions with
alsa-lib's.
* David B. Harris:
- Re-disable the GCC version-check warning message, as we already check
for this in debian/rules. I believe it got lost in the 1.0.2c-1 upload.
It's just a cosmetic thing, as the logic to actually do the
version-check was still disabled. (Closes: #234225)
- Change my Uploaders: email address from my private address to
[EMAIL PROTECTED]
- debian/alsa-base.init: Produce a more helpful error message when
'alsactl restore' fails. (Closes: #234233)
- debian/control (alsa-base): Add version to alsa-utils dependency,
1.0.2-2, so that the postinst's running of alsactl gets its state from
the new location (/var/lib/alsa/asound.state)
- debian/alsa-base.conf, debian/alsa-base.init: Add support to set the
runlevels within which mixer settings will be saved (the same setting is
also used to determine *from* which runlevels we'll be saving mixer
settings). Now if you boot into single-user mode and reboot right from
there, mixer settings won't be saved (so on your next boot you'll have
your normal levels, not all-muted). (Closes: #233974)
- Transition from /etc/modutils/alsa/0.9 to /etc/modutils/alsa/1.0
(Closes: #233752):
+ debian/alsa-base.config: Use /etc/alsa/modutils/1.0 if it exists, and
if it doesn't try to use /etc/alsa/modutils/0.9. Additionally, stop
replacing /etc/modutils/alsa with a symlink if it's a non-symlink.
+ debian/alsa-base.examples, debian/modutils-0.9.conf: Move to
modutils-1.0.conf
+ debian/alsa-base.postinst: Migrate /etc/alsa/modutils/0.9 to
/etc/alsa/modutils/1.0, if the latter doesn't exist. Update
/etc/{modprobe.d,modutils}/alsa symlinks if and only if they point to
0.9
+ debian/alsa-base.postrm: Remove /etc/{modprobe.d,modutils}/alsa and
known conffiles /etc/alsa/modutils/ on purge
+ debian/alsa-base.README.Debian: Update
+ debian/alsa-source.README.Debian: Update
- debian/alsa-common.templates: Remove extraneous , which would cause
'harmony (PCI: Harmony/Vivace sound chip)' to show up as two options.
Add two new chipsets, pc98-cs4232 and atiixp
- debian/patches/10_disable_gcc_version_check{1,2}.dpatch: Sync with new
upstream release
Files:
f86c098612cc6d5a8794d99531597440 1092 sound optional alsa-driver_1.0.3-1.dsc
df7a1eeed6e9574925738e5115cbfca1 2175930 sound optional alsa-driver_1.0.3.orig.tar.gz
4f5a6051c767959b9d9770757945b746 82799 sound optional alsa-driver_1.0.3-1.diff.gz
120b54a4da30119b3ad9d0ac71933e6c 52092 sound optional alsa-base_1.0.3-1_all.deb
c1d7b910bb278767ba6e3b56ec5f2d6e 1769588 sound optional alsa-source_1.0.3-1_all.deb
1db08c76c519fd927af8a1473be9549d 55018 sound optional alsa-headers_1.0.3-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
iQEVAwUBQEjYhGdoLXfrvKobAQKgOAf9H0Dhp6mPHMjDQN5S6tSPe6RZYwpQYmLN
00H1NwUAAjiAHKJI03KqbjvAQee+UoC/bN0XCNWxz9Qui55Jg6rTJBMdZTDy0I4O
GR6ZvPXMW3kkTNvA2dJQDy2tl7PtB9D2M1JG8+GhaiDS9PvFIhV1kGk20Q6Qe0kM
CLCfEWgAatYeHEA6ltZMCfUcvCKTUkEU6QNo9AcZxX7nyWnwXgwZnvW9ulsC+WR2
zJ0jD4+T2BH/EXqmb8fY67JzoBtk1yr/G82QWjYxJmJZqxjkxNh2S5AParBx2oXa
c6t/QM/dOVT2RCq+zuyMqpWcekfz/swa23KrFMaW9o6ubBjcRUwoNw==
=KJLj
-END PGP SIGNATURE-
Accepted:
alsa-base_1.0.3-1_all.deb
to pool/main/a/alsa-driver/alsa-base_1.0.3-1_all.deb
alsa-driver_1.0.3-1.diff.gz
to pool/main/a/alsa-driver/alsa-driver_1.0.3-1.diff.gz
alsa-driver_1.0.3-1.dsc
to pool/main/a/alsa-driver/alsa-driver_1.0.3-1.dsc
alsa-driver_1.0.3.orig.tar.gz
to pool/main/a/alsa-driver/alsa-driver_1.0.3.orig.tar.gz
alsa-headers_1.0.3-1_all.deb
to pool/main/a/alsa-driver/alsa-headers_1.0.3-1_all.deb
alsa-source_1.0.3-1_all.deb
to pool/main/a/alsa-driver/alsa-source_1.0.3-1_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted shaper 2.2.12-0.7.3-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 27 Feb 2004 03:48:16 -0500 Source: shaper Binary: shapecfg shaper Architecture: source all i386 Version: 2.2.12-0.7.3-1 Distribution: unstable Urgency: low Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: shapecfg - Bandwidth limiter for virtual network interfaces shaper - Traffic shaper init script (cbq.init) for Linux Closes: 228239 Changes: shaper (2.2.12-0.7.3-1) unstable; urgency=low . * Unreleased * New upstream release of cbq.init (/etc/init.d/shaper) * Change Maintainer: email address from my private address to [EMAIL PROTECTED] * Incorporate new pt_BR.po debconf translation. (Closes: #228239) * debian/po/ru.po: Fix missing msgid line (thanks Tollef and Joshua Kwan) Files: 509b8435d11f0c2ba4f6d3fc6494bb97 887 net extra shaper_2.2.12-0.7.3-1.dsc 56c7c53444d1de50f33bf06d242671d0 89178 net extra shaper_2.2.12-0.7.3.orig.tar.gz 883813e7eecb4b2967a9d50b7bee44ad 12488 net extra shaper_2.2.12-0.7.3-1.diff.gz b5df11a86c1c51a293f45392d50ce109 101662 net extra shaper_2.2.12-0.7.3-1_all.deb 86712351b5227744b099ff6a9f7d88c8 9202 net extra shapecfg_2.2.12-0.7.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQD8HumdoLXfrvKobAQI2Dgf/ZAR1J2xcEXnIpWuHGKAtc0zGZrEuLETy cZ0oH2FZYKdDoYPLyPqLGYu2TD2VW1yal2a1Ry38nrLd+FlL6v5sc3FEquhYL0gC 2sWDecSy3x50FE+a1pI9Jp1x2VJXxNbGXRYW87zA32JVqADkokgOVj5DkLZ1fMM5 AeyCXY2qb+FA3ZUXn3gX0M1urwrzHj7FzeHfy1XVEhOEsdd3ulkxRl35KIJ0VkwT KxUSBxJn5PFG0tllZRJhgCBwIqJUca6iyNr+a2OTaqeWZDpCQqyjpgisoXfDFiCt 1U2VPZPsOjg1e6b0q6J1+DmQw+4OxpQriJzU1o+9mDmhiBTtSPStjg== =WOoQ -END PGP SIGNATURE- Accepted: shapecfg_2.2.12-0.7.3-1_i386.deb to pool/main/s/shaper/shapecfg_2.2.12-0.7.3-1_i386.deb shaper_2.2.12-0.7.3-1.diff.gz to pool/main/s/shaper/shaper_2.2.12-0.7.3-1.diff.gz shaper_2.2.12-0.7.3-1.dsc to pool/main/s/shaper/shaper_2.2.12-0.7.3-1.dsc shaper_2.2.12-0.7.3-1_all.deb to pool/main/s/shaper/shaper_2.2.12-0.7.3-1_all.deb shaper_2.2.12-0.7.3.orig.tar.gz to pool/main/s/shaper/shaper_2.2.12-0.7.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ipband 0.7.2-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 27 Feb 2004 01:15:50 -0500 Source: ipband Binary: ipband Architecture: source i386 Version: 0.7.2-3 Distribution: unstable Urgency: medium Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: ipband - daemon for subnet bandwidth monitoring with reporting via email Changes: ipband (0.7.2-3) unstable; urgency=medium . * Change ipband's manpage section from 1 (Executable programs or shell commands) to 8 (System administration commands), and update all references to the manpage. * Fix bad grammar in /etc/default/ipband * Change urgency to medium; the bashism fixed in the last upload (which closed #231102) was a fairly serious problem. * Change Maintainer: email address from my private address to [EMAIL PROTECTED] Files: 630b7da06517348b3ab28e3891f116af 867 net optional ipband_0.7.2-3.dsc 4b85076bec4a4c0c78d3c707b855d251 5724 net optional ipband_0.7.2-3.diff.gz d36da9e043615be29489260aa947f2f5 27032 net optional ipband_0.7.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQD7g7WdoLXfrvKobAQKLVwf/TRVC6x/2J8SHtHMPIlRkCSkqEdqkZ5O5 PxDVqJ2gwPdvdqscGQlkgJPMHtu4nKj2mlXSYASQNuF5OifSy6GubYEFaJY8u8z1 1CKSw3KpXOPicJFRCJ+/VXIj3l5aT2J77cObKOi9FJa6lrN2BrUolFRtPka5JG6g nUUElNSejClwH0xPWFZAApYmumyhqPztHS/P3Cmld83HHjro4cX4HPnyZtVlRo7K QFp2PNjPm6IcKu0VT8izIxUTTm90yDbf8GFxjmUiFtyaCy/MckS7im7QGvqPX0wd H89SC1/f/Fv8jPaFP5POP9I4MXMDsYavKhEz0OscwX+m7GmaX1HS0A== =Kw0H -END PGP SIGNATURE- Accepted: ipband_0.7.2-3.diff.gz to pool/main/i/ipband/ipband_0.7.2-3.diff.gz ipband_0.7.2-3.dsc to pool/main/i/ipband/ipband_0.7.2-3.dsc ipband_0.7.2-3_i386.deb to pool/main/i/ipband/ipband_0.7.2-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gqmpeg 0.20.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 25 Feb 2004 20:43:31 -0500 Source: gqmpeg Binary: gqmpeg Architecture: source i386 Version: 0.20.0-2 Distribution: unstable Urgency: medium Maintainer: David B. Harris [EMAIL PROTECTED] Changed-By: David B. Harris [EMAIL PROTECTED] Description: gqmpeg - a GTK+ front end to mpg321/mpg123 and ogg123 Closes: 231673 Changes: gqmpeg (0.20.0-2) unstable; urgency=medium . * debian/control: - Build-Depend on libpng12-dev instead of libpng2-dev (Closes: #231673) - Change the Maintainer: email address I use to [EMAIL PROTECTED] - Update Standards-Version to 3.6.1.0, no changes required - 'Recommends: aumix-gtk | x-audio-mixer' instead of hardcoded (and long) list of known X11-based audio mixers * debian/menu: quote X11 and Apps/Sound Files: 9f270259b3cd2c2a609aeebf5d06797e 908 sound optional gqmpeg_0.20.0-2.dsc cdd06352e94a4d16ff60c41827c06ae5 16981 sound optional gqmpeg_0.20.0-2.diff.gz d1c94b58d0f9c962386660398fb3fb16 651138 sound optional gqmpeg_0.20.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iQEVAwUBQD1Ri2doLXfrvKobAQK6vggAswjtkramhlJqj3AIqlPWbA7AzfHK1+l9 ycA/yxT5RLpvqpLgnOB1T0SlmerBVBUmGi2O9BSNi0GsZmoem1usFltDtONoUKpx 977qiOF1BSbcYW1ssjlzV2J34HHFEKuW3qbVrrnTivnJ6q6pasnnFDAMOBwilfg3 Tq0oSPHgxAOQ8wVfXZHhilcUMk5CRipOAIbqwNNB3KucfnTadh6xUY6hNE+/QZaE vD7CZb0B/rvCWfnKAUs6l6bTnzkZjAKg29NssmIRQ0V0PexEk0pQXU1U27+gKsaX emlQWeTCLDxzWO+fx84O7PLdPZKDzabAqwQ3zYLT/R9XZCzWWO0hRQ== =lLtb -END PGP SIGNATURE- Accepted: gqmpeg_0.20.0-2.diff.gz to pool/main/g/gqmpeg/gqmpeg_0.20.0-2.diff.gz gqmpeg_0.20.0-2.dsc to pool/main/g/gqmpeg/gqmpeg_0.20.0-2.dsc gqmpeg_0.20.0-2_i386.deb to pool/main/g/gqmpeg/gqmpeg_0.20.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-driver 1.0.2c-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Feb 2004 18:56:54 -0500 Source: alsa-driver Binary: alsa-source alsa-headers alsa-base Architecture: source all Version: 1.0.2c-3 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: alsa-base - ALSA sound driver common files alsa-headers - ALSA sound driver header files alsa-source - ALSA sound driver source Closes: 232942 Changes: alsa-driver (1.0.2c-3) unstable; urgency=low . * David B. Harris: - Brown paper bag upload. - debian/alsa-common.templates: + Put module name where it's supposed to be, instead of a descriptive string. This broke debconf configuration for some people. (Closes: #232942) Files: 2aa89f3686a988f842e6601b870d022a 803 sound optional alsa-driver_1.0.2c-3.dsc 30ddb68092963d1fef99ab50c289c72b 80335 sound optional alsa-driver_1.0.2c-3.diff.gz dda96eb23cdfd93c74263289d33a1b0d 50648 sound optional alsa-base_1.0.2c-3_all.deb db1d5ea1dd5231bba40757959b432115 1764668 sound optional alsa-source_1.0.2c-3_all.deb 2961712274a59f0f3e75f63726d3c9c4 54232 sound optional alsa-headers_1.0.2c-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAMLgPJYSUupF6Il4RApa2AJ43Wc+sZUJpUnzytWxpfkyGa3aGQACgrEZj hnM+3Ga/oLFLxdgLDsc4+Cg= =Y16Q -END PGP SIGNATURE- Accepted: alsa-base_1.0.2c-3_all.deb to pool/main/a/alsa-driver/alsa-base_1.0.2c-3_all.deb alsa-driver_1.0.2c-3.diff.gz to pool/main/a/alsa-driver/alsa-driver_1.0.2c-3.diff.gz alsa-driver_1.0.2c-3.dsc to pool/main/a/alsa-driver/alsa-driver_1.0.2c-3.dsc alsa-headers_1.0.2c-3_all.deb to pool/main/a/alsa-driver/alsa-headers_1.0.2c-3_all.deb alsa-source_1.0.2c-3_all.deb to pool/main/a/alsa-driver/alsa-source_1.0.2c-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-driver 1.0.2c-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Feb 2004 19:34:41 -0500 Source: alsa-driver Binary: alsa-source alsa-headers alsa-base Architecture: source all Version: 1.0.2c-2 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: alsa-base - ALSA sound driver common files alsa-headers - ALSA sound driver header files alsa-source - ALSA sound driver source Changes: alsa-driver (1.0.2c-2) unstable; urgency=low . * Update debconf cardlist: - Add usb-usx2y (Tascam US-122 and US-428) - Add bt87x (Bt878/Bt879 TV card audio) - Add harmony (Harmony/Vivace sound chip) - Add hdspm (RME HDSP MADI board) - Add intel8x0m (Intel i8x0 software modem thing) Files: 400ce381888298657b000806b2605be8 803 sound optional alsa-driver_1.0.2c-2.dsc fa120a1b28191c6ad6a2c693e4de8e3d 80223 sound optional alsa-driver_1.0.2c-2.diff.gz dbb6364dd9a73296894c5ee1c263d751 50548 sound optional alsa-base_1.0.2c-2_all.deb 6b641e742da1f61e12b5322f4f805def 1764586 sound optional alsa-source_1.0.2c-2_all.deb 51bc62557a3e31043aa29159f44c2502 54138 sound optional alsa-headers_1.0.2c-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFALsU6JYSUupF6Il4RAkR+AJsHsXI/v2BvE/OBqLzsSKm06g2D4gCfU33F O9IA3QxMwaO//OrA0ytpDzA= =4DYR -END PGP SIGNATURE- Accepted: alsa-base_1.0.2c-2_all.deb to pool/main/a/alsa-driver/alsa-base_1.0.2c-2_all.deb alsa-driver_1.0.2c-2.diff.gz to pool/main/a/alsa-driver/alsa-driver_1.0.2c-2.diff.gz alsa-driver_1.0.2c-2.dsc to pool/main/a/alsa-driver/alsa-driver_1.0.2c-2.dsc alsa-headers_1.0.2c-2_all.deb to pool/main/a/alsa-driver/alsa-headers_1.0.2c-2_all.deb alsa-source_1.0.2c-2_all.deb to pool/main/a/alsa-driver/alsa-source_1.0.2c-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ipband 0.7.2-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Mar 2003 00:05:12 -0500 Source: ipband Binary: ipband Architecture: source i386 Version: 0.7.2-2 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: ipband - daemon for subnet bandwidth monitoring with reporting via email Closes: 156212 231102 Changes: ipband (0.7.2-2) unstable; urgency=low . * Maintainer upload (Closes: #156212) * Update maintainer email address * debian/ipband.init: Fix bashism (Closes: #231102) * Update to Standards-Version 3.6.1.0 (new $DEB_BUILD_OPTIONS stuff) + Support $DEB_BUILD_OPTIONS=noopt and ensure -g is always used. + Ensure that initscript always starts the deamon on restart (previously, it did '$0 stop' and '$0 start' on restart; now it does '$0 stop || true' and '$0 start') Files: 601622b8ba0b373f98407335beafaf2e 574 net optional ipband_0.7.2-2.dsc b23bc2996aa61aa4b1b79acfd4c14668 5414 net optional ipband_0.7.2-2.diff.gz b516729987e7979ddb0355097617422e 27056 net optional ipband_0.7.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAIV3NmdOZoew2oYURAqm/AJoC8Hpc2hN/KO+PD2+gcsLdnd1LPgCgwi/k SQm3w8MQdRCotKNFzH5EYi8= =Jp8t -END PGP SIGNATURE- Accepted: ipband_0.7.2-2.diff.gz to pool/main/i/ipband/ipband_0.7.2-2.diff.gz ipband_0.7.2-2.dsc to pool/main/i/ipband/ipband_0.7.2-2.dsc ipband_0.7.2-2_i386.deb to pool/main/i/ipband/ipband_0.7.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Accounts on debian.org machines
On Mon, 08 Dec 2003 03:18:53 + Matthew Garrett [EMAIL PROTECTED] wrote: Steve Langasek wrote: But an ssh key on removable media is not vulnerable to keysniffing alone, where a password is. If such behaviour becomes common, the keysniffers will simply copy anything that looks like an SSH key that exists on an item of removable media. There's no inherent increase in security from using a key on a USB device other than the fact that attackers aren't thinking about that yet. The old security through obscurity idea, eh? Well, if you *rely* on obscurity for your security (ie: if an attacker has free reign if they know the secret you're trying to keep [in this case, that the SSH key is on USB media]), then sure, there's a problem. It's not a problem, however, if it's only *part* of a security regimen. For instance, I'll ask a simple question: does the hacker who installed the hardware keylogger on my machine know that my SSH key is somewhere unusual? Do they even know about SSH keys? If either of those answers is no, I have effectively averted a compromise, whereas even if they *didn't* know, but I didn't use an SSH key, they'd have effective control of my machine. Some food for thought. Obscurity != security, but I've yet to see any effective security regimen which did *not* include some obscurity factors. I've also yet to see anybody post their IP address, userid, and password for their publicly-accessible servers to a public mailing list :)
Re: Accounts on debian.org machines
On Mon, 08 Dec 2003 18:38:25 -0500 Joe Drew [EMAIL PROTECTED] wrote: On Mon, 2003-12-08 at 15:37, David B Harris wrote: I've also yet to see anybody post their IP address, userid, and password for their publicly-accessible servers to a public mailing list :) I have. root, even. http://lists.debian.org/debian-devel/2002/debian-devel-200206/msg01187.html *THEIR* IP address, userid, and password. As opposed to a carefully sandboxed userid and environment. Or are you saying that you used [EMAIL PROTECTED] for your computing needs, including storing your unencrypted GPG, unencrypted SSH key (or encrypted, in which case both of which use the passwords you've posted), your email client, your web browsing, your programming, your work, and what have you? :)
Re: [custom] Debian Enterprise - packages
On Tue, 2 Dec 2003 22:49:20 -0600 John Goerzen [EMAIL PROTECTED] wrote: First of all. This is obviously not a Debian project (since it is not operating within the Debian framework.) I don't see why this then necessitates over a dozen threads on debian-devel -- AND why it gets to call itself Debian. Amen, brother.
Re: [debian enterprise] sub-project planning
On Mon, 01 Dec 2003 13:12:52 -0500 Andres Salomon [EMAIL PROTECTED] wrote: I have discussed this sub-project extensively at Voxel, and we are willing to commit to seeing this idea through - in a manner that allows the Debian community to benefit from resources that we put into it. We are willing to provide developmental resources (Voxel is more than willing to pay me to head up this sub-project), hardware, legal resources, bandwidth, and hosting, with development happening under the Debian moniker. We are also researching the possibility of 24/7 commercial support for enterprise clients, as that is a large part of what companies want (both for technical support, as well as someone to blame when something goes wrong). Up until this portion of the email, I was thinking, oh yeah, this sounds good, and get a big company involved too - like HP or IBM. Any thoughts on that? Anybody from HP or IBM here want to weigh in? P.S.: I'm willing to put work into the debix/FAI-type stuff.
Re: Debian Enterprise - a Custom Debian Distribution
On Mon, 01 Dec 2003 11:45:35 -0800 Bruce Perens [EMAIL PROTECTED] wrote: I am still negotiating with the large industry group that approached me about this project. When the price tag is north of $1M, it takes time. If that works out, they would fund 3-5 engineers full-time, plus myself and an admin to work on the aspects of this project that are important to their industry group. And only their industry group. Thus, there is room for participation of a number of vendors and/or industry groups, as well as direct participation by all of the various entities that would participate in Debian. Are you still on good terms with some people at HP? I don't even think we need funding, per se. I wouldn't mind getting paid well for the work I do, but that's a rarity. (Why does money always need to get involved?) What I'd really like to see is a company providing input, serving as a central point for customer contact, and above all, actually *supporting* the use of the end-product. ie: not being hostile to users who run it, as is so often the case these days. I can't count the number of times I've heard horror stories from HP customers (and other vendors as well) about people being unable to RMA hardware because they're using a decent software bundle that they're familiar with and can maintain, as opposed to whatever outdated and bastardised crap was included with the hardware. Okay, that sort of turned into a rant :) I do apologise, but I'd desperately like to help dispell the stigma that's associated with anything non-Red Hat.
Re: [debian enterprise] sub-project planning
On Tue, 02 Dec 2003 06:27:12 +1100 Zenaan Harkness [EMAIL PROTECTED] wrote: Any thoughts on that? Anybody from HP or IBM here want to weigh in? My primary thought wrt making money from Free Software - make as much as we possibly can - at least that's my goal, so that I can provide for myself and my family, and (in the future) work on more Free Software projects. My goals are only to provide something that and end-user can use without having their vendor tell them they're on their own, no RMAs, no hardware support, nothing.
Re: Debian Enterprise - a Custom Debian Distribution
On Mon, 01 Dec 2003 13:53:02 -0800 Bruce Perens [EMAIL PROTECTED] wrote: Are you still on good terms with some people at HP? Yes. Has anyone discussed this with Bdale? He hasn't participated in the thread yet. I wouldn't mind getting paid well for the work I do, but that's a rarity. (Why does money always need to get involved?) snip I admire those who don't have to consider money while fulfilling all three of the above goals. I meant more specifically, when corporate involvement is discussed :) There's lots of other things companies can do without writing cheques. What I'd really like to see is a company providing input, serving as a central point for customer contact, and above all, actually *supporting* the use of the end-product. ie: not being hostile to users who run it, as is so often the case these days. Yes, but let me add something. I think we will have failed if there is only one company doing this. No lock-ins, no lack of choices, please. That's one of the things wrong with RH/Fedora. And I think I have the structure to make this work. I'm writing now, should have something for you later today. Sorry, yeah. I should instead have said *their* company, not any one company. The company they buy their hardware and support from. In my mind, HP and IBM are paramount, since they also happen to be the only two major suppliers for the shop I work in :)
Accepted alsa-lib 0.9.8-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 14 Nov 2003 12:54:11 +0100 Source: alsa-lib Binary: libasound2-dev libasound2-plugins libasound2-doc libasound2 Architecture: source all i386 Version: 0.9.8-1 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: libasound2 - Advanced Linux Sound Architecture (libraries) libasound2-dev - Advanced Linux Sound Architecture (development) libasound2-doc - Advanced Linux Sound Architecture (developer's documentation) libasound2-plugins - Advanced Linux Sound Architecture (additional plugins) Changes: alsa-lib (0.9.8-1) unstable; urgency=low . * New upstream release. * David B Harris: + Bump shlibs requirement, as new symbols have been added Files: 311e0176de1a0bf75de432105ed9fc73 863 libs optional alsa-lib_0.9.8-1.dsc dbe9edd1d5251d272e7745775143bcab 742852 libs optional alsa-lib_0.9.8.orig.tar.gz c026c6644749b623af204e08b9e6ded5 7240 libs optional alsa-lib_0.9.8-1.diff.gz f027a9a79a111add962dc12a6ff75cd0 277786 libs optional libasound2_0.9.8-1_i386.deb e0802ae579516659d8415489df110a3e 402072 libdevel optional libasound2-dev_0.9.8-1_i386.deb 8552819ccc058bf679c5bd32f43352e1 15284 libs optional libasound2-plugins_0.9.8-1_i386.deb 1002a3a3632792a3e32eae1e45776400 365318 libdevel optional libasound2-doc_0.9.8-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/tMUWJYSUupF6Il4RAiOWAKDeKDDBMes/M/uOlvFq09I3fTu0iACfY5To P22HyjgQqI3bfF2n/ZwXrV4= =0D7e -END PGP SIGNATURE- Accepted: alsa-lib_0.9.8-1.diff.gz to pool/main/a/alsa-lib/alsa-lib_0.9.8-1.diff.gz alsa-lib_0.9.8-1.dsc to pool/main/a/alsa-lib/alsa-lib_0.9.8-1.dsc alsa-lib_0.9.8.orig.tar.gz to pool/main/a/alsa-lib/alsa-lib_0.9.8.orig.tar.gz libasound2-dev_0.9.8-1_i386.deb to pool/main/a/alsa-lib/libasound2-dev_0.9.8-1_i386.deb libasound2-doc_0.9.8-1_all.deb to pool/main/a/alsa-lib/libasound2-doc_0.9.8-1_all.deb libasound2-plugins_0.9.8-1_i386.deb to pool/main/a/alsa-lib/libasound2-plugins_0.9.8-1_i386.deb libasound2_0.9.8-1_i386.deb to pool/main/a/alsa-lib/libasound2_0.9.8-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted shaper 2.2.12-0.7.1-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 14 Nov 2003 11:33:12 -0400 Source: shaper Binary: shapecfg shaper Architecture: source all i386 Version: 2.2.12-0.7.1-2 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: shapecfg - Bandwidth limiter for virtual network interfaces shaper - Traffic shaper init script (cbq.init) for Linux Closes: 210725 211638 212473 213401 219266 Changes: shaper (2.2.12-0.7.1-2) unstable; urgency=low . * /etc/init.d/shaper (cbq.init): Change 'exit 1' to 'exit 0' for the case where there are no configuration files, apparently a fair number of people don't have any. (Closes: #210725, #213401) * Only attempt to load modules if /proc/modules exists (ie: if the kernel is modular). (Closes: #212473) * Update translations: + ru.po (Closes: #219266) + fr.po (Closes: #211638) * Added Dutch translation. Files: adaee87c012d7bd2d778661592944ab2 594 net extra shaper_2.2.12-0.7.1-2.dsc e1536cbf4b594cffd26229027613c230 12430 net extra shaper_2.2.12-0.7.1-2.diff.gz 9ca052824ab34de1172c51ff106c32bf 100654 net extra shaper_2.2.12-0.7.1-2_all.deb 317d3fd5799f253eef5c3d5b96e75393 9146 net extra shapecfg_2.2.12-0.7.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/tVWputvvqbTW3hMRAqmvAJ9nfiZfGSm99rZPKnPxgFmtE/nd8QCfVdFW YawsskQJY04c1ekO1Zk7XtY= =5pDx -END PGP SIGNATURE- Accepted: shapecfg_2.2.12-0.7.1-2_i386.deb to pool/main/s/shaper/shapecfg_2.2.12-0.7.1-2_i386.deb shaper_2.2.12-0.7.1-2.diff.gz to pool/main/s/shaper/shaper_2.2.12-0.7.1-2.diff.gz shaper_2.2.12-0.7.1-2.dsc to pool/main/s/shaper/shaper_2.2.12-0.7.1-2.dsc shaper_2.2.12-0.7.1-2_all.deb to pool/main/s/shaper/shaper_2.2.12-0.7.1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pre-Depends for postgresql
On Fri, 17 Oct 2003 02:18:00 +0100 Colin Watson [EMAIL PROTECTED] wrote: Uid 31 is reserved forever (speaking as the base-passwd maintainer), but new installations of postgresql should have a uid in the system range, namely 100-999, as created by 'adduser --system'. See the changelog for base-passwd 3.5.0. What for, out of curiosity? Just part of the standard range of 0-99? pgpZoZaNdEesN.pgp Description: PGP signature
Re: Bug#215103: ITP: gmasqdialer -- gtk/gnome client for masqdialer server
On Mon, 13 Oct 2003 00:02:47 -0400 Joe Drew [EMAIL PROTECTED] wrote: David B Harris wrote: As much as you may dislike it, people care about toolkit. I don't understand the witch-hunt to remove references to such things. Short description is a limited resource. By all means, put GTK or GNOME in the long description if it is deemed necessary; apt searches will still find what you're looking for. Obviously if the short description is too long, something needs to go - and in that case, certainly not mentioning the toolkit is reasonable. However, in this particular case (gtk/gnome client for masqdialer server, but really gnome client for masqdialer since the gtk is assumed when talking about GNOME) is 35 characters long. If you think 35 characters is too long, feel free to start filing thousands and thousands of bugs on all the other packages, suggesting that they remove little bits and pieces. pgpJg5QyDch8o.pgp Description: PGP signature
Re: Bug#215103: ITP: gmasqdialer -- gtk/gnome client for masqdialer server
On Mon, 13 Oct 2003 01:44:57 -0400 David B Harris [EMAIL PROTECTED] wrote: Obviously if the short description is too long, something needs to go - and in that case, certainly not mentioning the toolkit is reasonable. However, in this particular case (gtk/gnome client for masqdialer server, but really gnome client for masqdialer since the gtk is assumed when talking about GNOME) is 35 characters long. If you think 35 characters is too long, feel free to start filing thousands and thousands of bugs on all the other packages, suggesting that they remove little bits and pieces. (And if you don't, please don't bother people about it - instead file a bug on Policy asking for the short description guidelines to specifically say do not mention the application's toolkit.) pgpbH15Uf0TrV.pgp Description: PGP signature
Re: Bug#215103: ITP: gmasqdialer -- gtk/gnome client for masqdialer server
On Fri, 10 Oct 2003 21:04:23 -0400 Joe Drew [EMAIL PROTECTED] wrote: Description : gtk/gnome client for masqdialer server How about client for masqdialer? From the freshmeat description: GMasqdialer provides a GNOME/GTK client for the Masqdialer system. The Which is it, GTK only or GNOME? As much as you may dislike it, people care about toolkit. I don't understand the witch-hunt to remove references to such things. (Though I do agree that GNOME/GTK could easily be shortened to GNOME.) pgpbwd0428jOf.pgp Description: PGP signature
Re: Ideas about allowing Co-maintainer
On 05 Oct 2003 13:13:55 +0200 Goswin von Brederlow [EMAIL PROTECTED] wrote: There is no point for me working on those bugs if the patches will just rod in the bts or be thrown out so as not to differ from upstream. As I said before I won't work on the debian package again without an assurance by the maintainer that he will look at it. I've occasionally helped out with util-linux, and I must say that Debian's util-linux is already markedly different from upstream's, and this isn't a good thing. It's already bitten people once; for instance, it's unlikely that cryptoloop volumes created with Debian's util-linux will work on other machines (the passphrase is hashed before use in Debian's util-linux, and I don't believe it's done elsewhere.) As others have suggested, if you have fixes to upstream bugs, the best place to send them is to upstream. Failing that, you can always file them in the BTS and forward them upstream yourself. pgp9jP1FF6mg3.pgp Description: PGP signature
Re: apt-proxy/wget/squid caches file indefinitely
On Sun, 21 Sep 2003 11:11:37 +1000 Brian May [EMAIL PROTECTED] wrote: Ok, this is driving me bananas. I go to download the latest unstable packages, only to find that apt-get update has just retrieved a cached copy of the Packages file that (in some cases) can be a month old. I've seen similar a while ago, but I didn't bother tracking it down. I'll try to reproduce it again, an d I'll let you know if I'm able to fix it. pgp4N0rG5I9iB.pgp Description: PGP signature
Accepted gmrun 0.9.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 31 Aug 2003 04:13:48 -0400 Source: gmrun Binary: gmrun Architecture: source i386 Version: 0.9.1-1 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: gmrun - Featureful CLI-like GTK+ application launcher Closes: 186134 198539 203939 204714 Changes: gmrun (0.9.1-1) unstable; urgency=low . * New upstream release + %s and %u are expanded as many times as necessary in URL handlers (Closes: #203939) + Upstream fix for hitting 'e' when gmrun starts deselects the text and doesn't insert 'e' (Closes: #186134) + Upstream fix to make sure that ~/.gmrun_history is only created when History is 0 (Closes: #204714) * src/main.cc: Fix running comlex commands (ie: commands with spaces or other such things in them) with a terminal emulator * config/gmrunrc: Use x-www-browser as the default http handler, now that it's available. Used to be gnome-moz-remote (Closes: #198539) * debian/control: + Upstream now develops with GTK2, replace libgtk1.2-dev with libgtk2.0-dev in Build-Depends + Bump Standards-Version to 3.6.1.0, no changes required Files: f3af5870b73e0cdd2fe3000faaed631d 573 x11 optional gmrun_0.9.1-1.dsc e7789596f07b2ff628047a418fc63636 98201 x11 optional gmrun_0.9.1.orig.tar.gz 20e50c11adceb7fd7a9c67357e036c09 27623 x11 optional gmrun_0.9.1-1.diff.gz 90e2b927aef925566278d76293ed2f12 46432 x11 optional gmrun_0.9.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/WsR3hCzbekR3nhgRAtlTAJ9cO3KwaxPwPThlsUzAia894/E7KwCgkGTT E4/oweJ8ueOhuJEg8sECwcc= =/uSW -END PGP SIGNATURE- Accepted: gmrun_0.9.1-1.diff.gz to pool/main/g/gmrun/gmrun_0.9.1-1.diff.gz gmrun_0.9.1-1.dsc to pool/main/g/gmrun/gmrun_0.9.1-1.dsc gmrun_0.9.1-1_i386.deb to pool/main/g/gmrun/gmrun_0.9.1-1_i386.deb gmrun_0.9.1.orig.tar.gz to pool/main/g/gmrun/gmrun_0.9.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted snac 0.3-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 31 Aug 2003 04:38:24 -0400 Source: snac Binary: snac Architecture: source i386 Version: 0.3-4 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: snac - complete algebraic calculator for GNOME Closes: 201956 Changes: snac (0.3-4) unstable; urgency=low . * Changed section to `gnome' * debian/compat: Added (value is 3) * debian/rules: dpatchify source * debian/patches/10_libtool_update (added): + Update libtool (Closes: #201956) * debian/control: Update to Standards-Version 3.6.1.0, with changes to the extended description Files: 4b8bd5c7a452f79f9a20be32dcb111e7 582 gnome optional snac_0.3-4.dsc e713dad167db0538021cc9f09ab6cf78 298117 gnome optional snac_0.3-4.diff.gz 5cdf83a90981b72e917d677fac882921 26748 gnome optional snac_0.3-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/WsqRhCzbekR3nhgRAhf1AKCH+t37TjE4t5jjRaDRIF8ZZrQoawCgkEpj ATfIOaEMmMoIfdcAaXDlkoE= =4n5X -END PGP SIGNATURE- Accepted: snac_0.3-4.diff.gz to pool/main/s/snac/snac_0.3-4.diff.gz snac_0.3-4.dsc to pool/main/s/snac/snac_0.3-4.dsc snac_0.3-4_i386.deb to pool/main/s/snac/snac_0.3-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sopwith 1.7.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 31 Aug 2003 04:28:46 -0400 Source: sopwith Binary: sopwith Architecture: source i386 Version: 1.7.1-1 Distribution: unstable Urgency: medium Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: sopwith- port of the 1980's side-scrolling WWI dogfighting game Closes: 186898 206251 Changes: sopwith (1.7.1-1) unstable; urgency=medium . * New upstream release (Closes: #206251) + Upstream now allows the use of Left/Right arrow keys to control the plane, in addition to the traditional / and , (Closes: #186898) * debian/patches/00list: + Remove 90_ctrlkeyfix, which has been integrated upstream * debian/control: + Bump Standards-Version to 3.6.1.0, no changes required + Add pkg-config and libgtk2.0-dev to Build-Depends, as upstream requires Files: 1849aeee98dd7a2ab1373100cf4f22c0 638 games optional sopwith_1.7.1-1.dsc cc0431d3c0c506852ebe2c82db20a985 175323 games optional sopwith_1.7.1.orig.tar.gz ffbd61a247751521b0e2415e16f24c89 24971 games optional sopwith_1.7.1-1.diff.gz 35adf2dab0842f7d802989f83e55f425 51730 games optional sopwith_1.7.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/WsuUhCzbekR3nhgRAiNgAKCcvBYjcf57XSH1bay5mZMV0ra4egCghw7A ZZW7pDlz4nKrBhoYJfK+Haw= =cats -END PGP SIGNATURE- Accepted: sopwith_1.7.1-1.diff.gz to pool/main/s/sopwith/sopwith_1.7.1-1.diff.gz sopwith_1.7.1-1.dsc to pool/main/s/sopwith/sopwith_1.7.1-1.dsc sopwith_1.7.1-1_i386.deb to pool/main/s/sopwith/sopwith_1.7.1-1_i386.deb sopwith_1.7.1.orig.tar.gz to pool/main/s/sopwith/sopwith_1.7.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted shaper 2.2.12-0.7.1-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 31 Aug 2003 22:02:32 -0400 Source: shaper Binary: shapecfg shaper Architecture: source all i386 Version: 2.2.12-0.7.1-1 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: shapecfg - Bandwidth limiter for virtual network interfaces shaper - Traffic shaper init script (cbq.init) for Linux Closes: 163816 197060 202548 202850 Changes: shaper (2.2.12-0.7.1-1) unstable; urgency=low . * New upstream release of cbq.init (shaper package) * cbq.init: + Check for existence of configuration files before we attempt to load modules that may not be needed (Closes: #163816) + Add support for /etc/default/shaper to allow overriding some basic variables (Closes: #197060) * debian/shapecfg.8: Refer to /usr/share/doc/shapecfg instead of /usr/share/doc/shaper (Closes: #202850) * Clarify descriptions and debian/copyright, with respect to what shaper actually is, and where it comes from (thank a bunch, Joey Hess :) * Switch to po-debconf (thanks to the translation guys for the patch :) (Closes: #202548) * Update to Standards-Version 3.6.1.0, with minor adjustments in DEB_BUILD_OPTS handling Files: 38724d7e9961a24afc565d3c62099bc0 594 net extra shaper_2.2.12-0.7.1-1.dsc edf3af0c8ccb9ba9e0403d167a02cefe 88758 net extra shaper_2.2.12-0.7.1.orig.tar.gz fc6a072c231f1878a2f297e74b7b4f68 11386 net extra shaper_2.2.12-0.7.1-1.diff.gz 2f5f446abf8384b78f98a8a64fdaeb32 99656 net extra shaper_2.2.12-0.7.1-1_all.deb ebf438240ee79b0e83912e4be793ef4e 8836 net extra shapecfg_2.2.12-0.7.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/WsKbhCzbekR3nhgRAmNtAJ9DotDyDsCPMRZAfWTZxUUm+iLJ+gCeJLoj OhACxrY3FjU78pCKTJFXxWM= =w9w1 -END PGP SIGNATURE- Accepted: shapecfg_2.2.12-0.7.1-1_i386.deb to pool/main/s/shaper/shapecfg_2.2.12-0.7.1-1_i386.deb shaper_2.2.12-0.7.1-1.diff.gz to pool/main/s/shaper/shaper_2.2.12-0.7.1-1.diff.gz shaper_2.2.12-0.7.1-1.dsc to pool/main/s/shaper/shaper_2.2.12-0.7.1-1.dsc shaper_2.2.12-0.7.1-1_all.deb to pool/main/s/shaper/shaper_2.2.12-0.7.1-1_all.deb shaper_2.2.12-0.7.1.orig.tar.gz to pool/main/s/shaper/shaper_2.2.12-0.7.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A possible GFDL compromise
On Thu, 04 Sep 2003 21:55:07 -0400 Richard Stallman [EMAIL PROTECTED] wrote: This clause has a direct effect on all users, restricting the use of e.g. encrypted filesystems. That's a new one on me. I don't think the GFDL restricts the use of encrypted filesystems. I have mentioned it at least a half-dozen times myself, and at least once to you explicitly. (I believe you also responded to that mail, though not addressing the point in question.) As Jamin mentions, in section 2: You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. I'll also mention the first half of the sentence of section 4: You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above ... Please don't think that I'm quoting that out-of-context. I assume that anybody who will respond to this message has read the GFDL as fully as I have, and will instead point out other sections or clauses which render the above sentence irrelevant (I wasn't able to find any myself, and I looked quite hard). Taken literally (ie: should a copyright holder take a distributor to court over this point), the clause forbids _anything_ which might obstruct the reading or futher copying of the copies you make or distribute. Thus, we may not host the GFDL document on a password-protected portion of a web site. Nor may we use SSL to transmit any of the text. Nor may we store any text on an encrypted filesystem. An anonymous FTP server that requires USER and PASS would also fall into this category (regardless of whether the USER is anonymous or not). I've asked a couple of lawyers, and they strongly feel that a case could be made (though not so clear-cut as the above examples) for copying the document to a place that's already protected in some form (a $HOME that's not world-readable for instance, or on a machine that has a firewall), or distributing the document in a format that may be extraordinarily well-documented and not patent-encumbered, but for which the only reader implementation is non-Free. To RMS specifically: I have always assumed that this was simply a bug in the license, but it _has_ been brought up a lot, by myself as well as others, sometimes in messages you replied to. Now that you've noticed the point in question, I'm trying to present the rationale for the conclusion. It's not meant in a combatitive manner, nor is it meant as a personal attack against yourself. If for whatever reason somebody interprets as either of the above, I apologise and will correct that person if they're pointed out to me. pgpMyhXCdSliG.pgp Description: PGP signature
Re: A possible GFDL compromise
Sorry folks, I CC'd: -devel instead of -legal. God I hate Reply-To:s :) On Fri, 5 Sep 2003 12:03:59 -0400 David B Harris [EMAIL PROTECTED] wrote: On Thu, 04 Sep 2003 21:55:07 -0400 Richard Stallman [EMAIL PROTECTED] wrote: This clause has a direct effect on all users, restricting the use of e.g. encrypted filesystems. That's a new one on me. I don't think the GFDL restricts the use of encrypted filesystems. I have mentioned it at least a half-dozen times myself, and at least once to you explicitly. (I believe you also responded to that mail, though not addressing the point in question.) As Jamin mentions, in section 2: You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. I'll also mention the first half of the sentence of section 4: You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above ... Please don't think that I'm quoting that out-of-context. I assume that anybody who will respond to this message has read the GFDL as fully as I have, and will instead point out other sections or clauses which render the above sentence irrelevant (I wasn't able to find any myself, and I looked quite hard). Taken literally (ie: should a copyright holder take a distributor to court over this point), the clause forbids _anything_ which might obstruct the reading or futher copying of the copies you make or distribute. Thus, we may not host the GFDL document on a password-protected portion of a web site. Nor may we use SSL to transmit any of the text. Nor may we store any text on an encrypted filesystem. An anonymous FTP server that requires USER and PASS would also fall into this category (regardless of whether the USER is anonymous or not). I've asked a couple of lawyers, and they strongly feel that a case could be made (though not so clear-cut as the above examples) for copying the document to a place that's already protected in some form (a $HOME that's not world-readable for instance, or on a machine that has a firewall), or distributing the document in a format that may be extraordinarily well-documented and not patent-encumbered, but for which the only reader implementation is non-Free. To RMS specifically: I have always assumed that this was simply a bug in the license, but it _has_ been brought up a lot, by myself as well as others, sometimes in messages you replied to. Now that you've noticed the point in question, I'm trying to present the rationale for the conclusion. It's not meant in a combatitive manner, nor is it meant as a personal attack against yourself. If for whatever reason somebody interprets as either of the above, I apologise and will correct that person if they're pointed out to me. pgpzM26Bf4Cwx.pgp Description: PGP signature
Re: LWN subscription for Debian developers
On Sun, 31 Aug 2003 05:42:06 +0800 Dan Jacobson [EMAIL PROTECTED] wrote: Bdale ... I announced a group subscription to lwn.net for Debian Bdale developers, sponsored by HP... Debian may be seen as supporting non-disclosure conditions / protected proprietary information / trade secrets / etc. whatever. Bdale If you are a Debian developer and want full LWN access, go to Bdale lwn.net and create an account for yourself (no money is Bdale required... But the Debian developer cannot disclose the information seen with non Debian developers. Jealous? :) pgpKuaboT6Ya9.pgp Description: PGP signature
Accepted alsa-lib 0.9.6-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 26 Aug 2003 14:19:26 +0200 Source: alsa-lib Binary: libasound2-dev libasound2-plugins libasound2-doc libasound2 Architecture: source all i386 Version: 0.9.6-1 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: libasound2 - Advanced Linux Sound Architecture (libraries) libasound2-dev - Advanced Linux Sound Architecture (development) libasound2-doc - Advanced Linux Sound Architecture (developer's documentation) libasound2-plugins - Advanced Linux Sound Architecture (additional plugins) Closes: 199389 Changes: alsa-lib (0.9.6-1) unstable; urgency=low . * New upstream release. * David B. Harris + Import new upstream version to our CVS tree + Remove outdated Suggests: alsadriver. alsadriver doesn't exist any more, and nothing Provides: it. (Closes: #199389) Files: a9feb2c37aa1eb2f9f03bd2930566d1b 863 libs optional alsa-lib_0.9.6-1.dsc e74252e78722769dd02c9aa2632ec0f2 717190 libs optional alsa-lib_0.9.6.orig.tar.gz 30cb420a9f37d33923544580e639111a 6759 libs optional alsa-lib_0.9.6-1.diff.gz 151591e3c013344fae4041eb4960132e 251060 libs optional libasound2_0.9.6-1_i386.deb 373c6dfb1af2dfcb1460b13799abad57 370366 libdevel optional libasound2-dev_0.9.6-1_i386.deb 24c4ced64563cad1614d660206415cfe 14924 libs optional libasound2-plugins_0.9.6-1_i386.deb 2f1c38a9de13704b38be6cc2bb7207ad 352012 libdevel optional libasound2-doc_0.9.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/S1HiJYSUupF6Il4RAkkSAJ9/Po5OEtsuX6MtZNgblSzNjXa01gCfZksw 0/tvdQrabeyYxj0zwQEdUSA= =1EHs -END PGP SIGNATURE- Accepted: alsa-lib_0.9.6-1.diff.gz to pool/main/a/alsa-lib/alsa-lib_0.9.6-1.diff.gz alsa-lib_0.9.6-1.dsc to pool/main/a/alsa-lib/alsa-lib_0.9.6-1.dsc alsa-lib_0.9.6.orig.tar.gz to pool/main/a/alsa-lib/alsa-lib_0.9.6.orig.tar.gz libasound2-dev_0.9.6-1_i386.deb to pool/main/a/alsa-lib/libasound2-dev_0.9.6-1_i386.deb libasound2-doc_0.9.6-1_all.deb to pool/main/a/alsa-lib/libasound2-doc_0.9.6-1_all.deb libasound2-plugins_0.9.6-1_i386.deb to pool/main/a/alsa-lib/libasound2-plugins_0.9.6-1_i386.deb libasound2_0.9.6-1_i386.deb to pool/main/a/alsa-lib/libasound2_0.9.6-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-utils 0.9.6-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 26 Aug 2003 14:39:49 +0200 Source: alsa-utils Binary: alsa-utils Architecture: source i386 Version: 0.9.6-1 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: alsa-utils - Advanced Linux Sound Architecture (utils) Changes: alsa-utils (0.9.6-1) unstable; urgency=low . * New upstream release. * David B. Harris: + Import new upstream version to our CVS tree. Files: be29293c9fdaf879d8e8de27ee30db91 777 sound optional alsa-utils_0.9.6-1.dsc 2ec2b899603d08ff175f532145e4f204 138314 sound optional alsa-utils_0.9.6.orig.tar.gz 6d826f25d235a704de6e56dd428189ed 4886 sound optional alsa-utils_0.9.6-1.diff.gz 59f9fef2d30586843466ca46ea7e40bc 89450 sound optional alsa-utils_0.9.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/S1WMJYSUupF6Il4RAkGKAKD19v7gGPCSub/CtOUQ8x/LG0+SvgCfdOdN zkS3ND1Pg+v8F7tNvnf5cKA= =dX4+ -END PGP SIGNATURE- Accepted: alsa-utils_0.9.6-1.diff.gz to pool/main/a/alsa-utils/alsa-utils_0.9.6-1.diff.gz alsa-utils_0.9.6-1.dsc to pool/main/a/alsa-utils/alsa-utils_0.9.6-1.dsc alsa-utils_0.9.6-1_i386.deb to pool/main/a/alsa-utils/alsa-utils_0.9.6-1_i386.deb alsa-utils_0.9.6.orig.tar.gz to pool/main/a/alsa-utils/alsa-utils_0.9.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dpatch 1.24 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 3 Aug 2003 06:42:42 -0400 Source: dpatch Binary: dpatch Architecture: source all Version: 1.24 Distribution: unstable Urgency: medium Maintainer: Joerg Jaspert [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: dpatch - patch maintenance system for Debian source packages Closes: 203968 Changes: dpatch (1.24) unstable; urgency=medium . * David B Harris: - Revert broken @DPATCH@ preservation behaviour, which was introduced by a submitted patch some time ago. Thanks to Eduard Bloch for pointing it out. (Closes: #203968) Files: 41779ec5dc229af4fd097842268ebbfe 545 devel optional dpatch_1.24.dsc f1ff5238b3e3a7faf49272196691f1f1 22235 devel optional dpatch_1.24.tar.gz 4a12f56c23ea48296f1db89b89d048f7 27690 devel optional dpatch_1.24_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/LQBTR47eFMOy/N4RAmDTAJ4s6AJeEWMVXq4gkPnDgLxFTzdg7wCeOeS4 hnn7vSQMeUEb9YhZf1CAO20= =/V6j -END PGP SIGNATURE- Accepted: dpatch_1.24.dsc to pool/main/d/dpatch/dpatch_1.24.dsc dpatch_1.24.tar.gz to pool/main/d/dpatch/dpatch_1.24.tar.gz dpatch_1.24_all.deb to pool/main/d/dpatch/dpatch_1.24_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#203046: RFA: doc-linux -- Linux HOWTOs and FAQs
On Sun, 27 Jul 2003 11:47:06 +0100 Colin Watson [EMAIL PROTECTED] wrote: David Harris has expressed an interest in this job, and I've talked to him about it on IRC, so if he still wants it he's welcome. If anyone else is interested, then contact me: a small team would be a good idea anyway. I'll wait and see if anybody else, perhaps more suitable, will volounteer to be the primary maintainer before considering taking on a package this large. I'd have to think about it at any rate. I'd also be more comfortable in a team environment, I find that more work gets done that way. P.S.: The packages look to be in great shape now, so either way, thanks for the work :) pgpVhwgnaWuis.pgp Description: PGP signature
Re: new credit printing mechanism now present in reiserfsprogs
(That's a really long recipient list - does this need only go to reiserfs-list@namesys.com and [EMAIL PROTECTED]) On Wed, 23 Jul 2003 11:45:09 +0400 Hans Reiser [EMAIL PROTECTED] wrote: it now prints two random credits rather than all of them, and credits for the developers are in place. suggestions about how to improve this while preserving the credits (e.g. printing them at a different stage of mkreiserfs, etc.) are welcome. If mkreiserfs was slower, I would suggest printing them at the start of the program. It gives people something to read while they're waiting for it to finish. (They would probably be more likely to read it, too.) It takes less than 4 seconds on a regular file of 410M here, though, so that's not a whole lot of time. Does it take longer on bigger filesystems? Lots of people are making many-gigabyte filesystems these days, so perhaps that really is a good idea. pgpSmUZz0vdA1.pgp Description: PGP signature
Re: default MTA for sarge
On Sun, 13 Jul 2003 10:31:51 +0200 Joey Hess [EMAIL PROTECTED] wrote: For sarge we have two options for the default MTA in base: a. replace exim with exim4 b. no MTA installed by default, add a MTA task So do we want there to be a MTA by default? I would opt for a) personally. Exim has done me well for years, and exim-config (or its debconf-based replacement) is great. However, if b) is chosen ... doesn't this cry for a category, not a task? Or perhaps even a one-off frontend that lets one select from the list of 'grep-available -FProvides -sPackage mail-transport-agent'? pgplbFa6n1iM4.pgp Description: PGP signature
Re: Debian 10th birthday gear
On Tue, 8 Jul 2003 11:11:13 +0200 Sebastian Rittau [EMAIL PROTECTED] wrote: On Tue, Jul 08, 2003 at 05:36:22PM +1000, Anand Kumria wrote: General Debian 1 project 10 architectures 100 countries 1000 maintainers 1 packages 10 bug fixed 100 million users 1000 installations I would recommend to exchange these last two lines. More installations than users? I'm a single Debian user, and I maintain about a dozen Debian boxen. (And when I say maintain, I mean they do various things for me, the sysadmin, and I'm the closest thing to a user for them that exists.) So the 10:1 ratio is approximately accurate, at least here. It's a common demographic for Debian I believe. pgpcr0nofWLXi.pgp Description: PGP signature
Re: NEWS.Debian support is here
On Tue, 8 Jul 2003 22:48:48 +1200 Nick Phillips [EMAIL PROTECTED] wrote: On Tue, Jul 08, 2003 at 10:46:47AM +0200, Josselin Mouette wrote: Le mar 08/07/2003 ? 01:15, Matt Zimmerman a ?crit : All that's missing is an automatic debconf notice entry for each NEWS item. That wud be well c00l. As I recall, part of the idea of NEWS.Debian was to prevent having this kind of information end up as debconf notes. But some people like to have this information in debconf notes. Having the choice between displaying them and reading them in NEWS.Debian would be neat. He was JOKING... wasn't he? I doubt it. Some people have few enough packages installed that a nice pretty interface like that is reasonable. Keep in mind that debconf notes weren't implemented to piss people off - they were implemented because they can be used well. They're overused and overabused, but they're a valid presentation mechanism ... under the right circumstances :) pgpKKZh9syZb2.pgp Description: PGP signature
Re: NEWS.Debian support is here
On Sun Jul 06, 04:58pm -0400, Matt Zimmerman wrote: On Sun, Jul 06, 2003 at 04:31:22PM -0400, Matt Zimmerman wrote: On Sun, Jul 06, 2003 at 07:13:23PM +0100, Scott James Remnant wrote: Would this work just as well? [example without distribution and urgency] It would work just as well. The changelog format was used unmodified for purposes of simplicity. Tools already know how to parse it, and its format is already reasonably specified in the documentation. To clarify, I meant that such a format would meet the need of NEWS.Debian. However, the existing tools would not understand it. I do not see the extra unused information as a problem, and it lets us use existing tools for creating and editing NEWS.Debian (debchange, dpkg-dev-el, etc.) If you can make apt-listchanges understand the pared-down format, perhaps the others will support it eventually too. I don't care a whole lot about it myself, but it *does* look a lot nicer :)
Re: Please remove RFCs from the documentation in Debian packages
On 03 Jul 2003 23:45:56 -0500 Joe Wreschnig [EMAIL PROTECTED] wrote: On Thu, 2003-07-03 at 15:19, Thomas Viehmann wrote: Cameron Patrick wrote: On Thu, Jul 03, 2003 at 02:36:48PM -0500, Branden Robinson wrote: | Well, once you folks have come up with a definition of software, you | be sure and let us know. How about anything included in Debian? That way we won't be in danger of violating the Social Contract #1. Oh, cool. How about changing in DFSG to Anything that can go in main or contrib. Because that's a circular definition. Saying everything in Debian is software, is not. It's also the only reasonable way to define software. Or at least, the only reasonable way I (or anyone else who has voiced their opinion on this issue here) have come up with in 3 years, and it's not for a lack of trying. The assumption in his suggestion was that it would no longer be the Debian Free Software Guidelines, but the Debian Free main/contrib Guidelines. ie: if it's going to go into main or contrib, it needs to meet the guidelines. Except for the title, the DFSG is very content-agnostic. It can be applied equally well to software, fiction, nonfiction, images, what have you. pgpsRUM6OreNP.pgp Description: PGP signature
Re: Please remove RFCs from the documentation in Debian packages
On 03 Jul 2003 13:00:47 +0200 Petter Reinholdtsen [EMAIL PROTECTED] wrote: [Javier Fernández-Sanguino Peña] (For those who are not aware of this issue, please read #92810) There seem to be someone believing that standard documents should be treated as software. Standards are not software. Standards do not improve if everyone is allowed to modify them and publish the modified version as an updated version of the standard. Standards get their value from having a rigid procedure for updates and modifications. Software do not. I believe this whole case of RFC standards are not confirming to The Debian Free Software Guidelines display a complete lack of understanding of the value of standards, and should be rejected. Standards are not software, nor software manuals, and should not be treated as such. I haven't been following this case, and understand it might be late to speak up against it, but believe it is about time the whole case is stopped. #92810 specifically deals with whether the RFCs should be in main or non-free. They are not freely modifiable, so they should not be in main - end of story, regardless of whether it's a good thing or a bad thing. I happen to agree with your thoughts (if not the phrasing and tone), and agree that standards by their nature can't be both Free and effective. But they're no less effective in non-free, so just relax :) pgp0WiB4muIiQ.pgp Description: PGP signature
Re: Bug#198158: architecture i386 isn't i386 anymore
On Mon, 30 Jun 2003 18:17:57 +0200 Karsten Merker [EMAIL PROTECTED] wrote: I think ports to other kernels are generally worthwhile in and of themselves, simply for cleaning up the codebase and getting rid of unportable stuff. It's just plain old healthy is all. The previous comment about it was just meant in an informative manner is all. (I've never heard of a Turbochannel machine either, so I won't bother looking into it.) TurboChannel is a 32bit bus system used in Digital Equipment systems like the MIPS-based DECstation series and the Alpha-based DEC 3000 series. The former (at least some models) is supported by Linux/MIPS (and Debian/MIPS) as well as by NetBSD/OpenBSD, the latter is only supported by *BSD. Thanks :) pgpS2MBhvRyC8.pgp Description: PGP signature
Re: Bug#198158: architecture i386 isn't i386 anymore
On Sat, 28 Jun 2003 15:53:56 -0600 Joel Baker [EMAIL PROTECTED] wrote: No it doesn't. I've yet to even hear of an architecture that NetBSD runs on but which Linux doesn't. They just have a different definition of architecture than us. (ie: our hppa may be three or four arches to the NetBSD kernel folk.) There are a couple. I don't think most people care about any of them, right now (and quite possibly never will, in the case of old VAXen, for example). There's a working VAX port including a relatively complete driver set, at least, so that's not one. :) But, regardless; In discussing it the other day, I actually found a concise way to express one of the major reasons I choose to work on the port and find it worthwhile: I think ports to other kernels are generally worthwhile in and of themselves, simply for cleaning up the codebase and getting rid of unportable stuff. It's just plain old healthy is all. The previous comment about it was just meant in an informative manner is all. (I've never heard of a Turbochannel machine either, so I won't bother looking into it.) pgp0LjEdvp7zM.pgp Description: PGP signature
Re: but I want the GNU versions of packages
On Sat, 28 Jun 2003 07:57:55 +0800 Dan Jacobson [EMAIL PROTECTED] wrote: Gentlemen, after I installed Debian GNU/Linux, I found I had to take extra steps to get the GNU version of a program installed, as some other leading brand alternative was in its stead. So what is the single command to apt-get install all the GNU versions of everything? Last year I discovered mawk sitting there until I banished it away with apt-get install gawk. Yesterday I realized I had been using mailx all this time while GNU's mailutils were sitting unused. Do I look in Packages.gz for Conflicts:, and then look in Description: for this is the GNU version of...? What other other leading brands programs are sitting on my computer when I could have been using a genuine GNU program? What genuine GNU programs should I defer, lest e.g. messages get trunc A fair numbe rof those apps you probably want were implemented in Debian before GNU made their own versions - install-info(8) is one of the ones most often griped about. I believe which(1) is another case. Regardless, having a gnu task is perfectly reasonable as far as I'm concerned - just wanted to point out that it isn't necessarily maliciousness or even a judgement call so much as things just *weren't there* :) pgpLEMheDgw4I.pgp Description: PGP signature
Re: Bug#198158: architecture i386 isn't i386 anymore
On Wed, 25 Jun 2003 14:04:54 -0500 Gunnar Wolf [EMAIL PROTECTED] wrote: And not only 80386 needs this - There is the Sparc64 port which would also benefit from this (http://www.debian.org/ports/sparc/#64bit). If we had support for subarchtectures, not only would the ix86 mess be able to be split in many flavors (i.e. strict 386, 486 and up, 686, or whatever you fancy). And I am sure this can somehow help maintain the non-Linux ports - NetBSD gives us the potential to bring Debian to _many_ new platforms. No it doesn't. I've yet to even hear of an architecture that NetBSD runs on but which Linux doesn't. They just have a different definition of architecture than us. (ie: our hppa may be three or four arches to the NetBSD kernel folk.) pgpecAblVDzu4.pgp Description: PGP signature
Re: maildirmake
On Tue, 24 Jun 2003 13:12:04 +1000 (EST) Matthew Palmer [EMAIL PROTECTED] wrote: Capable of handling, yes, but then, so is cat. g Once delivered, though, there's no way of getting it back out again unless you're running something like courier or similar. Or Mutt, or a halfdozen other MUAs. :) My logic was that, from the basic system, Maildir mailboxes are no use. Things like courier make Maildir useful, so that's where the maildirmake script should live. It *might* make sense to put it in exim where people can run it to make their mailboxes, but since the delivery is useless without other programs to post-process, I'm still not won over on the idea... Well, it's a standard format, and it's a trivial shell script. The options are either including maildirmake(1) in each and every MUA that understands Maildir formats (understanding here that imapds perform many/most functions traditionally assigned to an MUA), and having them all either Conflicts: with one another or using alternatives. Given how simple it is, makes more sense to have it in one place. I don't know where it should be (in all the MTAs?), but there you go :) pgpmJKfebDkaV.pgp Description: PGP signature
Re: CGI:IRC on Debian
On Mon, 23 Jun 2003 16:02:39 +0200 Vincent Zweije [EMAIL PROTECTED] wrote: Dodging with symlinks is not really a solution, as all the files will actually still be in the wrong places. I believe he meant installing them to the proper locations, and then making symlinks from there to the big directory which is probably in /var/www. Thus, the files wouldn't actually be in the wrong places. I agree however, in that it's an unpleasant workaround. As for my own suggestion, I would say - fix the package. The diff.gz exists for a reason. If you're incapable of fixing it, find somebody who can (and hopefully get them to show you how they did it). pgppuQijpkXCx.pgp Description: PGP signature
Re: maildirmake
On Tue, 24 Jun 2003 11:46:48 +1000 (EST) Matthew Palmer [EMAIL PROTECTED] wrote: On Tue, 24 Jun 2003 [EMAIL PROTECTED] wrote: Now I'm wondering about it even more. IMHO `maildirmake' is _very_ necessary for any mail and as it seems to be only a 2-line-shell-script why it isn't included anywhere and anyway in the base-system? As I recall, maildirmake is only needed if you are running Maildir-based MDAs, which Debian does not by default[1]. That is enough of a reason not to ship it in the base system, regardless of whether it's a two line shell script or not. [1] Arguments as to whether Debian should do this or not should be directed to /dev/null. Exim is capable of handling Maildir mailboxes. It's Priority: important. I don't know if that counts as shipping it by default or not, but I would certainly say that it's the closest thing around. pgp8nmZT4A4RL.pgp Description: PGP signature
Re: CGI:IRC on Debian
On Mon, 23 Jun 2003 23:27:48 -0300 Gustavo Noronha Silva [EMAIL PROTECTED] wrote: As for my own suggestion, I would say - fix the package. The diff.gz exists for a reason. If you're incapable of fixing it, find somebody who can (and hopefully get them to show you how they did it). Additionally, try to make those modifications as compatible with the upstream's policies and code style as possible, as this is going to increase the possibility of he taking the patch. Excellent and important point, thanks. I'll try not to forget in the future. pgpUQCtjX1PCM.pgp Description: PGP signature
Accepted dpatch 1.22 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Jun 2003 04:01:28 -0400 Source: dpatch Binary: dpatch Architecture: source all Version: 1.22 Distribution: unstable Urgency: low Maintainer: Joerg Jaspert [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: dpatch - patch maintenance system for Debian source packages Changes: dpatch (1.22) unstable; urgency=low . * Brown paper bag release: - 'dpatch.make:45: *** unterminated call to function `shell': missing `)' fixed, caused all builds with 1.21 to break. Let us never upload on Friday the 13th again. Files: a5d55709e325c945403ff8ab43a974f5 545 devel optional dpatch_1.22.dsc 4cd182b545e0ea8aa74b62f2756cd400 21369 devel optional dpatch_1.22.tar.gz c9269d66156e17e86a1bfe0391893fe0 26238 devel optional dpatch_1.22_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+63kzR47eFMOy/N4RAsg6AJ0aYXF9yHSVVO44Ys1BzZnQKPZdPgCfbyN+ Qo4SzxIvCdZZfw+7impUiyI= =jmvY -END PGP SIGNATURE- Accepted: dpatch_1.22.dsc to pool/main/d/dpatch/dpatch_1.22.dsc dpatch_1.22.tar.gz to pool/main/d/dpatch/dpatch_1.22.tar.gz dpatch_1.22_all.deb to pool/main/d/dpatch/dpatch_1.22_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new bug tags
On Sun, 01 Jun 2003 15:33:29 +0100 James Troup [EMAIL PROTECTED] wrote: Since we're using bug tags for such specific things now wouldn't it make sense to add per architecture tags so one can search via http://bugs.debian.org/tag:hppa for hppa related issues (not that there are any of course!). It would help porters to identify arch related issues much more easily. I strongly second this. I don't; it's silly. At best you'll get an architecture tag for the arch that the buildd maintainer reported the bug on, but that's it. An inaccurate architecture tag is worse than useless, it's misleading. Just parse wanna-build's failed logs; it's trivial. I don't think he's specifically referring to buildd things as much as just general arch issues (ie: one might file a bug with respect to an endianness issue and tag it hppa). pgpkvbWqYwIAk.pgp Description: PGP signature
Accepted dpatch 1.20 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 26 May 2003 03:00:28 -0400
Source: dpatch
Binary: dpatch
Architecture: source all
Version: 1.20
Distribution: unstable
Urgency: low
Maintainer: Joerg Jaspert [EMAIL PROTECTED]
Changed-By: David B Harris [EMAIL PROTECTED]
Description:
dpatch - patch maintenance system for Debian source packages
Closes: 193392 193481 195104 195443
Changes:
dpatch (1.20) unstable; urgency=low
.
* David B. Harris:
- dpatch-edit-patch, dpatch-edit-patch.functions, dpatch-edit-patch.1:
+ The meaning of CLI option -k (keep temporary working directory) was
reversed. Thanks to Era Eriksson for the patch :) (Closes: #193392)
+ Another patch from Era - thanks again! This one allows
debian/patches/00template to be executable. See the manpage for more
details. (Closes: #193481)
* Gergely Nagy:
- debian/control (Standards-Version): Bumped to 3.5.10.0.
- dpatch.make (PATCHLIST_ALL): Redirect stderr to /dev/null.
(PATCHLIST_ARCH): Likewise.
Noticed by James Troup. (Closes: #195104)
- debian/rules (binary-indep): Mark all files in ${DPATCH}/etc as
conffiles.
- dpatch-list-patch: Use $( ( instead of $((. The latter is
treated as an aritmetic expression by dash, thus parsing fails. With
a space between the two parens, it is correctly recognised as a
nested command substitution thingy.
- dpatch-convert-diffgz: Addedd support for epochs. Patch from Junichi
Uekawa. (Closes: #195443)
Files:
b040fc50040f3db168310d5bc5d8b5a9 545 devel optional dpatch_1.20.dsc
964d87d0c5b2040de36d92132c3982f8 21117 devel optional dpatch_1.20.tar.gz
10d0b181b071efffd9f33f5a08671cbc 25882 devel optional dpatch_1.20_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+2ToDR47eFMOy/N4RAmsmAKCVOGbWYJtX/AJEz/4osVAWOr1wQgCgpZx4
5uWmM4fXbshYoX1cMb5tXF8=
=5AYn
-END PGP SIGNATURE-
Accepted:
dpatch_1.20.dsc
to pool/main/d/dpatch/dpatch_1.20.dsc
dpatch_1.20.tar.gz
to pool/main/d/dpatch/dpatch_1.20.tar.gz
dpatch_1.20_all.deb
to pool/main/d/dpatch/dpatch_1.20_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#194515: ITP: debdivert -- Debian packaging aid to create patch packages
On 24 May 2003 15:40:08 +0900 Masato Taruishi [EMAIL PROTECTED] wrote: Ah, the main point of this package is to create a local ad-hoc package which can coexist with its official package. Escpecially, I can manage my temporary on-going improvement to some debian package as a debian package. I didn't think to waste official debian packages because we shouldn't upload this kind of patch packages to the official but merge the patch to the official packages if we want to share them on public. The main question is what on god's green earth does this do that dpkg-divert doesn't do? Looking at the package description, it implies that it will in fact do a lot less than dpkg-divert unless you tell it otherwise. pgpaRVCmGccgC.pgp Description: PGP signature
Re: Unofficial projects related with Debian.
On Sat, 24 May 2003 10:19:38 +0200 Enrico Zini [EMAIL PROTECTED] wrote: http://www.debian.org/devel/, Projects section: * Debian Web Pages [...] * Alioth: Debian GForge Certainly seems that they're listed. The Debian Usability Research seems to be missing: http://deb-usability.alioth.debian.org I think that's fairly new, eh? Might be a while before it shows up. (I don't know how anal the webmaster for that page is, but I know I'd give it a while to make sure it was a viable, active effort.) pgp6TA44JuDfw.pgp Description: PGP signature
Re: Unofficial projects related with Debian.
On Fri, 23 May 2003 11:58:45 -0300 Gustavo Franco [EMAIL PROTECTED] wrote: Hi, Why Debian Desktop subproject is on official website and many others[1] aren't? The Debian Desktop is a good initiative, but there are many others that are being excluded from the website.I've some ideas: - Guidelines to Debian subprojects (Do you known what are the official and unofficial subprojects now?); - List the subprojects in two areas of the website: * Developers' corner, to subprojects in initial state; * A new area called: Subprojects, containing full information about the subprojects considered mature. [1] = Mono for Debian, ipv6 (is it official or unofficial?), ddtp, ... http://www.debian.org/devel/, Projects section: * Debian Web Pages * Debian archive * Debian Documentation Project (DDP) * The X Strike Force * The Quality Assurance group * Debian GNU/Linux CD images * The sponsorship program * The key signing coordination page * Debian IPv6 Project * Debian Jr. Project * Debian-Med Project * Debian-Edu Project * Debian-Lex Project * The Debian Desktop Project * Automatic package building system * Technical Committee * Debian Description Translation Project (DDTP) * Alioth: Debian GForge Certainly seems that they're listed. pgps6ZrYkKk9O.pgp Description: PGP signature
Re: What makes a debconf?
On Fri, 23 May 2003 17:33:58 -0700 Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote: Debconf is about Debian developers trying to meet other devels and users. Its about trying to make us a stronger organization. Its about hacking and all of the other reasons we love Debian. Treating it like a Comdex, a Linux World or anything else just seems wrong. The problem is that people who can get expenses reimbursed need to have a focus. Sponsors need to have a focus. There needs to be a major conference for these kinds of things; in other words, it has to be billed as something more than just a bunch of people getting together, even if that's what *all* conferences are at heart. If a Debian Developer's employer is willing to let them go to one trade conference a year, expenses paid or partially paid, and the options are one of a dozen Debian conferences or LinuxWorld, their employers will say LinuxWorld. If, on the other hand, the options are one of a dozen Debian conferences, Debconf, and LinuxWorld, their employers will likely allow either of the last two. Developers should feel encouraged to declare a conference whenever and whereever they can make one. If one of us can organize a meet and people will show up that makes a conference. Of course, but Debconf is a specific term. If you're arguing that it isn't, then we need to come up with another one, that denotes an annual Debian conference that's official in nature :) See above. I'm really not trying to say that people can't get together when they want to. Just saying that having something people can *focus* on is a benefit to the community. So an annual or semi-annual Debconf is good, even if all that _really_ distinguishes it from the rest is that we don't call two conferences Debconf within the same six/tweleve-month time frame :) pgpldMJDrEpvJ.pgp Description: PGP signature
Re: Time to package simpleinit?
On Sat Apr 26, 07:36pm +0200, Joachim Breitner wrote: * The /etc/init.d/ scripts would need to add need otherscript (and sometimes provide something). As I think it is a very bad idea to edit these scripts in our post-install (and try to reedit them in pre-remove)) one would have to file bugs agains packages with /etc/init.d scripts. Will that be sucessfull? How cooperative will the maintainers of these script be? I second Matthew Palmer and Henrique's sentiments. Matthew's in that if you do all the work for me, I'll merge it (likely quickly :). And Henrique's in that it needs to be fairly generic. pgp0FlsmzWqA1.pgp Description: PGP signature
Re: irssi-text - Not quite a release-critical bug
On Wed Apr 23, 09:35pm +0200, Wilmer van der Gaast wrote: Bug 183186 seems to be stopping irss-text 0.8.6 from entering Sarge, but IMHO the bug is not quite release critical. Botti is just a small part of irssi, not used by 90% of the package users (at least, I think so). (Maybe it should be split into a separate package anyway?) Can this bug be put back to normal priority? I can't even reproduce it in Sid's Irssi. pgpj8bLD1Ecma.pgp Description: PGP signature
Re: stop abusing debconf already
On Mon Apr 21, 10:05am -0500, Steve Greenland wrote: On 19-Apr-03, 11:44 (CDT), David B Harris [EMAIL PROTECTED] wrote: From debconf-devel(8): low: Very trivial items that have defaults that will work in the vast majority of cases; oinly control freaks see these. If you have a package that is asking only medium and lower priority debconf questions, then debconf should not be used at all. Those priorities *exist* because there are packages that have a high-priority, non-defaultable question, and once you've broken the conffile system, you might as well include those questions. Perhaps it was a bad idea. Another use for those lower priorities is for notes to the admin. I contend that this second use *is* a bad idea, because the common implementation is to NOT include the same information under /usr/share/doc/pkg, and thus those of us who have low and medium priority turned off lose that info. I never said otherwise, and in fact I have followed that practice myself. pgpK4f2EaPA2M.pgp Description: PGP signature
Re: stop abusing debconf already
On Sat Apr 19, 11:18am -0500, Steve Greenland wrote: On 19-Apr-03, 06:47 (CDT), Steve Kowalik [EMAIL PROTECTED] wrote: At 7:22 pm, Saturday, April 19 2003, Denis Barbier mumbled: I do not understand exactly what is good and bad use of debconf. For instance all questions asked by the debconf package have good default values, so there is no reason to prompt user, a configuration file is enough. So what am I missing? Well, not all use of debconf is bad. For example, libnet-perl is a terrible misuse of debconf, *but* it can be remedied by dropping the priority of the questions from medium to low. Huh? If all the questions it asks can be converted to priority low, then that means there are reasonable defaults, and therefore IT SHOULDN'T BE USING DEBCONF AT ALL. How hard is this? What is so unclear about Policy on this topic? From debconf-devel(8): low: Very trivial items that have defaults that will work in the vast majority of cases; oinly control freaks see these. pgpWKYL2Wz8BY.pgp Description: PGP signature
[david@eelf.ddts.net: Re: why do we care about configuration files?]
On Fri Apr 18, 11:15am -0400, Colin Walters wrote:
Perhaps I've been overly strong with the rhetoric. Let me give two
realistic scenarios where this manage foo with debconf? fails.
I like your two real-world examples, and I'd like to present a third.
3) Impatient but advanced user
Somebody who dislikes being asked repeatedly whether or not a
conffile can be overwritten. This user has tested xserver-xfree86's
debconf interface, and has taken the time to understand how
xserver-xfree86's postinst generates the configuration file based on
the debconf information. He is very confident in it doing the right
thing, and doesn't want to be bothered on each upgrade about whether
or not it can overwrite it. More importantly, this user knows full
well that, in the very rare circumstance where it *does* break, he
can easily fix it within minutes.
This user will likely feel the same way about almost all
debconf/postinst-managed configuration files, excepting the few which he
knows will break repeatedly. He doesn't want to get asked 50 may I
overwrite your file? questions each upgrade. He knows that in the time
spent reading and answering all those questions, he could just has
easily fixed the two cases of breakage. Which he would have to do in
addition to answering the questions, were they forced upon him.
I liked the concept behind your suggestion of managed and unmanaged
configuration files. I would, however, suggest a slightly different
interface:
1) Package has a configuration file which can (optionally) be managed
debconf/postinst
2) Package's .config asks, *once* (respecting debconf seen flag), the
following question:
File /etc/foo/bar can optionally be managed by this package's
maintenance scripts in an automated manner. How would you like
changes to /etc/foo/bar to be handled?
ask-no: If /etc/foo/bar will be changed, ask first. Default to
`no'
ask-yes: If /etc/foo/bar will be changed, ask first. Default to
`yes'
always-no: Never automatically overwrite /etc/foo/bar, don't even
ask.
always-yes: Always automatically overwrite /etc/foo/bar, don't even
ask (warning: dangerous).
ask-no
ask-yes
always-no
always-yes
3) That question should be standard amongst all packages, identical. It
should always be of priority medium.
4) A standard interface for ask-yes and ask-no would also be required,
similar to dpkg's conffile handling.
For ask-* interfaces, debconf's seen flag should (obviously) be
ignored, since it's *meant* to be asked repeatedly.
After some feedback, I will implement said standard interfaces as
example. I kind of like the idea of
/etc/conffiles/{managed,unmanaged,default}. That could easily be used as
the backend storage for the standard {ask,always}-{no,yes} question.
pgpddpFF01dCy.pgp
Description: PGP signature
Re: [david@eelf.ddts.net: Re: why do we care about configuration files?]
Apologies for starting a new thread, I accidentally replied to Colin privately, and instead of re-writing the email, I simply forwarded it. Bad clal :) pgpLvG6UUTUOa.pgp Description: PGP signature
Re: stop the manage with debconf madness
On Fri Apr 18, 12:54pm -0500, Manoj Srivastava wrote: On 18 Apr 2003 11:55:09 -0400, Colin Walters [EMAIL PROTECTED] said: So, opinions? Yeah, it's kind of gross. But the way things are now is far worse. As long as /etc/conffiles/managed, /etc/conffiles/unmanaged, and /etc/conffiles/default are never themselves unmanaged, this would work. And the factory default for /etc/conffiles/default should be managed; and the other two files should be empty. If we standardize on a easy to interpret format for these files, I'll add the logic to ucf to handle these directives. (how about a configuration file path per line for /etc/conffiles/managed and /etc/conffiles/unmanaged, and /etc/conffiles/default contain a single word, which is managed by default; anything other than unmanaged is interpreted as managed?). Something else worth thinking about, which I was gonna throw in my example package for all this stuff, is config-file-change priority. ie: It would be nice to differentiate between the entire config format has changed, I will break completely if the old one is used, some parameter options have changed; the old ones will still work - for now, I just changed some defaults, keep what they have now, and I fixed a typo in one of the documentation comments. We could then respect things like DEBCONF_PRIORITY, and not bother the user if all we've changed is the spelling of a descriptive (ie: not example) word in a comment. Pet peeve of mine in dpkg conffile handling :) pgp9z3wRbXkEU.pgp Description: PGP signature
Re: [david@eelf.ddts.net: Re: why do we care about configuration files?]
On Fri Apr 18, 05:28pm -0400, Colin Walters wrote:
1) Package has a configuration file which can (optionally) be
managed
debconf/postinst
This is already the way things are now; a package doesn't have to do
anything special to create configuration files in its postinst.
Yeah, I was just setting out the scenario.
2) Package's .config asks, *once* (respecting debconf seen flag), the
following question:
Uggg. We should be extremely hesitant about changing
/etc/conffiles/{managed,unmanaged,default} in maintainer scripts. I
mean they exist solely *because* of the problems of changing
configuration files in maintainer scripts :)
I think this is the *perfect* place for maintainer scripts. We can make
the format extraordinarily simple, such that anybody who is capable of
writing a maintainer script can take 60 seconds to parse it and write it
out. It could be as simple as:
if [[ $always_yes = true ]]; then
grep -v '^/etc/foo/bar$' /etc/conffiles/managed $tempfile cp
$tempfile /etc/conffiles/managed
if ! grep '^/etc/foo/bar$' /etc/conffiles/unmanaged; then
echo /etc/foo/bar /etc/conffiles/unmanaged
fi
fi
I may have the meanings of unmanaged and managed backwards :)
The root of this problem isn't that maintainers are changing config
files in postinst scripts; the root is that those scripts aren't smart
enough to parse those config files and preserve user changes.
I don't think we should use Debconf to prompt on each package
installation like this. Your proposal would make the medium debconf
priority far more painful than it is even now. Just think about how
many prompts you'd have to go through on an initial installation. It
would be at least a hundred.
I dunno. I agree that it's unpleasant, but at least it'd only have to be
done once. (And that's a common strength in Debian; you usually only
need to do things once, as unpleasant as it might be. I think the
tradeoff has worked really well thus far.)
If /etc/conffiles/* *only* lists files that could possible be managed by
postinsts, then I could live with the question never being asked,
instead being maintained manually through editing /etc/conffiles.
Basically, it seems to me that in your use case, the user could just:
echo managed /etc/conffiles/default
Yeah, I'm starting to think this.
And then explicitly list those files they want to keep unmanaged in
/etc/conffiles/unmanaged.
Now, it would be nice if at the end of a package installation run, dpkg
said something like:
The following new configuration files have been installed:
Managed:
/etc/foo/foo.conf
/etc/blah.config
Unmanaged;
/etc/whee/moo.conf
That way if you see something you want to maintain yourself, you drop it
into /etc/conffiles/unmaanaged.
Aaah. That's good, I like that.
But I dunno, the scenario I brought up would still remain. Even if a
file is in /etc/conffiles/managed, the user still needs to be asked if
it's okay to overwrite it, unless they tell the system otherwise.
How will we let them tell it otherwise?
I'm thinking in the may I upgrade your configuration file? question,
have the options I mentioned before (no, yes, always-no).
With no and yes being one-time-only things, always-no removing the
line from /etc/conffiles/managed and adding it to
/etc/conffiles/unmanaged.
How's that sound? It's unobtrusive, only adding a third option. We
ensure that /etc/conffiles/* is *extroardinarily* easy to deal with (we
can have a tool to do this for us, akin to
update-rc.d/update-inetd/etc), they'll only get changed when the user
tells us to change them, they're perfectly capable of changing it
themselves manually, and we end up with no more questions than we have
now.
pgp0J7QWh2iZv.pgp
Description: PGP signature
Re: [david@eelf.ddts.net: Re: why do we care about configuration files?]
On Fri Apr 18, 07:06pm -0400, David B Harris wrote: I'm thinking in the may I upgrade your configuration file? question, have the options I mentioned before (no, yes, always-no). How's that sound? It's unobtrusive, only adding a third option. We ensure that /etc/conffiles/* is *extroardinarily* easy to deal with (we can have a tool to do this for us, akin to update-rc.d/update-inetd/etc), they'll only get changed when the user tells us to change them, they're perfectly capable of changing it themselves manually, and we end up with no more questions than we have now. Gar. We'd still need always-yes to deal with the case I raised. Don't like it, but ... pgpwpHDeAJjRA.pgp Description: PGP signature
Re: [david@eelf.ddts.net: Re: why do we care about configuration files?]
On Fri Apr 18, 06:37pm -0500, Manoj Srivastava wrote: If you use ucf like mechanisms, and you acpet the first debconf generated file, then you will never be asked to over write your file -- since the md5sum of the installed file shall match the previous maintainer version. Bingo, we cater to all these use cases at once. Wouldn't that only be accurate if the postinst generated an identical config file every time? pgp88NKTvdObo.pgp Description: PGP signature
Re: Bug#189566: amavisd-new: bad interaction with package amavis-ng
On Sat Apr 19, 10:22am +1000, Brian May wrote: Any ideas? Share an initscript between them, if that's possible? pgp2vmAEIdmO0.pgp Description: PGP signature
Re: Bug#188564: ITP: exim-mysql -- An MTA (Mail Transport Agent) with mysql backend support.
On Fri Apr 11, 11:47am +0200, Philipp Kern wrote: * Package name: exim-mysql Version : 3.36 I already packaged with one (exim compiled with mysql and tls support). I needed it personally, with the provided debian exim package a recompile is necessary to use a mysql backend. debian package mirror: http://draenor.its-toasted.org/~phil/deb-pkgs distribution: unstable component: unofficial For what it's worth, exim4-daemon-heavy includes MySQL support; this package isn't in the archive yet, I grabbed it from q.bofh.de at some point, and that's stopped working. The package was from a team working on exim 4.x packaging, presumably it'll be uploaded to the archive eventually (though eventually may be far enough into the future to warrant this package, given how slow they're going at it). pgpydj4zb7MyI.pgp Description: PGP signature
Re: Bug#188564: ITP: exim-mysql -- An MTA (Mail Transport Agent) with mysql backend support.
On Fri Apr 11, 02:25pm +0200, Andreas Metzler wrote: http://pkg-exim4.alioth.debian.org/ Ack, sorry, I didn't realise you guys were uploading to experimental now :) pgp5PKNAFgS4V.pgp Description: PGP signature
Accepted sopwith 1.6.0-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Mar 2003 03:17:31 -0500 Source: sopwith Binary: sopwith Architecture: source i386 Version: 1.6.0-3 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: sopwith- port of the 1980's side-scrolling WWI dogfighting game Closes: 185449 Changes: sopwith (1.6.0-3) unstable; urgency=low . * debian/rules: ensure $(CFLAGS) gets passed to ./configure * Convert to dpatch to modify upstream source: + debian/patches/90_ctrlkeyfix.dpatch: - Allow both left and right control keys to be used in CTRL+C for quitting (previously only left was allowed). Thanks to Tollef Fog Heen for pointing this out. - Document using CTRL+C to quit in sopwith.6 manpage (Closes: #185449) + debian/patches/00list: Add 90_ctrlkeyfix * debian/menu: Execute /usr/games/sopwith, not /usr/bin/sopwith * debian/control: Add Suggests: menu ( 1.5) Files: c89882fa4685ff6719b2af3f9d33 598 games optional sopwith_1.6.0-3.dsc a89fde17efcdc679740af12708e3b380 24374 games optional sopwith_1.6.0-3.diff.gz 1a268f4a7f3004395ae3fa83081a7c6d 51418 games optional sopwith_1.6.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+gEe3s10SPRMEYVURAgvKAJ41v+MoU6ALWUpvWeXLrOFRHMYagACdHhW4 VYld7cu3l2MqOe7b6Usw72o= =8Tfc -END PGP SIGNATURE- Accepted: sopwith_1.6.0-3.diff.gz to pool/main/s/sopwith/sopwith_1.6.0-3.diff.gz sopwith_1.6.0-3.dsc to pool/main/s/sopwith/sopwith_1.6.0-3.dsc sopwith_1.6.0-3_i386.deb to pool/main/s/sopwith/sopwith_1.6.0-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sopwith 1.6.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 13 Mar 2003 09:54:35 -0500 Source: sopwith Binary: sopwith Architecture: source i386 Version: 1.6.0-2 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: sopwith- port of the 1980's side-scrolling WWI dogfighting game Changes: sopwith (1.6.0-2) unstable; urgency=low . * Fixed punctuation inconsistency in Description. * Start using dh_install. * Put the sopwith binary in /usr/games, where it belongs. Files: 21684a889e5173b80b0544a2b4502f2a 580 games optional sopwith_1.6.0-2.dsc de60b17c097fbd3a31207fa336d5e3c5 23386 games optional sopwith_1.6.0-2.diff.gz 2fe0c9950b3da411dc4c0bd4353a37f4 51310 games optional sopwith_1.6.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+c6sOmHaJYZ7RAb8RAl5rAJ4xEGCkR80L2sXv+DTTQO0Ph//ihgCeNquZ GZwtLrHUlhjatXC09bF3CgU= =SQzx -END PGP SIGNATURE- Accepted: sopwith_1.6.0-2.diff.gz to pool/main/s/sopwith/sopwith_1.6.0-2.diff.gz sopwith_1.6.0-2.dsc to pool/main/s/sopwith/sopwith_1.6.0-2.dsc sopwith_1.6.0-2_i386.deb to pool/main/s/sopwith/sopwith_1.6.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gqmpeg 0.20.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 22 Feb 2003 04:19:39 -0500
Source: gqmpeg
Binary: gqmpeg
Architecture: source i386
Version: 0.20.0-1
Distribution: unstable
Urgency: low
Maintainer: David B Harris [EMAIL PROTECTED]
Changed-By: David B Harris [EMAIL PROTECTED]
Description:
gqmpeg - a GTK+ front end to mpg321/mpg123 and ogg123
Closes: 155481 172504
Changes:
gqmpeg (0.20.0-1) unstable; urgency=low
.
* New upstream release (Closes: #155481)
* Update config.{sub,guess} (Closes: #172504)
* Support DEB_BUILD_OPTIONS, bringing standards-version up to 3.5.8.0
Files:
131105cfb46081ed75f60f725534d1d4 614 sound optional gqmpeg_0.20.0-1.dsc
18cc9e61969552fd6dabfded53907227 966991 sound optional gqmpeg_0.20.0.orig.tar.gz
6b769343000b2d1dcc671feacbbb3b8f 16845 sound optional gqmpeg_0.20.0-1.diff.gz
7a8fb75849f0471dfcb2933727bc8baa 626214 sound optional gqmpeg_0.20.0-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+YQBXHPo+jNcUXjARApnoAJ4wRPai7Rseya9r8vZKiNzBDuIn5ACfZ1hD
22A1+5vCYNBtZ4bCdVvaNvQ=
=pDZR
-END PGP SIGNATURE-
Accepted:
gqmpeg_0.20.0-1.diff.gz
to pool/main/g/gqmpeg/gqmpeg_0.20.0-1.diff.gz
gqmpeg_0.20.0-1.dsc
to pool/main/g/gqmpeg/gqmpeg_0.20.0-1.dsc
gqmpeg_0.20.0-1_i386.deb
to pool/main/g/gqmpeg/gqmpeg_0.20.0-1_i386.deb
gqmpeg_0.20.0.orig.tar.gz
to pool/main/g/gqmpeg/gqmpeg_0.20.0.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gmrun 0.8.1-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 23 Jan 2003 01:51:56 -0500 Source: gmrun Binary: gmrun Architecture: source i386 Version: 0.8.1-2 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: gmrun - Featureful CLI-like GTK+ application launcher Changes: gmrun (0.8.1-2) unstable; urgency=low . * src/main.cc: If the user hasn't set any position prefs (Top or Left directives), then center the window. Files: 74fd93901ddd754373f4f768851159f7 573 x11 optional gmrun_0.8.1-2.dsc d65c1768b8e4fb983e24c40b8be697f5 27410 x11 optional gmrun_0.8.1-2.diff.gz 028633071a9b9fee4e2ad0231ac5599e 48764 x11 optional gmrun_0.8.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+YP+fHPo+jNcUXjARAi0MAKCPund8O+1auPP8VORgfRSzsSrPlgCePa45 BEz0o5Z2/QtMbBkeRuxHAHs= =0ont -END PGP SIGNATURE- Accepted: gmrun_0.8.1-2.diff.gz to pool/main/g/gmrun/gmrun_0.8.1-2.diff.gz gmrun_0.8.1-2.dsc to pool/main/g/gmrun/gmrun_0.8.1-2.dsc gmrun_0.8.1-2_i386.deb to pool/main/g/gmrun/gmrun_0.8.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted snac 0.3-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 1 Mar 2003 11:39:49 -0500 Source: snac Binary: snac Architecture: source i386 Version: 0.3-3 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: snac - Complete algebraic calculator for GNOME Changes: snac (0.3-3) unstable; urgency=low . * Update maintainer email address to [EMAIL PROTECTED] * Support DEB_BUILD_OPTIONS nostrip and noopt, bringing standards-version up to 3.5.8.0 * Ensure that there are sensible defaults for colours (previously, all colours were set to black, foreground and background alike :) Files: 850f8a98df99de3c12933ccdaa46c8bc 563 utils optional snac_0.3-3.dsc c8ae200a48b25cbc4753638fa55edd76 20530 utils optional snac_0.3-3.diff.gz 6b2de5b28079ce3435ce750075ee18fc 25920 utils optional snac_0.3-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+YQIJHPo+jNcUXjARAkzeAJ9jklV9Din4EtC8zDAp+eGpZ/Ka0QCfcnYa dC8WpJ1B/pTZ6sYxRrE5E9I= =6Lvh -END PGP SIGNATURE- Accepted: snac_0.3-3.diff.gz to pool/main/s/snac/snac_0.3-3.diff.gz snac_0.3-3.dsc to pool/main/s/snac/snac_0.3-3.dsc snac_0.3-3_i386.deb to pool/main/s/snac/snac_0.3-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted shaper 2.2.12-0.7-3 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 22 Feb 2003 04:41:12 -0500 Source: shaper Binary: shapecfg shaper Architecture: source all powerpc Version: 2.2.12-0.7-3 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: shapecfg - Bandwidth limiter for virtual network interfaces shaper - Traffic Shaper init script for Linux Closes: 156270 Changes: shaper (2.2.12-0.7-3) unstable; urgency=low . * Make cron.d script check for the existence of /etc/shaper before running (Closes: #156270) Files: 08bd69d0a51ff6af3d549a9c49ecd3f7 584 net extra shaper_2.2.12-0.7-3.dsc b5b84456453dcdcae1191de3b0d3aaf8 9785 net extra shaper_2.2.12-0.7-3.diff.gz 6df7bf2f79130e4f0401aeadbb005b48 99828 net extra shaper_2.2.12-0.7-3_all.deb 26bd8f0351053c0e93a8cf7018c32625 8744 net extra shapecfg_2.2.12-0.7-3_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+WGcBvjztR8bOoMkRAjDBAKDlriZfyQ+eXmmrG20vdiwUDJt3uACgi3Gl WUqabz/L5IaBha19hCzghXo= =H2tq -END PGP SIGNATURE- Accepted: shapecfg_2.2.12-0.7-3_powerpc.deb to pool/main/s/shaper/shapecfg_2.2.12-0.7-3_powerpc.deb shaper_2.2.12-0.7-3.diff.gz to pool/main/s/shaper/shaper_2.2.12-0.7-3.diff.gz shaper_2.2.12-0.7-3.dsc to pool/main/s/shaper/shaper_2.2.12-0.7-3.dsc shaper_2.2.12-0.7-3_all.deb to pool/main/s/shaper/shaper_2.2.12-0.7-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gmrun 0.8.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 10 Jan 2003 02:20:28 -0500
Source: gmrun
Binary: gmrun
Architecture: source i386
Version: 0.8.1-1
Distribution: unstable
Urgency: low
Maintainer: David B Harris [EMAIL PROTECTED]
Changed-By: David B Harris [EMAIL PROTECTED]
Description:
gmrun - Featureful CLI-like GTK+ application launcher
Changes:
gmrun (0.8.1-1) unstable; urgency=low
.
* New upstream release
* Update config.{sub,guess} to latest versions
* Update to standards-version 3.5.8.0
Files:
be35f861f678bcf5ae82fcc297fdc9b6 573 x11 optional gmrun_0.8.1-1.dsc
b400f09e83bab0b6949dc159c6f27319 66831 x11 optional gmrun_0.8.1.orig.tar.gz
5812a14181e59780d2d3e8a89c8f86ee 26791 x11 optional gmrun_0.8.1-1.diff.gz
9406b0ea584de9fe10aaa7c055cdda79 48744 x11 optional gmrun_0.8.1-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+IA0pQSseMYF6mWoRAsrEAJ9M1GHIREHoJ6gEOYJ9wPL1iuEVlQCgnowR
p+FdrDa9JyYl7ZwZBIc60Z4=
=reYh
-END PGP SIGNATURE-
Accepted:
gmrun_0.8.1-1.diff.gz
to pool/main/g/gmrun/gmrun_0.8.1-1.diff.gz
gmrun_0.8.1-1.dsc
to pool/main/g/gmrun/gmrun_0.8.1-1.dsc
gmrun_0.8.1-1_i386.deb
to pool/main/g/gmrun/gmrun_0.8.1-1_i386.deb
gmrun_0.8.1.orig.tar.gz
to pool/main/g/gmrun/gmrun_0.8.1.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: description writing guide
On Sat, 7 Dec 2002 11:51:03 +0100 Martin Schulze [EMAIL PROTECTED] wrote: It is a bad practice to repeat the package name as the first word in the long description. Why is that again? Also the URL does not belong into the description but should be placed in the debian/copyright file instead. Joey might have said that, but I believe the consensus was it's a nice feature. The description is not a random dumping-ground for information, but what information we include is entirely arbitrary. If people like having the URL in the description (and they do), there's no reason why it shouldn't be included unless you want to make a case for Packages.gz bloat. pgp8Qr6wqeOwI.pgp Description: PGP signature
Re: description writing guide
On Thu, 5 Dec 2002 12:13:57 +0100 Michael Piefel [EMAIL PROTECTED] wrote: Line breaks already aren't preserved, and there already exist a very specific set of rules for that. Look into your documentation, and have a look at dselect. I already have example applications which don't preserve them :) packages.d.o was just one such example. Could you point me at the documentation in question? pgpZ1ILPPpLkT.pgp Description: PGP signature
Re: description writing guide
On Thu, 5 Dec 2002 20:59:09 +0100 Javier Fernández-Sanguino Peña [EMAIL PROTECTED] wrote: a good search interface in our package interface UIs (good search != search by words). ... as opposed to searching based on the contents of people's minds? :) pgphxF5io44ke.pgp Description: PGP signature
Re: Mozilla Calendar?
On Wed, 4 Dec 2002 12:55:35 +0200 [EMAIL PROTECTED] (Sami Haahtinen) wrote: In the past the only thing that stopped me from doing a build of my own from the sources was that debian missed libical.. and now that there appears to be libical-dev, i can't see any reason why not package it.. Yes, looks like it was uploaded somewhere near the end of September. Regardless, newer versions of Mozilla Calendar don't need it. :) pgp9rG0oGCoS7.pgp Description: PGP signature
Re: description writing guide
On 04 Dec 2002 12:55:50 -0500 Colin Walters [EMAIL PROTECTED] wrote: http://people.debian.org/~walters/descriptions.html Thanks. pgpfyKOIrBIap.pgp Description: PGP signature
Re: description writing guide
On 04 Dec 2002 12:55:50 -0500 Colin Walters [EMAIL PROTECTED] wrote: http://people.debian.org/~walters/descriptions.html I do have some differences of opinion, though. It's sad, but there are a getting to be a fairly large number of DDs who are attention grabbers. Just a few days ago, I saw a package description that said something along the lines of this is the best package for this purpose ... and it certainly wasn't. Even if it was, I think everybody would agree that that kind of language doesn't belong in a Debian package description. So, the opening section that talks about advertising and whatnot will probably give these sorts of people the wrong idea; I'd ammend it to: Debian package descriptions are the first avenue for you to give your audience relevant, useful information about your package. When you attempt to give somebody new knowledge, the key idea is to emknow your audience/em. Also, I'm not sure I agree with the third paragraph; everything in it is factual and well-said, but it'd be nice if somebody who *didn't* know what GTK+ and RAD are could know conclusively, this is not what I want. When you're looking for something specific, but don't know the exact package name, the process of elimination is the best start. I know I, *personally*, have installed packages which I couldn't immediately rule out from the package description because I didn't *quite* understand the jargon. glade is a bad example for my point, though, because it has a great description :) In paragraph five (So how can we better target these users?), I'd s/minimum/appropriate amount/. I've seen bloody jihads in very well-known projects to give only the minimum of technical jargon, and people invariably take it to far. Had they just stressed appropriateness of the text to the audience, things would have been much more reasonable. In paragraph six, (So far we've mainly discussed the synopsis line), I'd s/competition/alternatives/; s/advertisement/good documentation/. (BTW, if you totally disagree with me about this advertisement stuff, do replace all references to advertisements with good advertisements and whatnot :) Also, in the description template, two spaces are used after a period - is that standard nowadays? (My understanding was that they were primarily used for variable-width fonts, where a single space would take up very little page space. Since the descriptions should be presented in a fixed-width font (for many reasons, this also includes GUI package browsers), they're a bit redundant.) Thanks again :) pgpvz7X4QJZE4.pgp Description: PGP signature
Re: description writing guide
On 04 Dec 2002 19:19:38 + Scott James Remnant [EMAIL PROTECTED] wrote: In correct English grammar and typography the space after a full stop (period in Merkin) is supposed to be a wider space then that between words and after commas and suchlike. Ahh, allright, so there's still reason to be using them, at least in fixed-width fonts. I personally, though, suggest we just do away with it :) pgpzq11f5gZjV.pgp Description: PGP signature
Re: description writing guide
On Wed, 4 Dec 2002 11:33:35 -0800 Craig Dickson [EMAIL PROTECTED] wrote: I don't see any reason why package descriptions shouldn't be presented in variable-width fonts. The right margin might look a bit ragged (assuming the program preserves line breaks, which is probably a good idea to avoid messing up bulletted lists in the description), but so what? Package descriptions don't usually include tabular data that would be seriously messed up by variable-width fonts. Just for looks, and to allow some flexibility on the part of the description writer. If variable-width fonts are used, then line breaks shouldn't be preserved. If they're not going to be preserved, there needs to be a very specific set of rules as to how lines are joined. These already exist in code, actually; I believe packages.debian.org joins lines. pgpgVk65NIWMv.pgp Description: PGP signature
Accepted gqmpeg 0.19.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 3 Dec 2002 16:43:52 -0500 Source: gqmpeg Binary: gqmpeg Architecture: source i386 Version: 0.19.0-1 Distribution: unstable Urgency: low Maintainer: David B Harris [EMAIL PROTECTED] Changed-By: David B Harris [EMAIL PROTECTED] Description: gqmpeg - a GTK+ front end to mpg321/mpg123 and ogg123 Closes: 155481 Changes: gqmpeg (0.19.0-1) unstable; urgency=low . * New upstream release (Closes: #155481) * s/common-license/common-licenses/ in debian/copyright (oops! thank you lintian) Files: f9e28176488ee6c3563af3b143045f32 613 sound optional gqmpeg_0.19.0-1.dsc c0c4568bd85d679a9dc7f7a01b0269b3 961647 sound optional gqmpeg_0.19.0.orig.tar.gz c686401dad655e11649f10de8a5deb7b 3982 sound optional gqmpeg_0.19.0-1.diff.gz 7af70c77a19967467eeb8f02f9001ad5 616284 sound optional gqmpeg_0.19.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE97S4QR47eFMOy/N4RAmV0AJ0XDzcnAh7W82ubgUarBAXdbGx3KwCdF8Y0 ESSkTuysEpFSW758HXO8WO8= =YjoU -END PGP SIGNATURE- Accepted: gqmpeg_0.19.0-1.diff.gz to pool/main/g/gqmpeg/gqmpeg_0.19.0-1.diff.gz gqmpeg_0.19.0-1.dsc to pool/main/g/gqmpeg/gqmpeg_0.19.0-1.dsc gqmpeg_0.19.0-1_i386.deb to pool/main/g/gqmpeg/gqmpeg_0.19.0-1_i386.deb gqmpeg_0.19.0.orig.tar.gz to pool/main/g/gqmpeg/gqmpeg_0.19.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Are we losing users to Gentoo?
On Sat, 30 Nov 2002 23:27:33 +1300 Nick Phillips [EMAIL PROTECTED] wrote: Given the ISO mirroring situation? Care to elucidate? There being an order of magnitude more package mirrors than ISO mirrors. Completely ignoring the web site organisation, mind you, it's been common for a long time for people to encourage network-based installs, or anything other than downloading full 640M ISOs. Part of it, of course, is to enhance the user experience - users will rightfully go with full 640M ISOs because it's been their experience in the past that a) it was required, and b) shit broke often enough that they needed to reinstall. Almost everybody I got to do a 'net install never had any problems whatsoever, and they were EXTREMELY delighted. Had they gone wish the full 640M ISO, they'd have been happy, but they wouldn't have had as good an idea as to how things *can* work, when it's done right :) pgpZo7vImmMrN.pgp Description: PGP signature
Re: Are we losing users to Gentoo?
On Sat, 30 Nov 2002 16:06:40 -0500 Joey Hess [EMAIL PROTECTED] wrote: The problem with the net installs isos is mainly that they are unofficial and there are several varying cd's produced by different folks, and of varying quality (though quality is overall good; I've used them happily in the past). If we really want to promote them more it would be good to set things up so they can be generated from the debian-cd package, and make them official debian isos. Of course debian-installer should support 1.4 mb net install floppies too. But still if someone wants a whole debian CD, for whatever reasons, I'd rather they could easily find it, especially if they are a newcomer to debian. Agreed, on all counts :) pgpLK5R1aKajL.pgp Description: PGP signature
New thread about people switching to other distributions
Hey there :) I'm starting a new thread about people switching to other distributions. Why? Because I'd rather we start first with an information-gathering thread. I'm shortly going to relate my first-hand knowledge of why people have switched from Debian, to Gentoo. Everybody else who has any first-hand knowledge about it, please relate your experiences too. Also, if you know of somebody who was thinking Hmmm, Debian or Gentoo?, and they chose Gentoo, do tell why. (I don't know anybody who's been in that situation, unfortunately. I think they've probably got great insights. Joey's comments on the web site would probably also come from somebody in this group of Gentoo users.) If you don't have any first-hand knowledge, please don't respond to this thread. We'll start a what do we do with this knowledge now? thread later. Okay, so, my experiences. I've watched about three dozen people from #debian switch to Gentoo. About two dozen of them switched simply because it was cool. I mean, these people showed up in #debian because they had tried Slackware and failed miserably (yes. This happens like every other day). Now they were trying Debian, because it was the next step up in the coolness meter. No, I'm not just assuming these people are idiots :) I actually talk to them privately, help them out, and whatnot. The other third of people I've watched switched just wanted something new to play with. Would have been FreeBSD, probably, if Gentoo hadn't been around. Most of them have already tried SuSE, Mandrake, Red Hat, and their ilk. One person had a very good reason - they had a client whose company policy was to use specific gcc flags (can't remember which, but IIRC they had something to do with hardware stability and debugging) - Gentoo let them do that more easily. Anybody else? pgpuDqpwBovp8.pgp Description: PGP signature
Re: Are we losing users to Gentoo?
On Fri, 29 Nov 2002 15:58:51 -0500 Joey Hess [EMAIL PROTECTED] wrote: The comparison is only fair with organizations that *want* you do do so(so not redhat, probably not openbsd, or mandrake, or others whose principal developers try to sell cds). Strictly speaking, given the ISO mirroring situation, we've never wanted people to use full 640M ISOs when we knew that 99% of people downloading would use a couple hundreds megs, at most. pgpYSbDdC8lGr.pgp Description: PGP signature
