Re: Change user used by package
Marvin Renich wrote: * Harald Braumann ha...@unheit.net [090113 05:47]: AFAIK, there's no way for multiple independent packages for using the same user. So jabber-muc needs to create its own user. On update, that's no problem. The post-install script can chown the package's directories for the new user. But a downgrade would then not be possible. The old version couldn't access the directories. Is there precedence for such a situation? How can it be resolved? Cheers, harry BTW, are you coordinating this with the current jabber-muc maintainer (CC'ed in case he is not subscribed)? I'm not subscribed, haven't been following the lists for a while. The old package should probably be removed completely in favor of the new. However, more to the point, I don't see why the two packages couldn't use the same user. Why not check during installation to see if the user account exists? If it does, use it. If not create it? -- Jamin W. Collins -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted mediamate 0.9.3.6-5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 01 Nov 2008 19:04:31 -0400 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3.6-5 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Closes: 504172 Changes: mediamate (0.9.3.6-5) unstable; urgency=low . * Use external version of class.jabber.php * Use external version of Snoopy, CVE-2008-4796 (Closes: #504172) * corrected boolean default (true v. True) * updated homepage reference in description * updated build-depends * updated docs file to remove wildcard * added patch to update IMDB parsing * updated standards vesion * moved source changes to patches where they belong * changed default web server to Apache2 Checksums-Sha1: f14b5ebb3895303aad53ed6794bb0c58a50e696d 993 mediamate_0.9.3.6-5.dsc 0ca5cd53475dd4f931838c169dc9c6cf9d7cfa1c 29366 mediamate_0.9.3.6-5.diff.gz 454ee6cbdbceeec30fce1ff2c5fa05f6dca66abc 219544 mediamate_0.9.3.6-5_all.deb Checksums-Sha256: de0c401ed3e2bbd5a8b0031ff2c89b993e5b535a8d5bec2929d4a9a02596bc8e 993 mediamate_0.9.3.6-5.dsc dd7af8845ea81551bc4537feeb2490ec0e10ab8e3b24e55027bd9387fdef2c3e 29366 mediamate_0.9.3.6-5.diff.gz 89e3e10aded7e3fd3f22522ef366cefef2ce25ed97cd8d831b0bbb803764043f 219544 mediamate_0.9.3.6-5_all.deb Files: 5f30d58bbd063e719d09d1e25a3df023 993 web optional mediamate_0.9.3.6-5.dsc ec85d6dd6ca9dabb5bdbfcea09b08882 29366 web optional mediamate_0.9.3.6-5.diff.gz 934786d310512321f6ab39e205970977 219544 web optional mediamate_0.9.3.6-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkNhmQACgkQ62zWxYk/rQeddACgy6MQ8xSbw3e6wkaZbdLAEzlj zSAAn2+2syOj1hcxmJrzqytGiEgQ9YrW =RY4v -END PGP SIGNATURE- Accepted: mediamate_0.9.3.6-5.diff.gz to pool/main/m/mediamate/mediamate_0.9.3.6-5.diff.gz mediamate_0.9.3.6-5.dsc to pool/main/m/mediamate/mediamate_0.9.3.6-5.dsc mediamate_0.9.3.6-5_all.deb to pool/main/m/mediamate/mediamate_0.9.3.6-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time to rethink ifupdown
Alexey Feldgendler wrote: Greetings to everybody on this list, it's my first post here. ifupdown, the official Debian network configuration tool, is great for configuring interfaces like Ethernet adapters. However, as time goes, more and more use cases occur which are hard to fulfill with ifupdown as it is. My guess is that it's time to rethink the philosophy behind ifupdown and give it some natural development. Beyond the need to potentially rethink its development is the existence of a rather obscure and frustrating bug #253472. The short of this bug is the ifup calls dhclient with the -e switch. This means that if at any point in the interfaces life the dhclient is unable to acquire a functional IP lease for the interface, dchclient will error and exit. This can leave a system completely unreachable. A check of the latest ifupdown sources in unstalbe (0.6.7) shows that the use of the -e switch is still present. -- Jamin W. Collins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabberd2 2.0s10-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 7 Oct 2005 09:47:16 -0600 Source: jabberd2 Binary: jabberd2-ldap-pgsql jabberd2-ldap-mysql jabberd2-mysql jabberd2-pgsql jabberd2-bdb jabberd2-ldap-bdb Architecture: source i386 Version: 2.0s10-1 Distribution: experimental Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabberd2-bdb - Jabber Open Source Instant Messenger Server (Berkeley DB) jabberd2-ldap-bdb - Jabber Open Source Instant Messenger Server (LDAP Berkeley DB) jabberd2-ldap-mysql - Jabber Open Source Instant Messenger Server (LDAP MySQL) jabberd2-ldap-pgsql - Jabber Open Source Instant Messenger Server (LDAP PostgreSQL) jabberd2-mysql - Jabber Open Source Instant Messenger Server (MySQL) jabberd2-pgsql - Jabber Open Source Instant Messenger Server (PostgreSQL) Changes: jabberd2 (2.0s10-1) experimental; urgency=low . * new upstream version Files: 6eb79e007e0a149c9afc76abb2ba9055 804 net optional jabberd2_2.0s10-1.dsc e8df4a9a5680009071204d423cff2de0 772817 net optional jabberd2_2.0s10.orig.tar.gz e08c37826e1384c52baca5fadf9bc2ff 20508 net optional jabberd2_2.0s10-1.diff.gz efb59bc2548abdb151c7c643b81fd034 551590 net optional jabberd2-bdb_2.0s10-1_i386.deb 0a2866a68d99935aa5daea0ecec7ec2b 552630 net optional jabberd2-ldap-bdb_2.0s10-1_i386.deb 316e986da7cc6dcdfb2025a9c598177c 554478 net optional jabberd2-mysql_2.0s10-1_i386.deb 93d2fa496da32e6160dce3f3cf84a400 556374 net optional jabberd2-ldap-mysql_2.0s10-1_i386.deb be39498ee87bb88a7d7be8e5abfbc452 554626 net optional jabberd2-pgsql_2.0s10-1_i386.deb 3a577d9f072cc9ee3e97aef1963ff0b4 556410 net optional jabberd2-ldap-pgsql_2.0s10-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDSRcRI49lBuo6JyYRAmQTAJ4vwIEMMax1NgqhBk+mVdD1OFT/yACggt0l CfRtL7qeKWYT/UgRuvyegSo= =SptL -END PGP SIGNATURE- Accepted: jabberd2-bdb_2.0s10-1_i386.deb to pool/main/j/jabberd2/jabberd2-bdb_2.0s10-1_i386.deb jabberd2-ldap-bdb_2.0s10-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-bdb_2.0s10-1_i386.deb jabberd2-ldap-mysql_2.0s10-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-mysql_2.0s10-1_i386.deb jabberd2-ldap-pgsql_2.0s10-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-pgsql_2.0s10-1_i386.deb jabberd2-mysql_2.0s10-1_i386.deb to pool/main/j/jabberd2/jabberd2-mysql_2.0s10-1_i386.deb jabberd2-pgsql_2.0s10-1_i386.deb to pool/main/j/jabberd2/jabberd2-pgsql_2.0s10-1_i386.deb jabberd2_2.0s10-1.diff.gz to pool/main/j/jabberd2/jabberd2_2.0s10-1.diff.gz jabberd2_2.0s10-1.dsc to pool/main/j/jabberd2/jabberd2_2.0s10-1.dsc jabberd2_2.0s10.orig.tar.gz to pool/main/j/jabberd2/jabberd2_2.0s10.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mediamate 0.9.3.6-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 5 Sep 2005 14:25:21 -0600 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3.6-4 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Closes: 312759 319627 319647 325378 Changes: mediamate (0.9.3.6-4) unstable; urgency=low . * changed location of adodb.inc.php (Closes: #325378) * added note to README.Debian about enabling php (Closes: #319647) * added vietnamese debconf translation (Closes: #312759) * added czech debconf translation (Closes: #319627) * added postinst logic to try and ensure php is enabled for apache2 Files: 23f75e9bc50e9178b3a34b0cfd95cfc1 602 web optional mediamate_0.9.3.6-4.dsc a23b0ccf98665d25e7d33cc505a1a448 19703 web optional mediamate_0.9.3.6-4.diff.gz 2307942c0b65787044865392aa95036e 224936 web optional mediamate_0.9.3.6-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDHLQdI49lBuo6JyYRAmhcAKCA5jFrLWQowX/Bgpz0QtbBBagv/ACfXS4z 7Uw7qKz1mbuQ8BsHoJEZsqE= =Sd94 -END PGP SIGNATURE- Accepted: mediamate_0.9.3.6-4.diff.gz to pool/main/m/mediamate/mediamate_0.9.3.6-4.diff.gz mediamate_0.9.3.6-4.dsc to pool/main/m/mediamate/mediamate_0.9.3.6-4.dsc mediamate_0.9.3.6-4_all.deb to pool/main/m/mediamate/mediamate_0.9.3.6-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabberd2 2.0s9-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 19 Aug 2005 08:44:10 -0600 Source: jabberd2 Binary: jabberd2-ldap-pgsql jabberd2-ldap-mysql jabberd2-mysql jabberd2-pgsql jabberd2-bdb jabberd2-ldap-bdb Architecture: source i386 Version: 2.0s9-1 Distribution: experimental Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabberd2-bdb - Jabber Open Source Instant Messenger Server (Berkeley DB) jabberd2-ldap-bdb - Jabber Open Source Instant Messenger Server (LDAP Berkeley DB) jabberd2-ldap-mysql - Jabber Open Source Instant Messenger Server (LDAP MySQL) jabberd2-ldap-pgsql - Jabber Open Source Instant Messenger Server (LDAP PostgreSQL) jabberd2-mysql - Jabber Open Source Instant Messenger Server (MySQL) jabberd2-pgsql - Jabber Open Source Instant Messenger Server (PostgreSQL) Closes: 305024 Changes: jabberd2 (2.0s9-1) experimental; urgency=low . * new upstream release (Closes: #305024) Files: 8558fd48288759290245d5ad3d3e2590 800 net optional jabberd2_2.0s9-1.dsc 64905ccbbe5c6fe1f583401802a3e303 769049 net optional jabberd2_2.0s9.orig.tar.gz f5dcf2a102798086db0d4e85d5a445a1 9719 net optional jabberd2_2.0s9-1.diff.gz 5a6beaf60a9b8662164768d02f761648 547378 net optional jabberd2-bdb_2.0s9-1_i386.deb fe5a9b8c5398b639565d52b7548a2ebb 548708 net optional jabberd2-ldap-bdb_2.0s9-1_i386.deb 49c756e8deacb51060cd762e4275708b 550670 net optional jabberd2-mysql_2.0s9-1_i386.deb 0415df0d3e4aaefbe2c0ca79dd9cc8b0 552146 net optional jabberd2-ldap-mysql_2.0s9-1_i386.deb 4e40e354f7b6e87700176d08693558eb 550840 net optional jabberd2-pgsql_2.0s9-1_i386.deb 9c4b57695bb0add33f5a01b07269b9c2 552276 net optional jabberd2-ldap-pgsql_2.0s9-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDBhGVI49lBuo6JyYRAqxSAKDNu+aq3htBRYH5zjCYs/8r25FOcACgmtde cu/t+c/P2FSfzj8IyOlTikw= =/XYV -END PGP SIGNATURE- Accepted: jabberd2-bdb_2.0s9-1_i386.deb to pool/main/j/jabberd2/jabberd2-bdb_2.0s9-1_i386.deb jabberd2-ldap-bdb_2.0s9-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-bdb_2.0s9-1_i386.deb jabberd2-ldap-mysql_2.0s9-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-mysql_2.0s9-1_i386.deb jabberd2-ldap-pgsql_2.0s9-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-pgsql_2.0s9-1_i386.deb jabberd2-mysql_2.0s9-1_i386.deb to pool/main/j/jabberd2/jabberd2-mysql_2.0s9-1_i386.deb jabberd2-pgsql_2.0s9-1_i386.deb to pool/main/j/jabberd2/jabberd2-pgsql_2.0s9-1_i386.deb jabberd2_2.0s9-1.diff.gz to pool/main/j/jabberd2/jabberd2_2.0s9-1.diff.gz jabberd2_2.0s9-1.dsc to pool/main/j/jabberd2/jabberd2_2.0s9-1.dsc jabberd2_2.0s9.orig.tar.gz to pool/main/j/jabberd2/jabberd2_2.0s9.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-aim 20040131b-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Aug 2005 16:38:33 -0600 Source: jabber-aim Binary: jabber-aim Architecture: source i386 Version: 20040131b-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-aim - Provides AIM messenger transport for Jabber IM server Closes: 286483 Changes: jabber-aim (20040131b-2) unstable; urgency=low . * added patch to correct building under gcc v4.0 (01-gcc4.0.dpatch) (Closes: #286483) * updated standards version to 3.6.2 Files: f12b14ce815b5e0344b17235f0583da1 627 net optional jabber-aim_20040131b-2.dsc c7176675badcc91fa92ef6240ea5ca74 6145 net optional jabber-aim_20040131b-2.diff.gz fa23b2a41d1df48cbd6428bee1fa21b1 82562 net optional jabber-aim_20040131b-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC/SYPI49lBuo6JyYRAnCrAJ9bR2/vvwQQF/PwwwHKbIuP5iqIxACeMTe8 +K5jzbZGapzqRVJxCaLAue8= =IK8F -END PGP SIGNATURE- Accepted: jabber-aim_20040131b-2.diff.gz to pool/main/j/jabber-aim/jabber-aim_20040131b-2.diff.gz jabber-aim_20040131b-2.dsc to pool/main/j/jabber-aim/jabber-aim_20040131b-2.dsc jabber-aim_20040131b-2_i386.deb to pool/main/j/jabber-aim/jabber-aim_20040131b-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting openswan 2.2.0 back into sarge
On Mar 24, 2005, at 2:39 AM, Rene Mayrhofer wrote: Hi all, [Please CC me in replies, I am currently not subscribed to this list.] As some have already noticed, openswan has been removed from testing a while ago, most probably because of bug #291274, which did not apply to package version 2.2.0-4 (the one that has been removed from testing). There are other problems with the 2.2.0 version such as #261892 which effectively cripples the network stack. -- Jamin W. Collins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mediamate 0.9.3.6-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Feb 2005 17:10:24 -0700 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3.6-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Closes: 232280 250380 268529 275104 277266 296644 Changes: mediamate (0.9.3.6-2) unstable; urgency=low . * added support for Apache2 (Closes: #275104) * corrected long description typo (Closes: #277266, #268529) * added German language patches (Closes: #250380) * switched to po-debconf (I think) (Closes: #232280) * debconf translation updates - French added (Closes: #296644) - Basque added - Dutch added - Danish added - Traditional Chinese added * Files: 3321d89b67578a7f9d90c6499e283062 602 web optional mediamate_0.9.3.6-2.dsc e2cb29ba09f000ceeb05a155d38e7838 17283 web optional mediamate_0.9.3.6-2.diff.gz 9ae36d93d4ecc7d433f634a090aadd55 222942 web optional mediamate_0.9.3.6-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCMz0AI49lBuo6JyYRAuLjAJ0fTuUTUDdfaZWFIdEY/IoUIsor7gCfVv6O eUwdV5g+g61/oMPSRk8Bz7c= =PKCJ -END PGP SIGNATURE- Accepted: mediamate_0.9.3.6-2.diff.gz to pool/main/m/mediamate/mediamate_0.9.3.6-2.diff.gz mediamate_0.9.3.6-2.dsc to pool/main/m/mediamate/mediamate_0.9.3.6-2.dsc mediamate_0.9.3.6-2_all.deb to pool/main/m/mediamate/mediamate_0.9.3.6-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabberd2 2.0s6-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 1 Jan 2005 12:54:22 -0700 Source: jabberd2 Binary: jabberd2-ldap-pgsql jabberd2-ldap-mysql jabberd2-mysql jabberd2-pgsql jabberd2-bdb jabberd2-ldap-bdb Architecture: source i386 Version: 2.0s6-1 Distribution: experimental Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabberd2-bdb - Jabber Open Source Instant Messenger Server (Berkeley DB) jabberd2-ldap-bdb - Jabber Open Source Instant Messenger Server (LDAP Berkeley DB) jabberd2-ldap-mysql - Jabber Open Source Instant Messenger Server (LDAP MySQL) jabberd2-ldap-pgsql - Jabber Open Source Instant Messenger Server (LDAP PostgreSQL) jabberd2-mysql - Jabber Open Source Instant Messenger Server (MySQL) jabberd2-pgsql - Jabber Open Source Instant Messenger Server (PostgreSQL) Changes: jabberd2 (2.0s6-1) experimental; urgency=low . * new upstream release Files: e699f5f54b91af67143703dfd59b732a 798 net optional jabberd2_2.0s6-1.dsc ca2818885e126181e002949c71603df3 724448 net optional jabberd2_2.0s6.orig.tar.gz 8e8fb01026c0684308e9dfc71b4f146b 9548 net optional jabberd2_2.0s6-1.diff.gz 675cbbec85ecf544dd9f7846ffcab227 561824 net optional jabberd2-bdb_2.0s6-1_i386.deb 06fe84ca771e4d556f233aaebb19ddeb 563100 net optional jabberd2-ldap-bdb_2.0s6-1_i386.deb e112b75c2128a35f5073f925403bad10 564808 net optional jabberd2-mysql_2.0s6-1_i386.deb 4f7d33adbc86e4751370466d2a21178e 566722 net optional jabberd2-ldap-mysql_2.0s6-1_i386.deb e766a7cffd500e46242f199013b94cb4 565112 net optional jabberd2-pgsql_2.0s6-1_i386.deb b402dcd1b449af105ccbbd3a187c29c4 567054 net optional jabberd2-ldap-pgsql_2.0s6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB1xC1I49lBuo6JyYRApaWAJ4rGOM5+nlPEdsOnAT5cKzFdypGaACg2/5M Pu4PVAtVoWnO5HOsx8grRM0= =+73u -END PGP SIGNATURE- Accepted: jabberd2-bdb_2.0s6-1_i386.deb to pool/main/j/jabberd2/jabberd2-bdb_2.0s6-1_i386.deb jabberd2-ldap-bdb_2.0s6-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-bdb_2.0s6-1_i386.deb jabberd2-ldap-mysql_2.0s6-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-mysql_2.0s6-1_i386.deb jabberd2-ldap-pgsql_2.0s6-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-pgsql_2.0s6-1_i386.deb jabberd2-mysql_2.0s6-1_i386.deb to pool/main/j/jabberd2/jabberd2-mysql_2.0s6-1_i386.deb jabberd2-pgsql_2.0s6-1_i386.deb to pool/main/j/jabberd2/jabberd2-pgsql_2.0s6-1_i386.deb jabberd2_2.0s6-1.diff.gz to pool/main/j/jabberd2/jabberd2_2.0s6-1.diff.gz jabberd2_2.0s6-1.dsc to pool/main/j/jabberd2/jabberd2_2.0s6-1.dsc jabberd2_2.0s6.orig.tar.gz to pool/main/j/jabberd2/jabberd2_2.0s6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabberd2 2.0s4-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 26 Nov 2004 23:58:22 -0700 Source: jabberd2 Binary: jabberd2-ldap-pgsql jabberd2-ldap-mysql jabberd2-mysql jabberd2-pgsql jabberd2-bdb jabberd2-ldap-bdb Architecture: source i386 Version: 2.0s4-2 Distribution: experimental Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabberd2-bdb - Jabber Open Source Instant Messenger Server (Berkeley DB) jabberd2-ldap-bdb - Jabber Open Source Instant Messenger Server (LDAP Berkeley DB) jabberd2-ldap-mysql - Jabber Open Source Instant Messenger Server (LDAP MySQL) jabberd2-ldap-pgsql - Jabber Open Source Instant Messenger Server (LDAP PostgreSQL) jabberd2-mysql - Jabber Open Source Instant Messenger Server (MySQL) jabberd2-pgsql - Jabber Open Source Instant Messenger Server (PostgreSQL) Closes: 283189 Changes: jabberd2 (2.0s4-2) experimental; urgency=low . * added patch to correct mysql and pgsql buffer overflow (Closes: #283189) Files: 4ac8b419c437ce8d8ca966a635d92b56 799 net optional jabberd2_2.0s4-2.dsc 2debe904218f5276543388c1738e233c 11213 net optional jabberd2_2.0s4-2.diff.gz 7c11300e1473022ffad211b8d8653687 556468 net optional jabberd2-bdb_2.0s4-2_i386.deb 56fcfa9d01006d0e9194731cc8fcfccf 557638 net optional jabberd2-ldap-bdb_2.0s4-2_i386.deb 9a5c1878501962ce7a1e219ac6859112 559570 net optional jabberd2-mysql_2.0s4-2_i386.deb 721b285c034f21bab0faa8e87fd5712b 561400 net optional jabberd2-ldap-mysql_2.0s4-2_i386.deb b817deaad912285c4f7082b67b4e087d 560052 net optional jabberd2-pgsql_2.0s4-2_i386.deb db95072a13dd97f964bfd43e1136ce79 561860 net optional jabberd2-ldap-pgsql_2.0s4-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBqLZ6I49lBuo6JyYRAkdoAJ9ckoZfVZRBl4KdADjfz3dcYFv27ACgh6RI slGCftVkYZn8z/FNV3hnjZw= =cakW -END PGP SIGNATURE- Accepted: jabberd2-bdb_2.0s4-2_i386.deb to pool/main/j/jabberd2/jabberd2-bdb_2.0s4-2_i386.deb jabberd2-ldap-bdb_2.0s4-2_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-bdb_2.0s4-2_i386.deb jabberd2-ldap-mysql_2.0s4-2_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-mysql_2.0s4-2_i386.deb jabberd2-ldap-pgsql_2.0s4-2_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-pgsql_2.0s4-2_i386.deb jabberd2-mysql_2.0s4-2_i386.deb to pool/main/j/jabberd2/jabberd2-mysql_2.0s4-2_i386.deb jabberd2-pgsql_2.0s4-2_i386.deb to pool/main/j/jabberd2/jabberd2-pgsql_2.0s4-2_i386.deb jabberd2_2.0s4-2.diff.gz to pool/main/j/jabberd2/jabberd2_2.0s4-2.diff.gz jabberd2_2.0s4-2.dsc to pool/main/j/jabberd2/jabberd2_2.0s4-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-msn 1.2.1-1.3cvs4-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 27 Nov 2004 11:01:24 -0700 Source: jabber-msn Binary: jabber-msn Architecture: source i386 Version: 1.2.1-1.3cvs4-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-msn - Provides the MSN transport for the Jabber IM server Closes: 276188 279463 Changes: jabber-msn (1.2.1-1.3cvs4-1) unstable; urgency=low . * new upstream version (Closes: #276188) * bumping Build-Depends to libcurl3-dev (Closes: #279463) Files: dc441b6500fa24bc1996bb38fbe9f25b 659 net optional jabber-msn_1.2.1-1.3cvs4-1.dsc 572c389065f327a72028e597087f6899 72681 net optional jabber-msn_1.2.1-1.3cvs4.orig.tar.gz 5b1da7a66dbeb95343b04dcffe570e4b 14892 net optional jabber-msn_1.2.1-1.3cvs4-1.diff.gz dfb3f22d0eb9e345e0b8e6b0138afd29 67368 net optional jabber-msn_1.2.1-1.3cvs4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBqMNsI49lBuo6JyYRAq4xAKCDHRR91p3/ORBfvhr08VJAd2Zn+ACZAZrP wRiOCEf0TIvo8jkitsmxElM= =8iGC -END PGP SIGNATURE- Accepted: jabber-msn_1.2.1-1.3cvs4-1.diff.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.3cvs4-1.diff.gz jabber-msn_1.2.1-1.3cvs4-1.dsc to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.3cvs4-1.dsc jabber-msn_1.2.1-1.3cvs4-1_i386.deb to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.3cvs4-1_i386.deb jabber-msn_1.2.1-1.3cvs4.orig.tar.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.3cvs4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabberd2 2.0s4-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 6 Nov 2004 14:59:13 -0700 Source: jabberd2 Binary: jabberd2-ldap-pgsql jabberd2-ldap-mysql jabberd2-mysql jabberd2-pgsql jabberd2-bdb jabberd2-ldap-bdb Architecture: source i386 Version: 2.0s4-1 Distribution: experimental Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabberd2-bdb - Jabber Open Source Instant Messenger Server (Berkeley DB) jabberd2-ldap-bdb - Jabber Open Source Instant Messenger Server (LDAP Berkeley DB) jabberd2-ldap-mysql - Jabber Open Source Instant Messenger Server (LDAP MySQL) jabberd2-ldap-pgsql - Jabber Open Source Instant Messenger Server (LDAP PostgreSQL) jabberd2-mysql - Jabber Open Source Instant Messenger Server (MySQL) jabberd2-pgsql - Jabber Open Source Instant Messenger Server (PostgreSQL) Closes: 237303 245260 250886 256382 275976 279478 279922 Changes: jabberd2 (2.0s4-1) experimental; urgency=low . * New upstream version (Closes: #279922, #275976) * Upstream exception added for OpenSSL (Closes: #237303) * updated default start/stop sequence to start after and stop before mysql/pgsql (Closes: #250886) * built packages offering ldap option (Closes: #256382, #279478) * corrected typo referencing MSM instead of MSN in long descriptions * added dependency on jabber-common * components now run as jabber:adm (Closes: #245260) Files: b179c511f949367ce9c5e51652cb78d2 798 net optional jabberd2_2.0s4-1.dsc 2682037fc177e1f3e7d7869cb3f59c1d 716819 net optional jabberd2_2.0s4.orig.tar.gz 8f340e358d01ca7ff8481d825dd9e553 9468 net optional jabberd2_2.0s4-1.diff.gz 468fc5a464e4ea45d0a3297588b7bc8f 556442 net optional jabberd2-bdb_2.0s4-1_i386.deb 35dd4aee86db8b1f3407f6a67b542436 557624 net optional jabberd2-ldap-bdb_2.0s4-1_i386.deb d1caef1d4e0c0c2b4120b2e8a67c5f0a 559422 net optional jabberd2-mysql_2.0s4-1_i386.deb 7e9cd05eb554ce0356d14663e903781d 561258 net optional jabberd2-ldap-mysql_2.0s4-1_i386.deb 24065d19e7ed77c32c3fb7d77a7b4e89 559880 net optional jabberd2-pgsql_2.0s4-1_i386.deb 844ee385d6210405aa4865fa92a7a841 561744 net optional jabberd2-ldap-pgsql_2.0s4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBjX9dI49lBuo6JyYRAipLAJ0TQMC/nyfXz2aU0YR7C71qDnMXTgCggW69 wiv6vihMGfODH/+HOiIho3g= =Ptfk -END PGP SIGNATURE- Accepted: jabberd2-bdb_2.0s4-1_i386.deb to pool/main/j/jabberd2/jabberd2-bdb_2.0s4-1_i386.deb jabberd2-ldap-bdb_2.0s4-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-bdb_2.0s4-1_i386.deb jabberd2-ldap-mysql_2.0s4-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-mysql_2.0s4-1_i386.deb jabberd2-ldap-pgsql_2.0s4-1_i386.deb to pool/main/j/jabberd2/jabberd2-ldap-pgsql_2.0s4-1_i386.deb jabberd2-mysql_2.0s4-1_i386.deb to pool/main/j/jabberd2/jabberd2-mysql_2.0s4-1_i386.deb jabberd2-pgsql_2.0s4-1_i386.deb to pool/main/j/jabberd2/jabberd2-pgsql_2.0s4-1_i386.deb jabberd2_2.0s4-1.diff.gz to pool/main/j/jabberd2/jabberd2_2.0s4-1.diff.gz jabberd2_2.0s4-1.dsc to pool/main/j/jabberd2/jabberd2_2.0s4-1.dsc jabberd2_2.0s4.orig.tar.gz to pool/main/j/jabberd2/jabberd2_2.0s4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-yahoo 2.3.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 26 Sep 2004 11:57:42 -0600 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 Version: 2.3.2-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Closes: 258255 Changes: jabber-yahoo (2.3.2-1) unstable; urgency=low . * new upstream version (Closes: #258255) Files: b3dcb699fa8abc22edbf4d9420903f57 657 net optional jabber-yahoo_2.3.2-1.dsc bfe48aa7980a5e27ec929311615e792c 117944 net optional jabber-yahoo_2.3.2.orig.tar.gz ed5d1e3b9b79736a44e42139c0183627 6607 net optional jabber-yahoo_2.3.2-1.diff.gz 051e10d12bdb6730b5967a43a2c76250 64462 net optional jabber-yahoo_2.3.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBVwT3I49lBuo6JyYRAvCoAKDWugAELkSTPerUiJAbCf/324mfcgCg3OX/ cztIdJZZbs/LN14b4EWCdR8= =58p5 -END PGP SIGNATURE- Accepted: jabber-yahoo_2.3.2-1.diff.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.2-1.diff.gz jabber-yahoo_2.3.2-1.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.2-1.dsc jabber-yahoo_2.3.2-1_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.2-1_i386.deb jabber-yahoo_2.3.2.orig.tar.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-jit 1.1.6-9 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 25 Sep 2004 10:56:04 -0600 Source: jabber-jit Binary: jabber-jit Architecture: source i386 Version: 1.1.6-9 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-jit - Jabber ICQ Transport Closes: 262286 265635 273301 Changes: jabber-jit (1.1.6-9) unstable; urgency=low . * added patch to support UTF-8 and UTF-16 messages (Closes: #273301) * added patch to support importing roster with international characters (Closes: #265635, #262286) Files: 40cae2194176cdff4a5ebf4606678c1d 595 net optional jabber-jit_1.1.6-9.dsc e2c9a1063654628f14c644681927752d 34783 net optional jabber-jit_1.1.6-9.diff.gz 449e1c29203a273f9866638b5e7044eb 382278 net optional jabber-jit_1.1.6-9_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBVbWJI49lBuo6JyYRAju3AKCX1/z19DbWSUUY8O7qMWa5FqjMagCfdQVb C9AsYUOCJJSg1nx7CFeZznU= =zCbY -END PGP SIGNATURE- Accepted: jabber-jit_1.1.6-9.diff.gz to pool/main/j/jabber-jit/jabber-jit_1.1.6-9.diff.gz jabber-jit_1.1.6-9.dsc to pool/main/j/jabber-jit/jabber-jit_1.1.6-9.dsc jabber-jit_1.1.6-9_i386.deb to pool/main/j/jabber-jit/jabber-jit_1.1.6-9_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber 1.4.3-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Sep 2004 17:48:56 -0600 Source: jabber Binary: jabber-dev jabber Architecture: source i386 Version: 1.4.3-3 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber - Daemon for the jabber.org Open Source Instant Messenger jabber-dev - Daemon for the jabber.org Open Source Instant Messenger Closes: 269284 272408 Changes: jabber (1.4.3-3) unstable; urgency=low . * added patch to correct libexpat vulnerability (Closes: #272408) * corrected typo referencing MSM instead of MSN (Closes: #269284) Files: aa3ac8de7a8fe545ef65efe4403f4e5b 657 net optional jabber_1.4.3-3.dsc 6313d0b204f0ab8f21b4aa76ac3e91af 70161 net optional jabber_1.4.3-3.diff.gz 45fb67f812ee7f13660f0de48fb07456 153154 net optional jabber_1.4.3-3_i386.deb f88f4014e31cd96f83ebe809e0949061 24174 devel optional jabber-dev_1.4.3-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBTiM6I49lBuo6JyYRAjHbAKCHlD40HBp99FBtJbeIb0za7/3/7wCeJGEy 8A5NncPazMZyeF9UTsfwFPw= =b4sy -END PGP SIGNATURE- Accepted: jabber-dev_1.4.3-3_i386.deb to pool/main/j/jabber/jabber-dev_1.4.3-3_i386.deb jabber_1.4.3-3.diff.gz to pool/main/j/jabber/jabber_1.4.3-3.diff.gz jabber_1.4.3-3.dsc to pool/main/j/jabber/jabber_1.4.3-3.dsc jabber_1.4.3-3_i386.deb to pool/main/j/jabber/jabber_1.4.3-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-yahoo 2.3.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Jun 2004 14:36:57 -0600 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 Version: 2.3.1-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Changes: jabber-yahoo (2.3.1-1) unstable; urgency=low . * new upstream version * includes yet another new auth patch Files: 61b799d78ab0e61cb49fa45ba452a50b 657 net optional jabber-yahoo_2.3.1-1.dsc 1fe2c651d612eb58dccae2baad3c4c97 64127 net optional jabber-yahoo_2.3.1.orig.tar.gz 90ef771eb9c99795c6fa4a9b271d55ce 75284 net optional jabber-yahoo_2.3.1-1.diff.gz 9f604d2639c33489bc16971dd69b4950 64546 net optional jabber-yahoo_2.3.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA3I/PI49lBuo6JyYRAltNAJ0T7mvzBv7et2YC5H0bt6lAv6WengCfbmon +4E5kejvDFzBtWbJyc/+juk= =3Qp1 -END PGP SIGNATURE- Accepted: jabber-yahoo_2.3.1-1.diff.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.1-1.diff.gz jabber-yahoo_2.3.1-1.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.1-1.dsc jabber-yahoo_2.3.1-1_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.1-1_i386.deb jabber-yahoo_2.3.1.orig.tar.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-aim 20040131b-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 May 2004 09:15:02 -0600 Source: jabber-aim Binary: jabber-aim Architecture: source i386 Version: 20040131b-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-aim - Provides AIM messenger transport for Jabber IM server Closes: 249120 Changes: jabber-aim (20040131b-1) unstable; urgency=low . * new upstream package (Closes: #249120) Files: 13c28bd2101720d1aefb384309a8153d 629 net optional jabber-aim_20040131b-1.dsc b27a243ace3ce57e56ffabfe6db80042 403221 net optional jabber-aim_20040131b.orig.tar.gz ca8fafadbab9957210edcde5af7248e0 5654 net optional jabber-aim_20040131b-1.diff.gz d1a64dd62cdb083b61304a890f618dcd 82896 net optional jabber-aim_20040131b-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAqinbI49lBuo6JyYRAj9DAKDIU3yT9uCIdiFlnYpgJfI0EoM+fQCePsVk 8XGNDyWCHGPyM6oQHozmh34= =UCDQ -END PGP SIGNATURE- Accepted: jabber-aim_20040131b-1.diff.gz to pool/main/j/jabber-aim/jabber-aim_20040131b-1.diff.gz jabber-aim_20040131b-1.dsc to pool/main/j/jabber-aim/jabber-aim_20040131b-1.dsc jabber-aim_20040131b-1_i386.deb to pool/main/j/jabber-aim/jabber-aim_20040131b-1_i386.deb jabber-aim_20040131b.orig.tar.gz to pool/main/j/jabber-aim/jabber-aim_20040131b.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-aim 20040131-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 11 May 2004 14:46:23 -0600 Source: jabber-aim Binary: jabber-aim Architecture: source i386 Version: 20040131-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-aim - Provides AIM messenger transport for Jabber IM server Closes: 247248 Changes: jabber-aim (20040131-1) unstable; urgency=low . * new upstream version (Closes: #247248) Files: 85222013f60d86bbe9ca62a9511431c9 628 net optional jabber-aim_20040131-1.dsc 2f5595c9560c3cf529ae5da9816e5587 247349 net optional jabber-aim_20040131.orig.tar.gz 6ef0677b7a7a774bb4cb44830997de35 257085 net optional jabber-aim_20040131-1.diff.gz f889aef6b519e12258e22258ec9b1a0d 82856 net optional jabber-aim_20040131-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoUOSI49lBuo6JyYRAlKdAJ9lW7YHckQPiFdNFaZC1IiH9JvmRwCgt+VL JjGqdrejtk8q4Trl2976C8o= =mQVF -END PGP SIGNATURE- Accepted: jabber-aim_20040131-1.diff.gz to pool/main/j/jabber-aim/jabber-aim_20040131-1.diff.gz jabber-aim_20040131-1.dsc to pool/main/j/jabber-aim/jabber-aim_20040131-1.dsc jabber-aim_20040131-1_i386.deb to pool/main/j/jabber-aim/jabber-aim_20040131-1_i386.deb jabber-aim_20040131.orig.tar.gz to pool/main/j/jabber-aim/jabber-aim_20040131.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mediamate 0.9.3.6-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 8 May 2004 21:10:19 -0600 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3.6-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Changes: mediamate (0.9.3.6-1) unstable; urgency=low . * new upstream version Files: 36f0e0665faa871bd16d58cbd01a42a3 601 web optional mediamate_0.9.3.6-1.dsc ba56d82e5942ded928d0abe0a173e00a 228549 web optional mediamate_0.9.3.6.orig.tar.gz e76c15de174aa8b3bfea9a21552e596a 9483 web optional mediamate_0.9.3.6-1.diff.gz db5e849db11e53820677d363f67edcac 219094 web optional mediamate_0.9.3.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAnaNwI49lBuo6JyYRAnw1AKC1IcYmqqp70czTgkYAivCwdUsLqwCfeaCV OwEKrtDpj5Y3q42oWnn3skY= =sS3R -END PGP SIGNATURE- Accepted: mediamate_0.9.3.6-1.diff.gz to pool/main/m/mediamate/mediamate_0.9.3.6-1.diff.gz mediamate_0.9.3.6-1.dsc to pool/main/m/mediamate/mediamate_0.9.3.6-1.dsc mediamate_0.9.3.6-1_all.deb to pool/main/m/mediamate/mediamate_0.9.3.6-1_all.deb mediamate_0.9.3.6.orig.tar.gz to pool/main/m/mediamate/mediamate_0.9.3.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mediamate 0.9.3.5-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Apr 2004 14:43:09 -0600 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3.5-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Changes: mediamate (0.9.3.5-1) unstable; urgency=low . * new upstream version * added release file to installed files Files: f5e60654cedbb24288eabb6c9d8f20e2 601 web optional mediamate_0.9.3.5-1.dsc 5acf86c10808ea525fac9221e6169b99 228230 web optional mediamate_0.9.3.5.orig.tar.gz 18ad1836feb2f87821e13857d7ed63e7 9447 web optional mediamate_0.9.3.5-1.diff.gz c8937430bce46c83c4ed243c594c2134 218934 web optional mediamate_0.9.3.5-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAeHcqI49lBuo6JyYRAtXsAKDcJUb42pWpxFhnERUDIqR4Sk/q7ACgvKIs 0Ium3PhscqBMjvOgWzuagTM= =owpb -END PGP SIGNATURE- Accepted: mediamate_0.9.3.5-1.diff.gz to pool/main/m/mediamate/mediamate_0.9.3.5-1.diff.gz mediamate_0.9.3.5-1.dsc to pool/main/m/mediamate/mediamate_0.9.3.5-1.dsc mediamate_0.9.3.5-1_all.deb to pool/main/m/mediamate/mediamate_0.9.3.5-1_all.deb mediamate_0.9.3.5.orig.tar.gz to pool/main/m/mediamate/mediamate_0.9.3.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber 1.4.3-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Apr 2004 18:03:39 -0600 Source: jabber Binary: jabber-dev jabber Architecture: source i386 Version: 1.4.3-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber - Daemon for the jabber.org Open Source Instant Messenger jabber-dev - Daemon for the jabber.org Open Source Instant Messenger Closes: 243049 Changes: jabber (1.4.3-2) unstable; urgency=low . * removed jabber-dev dependency on jabber (Closes: #243049) Files: f01264c174a160a07529424ad52c05e3 630 net optional jabber_1.4.3-2.dsc 6028cf1c10b53fa3d147d4ccadbbc555 22442 net optional jabber_1.4.3-2.diff.gz 6a766ffd1b8a2c49070fda2323cfa195 185900 net optional jabber_1.4.3-2_i386.deb c3fae08610a114c0c5fe2b645e38309d 28906 devel optional jabber-dev_1.4.3-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAeMB9I49lBuo6JyYRApwkAKCdkdSKuDjhEzfuBJkhTVUZlxcP/ACgg9DM 9hXUP9droI1NwTjnLIsBlgE= =YAPQ -END PGP SIGNATURE- Accepted: jabber-dev_1.4.3-2_i386.deb to pool/main/j/jabber/jabber-dev_1.4.3-2_i386.deb jabber_1.4.3-2.diff.gz to pool/main/j/jabber/jabber_1.4.3-2.diff.gz jabber_1.4.3-2.dsc to pool/main/j/jabber/jabber_1.4.3-2.dsc jabber_1.4.3-2_i386.deb to pool/main/j/jabber/jabber_1.4.3-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabberd2 2.0s2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Mar 2004 20:53:07 -0700 Source: jabberd2 Binary: jabberd2-mysql jabberd2-pgsql jabberd2-bdb Architecture: source i386 Version: 2.0s2-1 Distribution: experimental Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabberd2-bdb - Jabber Open Source Instant Messenger Server (Berkeley DB) jabberd2-mysql - Jabber Open Source Instant Messenger Server (MySQL) jabberd2-pgsql - Jabber Open Source Instant Messenger Server (PostgreSQL) Changes: jabberd2 (2.0s2-1) experimental; urgency=low . * New upstream version Files: 861270eac2b344e8b0888ca111f56ad8 723 net optional jabberd2_2.0s2-1.dsc 5b276f9b2426eb938eb12828138a20c5 791339 net optional jabberd2_2.0s2.orig.tar.gz 6c9303c84775bd8e9484e044b2177962 7822 net optional jabberd2_2.0s2-1.diff.gz 11f0d370ff7aa05c4f10efc96ce7c8ff 732436 net optional jabberd2-bdb_2.0s2-1_i386.deb ee482c867f2304c2c5d90c653976c180 735306 net optional jabberd2-mysql_2.0s2-1_i386.deb 5adb0ae05359aef429f63efeabb99a1c 735946 net optional jabberd2-pgsql_2.0s2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFARC3nI49lBuo6JyYRAm9KAKC+Glib+CZbgvcKdRr9pLy4Zu/jhgCdFWpS zZ9LYfJhroZnXsENqWN7oUw= =4IiU -END PGP SIGNATURE- Accepted: jabberd2-bdb_2.0s2-1_i386.deb to pool/main/j/jabberd2/jabberd2-bdb_2.0s2-1_i386.deb jabberd2-mysql_2.0s2-1_i386.deb to pool/main/j/jabberd2/jabberd2-mysql_2.0s2-1_i386.deb jabberd2-pgsql_2.0s2-1_i386.deb to pool/main/j/jabberd2/jabberd2-pgsql_2.0s2-1_i386.deb jabberd2_2.0s2-1.diff.gz to pool/main/j/jabberd2/jabberd2_2.0s2-1.diff.gz jabberd2_2.0s2-1.dsc to pool/main/j/jabberd2/jabberd2_2.0s2-1.dsc jabberd2_2.0s2.orig.tar.gz to pool/main/j/jabberd2/jabberd2_2.0s2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-msn 1.2.1-1.2.8rc1-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Feb 2004 20:35:17 -0700 Source: jabber-msn Binary: jabber-msn Architecture: source i386 Version: 1.2.1-1.2.8rc1-3 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-msn - Provides the MSN transport for the Jabber IM server Closes: 232807 Changes: jabber-msn (1.2.1-1.2.8rc1-3) unstable; urgency=low . * increased require jabber and jabber-dev versions to 1.4.3 or later * added libpth-dev build dependency (Closes: #232807) Files: 9fbdd859c61ad81b943ec4c8814abd74 662 net optional jabber-msn_1.2.1-1.2.8rc1-3.dsc cd421dd07ef9c4fb02285bd14d20e94d 35696 net optional jabber-msn_1.2.1-1.2.8rc1-3.diff.gz ed65a4220b581ef65e794d2fbc309b40 61102 net optional jabber-msn_1.2.1-1.2.8rc1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFANDPHI49lBuo6JyYRAimeAJ9hq+hn9ROSSnmrfpTuse6BSDsPwQCfXJT0 TxvBpRHBMaXfvh7UsF8e3eg= =o1oP -END PGP SIGNATURE- Accepted: jabber-msn_1.2.1-1.2.8rc1-3.diff.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-3.diff.gz jabber-msn_1.2.1-1.2.8rc1-3.dsc to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-3.dsc jabber-msn_1.2.1-1.2.8rc1-3_i386.deb to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted moviemate 0.9.3-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 11 Feb 2004 15:10:15 -0700 Source: moviemate Binary: moviemate Architecture: source all Version: 0.9.3-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: moviemate - web-based movie database and tracker (dummy) Closes: 232278 Changes: moviemate (0.9.3-2) unstable; urgency=low . * removed extraneous templates and added dummy to short desc (Closes: #232278) Files: d54713bcca66ebaa3eab25c48d0f15b0 516 web optional moviemate_0.9.3-2.dsc f06ef69f310457948d9a199e5d2dbb3f 2915 web optional moviemate_0.9.3-2.tar.gz 4028e8035dca40904a0bbe2b9144ffa0 3264 web optional moviemate_0.9.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAKqzLI49lBuo6JyYRAqUCAJ9d7xwqUKK1yWUukQDcMbpPfWj/mwCg4fcf WdeQ/CA2hfdrgOn8SoZcxaM= =YU0J -END PGP SIGNATURE- Accepted: moviemate_0.9.3-2.dsc to pool/main/m/moviemate/moviemate_0.9.3-2.dsc moviemate_0.9.3-2.tar.gz to pool/main/m/moviemate/moviemate_0.9.3-2.tar.gz moviemate_0.9.3-2_all.deb to pool/main/m/moviemate/moviemate_0.9.3-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-muc 0.6.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 21 Jan 2004 21:54:57 -0700 Source: jabber-muc Binary: jabber-muc Architecture: source i386 Version: 0.6.0-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-muc - Multi User Chat module for the Jabber IM Server Closes: 228877 Changes: jabber-muc (0.6.0-2) unstable; urgency=low . * added needed build depends on libglib2.0-dev (Closes: #228877) Files: 129326ab08606ac52769975a59bf4b1f 637 net optional jabber-muc_0.6.0-2.dsc 2e1dee3acf584f00e2ef1d1905d18c54 14390 net optional jabber-muc_0.6.0-2.diff.gz 1e108ef1a20f4483089e9e2023dda2af 67848 net optional jabber-muc_0.6.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAD1wqI49lBuo6JyYRApnFAKDVjtQsotWx4he7pCNB6Gf7x3s3EQCgqDgA Jzxvlpx17N7QCIvawB3JfBo= =M/4Y -END PGP SIGNATURE- Accepted: jabber-muc_0.6.0-2.diff.gz to pool/main/j/jabber-muc/jabber-muc_0.6.0-2.diff.gz jabber-muc_0.6.0-2.dsc to pool/main/j/jabber-muc/jabber-muc_0.6.0-2.dsc jabber-muc_0.6.0-2_i386.deb to pool/main/j/jabber-muc/jabber-muc_0.6.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-yahoo 2.3.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 15 Jan 2004 20:21:53 -0700 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 Version: 2.3.0-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Closes: 227297 Changes: jabber-yahoo (2.3.0-2) unstable; urgency=low . * added newauth patch (Closes: #227297) Files: 218014548c0dde598267c8d1b3d1fb2b 596 net optional jabber-yahoo_2.3.0-2.dsc bb9bd5a86850ce64dad592b381f0d7a8 72118 net optional jabber-yahoo_2.3.0-2.tar.gz 6d387a132b2c8e713b9cf8b4f6834ceb 42710 net optional jabber-yahoo_2.3.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAB1rII49lBuo6JyYRAqZgAJ0YgllEr6CTdvKIROosPbdU611m0wCgjHA7 5lF5NMDbePxfD2cQ48G/5Xs= =JmaL -END PGP SIGNATURE- Accepted: jabber-yahoo_2.3.0-2.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.0-2.dsc jabber-yahoo_2.3.0-2.tar.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.0-2.tar.gz jabber-yahoo_2.3.0-2_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-yahoo 2.3.0+0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 15 Jan 2004 20:58:43 -0700 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 Version: 2.3.0+0-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Changes: jabber-yahoo (2.3.0+0-1) unstable; urgency=low . * correcting incorrect upload Files: d04a1819e4705c23bef089a1be655335 674 net optional jabber-yahoo_2.3.0+0-1.dsc 4ff576fe97b0ea7e72c2458f584cf0b7 44741 net optional jabber-yahoo_2.3.0+0.orig.tar.gz 3761d49176480bf06d9d1c1ec0870a0d 27462 net optional jabber-yahoo_2.3.0+0-1.diff.gz 01a3fd396ac2399c443d58ece5e1622a 42736 net optional jabber-yahoo_2.3.0+0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAB2QfI49lBuo6JyYRAsTSAJ97vhprkInhygJBkD+bvq8E0qEt6ACfWBMm 9Vq1wnxNt7CeDL1z9mkRfmQ= =5pso -END PGP SIGNATURE- Accepted: jabber-yahoo_2.3.0+0-1.diff.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.0+0-1.diff.gz jabber-yahoo_2.3.0+0-1.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.0+0-1.dsc jabber-yahoo_2.3.0+0-1_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.0+0-1_i386.deb jabber-yahoo_2.3.0+0.orig.tar.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.3.0+0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-muc 0.6.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 16 Jan 2004 15:27:01 -0700 Source: jabber-muc Binary: jabber-muc Architecture: source i386 Version: 0.6.0-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-muc - Multi User Chat module for the Jabber IM Server Closes: 228148 Changes: jabber-muc (0.6.0-1) unstable; urgency=low . * new upstream version (Closes: #228148) Files: fcf04f45bb111f2346246f752502b03b 621 net optional jabber-muc_0.6.0-1.dsc a2c82e7b08e6f121754d0c9b96db4497 56287 net optional jabber-muc_0.6.0.orig.tar.gz c618d96d99895e745d5127f1c772a240 14341 net optional jabber-muc_0.6.0-1.diff.gz 315c928ea6c1dfefda650167c0ffceb0 67788 net optional jabber-muc_0.6.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFACGwSI49lBuo6JyYRAi3lAKDO+obG6sGMwhBshx7ccNjaGsCNogCfdbLj 4g6RQKF1PxuW30WaUXfp3DQ= =88UJ -END PGP SIGNATURE- Accepted: jabber-muc_0.6.0-1.diff.gz to pool/main/j/jabber-muc/jabber-muc_0.6.0-1.diff.gz jabber-muc_0.6.0-1.dsc to pool/main/j/jabber-muc/jabber-muc_0.6.0-1.dsc jabber-muc_0.6.0-1_i386.deb to pool/main/j/jabber-muc/jabber-muc_0.6.0-1_i386.deb jabber-muc_0.6.0.orig.tar.gz to pool/main/j/jabber-muc/jabber-muc_0.6.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-yahoo 2.2.0-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 29 Dec 2003 12:48:49 -0700 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 Version: 2.2.0-3 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Changes: jabber-yahoo (2.2.0-3) unstable; urgency=low . * added yahoo-timeout patch from upstream author * updated yahoo login server in jabber-yahoo.xml Files: b601a3ffd6e17482f6507b3bf1d709c8 667 net optional jabber-yahoo_2.2.0-3.dsc 669a74e2b8989da30ec7a96df15a4b35 5736 net optional jabber-yahoo_2.2.0-3.diff.gz 7a05ca8bf8b672594a08aa66adc72cd0 28450 net optional jabber-yahoo_2.2.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/8IenI49lBuo6JyYRAqENAJ9IpGc5X4gDclDp6nZPzKijfq3OkgCfWJHZ 4/kXPmE7/XHg+H56K/HApdQ= =UQvj -END PGP SIGNATURE- Accepted: jabber-yahoo_2.2.0-3.diff.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-3.diff.gz jabber-yahoo_2.2.0-3.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-3.dsc jabber-yahoo_2.2.0-3_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-aim 20030314-7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 18 Dec 2003 11:12:39 -0700 Source: jabber-aim Binary: jabber-aim Architecture: source i386 Version: 20030314-7 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-aim - Provides AIM messenger transport for Jabber IM server Changes: jabber-aim (20030314-7) unstable; urgency=low . * updated for the removal of pth from jabber source, now builds using installed libpth-dev package as does the jabber package Files: 1303a849f1774e59cca1380a929e3ed9 619 net optional jabber-aim_20030314-7.dsc 0040fef98f102191465cb995979d6cc5 10438 net optional jabber-aim_20030314-7.diff.gz 3e6e1c7d915a460230588260a9176a90 81384 net optional jabber-aim_20030314-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/4fDVI49lBuo6JyYRAoRUAJsGFx5G9qbchYXAva538fs6Ud4IZgCg7ek1 TkGoUHgqj6SlG8h9CWRINZQ= =qbgF -END PGP SIGNATURE- Accepted: jabber-aim_20030314-7.diff.gz to pool/main/j/jabber-aim/jabber-aim_20030314-7.diff.gz jabber-aim_20030314-7.dsc to pool/main/j/jabber-aim/jabber-aim_20030314-7.dsc jabber-aim_20030314-7_i386.deb to pool/main/j/jabber-aim/jabber-aim_20030314-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-jit 1.1.6-8 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 16 Dec 2003 20:17:17 -0700 Source: jabber-jit Binary: jabber-jit Architecture: source i386 Version: 1.1.6-8 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-jit - Jabber ICQ Transport Changes: jabber-jit (1.1.6-8) unstable; urgency=low . * applied gcc/g++ 3.3 patch from JIT bug tracker * removed gcc-3.2 and g++-3.2 depends * updated default configuration to use login.icq.com instead of ips Files: 21f81114517acf0781eafc00d7962a83 593 net optional jabber-jit_1.1.6-8.dsc 924862786ea9df3e8ad7d7be9a289088 28827 net optional jabber-jit_1.1.6-8.diff.gz 64d9099cb1138007051013535882874b 373038 net optional jabber-jit_1.1.6-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/380qI49lBuo6JyYRAnUmAJ9Ln3QvEndVtnNtIPN3Lpp+Rh2diACeLRxr 2xL235wP4PkfCqL4Dx5xmzk= =MFxD -END PGP SIGNATURE- Accepted: jabber-jit_1.1.6-8.diff.gz to pool/main/j/jabber-jit/jabber-jit_1.1.6-8.diff.gz jabber-jit_1.1.6-8.dsc to pool/main/j/jabber-jit/jabber-jit_1.1.6-8.dsc jabber-jit_1.1.6-8_i386.deb to pool/main/j/jabber-jit/jabber-jit_1.1.6-8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Any Progress?
On Sun, Dec 14, 2003 at 10:43:02PM -0600, Chris Cheney wrote: I haven't noticed it bouncing but it has yet to process the bug email I mentioned in my other post. Also, I have not heard back from anyone as to why that might have happened. With the BTS being broken (or at least appears to be) working on packages becomes a lot more of a pita. You have to fix the bugs, close them, and then go back later and make sure they actually got closed, which isn't happening. This seems to be hit and miss. All the bugs I've recently update/closed on my packages have processed fine. -- Jamin W. Collins Facts do not cease to exist because they are ignored. --Aldous Huxley, Proper Studies, 1927
Accepted mediamate 0.9.3-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 13 Dec 2003 14:18:09 -0700 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3-3 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Changes: mediamate (0.9.3-3) unstable; urgency=low . * added movies-snoopy patch to compensate for IMDB change Files: 57c56bf3728cff27765e97b74dcbe3b2 595 web optional mediamate_0.9.3-3.dsc 45f9dc87c04b5ba3ec487b43bb44cc5b 26128 web optional mediamate_0.9.3-3.diff.gz 296aa6d3fe624ca1b9f8cfce8a046135 205574 web optional mediamate_0.9.3-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/24dAI49lBuo6JyYRAlrpAKDxfrBW/Ys+RtY1jyPG0ShzxvAx4QCfUAzd Rgo1opU7zOvqqc138rdLZBs= =WyF9 -END PGP SIGNATURE- Accepted: mediamate_0.9.3-3.diff.gz to pool/main/m/mediamate/mediamate_0.9.3-3.diff.gz mediamate_0.9.3-3.dsc to pool/main/m/mediamate/mediamate_0.9.3-3.dsc mediamate_0.9.3-3_all.deb to pool/main/m/mediamate/mediamate_0.9.3-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-common 0.4 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 11 Dec 2003 13:14:35 -0700 Source: jabber-common Binary: jabber-common Architecture: source all Version: 0.4 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-common - Jabber server and transport (common files) Changes: jabber-common (0.4) unstable; urgency=low . * added conflict with jabber package versions prior to jabber-common's existence ( 1.4.2a-13) Files: 412bfd706f76823fc382bf93b717afac 522 net optional jabber-common_0.4.dsc e41de12f8a9882cd3efb2dc0e737bc80 3603 net optional jabber-common_0.4.tar.gz cbda392ba285c2199752e29e8f9da9d1 3848 net optional jabber-common_0.4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2NHLI49lBuo6JyYRAtRwAJ4yDW9a6sizOZ2yLnOFowOErhYmVwCdFjo0 w6/NR1HKyWf2r4F3GC+i4g0= =etvH -END PGP SIGNATURE- Accepted: jabber-common_0.4.dsc to pool/main/j/jabber-common/jabber-common_0.4.dsc jabber-common_0.4.tar.gz to pool/main/j/jabber-common/jabber-common_0.4.tar.gz jabber-common_0.4_all.deb to pool/main/j/jabber-common/jabber-common_0.4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber 1.4.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Nov 2003 13:17:08 -0700 Source: jabber Binary: jabber-dev jabber Architecture: source i386 Version: 1.4.3-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber - Daemon for the jabber.org Open Source Instant Messenger jabber-dev - Daemon for the jabber.org Open Source Instant Messenger Changes: jabber (1.4.3-1) unstable; urgency=low . * new upstream version * now using dpatch to apply source changes * added libpth2 and libpth-dev dependancies Files: 82a82d5ba513240f3cc1dc4a5876392e 630 net optional jabber_1.4.3-1.dsc 8d1ef5d1e276aa757b0af4c62a3e7d09 258108 net optional jabber_1.4.3.orig.tar.gz cca4bb2dfbb84f4427e1d972977fd19b 22241 net optional jabber_1.4.3-1.diff.gz cc6c8bb3a25462bf71e683f5e0a9417d 185838 net optional jabber_1.4.3-1_i386.deb fd43c4c249a9c5f7125fdc238515c469 28874 devel optional jabber-dev_1.4.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2PEdI49lBuo6JyYRAhCZAKDs7oknp7kz3UnNgxC1w8zW6IXYZwCg1ukG Xb6qXXpjM76AJE4BsRj9WYQ= =wcMZ -END PGP SIGNATURE- Accepted: jabber-dev_1.4.3-1_i386.deb to pool/main/j/jabber/jabber-dev_1.4.3-1_i386.deb jabber_1.4.3-1.diff.gz to pool/main/j/jabber/jabber_1.4.3-1.diff.gz jabber_1.4.3-1.dsc to pool/main/j/jabber/jabber_1.4.3-1.dsc jabber_1.4.3-1_i386.deb to pool/main/j/jabber/jabber_1.4.3-1_i386.deb jabber_1.4.3.orig.tar.gz to pool/main/j/jabber/jabber_1.4.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Infinite http redirect loop from people.d.o
Not sure if this is still part of the ongoing recovery or something else, but people.d.o is producing an infinite redirect loop for any personal page request. $ telnet people.debian.org 80 Trying 192.25.206.10... Connected to gluck.debian.org. Escape character is '^]'. GET http://people.debian.org/~jcollins/ !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN HTMLHEAD TITLE302 Found/TITLE /HEADBODY H1Found/H1 The document has moved A HREF=http://people.debian.org/~jcollins/;here/A.P HR ADDRESSApache/1.3.26 Server at gluck.debian.org Port 80/ADDRESS /BODY/HTML -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: RFS: phpgroupware
On Tue, Dec 09, 2003 at 09:06:02PM +0100, Thomas Viehmann wrote: Jamin W. Collins wrote [in a different order]: However, I'd prefer to have a work in progress blurb in README.Debian, partially to acknowledge that there are still some things to be smoothed out. (The reason I believe an update is appropriate in spite of regarding this as work in progress is that the version fixes many errors (some severe and security) of the package currently in unstable.) Why not request the removal of the version that is in unstable and put the work in progress version into experimental? Then as the kinks are worked out of the packages they could be moved over into unstable. This might mean that a few of the modules don't make it in right away, but would probably make for a smoother transition. - The database admin password is stored in debconf. This should not be done. Ask for it, use it, and then remove it from the database. What does this mean for the removal of the database upon purging the package? I don't have the impression that people will be very happy with debconf prompts in the postrm. (Of course, debconf might already have been removed in the postrm...) Should I just not drop the database? Dropping user entered data blindly isn't usually a good thing. While a prompt during postrm isn't great, IMHO it's better than storing a DB admin password in debconf. -- Jamin W. Collins Facts do not cease to exist because they are ignored. --Aldous Huxley, Proper Studies, 1927
Re: Some observations regardig the progress towards Debian 3.1
On Tue, Nov 18, 2003 at 05:08:40PM +0100, Thomas -Balu- Walter wrote: For now I have to fiddle around, creating bootdisks with newer kernels, Maybe I've just been very lucky, but I've yet to need to create a custom boot disk to install any of my various systems. I wouldn't consider most of them to be extremely old, some of them were bought within the last 6 months. In all cases using the 2.4 kernel on the first woody cd has worked fine for installation. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Accepted jabber-common 0.2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 20 Oct 2003 09:22:06 -0600 Source: jabber-common Binary: jabber-common Architecture: source all Version: 0.2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-common - Jabber server and transport (common files) Changes: jabber-common (0.2) unstable; urgency=low . * added libc6 and adduser to Depends * added /var/run/jabber and /var/log/jabber to package dirs Files: ee76b96caa408482932e98676799ce33 522 net optional jabber-common_0.2.dsc dab123ab5d54f54c680e244239373dc1 3442 net optional jabber-common_0.2.tar.gz ffc80b8ee97f90989a6efc62b609cdc3 3556 net optional jabber-common_0.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/k/6LI49lBuo6JyYRAkUsAKDqQ9MUI1WVAJoANt4CyojIdsO46gCgi9eN TElfD1h73kw2fHAdWlByuHQ= =JYeO -END PGP SIGNATURE- Accepted: jabber-common_0.2.dsc to pool/main/j/jabber-common/jabber-common_0.2.dsc jabber-common_0.2.tar.gz to pool/main/j/jabber-common/jabber-common_0.2.tar.gz jabber-common_0.2_all.deb to pool/main/j/jabber-common/jabber-common_0.2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-common 0.3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 27 Oct 2003 19:38:17 -0700 Source: jabber-common Binary: jabber-common Architecture: source all Version: 0.3 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-common - Jabber server and transport (common files) Closes: 216701 217887 Changes: jabber-common (0.3) unstable; urgency=low . * jabber-common exists (Closes: #216701) * added libc6.1 and libc0.3 as alternatives for libc6 Depends (Closes: #217887) * moved adduser usage to postinst script * added check in postrm to see if $USERID is null during purge Files: 34e9ae1730f8cbf3e4bd6fcc0b4c07eb 522 net optional jabber-common_0.3.dsc dd290bb0a5e9893d0106d53af07ae5e6 3588 net optional jabber-common_0.3.tar.gz 78b933b9e3981beb1de2646c93718d07 3744 net optional jabber-common_0.3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/ndeJI49lBuo6JyYRAl8PAKDpPCjFyOF+uXM2aZo8vIu+5ZOQZwCgso4g BDnHpIs86NnMkSktHVTHWoU= =hsLO -END PGP SIGNATURE- Accepted: jabber-common_0.3.dsc to pool/main/j/jabber-common/jabber-common_0.3.dsc jabber-common_0.3.tar.gz to pool/main/j/jabber-common/jabber-common_0.3.tar.gz jabber-common_0.3_all.deb to pool/main/j/jabber-common/jabber-common_0.3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber 1.4.2a-13 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Oct 2003 13:44:07 -0600 Source: jabber Binary: jabber-dev jabber Architecture: source i386 Version: 1.4.2a-13 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber - Daemon for the jabber.org Open Source Instant Messenger jabber-dev - Daemon for the jabber.org Open Source Instant Messenger Closes: 211346 212125 216087 Changes: jabber (1.4.2a-13) unstable; urgency=low . * added dependancy on jabber-common * now runs as jabber:adm LSB 1.3 (Closes: #211346) * added dependancy on procps (Closes: #216087) * updated config ownership to jabber:adm and 0640 * updated jabber.xml SRV lookup to use jabber-server (Closes: #212125) - http://www.jabber.org/ietf/draft-ietf-xmpp-core-18.html Files: ee7c5466f62e98c726ba82cf87abb4e5 605 net optional jabber_1.4.2a-13.dsc 814bd1d653272b93e97274aed0e35c28 95725 net optional jabber_1.4.2a-13.diff.gz 772f04d9a951dfea35bbe755751d26cc 195962 net optional jabber_1.4.2a-13_i386.deb 4b9ad08c79ad5c11c61994eb47430876 40980 devel optional jabber-dev_1.4.2a-13_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kWl6I49lBuo6JyYRAiinAJ9WQjZ2vDX3560XCoRq2WA/Oa2IjwCgldHA xoCo6N1XQUJzr1p5Vj6243o= =bogd -END PGP SIGNATURE- Accepted: jabber-dev_1.4.2a-13_i386.deb to pool/main/j/jabber/jabber-dev_1.4.2a-13_i386.deb jabber_1.4.2a-13.diff.gz to pool/main/j/jabber/jabber_1.4.2a-13.diff.gz jabber_1.4.2a-13.dsc to pool/main/j/jabber/jabber_1.4.2a-13.dsc jabber_1.4.2a-13_i386.deb to pool/main/j/jabber/jabber_1.4.2a-13_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-jit 1.1.6-7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Oct 2003 19:57:01 -0600 Source: jabber-jit Binary: jabber-jit Architecture: source i386 Version: 1.1.6-7 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-jit - Jabber ICQ Transport Changes: jabber-jit (1.1.6-7) unstable; urgency=low . * process now runs as jabber:adm * added dependancy on procps and jabber-common * tightened default permissions on jabber-jit.xml - now owned by jabber:adm and 0640 Files: 0b605a0332aa4be3f3bb8c2552470ad7 611 net optional jabber-jit_1.1.6-7.dsc 37ae56f241455617c82de8a9ba4c9a53 28421 net optional jabber-jit_1.1.6-7.diff.gz b619262a973c7eee2d9537870e74d650 376832 net optional jabber-jit_1.1.6-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kW8UI49lBuo6JyYRAgMaAKCNSeqy+yOrgIxbp3GGn2uEO8sC5wCgi6iA 0W8u4bIfy6KoqWSj72wK8fA= =VSuM -END PGP SIGNATURE- Accepted: jabber-jit_1.1.6-7.diff.gz to pool/main/j/jabber-jit/jabber-jit_1.1.6-7.diff.gz jabber-jit_1.1.6-7.dsc to pool/main/j/jabber-jit/jabber-jit_1.1.6-7.dsc jabber-jit_1.1.6-7_i386.deb to pool/main/j/jabber-jit/jabber-jit_1.1.6-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-jud 0.5-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 18 Oct 2003 10:34:02 -0600 Source: jabber-jud Binary: jabber-jud Architecture: source i386 Version: 0.5-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-jud - Provides User Directory support for the Jabber IM server Changes: jabber-jud (0.5-2) unstable; urgency=low . * switched to a service restart in postinst * updated init script - module existence check - use of /etc/jabber/functions Files: 250c5868a9ef83cca334c3abfc355d1c 614 net optional jabber-jud_0.5-2.dsc a48e97cb35aab8b0a7071b6c58ee52f5 14748 net optional jabber-jud_0.5-2.diff.gz d6550c71b4326683c0ae0656304f7196 20424 net optional jabber-jud_0.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kWztI49lBuo6JyYRAuGGAJ0Y4a+XNcZkwnSpybDnlI8eNg+S2ACeOZ9Y GSa/WvOP0NWHiJQGgJSiHdE= =KKvV -END PGP SIGNATURE- Accepted: jabber-jud_0.5-2.diff.gz to pool/main/j/jabber-jud/jabber-jud_0.5-2.diff.gz jabber-jud_0.5-2.dsc to pool/main/j/jabber-jud/jabber-jud_0.5-2.dsc jabber-jud_0.5-2_i386.deb to pool/main/j/jabber-jud/jabber-jud_0.5-2_i386.deb jabber-jud_0.5.orig.tar.gz to pool/main/j/jabber-jud/jabber-jud_0.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-msn 1.2.1-1.2.8rc1-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Oct 2003 15:31:25 -0600 Source: jabber-msn Binary: jabber-msn Architecture: source i386 Version: 1.2.1-1.2.8rc1-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-msn - Provides the MSN transport for the Jabber IM server Changes: jabber-msn (1.2.1-1.2.8rc1-2) unstable; urgency=low . * added support for get-orig-source debian/rules target * updated standards version to 3.6.1.0 * daemon now runs as jabber:adm like current jabber server * tightened default permissions on jabber-msn.xml - now owned by jabber:adm and 0640 Files: d003ca237a74911955ee4b74739a8d96 654 net optional jabber-msn_1.2.1-1.2.8rc1-2.dsc a29c6b5803796e3d49bb7a524db8e163 35342 net optional jabber-msn_1.2.1-1.2.8rc1-2.diff.gz 3ab493592896b7e3ce5bc7babf47efc7 60390 net optional jabber-msn_1.2.1-1.2.8rc1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kXAmI49lBuo6JyYRAgK3AJ0Xr/eqoxcRqSCy9a6akFTcSsPP1ACdH0Zs LdSCzXi0pFFlZ++BBEzfb38= =pFhz -END PGP SIGNATURE- Accepted: jabber-msn_1.2.1-1.2.8rc1-2.diff.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-2.diff.gz jabber-msn_1.2.1-1.2.8rc1-2.dsc to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-2.dsc jabber-msn_1.2.1-1.2.8rc1-2_i386.deb to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-yahoo 2.2.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Oct 2003 16:29:01 -0600 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 Version: 2.2.0-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Changes: jabber-yahoo (2.2.0-2) unstable; urgency=low . * added support for get-orig-source debian/rules target * updated standards version to 3.6.1.0 * daemon now runs as jabber:adm like current jabber server * tightened default permissions on jabber-yahoo.xml - now owned by jabber:adm and 0640 Files: 5cb215d898a6463d43e4042bc863db98 659 net optional jabber-yahoo_2.2.0-2.dsc bced347e9e31c6b8bb75f94accba3204 5134 net optional jabber-yahoo_2.2.0-2.diff.gz c8072a527e1116482ac4f8744d8d6a6b 28304 net optional jabber-yahoo_2.2.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kXNhI49lBuo6JyYRAuG+AJ9kiADqx7z6UDx350kaStYY5JMmzQCgqt8o mnowLhWQDP8u50m3wt+/JE4= =txwp -END PGP SIGNATURE- Accepted: jabber-yahoo_2.2.0-2.diff.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-2.diff.gz jabber-yahoo_2.2.0-2.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-2.dsc jabber-yahoo_2.2.0-2_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-aim 20030314-6 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 19 Sep 2003 19:26:44 -0600 Source: jabber-aim Binary: jabber-aim Architecture: source i386 Version: 20030314-6 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-aim - Provides AIM messenger transport for Jabber IM server Changes: jabber-aim (20030314-6) unstable; urgency=low . * added support for get-orig-source debian/rules target * updated standards version to 3.6.1.0 * daemon now runs as jabber:adm like current jabber server * tightened default permissions on jabber-aim.xml - now owned by jabber:adm and 0640 Files: 31ae5aa8beda81a598921be15d98859e 623 net optional jabber-aim_20030314-6.dsc e27c495a2c90092ab8350cc7b95a5cc9 10374 net optional jabber-aim_20030314-6.diff.gz 809dc8dd010b79b4e602a0d0f7ae77ba 81298 net optional jabber-aim_20030314-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kXcvI49lBuo6JyYRAvJIAJ4shHRKfvIu5mAq2irBGxzMLGurnwCfRmIK PVDv02zxkI6BptB2TnSbdiM= =Xo9o -END PGP SIGNATURE- Accepted: jabber-aim_20030314-6.diff.gz to pool/main/j/jabber-aim/jabber-aim_20030314-6.diff.gz jabber-aim_20030314-6.dsc to pool/main/j/jabber-aim/jabber-aim_20030314-6.dsc jabber-aim_20030314-6_i386.deb to pool/main/j/jabber-aim/jabber-aim_20030314-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-muc 0.5.2-7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 17 Oct 2003 15:56:24 -0600 Source: jabber-muc Binary: jabber-muc Architecture: source i386 Version: 0.5.2-7 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-muc - Multi User Chat module for the Jabber IM Server Changes: jabber-muc (0.5.2-7) unstable; urgency=low . * added support for get-orig-source debian/rules target * updated standards version to 3.6.1.0 * daemon now runs as jabber:adm like current jabber server * tightened default permissions on jabber-muc.xml - now owned by jabber:adm and 0640 Files: 0a6696b4d2c2ac4bc558c8309666c120 613 net optional jabber-muc_0.5.2-7.dsc f8bbc17aa46d8366749ca9d552a91d49 13869 net optional jabber-muc_0.5.2-7.diff.gz 9f5745a8d180c0e49a3e7b6f7e6d4668 63754 net optional jabber-muc_0.5.2-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/kXghI49lBuo6JyYRArqTAJ9YuIb110UKorrkBRuZB+Zppo8o2gCbB7W4 MLwkPVRpoRxkNTBeE0gx/ig= =EJye -END PGP SIGNATURE- Accepted: jabber-muc_0.5.2-7.diff.gz to pool/main/j/jabber-muc/jabber-muc_0.5.2-7.diff.gz jabber-muc_0.5.2-7.dsc to pool/main/j/jabber-muc/jabber-muc_0.5.2-7.dsc jabber-muc_0.5.2-7_i386.deb to pool/main/j/jabber-muc/jabber-muc_0.5.2-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-msn 1.2.1-1.2.8rc1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 15 Oct 2003 08:13:11 -0600 Source: jabber-msn Binary: jabber-msn Architecture: source i386 Version: 1.2.1-1.2.8rc1-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-msn - Provides the MSN transport for the Jabber IM server Closes: 212400 Changes: jabber-msn (1.2.1-1.2.8rc1-1) unstable; urgency=low . * new upstream version (Closes:#212400) - adds support for MSNP8 Files: e85dd4f1fa8be6743be5d3c84f3c8b0d 652 net optional jabber-msn_1.2.1-1.2.8rc1-1.dsc c1c3982ae6aeeaa47f73fe019aa17e6c 81715 net optional jabber-msn_1.2.1-1.2.8rc1.orig.tar.gz eddfcd9823272b7ef4c74e4d3c82ee0c 35250 net optional jabber-msn_1.2.1-1.2.8rc1-1.diff.gz c7c49640649c47a0cd0d64dd199a97c6 58092 net optional jabber-msn_1.2.1-1.2.8rc1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/jVjcI49lBuo6JyYRArp9AJ9lYb+1SHHB/PAOemS8K81TielvHACg4A5j ASHAcWNqJ8+Y5XGZsM5xoGg= =8HnP -END PGP SIGNATURE- Accepted: jabber-msn_1.2.1-1.2.8rc1-1.diff.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-1.diff.gz jabber-msn_1.2.1-1.2.8rc1-1.dsc to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-1.dsc jabber-msn_1.2.1-1.2.8rc1-1_i386.deb to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1-1_i386.deb jabber-msn_1.2.1-1.2.8rc1.orig.tar.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1-1.2.8rc1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian should not modify the kernels!
On Mon, Oct 06, 2003 at 10:41:47PM +0200, martin f krafft wrote: also sprach martin f krafft [2003.09.30.1016 +0200]: How do y'all suggest we continue on this, because apparently there are two camps with different opinions, Herbert doesn't think he needs to do anything, and this issue will just die without a change happening. I think we have to properly address and close the whole thing! Apparently noone agrees with me. I agree that the Debian kernel sources shouldn't contain any feature backports that aren't specifically to address security issues. I'd prefer a kernel source package with as few changes as possible. However, I also agree that it's Herbert's perrogative as pacakge maintainer to package what he wants (short of a policy violation or general resolution). I can't help but state that I am rather pissed off! I am especially annoyed with Herbert, who refused to make even the slightest budge in a direction showing his willingness to cooperate. I am sick and tired of these it's your problem and it's my choice excuses. Debian is a cooperative effort, it's not a conglomeration of hundreds of maintainers that do their own thing with their own packages. Sadly, you must be seeing a different Debian that I've seen. Sure the developers frequently work together toward an end goal, but I've seen meantion of a few cases of developers maintaining their packages exactly the way they want regardless of what other have to say. You've always got the option of packaging a new kernel source package without the excess. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Accepted jabber-yahoo 2.2.0-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Oct 2003 08:35:41 -0600 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 Version: 2.2.0-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Closes: 213831 Changes: jabber-yahoo (2.2.0-1) unstable; urgency=low . * new upstream release (Closes: #213831) Files: 3421106086243ddd1bba14ce0cfaed76 657 net optional jabber-yahoo_2.2.0-1.dsc 736e027579220aca3e19004927d2d227 41710 net optional jabber-yahoo_2.2.0.orig.tar.gz 71bde4f62b7f828e191fbce1cfb74d32 5166 net optional jabber-yahoo_2.2.0-1.diff.gz a8c0947b758261c73b2ed5f12570c6fc 27928 net optional jabber-yahoo_2.2.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/fdOGI49lBuo6JyYRAiaAAJ4zoJXZb1Tm+eqLh4RLXNO6YzAXZACfcztK 0w7pivI2T2QoPebQRdvsNkI= =ThI3 -END PGP SIGNATURE- Accepted: jabber-yahoo_2.2.0-1.diff.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-1.diff.gz jabber-yahoo_2.2.0-1.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-1.dsc jabber-yahoo_2.2.0-1_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0-1_i386.deb jabber-yahoo_2.2.0.orig.tar.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Where are we now? (Was: Bits from the RM)
On Thu, Oct 02, 2003 at 02:27:48PM -0400, Ervin Hearn III wrote: On Thu, Oct 02, 2003 at 10:50:09AM -0700, Chris Jantzen wrote: Easier for new people to use?!? /me rolls off chair laughing. I sincerely hope the :-P means you are using sarcasm. Quite seriously, I prefer using dselect... the main complaint I've heard from new users is being able to search for a specific package quickly. As soon as I teach them about / for find and \ for find again, they generally find it just as useful as I do. Not I. I made a few attempts to use it in the beginning. After that I decided that any and all installs I did from that point forward would not run dselect. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Accepted jabber-jud 0.4-7 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 10 Sep 2003 09:53:59 -0600 Source: jabber-jud Binary: jabber-jud Architecture: source i386 Version: 0.4-7 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-jud - Provides User Directory support for the Jabber IM server Closes: 156510 Changes: jabber-jud (0.4-7) unstable; urgency=low . * jabber user directory packaged, (Closes: #156510) Files: 92eb7c1da0561f8dfb7df7517aae995b 612 net optional jabber-jud_0.4-7.dsc d3442bc179df1c88abde65c2b07d4447 14183 net optional jabber-jud_0.4-7.diff.gz cf0d662e9106cf6cba8de2415a57448d 19348 net optional jabber-jud_0.4-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/X34mI49lBuo6JyYRAndqAKCu8Ws0MRxiElidaVFjLIsLgqrYmwCfYAzC YLxANAbJ1r1Vepk88hsHHMI= =FFhG -END PGP SIGNATURE- Accepted: jabber-jud_0.4-7.diff.gz to pool/main/j/jabber-jud/jabber-jud_0.4-7.diff.gz jabber-jud_0.4-7.dsc to pool/main/j/jabber-jud/jabber-jud_0.4-7.dsc jabber-jud_0.4-7_i386.deb to pool/main/j/jabber-jud/jabber-jud_0.4-7_i386.deb jabber-jud_0.4.orig.tar.gz to pool/main/j/jabber-jud/jabber-jud_0.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber 1.4.2a-12 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Sep 2003 13:31:57 -0600 Source: jabber Binary: jabber-dev jabber Architecture: source i386 Version: 1.4.2a-12 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber - Daemon for the jabber.org Open Source Instant Messenger jabber-dev - Daemon for the jabber.org Open Source Instant Messenger Closes: 139883 195300 Changes: jabber (1.4.2a-12) unstable; urgency=low . * added versioned depends to jabber-dev (Closes: #195300) * added umask 0027 to jabber log files (Closes: #139883) * updated to init.d script to allow jabber.d directory to be missing * new standards version * updated purge to handle missing log files * removed use of dh_undocumented * updated ownership of log files to daemon:adm Files: f5e3e5d39d93c96e25748554b6ae261b 603 net optional jabber_1.4.2a-12.dsc 949db13e9e0808a1c2c43e264deb952e 95197 net optional jabber_1.4.2a-12.diff.gz 00e26f20ce936867ab889260d239aff8 191408 net optional jabber_1.4.2a-12_i386.deb 82a1877b83a52b08d0223301c112ec14 40818 devel optional jabber-dev_1.4.2a-12_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/YiQEI49lBuo6JyYRAhO5AKDPw48xlu244PlxG2TgxFWEJniJjgCgp2sV BiPjrxzYus6aJcRnaOR+Cdw= =emdr -END PGP SIGNATURE- Accepted: jabber-dev_1.4.2a-12_i386.deb to pool/main/j/jabber/jabber-dev_1.4.2a-12_i386.deb jabber_1.4.2a-12.diff.gz to pool/main/j/jabber/jabber_1.4.2a-12.diff.gz jabber_1.4.2a-12.dsc to pool/main/j/jabber/jabber_1.4.2a-12.dsc jabber_1.4.2a-12_i386.deb to pool/main/j/jabber/jabber_1.4.2a-12_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-muc 0.5.2-6 (powerpc i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 29 Aug 2003 10:12:11 -0600 Source: jabber-muc Binary: jabber-muc Architecture: source i386 powerpc Version: 0.5.2-6 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-muc - Multi User Chat module for the Jabber IM Server Changes: jabber-muc (0.5.2-6) unstable; urgency=low . * updated postinst to start the service * updated prerm to stop the service * added /etc/default file to control whether service starts Files: 0e73f09cf00510aa5311e500c93e137f 611 net optional jabber-muc_0.5.2-6.dsc 9f72087b03cf09594865e824b3838364 47283 net optional jabber-muc_0.5.2.orig.tar.gz dd8c17b30abb2f1e8b58e14a046b8ad3 13810 net optional jabber-muc_0.5.2-6.diff.gz f152c9a1fcb49912a1b7cdd9fcfe1a3d 63708 net optional jabber-muc_0.5.2-6_i386.deb ee9d9b483826a930b6f9097a804a1ab5 67650 net optional jabber-muc_0.5.2-6_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/WfM7J2Vo11xhU60RAh6uAKCtd6ZgUy8A2WI6Wt/o/es+6ZfGHwCeIZ0D 9ZPmW5pg9lPDTxQC6GF2WWA= =j7dg -END PGP SIGNATURE- Accepted: jabber-muc_0.5.2-6.diff.gz to pool/main/j/jabber-muc/jabber-muc_0.5.2-6.diff.gz jabber-muc_0.5.2-6.dsc to pool/main/j/jabber-muc/jabber-muc_0.5.2-6.dsc jabber-muc_0.5.2-6_i386.deb to pool/main/j/jabber-muc/jabber-muc_0.5.2-6_i386.deb jabber-muc_0.5.2-6_powerpc.deb to pool/main/j/jabber-muc/jabber-muc_0.5.2-6_powerpc.deb jabber-muc_0.5.2.orig.tar.gz to pool/main/j/jabber-muc/jabber-muc_0.5.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-msn 1.2.1-4 (powerpc i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 29 Aug 2003 10:08:37 -0600 Source: jabber-msn Binary: jabber-msn Architecture: source i386 powerpc Version: 1.2.1-4 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-msn - Provides the MSN transport for the Jabber IM server Changes: jabber-msn (1.2.1-4) unstable; urgency=low . * updated postinst to start the service * updated prerm to stop the service * added /etc/default file to control whether service starts Files: 012df3b561349646088aa37bf3e24afd 611 net optional jabber-msn_1.2.1-4.dsc b7935c5021937d1ea1b9ef569af0ce58 74709 net optional jabber-msn_1.2.1.orig.tar.gz d7c28cc65b4cb335ef120ac62c61a328 34712 net optional jabber-msn_1.2.1-4.diff.gz 9580508cdbb8fcd133df53a7fd19a979 55188 net optional jabber-msn_1.2.1-4_i386.deb 01645186896ba430cc3661ae10180472 56138 net optional jabber-msn_1.2.1-4_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/WfH4J2Vo11xhU60RAq+WAJ9PqFIfNHt6597OUTCuamBkuKMJKgCg3xWV fovCXfeKCPVQw16aiBOIs3E= =mMoZ -END PGP SIGNATURE- Accepted: jabber-msn_1.2.1-4.diff.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1-4.diff.gz jabber-msn_1.2.1-4.dsc to pool/main/j/jabber-msn/jabber-msn_1.2.1-4.dsc jabber-msn_1.2.1-4_i386.deb to pool/main/j/jabber-msn/jabber-msn_1.2.1-4_i386.deb jabber-msn_1.2.1-4_powerpc.deb to pool/main/j/jabber-msn/jabber-msn_1.2.1-4_powerpc.deb jabber-msn_1.2.1.orig.tar.gz to pool/main/j/jabber-msn/jabber-msn_1.2.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jabber-yahoo 2.1.1-4 (powerpc i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 29 Aug 2003 10:15:19 -0600 Source: jabber-yahoo Binary: jabber-yahoo Architecture: source i386 powerpc Version: 2.1.1-4 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber-yahoo - Provides Yahoo messenger transport for Jabber IM server Changes: jabber-yahoo (2.1.1-4) unstable; urgency=low . * updated postinst to start the service * updated prerm to stop the service * added /etc/default file to control whether service starts Files: c6d3c6fc05b991586e832ff33d3045b7 634 net optional jabber-yahoo_2.1.1-4.dsc c2c1679cdb862a0b9e82862f56afc0e0 35566 net optional jabber-yahoo_2.1.1.orig.tar.gz 9b37722d89911d7b86e54eaa61c9e6c2 4931 net optional jabber-yahoo_2.1.1-4.diff.gz 2e2b9f3d9b4175ce15df9e02714ffe9c 24040 net optional jabber-yahoo_2.1.1-4_i386.deb f8373a81bcc192dfc14a7864199598a5 25780 net optional jabber-yahoo_2.1.1-4_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/WfTLJ2Vo11xhU60RAkdoAJ9gtWp/oetBxtqVAAy8gNMD4W7HbACg6Jx0 vN80cohI2BOJgYjfu9aVBLs= =I9Or -END PGP SIGNATURE- Accepted: jabber-yahoo_2.1.1-4.diff.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.1.1-4.diff.gz jabber-yahoo_2.1.1-4.dsc to pool/main/j/jabber-yahoo/jabber-yahoo_2.1.1-4.dsc jabber-yahoo_2.1.1-4_i386.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.1.1-4_i386.deb jabber-yahoo_2.1.1-4_powerpc.deb to pool/main/j/jabber-yahoo/jabber-yahoo_2.1.1-4_powerpc.deb jabber-yahoo_2.1.1.orig.tar.gz to pool/main/j/jabber-yahoo/jabber-yahoo_2.1.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mediamate 0.9.3-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 10 Sep 2003 16:18:51 -0600 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3-2 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Changes: mediamate (0.9.3-2) unstable; urgency=low . * switched to dpatch for patch application * added patch to change to eregi for IMDB changes * added patch to correct potentially short coverart reads Files: c4e377d408d98c1999ab9da81e885622 595 web optional mediamate_0.9.3-2.dsc 4a65d2937f389e1a5d331c89826f24bc 10800 web optional mediamate_0.9.3-2.diff.gz 0d1561362dcfe57711db393ebcfe42d0 198092 web optional mediamate_0.9.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/X6PCI49lBuo6JyYRAvmMAJ9orjE2kfpJXIDluDSHtHkMzahKfACfcMoQ HRebAzpC1o7U0V4uK/X5wsg= =0pAr -END PGP SIGNATURE- Accepted: mediamate_0.9.3-2.diff.gz to pool/main/m/mediamate/mediamate_0.9.3-2.diff.gz mediamate_0.9.3-2.dsc to pool/main/m/mediamate/mediamate_0.9.3-2.dsc mediamate_0.9.3-2_all.deb to pool/main/m/mediamate/mediamate_0.9.3-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mediamate 0.9.3-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 1 Aug 2003 10:20:38 -0600 Source: mediamate Binary: mediamate Architecture: source all Version: 0.9.3-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: mediamate - web-based movie database and tracker Changes: mediamate (0.9.3-1) unstable; urgency=low . * new upstream version * migrated moviemate configuration to mediamate * added update-movies script (see README.Debian) * includes upstream edit patch * corrected actor search * added /etc/mediamate/modules for all module apache includes Files: d3d43133c122d7b4cc31f1642e5f735e 586 web optional mediamate_0.9.3-1.dsc f7c0722e0e840e0561c63fb48d8a46c7 210257 web optional mediamate_0.9.3.orig.tar.gz 77ebf5c66a590a1bcf0c7d9983d86236 9129 web optional mediamate_0.9.3-1.diff.gz d27aec2e96a19de913bc35b9783c6e17 197202 web optional mediamate_0.9.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/U6wCCZSR95Gw07cRAn2aAKCL/NuaujWR9VQU/ZIcOqxXq+v/RACfSftr c7wl1XIwBDKmFY3u0uGbz+Q= =6uKG -END PGP SIGNATURE- Accepted: mediamate_0.9.3-1.diff.gz to pool/main/m/mediamate/mediamate_0.9.3-1.diff.gz mediamate_0.9.3-1.dsc to pool/main/m/mediamate/mediamate_0.9.3-1.dsc mediamate_0.9.3-1_all.deb to pool/main/m/mediamate/mediamate_0.9.3-1_all.deb mediamate_0.9.3.orig.tar.gz to pool/main/m/mediamate/mediamate_0.9.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted moviemate 0.9.3-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 26 Aug 2003 14:31:19 -0600 Source: moviemate Binary: moviemate Architecture: source all Version: 0.9.3-1 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: moviemate - web-based movie database and tracker Changes: moviemate (0.9.3-1) unstable; urgency=low . * empty package to facilitate name change to mediamate Files: 6fc30bafa339c66378303f963197d343 516 web optional moviemate_0.9.3-1.dsc 756a5ab382368fbb7105ec17be4d5c22 3162 web optional moviemate_0.9.3-1.tar.gz d7c8371893879e4181891df562e68f25 3504 web optional moviemate_0.9.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/U6wTCZSR95Gw07cRAq91AJ0cUfRQXM7vb0HZFOiJCbjyubJSVwCdEYam jGdeRz/bgaL84iYazZ9EA9A= =fm9a -END PGP SIGNATURE- Accepted: moviemate_0.9.3-1.dsc to pool/main/m/moviemate/moviemate_0.9.3-1.dsc moviemate_0.9.3-1.tar.gz to pool/main/m/moviemate/moviemate_0.9.3-1.tar.gz moviemate_0.9.3-1_all.deb to pool/main/m/moviemate/moviemate_0.9.3-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-DD contributors and the debian keyring
On Tue, Aug 26, 2003 at 10:36:07AM +1000, Glenn McGrath wrote: If there was a keyring where peoples keys would only be accepted if it were signed by someone in the developer keyring, then it would 1) Extend debians web of trust. 2) Debian would be taking more responsability for itself. 3) Debian would be supporting non DD who are contributing to the the project. 4) Create a staging area for future DD's keys, where they can get somee experience managing their key. What are the reasons not to do it (keeping in mind my point 2) ? Items 1-3 are already addressed with DD signatures on other individuals keys on public key servers. Item 4 can be addressed with public key servers too. I'm not against Debian having another key ring, I simply don't see a specific need for one, although Goswin did bring up some good points. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: Snort: Mass Bug Closing
On Tue, Aug 26, 2003 at 11:07:00AM -0400, Matt Zimmerman wrote: On Mon, Aug 25, 2003 at 09:04:08AM -0600, Jamin W. Collins wrote: Actually that's not true, as an example I refer you to SSH. A stunning example of what a terrible idea it is to do this. Never said it was a good idea, just that it did and has happened. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: Snort: Mass Bug Closing
On Mon, Aug 25, 2003 at 10:19:55AM +0200, Sander Smeenk wrote: The problem is that the buglist i'm having on snort now, consists of mainly bugs filed on the stable package of snort, which has been long solved in the later releases of snort that didn't make it in the release of Debian. So, tag them as such. If you close them, they will just be reopened by the next individual to find it in the stable package. Tagging it with the release effected. We've been over this in debian-security before. I fixed the 1.8.4 package once, it got rejected, and I tried to have 2.0.x installed in Stable, but ofcourse, you can't put a new upstream version in a released stable Debian. Actually that's not true, as an example I refer you to SSH. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: non-DD contributors and the debian keyring
On Mon, Aug 25, 2003 at 05:18:45PM +0200, Sven Luther wrote: On Wed, Aug 20, 2003 at 05:03:17PM -0400, Stephen Frost wrote: * Martin Quinson ([EMAIL PROTECTED]) wrote: On Wed, Aug 20, 2003 at 09:40:02AM -0400, Stephen Frost wrote: keyring.debian.org has only DDs in it. I think people were suggesting using the public keyservers. keyring.debian.org isn't a part of the public key servers. That's the part of the system I was criticizing :) Not going to change. Why ? Because there is no need for it to change. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: non-DD contributors and the debian keyring
On Mon, Aug 25, 2003 at 07:16:31PM +0200, Sven Luther wrote: On Mon, Aug 25, 2003 at 10:35:17AM -0600, Jamin W. Collins wrote: Because there is no need for it to change. Err, why not, What is the goal? To indicate that the e-mail signed came from someone in possession of person X's private key. X's public key can be put up on existing public key servers. There are already numerous public key servers functioning and no need for keyring.debian.org to be another. What would be the problem to adding another 'official' debian keyring for those people in the project who don't need to upload packages, but may be otherwise active in the project. The lack of need. Why is such a keyring needed? What purpose would it serve that public key servers don't already? We already have, if i am not mistaken, an emeritus keyring and other such, is the idea of adding a contributor, or translator, or whatever keyring such a big issue ? Don't know if it's an issue (wouldn't think it was), but rather a question of need, see above. If it is not possible for technical reasons, then explain, if you feel the project don't need translator or other documentation writers, then say it and explain your position, but this no and it is not going to change is not acceptable as a response. I've never indicated in any way that the Debian project doesn't need translators. Please reread my statements. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: Snort: Mass Bug Closing
On Sun, Aug 24, 2003 at 03:57:45PM +0200, Sander Smeenk wrote: Before you object to this rather 'rude' bughandling, please keep in mind that version 1.8.4 of snort, which is in stable, has 3 severe security exploits, So, why hasn't a security update been released for it? -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: Monitoring RC bugs
On Thu, Aug 21, 2003 at 08:05:01PM +0100, Colin Watson wrote: So, all mails sent to bugs with release-critical severities, including acknowledgements of control messages, will now be copied to a new list: [EMAIL PROTECTED] Very nice! -- Jamin W. Collins To be nobody but yourself when the whole world is trying it's best night and day to make you everybody else is to fight the hardest battle any human being will fight. -- E.E. Cummings
Re: #206298 spip: prerm script blindly removes directories
On Wed, Aug 20, 2003 at 01:45:09PM +0200, Gaetan Ryckeboer wrote: Package: spip Version: 1.6.0-2 Severity: normal The prerm script blindly deletes the following directories and all subdirectories: /var/cache/spip /usr/share/spip/ecrire/upload /usr/share/spip/ecrire/data There is no guarantee that the files in these directories belong only to this package. While it is quite likely that they will, it can not be guaranteed and care should be taken on package removal to not remove any files that are not owned solely by the package. All right. I understand the problem. But the directories removed by the postrm/purge are normaly only used : - by user, to upload datas related to his spip installation, Is this uploaded data recorded anywhere? In the MySQL database perhaps? If so, the file names can be retrieved from there for removal on purge. Additionally, you may upset users by simply deleting their uploaded files on purge. Some may see this as deletion of user data, which should not be done. - by spip himself, to store cache informations, Are the file names predictable in any way? If so, you can look for files fitting the pattern. - by spip himself, for log or backups. The file names of the logs or backups should be predictable, right? As someone else has already pointed out, /usr/share should be capable of being made read-only. Any runtime changing data for an application should be under /var/lib. For more information the following link may help: http://www.debian.org/doc/packaging-manuals/fhs/fhs-toc.html -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: #206298 spip: prerm script blindly removes directories
On Wed, Aug 20, 2003 at 05:38:42PM +0200, Gaetan Ryckeboer wrote: Le Wed, Aug 20, 2003 at 09:26:14AM -0600, Jamin W. Collins a ?crit : Is this uploaded data recorded anywhere? In the MySQL database perhaps? If so, the file names can be retrieved from there for removal on purge. Mmm... yes and no. Some of them could be. But a user may upload files without using them in the application. So, the files are available, but unused, and unreferenced. That would appear to be a deficiency of the spip app and one that should probably be brought to the upstream developers attention. The application should probably log all uploads. Additionally, you may upset users by simply deleting their uploaded files on purge. Some may see this as deletion of user data, which should not be done. Of course, I understand. But I wonder they won't upload personal files for another use than spip here... This falls into something of a grey area. Can the data concievably be of value ot the user without spip? If so, then it is probably user data and should not be removed without confirmation from the user (debconf prompt that defaults to no?) As someone else has already pointed out, /usr/share should be capable of being made read-only. Any runtime changing data for an application True. But due to the implemntation of the application, which is written in php, datas are stored on the program dir. There is no real separation between datas and functions. And if i symlink some datas (for apache access AND direct file handler access), i'll will setup another alarm... and it won't be accepted. So, use Alias directives to relocate the directories that need changing data to /var/lib. There is no need to use symlinks to accomplish this. As a matter of fact, your current apache include enables the following of symlinks, which it doesn't need and probably shouldn't. I can provide examples of this if you need. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: Debian Weekly News - August 19th, 2003
On Wed, Aug 20, 2003 at 05:30:39PM +0200, J?r?me Marant wrote: Quoting Scott James Remnant [EMAIL PROTECTED]: No he wouldn't. FDL is about free documentation. :-) Except it isn't :-) According to you :-) This has been covered to death already. There are a sufficient number of respondents that see it as non-free. The RM's recent post indicates that possibly the FSF has even come around to the idea that their license is less than Free. Can we please move along now? -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: #206298 spip: prerm script blindly removes directories
On Wed, Aug 20, 2003 at 07:53:41PM +0200, Gaetan Ryckeboer wrote: Not necessary. Web administrators may upload files via FTP, andspip users never use them onto spip ? If so, the files will stay in place in upload, instead of beeing integrated onto the spip tree at the right place, and being logged in the sql database. In which case should you be deleting them? I would say no. While they are in that directory, they are not used by spip and thus not really a part of spip. The user(s) put them there, when in doubt, leave them there. Yes it needs. I've still moves documentation to usr/share/doc, instead of spip/ecrire/doc, but it is rather different with the cache and other application managed files. You may access the php files via apache, but php files may access to other php file, or static file. For instance, to modify the configuration, or read the cache. Yes, symlinks are needed for direct file access (unless you patch the source). Sorry, when I stated symlinks weren't needed I meant on the Apache side. I've dealt with this exact problem in my packaging of Media Mate (new name for Movie Mate). I'm currently using symlinks to allow the php script to access files by the paths they expect and Apache Alias directives to allow http requests to get the files without enabling symlink following. I accept. Please send me examples in private, if you found a way to move php files accessing each other (via include) in another directory, without patching the application. I'll forward Media Mate's packaging over to you. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: Proposal: make kernel install easier
On Wed, 2003-08-20 at 14:46, Manoj Srivastava wrote: On 20 Aug 2003 10:51:54 -0400, Adam C Powell IV said: Greetings, Installing a new kernel package can be a bit of a pain, especially for newbies, what with hand-editing lilo.conf or config Why on earth are you hand editing the lilo.conf file for every kernel image? Well, if they move from an installation kernel to a kernel-image package, they have to add an entry for an initrd file. After that, if they upgrade to another kernel-image package and want to be able to use both the new and the old they need to edit the old entry for an initrd too. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
How to locate package uploader?
Is there any way to find out who uploaded a given package? Specifically, I'm interested in learning who uploaded the spip package. I know it lists Gaetan RYCKEBOER as the maintainer, but this individual doesn't appear to be listed in the Debian keyring (this would mean they couldn't have uploaded it as I understand) and doesn't appear to be listed in the list of NM applicants. So, I'm assuming that there must be a sponsor for the upload, but is this information kept anywhere? -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: About NM and Next Release
On Fri, Aug 08, 2003 at 08:29:54AM +0100, Andrew Suffield wrote: On Thu, Aug 07, 2003 at 04:55:19PM -0700, Steve Lamb wrote: That, however, is not enough in and of itself. I *could* very well contribute to FreeBSD. I don't. Why? Because I don't like FreeBSD. I like Debian. You're misconstruing that the statement is you like it therefore you should contribute when it is is I like it therefore I want to contribute. Actually, you have misconstrued it the other way. It really was You like it therefore you should contribute. I didn't take it that way, the statement seemed rather clear that it was a matter of liking the project and wanting to contribute to it, not a matter of feeling like one should. -- Jamin W. Collins To be nobody but yourself when the whole world is trying it's best night and day to make you everybody else is to fight the hardest battle any human being will fight. -- E.E. Cummings
Access to an ARM system?
Does someone have an ARM system that I could gain access to? I'd really like to put the ARM specific bug[1] filed against the Jabber package to bed once and for all. I've seen reports of Jabber running on ARM systems and of course the bug report of it segfaulting. Any assistance in this matter would be most appreciated. I've sent a request to debian-admin, but have heard nothing back from them. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar [1] - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=142599
Re: Access to an ARM system?
On Fri, Aug 08, 2003 at 12:00:37PM -0700, Marc Singer wrote: On Fri, Aug 08, 2003 at 12:55:11PM -0600, Jamin W. Collins wrote: Does someone have an ARM system that I could gain access to? I'd really like to put the ARM specific bug[1] filed against the Jabber package to bed once and for all. I've seen reports of Jabber running on ARM systems and of course the bug report of it segfaulting. Any assistance in this matter would be most appreciated. I've sent a request to debian-admin, but have heard nothing back from them. I have a couple of ARM boards that boot Debian. I'm not sure what it is you want to do on the machine. What is it you are trying to do? Ideally, get an installation of Jabber (from the debian package binaries) to run and accept a client connection. According to the bug report, the Jabber server segfaults on startup. So, if I can get the server up and running and connect to it, I'd consider that something of a success. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: Access to an ARM system?
On Fri, Aug 08, 2003 at 12:45:10PM -0700, Marc Singer wrote: So, you want the Jabber server installed on an ARM system so that you can connect to it and either a) verify that it crashes, or b) demonstrate that it doesn't. That's about the size of it. If this is so, then I can do this for you and give you a routable address to the ARM machine. Do you need to be able to do anything *on* the ARM? I think I can get ssh and some other utilities running on it. Only if it crashes. Then I might need strace and maybe build dependancies to try a new build with pth2. However, these can also probably be worked around. Still, let me be clear. I am using a Sharp KEV7A400 for some embedded systems development. I have a script that produces stripped-down filesystems for the target using the Debian package archive. It isn't hard for me to add programs to the filesystem, but I need to know exactly what has to be there since this isn't exactly an 'apt-get install' situation. Ahhh, now I understand. Well, simply adding the Jabber package and seeing if it will start on the system should be enough. Shouldn't need to change any config files for the test. Once it's running I'd simply need an IP that I can connect to port 5222 on to send some tests. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: About NM and Next Release
On Thu, Aug 07, 2003 at 06:00:53PM +0200, Nicolas Bertolissio wrote: Le jeudi 7 ao?t 2003, Goswin von Brederlow ?crit : WE NMs WANT FEEDBACK. Someone please tell the DAM already to activate YOU, not 'we', YOU are impatient, YOU are cannot wait any more, I am waiting for DAM approval, so I just wait... Just because you don't wish to be included in the 'we' doesn't mean there isn't more than just Goswin in the NM queue that would like to see updates and feedback. I know of several (myself included) that would like to see updates to their applications. Does this mean that we cannot wait any more, no. We are still waiting. However, this doesn't mean that we are happy with the way the queue has been handled in the past. We see room for improvement. However, we are not in a position to directly effect a change of the situation. So, the options are to wait silently or attempt to change it through making others aware of the problems. It's not a question of cannot wait any more it's a question of courtesy. Are you saying that you do not want, and would not welcome, feedback on your application? I'm not asking whether you would clamor for updates, but whether receiving them would be a problem for you? -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: About NM and next release
On Thu, Aug 07, 2003 at 11:57:32PM +0100, Andrew Suffield wrote: On Thu, Aug 07, 2003 at 04:56:44PM -0400, Nathanael Nerode wrote: Wrong. There have been specific technical things I wanted to do which simply cannot be done easily as an outsider. Generally it's QA stuff. I'm doing it anyway, of course; it's just slower and more tedious and discouraging. You just contradicted yourself. It's clearly not wrong - you *are* doing it anyway. So the system works as it is supposed to. Just because it _can_ be done under the current system doesn't mean that the current system isn't broken or in need of improvement. Some of us feel it can be done _better_. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: NM non-process
On Wed, Aug 06, 2003 at 08:41:20AM -0400, Matt Zimmerman wrote: On Wed, Aug 06, 2003 at 04:56:59AM +0200, Goswin Brederlow wrote: I know of several DDs and non-DDs thinking about creating a Debian2 (or whatever named) project due to this and other lack of responce problems and the group is growing. The danger is already there and should not be ignored. Why is this a danger? This is one of the freedoms provided by free software, which we work hard to promote. Because while it is one of the freedomes provide by free software, and one we work hard to promote, there would be a lot of time and effort in setting up another Debian-like infrastructure. This effort could be put toward the current Debian infrastructure if it was accepted (which remains to be seen), rather than to reimplementing a good deal of the already existing infrastructure for another project. This could in some ways result in something of a competition for developers between the two projects, thus resulting in each being something less than they could have been as one. -- Jamin W. Collins
Re: NM non-process
On Wed, Aug 06, 2003 at 04:09:15PM -0400, Matt Zimmerman wrote: On Wed, Aug 06, 2003 at 03:16:12PM -0400, Nathanael Nerode wrote: Matt Zimmerman wrote: And neither does the fact that some have been there for years indicate anything in particular. Here is where you're entirely and totally wrong. It indicates a breakdown in the communication process. Communication with whom? I don't think that anyone besides the applicant himself needs to be informed. Based on the e-mails from many of these applicants (private and to the list), the applicants are *not* being informed at all. As for whether the applicant is the only one that should be informed, I disagree. If there's a problem with the application it should be clearly noted on the application status. If these people are being delayed for a reason, the reason needs to be written down publically in the appropriate place. I disagree; if the applicant knows why they are being delayed, then the fact that this information is not published on the website does not indicate that the process is broken. That's a pretty big *if*, and as I've indicated above the applicants don't seem to be informed or contacted. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: NM non-process
On Wed, Aug 06, 2003 at 10:22:01PM -0400, Matt Zimmerman wrote: On Wed, Aug 06, 2003 at 05:34:06PM -0600, Jamin W. Collins wrote: On Wed, Aug 06, 2003 at 04:09:15PM -0400, Matt Zimmerman wrote: I disagree; if the applicant knows why they are being delayed, then the fact that this information is not published on the website does not indicate that the process is broken. That's a pretty big *if*, and as I've indicated above the applicants don't seem to be informed or contacted. This condition was directed at people who seem to be complaining about the process without being involved in it, nor in communication with those who are. These days, there are more complaints about NM from the peanut gallery than from the applicants themselves. Perhaps that's because the applicants have found that their attempts to voice their complaints are ignored. Just because someone is in the peanut gallery doesn't mean they can't see a problem with the current state of things WRT the NM queue. A recent run (moments ago) of my nm-status script shows that there are a number of new comments that have been added to some of the applicants that are awaiting DAM approval. This looks rather promising. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: package name change (moviemate - mediamate)
On Thu, Jul 31, 2003 at 09:46:43AM +0200, Matthias Urlichs wrote: Hi, Jamin W. Collins wrote: The old DB works fine after the upgrade against it. The questions are. Whether removing the configuration files (/etc/moviemate) is a taboo, even though the configuration is migrated (/etc/mediamate). Leave it there. What if the user wants to downgrade? Then there would be a problem either way since the DB format changed between versions. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
package name change (moviemate - mediamate)
What is the preferred method of effecting a package rename and upgrade between versions? Movie Mate v0.9.2 is currently in the Debian archive. Due to upstream changes (added tracking for other media types), the name has been changed to Media Mate. Thus, Media Mate is the upgrade to Movie Mate. This leaves me with the question of how to properly change the package name and upgrade installations of the older package. In building the new Media Mate package, I've declared a Conflicts with the moviemate package to effect moviemate's uninstall when the mediamate package is installed. However, this leaves the question of migrating the moviemate's configuration to mediamate. For this, I pull the debconf answers for moviemate's questions and set them as the answers to mediamate's questions (which are mostly the same), and set the _seen_ flag to true so the questions will not be asked (much like an upgrade where the package name has not changed). Since the package name has changed, the configuration and data files are now stored in different locations. So, I plan on moving the data files to their new location. But, what about the old configuration files, and the old package's state in dpkg? Should these be removed since the new package is installed (more or less an upgrade) or should these be left because the old package hasn't been purged and the new one has a different name? Also, moviemate has asks a question during install about removing the DB on purge, with the answer stored in debconf's db. During the upgrade would it be acceptable to clear this answer under moviemate once it's been migrated to mediamate since the old DB is upgraded and used by mediamate and a purge of moviemate would then remove a database that's still in use? Or, should mediamate copy the old database and and leave it for moviemate to potentially purge? Personally, I'm leaning toward having the new package manually remove all the old packages configuration files and unsetting the DB purge flag. But, I can see how this may be seen as a bad thing. Thus, I figured I'd ask here for comments and suggestions on how to handle this type of situation. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: package name change (moviemate - mediamate)
On Wed, Jul 30, 2003 at 06:17:17PM -0700, Sean 'Shaleh' Perry wrote: you should Conflict, Replace, and provide MovieMate. This will ensure a smooth transition. You instead (may) want to upload a package called moviemate which is a dummy package that depends on MediaMate. Remember, if the user has MovieMate installed they will not get MediaMate without actually asking for it. I was thinking about the dummy package approach, but then the dummy package would just hang around indefinitely, right? how much work is involved in hiding this from the user? In general you should try to just make things work. The packaging details are something our users should not need to know about. Remember from their perspective nothing changed. Not a whole lot, I've got the answers being migrated already. if you can scarf in the old db and make the upgrade just work, that is the preferred approach. Of course that may prove to be too complicated or you may just not have enough time. The old DB works fine after the upgrade against it. The questions are. Whether removing the configuration files (/etc/moviemate) is a taboo, even though the configuration is migrated (/etc/mediamate). And, whether blanking the answer to the DB purge from moviemate's install is seen as a problem. I think if I do the above two items I can provide a very smooth transition from moviemate to mediamate that a user really won't notice (as far as the backend changes). I'd just like to know if anything I'm planning is frowned upon or can be done better. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: should bugs really be closed?
On Tue, Jul 29, 2003 at 06:28:42PM +0100, Andrew Suffield wrote: I think he just wants them kept open until the old gcc versions get removed from the archive. That does make a certain amount of sense. Could tag them with the release name that affected release name (woody, sarge, sid, etc...). It's what I've done with the Jabber bug reports that only affect the woody release. -- Jamin W. Collins To be nobody but yourself when the whole world is trying it's best night and day to make you everybody else is to fight the hardest battle any human being will fight. -- E.E. Cummings
Re: Future releases of Debian
On Fri, Jul 25, 2003 at 04:25:57PM +0100, Scott James Remnant wrote: On Thu, 2003-07-24 at 19:34, Jamin W. Collins wrote: So, are you volunteering to help those of us without access to either of the above architectures with bugs found in our packages? I'm not saying that all architectures shouldn't be supported equally. I just don't have access to either of the above architectures to correct problems found in my packages. Strange, the rest of us Debian Developers have access to all of these strange platforms ... http://raw.no/debian/machines.html By the rest of us Debian Developers I assume you mean *full* Debian Developers (those of you with DD accounts). Perhaps you haven't read the rest of this thread. I'm not a *full* DD and thus don't have access to all the resources a *full* DD has. As I've inferred elsewhere this is one of the problems with keeping NMs in queue waiting on one approval for several months (and potentially years). If your package has a bug affecting arm, login to debussy and fix it. If your package has a bug affecting mips, login to casals and fix it. If your package has a bug affecting m68k, login to kullervo and fix it. Would be happy to. Unfortunately, I can't, don't have an account. If you're going to claim that you don't have the knowledge to investigate and fix difficult problems, perhaps you should reconsider whether you are able to maintain your packages? I never claimed I didn't have the knowledge to fix it. I stated I don't have access to the architecture. Lacking access to a resource does not mean one lacks the knowledge of how to preform tasks on/with the resource. Who is sick of this I don't have an m68k box to fix my bug excuse. That's cool, because I'm a little sick of the assumptions that someone has access to resources because they maintain X package. Not everyone listed on http://www.debian.org/devel/people is a full Debian Developer. As such, not all of them have access to the resources available to full Debian Developers, or even the rights of them. Yet, we are expected to function as one and are berated by some DDs when we state we don't have access to some resources. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: Future releases of Debian
On Fri, Jul 25, 2003 at 05:31:36PM +0200, Adrian Bunk wrote: On Thu, Jul 24, 2003 at 02:23:30PM -0600, Jamin W. Collins wrote: Now you're assuming that I have access to the Debian machines. TMK, these machines are *not* public access machines, but instead are accessible to full DDs only. This excludes all new maintainer applicants, myself included. The DAM discussion is a different discussion, no need to restart it in this thread. I didn't attempt to restart it, I simply point out a flaw in the argument provided. There are at least two ways how you can get an account on a machine in such a situation: - ask the Debian admins for a guest account on a machine of this architecture I was not aware that this was an option. Is this documented somewhere as an option to NMs or others? I for one never considered it because TMK it was restricted to full DDs only. If this is not the case, documentation to that effect could be very helpful. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: Future releases of Debian
On Fri, Jul 25, 2003 at 06:46:16PM +0200, Adrian Bunk wrote: On Fri, Jul 25, 2003 at 09:45:01AM -0600, Jamin W. Collins wrote: ... There are at least two ways how you can get an account on a machine in such a situation: - ask the Debian admins for a guest account on a machine of this architecture I was not aware that this was an option. Is this documented somewhere as an option to NMs or others? I for one never considered it because TMK it was restricted to full DDs only. If this is not the case, documentation to that effect could be very helpful. I don't know whether it's documented somewhere. All I know is that it worked in the past and it's worth trying it. It's certainly worth trying, and I'll keep it in mind. However, the information I did find on it lead me to believe it would be pointless to request access to these machines since they were for Debian Developers only, and they would get access (more or less automatically) because they were a Debian Developer. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: Future releases of Debian
On Thu, Jul 24, 2003 at 08:25:16PM +0200, Robert Lemmen wrote: On Thu, Jul 24, 2003 at 08:39:11PM +0300, Halil Demirezen wrote: Are we in dilemma on should we support arch that are not used widely? or We should support all architectures what i prefer is the second one. me too! any package that doesn't build on m68k or arm is broken and needs to be fixed, even if it works on x86 by chance! So, are you volunteering to help those of us without access to either of the above architectures with bugs found in our packages? I'm not saying that all architectures shouldn't be supported equally. I just don't have access to either of the above architectures to correct problems found in my packages. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: Future releases of Debian
On Thu, Jul 24, 2003 at 10:12:11PM +0300, Halil Demirezen wrote: So, are you volunteering to help those of us without access to either of the above architectures with bugs found in our packages? I'm not saying that all architectures shouldn't be supported equally. I just don't have access to either of the above architectures to correct problems found in my packages. do you mean you do not have any archs to test them out? All over the world someone probably have access to them. Quitting support is not the aim of Debian. However, If you talk about Commodorre 63, I say ok. Yes, I do not have access to them for testing or debugging. I have access to only x86 machines currently. Thus, I can not adequately resolve problems with my packages on arm or other architectures. This is currently a bug report for Jabber concerning a segfault on the arm architecture, I can not replicate the problem and thus can not resolve it. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Re: Future releases of Debian
On Thu, Jul 24, 2003 at 03:52:38PM -0400, David Z Maze wrote: Jamin W. Collins [EMAIL PROTECTED] writes: On Thu, Jul 24, 2003 at 08:25:16PM +0200, Robert Lemmen wrote: me too! any package that doesn't build on m68k or arm is broken and needs to be fixed, even if it works on x86 by chance! So, are you volunteering to help those of us without access to either of the above architectures with bugs found in our packages? But Debian has ~public machines for pretty much every architecture. I'd say look on http://db.debian.org/machines.cgi;, except that's down; I can at least point you at section 4.4 of the Developer's Reference, though that doesn't say a whole lot beyond this. I admit that this doesn't necessarily help for testing installers, but for your own packages it should be straightforward for you to do testing and bugfixing even on architectures you don't personally own a machine for. Now you're assuming that I have access to the Debian machines. TMK, these machines are *not* public access machines, but instead are accessible to full DDs only. This excludes all new maintainer applicants, myself included. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: Future releases of Debian
On Thu, Jul 24, 2003 at 04:23:29PM -0500, Steve Langasek wrote: On Thu, Jul 24, 2003 at 01:08:40PM -0600, Jamin W. Collins wrote: Yes, I do not have access to them for testing or debugging. I have access to only x86 machines currently. Thus, I can not adequately resolve problems with my packages on arm or other architectures. This is currently a bug report for Jabber concerning a segfault on the arm architecture, I can not replicate the problem and thus can not resolve it. This does not excuse broken, ugly x86isms in packages. Did I say it excused them? No! Please refrain from trying to put words in my mouth. The vast majority of portability problems are NOT confined to a single oddball architecture; they may manifest in different ways, but the bugs are usually there on multiple architectures at once. If you don't directly have the hardware or experience to debug a particular problem, there are several mailing lists (debian-mentors, debian-devel, or upstream) where it might be appropriate to ask. The jabber bug in question doesn't even have a 'help' tag -- nor does it have a severity appropriate for a bug that renders a package completely inoperable on a given architecture. It doesn't have a help tag, but it does have both unreproducible, and moreinfo. The definition of unreproducible is: unreproducible This bug can't be reproduced on the maintainer's system. Assistance from third parties is needed in diagnosing the cause of the problem. So, it would seem that the bug was appropriately tagged, and a request for help was made. Tagging the bug with help would have fulfilled the help request, but whould not have been as accurrate a tag. help The maintainer is requesting help with dealing with this bug. I tagged it for assistance as of: 13 Apr 2003 -- Jamin W. Collins To be nobody but yourself when the whole world is trying it's best night and day to make you everybody else is to fight the hardest battle any human being will fight. -- E.E. Cummings
RFS: jabber transports and services
I'm hoping that one (or more) of the DDs here might be willing to sponsor one (or more) of the following packages. All of these have either an RFP or ITP filed for them. I have updated the ITP entries that where not filed by me and asked to assume the ITP, Evan (the original ITP filer in both cases) is amiable to this. jabber-aim - Jabber AIM transport jabber-jit - Jabber ICQ transport jabber-jud - Jabber User Directory service jabber-msn - Jabber MSN transport jabber-muc - Jabber Multi-User Chat service jabber-yahoo - Jabber Yahoo transport The packages can be found at: http://asgardsrealm.net/~jcollins/debs/ Note: jabber-jit is in need of a manpage, but otherwise passes all Lintian checks. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
Accepted jabber 1.4.2a-11 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 23 Jul 2003 11:27:52 -0600 Source: jabber Binary: jabber-dev jabber Architecture: source i386 Version: 1.4.2a-11 Distribution: unstable Urgency: low Maintainer: Jamin W. Collins [EMAIL PROTECTED] Changed-By: Jamin W. Collins [EMAIL PROTECTED] Description: jabber - Daemon for the jabber.org Open Source Instant Messenger jabber-dev - Daemon for the jabber.org Open Source Instant Messenger Closes: 177097 195108 202518 Changes: jabber (1.4.2a-11) unstable; urgency=low . * corrected init script bashism (Closes: #195108) * added description indication that this is not a client (Closes: #177097) * restart now sleeps 3 seconds between stop and start (Closes: #202518) * added /etc/jabber/jabber.d hook directory and init script support * changed location of jabber-config to /usr/lib/jabber * added one line fix to mod_auth_0k.c * updated postrm to play nice and share directories Files: 6443fcf49236ab4e919ad20b60af028a 603 net optional jabber_1.4.2a-11.dsc e76101006ec23b64f6da468ad034a06d 94627 net optional jabber_1.4.2a-11.diff.gz 1ec23ea1c649911edda952e3d98617d7 190516 net optional jabber_1.4.2a-11_i386.deb f5e2c8bedd0381882eb1fbd4886322a7 40638 devel optional jabber-dev_1.4.2a-11_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/H0dkCZSR95Gw07cRAve7AJ9kgoeEhkAQ8I4tUUYgy9QVDtp2yQCaAqLf BTqHRUkwtyonT9YjNpDq4KQ= =UxXK -END PGP SIGNATURE- Accepted: jabber-dev_1.4.2a-11_i386.deb to pool/main/j/jabber/jabber-dev_1.4.2a-11_i386.deb jabber_1.4.2a-11.diff.gz to pool/main/j/jabber/jabber_1.4.2a-11.diff.gz jabber_1.4.2a-11.dsc to pool/main/j/jabber/jabber_1.4.2a-11.dsc jabber_1.4.2a-11_i386.deb to pool/main/j/jabber/jabber_1.4.2a-11_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel question: initrd/cramfs
On Sat, Jul 12, 2003 at 06:04:41PM +1000, Herbert Xu wrote: Nenad Antonic [EMAIL PROTECTED] wrote: Apparently, there is a bug (at least from my perspective) which prevents initrd/cramfs in stock kernels, which has been arround for years. On the other hand, this bug gets fixed in every version of debian Why are you trying to use initrd anyway? It's much easier to build the drivers into the kernel. Not if you want the kernel to function on a wide variety of hardware. Plus there are some situations that a monolithic kernel just can adapt to, such as system partitions on a firewire device (sbp2 can't be built into the kernel TMK). -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar
Re: Work-needing packages report for Jul 11, 2003
On Sat, Jul 12, 2003 at 05:06:45PM +0200, Robert J?rdens wrote: Oh guys. I'm waiting some 500 days now. I think that's a record (the current is around 470). And I'm still working and contributing. Some nice other DDs stepped forward and wrote mails to the DAM but that didn't cause anything. No, you've been waiting 188 days (as of today) for DAM according to: http://nm.debian.org/nmstatus.php?email=rjo%40gmx.de According to the above page you application was approved by your AM on 2002-01-04. I'm only referring to the time since the application was approved by AM and DAM became the holdup. You have still been waiting longer, but could still have another 290 days to go (before a new record). So, who does DAM report to? Who can do something about this extremely long wait? -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: Work-needing packages report for Jul 11, 2003
On Sat, Jul 12, 2003 at 07:23:55PM +0200, Mateusz Papiernik wrote: No, you've been waiting 188 days (as of today) for DAM according to: Hm, there are two possibilities: a) I'm blind b) You're wrong Ahh I'm indeed wrong, misread the year both times. You have amazing patience if you haven't bitched about this before. Your situation makes this even more depressing. Here I thought 470 was the current top end, now I find that I may as well not get worked up about it until I've been waiting for nearly 2 years. Something has to change. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: Work-needing packages report for Jul 11, 2003
On Fri, Jul 11, 2003 at 08:49:46AM +0200, Marcelo E. Magallon wrote: I can't believe that the QA people can say, with a straight face, that they are willing to maintain this pile of dung until someone shows up. If we have so many maintainers and there are more at the burg's doors piling over each other in order to enter, why does the WNPP list keep growing like this? Sure there are a number of people at burg's doors waiting to become a Debian Maintainer. I'm one of them. As of today, I've been awaiting DAM approval now for 155 days, with no end to the wait in sight. I've already adopted one orphaned package (Jabber) and made significant improvements to it. However, the 150+ day wait for DAM approval has deterred me from looking at adopting any more packages. Perhaps a requirement of becoming a Debian Maintainer could be the adoption of one of the WNPP packages (assuming there are any in line with the applicants skills). However, the DAM approval process needs serious review. Keeping anyone in awaiting DAM approval for more than 60 days without any kind of notice or update is quite frankly rude and unneeded. -- Jamin W. Collins Remember, root always has a loaded gun. Don't run around with it unless you absolutely need it. -- Vineet Kumar
Re: but I want the GNU versions of packages
On Fri, Jul 11, 2003 at 04:16:30PM +0200, Robert Millan wrote: On Fri, Jul 11, 2003 at 03:43:55PM +0200, Mathieu Roy wrote: Aside from the joke, we are talking about a package available also for Debian GNU/_Linux_, aren't we? Fine, but then it can't be task-gnu-_only_.. maybe task-gnu-usualy? :) The name task-gnu-only seems misleading. From what we said previously, it should be something like task-gnu-when-it-exists. IMHO when-it-exists is missleading also. Bleeding-edge or stuff we don't provide still exists. Fine so call it task-gnu-preferred. -- Jamin W. Collins Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo
