Uploaded xdaliclock 2.18-5 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 28 Dec 2000 14:43:37 -0800
Source: xdaliclock
Binary: xdaliclock
Architecture: m68k
Version: 2.18-5
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Joey Hess [EMAIL PROTECTED]
Description: 
 xdaliclock - Melting digital clock
Closes: 80777
Changes: 
 xdaliclock (2.18-5) unstable; urgency=low
 .
   * Moved a man page, Closes: #80777 (serious?)
Files: 
 fb55248238006d76b94779598c9ec888 35250 x11 optional xdaliclock_2.18-5_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUQiYACgkQcS3JWD3FdvdEDwCfWn+Lr4fWq9eR5TPb+i3juHZK
sHgAnAoOmnUdlhl+n2brFfe6AAXtsCoq
=//fZ
-END PGP SIGNATURE-




Uploaded base-files 2.2.6 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 11:41:55 +0100
Source: base-files
Binary: base-files
Architecture: m68k
Version: 2.2.6
Distribution: unstable
Urgency: medium
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Santiago Vila [EMAIL PROTECTED]
Description: 
 base-files - Debian base system miscellaneous files
Changes: 
 base-files (2.2.6) unstable; urgency=medium
 .
   * Use testing/unstable instead of 2.2 for the distribution number.
 It seems everybody prefers to see something else other than 2.2.
Files: 
 63d33a5daba9373e30299afd95fc813b 29244 base required base-files_2.2.6_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUQJkACgkQcS3JWD3FdvclxwCeODl+jWa6z3R+2uvLK0udz7ZF
pY4An0QiGhMCRLshBHvSZ39xTu/9V5cj
=k4pm
-END PGP SIGNATURE-




Uploaded debconf 0.5.39 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 18:04:39 -0800
Source: debconf
Binary: debconf-utils debconf debconf-doc
Architecture: m68k
Version: 0.5.39
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Joey Hess [EMAIL PROTECTED]
Description: 
 debconf- Debian configuration management system
Closes: 80163
Changes: 
 debconf (0.5.39) unstable; urgency=low
 .
   * To keep debconf out of testing for nother two weeks, I fixed a bug
 involving truncation of excessively-long short descriptions in the
 slang frontend. Closes: #80163
Files: 
 37939d440ff4b9996b8f71ed3f411b31 71588 admin standard debconf_0.5.39_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUQMwACgkQcS3JWD3FdvcDBACfVV3nO1bU2Ly4ugeHfQadCDAN
HQAAnRSxi/6xM0pPl5D/TrQwRgmtPmx7
=x7H1
-END PGP SIGNATURE-




Uploaded iputils 20001110-1 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 26 Dec 2000 15:03:20 +1000
Source: iputils
Binary: iputils-tracepath iputils-ping
Architecture: m68k
Version: 20001110-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Anthony Towns [EMAIL PROTECTED]
Description: 
 iputils-ping - The ping utility from iputils
 iputils-tracepath - The tracepath utility from iputils
Closes: 65597 68973 69472 80250 80251
Changes: 
 iputils (20001110-1) unstable; urgency=low
 .
   * New upstream version. (Closes: Bug#80250, Bug#80251)
   * Removed most of the Debian patches: too much has changed upstream to
 reasonably forward port them. Maxwait argument thus
 disappeared. (Closes: Bug#65597)
   * Shouldn't have any security problems, theoretically. (Closes: Bug#69472)
   * Descriptions have been updated a while ago. (Closes: Bug#68973)
 .
   * Orphaned, maintainer set to debian-qa.
Files: 
 4174a091e47ff576fa3d12505b0a6bc6 26502 net extra 
iputils-ping_20001110-1_m68k.deb
 c12e5ae39214ea4ca0d8c6127d61d749 13060 net extra 
iputils-tracepath_20001110-1_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUUxoACgkQcS3JWD3Fdve0VgCeODg4bbbV6Rzy4hAvU9lzn80v
c/4An2tuNs/tjvaCuIUXZQeATnVvkmEM
=/owz
-END PGP SIGNATURE-




Uploaded irssi-text 0.7.97.2-1 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 19 Dec 2000 15:22:56 +0200
Source: irssi-text
Binary: irssi-text
Architecture: m68k
Version: 0.7.97.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Pekka Aleksi Knuutila [EMAIL PROTECTED]
Description: 
 irssi-text - text-mode version of the irssi IRC client
Changes: 
 irssi-text (0.7.97.2-1) unstable; urgency=low
 .
   * New upstream release
Files: 
 935c2e1729a065ab8f8871348f2d2b6a 844124 net optional 
irssi-text_0.7.97.2-1_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUTnAACgkQcS3JWD3FdvdVwgCfRNY5Dl7QbEqj9+c1VpwjdrXY
rAAAnjPkb/jyMUvyVKShojPaQoLiSyZ/
=AbDb
-END PGP SIGNATURE-




Uploaded ruby 1.6.2-1 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 25 Dec 2000 16:20:47 +0900
Source: ruby
Binary: libreadline-ruby libtk-ruby libnkf-ruby libpty-ruby libsdbm-ruby 
ruby-dev ruby libgdbm-ruby libcurses-ruby irb ruby-examples libruby libdbm-ruby 
libtcltk-ruby ruby-elisp
Architecture: m68k
Version: 1.6.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: akira yamada [EMAIL PROTECTED]
Description: 
 libcurses-ruby - Curses interface for scripting language Ruby.
 libdbm-ruby - DBM interface for scripting language Ruby.
 libgdbm-ruby - GDBM interface for scripting language Ruby.
 libnkf-ruby - Network Kanji code conversion Filter for Ruby.
 libpty-ruby - pseudo tty interface for the scripting language ruby.
 libreadline-ruby - Readline interface for the scripting language ruby.
 libruby- Libraries necessary to run the ruby.
 libsdbm-ruby - SDBM interface for scripting language Ruby.
 libtcltk-ruby - Tk interface for scripting language Ruby.
 libtk-ruby - Tk interface for scripting language Ruby.
 ruby   - An interpreter of object-oriented scripting language Ruby.
 ruby-dev   - Header files for compiling extension modules for the Ruby.
Changes: 
 ruby (1.6.2-1) unstable; urgency=low
 .
   * Upgraded to new upstream version.
Files: 
 a983a040faefb7102a97d9289f0c098d 104980 interpreters optional 
ruby_1.6.2-1_m68k.deb
 be4172e8776f64f6dd5da82d6cb8d57e 448680 interpreters optional 
libruby_1.6.2-1_m68k.deb
 b7e41810da90bb4a31a21914adaab305 430636 interpreters optional 
ruby-dev_1.6.2-1_m68k.deb
 25574159af0aef103e3e956be06d51c1 98384 interpreters optional 
libcurses-ruby_1.6.2-1_m68k.deb
 61b56fa2b06536c629b305fbf658a89f 96736 interpreters optional 
libdbm-ruby_1.6.2-1_m68k.deb
 d7d936a8ae259f82b7364559efd8050f 96848 interpreters optional 
libgdbm-ruby_1.6.2-1_m68k.deb
 740e7065302033aeaf0dcb735f2f7db3 102704 interpreters optional 
libnkf-ruby_1.6.2-1_m68k.deb
 02bb161dc8bb64e700d34edae25edc82 100736 interpreters optional 
libpty-ruby_1.6.2-1_m68k.deb
 f50cb85fc64289a15b8ec5e4bb4827c5 96656 interpreters optional 
libreadline-ruby_1.6.2-1_m68k.deb
 19379cff7dee9b017118c225d9663cb5 99208 interpreters optional 
libsdbm-ruby_1.6.2-1_m68k.deb
 b8cf09acf01271f1d507d90c141e39ac 116360 interpreters optional 
libtcltk-ruby_1.6.2-1_m68k.deb
 f85233725b6d5a60475325727b414c35 130872 interpreters optional 
libtk-ruby_1.6.2-1_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUU34ACgkQcS3JWD3FdvcuJQCfTOrMlsib4cMl7/nNbuBVPeI0
4J8AnArrl9eV0gN9DKGxNK7uEHKuiZyG
=riwJ
-END PGP SIGNATURE-




Uploaded bonnie++ 1.00g (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 1 Jan 2001 14:29:32 +1100
Source: bonnie++
Binary: bonnie++
Architecture: m68k
Version: 1.00g
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Russell Coker [EMAIL PROTECTED]
Description: 
 bonnie++   - Hard drive bottleneck testing benchmark suite.
Closes: 53545 53546 61925 64995 70331
Changes: 
 bonnie++ (1.00g) unstable; urgency=low
 .
   * Fixed a bug in zcav that prevented it working with parameters other than
 the file name.
 .
   * Updated to standards version 3.2.1.
 .
   * Closes:#70331
 Fixed this a couple of versions ago.
 .
   * Fixed these bugs ages ago but being a sponsored package had confused the
 bug tracker:
 Closes:#53545
 Closes:#53546
 Closes:#61925
 Closes:#64995
 .
   * Back-ported some extra error handling from 1.90c.
Files: 
 24ad0970cdf8aea7b19903887cb46e7b 39994 utils optional bonnie++_1.00g_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUQYUACgkQcS3JWD3FdveceACdGiEuZnfKgo7S973QWchddlVB
YqMAnRD55I5LBdouTkTx7UwP9wQwQjTE
=0htn
-END PGP SIGNATURE-




Uploaded dante 1.1.6-1 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 23 Dec 2000 19:39:38 +
Source: dante
Binary: libsocksd dante-client dante-server libsocksd-dev
Architecture: m68k
Version: 1.1.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Adrian Bridgett [EMAIL PROTECTED]
Description: 
 dante-client - Provides a SOCKS wrapper for users behind a firewall.
 dante-server - SOCKS server.
 libsocksd  - SOCKS library for dante-client.
 libsocksd-dev - Development files for compiling programs with SOCKS support.
Changes: 
 dante (1.1.6-1) unstable; urgency=low
 .
   * new upstream
Files: 
 454403c78ed40035198ac36f029065e0 74224 libs optional libsocksd_1.1.6-1_m68k.deb
 636f1f9a6f8b12e0d83a0fa1efbecc0e 72498 devel optional 
libsocksd-dev_1.1.6-1_m68k.deb
 02f70d05a6a95a09c92c35f5fa402ae9 87146 net optional 
dante-client_1.1.6-1_m68k.deb
 ea6b5027c3c0dc6696e9f5f5c96d1be4 86686 net optional 
dante-server_1.1.6-1_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUTmEACgkQcS3JWD3FdvcTowCePWf33w3+J+Y1mT6XxRa3q0/3
+rAAn1ky6NvTOAGQEe/rjyjZ5RX+WMV4
=IZyk
-END PGP SIGNATURE-




Uploaded epos 2.4.43a-2 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 23 Dec 2000 18:10:18 +0100
Source: epos
Binary: epos
Architecture: m68k
Version: 1:2.4.43a-2
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Milan Zamazal [EMAIL PROTECTED]
Description: 
 epos   - Language independent text-to-speech system.
Changes: 
 epos (1:2.4.43a-2) unstable; urgency=low
 .
   * Alternatives fixed.
   * Conflict with rsynth.
Files: 
 79dd8a3f9cf0a6d6f37a05d9f915fa7c 511372 sound optional epos_2.4.43a-2_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUT2gACgkQcS3JWD3FdvfmaACfVsWHFSnmYcWJ3umEXzDsy3r5
risAnjjTiUbQ7oxdz6lDE21CZSpDFm88
=Wl4G
-END PGP SIGNATURE-




Uploaded sirc 2.211-4 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 22 Dec 2000 19:11:56 -0800
Source: sirc
Binary: sirc
Architecture: m68k
Version: 2.211-4
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Ben Gertzfield [EMAIL PROTECTED]
Description: 
 sirc   - The full-featured Perl IRC client
Closes: 29290 35412 37995 37995
Changes: 
 sirc (2.211-4) unstable; urgency=low
 .
   * Long-overdue rebuild (heh, two years and no new upstream version)
 to bump Standards-Version to 3.2.1, add Source-Depends on
 libncurses5-dev.
   * Include README.socks. Closes: #37995
   * Don't include LICENSE. Closes: #35412, #37995
   * Bugs fixed long ago: Closes: #29290
Files: 
 85e87554dcf17494a1737a20e2107507 84838 net optional sirc_2.211-4_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUTpgACgkQcS3JWD3Fdve3IQCeOH0VTCfVKyYLOc+DpP3d1/EX
NhkAnj4xGPBq4Jpqrc80DH0NfXfEV9E3
=cLKR
-END PGP SIGNATURE-




Uploaded rrdtool 1.0.27-6 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 19 Dec 2000 21:23:55 -0500
Source: rrdtool
Binary: librrdp-perl librrd0-dev librrds-perl rrdtool rrdtool-tcl librrd0
Architecture: m68k
Version: 1.0.27-6
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Matt Zimmerman [EMAIL PROTECTED]
Description: 
 librrd0- Time-series data storage and display system (runtime)
 librrd0-dev - Time-series data storage and display system (development)
 librrds-perl - Time-series data storage and display system (perl-shared)
 rrdtool- Time-series data storage and display system (programs)
 rrdtool-tcl - Time-series data storage and display system (tcl)
Changes: 
 rrdtool (1.0.27-6) unstable; urgency=low
 .
   * debian/rules: Handle DEB_BUILD_OPTIONS debug, nostrip
   * debian/rules: Separate out configure target
   * debian/rules: Miscellaneous cleanup
   * Recompile librrds-perl against perl-5.6
Files: 
 d0e54591f86adfc810f98bccbf471e2a 330354 utils extra rrdtool_1.0.27-6_m68k.deb
 a1e075d23e5cc84dddacf3877e898082 54852 libs extra librrd0_1.0.27-6_m68k.deb
 58a5b0a02e158d66797d4f899d65f328 57398 devel extra 
librrd0-dev_1.0.27-6_m68k.deb
 f321e61c903d07685b0e069b11359815 21470 devel extra 
librrds-perl_1.0.27-6_m68k.deb
 4549a52bb71ef23403c2be75f50c9332 15408 utils extra 
rrdtool-tcl_1.0.27-6_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUUAIACgkQcS3JWD3FdvdGzwCggivI07ZVWkVHJ5WPsI7UNuIR
YeIAnRSG2ulgJ5JAC7cEAtI8En4JCx0y
=kU2q
-END PGP SIGNATURE-




Uploaded libmcal 0.6-7 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 21 Dec 2000 12:48:30 +0100
Source: libmcal
Binary: libmcal0-dev libmcal libmcal0
Architecture: m68k
Version: 0.6-7
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Ola Lundqvist [EMAIL PROTECTED]
Description: 
 libmcal0   - Shared mcal libraries.
 libmcal0-dev - Development library for mcal support.
Changes: 
 libmcal (0.6-7) unstable; urgency=low
 .
   * Fixing maintainer field.
   * Fixing permissions for /var/lib/mstore
   * Creating a empty (touch) /etc/mpasswd file at installation.
Files: 
 7eff554a2fc867338de3ecf3925fabb2 26536 devel optional libmcal0_0.6-7_m68k.deb
 75e6c8250fedbc8ecdb4e281e84f328e 32544 devel optional 
libmcal0-dev_0.6-7_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUStgACgkQcS3JWD3FdvcqaQCeO8dRwzigmS16SipC4DkgM5ml
8vMAn0zS832GUBR8R4TdbQUDaz9gaj7u
=aqZm
-END PGP SIGNATURE-




Uploaded shadow 20000902-2 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 14:33:47 -0500
Source: shadow
Binary: passwd login
Architecture: m68k
Version: 2902-2
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Ben Collins [EMAIL PROTECTED]
Description: 
 login  - System login tools
 passwd - Change and administer password and group data.
Closes: 17911 63801 64756 71114 75435 75510 76806 76817 76898 77824 77940 78186 
79447 80111 80398 80494
Changes: 
 shadow (2902-2) unstable frozen; urgency=low
 .
   * control.hurd-control.gnu: closes: #77940
   * Cannot reproduce, closes: #79447
   * User never sent a patch, plus I think removing the passwd/account when
 doing passwd -l is a bad idea. Makes it so you cannot unlock the
 account. closes: #77824
   * Don't allow shadowconfig to change perms of other binaries, close: #77057
   * IMO, this is not a bug. It's part of a feature, and can be disabled by
 turning off USER_GROUPS. closes: #76806
   * /bin/login is suid root for several good reasons. For one, it allows
 daemons that use it to run as non-root. This is a good thing since it
 means only one program is running as root, and not several. closes: #17911
   * sulog is fairly easy to grep or parse so I don't see how the
 similarity of the log entries for failed and successful is a problem.
 '-' for failed, '+' for success. closes: #63801
   * logoutd.8: s,/etc/utmp,/var/run/utmp, closes: #80494
   * Fix case where pam_auth returns a NULL username, closes: #76817, #75510
   * Hmm, Linux is a sysv derivative, so the comment is perfectly
 legitimate, closes: #76898
   * MAX_PASSWORD is used by useradd, and CHFN_AUTH is actually used by
   * chfn to decide if the current user needs to auth in order to change
 their info, closes: #71114
   * login.1: Fix \' closes: #75435
   * login -f works for me assuming you call it as root. I tested this with
 plain pam_unix.so, and also with pam_unix.so stacked with pam_ldap.so.
 So if it doesn't work with telnet-heimdal, then that program is not
 doing something right. closes: #78186
   * login.pam.d: made pam_nologin.so requisite. closes: #80111
   * su to root seems pretty quick to me, closes: #64756
   * xmalloc.c: remove decleration of malloc, which was causing system
   * header conflicts. closes: #80398
Files: 
 95ebab7454b64d8f80098f0e18b58e3f 254096 base required 
passwd_2902-2_m68k.deb
 fe3a439ebfb35e3d8a3c15196b740d19 108190 base required login_2902-2_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUQKgACgkQcS3JWD3FdvcW5ACfZ18naFpYEPWilBnAqN3Bx6me
rcwAnRIYH+HMLZMFH8jSZC0hsIYm8n/i
=M1ho
-END PGP SIGNATURE-




Uploaded ezbounce 0.99.10-1 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri,  8 Dec 2000 16:45:47 +0100
Source: ezbounce
Binary: ezbounce
Architecture: m68k
Version: 0.99.10-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Karl Soderstrom [EMAIL PROTECTED]
Description: 
 ezbounce   - A highly configurable IRC proxy
Closes: 79099
Changes: 
 ezbounce (0.99.10-1) unstable; urgency=low
 .
   * Initial Release (Closes: #79099).
Files: 
 b6d0f2aa972dce56162af014d469c0c9 68420 net optional ezbounce_0.99.10-1_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUSlQACgkQcS3JWD3FdveJegCff/irviIL1Co4wKGAQwhFYQEA
5ccAn0qEFF87Ux8v9FP+njZpeq4eVAXM
=+22a
-END PGP SIGNATURE-




Uploaded bplay 0.991-2 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 20 Dec 2000 22:51:16 +0100
Source: bplay
Binary: bplay
Architecture: m68k
Version: 0.991-2
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Peter Makholm [EMAIL PROTECTED]
Description: 
 bplay  - Buffered audio file player/recorder
Closes: 80007
Changes: 
 bplay (0.991-2) unstable; urgency=low
 .
   * Added build-depends (Closes #70298)
   * Added patch from #80007 to enable -j/-J options. (Closes: #80007)
 patch by [EMAIL PROTECTED]
Files: 
 4971671ba9293c26a495571ba862b3ae 15098 sound extra bplay_0.991-2_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUT2IACgkQcS3JWD3FdvdY/QCdGF2r4ltWzn2w42AsnJrAnpsx
5RMAnRTX8ZQ3J1ZgthjcHVrvaOhB25vu
=Ir2G
-END PGP SIGNATURE-




Uploaded gdm 2.0-0.beta4.15 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 24 Dec 2000 21:43:55 -0800
Source: gdm
Binary: gdm
Architecture: m68k
Version: 2.0-0.beta4.15
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Ryan Murray [EMAIL PROTECTED]
Description: 
 gdm- GNOME Display Manager
Closes: 55712 75091 75094 76148 77163 80408
Changes: 
 gdm (2.0-0.beta4.15) unstable; urgency=low
 .
   * Added xutils dependancy (closes: #76148)
   * Added patch to remove locale menu, allowing dependancy on locales to
 be lowered to suggests (closes: #80408)
   * Apparently X has some issues with all the clients being killed in a row,
 and doesn't decide to exit.  XDM kills the server instead of the nice
 method, so now we do that, too. (closes: #77163)
   * Remove non-sensical code that broke %d (closes: #75094)
   * Add documentation on the face browser (closes: #75091)
   * It seems updating the cookies already happens, so now the hostname is
 reread each time the cookies regenerate (closes: #55712)
   * Remove inappropriate Xsession session.
   * Fix a syslog() format.
Files: 
 4220d91f0ff074dfa6296fb8bf5560c4 401508 x11 optional 
gdm_2.0-0.beta4.15_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUUxEACgkQcS3JWD3FdvfcXACfdrvXo410srH4UWPCI5owstub
P+QAn0cCoXqIOxI5xh4KWp7q758J5Exp
=C00+
-END PGP SIGNATURE-




Uploaded gtkfontsel 1.1-5 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 17:07:40 +
Source: gtkfontsel
Binary: gtkfontsel
Architecture: m68k
Version: 1.1-5
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Dima Barsky [EMAIL PROTECTED]
Description: 
 gtkfontsel - A gtk+ based font selection utility
Closes: 65393
Changes: 
 gtkfontsel (1.1-5) unstable; urgency=low
 .
   * Some changes in the rules and control files to make the package
 policy compliant (thanks to Josip Rodin).
   * Added menu entry (Closes: #65393)
Files: 
 3e8dd01f258c17ad489e592941cf91e5 8456 x11 optional gtkfontsel_1.1-5_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUQeAACgkQcS3JWD3FdveKAgCfbuImLGLkXRoDF4+YTr7Gx8xw
usoAnjjZzDQULT92aRRXg9WUjYwZmmWd
=wS2v
-END PGP SIGNATURE-




Uploaded gtk+ 1.0.6-5 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 23 Dec 2000 16:32:34 -0800
Source: gtk+
Binary: libgtk-doc libgtk-dbg libgtk1 libgtk-dev
Architecture: m68k
Version: 1:1.0.6-5
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Ben Gertzfield [EMAIL PROTECTED]
Description: 
 libgtk-dbg - Debugging static libraries for the GIMP Toolkit
 libgtk-dev - Header files and static libraries for the GIMP Toolkit
 libgtk1- The GIMP Toolkit set of widgets for X
Changes: 
 gtk+ (1:1.0.6-5) unstable; urgency=low
 .
   * Update Standards-Version to 3.2.1.
   * Add Build-Depends in control file.
   * Fix bashisms in debian/rules.
   * /usr/doc - /usr/share/doc everywhere, /usr/man - /usr/share/man
   * (Whoa.) Change Section: of libgtk-doc from 'docs' to 'doc'. Oops.
Files: 
 bce7539f873f32305cd6db9570bc3aeb 486900 devel optional 
libgtk-dev_1.0.6-5_m68k.deb
 715230391925fc61d14edc811cc427c7 359034 libs optional libgtk1_1.0.6-5_m68k.deb
 2b2507c399eaa5404fa1067cd1d37b31 2658644 devel optional 
libgtk-dbg_1.0.6-5_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUTLIACgkQcS3JWD3FdvfyNQCfWZuniQ6FsRx/rSbp/RBHtFiV
QMYAnju3xaPctz0NQXtOQtR3rsB4ip13
=rDs5
-END PGP SIGNATURE-




Uploaded snort 1.6.3a-3 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon,  1 Jan 2001 19:32:23 +0100
Source: snort
Binary: snort
Architecture: m68k
Version: 1.6.3a-3
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Christian Hammers [EMAIL PROTECTED]
Description: 
 snort  - flexible packet sniffer/logger that detects attacks
Closes: 80996
Changes: 
 snort (1.6.3a-3) unstable; urgency=low
 .
   * Changed the interface debconf question to medium. Closes: #80996
Files: 
 686d0925fbda567ea04effe1a32458de 247724 net optional snort_1.6.3a-3_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpURa4ACgkQcS3JWD3FdvfqfQCcDXnv0vvqzj3rxl9Wm+KeTCRz
ikEAnAjSmj5r1qOeE6kjJVU5VkYUXNkx
=PaR6
-END PGP SIGNATURE-




Uploaded gtypist 2.3.2-1 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon,  4 Dec 2000 10:04:44 -0400
Source: gtypist
Binary: gtypist
Architecture: m68k
Version: 2.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Ben Armstrong [EMAIL PROTECTED]
Description: 
 gtypist- A simple ncurses typing tutor
Changes: 
 gtypist (2.3.2-1) unstable; urgency=low
 .
   * New upstream release
   * Package renamed from typist to gtypist (GNU typist)
Files: 
 20790c326ad68d625444b5f59099e0d3 279908 misc optional gtypist_2.3.2-1_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUjbsACgkQcS3JWD3Fdve8gwCdFgrJD5MVhHDiIt9Djv3d8nJ/
50oAnjcmaBb6PDhUXi8yGMguKT0i+FK2
=twOt
-END PGP SIGNATURE-




Uploaded lxr 0.3-1 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu,  2 Nov 2000 16:07:19 +0100
Source: lxr
Binary: lxr
Architecture: m68k
Version: 0.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Giacomo Catenazzi [EMAIL PROTECTED]
Description: 
 lxr- Linux Cross-Reference
Changes: 
 lxr (0.3-1) unstable; urgency=low
 .
   * Initial Release.
Files: 
 5db59c280a79b1820c174ccb1258bff1 27138 misc extra lxr_0.3-1_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUja0ACgkQcS3JWD3FdvdYzwCfeMms+4haCbXJkHuycgnsYcrF
evIAn3yJKv3ANe5fyx4oEnD8w5V+y2Z+
=JXeD
-END PGP SIGNATURE-




Uploaded ircii-pana 1.0-0c17-4 (m68k) to erlangen

2001-01-04 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun,  5 Nov 2000 14:58:05 -0500
Source: ircii-pana
Binary: bitchx bitchx-gtk
Architecture: m68k
Version: 1:1.0-0c17-4
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Daniel Jacobowitz [EMAIL PROTECTED]
Description: 
 bitchx - Advanced Internet Relay Chat client
 bitchx-gtk - GTK interface for BitchX
Changes: 
 ircii-pana (1:1.0-0c17-4) unstable; urgency=low
 .
   * Update from CVS partially to fix the strobing input color bug and some
 problems with transparent xterms; upstream figured this one out.
 Thanks, nuke.
   * Remove i386-only findcomm binary from the package.
   * Update build-deps to libmysqlclient10-dev and rebuild.
Files: 
 34020ae15eac5d6742bf6b6ea349c5c8 1280500 net optional 
bitchx_1.0-0c17-4_m68k.deb
 e3be1b3a8290d2a8b6b7d9ea21254811 447100 net optional 
bitchx-gtk_1.0-0c17-4_m68k.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard 
http://www.gnupg.org/

iEYEARECAAYFAjpUjcMACgkQcS3JWD3FdvcnoQCfX6vVJIHEQ1n5TIVSHeWWULW9
fKAAnRgrngN8RVwgFez8DNrTiNxIGmwU
=aCBu
-END PGP SIGNATURE-




Uploaded groff 1.16-3.1 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 28 Dec 2000 20:51:34 -0800
Source: groff
Binary: groff
Architecture: sparc
Version: 1.16-3.1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Robert Woodcock [EMAIL PROTECTED]
Description: 
 groff  - GNU troff text-formatting system.
Closes: 76813 77024 77515 77608 77684 78054 78905 79472 80559
Changes: 
 groff (1.16-3.1) unstable; urgency=low
 .
   * Rebuilt on a system with Xfree 4 and toasted contents of /usr/X11R6/lib,
 closes: #76813, #77024, #77515, #77608, #77684, #78054, #78905, #79472,
 #80559
Files: 
 66b97a70f10916ae3515bb128ffaca5d 1826876 text important 
groff_1.16-3.1_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VKhffNc/ZB4E7C0RAm50AKCNBfLMv8fWYLIfkGBArf8hfb24mACfTyrF
1L/+OC/0P1kkbz17qpbwQ7g=
=oSLl
-END PGP SIGNATURE-




Uploaded fileutils 4.0.35-1 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 28 Dec 2000 22:46:27 -0500
Source: fileutils
Binary: fileutils
Architecture: sparc
Version: 4.0.35-1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Michael Stone [EMAIL PROTECTED]
Description: 
 fileutils  - GNU file management utilities.
Closes: 67246 79338 80084 80266 80642
Changes: 
 fileutils (4.0.35-1) unstable; urgency=low
 .
   * New upstream version (Closes: #80642, #79338, #67246)
   * Documentation changes (Closes: #80084, #80266)
Files: 
 3148c55856673dd3cf0f9d76b5a988c1 687140 base required 
fileutils_4.0.35-1_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VKYXfNc/ZB4E7C0RAt4YAKCMgRmLMIy8b+9ZjqWAelX7oFacMACgm3eq
0XjDsUBXsV3rrnoNKiDYg5M=
=990z
-END PGP SIGNATURE-




Uploaded less 358-5 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon,  1 Jan 2001 12:52:04 +0100
Source: less
Binary: less
Architecture: sparc
Version: 358-5
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Thomas Schoepf [EMAIL PROTECTED]
Description: 
 less   - A file pager program, similar to more(1)
Closes: 80989
Changes: 
 less (358-5) unstable; urgency=low
 .
   * Closes: Bug#80989: less: less on a deb file that does not exist
Files: 
 bcb4eac9e14fe4a458344572b1b7a383 93462 text standard less_358-5_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VLeffNc/ZB4E7C0RAvdwAKC/4xhbWHP8Z6ZHQ3zpRykcRt2NQwCghMp2
wQkXLx5QVp/G6Kt+fxUikng=
=8G13
-END PGP SIGNATURE-




Uploaded perl-5.6 5.6.0-6.2 (sparc all) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 29 Dec 2000 16:36:26 +1100
Source: perl-5.6
Binary: perl-5.6-doc perl-5.6-suid perl-5.6-debug perl-5.6 libperl5.6 
perl-5.6-thread perl-5.6-base
Architecture: sparc all
Version: 5.6.0-6.2
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Brendan O'Dea [EMAIL PROTECTED]
Description: 
 libperl5.6 - Shared Perl library
 perl-5.6   - Larry Wall's Practical Extracting and Report Language.
 perl-5.6-base - The Pathologically Eclectic Rubbish Lister
 perl-5.6-debug - View internals of Perl and debug Perl itself.
 perl-5.6-doc - Man pages and pod docs for Perl
 perl-5.6-suid - Runs setuid Perl scripts.
 perl-5.6-thread - Experimental Perl binary with threading enabled
Closes: 80794
Changes: 
 perl-5.6 (5.6.0-6.2) unstable; urgency=low
 .
   * NMU
   * Moving the libperl.so symlink to libperl5.6 requires conflicts and
 replaces.  (Closes: #80794).
Files: 
 506a8e6fec0123704cd3c437bcaa904e 2901308 interpreters important 
perl-5.6_5.6.0-6.2_sparc.deb
 8c6d37ca09bb122e8801913d4e198471 641466 base required 
perl-5.6-base_5.6.0-6.2_sparc.deb
 0d84f775c451585487fde3877fcaae0d 391032 libs optional 
libperl5.6_5.6.0-6.2_sparc.deb
 601f0f144b9405ee93300a0fb98e3360 373782 interpreters optional 
perl-5.6-suid_5.6.0-6.2_sparc.deb
 22068a8219418cabfe4c878f9be4acfc 2159480 interpreters extra 
perl-5.6-debug_5.6.0-6.2_sparc.deb
 ccd6a991e2a6c139beb619ee9ffe8cc7 2075316 interpreters extra 
perl-5.6-thread_5.6.0-6.2_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VLeXfNc/ZB4E7C0RAqPQAKDJNuA4qQCa3E6zqKNNfUxc/jknegCaA95B
NHrvpRipoR6b81v9Spkw+8s=
=EjL6
-END PGP SIGNATURE-




Uploaded gdbm 1.7.3-27 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 30 Dec 2000 01:07:10 +
Source: gdbm
Binary: libgdbmg1-dev libgdbmg1
Architecture: sparc
Version: 1.7.3-27
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: James Troup [EMAIL PROTECTED]
Description: 
 libgdbmg1  - GNU dbm database routines (runtime version). [libc6 version]
 libgdbmg1-dev - GNU dbm database routines (development files) [libc6 version]
Closes: 33792 41170 41718 41820 43255 54401 80750
Changes: 
 gdbm (1.7.3-27) unstable; urgency=low
 .
   * No 1.8 yet because a) the soname has changed, making packaging it less
 trivial, b) the upstream changes are not hugely important and c) 1.8
 appears after 5 years of upstream inactivity and has since been
 followed by another 18 months of upstream inactivity despite some
 trivial and annoying build bugs in 1.8 which must hit almost everyone
 who tries to build it from source.
 .
   * Migration warnings are left unchanged as a result of (c) above.
 .
   * Drop support for libc5.  rules and control files updated and
 libc[56]-? suffix removed from maintainer script names. Closes:
 bug#54401.
   * debian/copyright: update location of system copy of GPL.  Remove
 references to Linux.
   * debian/postinst: create /usr/doc/libgdbmg1 symlink.
   * debian/postinst.dev: likewise.
   * debian/prerm: remove /usr/doc/libgdbmg1 symlink.
   * debian/prerm.dev: likewise.
   * debian/rules (binary-arch): install documentation into
 /usr/share/{doc,man,info} (Closes: bug#80750).
   * debian/control (Standards-Version): update to 3.2.1.
 .
   * gdbm.texinfo: fix two references to /usr/local/. (Closes: bug#43255)
 .
   * Maintainer release.  Acknowledge two NMUs.  (Closes: bug#41820,
 #41718, #33792)
 .
   * debian/control: fix path to MIGRATE file in libgdbmg1-dev's extended
 description. (Closes: bug#41170)
Files: 
 a669c26244c7a924fd27a6cb858fd5b2 18978 base standard 
libgdbmg1_1.7.3-27_sparc.deb
 fc5bd37ef46e6a0f88b58396587da24a 44420 devel optional 
libgdbmg1-dev_1.7.3-27_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VKRWfNc/ZB4E7C0RAgz3AJ9yOSdkXtThf3NBr4rFsqYT7L8xnwCghHnT
3sykD6G8DsNsJ8HXClpf0ko=
=i0Ez
-END PGP SIGNATURE-




Uploaded netkit-base 0.10-5 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 13:47:13 +1000
Source: netkit-base
Binary: netkit-ping netkit-rpc netkit-inetd
Architecture: sparc
Version: 0.10-5
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Anthony Towns [EMAIL PROTECTED]
Description: 
 netkit-inetd - The Internet Superserver
 netkit-ping - The ping utility from netkit
 netkit-rpc - The rpcgen and rpcinfo utilities
Closes: 69397
Changes: 
 netkit-base (0.10-5) unstable; urgency=low
 .
   * Remove the --exec arguments from inetd's init.d script, so that it can
 be stopped/restarted in the postinst, after the running binary has
 been updated. Kill any additional leftover inetd processes left
 from previous, buggy, netbases in case the admin hasn't already done
 so. (Closes: Bug#69397)
 .
   * Mark cron.daily/netkit-inetd as a conffile.
Files: 
 4b12a19a62519205491da8f2e6d38405 26014 net standard 
netkit-inetd_0.10-5_sparc.deb
 a556b8843583bde3e7f137c57e3c4c49 46056 net standard netkit-rpc_0.10-5_sparc.deb
 dc64725b7163654806d0652bdb6b0897 20554 net standard 
netkit-ping_0.10-5_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VLecfNc/ZB4E7C0RAgsLAKCaU2sz1D43gPxt9rEeAW8X591rCwCbBg5v
nqEAd8dCCnvPDgrLYrsCOOw=
=w0s6
-END PGP SIGNATURE-




Uploaded procmail 3.15-3 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 17:20:47 +0100
Source: procmail
Binary: procmail
Architecture: sparc
Version: 3.15-3
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Santiago Vila [EMAIL PROTECTED]
Description: 
 procmail   - Versatile e-mail processor.
Closes: 80437
Changes: 
 procmail (3.15-3) unstable; urgency=low
 .
   * Fixed formatting error in procmailrc(5). Patch by the author.
 (Closes: #80437).
Files: 
 70780155128704eee0cb8c5c749a50c6 132840 mail standard procmail_3.15-3_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VLedfNc/ZB4E7C0RAsudAJ0akJBu/SYbD7MFcv1/jEhFwVWqvQCgtWaU
uUoZ/3ToGh9QLTQq+HAPEzs=
=xpO7
-END PGP SIGNATURE-




Uploaded libpam-opie 0.21-4 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue,  2 Jan 2001 07:12:36 -0500
Source: libpam-opie
Binary: libpam-opie
Architecture: sparc
Version: 0.21-4
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Michael Stone [EMAIL PROTECTED]
Description: 
 libpam-opie - Use OTP's for PAM authentication
Changes: 
 libpam-opie (0.21-4) unstable; urgency=low
 .
   * link with -lpam. benc insists it's needed. I don't care one way or
 the other, and doing so Closes: 80898
Files: 
 7e6f9846911e99ecf8a16f1ca996dc2c 20584 libs optional 
libpam-opie_0.21-4_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VNaRfNc/ZB4E7C0RAsV+AJ4v1GWGc9XcC6oej7emNTWi7CSfyACgxMwO
1QKzwpNiWirtrM//dA0YKfE=
=FC6o
-END PGP SIGNATURE-




Uploaded kdelibs 2.1-20010101-1 (all sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 01 Jan 2001 03:30:00 -0700
Source: kdelibs
Binary: libarts-dev kdelibs3 kdelibs3-dev kdelibs3-doc libarts
Architecture: all sparc
Version: 4:2.1-20010101-1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Ivan E. Moore II [EMAIL PROTECTED]
Description: 
 kdelibs3   - KDE core libraries (runtime files)
 kdelibs3-dev - KDE core libraries (development files)
 kdelibs3-doc - KDE core library documentation
 libarts- aRts Sound system
 libarts-dev - aRts Sound system (development files)
Closes: 81003
Changes: 
 kdelibs (4:2.1-20010101-1) unstable; urgency=low
 .
* more upstream bug fixes
* Applying new i18n patch
* Adding in conflicts for old task- packages (Closes: #81003)
Files: 
 d61b90eab14431fca46c0cda073abcd8 4946378 libs optional 
kdelibs3_2.1-20010101-1_sparc.deb
 f4e4c806a2671b6c3c5c421ff0cddaea 561682 libs optional 
libarts_2.1-20010101-1_sparc.deb
 d0de034e9882810515f9961b5ae51bbf 69716 devel optional 
libarts-dev_2.1-20010101-1_sparc.deb
 cdb80ea2e9620c09cb0aca5cb4f7ec2f 580972 devel optional 
kdelibs3-dev_2.1-20010101-1_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VNaOfNc/ZB4E7C0RAikhAJ4/3MeMwRgCvBQqidBVuTDCQQhCtgCgh2RN
QZ6J66ZsRpsjOVZr0Xq/Jus=
=cuBl
-END PGP SIGNATURE-




Uploaded libmime-base64-perl 2.11-3 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 29 Dec 2000 05:52:49 -0400
Source: libmime-base64-perl
Binary: libmime-base64-perl
Architecture: sparc
Version: 2.11-3
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Michael Alan Dorman [EMAIL PROTECTED]
Description: 
 libmime-base64-perl - MIME/Base64 decoding for Perl
Closes: 76848 80678 80760
Changes: 
 libmime-base64-perl (2.11-3) unstable; urgency=low
 .
   * Fix man page location (closes: bug#80760)
   * Fix perl dependency (closes: bug#80678, bug#76848)
Files: 
 0786defba7717e906fa54d6f3bf6168b 17754 libs optional 
libmime-base64-perl_2.11-3_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VNaQfNc/ZB4E7C0RAlLFAKC6Go42G+Eu6ZakXOFcaNVPIFl/6wCaAmke
Wp82rmm/CbdUL4ZU7Mg7fpk=
=qeKg
-END PGP SIGNATURE-




Uploaded hanterm 3.3.1p18-2 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue,  2 Jan 2001 10:46:27 +0900
Source: hanterm
Binary: hanterm
Architecture: sparc
Version: 1:3.3.1p18-2
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Chu-yeon Park [EMAIL PROTECTED]
Description: 
 hanterm- X terminal terminal emulator with Hangul support
Closes: 80502
Changes: 
 hanterm (1:3.3.1p18-2) unstable; urgency=low
 .
   * New standards 3.1.2.0
   * Changed the location of Hanterm resource file from
 /usr/X11R6/lib/X11/app-defaults/Hanterm to /etc/X11/app-defaults/Hanterm.
 (Closes: #80502)
   * Removed dependencies on xfonts-cjk, which is unavailable at all.
Files: 
 aae6eff559bb27201ebf2462a7f5217c 115524 x11 optional 
hanterm_3.3.1p18-2_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VUH7fNc/ZB4E7C0RAg6VAKC38D6CLgUhqxRpRBzYE6mYYvvmGACfXKgq
FaNu97BQ2q8f0cilhtCTkSw=
=b4N9
-END PGP SIGNATURE-




Uploaded zip 2.30-2 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon,  1 Jan 2001 18:09:38 +0100
Source: zip
Binary: zip
Architecture: sparc
Version: 2.30-2
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Santiago Vila [EMAIL PROTECTED]
Description: 
 zip- Archiver for .zip files
Changes: 
 zip (2.30-2) unstable; urgency=low
 .
   * Updated upstream URL in copyright file.
Files: 
 ac2b1a6ab32c61232a0a875bf03191a5 91262 utils optional zip_2.30-2_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VUH4fNc/ZB4E7C0RAmiSAKCAEmigOVNxAPeCxUEotmj7j50hZgCdGNnq
45kAHPAUJJcPAnHTIJlIqHM=
=LBCq
-END PGP SIGNATURE-




Uploaded unison 2.6.1-2 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 28 Dec 2000 18:23:55 +
Source: unison
Binary: unison
Architecture: sparc
Version: 2.6.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Robert McQueen [EMAIL PROTECTED]
Description: 
 unison - A file-synchronization tool for Unix and Windows.
Changes: 
 unison (2.6.1-2) unstable; urgency=low
 .
   * Fixed to take account of no native (ocamlopt) compiler on
 some archs.
   * Minor debian/rules cleanups.
Files: 
 0c78aad9d8899f5c9d75357da87a9cde 394452 utils optional unison_2.6.1-2_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VUH3fNc/ZB4E7C0RArNrAJ9U2hPAWUD5YIvPWWmMNNZuaPOBqwCeLPtB
jBIRLJPzRfsx4JITrO38280=
=BqYL
-END PGP SIGNATURE-




Uploaded kdeutils 2.1-20010101-1 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 01 Jan 2001 17:11:00 -0700
Source: kdeutils
Binary: kab karm klpq kdepasswd klaptopdaemon kedit khexedit kfloppy kcalc kpm 
knotes ark kjots kfind kljettool kcharselect ktimemon
Architecture: sparc
Version: 4:2.1-20010101-1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Ivan E. Moore II [EMAIL PROTECTED]
Description: 
 ark- An archiver for KDE
 kab- An addressbook for KDE
 karm   - A time tracker for KDE
 kcalc  - A calculator for KDE
 kcharselect - A Character set selector for KDE
 kdepasswd  - A Password changer frontend for KDE
 kedit  - A simple text editor for KDE
 kfind  - A KDE based file finder
 kfloppy- A floppy disk formater frontend
 khexedit   - A hex editor for KDE
 kjots  - A small note taker program for KDE
 klaptopdaemon - battery monitoring and management for laptops
 kljettool  - Laser Jet tools for KDE
 klpq   - KDE port of a program called xlpq
 knotes - Sticky notes for KDE
 kpm- Process manager for KDE
 ktimemon   - small but nifty system monitor
Changes: 
 kdeutils (4:2.1-20010101-1) unstable; urgency=low
 .
   * More upstream fixes
Files: 
 86c73306d90a652d61e378f515c614b9 147740 utils optional 
ark_2.1-20010101-1_sparc.deb
 9e800aefc3ab80cb24433675981af90d 173940 utils optional 
kab_2.1-20010101-1_sparc.deb
 be1f3098be887e14c4ba0a36b2616595 79462 utils optional 
karm_2.1-20010101-1_sparc.deb
 afe22642d2a7e488031850d5bf3bb89e 86262 utils optional 
kcalc_2.1-20010101-1_sparc.deb
 ccc8ad8aedaacc80826ef09a3c7dbff0 19484 utils optional 
kcharselect_2.1-20010101-1_sparc.deb
 c7ee72d024522d7d6ce0347fb0e9789d 19200 utils optional 
kdepasswd_2.1-20010101-1_sparc.deb
 8bffb92bb8c0556c4bec1f0f0726b80d 96094 editors optional 
kedit_2.1-20010101-1_sparc.deb
 3eb5a6f5c8ce2cd0adf5d2b23fcbd153 72874 utils optional 
kfind_2.1-20010101-1_sparc.deb
 fb00bf1830fb87cf2058f73a119a187a 43110 utils optional 
kfloppy_2.1-20010101-1_sparc.deb
 b5c5c038bdb018b8ad8a6bc3756afec6 252502 utils optional 
khexedit_2.1-20010101-1_sparc.deb
 1a3a6689fcfa4c283f3b8d5310e8cfae 69992 utils optional 
kjots_2.1-20010101-1_sparc.deb
 4f897b0abc7f36230f0527d6c271860f 70100 utils optional 
klaptopdaemon_2.1-20010101-1_sparc.deb
 09685c8f1a9d731857c750d67996fdf5 86718 utils optional 
kljettool_2.1-20010101-1_sparc.deb
 5c376efb1d35a4c7b27675d7f6013130 62450 utils optional 
klpq_2.1-20010101-1_sparc.deb
 06074b3393cfaa03d0a4e79c2498c939 70366 utils optional 
knotes_2.1-20010101-1_sparc.deb
 e822a60a59af9a15f1bb0f83cae8de17 199134 utils optional 
kpm_2.1-20010101-1_sparc.deb
 5e1e273118b0885f6fd9fa1a147b644d 51020 utils optional 
ktimemon_2.1-20010101-1_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VUH1fNc/ZB4E7C0RAjuCAKCM/3ZyrKA2FxKrK9ofhfjeRBP2kwCbBjZ7
wnWuu+ZbF6Lc80Y1/eTVAMo=
=0tPp
-END PGP SIGNATURE-




Uploaded gtkfontsel 1.1-5 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 17:07:40 +
Source: gtkfontsel
Binary: gtkfontsel
Architecture: sparc
Version: 1.1-5
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Dima Barsky [EMAIL PROTECTED]
Description: 
 gtkfontsel - A gtk+ based font selection utility
Closes: 65393
Changes: 
 gtkfontsel (1.1-5) unstable; urgency=low
 .
   * Some changes in the rules and control files to make the package
 policy compliant (thanks to Josip Rodin).
   * Added menu entry (Closes: #65393)
Files: 
 87bc4b426eca4933cf97e254b4ffde15 11356 x11 optional gtkfontsel_1.1-5_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VUH6fNc/ZB4E7C0RArGGAJ40sV0ME8wwJSPshYyGu2/hhNFUbwCfdsmT
+KjFQ34FvTk5TF/iBdcC3nU=
=++wf
-END PGP SIGNATURE-




Uploaded queue 1.30.1-2 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue,  2 Jan 2001 10:46:02 -0800
Source: queue
Binary: queue
Architecture: sparc
Version: 1.30.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Joey Hess [EMAIL PROTECTED]
Description: 
 queue  - transparent load balancing system
Closes: 81033
Changes: 
 queue (1.30.1-2) unstable; urgency=medium
 .
   * Applied patch from [EMAIL PROTECTED] to fix a crash on any trivial
 command, related to rlimits. Closes: #81033
Files: 
 14a91e9a11f00df02e3f63e330d5e247 121886 admin optional queue_1.30.1-2_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VSvBfNc/ZB4E7C0RAguWAJ9uWIJLnS9uqn6KlvnfHdPnadImSgCdEpTT
qXzCLtQYDFI2B6hQErrxSY8=
=a6sR
-END PGP SIGNATURE-




Uploaded libghttp 1.0.8-3 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu,  4 Jan 2001 00:20:37 +0100
Source: libghttp
Binary: libghttp1 libghttp-dev
Architecture: sparc
Version: 1.0.8-3
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Christian Marillat [EMAIL PROTECTED]
Description: 
 libghttp-dev - Gnome HTTP client library - Development
 libghttp1  - Gnome HTTP client library
Closes: 79216
Changes: 
 libghttp (1.0.8-3) unstable; urgency=low
 .
   * debian/control Replaces: = not  (Closes: #79216)
Files: 
 98ae6816a68df6f065028ac8ca964495 26310 x11 optional libghttp1_1.0.8-3_sparc.deb
 125522710cf76b1cc7c8b9004cd29797 21372 x11 optional 
libghttp-dev_1.0.8-3_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VQuufNc/ZB4E7C0RAu6qAJ4nJ/sK8Wl/YWvDdkNZUYVeZGYu4ACgwGx9
rrXM3ltR1HWQ0nj9ZKMPy8E=
=Jsoq
-END PGP SIGNATURE-




Uploaded psmisc 19-3 (sparc) to ftp-master

2001-01-04 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 31 Dec 2000 17:27:30 +1100
Source: psmisc
Binary: psmisc
Architecture: sparc
Version: 19-3
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Craig Small [EMAIL PROTECTED]
Description: 
 psmisc - Utilities that use the proc filesystem
Closes: 59009 80045
Changes: 
 psmisc (19-3) unstable; urgency=low
 .
   * New standards version
   * Added menu hints Closes: #80045
   * Changed call from xterm to x-terminal emulator Closes: #59009
Files: 
 0f99ccd438be4f7f2923943514eda53f 33740 base optional psmisc_19-3_sparc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins [EMAIL PROTECTED]

iD8DBQE6VSu/fNc/ZB4E7C0RAu5aAJ9WynJhm/S04DUv9Irlrcli/qtzwwCgnsK9
wv8JXjWpsfE23X00akqKdJw=
=ibiA
-END PGP SIGNATURE-




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Ethan Benson
On Thu, Jan 04, 2001 at 12:41:24AM -0500, Adam McKenna wrote:
  as for including other's in the Mail-Followup-To mutt only does this
  if those users had used `lists' instead of `subscribe' indicating they
  WANT to be CCed.  
 
 There must be a bug in it somewhere, then, because I often see people getting
 added to Mail-Followup-To that shouldn't be there.  In fact, I personally 
 have been added to Mail-Followup-To by other Mutt users, and I don't use the 
 lists command at all.

in that case there would be something funny going on, here is my
theory:

you post to list, you M-F-To: is set to only the list

someone (Mr-Broken) with broken mailer uses reply-to-all which CCs you
anyway ignoring M-F-To.

mutt user uses list-reply to Mr-Broken's post, mutt sees you were CCed
and assumes you should be included since there is no M-F-To header.
mutt then sets the M-F-To header to include you for the benifit of
later list-replies.  

if this is the case the solution is fixing broken mailers, many of
them are Free software so why have patches to support M-F-To not been
made?

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpqtpqwUSa94.pgp
Description: PGP signature


Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread John Galt
On Thu, 4 Jan 2001, Craig Sanders wrote:

 On Wed, Jan 03, 2001 at 09:53:04PM -0700, John Galt wrote:
In fact, the only thing the RFC says to do is to honor Reply-To: 
headers,
which I might note you didn't include in your message.
   
   Why should I, when it would be no different from my From: header?
  
  It would be in your case: 
  
  Reply-to: debian-devel@lists.debian.org
 
 no, that would make it difficult for people to reply privately to him.
 
 Mail-Followup-To is the correct header to use.

Mail-Followup-To isn't even a registered header!  The closest thing to a
registry that RFC822 implies is in the hands of SRI International is

http://www.dsv.su.se/jpalme/ietf/mail-headers/

(jpalme is as much of a member as one can be of the IETF RFC822 WG)

which says that a Followup-To: header is from RFC 1036, but RFC 1036 is
for USENET messages, not email.  The only thing I can think of is that
somebody liked the usenet idea of the followup-to: and just appended a
mail on it.  Just because somebody breaks the standards does NOT mean that
everybody should.  

  The difference between pine and mutt is that you KNOW the overflows in
  pine
 
 incorrect, again. the difference between mutt and pine is that mutt is
 a decent piece of free software that works and follows the relevant
 standards, while pine is a broken piece of non-free shit which doesn't.

Horsefeathers!  The Mail-followup-to: header is NOT a part of the relevant
standards!  

  mutt allegedly shares code with pine...
 
 since the source-code of both programs is readily available it should be
 easy enough to check this allegation.
 
 
 craig
 
 --
 craig sanders
 
 
 

-- 
Pardon me, but you have obviously mistaken me for someone who gives a
damn.
email [EMAIL PROTECTED]




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Adam McKenna
On Wed, Jan 03, 2001 at 09:07:27PM -0900, Ethan Benson wrote:
  have been added to Mail-Followup-To by other Mutt users, and I don't use 
  the 
  lists command at all.
 
 in that case there would be something funny going on, here is my
 theory:
 
 you post to list, you M-F-To: is set to only the list
 
 someone (Mr-Broken) with broken mailer uses reply-to-all which CCs you
 anyway ignoring M-F-To.
 
 mutt user uses list-reply to Mr-Broken's post, mutt sees you were CCed
 and assumes you should be included since there is no M-F-To header.
 mutt then sets the M-F-To header to include you for the benifit of
 later list-replies.  

Sounds like a reasonable scenario.

 if this is the case the solution is fixing broken mailers, many of
 them are Free software so why have patches to support M-F-To not been
 made?

I'd like to see someone convince that M-F-To fix Pine.  But I doubt you'll
have an easy time getting Crispin to apply a patch.  He won't even implement 
maildir, for christ sake, and patches for that have been around for over 2
years now.

--Adam




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Ethan Benson
On Thu, Jan 04, 2001 at 01:18:40AM -0500, Adam McKenna wrote:
  if this is the case the solution is fixing broken mailers, many of
  them are Free software so why have patches to support M-F-To not been
  made?
 
 I'd like to see someone convince that M-F-To fix Pine.  But I doubt you'll
 have an easy time getting Crispin to apply a patch.  He won't even implement 
 maildir, for christ sake, and patches for that have been around for over 2
 years now.

pine is a lost cause anyway.  i was thinking of GNUs which seems to be
the other big offender of ignorage of M-F-To.  (i am not sure if it
respects Mail-Copies-To: never i just started adding that.)  

btw is it Mail-Copies-To: never or Mail-Copies-To: nobody ?  i have
seen both which is correct?  (assuming any MUA actually pays any
attention to this header anyway)

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpGg3g9t1U7S.pgp
Description: PGP signature


Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Adam McKenna
On Wed, Jan 03, 2001 at 09:23:23PM -0900, Ethan Benson wrote:
 On Thu, Jan 04, 2001 at 01:18:40AM -0500, Adam McKenna wrote:
   if this is the case the solution is fixing broken mailers, many of
   them are Free software so why have patches to support M-F-To not been
   made?
  
  I'd like to see someone convince that M-F-To fix Pine.  But I doubt you'll
  have an easy time getting Crispin to apply a patch.  He won't even 
  implement 
  maildir, for christ sake, and patches for that have been around for over 2
  years now.
 
 pine is a lost cause anyway.  i was thinking of GNUs which seems to be
 the other big offender of ignorage of M-F-To.  (i am not sure if it
 respects Mail-Copies-To: never i just started adding that.)  

Actually, I'm pretty sure that Gnus respects M-F-To.  The biggest offenders
in that arena seem to be PINE and the GUI MUA's.

 btw is it Mail-Copies-To: never or Mail-Copies-To: nobody ?  i have
 seen both which is correct?  (assuming any MUA actually pays any
 attention to this header anyway)

Don't know, I don't use it.

--Adam




ITP: aterm -- an x terminal emulator

2001-01-04 Thread Chris Gray
Package: wnpp
Severity: wishlist

Description:http://aterm.sourceforge.net
aterm is based upon rxvt v.2.4.8 with add ons of 
Alfredo Kojima's NeXT-ish scrollbars. Fast transparency 
functionality, background lightening/darkening or/and 
tinting(coloring). Original idea of using ParentRelative
transparency mode belongs to Alfredo also, although code 
has been mostly reworked. It can also be integrated with
AfterStep libasimage for pixmap loading from various formats.

The licence is GPL.

If no one else is packaging this, I'd like to take it on.  I'm not a
maintainer yet, so I'll need a sponsor to upload it when it is ready.
I'll have it up on my apt-able site as soon as possible:

deb  http://www.cs.mcgill.ca/~cgray4 woody main
deb-src http://www.cs.mcgill.ca/~cgray4 woody main

Cheers,
Chris

-- 
Got jag?  http://www.tribsoft.com




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Ben Gertzfield
 Ethan == Ethan Benson [EMAIL PROTECTED] writes:

Ethan pine is a lost cause anyway.  i was thinking of GNUs which
Ethan seems to be the other big offender of ignorage of M-F-To.
Ethan (i am not sure if it respects Mail-Copies-To: never i just
Ethan started adding that.)

Gnus definitely respects M-F-To.  I'm using it now, and it confirmed
that I wanted to obey M-F-To when I followed-up to your message.

Ben

-- 
Brought to you by the letters J and Q and the number 7.
If you turn both processors off, you will have to reboot.
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/




Re: ITP: aterm -- an x terminal emulator

2001-01-04 Thread Branden Robinson
On Thu, Jan 04, 2001 at 01:27:13AM -0500, Chris Gray wrote:
 Package: wnpp
 Severity: wishlist
 
 Description:http://aterm.sourceforge.net

Someone please close this bug once it gets a number from the BTS.

Package: aterm
Priority: optional
Section: x11
Installed-Size: 308
Maintainer: Jordi Mallach [EMAIL PROTECTED]
Architecture: i386
Version: 0.4.0-2
Provides: x-terminal-emulator
Depends: libc6 (= 2.1.97), xlibs (= 4.0.1-1)
Filename: dists/woody/main/binary-i386/x11/aterm_0.4.0-2.deb
Size: 91952
MD5sum: 397b191f85e3140aaf82da0a75a37266
Description: Afterstep XVT - a VT102 emulator for the X window system
 Aterm is a colour vt102 terminal emulator, based on rxvt 2.4.8 with
 some additions of fast transparency, intended as an xterm replacement
 for users who do not require features such as Tektronix 4014
 emulation and toolkit-style configurability. As a result, aterm uses
 much less swap space -- a significant advantage on a machine serving
 many X sessions. It was created with AfterStep Window Manager users
 in mind, but is not tied to any libraries, and can be used anywhere.

-- 
G. Branden Robinson |You should try building some of the
Debian GNU/Linux|stuff in main that is modern...turning
[EMAIL PROTECTED]  |on -Wall is like turning on the pain.
http://www.debian.org/~branden/ |-- James Troup


pgpovSvyoatZr.pgp
Description: PGP signature


Re: our broken man package

2001-01-04 Thread Ethan Benson
On Wed, Jan 03, 2001 at 03:23:03PM -0800, Joey Hess wrote:
 I'm concerned with some breakage in the man program. Here is an example:
 
[snip examples]
 
 This is because man runs via a wrapper that makes it run as user man
 (and makes root's pager run as user man too for some reason).
 
 Related bugs: #74790, #60084, #58112, #42128.
 
 I have never seen an explination of why this wrapper program makes man
 run as user man. If it just ran it as group man, everything would be ok.
 As bug #42128 suggests, /var/catman/ could be writable by group man,
 rather than user man.

the problem with this is you end up with the catman files owned by
whatever user reads whatever man page.  personally as a sysadmin i
don't want users gaining write permission to files in any more places
under /var then there already is (ahem texmf).  i am not certain if
there is potential security threats to users being able to write bogus
catman files, perhaps via groff tricks there is.  

IMO a setgid man with a group writable /var/catman is not any better
then a mode 1777 /var/catman.  (which is what slackware does btw)
OpenBSD took another tack on this problem and just did away with
cached man pages altogether.  (no suid or sgid man) 

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgp1CiH8rxzJQ.pgp
Description: PGP signature


Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Adi Stav
On Wed, Jan 03, 2001 at 09:07:27PM -0900, Ethan Benson wrote:
 in that case there would be something funny going on, here is my
 theory:
 
 you post to list, you M-F-To: is set to only the list
 
 someone (Mr-Broken) with broken mailer uses reply-to-all which CCs you
 anyway ignoring M-F-To.
 
 mutt user uses list-reply to Mr-Broken's post, mutt sees you were CCed
 and assumes you should be included since there is no M-F-To header.
 mutt then sets the M-F-To header to include you for the benifit of
 later list-replies.  

How about having the mailing list software add M-F-To headers to mails
that do not have it and do not have Reply-To, filling it with the
mailing list only? Might help at least some of the cases.



- Adi Stav




Re: Rambling apt-get ideas

2001-01-04 Thread Matt Zimmerman
On Fri, Dec 29, 2000 at 11:11:01PM +0100, [EMAIL PROTECTED] wrote:

 Why not look at this from a different perspective? I don't know if it may be
 useful or not for upgrading machines, but the multicast server would be a
 very nice thing for mass installations.

I still disagree.  Multicast is the wrong solution.  Multicast data is
basically equivalent to a cache with zero object TTL.  Packets (objects) are
stored (by a network device) until a client needs them (immediately), at which
point they are served (multicasted/broadcasted) and expired (discarded).  Why
not replace this with a _real_ cache, which can store objects for a
user-definable period of time, allowing for later operations to benefit from
the cache?

It _might_ be useful to use multicast for a system which would trigger a bunch
of daemons to all download the same data from the cache, but even this is
doubtful.  Unless you are dealing with many thousands of clients, the overhead
for sending individually-addressed packets to the clients is minimal.

This is definitely a pull problem rather than a push problem.  Say a system
is being installed in a new location, which has network connectivity, but no
user consoles (yet).  Why should the admin have to find a live terminal in
order to tell the server to initiate a multicast installation?  Why not just
have the bootstrap disk fetch the necessary data?

 Image large computer rooms at a lan with (usually) uniform hardware. If there
 was a package (say apt-getd) that could be installed on one, already
 running box, which lets you make a special boot disk. The machine that runs
 apt-getd has a way to get to a debian archive (be it local mirror, a set of
 cdroms - this would probably be a bit harder with cd swapping - or a mirror
 on the larger network that it is connected to).

Better to separate automatic system building/configuration (a very hard problem
with relatively little progress) from efficient hierarchical file distribution
(an easier problem, with many good, stable tools already released).

 You boot with the floppy that configures the network, apt-getd starts
 spawning multicast packets, the workstations pick them up and install them.
 Voilà! You just installed an entire network!

Also consider:

You boot with the floppy that configures the network, start downloading files
over TCP, the workstations install them.
Voilà!  You just installed an entire network!

This approach will also work with heterogenous hardware, which is an issue in
a majority of enterprises.

-- 
 - mdz


pgpM6hCEo7s6C.pgp
Description: PGP signature


Re: need headers for target architecture: asm/unistd.h

2001-01-04 Thread Matt Zimmerman
On Fri, Dec 29, 2000 at 11:24:26PM +0100, Andreas Schuldei wrote:

 I try to build a crosscompiler i386-arm (but also other archs). At one 
 point headerfiles for the target architecture are needed. Where could I find
 headerfiles for other archs? Are there development packages for this purpose?
 Who has done this before?

You can find them in the libc6-dev package (or equivalent) for the target
architecture.  Perhaps they should be split off into an Architecture: all
package, so that they can be installed for use in cross-compilation?

-- 
 - mdz




Re: need headers for target architecture: asm/unistd.h

2001-01-04 Thread Matt Zimmerman
On Sat, Dec 30, 2000 at 12:39:58PM +0100, Andreas Schuldei wrote:

 * Andreas Schuldei ([EMAIL PROTECTED]) [001229 23:24]:
  I try to build a crosscompiler i386-arm (but also other archs). At one 
  point headerfiles for the target architecture are needed. Where could I find
  headerfiles for other archs? Are there development packages for this 
  purpose?
  Who has done this before?
 
 Will desaster wait at the other end if I use the include files from the
 kernel?

Sometimes.  You should use the same asm/ headers as were used when compiling
the libc you are linking with.

-- 
 - mdz




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Craig Sanders
On Wed, Jan 03, 2001 at 11:11:50PM -0700, John Galt wrote:
 On Thu, 4 Jan 2001, Craig Sanders wrote:
  Mail-Followup-To is the correct header to use.
 
 Mail-Followup-To isn't even a registered header!  The closest thing to a
 registry that RFC822 implies is in the hands of SRI International is

the thing about internet standards such as the RFCs is that they tell
you what you *must* do, and what you *must not* do. as long as you
follow those rules faithfully you are free to implement as many other
good ideas as you like.

 http://www.dsv.su.se/jpalme/ietf/mail-headers/
 
 (jpalme is as much of a member as one can be of the IETF RFC822 WG)
 
 which says that a Followup-To: header is from RFC 1036, but RFC 1036 is
 for USENET messages, not email.  The only thing I can think of is that
 somebody liked the usenet idea of the followup-to: and just appended a
 mail on it.  Just because somebody breaks the standards does NOT mean that
 everybody should.  

well done! it only took you a few years to catch on. that header has
been in common usage for several years.

btw, it's interesting that you mention Jacob Palme. take a look at the
following document written by him in November 1997:

http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt

Network Working Group   Jacob Palme
Internet Draft Stockholm University/KTH
draft-ietf-drums-mail-followup-to-00.txt
Expires: May 1998 November 1997


   The difference between pine and mutt is that you KNOW the
   overflows in pine
 
  incorrect, again. the difference between mutt and pine is that
  mutt is a decent piece of free software that works and follows the
  relevant standards, while pine is a broken piece of non-free shit
  which doesn't.

 Horsefeathers!  The Mail-followup-to: header is NOT a part of the
 relevant standards!

that wasn't what i said, and i in no way meant to imply that failure to
implement an optional but well-documented and well-known header is what
makes pine broken. pine is broken in numerous other ways.

craig

--
craig sanders




Re: our broken man package

2001-01-04 Thread Joey Hess
Ethan Benson wrote:
 the problem with this is you end up with the catman files owned by
 whatever user reads whatever man page.  personally as a sysadmin i
 don't want users gaining write permission to files in any more places
 under /var then there already is (ahem texmf).  i am not certain if
 there is potential security threats to users being able to write bogus
 catman files, perhaps via groff tricks there is.  

I'll bet (have not verified) that you can already trick it into writing
bogus file by sticking trojan pages elsewhere in your manpath.

 IMO a setgid man with a group writable /var/catman is not any better
 then a mode 1777 /var/catman.  (which is what slackware does btw)
 OpenBSD took another tack on this problem and just did away with
 cached man pages altogether.  (no suid or sgid man) 

-- 
see shy jo




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Craig Sanders
On Wed, Jan 03, 2001 at 11:15:23PM +0100, Sven Burgener wrote:
 On Wed, Jan 03, 2001 at 05:23:55PM +1100, Craig Sanders wrote:
  the new 'testing' distribution (sid) should be even better - nearly
  all the benefits of 'unstable' but tested to at least install properly
  without error.
 
 Wrong: unstable-sid; testing-woody.

yes, my mistake.  i don't know why i called it sid when i know it isn't.  a
brainfart.

my comments about the usefulness of the 'testing' distribution still
apply.

 Personally, I would recommend the use of 'testing' in a production
 environment, but not unstable. One doesn't always have the time to
 fix problems related to the distribution itself whilst working in a
 production environment.

i would recommend the use of either testing or unstable or stable
depending upon the particular requirements of the situation.

stable is good when you don't need or want any change at all.

testing is good when you want/need to be mostly up-to-date with the
latest versions but don't have the time to deal with packaging errors.

unstable is good when you want/need to be up-to-date and have both the
time and the skill to deal with any problems that may arise.



most people with a decent net connection will probably settle for using
'testing'however that won't be much use if nobody uses 'unstable' as
unstable packages won't get installed and tested, so bug reports won't
be filed, so unstable packages will move into testing without actually
having been tested by anyone.


craig

--
craig sanders




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Craig Sanders
On Wed, Jan 03, 2001 at 09:23:23PM -0900, Ethan Benson wrote:
 btw is it Mail-Copies-To: never or Mail-Copies-To: nobody ?  i have
 seen both which is correct?  (assuming any MUA actually pays any
 attention to this header anyway)

'nobody' is correct.

'never' is deprecated but still observed by many MUAs.

from the draft of Mail-Copies-To posted to the usenet-format list on 6
Nov 2000 (Message-Id: [EMAIL PROTECTED]):


6.  Optional Headers

6.1.  Mail-Copies-To

   The Mail-Copies-To header indicates whether or not the poster wishes
   to have followups to an article emailed in addition to being posted
   to Netnews and, if so, establishes the address to which they should
   be sent.

   The content syntax makes use of syntax defined in [MESSFOR], but
   subject to the revised definition of local-part given in section 5.2.

  Mail-Copies-To-content= copy-addr / nobody / poster
  copy-addr = mailbox

   The keyword nobody indicates that the author does not wish copies
   of any followup postings to be emailed.

   The keyword poster indicates that the author wishes a copy of any
   followup postings to be emailed to him.

   Otherwise, this header contains a copy-addr to which the author
   wishes a copy of any followup postings to be sent.

NOTE: Some existing practice uses the keyword never in place
of nobody and always in place of poster. These usages are
deprecated, but followup agents MAY observe them.



craig

--
craig sanders




Re: our broken man package

2001-01-04 Thread Ethan Benson
On Wed, Jan 03, 2001 at 11:53:37PM -0800, Joey Hess wrote:
 Ethan Benson wrote:
  the problem with this is you end up with the catman files owned by
  whatever user reads whatever man page.  personally as a sysadmin i
  don't want users gaining write permission to files in any more places
  under /var then there already is (ahem texmf).  i am not certain if
  there is potential security threats to users being able to write bogus
  catman files, perhaps via groff tricks there is.  
 
 I'll bet (have not verified) that you can already trick it into writing
 bogus file by sticking trojan pages elsewhere in your manpath.

i just tried it, did not end up with a cached file.  

[EMAIL PROTECTED] eb]$ export MANPATH=/home/eb/test
[EMAIL PROTECTED] eb]$ find /var/cache/man -name 'bogus*'
[EMAIL PROTECTED] eb]$ ls -l /home/eb/test/man8/
total 8
-rw-r--r--1 eb   eb   5193 Jan  3 23:03 bogus.8
[EMAIL PROTECTED] eb]$ man bogus 
Reformatting bogus(8), please wait...
...
[EMAIL PROTECTED] eb]$ find /var/cache/man -name 'bogus*'


it also doesn't cache anything when pointing man directly at a
specific man page:

[EMAIL PROTECTED] eb]$ find /var/cache/man -name 'yaboot*'
[EMAIL PROTECTED] eb]$ man devel/ybin/man/yaboot.8 
Reformatting yaboot.8, please wait...
...
[EMAIL PROTECTED] eb]$ find /var/cache/man -name 'yaboot*'
[EMAIL PROTECTED] eb]$

and yes my caching does work as you can see for a normal man page:

[EMAIL PROTECTED] eb]$ man yaboot
Reformatting yaboot(8), please wait...
...
[EMAIL PROTECTED] eb]$ find /var/cache/man -name 'yaboot*'
/var/cache/man/cat8/yaboot.8.gz

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpKKDIEKxmZF.pgp
Description: PGP signature


Re: DEBIAN IS LOOSING PACKAGES AND NOBODY CARES!!!

2001-01-04 Thread Brendan O'Dea
On Sun, Dec 31, 2000 at 01:09:07PM +, Oliver Elphick wrote:
Peter Palfrader wrote:
   There is a further weird package disappearance in unstable: all mgetty
   packages (execept mgetty-doc) are gone!
[...]
   Hey, these are important packages.
  
  mgetty is not important, it's extra.
 
That may be, but where has it gone?

mgetty* got bitten by an old [pre-pool] dinstall bug, where uploads
without unstable in the changelog disappear from unstable:

  mgetty (1.1.21-3) stable; urgency=low

* make mgetty-fax's postinst create /var/spool/fax/outgoing/.last_run
  to close a potential symlink exploit by members of the fax group
  that is otherwise possible until that file is created

   -- Philip Hands [EMAIL PROTECTED]  Thu, 31 Aug 2000 19:05:13 +0100

See http://bugs.debian.org/77585 .

Regards,
-- 
Brendan O'Deabod@compusol.com.au
Compusol Pty. Limited  (NSW, Australia)  +61 2 9810 3633




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Manoj Srivastava
Ethan == Ethan Benson [EMAIL PROTECTED] writes:

 Ethan pine is a lost cause anyway.  i was thinking of GNUs which
 Ethan seems to be the other big offender of ignorage of M-F-To.  (i
 Ethan am not sure if it respects Mail-Copies-To: never i just
 Ethan started adding that.)

That just demonstrates you have no idea what you are talking about.

manoj

-- 
 Alan Turing thought about criteria to settle the question of whether
 machines can think, a question of which we now know that it is about
 as relevant as the question of whether submarines can swim. Dijkstra
Manoj Srivastava   [EMAIL PROTECTED]  http://www.debian.org/%7Esrivasta/
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread John Galt
On Thu, 4 Jan 2001, Craig Sanders wrote:

 On Wed, Jan 03, 2001 at 11:11:50PM -0700, John Galt wrote:
  On Thu, 4 Jan 2001, Craig Sanders wrote:
   Mail-Followup-To is the correct header to use.
  
  Mail-Followup-To isn't even a registered header!  The closest thing to a
  registry that RFC822 implies is in the hands of SRI International is
 
 the thing about internet standards such as the RFCs is that they tell
 you what you *must* do, and what you *must not* do. as long as you
 follow those rules faithfully you are free to implement as many other
 good ideas as you like.

True, but you aren't free to bitch at people who follow the RFC's for
their failures (Branden...).  In fact, the header Branden's bitching
about is an animal of a wholly different color: the Mail-copies-to: header

Oh, BTW, I decided in the middle of this thread to finally throw in a
reply-to header.  You managed to email both myself and the list, so the
reply-to won't prevent people from privately emailing Branden: it didn't
prevent you from CCing the list (it's Reply-to: [EMAIL PROTECTED],
FWIW)--you see, I DO prefer CCs of list mail: it allows me to pay extra
attention to list mail directed at me.
 
  http://www.dsv.su.se/jpalme/ietf/mail-headers/
  
  (jpalme is as much of a member as one can be of the IETF RFC822 WG)
  
  which says that a Followup-To: header is from RFC 1036, but RFC 1036 is
  for USENET messages, not email.  The only thing I can think of is that
  somebody liked the usenet idea of the followup-to: and just appended a
  mail on it.  Just because somebody breaks the standards does NOT mean that
  everybody should.  
 
 well done! it only took you a few years to catch on. that header has
 been in common usage for several years.
 
 btw, it's interesting that you mention Jacob Palme. take a look at the
 following document written by him in November 1997:
 
 http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt

Curious he doesn't have in his updated RFC2097 (the URL I used)... Well, I
was looking for it, I found it (with your help).  Still, M-F-T is designed
for GROUP replies, not individual--from 2.2

The Mail-Followup-To header can be inserted by the sender of a
message to indicate suggestions on where replies, intended for the
group of people who are discussing the issue of the previous message,
are to be sent. Here are some ways of constructing this header:

Individual replies are still covered by the Reply-to: header, which is the
second away in alphabetical order from 98Dec proceedings (Chris Newman
at Innosoft wrote it):

http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-replyto-meaning-00.txt

---paste---
2. Reply-To Current Practice

 The Reply-To header is currently used for the following purposes:
---...---

 (2) The author/sender can recommend an address or addresses to use
 instead of the from address for replies.

 (3) The author/sender can post to multiple mailing lists and
 suggest group replies go to only one of them.

 (4) When the author/sender is subscribed to a mailing list, he can
 suggest that he doesn't want two copies of group replies to
 messages he posts to the list.

 (5) A mailing list can suggest that the list is a discussion list
 and replies should be sent just to the list by default.
---end paste---

I believe that there is some bit of what this thread first started about
within those 4 items...

 Network Working Group   Jacob Palme
 Internet Draft Stockholm University/KTH
 draft-ietf-drums-mail-followup-to-00.txt
 Expires: May 1998 November 1997
 
 
The difference between pine and mutt is that you KNOW the
overflows in pine
  
   incorrect, again. the difference between mutt and pine is that
   mutt is a decent piece of free software that works and follows the
   relevant standards, while pine is a broken piece of non-free shit
   which doesn't.
 
  Horsefeathers!  The Mail-followup-to: header is NOT a part of the
  relevant standards!
 
 that wasn't what i said, and i in no way meant to imply that failure to
 implement an optional but well-documented and well-known header is what
 makes pine broken. pine is broken in numerous other ways.

 craig
 
 --
 craig sanders
 

-- 
Pardon me, but you have obviously mistaken me for someone who gives a
damn.
email [EMAIL PROTECTED]





Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Ethan Benson
On Thu, Jan 04, 2001 at 02:48:46AM -0600, Manoj Srivastava wrote:

   That just demonstrates you have no idea what you are talking about.

oh please.  someone already pointed out to me that older versions of
Gnus ignored M-F-To but the current one does not.

go fuck off.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpBNlHDjb9vb.pgp
Description: PGP signature


Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Peter Makholm
John Galt [EMAIL PROTECTED] writes:

PLEASE DON'T CC ME. I'M ON THE LIST

 FYI 28 (aka RFC 1855) is the standard.

Strictly speaking it's is only a standard if it is on the Standard
Track and RFC1855 isn't. It is only an informational RFC.

PLEASE DON'T CC ME. I'M ON THE LIST




Re: Anybody seen Loic Prylli lately?

2001-01-04 Thread Christian Kurz
On 01-01-04 Chuan-kai Lin wrote:
 Does anyone know where Loic has been lately (i.e., for the past two years
 or so)?  AFAIK his last package upload was in November 1998, and the mail
 I sent him about whether he needs help with mailx has generated no reply.
 Since mailx is important, if the maintainer is indeed MIA, somebody should
 take over this package and jove.  I would volunteer for mailx in the
 unlikely event that nobody else wants that package.

If you would have looked into unstable first, you would have noticed
that jove has been taken over by Cord Beermann, an upcoming new
maintainer and I had once a contact with Loic to talk with him about his
jove package. Now I'm waiting for his answer about mailx, so please wait
some time more, so that I be able to get an answer from him.

Ciao
 Christian
-- 
  Debian Developer and Quality Assurance Team Member
1024/26CC7853 31E6 A8CA 68FC 284F 7D16  63EC A9E6 67FF 26CC 7853




Re: Problem with start-stop-daemon and pidfile

2001-01-04 Thread Matt Zimmerman
On Wed, Jan 03, 2001 at 02:10:19AM +0100, Goswin Brederlow wrote:

 touch /var/run/debian-mirror.pid
 chown mirror.nogroup /var/run/debian-mirror.pid
 
 touch /var/log/debian-mirror.log
 chown mirror.nogroup /var/log/debian-mirror.log

Please don't do this.  nogroup should not be the group of any files, just as
nobody should not be the owner of any files.

-- 
 - mdz




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Matt Zimmerman
On Mon, Jan 01, 2001 at 11:06:18PM -0800, Erik Hollensbe wrote:

 apt-get and it's kin need more simple getopt-style flags that allow
 overriding of certain things, mainly conflicts. Also, an option to
 actually view what's being upgraded before you download 250 packages that
 are only going to break your system would be nice as well.

I assume you already are using apt-get's -u/--show-upgraded flag.  Beyond that,
check out apt-listchanges, in the package of the same name.  Currently, you
need to download the .deb's first, but even if there is a breakage, you would
have ended up downloading them eventually anyway.  Eventually, apt-listchanges
will be able to show changelogs before downloading any packages.

-- 
 - mdz




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Manoj Srivastava
Ethan == Ethan Benson [EMAIL PROTECTED] writes:

 Ethan On Thu, Jan 04, 2001 at 02:48:46AM -0600, Manoj Srivastava wrote:
  That just demonstrates you have no idea what you are talking about.

 Ethan oh please.  someone already pointed out to me that older
 Ethan versions of Gnus ignored M-F-To but the current one does not.

Considering the mail-followup-to stuff was only introduced in
 a failed standards attempt in 1998, it is not surprising that
 versions of Gnus before that (not having the gift of prescience) did
 not honour that. 

 Ethan go fuck off.

You prove my point. Resorting to invective is the last refuge
 of the incompetent. This is your second demonstration of incompetence
 in a public forum in 24 hours; and I suspect your drop in the
 estimation of the readers of this mailing list is far worse than any
 response in kind I could indulge in.

manoj
-- 
 There are times when truth is stranger than fiction and lunch time is
 one of them.
Manoj Srivastava   [EMAIL PROTECTED]  http://www.debian.org/%7Esrivasta/
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




Unclean licences

2001-01-04 Thread Pawel Wiecek
Hello

One of the programs I'd like to package has somewhat unclean licence.
The readme file says only:

COPYRIGHT: This program is FREEWARE!

which I don't suppose is enough for us.

The webpage is a bit more descriptive and says:

   These programs are freeware, which means that they may be distributed
   freely.

Is this enough for us, or do I have to bug authors for a cleaner licence?

Pawel

-- 
 (___)  | Pawel Wiecek  +48603240006  http://www.coven.vmh.net/ |
 o o  | [EMAIL PROTECTED] GPG/PGP: www.coven.vmh.net/personal/pgpkey.html |
 \ ^ /  |  *   *   If you don't like the answer,   *   *  |
  ()   |  *   *   you shouldn't have asked the question.  *   *  |




Re: [Fwd: Bug#63511 acknowledged by developer(Bug#63511: fixed in glibc 2.2-7)]

2001-01-04 Thread Eray Ozkural \(exa\)
Russell Coker wrote:
 
 I'm sure that Ben will welcome your contributions towards maintaining the
 libc6 package.  All you have to do is read the list of bugs, solve some, and
 send in patches.

I'm not trying to bash Ben. He did a wonderful work in resolving many
bugs and generally keeping up-to-date with the CVS and builds of
all architectures which is a difficult job. My suggestion is another:
give packages multiple developers and have a more formal way for others
to evaluate bugs... It wouldn't be wrong to have at least 2 developers
especially for important packages.

Thanks,

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Ethan Benson
On Thu, Jan 04, 2001 at 03:34:26AM -0600, Manoj Srivastava wrote:

   You prove my point. Resorting to invective is the last refuge
  of the incompetent. This is your second demonstration of incompetence
  in a public forum in 24 hours; and I suspect your drop in the
  estimation of the readers of this mailing list is far worse than any
  response in kind I could indulge in.

if only we could all be as perfect as you.   I has simply made the
statement that Gnus users were commonly ignoring M-F-To and rather
then kindly point out that old versions did but the current one no
longer has this problem like another poster did you had to be
insulting and condescending.  well i returned the favor.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpBzEHyz3hjA.pgp
Description: PGP signature


ITP: crack

2001-01-04 Thread Pawel Wiecek
Hello.

I'd like to package CRACK, the well know password security checker.
It has a nice licence, derived from Artistic and is no doubt a useful tool
for an administrator.

  Pawel

-- 
 (___)  | Pawel Wiecek  +48603240006  http://www.coven.vmh.net/ |
 o o  | [EMAIL PROTECTED] GPG/PGP: www.coven.vmh.net/personal/pgpkey.html |
 \ ^ /  |  *  *  Join the army! Meet interesting, exciting people.  *  *  |
  ()   |  *  *And kill them.   *  *  |




Re: our broken man package

2001-01-04 Thread Peter Makholm
Lars Wirzenius [EMAIL PROTECTED] writes:

 On the other hand, we might want to copy the OpenBSD version instead
 of maintaining our own man. But I leave that to whoever maintains the
 packages.

We have alternatives on almost everything but dpkg and man. If someone
thinks it's worth the effort to make alternatives for these they
should do it. If there is a general agreement that the alternatives is
better than the original packages we just switch prioryties.

So simple is that.




Need server

2001-01-04 Thread Michael Meskes
Is there any apt-able server out there that is accessible with a better
bandwidth than ftp.debian.org (currently 468 bytes/sec) but still is
up-to-date?

ftp.debian.org has been very flaky for me for weeks. And neither
ftp.de.debian.org nor source.rfc822.org are up-to-date. I guess they have
the very same problem accessing ftp.debian.org during their mirror process.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!




Re: Unclean licences

2001-01-04 Thread Peter Makholm
Pawel Wiecek [EMAIL PROTECTED] writes:

These programs are freeware, which means that they may be distributed
freely.

Nope, we should explicitly have the rights to distribute and modify
the program.




What happened to libnss1-compat?

2001-01-04 Thread Michael Meskes
I have a commercial binary that needs this library. Yes, I can find it in
potato, but not in unstable. Is there a new package providing
libnss1-compat?

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!




Re: [Fwd: Bug#63511 acknowledged by developer(Bug#63511: fixed in glibc 2.2-7)]

2001-01-04 Thread Matt Zimmerman
On Wed, Jan 03, 2001 at 10:20:11AM -0500, Ben Collins wrote:

  I've just reported what I had thought, some many many months ago,
  to be a problem. Of course, the maintainer has not done anything
  about this report for 7 months, and then he closes it like that.
  Not good.
 
 Oh, and just to chime in on this little bit, I did not start maintaining
 glibc until Aug 31, 2000 (my first changelog entry). So no, I have not
 been sitting on this for 7 months. Get your facts straight.

And just to chime in, I appreciate the huge effort and many juicy changelog
entries that have gone into libc6 recently.

-- 
 - mdz




ITP: lovecalc

2001-01-04 Thread Pawel Wiecek
Hello

I'd like to package lovecalc (http://www.lovecalculator.com/).
Because of kinda unclean licence I'm not quite sure if it'll go into main or
non-free (this depends on whether I convince the author to write a more
precise one, I guess).

Pawel

-- 
 (___)  | Pawel Wiecek --- [EMAIL PROTECTED] +48603240006 |
 o o  | WWW: http://www.coven.vmh.net/   [ Debian GNU/Linux developer ] |
 \ ^ /  |   GPG/PGP key:  http://www.coven.vmh.net/personal/pgpkey.html   |
  ()   |   *  What's apathy? I don't know and I don't care.  *   |




Re: [Fwd: Bug#63511 acknowledged by developer(Bug#63511: fixed in glibc 2.2-7)]

2001-01-04 Thread Russell Coker
On Thursday 04 January 2001 20:50, Eray Ozkural (exa) wrote:
 Russell Coker wrote:
  I'm sure that Ben will welcome your contributions towards maintaining the
  libc6 package.  All you have to do is read the list of bugs, solve some,
  and send in patches.

 I'm not trying to bash Ben. He did a wonderful work in resolving many
 bugs and generally keeping up-to-date with the CVS and builds of
 all architectures which is a difficult job. My suggestion is another:
 give packages multiple developers and have a more formal way for others
 to evaluate bugs... It wouldn't be wrong to have at least 2 developers
 especially for important packages.

This is already being done for some packages.  Check the maintainer address 
on the gcc package for an example.

The thing that determines this is whether there are multiple people who are 
skillful and willing to work.

If you want to be the second developer for libc6 then start fixing some bugs!

-- 
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/   Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page




Re: Bug#81180: ITP: aterm -- an x terminal emulator

2001-01-04 Thread Marcelo E. Magallon
 Chris Gray [EMAIL PROTECTED] writes:

  Description:http://aterm.sourceforge.net

 [4 ysabell:~] grep-available -s Package,Maintainer -P aterm
 Package: aterm-ml
 Maintainer: Jordi Mallach [EMAIL PROTECTED]

 Package: aterm
 Maintainer: Jordi Mallach [EMAIL PROTECTED]

 Please close bug#81180 as appropiate.

--
Marcelo




ITP: yardradius

2001-01-04 Thread Francesco Lovergine

I gonna package yardradius, see http://yardradius.sourceforge.net.
I'm the upstream author.

$Id: README,v 1.4 2001/01/02 09:41:19 kiavik Exp $

Yet Another Radius Daemon (YARD RADIUS) README File


This program is a RADIUS RFC compliant daemon which is derived from
original Livingston Enterprise Inc. RADIUS daemon release 2.1. It adds a
number of useful features to the LE daemon, i.e.

Control of simultaneous logins.
Support of Ascend, Cisco and USR boxes.
Extended daily/monthly/yearly accouting information on a per-user basis.
MD5 encrypted passwords support (both in passwd file and/or users file).
Expirations in shadow file.
Checking based on time-of-day, traffic and connection time.
Support of PAM authentication and accounting.
Binary form of accounting file.
GDBM formats for users and user stats databases.
Autoconfiguring capabilities of sources. 

It supports also all features of LE daemon, i.e.:

Proxy RADIUS
ActivCarda and iPass Support
Accounting Signatures Now Required
Vendor  Specific Attributes
Virtual Ports
Alternate Password File
Address Binding
Improved Messages
Enhanced Debugging

All sources are much cleaner than the original version of Livingston, and
require an ANSI C compiler. A lots of potential buffer overflows have
been corrected by means of massive use of snprintf().

All software is under BSD like license. 

-- 
Francesco P. Lovergine




Re: libapache-asp-perl - perl Apache::ASP - Active Server Pages for Apache with mod_perl.

2001-01-04 Thread Piotr Roszatycki
On 22 Dec 2000, Stephen Zander wrote:
 Piotr ITO: libapache-asp-perl
 Piotr ITO: libapache-filter-perl
 Piotr ITO: libapache-ssi-perl
 Piotr ITO: libcgi-pm-perl
 Piotr ITO: libdbd-csv-perl
 Piotr ITO: libhtml-clean-perl
 Piotr ITO: libhtml-simpleparse-perl
 Piotr ITO: libsql-statement-perl
 Piotr ITO: libtext-csv-perl
 
 I will happily pick all these up.

Ok, they're your.


-- 
Piotr Roszatycki | SD Specialist
Internetia Telekom Sp. z o.o.
Netia Holdings S.A. | PL 00-822 Warszawa, ul. Poleczki 13
tel. +48 (22) 648 45 00 wew. 2068




Re: [Fwd: Bug#63511 acknowledged by developer(Bug#63511: fixed in glibc 2.2-7)]

2001-01-04 Thread Eray Ozkural \(exa\)
Matt Zimmerman wrote:
 
  Oh, and just to chime in on this little bit, I did not start maintaining
  glibc until Aug 31, 2000 (my first changelog entry). So no, I have not
  been sitting on this for 7 months. Get your facts straight.
 
 And just to chime in, I appreciate the huge effort and many juicy changelog
 entries that have gone into libc6 recently.

I do, too. I appreciate Ben's skills and effort. Sorry if there's
misunderstanding. For instance, there was this bug about fmemopen() and
a few days later, the fix from CVS was in debian. Amazing.

Thanks,

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo




Re: [Fwd: Bug#63511 acknowledged by developer(Bug#63511: fixed in glibc 2.2-7)]

2001-01-04 Thread Eray Ozkural \(exa\)
Russell Coker wrote:
 
 This is already being done for some packages.  Check the maintainer address
 on the gcc package for an example.
 
 The thing that determines this is whether there are multiple people who are
 skillful and willing to work.
 
 If you want to be the second developer for libc6 then start fixing some bugs!

Ahem! *choke* Perhaps, I must start with the (inaccurate) bug I'd
reported!!

I'll just determine the cause of that bug and see what I can do myself.

Thanks,

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo




PGP/GPG transition + db.debian.org

2001-01-04 Thread Pawel Wiecek
How long does it take usually for a (GPG) key sent to keyring.debian.org
to show up in official keyring (and maintainers database)?
I'm waiting for my new GPG key to show up for quite a few weeks and it seems a
bit excessive to me :^)

BTW -- our web interface to developers database (http://db.debian.org/) seems
to be broken since a week or so... Both searching (goes back to index page)
and logging in (returns page redirected to itself) don't seem to work.

 Pawel

-- 
 (___)  | Pawel Wiecek --- [EMAIL PROTECTED] +48603240006 |
 o o  | WWW: http://www.coven.vmh.net/   [ Debian GNU/Linux developer ] |
 \ ^ /  |   GPG/PGP key:  http://www.coven.vmh.net/personal/pgpkey.html   |
  ()   |  *   Never explain.  *  |




ITP: Rhythm Composer TK-707 (And suggestions for sound in debian)

2001-01-04 Thread Eduardo Marcel Macan
Yes, I've been in a packaging mood lately :)

I'd like to have Tk707 packaged. Tk707 is a software clone of the
Roland TR-707 rhythm composer, a drum machine.

It is written in C and Tk and it uses the alsa sequencer. I am using
it together with the latest alsa modules and lib (compiled from source)
so I'd need someone who uses the alsa drivers provided in woody to help
me get dependencies right and test it.

I am also using timidity++ as an alsa server doing software wavetable
synthesis compiled from sources, the debian package was not compiled
with this option. It would be nice if we had this option enabled in
timidity++ or a timidity-alsa package. (I haven't checked to see if
this was done lately).

alsa + timidity makes it possible do create really good sounding music
without having an expensive sound card. Jazz++ can also use alsa and 
timidity.  If we had alsa, timidity and jazz++ into debian enabled to
work together we would provide an almost complete MIDI music composition
environtment.

Someone tried to get jazz++ packaged (again) a while ago but I
have not seen it in unstable nor any news from the person trying to
do it...

Regards,

Eduardo.




Re: dpkg-statoverride vs. suidmanager

2001-01-04 Thread Wichert Akkerman
Previously Joey Hess wrote:
 Wichert Akkerman wrote:
  This still leaves us with two problems:
  1. there is no 100% correct way to decide if something is an override
 or not
 
 They're flagged local or so arn't they?

Either `local' or 'user' in my suid.conf, but it could be anything
except the packagename basically.

Wichert.

-- 
   
 / Generally uninteresting signature - ignore at your convenience  \
| [EMAIL PROTECTED]  http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |




Re: PGP/GPG transition + db.debian.org

2001-01-04 Thread Peter Palfrader
Hi Pawel!

On Thu, 04 Jan 2001, Pawel Wiecek wrote:

 How long does it take usually for a (GPG) key sent to keyring.debian.org
 to show up in official keyring (and maintainers database)?
 I'm waiting for my new GPG key to show up for quite a few weeks and it seems a
 bit excessive to me :^)

New keys sent to keyring.debian.org via gpg --send will take approximatly
forever. New keys have to be added my hand by the keyring maintainer and
this might long (up 2 12 months?) (see a thread here on -devel perhaps a
month or two ago).


 BTW -- our web interface to developers database (http://db.debian.org/) seems
 to be broken since a week or so... Both searching (goes back to index page)
 and logging in (returns page redirected to itself) don't seem to work.

[EMAIL PROTECTED] knows about this.

yours,
peter

-- 
PGP signed and encrypted messages preferred.
http://www.palfrader.org/


pgpo7LWgjJNJK.pgp
Description: PGP signature


Re: Need server

2001-01-04 Thread Josip Rodin
On Thu, Jan 04, 2001 at 11:01:43AM +0100, Michael Meskes wrote:
 Is there any apt-able server out there that is accessible with a better
 bandwidth than ftp.debian.org (currently 468 bytes/sec) but still is
 up-to-date?

There are almost two hundred public Debian mirrors, use them.

http://www.debian.org/misc/README.mirrors

-- 
Digital Electronic Being Intended for Assassination and Nullification




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Mark Brown
On Wed, Jan 03, 2001 at 08:44:49PM -0500, Adam McKenna wrote:
 On Wed, Jan 03, 2001 at 08:41:06PM -0500, Branden Robinson wrote:

  If I'm already replying to a list, I'm not going to waste bandwidth by
  mailing you personally as well.

 So what you're saying is that you're purposely ignoring people's
 Mail-Followup-To when it suits you, while insisting that others abide by 
 yours?  That sounds kind of ridiculous to me.

OTOH, the behaviour in the absence of any Mail-Followup-To: should be to
reply to either the list or the sender but not both.

-- 
Mark Brown  mailto:[EMAIL PROTECTED]   (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/




Re: maybe ITP rsync mirror script for pools

2001-01-04 Thread Ingo Saitz
On Wed, Jan 03, 2001 at 06:14:05PM -0500, Adam McKenna wrote:
 On Wed, Jan 03, 2001 at 11:57:07PM +0100, Marco d'Itri wrote:
  Please don't encourage private mirrors!
 
 Debian itself encourages private mirrors.  Personally, I'd rather just
 download a new ISO every 3 months or so as new versions come out but the
 cdimage.debian.org pages steer people heavily toward mirroring and producing
 their own CD images with the debian-cd package.

I think you missed the point Marco d'Itri was talking about.
Downloading CD images is not different from keeping a private
mirror up to date. The private mirror even might save you some
bandwidth.

Also cdimage.debian.org suggests that you install from a public
mirror, if you have the bandwidth you'd also require to keep a
local mirror or download CD images.

Debian currently contains much more packages than anybody would
install. I doubt that even on big installations more than 50%
of all debian packages would be installed. Debian includes
additional tools (apt), that make accessing remote repositories
easier than finding packages by hand in a local mirror.

Thus a proxy would serve local machines much better than a local
mirror or CD images. For a single host I'd suggest running
apt-get -d overnight.

Ingo
-- 
16  Hard coded constant for amount of room allowed for
cache align and faster forwarding (tunable)

-- seen in /usr/src/linux-2.2.14/net/TUNABLE




Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Erik Hollensbe
THANK YOU. Finally, an answer that I can use.

I will look into contributing towards this package.

-- 
Erik Hollensbe [EMAIL PROTECTED]
Programmer, Powells Internet Division
I respect a man who lets me know where he stands, even if he is wrong.
- Malcolm X

On Thu, 4 Jan 2001, Matt Zimmerman wrote:

 On Mon, Jan 01, 2001 at 11:06:18PM -0800, Erik Hollensbe wrote:

  apt-get and it's kin need more simple getopt-style flags that allow
  overriding of certain things, mainly conflicts. Also, an option to
  actually view what's being upgraded before you download 250 packages that
  are only going to break your system would be nice as well.

 I assume you already are using apt-get's -u/--show-upgraded flag.  Beyond 
 that,
 check out apt-listchanges, in the package of the same name.  Currently, you
 need to download the .deb's first, but even if there is a breakage, you would
 have ended up downloading them eventually anyway.  Eventually, apt-listchanges
 will be able to show changelogs before downloading any packages.






quota package and wishlist #67556

2001-01-04 Thread Illo de' Illis
The severity of bug #67556 (package quota) should be changed from wishlist to
important since it fixes a problem which makes the package unusable on big
endian architectures (getopt() returns int(-1) and not char(-1)). Or at least
it should be advisable to separate the getopt() bug from the rest and submit
it as important.

Ciao,
Illo.

-- 

Ilario Nardinocchi, [EMAIL PROTECTED] - Computer Science Adept since 1982
[EMAIL PROTECTED]   - Oy gevalt, I'm so ferklempt that I
   could plotz!
Know-nothing-bozo rule:
The views expressed above are entirely mine and do not represent the views,
policy or understanding of any other person or official body.





Re: What happened to libnss1-compat?

2001-01-04 Thread Ben Collins
On Thu, Jan 04, 2001 at 11:03:15AM +0100, Michael Meskes wrote:
 I have a commercial binary that needs this library. Yes, I can find it in
 potato, but not in unstable. Is there a new package providing
 libnss1-compat?

libnss1-compat would not compile cleanly with the latest glibc. So if
you need this, either keep it around from potato, or convince someone to
package it seperately.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'




Re: Need server

2001-01-04 Thread Michael Meskes
On Thu, Jan 04, 2001 at 01:48:34PM +0100, Josip Rodin wrote:
 There are almost two hundred public Debian mirrors, use them.

Sure. But I was hoping someone would know a machine that a) is up-to-date
(the three machines outside the US I tried so far are not) and b) is
accessible pretty well (which ftp.debian.org is not).

As you might imagine trying 200 machines is not really funny. In fact I was
hoping someone would tell me that ftp.debian.org will be much better
accessible in the near future.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!




Re: ITP: crack

2001-01-04 Thread Andreas Voegele
Pawel Wiecek writes:

 I'd like to package CRACK, the well know password security checker.
 It has a nice licence, derived from Artistic and is no doubt a
 useful tool for an administrator.

Have you looked at the package john?  AFAIK john can do anything crack
can do.




Re: Need server

2001-01-04 Thread Bart Schuller
On Thu, Jan 04, 2001 at 02:56:41PM +0100, Michael Meskes wrote:
 On Thu, Jan 04, 2001 at 01:48:34PM +0100, Josip Rodin wrote:
  There are almost two hundred public Debian mirrors, use them.
 
 Sure. But I was hoping someone would know a machine that a) is up-to-date
 (the three machines outside the US I tried so far are not) and b) is
 accessible pretty well (which ftp.debian.org is not).

download.sourceforge.net

Does rsync too :-)

-- 
The idea is that the first face shown to people is one they can readily
accept - a more traditional logo. The lunacy element is only revealed
subsequently, via the LunaDude. [excerpted from the Lunatech Identity Manual]




Re: ITP: crack

2001-01-04 Thread Mark Brown
On Thu, Jan 04, 2001 at 03:04:07PM +0100, Andreas Voegele wrote:
 Pawel Wiecek writes:

  I'd like to package CRACK, the well know password security checker.
  It has a nice licence, derived from Artistic and is no doubt a
  useful tool for an administrator.

 Have you looked at the package john?  AFAIK john can do anything crack
 can do.

john is a single process cracker - it can't distribute the load over
multiple CPUs and multiple machines.

-- 
Mark Brown  mailto:[EMAIL PROTECTED]   (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/




Re: PGP/GPG transition + db.debian.org

2001-01-04 Thread Pawel Wiecek
On Jan 4,  1:11pm, Peter Palfrader wrote:
 New keys sent to keyring.debian.org via gpg --send will take approximatly

Gosh...

 forever. New keys have to be added my hand by the keyring maintainer and

Emailed him as well...

 this might long (up 2 12 months?) (see a thread here on -devel perhaps a
 month or two ago).

I can't find it in the archive...

   Pawel

-- 
 (___)  | Pawel Wiecek --- [EMAIL PROTECTED] +48603240006 |
 o o  | WWW: http://www.coven.vmh.net/   [ Debian GNU/Linux developer ] |
 \ ^ /  |   GPG/PGP key:  http://www.coven.vmh.net/personal/pgpkey.html   |
  ()   | Love isn't only blind, it's also deaf, dumb, and stupid.|




Re: Rambling apt-get ideas

2001-01-04 Thread Vince Mulhollon


With the raging flame war going on about MUAs, I'm embarassed to mail this
with lotus notes, but, hey, its all I have at work.

Back on topic, I would have thought that package distribution was a one
time shot.  Caches are for people who would otherwise download the
slashdot.org header graphic fifty times a day.  Whereas each individual
debian machine should only have to download the latest perl .deb once in
it's life.  If I apt-get upgrade through my http cache, all I do is flood
the cache with megs of data I'll never download again.

I'm not sure about the overhead is minimal for less than a thousand
clients.  I have 18 or so debian workstations at work.  If it takes 5
minutes to transfer all the .debs to upgrade one machine, then I think it
would take a unicast system slightly less than 18*5 minutes (about 1 1/2
hours) to upgrade, vs 5 minutes for a multicast system to upgrade.  A
unicast upgrade could be an start it and go to lunch process whereas a
multicast upgrade would be a get a cup of coffee process.  If I had a
hundred machines to upgrade, the comparison would be even greater.  Yeah,
wasting 17*5 minutes is not the end of the world, but why not try harder to
do better?

The concept of the system I'm discussing, is one master machine downloads
the .deb via http.  Then it multicasts the .deb to all the other machines
at once.  All of them are on the same subnet so some variety of layer 2
multicast / broadcast would work, although it would be nice to go beyond
the subnet if necessary.

I agree that the discussion about new installs points out that sometimes,
pull based systems have an advantage.  I'm pointing out that sometimes,
push based systems have an advantage.  And I'm motiviated because I
believe my situation at work is one of those situations where push is the
better answer.





Matt

ZimmermanTo: debian-devel@lists.debian.org  

[EMAIL PROTECTED]cc: (bcc: Vince 
Mulhollon/Brookfield/Norlight) 
rg  Fax to:

Sent by: MattSubject: Re: Rambling apt-get 
ideas
Zimmerman   

[EMAIL PROTECTED]  
 
t  





01/04/2001  

01:45 AM









On Fri, Dec 29, 2000 at 11:11:01PM +0100, [EMAIL PROTECTED] wrote:

 Why not look at this from a different perspective? I don't know if it may
be
 useful or not for upgrading machines, but the multicast server would be a
 very nice thing for mass installations.

I still disagree.  Multicast is the wrong solution.  Multicast data is
basically equivalent to a cache with zero object TTL.  Packets (objects)
are
stored (by a network device) until a client needs them (immediately), at
which
point they are served (multicasted/broadcasted) and expired (discarded)

Re: bugs + rant + constructive criticism (long)

2001-01-04 Thread Jim Lynch
 
 Date:Thu, 04 Jan 2001 11:06:43 +1100
 To:  Jim Lynch [EMAIL PROTECTED]
 cc:  Erik Hollensbe [EMAIL PROTECTED], debian-devel@lists.debian.org,
[EMAIL PROTECTED]
 From:Craig Sanders [EMAIL PROTECTED]
 Subject: Re: bugs + rant + constructive criticism (long)
 
 On Wed, Jan 03, 2001 at 06:16:17AM -0800, Jim Lynch wrote:
  If you want to advocate the use of unstable software, please be my
  guest... but not on #debian. it changes daily, and can potentially
  break every day, potentially disasterously. So -no-. It's NOT
  appropriate to tell people to run servers on unstable software.
 
 if i ever happen to be on #debian and someone has a problem where the
 best solution is to upgrade to unstable (either a full dist-upgrade or
 just selected packages) then i certainly will recommend exactly that.

So long as you warn the person about (1) general unstability and (2)
unstability produced by upgrading, no problem. Fail to do that (I don't
think you will) and you represent a problem. I will act in some way if
I see it.

 it is *always* appropriate to provide a good solution to a problem -
 whether it accords with your opinion or not.

That's fairly general, enough to be overbroad and out of this context
and in some other; in that other, broader context, of course I agree.

-Jim




  1   2   >