Release-critical Bugreport for December 22, 2000

2000-12-22 Thread BugScan reporter
Bug stamp-out list for Dec 22 05:15 (CST)

Total number of release-critical bugs: 485
Number that will disappear after removing packages marked [REMOVE]: 0

--

Package: afbackup (debian/main)
Maintainer: Christian Meder [EMAIL PROTECTED]
  77189  afbackup: cartis cannot detect which is the server config file

Package: afterstep (debian/main)
Maintainer: Steven R. Baker [EMAIL PROTECTED]
  69297  afterstep: Pager causes wharf to go wonky
  75330  afterstep: Please merge changes from potato version (patch available).

Package: aolserver (debian/main)
Maintainer: Brent A. Fulgham [EMAIL PROTECTED]
  77783  SECURITY: buffer overrun potential in Ns_DStringPrintf() call

Package: apache (debian/main)
Maintainer: Johnie Ingram [EMAIL PROTECTED]
  72468  apache: log file permissions are insecure
  75087  cron.daily for apache sends SIGHUP to any process with
  75941  jserv: configuring jserv kills libapache-mod-ssl
  77621  Assertion `new_opencount[0] == 0' failed
  78527  Apache 1.3.12-2.2 returns no data (at least when calling 
http://localhost/)
  79256  apache should include mod_mime module
  79301  Apache's mod_auth_db insists existent and world readable file does not 
exist
  79364  apache build on potato breaks woody php4 (DB2 and pgsql)
  80210  Needs a recompile against new libc6 (again)

Package: apache-common (debian/main)
Maintainer: Johnie Ingram [EMAIL PROTECTED]
  73004  apache-common: undefined symbol shm_ something
  73013  Security vulnerability in Apache mod_rewrite (fwd)
  74306  apache-common: Incorrect mysql return results

Package: apache-perl (debian/main)
Maintainer: Daniel Jacobowitz [EMAIL PROTECTED]
  70472  AddDefaultCharset problem
  77893  libapache-dbi-perl: @INC problems when starting apache with module 
AuthDBI
  78676  Apache in woody is now 1.3.14, apache-perl needs to be re-compiled

Package: apcupsd (debian/main)
Maintainer: Martin Mitchell [EMAIL PROTECTED]
  74060  apcupsd: apcupsd doesn't take any action on powerfail

Package: apt (debian/main)
Maintainer: APT Development Team [EMAIL PROTECTED]
  78712  apt: problem resolver refuses to deinstall obsolete packages

Package: aptitude (debian/main)
Maintainer: Daniel Burrows [EMAIL PROTECTED]
  80183  aptitude_0.0.7.14-1(unstable): error in build dependencies

Package: arpwatch (debian/main)
Maintainer: KELEMEN Peter [EMAIL PROTECTED]
  78228  arpwatch: On upgrade /var/lib/arpwatch/arp.dat is cleared

Package: aspell (debian/main)
Maintainer: Sudhakar Chandrasekharan [EMAIL PROTECTED]
  78986  aspell dies, seemingly due to too many Ignores

Package: autofs (debian/main)
Maintainer: Adam Heath [EMAIL PROTECTED]
  75909  [PATCH] autofs needs a patch for building on Alpha and sparc

Package: autolog (debian/main)
Maintainer: Nicolás Lichtmaier [EMAIL PROTECTED]
  73051  autolog: autolog creates endless zombies after upgrade to libc6-2.1.94

Package: barracuda (debian/main)
Maintainer: Arpad Magosanyi [EMAIL PROTECTED]
  79646  Database code errors during installation.

Package: base-config (debian/main)
Maintainer: Joey Hess [EMAIL PROTECTED]
  77920  passwords entered in base-config are not treated literally
  79336  base-config bug

Package: base-passwd (debian/main)
Maintainer: Wichert Akkerman [EMAIL PROTECTED]
  52065  [hurd] does not compile
  69819  base-passwd: update-passwd fails when a group has too many members

Package: bbdb (debian/main)
Maintainer: Takuo KITAME [EMAIL PROTECTED]
  78564  bbdb breaks gnus

Package: binutils (debian/main)
Maintainer: Christopher C. Chimelis [EMAIL PROTECTED]
  74396  binutils_2.10.0.27-0.cvs2923.1(unstable): serious malfunction on 
m68k
  78562  binutils: Strip corrupts static libraries if given the wrong kind of 
pathname

Package: bock (debian/main)
Maintainer: Charles Briscoe-Smith [EMAIL PROTECTED]
  70903  bock is not installable

Package: bugs.debian.org (pseudo)
Maintainer: Darren O. Benham and others [EMAIL PROTECTED]
  69406  static BTS HTML pages not being updated

Package: cdrdao (debian/main)
Maintainer: Martin Mitchell [EMAIL PROTECTED]
  77255  cdrdao: gcdmaster doesn't work (properly or otherwise)

Package: cdrecord (debian/main)
Maintainer: Erik Andersen [EMAIL PROTECTED]
  79353  postinst checks for wrong filetype

Package: chimera (debian/non-free)
Maintainer: Debian QA Group debian-qa@lists.debian.org
  76234  [do not fix, package being removed] segmentation fault with new xlibs

Package: chpp (debian/main)
Maintainer: Darren Benham [EMAIL PROTECTED]
  65780  chpp not installable

Package: clisp (debian/main)
Maintainer: Kevin Dalley [EMAIL PROTECTED]
  62116  clisp_2000-03-06-1(unstable): m68k build error [woody]

Package: cocoon (debian/contrib)
Maintainer: Julio Maia [EMAIL PROTECTED]
  71142  ajp12: Servlet Error: java.lang.NoClassDefFoundError: 
com/jtauber/fop/Version: com/jtauber/fop/Version

Package: colorgcc (debian/main)
Maintainer: Raphael Bossek [EMAIL PROTECTED]
  75789  

[ADMIN] Unsubscription problems

2000-12-22 Thread Anand Kumria
Hi there,

A number of people have reported problems with unsubscribing from
various lists, principally debian-user and debian-devel.

We, the listmaster team, believe we have fixed the underlying
problem and you should merrily be able to [un]subscribe as needed.

Please inform us if you aren't but keep in mind that you may 
not get a response with 24 hours. Three to four days is the
norm.

Thanks,
Anand

-- 
Linux.Conf.Au   --  http://linux.conf.au/
17th - 20th January,--  Alan Cox, David Miller,
Sydney, Australia   --  Tridge, maddog and you?




Uploaded cmatrix 1.1b-3 (m68k) to erlangen

2000-12-22 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 19 Dec 2000 05:25:06 -0700
Source: cmatrix
Binary: cmatrix
Architecture: m68k
Version: 1.1b-3
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Edward Betts [EMAIL PROTECTED]
Description: 
 cmatrix- Console Matrix simulates the display from The Matrix
Closes: 79879
Changes: 
 cmatrix (1.1b-3) unstable; urgency=low
 .
   * Added Depends on xutils because postinst uses mkfontdir
 (closes: Bug#79879)
Files: 
 91c3f37e8f500e89ec97f4a44d4985b9 20330 misc optional cmatrix_1.1b-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/

iEYEARECAAYFAjpDPkIACgkQcS3JWD3FdvcNeACeL3N3wr9xXWAkaAg/TmmBZfeS
bpoAnRhqYd1FnxzrqYuMDOcZsyWGhMhG
=wywk
-END PGP SIGNATURE-




Uploaded black-box 1.4-1 (m68k) to erlangen

2000-12-22 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 12 Dec 2000 23:59:06 +0100
Source: black-box
Binary: black-box
Architecture: m68k
Version: 1.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Adrian Bunk [EMAIL PROTECTED]
Description: 
 black-box  - Find the crystals
Changes: 
 black-box (1.4-1) unstable; urgency=low
 .
   * New upstream release.
   * Changed the build dependency from libsdl-mixer-dev to
 libsdl-mixer1.1-dev.
   * Added a build dependency on libsdl-image1.1-dev.
   * Removed no longer needed build dependencies on libgpmg1-dev,
 libncurses5-dev and slang1-dev.
   * Remove all Makefile.in in the clean target of debian/rules
Files: 
 9599c3d0932ba749709133c94e58fed0 233610 games optional black-box_1.4-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/

iEYEARECAAYFAjpDPfQACgkQcS3JWD3FdvdeOQCfU7P2bpvfQSdbCXRvIZm3BbzB
BoYAn2On0OwLEWfCHC+n0w/p0UfL2O+g
=9H8T
-END PGP SIGNATURE-




Uploaded tidy 20000804-1 (m68k) to erlangen

2000-12-22 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 18 Dec 2000 04:25:16 +0100
Source: tidy
Binary: tidy
Architecture: m68k
Version: 2804-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Matej Vela [EMAIL PROTECTED]
Description: 
 tidy   - HTML syntax checker and reformatter
Closes: 79626
Changes: 
 tidy (2804-1) unstable; urgency=low
 .
   * New upstream version.  Closes: Bug#79626.
   * Conforms to Standards version 3.2.1:
 * debian/rules: Supports `debug' and `nostrip' build options.
   * debian/control: No longer suggests lynx because it doesn't seem
 relevant.  (Feel free to contact me if you disagree.)
Files: 
 a55ed1b650d4207bafd789da6cee9805 103126 web optional tidy_2804-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/

iEYEARECAAYFAjpDPbkACgkQcS3JWD3Fdvd0mwCeLR4yMo+jJdZW7QNri27H7eXx
B7MAnAsFtynmi1fR1HXXCfHzkrVpYOjT
=pSes
-END PGP SIGNATURE-




Uploaded sgrep 1.92a-4 (m68k) to erlangen

2000-12-22 Thread Debian/m68k Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 15 Dec 2000 17:22:19 -0600
Source: sgrep
Binary: sgrep
Architecture: m68k
Version: 1.92a-4
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED]
Changed-By: Jim Studt [EMAIL PROTECTED]
Description: 
 sgrep  - a tool to search a file for structured pattern
Changes: 
 sgrep (1.92a-4) unstable; urgency=low
 .
   * [EMAIL PROTECTED] takes over package.
   * Fix parser to handle backslashed quotation marks in patterns.
 (closes Bug#79495) (closes Bug#69450)
   * Add a Depends: m4.  Not strictly true, its possible to avoid it, but I
 suspect its true for nearly everyone. (close Bug#76296)
Files: 
 f17df035f906c9ba25a8e79e17d515ad 83088 text optional sgrep_1.92a-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/

iEYEARECAAYFAjpDPa8ACgkQcS3JWD3FdvfI8ACfZsLFcujYeC5qXv1VV/d4cp6Q
y/oAn39h9QbhmalD6Jg+dX8m3LoE8RoN
=Y8CB
-END PGP SIGNATURE-




Uploaded tar 1.13.18-1 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 20 Dec 2000 13:09:44 -0700
Source: tar
Binary: tar
Architecture: sparc
Version: 1.13.18-1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Bdale Garbee [EMAIL PROTECTED]
Description: 
 tar- GNU tar
Closes: 51889 57436 58171 64279
Changes: 
 tar (1.13.18-1) unstable; urgency=low
 .
   * new upstream version, closes: #57436, #51889
   * add suggestion for bzip2, closes: #64279
   * this package is pristine upstream source plus the debian/ directory, so
 there should be no issues compiling on any platform, closes: #58171
Files: 
 444d1a79d17b2b5fe1e27bf07e1fb6bf 441174 base required tar_1.13.18-1_sparc.deb

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

iD8DBQE6Q3szfNc/ZB4E7C0RAuWbAJ9j6f5ugXrqxQuo5EsopMV4OxIvegCgrlpQ
B4h94THXEeAhYXamxhm4aPQ=
=hHE9
-END PGP SIGNATURE-




Uploaded update 2.11-2 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue,  5 Dec 2000 19:01:38 -0600
Source: update
Binary: update
Architecture: sparc
Version: 2.11-2
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Roland Bauerschmidt [EMAIL PROTECTED]
Description: 
 update - daemon to periodically flush filesystem buffers.
Changes: 
 update (2.11-2) unstable; urgency=low
 .
   * Non Maintainer Upload
   * /usr/man  /usr/share/man
   * /usr/doc  /usr/share/doc
   * Maintainer Field set to Debian QA
   * dpkg-gencontrol will be invoked with -isp now
Files: 
 e2d868dc466a61500b8514966637550d 8504 base required update_2.11-2_sparc.deb

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

iD8DBQE6Q3s1fNc/ZB4E7C0RAqr1AKDHZCiS/DSDnyjBBpyZKAU8b0LeqgCeNjEF
mcGR/NT8SNeB+dunxynulVk=
=1IiW
-END PGP SIGNATURE-




Uploaded bsdmainutils 5.20001028-5 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 20 Dec 2000 21:24:32 +0100
Source: bsdmainutils
Binary: bsdmainutils
Architecture: sparc
Version: 5.20001028-5
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Marco d'Itri [EMAIL PROTECTED]
Description: 
 bsdmainutils - More utilities from FreeBSD.
Closes: 78224 78873 79128 79219
Changes: 
 bsdmainutils (5.20001028-5) unstable; urgency=low
 .
   * Removed debconf invocation in postinst (Closes: #79128).
   * Fixed some entries in calendar.music (Closes: #79219).
   * Added Japanese and Croatian holidays (Closes: #78224, #78873).
Files: 
 5ce92ed6d71e78aa160ee1c88c7ed43c 141500 utils important 
bsdmainutils_5.20001028-5_sparc.deb

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

iD8DBQE6Q3s3fNc/ZB4E7C0RArvBAJ4qNKkajIarNq/Hvv+yc3JP6zd4rgCgmWGG
99FmXodcuxQ6+Fedqf4+ygg=
=20uo
-END PGP SIGNATURE-




Uploaded kdelibs 2.1-20001218-2 (all sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 20 Dec 2000 12:22:00 -0700
Source: kdelibs
Binary: libarts-dev kdelibs3 kdelibs3-dev kdelibs3-doc libarts
Architecture: all sparc
Version: 4:2.1-20001218-2
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)
Changes: 
 kdelibs (4:2.1-20001218-2) unstable; urgency=low
 .
   * more upstream bug fixes
Files: 
 68c51a6cdf43f248f12a644b19244ded 4923382 libs optional 
kdelibs3_2.1-20001218-2_sparc.deb
 b0c6e61e3c0aa14c1a6ce99e4df34d42 562630 libs optional 
libarts_2.1-20001218-2_sparc.deb
 3cb38d923f053930b7959ff95e6021fa 69648 devel optional 
libarts-dev_2.1-20001218-2_sparc.deb
 18a8342ddd41e5d262619aa3f0061a82 579348 devel optional 
kdelibs3-dev_2.1-20001218-2_sparc.deb

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

iD8DBQE6Q5xTfNc/ZB4E7C0RAgLuAKCPP14ucMwRp7qCwEBf3gPyHyMthQCfean5
mCfYQ99FF/32vch9KnByVZA=
=HvqS
-END PGP SIGNATURE-




Uploaded libmcal 0.6-7 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC 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: sparc
Version: 0.6-7
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC 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: 
 6a7c21034563520b23df4abfbe659611 27122 devel optional libmcal0_0.6-7_sparc.deb
 d2c1c286a308081d768cd4431c3f2355 36578 devel optional 
libmcal0-dev_0.6-7_sparc.deb

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

iD8DBQE6Q59jfNc/ZB4E7C0RAmFSAKCgx7zG27r3CHrWGXRWV5WHu+LsWgCfbE4U
ArGcMCtNltuCLExrKkHdIuQ=
=U/K6
-END PGP SIGNATURE-




Uploaded qt2.2 2.2.3-3 (sparc all) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 18 Dec 2000 01:13:00 -0700
Source: qt2.2
Binary: qt2.2-doc libqt2.2-dev libqt2.2-mt-dev libqt2.2-mt libqt2.2 libqt2.2-gl
Architecture: sparc all
Version: 2:2.2.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Ivan E. Moore II [EMAIL PROTECTED]
Description: 
 libqt2.2   - Qt GUI Library (runtime version).
 libqt2.2-dev - Qt GUI development headers, static libraries
 libqt2.2-gl - Qt GUI Library (Open GL Version).
 libqt2.2-mt - Qt GUI Library (runtime threaded version).
 libqt2.2-mt-dev - Qt GUI development headers, static libraries (Threaded 
version)
 qt2.2-doc  - Tutorial and reference documentation and examples for Qt.
Closes: 79876
Changes: 
 qt2.2 (2:2.2.3-3) unstable; urgency=low
 .
   * Applying Anti-Aliasing patch
   * Adjusting Build-Depends as we now must have the latest X4
   * Adding libfreetyp6-dev to Build-Depends
   * Fixing document links (Closes: #79876)
   * New i18n patch update for qpsprinter
Files: 
 3be3954ea83791e5cd67fc76f6a61076 1981152 libs optional 
libqt2.2_2.2.3-3_sparc.deb
 afa26a6876fef11e7c40560c988712f9 1985202 libs optional 
libqt2.2-gl_2.2.3-3_sparc.deb
 e27577440ccf11adc778ed7841654734 1964434 libs optional 
libqt2.2-mt_2.2.3-3_sparc.deb
 81e00ff4ec63a523fc2c020b1edd9001 2629042 devel optional 
libqt2.2-mt-dev_2.2.3-3_sparc.deb
 3f95f823e7f7e1be376e11dd91ed1a19 3604120 devel optional 
libqt2.2-dev_2.2.3-3_sparc.deb

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

iD8DBQE6Q80qfNc/ZB4E7C0RAkx8AJ9s7D5OOLP8YqljoY4pdMe5gJqGfACgm+Kr
CnQwnltyXVzKqq0wuRU1ZMs=
=V0tZ
-END PGP SIGNATURE-




Uploaded ami 1.0.8-1 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 18 Dec 2000 18:32:23 +0900
Source: ami
Binary: ami ami-gnome
Architecture: sparc
Version: 1.0.8-1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Changwoo Ryu [EMAIL PROTECTED]
Description: 
 ami- An X input method server for Korean text input
 ami-gnome  - An X input method server for Korean text input (GNOME applet)
Changes: 
 ami (1.0.8-1) unstable; urgency=low
 .
   * New upstream release
Files: 
 f1e9651f9f7ab06ee9a84dd6b46bc072 370554 x11 optional ami_1.0.8-1_sparc.deb
 2d8277084c03c8df75075701033e13d3 169702 x11 optional 
ami-gnome_1.0.8-1_sparc.deb

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

iD8DBQE6RA2UfNc/ZB4E7C0RArVEAKCfUO0uvidTRdrjAZ7K73mZc7tBowCdE1Z2
PLR8jarHJhU6EXNk5G7MUaA=
=HSZJ
-END PGP SIGNATURE-




Uploaded kdegraphics 2.1-20001218-1 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 18 Dec 2000 23:50:00 -0700
Source: kdegraphics
Binary: kpixmap2bitmap kghostview ksnapshot kfract libminimagick-dev pixie 
kview libminimagick5
Architecture: sparc
Version: 4:2.1-20001218-1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Ivan E. Moore II [EMAIL PROTECTED]
Description: 
 kfract - fractal generator for KDE
 kghostview - PostScript viewer for KDE.
 kpixmap2bitmap - pixmap to bitmap conversion tool
 ksnapshot  - Screenshot application for KDE
 kview  - A simple image viewer/converter for KDE.
 libminimagick-dev - KDE graphics libraries (development files)
 libminimagick5 - Mini version of ImageMagick for use with KDE
 pixie  - Image Management System for KDE
Changes: 
 kdegraphics (4:2.1-20001218-1) unstable; urgency=low
 .
   * More upstream fixes
   * Adding in missing conflicts for kdegraphics
Files: 
 5b07c19dd76600e39813dfad3b5c7b18 282628 graphics optional 
kfract_2.1-20001218-1_sparc.deb
 871f169b3336d346549d79540bba4762 130416 graphics optional 
kghostview_2.1-20001218-1_sparc.deb
 a35c0492711cf2abb30fd94b79d0d99d 49574 graphics optional 
ksnapshot_2.1-20001218-1_sparc.deb
 03de8aab468239bdd4e99e3bbebb0895 37730 graphics optional 
kpixmap2bitmap_2.1-20001218-1_sparc.deb
 d0b50c9842d07908e6a84504c781396b 486036 graphics optional 
kview_2.1-20001218-1_sparc.deb
 71959fa7fafcedb22cd323c6aa54c623 256304 graphics optional 
pixie_2.1-20001218-1_sparc.deb
 1ed1c7581e7f48d0c823e887ef48e7a9 147028 libs optional 
libminimagick5_2.1-20001218-1_sparc.deb
 5f9bb941aa926d6fd44cec4ed8a17ffb 5108 devel optional 
libminimagick-dev_2.1-20001218-1_sparc.deb

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

iD8DBQE6Q+8lfNc/ZB4E7C0RAhEnAKDDXRwwjTpxu7HveYPc1Nf4jofHbACffI3z
CWfhKjdsDIxzqBkq9TJNsCk=
=75dX
-END PGP SIGNATURE-




Uploaded imagemagick 5.2.6-3 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 19 Dec 2000 10:27:58 +0900
Source: imagemagick
Binary: libmagick++5 imagemagick libmagick5-dev libmagick5 libmagick++5-dev
Architecture: sparc
Version: 1:5.2.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Ryuichi Arafune [EMAIL PROTECTED]
Description: 
 imagemagick - Image manipulation programs.
 libmagick++5 - The object-oriented C++ API to the ImageMagick library
 libmagick++5-dev - The object-oriented C++ API to the ImageMagick 
library.--developm
 libmagick5 - Image manipulation library (free version).
 libmagick5-dev - Image manipulation library (free version) -- development
Closes: 79936
Changes: 
 imagemagick (1:5.2.6-3) unstable; urgency=medium
 .
   *(libmagick5)  Conflicts imagemagick (=5.2.6-1)
   closes: #79936
Files: 
 d9a80a6d5076dc62958ec10639820e70 1129588 graphics optional 
imagemagick_5.2.6-3_sparc.deb
 dec12cfd41b7cebfdb546a9fc08e0cb3 733094 graphics optional 
libmagick5_5.2.6-3_sparc.deb
 f6e4b2b2a4aa76214f63c20749949f33 52862 graphics optional 
libmagick5-dev_5.2.6-3_sparc.deb
 ce51c13f680e0d3bd1af01c9d573e7a3 288554 graphics optional 
libmagick++5_5.2.6-3_sparc.deb
 cdaaa428eb6ef8979d10cb0c7039a5c9 47144 graphics optional 
libmagick++5-dev_5.2.6-3_sparc.deb

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

iD8DBQE6Q+jIfNc/ZB4E7C0RAvvdAKCrUq6E27EThZcG69e0efQY1IkrogCfeukg
ZpKAsg48kDkP84XICuhTkrI=
=GWPc
-END PGP SIGNATURE-




Uploaded w3c-libwww 5.3.1-3 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 18 Dec 2000 17:18:27 +0900
Source: w3c-libwww
Binary: libwww-dev libwww0
Architecture: sparc
Version: 5.3.1-3
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Takuo KITAME [EMAIL PROTECTED]
Description: 
 libwww-dev - The W3C-WWW library - development files.
 libwww0- The W3C-WWW library.
Closes: 78438
Changes: 
 w3c-libwww (5.3.1-3) unstable; urgency=low
 .
   * closes: #78438: missing build dependency
Files: 
 15807980197c7ae397085469ac9f7b3f 408612 libs optional libwww0_5.3.1-3_sparc.deb
 8661adef91d5c41ed03a8a95fbaca8e5 576930 devel optional 
libwww-dev_5.3.1-3_sparc.deb

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

iD8DBQE6Q+jEfNc/ZB4E7C0RAqBhAJ9vTU3TGLDI0SJjxL3GX53eydiFPACgyIw0
G/8Iz6lQA9ZEJLkruFrc344=
=t05k
-END PGP SIGNATURE-




Uploaded mc 4.5.51-12 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 21 Dec 2000 14:48:35 +0100
Source: mc
Binary: mc mc-common gmc
Architecture: sparc
Version: 4.5.51-12
Distribution: unstable
Urgency: high
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Martin Bialasinski [EMAIL PROTECTED]
Description: 
 gmc- Midnight Commander - A powerful file manager. - Gnome version
 mc - Midnight Commander - A powerful file manager. - normal version
 mc-common  - Common files for mc and gmc
Closes: 74905 74906 75134 77172 79639 80014 80038
Changes: 
 mc (4.5.51-12) unstable; urgency=high
 .
   * Added build-depends
   * Recompiled with latest glibc, closes: #74905, #74906, #75134, #77172
   * Added menu hints, closes: #80014, #80038
   * Fix problems with file selection code, closes: #79639
 Thanks to Alexander Viro
Files: 
 f0ac88b0bdd86cda25f907a891f0266b 419196 utils optional mc_4.5.51-12_sparc.deb
 d7b7a2ddd4d7a6b00141189fec75ae96 1569758 utils optional gmc_4.5.51-12_sparc.deb
 425f9e85ac5179aabc2924c49d11d75e 1244274 utils optional 
mc-common_4.5.51-12_sparc.deb

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

iD8DBQE6RA2QfNc/ZB4E7C0RAhVZAJwObUWMpYLgJYwHAGt+W8fojeavdwCgvVQI
lnh4j9xJ5A7DOqx7WuI5Ylw=
=5Ki4
-END PGP SIGNATURE-




Uploaded ash 0.3.7-13 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 20 Dec 2000 19:32:34 +1100
Source: ash
Binary: ash-udeb ash ash-medium
Architecture: sparc
Version: 0.3.7-13
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: Herbert Xu [EMAIL PROTECTED]
Description: 
 ash- NetBSD /bin/sh
 ash-medium - NetBSD /bin/sh with HETIO
Changes: 
 ash (0.3.7-13) unstable; urgency=low
 .
   * Renamed the udeb to ash-udeb.
Files: 
 88243cd2ae2e56ba2199cb354eaca60a 76406 shells optional ash_0.3.7-13_sparc.deb
 d99e977b346ea4e12c1dc98daee16d6f 78054 shells extra 
ash-medium_0.3.7-13_sparc.deb
 452c6c2496a054319772db8a19288d41 51512 debian-installer optional 
ash-udeb_0.3.7-13_sparc.udeb

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

iD8DBQE6Q+jHfNc/ZB4E7C0RAlmeAJ9rs4ns55aUmtaK14syap0U/HXb2ACeOwXN
pJtjiOkYxRGkfU/aqyHPxfE=
=lg9x
-END PGP SIGNATURE-




Uploaded t-code 2.1pre3-1 (sparc) to ftp-master

2000-12-22 Thread Debian/SPARC Build Daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 18 Dec 2000 15:17:53 +0900
Source: t-code
Binary: t-code
Architecture: sparc
Version: 1:2.1pre3-1
Distribution: unstable
Urgency: low
Maintainer: Debian/SPARC Build Daemon [EMAIL PROTECTED]
Changed-By: UEYAMA Rui [EMAIL PROTECTED]
Description: 
 t-code - Yet another Japanese input method
Changes: 
 t-code (1:2.1pre3-1) unstable; urgency=low
 .
   * New upstream version.
Files: 
 c040bc18a8e6bad4847f51dc99305783 870906 utils optional 
t-code_2.1pre3-1_sparc.deb

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

iD8DBQE6RA2RfNc/ZB4E7C0RAsx3AJ9tqaq2fM73FeVc+9vG2wopHdBuLwCdFSoe
TC6pifUm8FW2ewchw2jGSvU=
=CPFW
-END PGP SIGNATURE-




Re: ITP: charities.cron

2000-12-22 Thread Marcelo E. Magallon
 [EMAIL PROTECTED] writes:

  http://freshmeat.net/projects/charities.cron/
  
  I'll look at it and make a package, unless someone really objects...

 Fix the tmp security hole while you are at it, will you?

 Thanks,

--
Marcelo




looking for replacement for run (because of critical bug in

2000-12-22 Thread Marc Haber
Hi,

I am maintainer for run and console-log, and waiting for NM to
complete. Unfortunately, run has a nasty bug that causes console-log
to hang which in turn may prevent a clean shutdown. Upstream doesn't
maintain run any more (and I shouldn't have packaged it in the first
place), and isn't interested in fixing that bug. I don't have the
expertise to fix this one as it is buried deep inside interprocess
communication and vanishes under the debugger and when debugging
outputs are included, and asking for help on debian-devel multiple
times didn't show a helper.

I am now seriously thinking of having run pulled from the project
since its quality surely isn't up to Debian's standards.

To keep console-log, I need a program that can daemonize a normal
program, i.e. put it in the background, maintain a pid file unter
/var/run and optionally restart the program when it dies. Is something
that can do this in Debian at the moment, or is there maybe somebody
who can help in debugging run?

Any hints will be appreciated.

Greetings
Marc

-- 
-
Marc Haber | I don't trust Computers. They | Mailadresse im Header
Karlsruhe, Germany |  lose things.Winona Ryder | Fon: *49 721 966 32 15
Nordisch by Nature |  How to make an American Quilt | Fax: *49 721 966 31 29




RE: linkchecker lintian warnings

2000-12-22 Thread Sean 'Shaleh' Perry

On 22-Dec-2000 Bastian Kleineidam wrote:
 Hi,
 
 if you test my linkchecker .deb package:
 I just noticed that lintian gives the following warnings on my 1.2.12
 package of LinkChecker:
 W: linkchecker: postinst-does-not-set-usr-doc-link
 W: linkchecker: prerm-does-not-remove-usr-doc-link
 

a mental typo on my part in lintian.  I am uploading 1.11.13 in a few minutes. 
Should be installed during dinstall run tomorrow.

(btw it is debhelper, not debconf -- two different things)




finishing up the /usr/share/doc transition

2000-12-22 Thread Joey Hess
It has been more than 1 year since the technical committee decided how
the /usr/share/doc transition would be accomplished[1], and in that time
most packages have implementede the transition. The decision stated that
Thus, potato+1 (woody) ships with a full /usr/share/doc, and a
/usr/doc full of symlinks. and went on to detail how woody+1 (sarge?)
will begin to phase out the symlinks and how woody+2 will finally be
free of this mess. 

I'm looking forward to a day with a lot less postinst and postrm scripts
myself, so I want to make sure we don't miss the traget of full
conversion by woody's release.

There are a total of 645 packages that have not been converted[2]. There
are 16 weeks between December 31st and Aj's projected freeze date for woody.
If 40 people could do one package a week, we would be done. Or 20 people
doing two a week, or just 6 people doing one a day. In other words, it
seems acheivable, especially if we file bugs now on the undone packages,
which would probably wake a fair number of maintainers up..

What do you think?

-- 
see shy jo

[1] http://lists.debian.org/debian-ctte-9908/msg00038.html
[2] 
web/weblint
mail/signify
web/faqomatic
doc/debian-guide
x11/sfm
oldlibs/libstdc++2.8
x11/libcqcam-dev
x11/icewm-themes
otherosfs/pilot-manager
devel/lib-sax-java
math/plotmtv
net/asp
devel/pydb
base/libgdbmg1
non-free/x11/xtoolplaces
devel/et
non-free/news/trn
devel/tk8.0-ja-dev
text/ibrazilian
text/ppd-gs
utils/quickppp
math/dome
oldlibs/libg++27
non-free/sound/mp3asm
devel/librx1g-dbg
graphics/qvplay
web/htget
non-free/web/netscape-java-408
non-free/web/communicator-spellchk-408
sound/timidity-patches
oldlibs/libc5-altdbg
oldlibs/ncurses3.0
libs/libtime-modules-perl
non-free/admin/idled
oldlibs/ncurses3.4
non-free/graphics/xwpick
libs/libggi-target-vcsa
text/abc2ps
utils/lsof-2.0.36
libs/libggi2
devel/libstringlist-dev
interpreters/bwbasic
devel/cflow
x11/xpaste
non-free/devel/scheme-to-c
devel/curves
net/lambdamoo-docs
math/g2
non-free/web/chimera
sound/awe-drv
misc/dbf2mysql
devel/libliteclue-dev
net/rinetd
non-free/web/netscape-dmotif-408
libs/aalib1-dev
mail/xlbiff
libs/umich-libldap
math/tela
math/dstool
libs/libggi-target-aa
games/g5
x11/xinput
mail/splitdigest
math/seesat5
editors/emacs20
editors/jed-sl-ja
doc/tochnog-doc
x11/xserver-ggi
x11/iceconf
libs/ftplib-dev
games/netmaze
non-free/misc/xacc-smotif
interpreters/perl-debug
libs/libawe0.4
text/wfrench
devel/libgdbmg1-dev
games/xvier
misc/titrax
net/sirc
devel/rscheme-modules
libs/libsrp-dev
devel/librecode-dev
libs/libliteclue
oldlibs/librx1-altdev
oldlibs/xaw95
graphics/cdlabelgen
web/gtml
utils/cracklib2
devel/sup
base/update
text/brazilian-conjugate
libs/libggidemos
interpreters/libfile-tail-perl
doc/stl-manual
x11/swisswatch
utils/afbackup
non-free/x11/xarchie
x11/xfntmizi-ko
devel/librx1g-dev
editors/gnuserv
interpreters/perl-suid
admin/dialdcost
oldlibs/libc5-altdev
x11/fvwmconf
non-free/web/communicator-dmotif-408
utils/libxdelta2
contrib/devel/cup
editors/xcoral
net/tinyirc
graphics/vstream
utils/cpbk
otherosfs/hfsutils
games/crossfire-client-gtk
interpreters/bigloo
non-free/graphics/picon-domains
web/swish-e
doc/installmanual-de
devel/perl-byacc
net/ftp-upload
admin/lexmark7000linux
non-free/net/archie
x11/xmanpages-ja
base/dpkg-multicd
comm/seyon
non-free/x11/xsnow
devel/sml-nj
contrib/x11/metro-motif-man
otherosfs/pilot-template
libs/libggi-target-svgalib
non-free/x11/x3270
devel/libcdaudio0-dev
misc/dtaus
oldlibs/libgdbm1
oldlibs/libc5
games/mgt
non-free/devel/gbdk-dev
non-free/graphics/picon-news
web/python-bobopos
devel/libdnd1-dev
net/sendfile
libs/libggi-target-fbdev
utils/authbind
devel/fhist
admin/mingetty
text/sgml-base
devel/kernel-patch-2.0.37-raid
devel/kernel-source-2.0.36
games/xchain
sound/mikmod
libs/libgii0
non-free/web/navigator-dmotif-408
net/dhcp-dns
devel/stalin
net/rlinetd
devel/binutils-m68k-linux
net/zone-file-check
doc/libgtk-doc
sound/xmp
non-free/games/ines
comm/minicom
devel/libawe0.4-dev
utils/kbackup
non-free/graphics/picon-misc
games/empire-hub
non-free/graphics/giflib3g-dev
mail/bulkmail
net/omirr
non-free/math/gap4-tdat
utils/kbackup-doc
utils/tleds
libs/libggi-samples
interpreters/libtime-period-perl
x11/logout-button
doc/tkinfo
x11/fsviewer
utils/konfont
text/psutils
utils/lzop
admin/timeoutd
admin/printop
devel/xxgdb
misc/puzzle
mail/tkmail
non-free/misc/phylip
utils/sformat
non-free/x11/freefont
devel/m2c
graphics/libjpeg-progs
non-free/web/netscape-smotif-408
non-free/graphics/picon-usenix
contrib/web/netscape3
contrib/web/netscape4
text/par
admin/bpowerd
games/xbat
sound/cdcd
net/jail
misc/readseq
x11/rt
doc/manpages-de-dev
utils/synaptics
devel/bock
hamradio/ax25-tools
devel/kernel-patch-2.2.10-netwinder
non-free/utils/glimpse
games/spider
tex/bibview
non-free/games/gsn-curses
doc/ldp-ligs
non-free/mail/rblsmtpd-src
interpreters/gcl
doc/r5rs-doc
text/gsfonts
math/meschach
doc/guile1.3-doc
interpreters/libprpc-perl
graphics/phototk
non-free/devel/ocamltk
oldlibs/ncurses3.0-altdev

NSA's Secure Linux Distribution

2000-12-22 Thread Brent Fulgham
No doubt most of you have seen the NSA's secure linux posting
on Slashdot this morning.

Looking at:
http://www.nsa.gov/selinux/docs.html

there appears to be several utilities that have been updated
to provide enhanced security.

Should we be merging these patches into Debian, assuming they
appear to be compatible with our policy, etc.?

Thanks,

-Brent





please fix the smartlist setup on lists.debian.org

2000-12-22 Thread Brian Frederick Kimball
Donald J Bindner wrote:

 On Thu, Dec 21, 2000 at 01:44:54PM -0600, Vince Mulhollon wrote:

  The cruddy, slow, GUI based email program I use at work seems to imply your
  reply to address is [EMAIL PROTECTED] but your email came from
  [EMAIL PROTECTED]  Or maybe its the other way around.  I hate
  GUIs, they just make it harder.
 
 If this really causes the problem [...]

It doesn't.  The problem is explained in the attached email.
Someone with access to lists.debian.org needs to fix it.
[EMAIL PROTECTED] is apparently unresponsive.
---BeginMessage---
On Thu, Dec 21, 2000 at 10:53:45PM +0100, Marco Herrn wrote:
 Now I have the same problem. I tried it several times written the
 unsubscribe in the subject and in the body. But it doesn't work. Thats the
 answer I get:
 
 You have not been removed, I couldn't find your name on the list.
 What I did find were the following approximate matches:
 
 1745 [EMAIL PROTECTED]  32752 [EMAIL PROTECTED]
 822 [EMAIL PROTECTED] 18529 [EMAIL PROTECTED]
 432 [EMAIL PROTECTED]18227 [EMAIL PROTECTED]
 741 [EMAIL PROTECTED]18227 [EMAIL PROTECTED]
 623 [EMAIL PROTECTED]   17202 [EMAIL PROTECTED]
 791 [EMAIL PROTECTED]   17202 [EMAIL PROTECTED]
 1197 [EMAIL PROTECTED]  16631 [EMAIL PROTECTED]
 704 [EMAIL PROTECTED] 15460 [EMAIL PROTECTED]
 
 
 What I find really interesting is that my e-mail adress is contained 9
 times!

Because it found 9 'similar' things and wasn't sure which you were
talking about.

The left hand side is 'addresses on the list', the right hand side is 'I
think it matches this address-like-thing I found in your mail'. 
Admittedly SmartList isn't exactly clear about the meanings there, but
I've played with SmartList for years and know it well.  :)

SmartList uses some weird logic to find address-like-things in mail
headers because, well, people suck and are subscribed based on all sorts
of things other than their 'From:' header (it could be their 'reply-to'
or their 'envelope-from' or 'sender:' and even then it may or may not
include a hostname like mail.example.com instead of just example.com
handling mailing lists sucks when so many clients and users are broken).

 And this problem must be new. I have subscribed and unsubscribed several
 times already. And evertime it worked.

Someone changed the thresholds in SmartList (those funny numbers in the
3rd column).  The defaults (from ~list/.etc/rc.init on a Debian machine):

match_threshold =   30730   # for close matches to the list
medium_threshold=   28672   # for not so close matches to the list
loose_threshold =   24476   # for loosely finding your name

auto_off_threshold=   $medium_threshold # for auto-unsubscribing bouncers
off_threshold   =  $loose_threshold # for unsubscribing
reject_threshold=  $match_threshold # for rejecting subscriptions
submit_threshold= $medium_threshold # for permitting submissions

Clearly the first line in your quote above is more close (32752  30730)
than is needed in a stock install of SmartList and is the -only- one that
is above the 'off_threshold', so it should remove you just fine.  It
should have matched your address, removed it and been done here:

 if $multigram -b1 -l$off_threshold -x$listreq -x$listaddr $remov $dist \
 2/dev/null
 then
   $echo 
   $echo You have been removed from the list.

Instead it fell through to:
 else
   $echo You have not been removed, I couldn't find your name on the list.
   if test ! -z $unsub_assist -a 0 != $unsub_assist
   then
  $echo What I did find were the following approximate matches:
  $echo 
  $multigram -m -b$unsub_assist -l-32767 -x$listreq -x$listaddr $dist \
   $tmprequest
   (etc)

Note that it opens the limit (-l) on the second part to show you
everything, even things far looser than what would normally match.

The numbers shouldn't be tweaked casually, but aparrently someone did
that.   They should undo that tweaking.

-- 
CueCat decoder .signature by Larry Wall:
#!/usr/bin/perl -n
printf Serial: %s Type: %s Code: %s\n, map { tr/a-zA-Z0-9+-/ -_/; $_ = unpack
'u', chr(32 + length()*3/4) . $_; s/\0+$//; $_ ^= C x length; } /\.([^.]+)/g; 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
---End Message---


RE: finishing up the /usr/share/doc transition

2000-12-22 Thread Sean 'Shaleh' Perry
 
 There are a total of 645 packages that have not been converted[2]. There
 are 16 weeks between December 31st and Aj's projected freeze date for woody.
 If 40 people could do one package a week, we would be done. Or 20 people
 doing two a week, or just 6 people doing one a day. In other words, it
 seems acheivable, especially if we file bugs now on the undone packages,
 which would probably wake a fair number of maintainers up..
 
 What do you think?
 

other than perl packages and debconf packages, lintian tests are getting quite
close to showing policy complience.  Perhaps we should start pinging people
whose packages fail in lintian.

Either way, yes, it would be nice to kill many many postinsts.




Re: finishing up the /usr/share/doc transition

2000-12-22 Thread Roland Bauerschmidt
Joey Hess wrote:
 There are a total of 645 packages that have not been converted[2]. There
 are 16 weeks between December 31st and Aj's projected freeze date for woody.
 If 40 people could do one package a week, we would be done. Or 20 people
 doing two a week, or just 6 people doing one a day. In other words, it
 seems acheivable, especially if we file bugs now on the undone packages,
 which would probably wake a fair number of maintainers up..

I'd be glad to help. How should we proceed? Should we send patches to
the appropiate maintainers or directly upload the NMUs? Honestly, they
had enough time to tranist to /usr/share/doc.

Roland

-- 
Roland Bauerschmidt [EMAIL PROTECTED]




Re: finishing up the /usr/share/doc transition

2000-12-22 Thread Ben Collins
On Fri, Dec 22, 2000 at 01:04:26PM -0800, Joey Hess wrote:
 It has been more than 1 year since the technical committee decided how
 the /usr/share/doc transition would be accomplished[1], and in that time
 most packages have implementede the transition. The decision stated that
 Thus, potato+1 (woody) ships with a full /usr/share/doc, and a
 /usr/doc full of symlinks. and went on to detail how woody+1 (sarge?)
 will begin to phase out the symlinks and how woody+2 will finally be
 free of this mess. 
 
 I'm looking forward to a day with a lot less postinst and postrm scripts
 myself, so I want to make sure we don't miss the traget of full
 conversion by woody's release.
 
 There are a total of 645 packages that have not been converted[2]. There
 are 16 weeks between December 31st and Aj's projected freeze date for woody.
 If 40 people could do one package a week, we would be done. Or 20 people
 doing two a week, or just 6 people doing one a day. In other words, it
 seems acheivable, especially if we file bugs now on the undone packages,
 which would probably wake a fair number of maintainers up..
 
 What do you think?

I think we need to reevaluate this decision based on the fact that the bug
in dpkg that forced this implementation (as opposed to a clean /usr/doc
symlink to share/doc) has been gone for awhile now (the potato dpkg is
fixed).

For those that do not remember, the bug in dpkg would have caused doc
files to go missing if /usr/doc was a symlink to share/doc, once a package
was upgraded from the latter to the former (docs in /usr/share/doc).

That is no longer the case, so I would hope that our efforts would be
better spent writing a transition script to handle the move (moving things
from /usr/doc to /usr/share/doc, if needed, and removing symlinks). Note
that I have a /usr/doc - share/doc symlink on all my systems right now
(note, auric is also setup this way, running potato, without any errors or
missing files).

Can we do this and avoid further hacking around with this? Moving to
/usr/share/doc in woody is possible. The tools handle it, packages
that support the symlink in postinst/prerm already magically work (IOW,
any policy abiding app supports it), packages that use the old /usr/doc
work with it, and new packages that only use /usr/share/doc will work with
it.

We just need a script/program that sanely does this transition, then
creates the /usr/doc - share/doc symlink.

Ben

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




Re: finishing up the /usr/share/doc transition

2000-12-22 Thread Sean 'Shaleh' Perry
 
 I'd be glad to help. How should we proceed? Should we send patches to
 the appropiate maintainers or directly upload the NMUs? Honestly, they
 had enough time to tranist to /usr/share/doc.
 

send patch, wait some period of time (maybe a week?) then warn of NMU, then NMU.




[ADMIN] Unsubscription problems

2000-12-22 Thread Anand Kumria
Hi there,

A number of people have reported problems with unsubscribing from
various lists, principally debian-user and debian-devel.

We, the listmaster team, believe we have fixed the underlying
problem and you should merrily be able to [un]subscribe as needed.

Please inform us if you aren't but keep in mind that you may 
not get a response with 24 hours. Three to four days is the
norm.

Thanks,
Anand

-- 
Linux.Conf.Au   --  http://linux.conf.au/
17th - 20th January,--  Alan Cox, David Miller,
Sydney, Australia   --  Tridge, maddog and you?




Re: NSA's Secure Linux Distribution

2000-12-22 Thread Jacob Kuntz
from the secret journal of Brent Fulgham ([EMAIL PROTECTED]):
 No doubt most of you have seen the NSA's secure linux posting
 on Slashdot this morning.
 
 Looking at:
 http://www.nsa.gov/selinux/docs.html
 
 there appears to be several utilities that have been updated
 to provide enhanced security.
 
 Should we be merging these patches into Debian, assuming they
 appear to be compatible with our policy, etc.?
 

unless we have a policy against security, it should be fine. :) it's all
gpl.

-- 
jacob kuntz
[EMAIL PROTECTED]
underworld.net/~jake




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread Erik Steffl
Daniel Stone wrote:
 
  On Fri, Dec 22, 2000 at 01:06:53AM +0100, Robert van der Meulen wrote:
   Quoting Bas Zoetekouw ([EMAIL PROTECTED]):
 Now you can boost the reliability of ordinary Windows 3.x, 95 and 98 
 to
 nearly the level of Windows NT or 2000, Microsoft's professional and
 industrial
 version of Windows.
Hmm, the debian lists get quite a lot of spam lately. Is there anything
that can be done about this?
   Close debian-devel for posting by non-subscribers, ask for volunteers who
   would like to 'moderate' debian-devel, and have them look at the rejected
   messages and accept them if on-topic.
   Every mailing list i know has these functions, I was also wondering why we
   weren't using such a system ;)
 
  Every mailing list software might have these functions, but none of the
  open project mailing lists that I know of do this. linux-kernel, gcc,
  glibc, openldap.
 
  There's a very good reason for this. Not the least of which is the effort
  in keeping it up. Secondly, not all developers use the same email
  accounts. I, for example, have three email accounts from which I post to
  Debian-devel.
 
 Solution: Pick one you like, stick to it, even if it means having
 forwarders, having to SSH in, faking senders, whatever.

  anot her solution is the one I've seen svlug.org using: you can
subscribe without email being sent to you (they use mailman, IIRC). So
you can subscribe all your addresses and sent email to list from all of
them but receive email from list only in one account.

erik




Re: wnpp bug reports

2000-12-22 Thread Josip Rodin
On Fri, Dec 22, 2000 at 12:58:54PM -0500, Bob Hilliard wrote:
  Is there any way to submit an ITP bug on WNPP, so that the bug
 number appears in the copy to -devel?

Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields.

-- 
Digital Electronic Being Intended for Assassination and Nullification




Re: NSA's Secure Linux Distribution

2000-12-22 Thread Miquel van Smoorenburg
In article [EMAIL PROTECTED],
Brent Fulgham  [EMAIL PROTECTED] wrote:
No doubt most of you have seen the NSA's secure linux posting
on Slashdot this morning.

Looking at:
http://www.nsa.gov/selinux/docs.html

there appears to be several utilities that have been updated
to provide enhanced security.

Ofcourse it's not just the utilities - they rely on the special NSA
Linux kernel.

Packaging the NSA versions of the utilities is only useful if
Debian was also using the NSA Linux kernel.

The NSA Linux kernel is based on 2.2 (while 2.4 is due out soon),
it deviates from the standard kernel in a big way, and it is
higly experimental.

The kernel people are going to look at the NSA kernel, and might
merge the security features in 2.6 or 3.0, then again they might
not merge them at all.

So I guess it's not an issue. Unless you want to start a
seperate destribution, based on Debian: Debian/GNU/NSA Linux

Mike.




Re: NSA's Secure Linux Distribution

2000-12-22 Thread Buddha Buck
At 04:38 PM 12-22-2000 -0500, Jacob Kuntz wrote:
from the secret journal of Brent Fulgham ([EMAIL PROTECTED]):
 No doubt most of you have seen the NSA's secure linux posting
 on Slashdot this morning.

 Looking at:
 http://www.nsa.gov/selinux/docs.html

 there appears to be several utilities that have been updated
 to provide enhanced security.

 Should we be merging these patches into Debian, assuming they
 appear to be compatible with our policy, etc.?

unless we have a policy against security, it should be fine. :) it's all
gpl.
I'd take a close look at what they did before deciding to integrate their 
patches in.

The goals of the NSA in doing this may not be suitable for Debian.  I'm not 
talking about paranoia concerning the NSA putting back-doors into 
everything; I'm taking as given that they are being honest and upfront 
about what they are doing and why.  But...

Here is a quote from their overview page 
(http://www.nsa.gov/selinux/index.html):

Security-enhanced Linux is not an attempt to correct any flaws that may 
currently exist in Linux. Instead, it is simply an example of how 
mandatory access controls that can confine the actions of any process, 
including a superuser process, can be added into Linux. The focus of this 
work has not been on system assurance or other security features such as 
security auditing, although these elements are also important for a secure 
system.
In addition, while they provide 15 new or modified system utilities, they 
also provide 36 new system-calls, and require a custom kernel to handle the 
system.

On their to-do list are the following items:
Port the kernel patches to the latest 2.2 kernel
Port the kernel patches to the 2.4.0 kernel
Port the utility patches to the latest versions of the base utilities
so I'm not even sure we -could- apply their patches, even if we wanted to.

--
jacob kuntz
[EMAIL PROTECTED]
underworld.net/~jake
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2000-12-22 Thread Stephen Zander
 Piotr == Piotr Roszatycki [EMAIL PROTECTED] writes:
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.

-- 
Stephen

If I claimed I was emporer just cause some moistened bint lobbed a
scimitar at me they'd put me away




Re: NSA's Secure Linux Distribution

2000-12-22 Thread Jacob Kuntz
from the secret journal of Buddha Buck ([EMAIL PROTECTED]):
 unless we have a policy against security, it should be fine. :) it's all
 gpl.

i posted that before i hit the download page.

 Security-enhanced Linux is not an attempt to correct any flaws that may 
 currently exist in Linux. Instead, it is simply an example of how 
 mandatory access controls that can confine the actions of any process, 
 including a superuser process, can be added into Linux. The focus of this 
 work has not been on system assurance or other security features such as 
 security auditing, although these elements are also important for a secure 
 system.
 
 In addition, while they provide 15 new or modified system utilities, they 
 also provide 36 new system-calls, and require a custom kernel to handle the 
 system.
 
 On their to-do list are the following items:
 
 Port the kernel patches to the latest 2.2 kernel
 Port the kernel patches to the 2.4.0 kernel
 Port the utility patches to the latest versions of the base utilities
 
 so I'm not even sure we -could- apply their patches, even if we wanted to.
 

you have a point. but what about seperate packages for the modified ones, or
even wrapper scripts like we do with dhcpd? that sounds somewhat ugly,
adding quite a bit of bulk to the default install since even tar and procps
get patched.

-- 
jacob kuntz
[EMAIL PROTECTED]
underworld.net/~jake




the experimental mutt package

2000-12-22 Thread Marco d'Itri
Some days ago I uploaded mutt 1.3.12 to experimental.
Please test it, because if people will not complain I'm going to upload
it to woody.

README.Debian says:

~~
~ NOTES ABOUT THE EXPERIMENTAL PACKAGE
~
~ There is no support for building dinamically loadable crypto modules.
~ There is no GSSAPI support.
~ If it works, great.
~ If it breaks, you keep bot pieces (but send a bug report).
~
~~

-- 
ciao,
Marco




Re: NSA's Secure Linux Distribution

2000-12-22 Thread Britton

Pardon my paranoia, but even if it was worth making all the changes they
are talking about (which are pretty extensive), I'd want to see anything
coming from the NSA audited carefully before being included.

Britton Kerin
__
GNU GPL: The Source will be with you... always.

On Fri, 22 Dec 2000, Jacob Kuntz wrote:

 from the secret journal of Brent Fulgham ([EMAIL PROTECTED]):
  No doubt most of you have seen the NSA's secure linux posting
  on Slashdot this morning.
 
  Looking at:
  http://www.nsa.gov/selinux/docs.html
 
  there appears to be several utilities that have been updated
  to provide enhanced security.
 
  Should we be merging these patches into Debian, assuming they
  appear to be compatible with our policy, etc.?
 

 unless we have a policy against security, it should be fine. :) it's all
 gpl.

 --
 jacob kuntz
 [EMAIL PROTECTED]
 underworld.net/~jake




Re: NSA's Secure Linux Distribution

2000-12-22 Thread Jacob Kuntz
from the secret journal of Britton ([EMAIL PROTECTED]):
 
 Pardon my paranoia, but even if it was worth making all the changes they
 are talking about (which are pretty extensive), I'd want to see anything
 coming from the NSA audited carefully before being included.
 
 Britton Kerin

you're pardoned. i'm sure we're all a little wary of No Such Agency right
now, with carnivore and all.

but what fact are these fears based in? would the nsa really plop a backdoor
in an opensource project, hoping it missed and accepted with the rest of the
code? i doubt it. their whole (advertised) motive was to protect against the
possibility of Trusted (AIX|Solaris|PalmOS|whatever closed os) going belly
up.

of course i plan on running this monster on a throwaway machine before i
make form any real opinions.

-- 
jacob kuntz
[EMAIL PROTECTED]
underworld.net/~jake




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread esoR ocsirF
On Sat, Dec 23, 2000 at 01:39:45AM +1100, Daniel Stone wrote:
  On Fri, Dec 22, 2000 at 12:43:03AM +0100, Bas Zoetekouw wrote:
   Hmm, the debian lists get quite a lot of spam lately. Is there anything
   that can be done about this?
  
 
 Pardon my French, but this is a fucking stupid idea. Did you ever stop to
 think that there are only a tiny handful of mailers that even think about
 supporting this? And in a half-decent way? If this is implemented in -devel,
 or any Debian lists, it will be one of the, if not the, most stupid
 decisions made.
 

A possability might be to have a signature key. This is not
significantly different than the extra header idea but it would allow
*any* MUA to work with it. Could be something like a GPG fingerprint or
whatever. Just a thought.

-- 
Frisco Rose By any other name, I would smell the same
E.O.U. Stud. [EMAIL PROTECTED] [EMAIL PROTECTED]
Physics  Mathematics  Computer Science

INTACT Director




Bug#80343: general: Lack of policy on which files should be owned by which user

2000-12-22 Thread KORN Andras
Package: general
Version: 20001222
Severity: important

Hi,

I feel that there exists a general confusion among some Debian developers as
to what user ids such as 'nobody' should be used for. I suggest that the
policy be updated with relevant advice.

As I see it, 'nobody' should be a user that owns no files and has no
privileges; thus, if a service running as 'nobody' were to be compromised,
the attacker wouldn't gain the ability to change any files.

However, some packages seem to contain or create files owned by 'nobody' or
the 'nogroup' group (for example, the buffers of distributed-net-pproxy are
owned by nobody.nogroup).

www-data is another user that shouldn't own files (so that breaking into the
webserver won't allow the attacker to replace files on the system); sadly,
Roxen needs to own its own configuration files for the web-based
configuration interface to work.

'daemon' is another user that is, in my opinion, often abused. For example,
portmap, the 'at' daemon, lprng and the distributed-net client all run under
the 'daemon' uid. There is no need for these to be able to affect each other
in any way (e.g. send each other signals). All of these should probably run
under their own (dynamically allocated) user id.

A quick search for files owned by 'daemon' turned up the following:

/var/state/mon
/var/lib/distributed-net
/var/lib/distributed-net/distributed-net.ini
/var/lib/distributed-net/distributed-net
/var/lib/distributed-net/buff-out.rc5
/var/lib/distributed-net/buff-in.rc5
/var/log/mon
/var/run/lprng/lpd.printer
/var/run/mon
/var/spool/cron/atjobs
/var/spool/cron/atjobs/.SEQ
/var/spool/cron/atspool
and any number of files and directories under /var/spool/lpd/.

Obviously, the portmapper has no need to write to any of these; however, if
an attacker were to compromise it and gain its privileges, they could break
unrelated software (like lprng or distributed-net) on the system, perhaps
even leading to privilege escalation.

Imho 'daemon' is a user that exists mainly for historical reasons, reminding
us of times when security wasn't as much an issue as it is now.

Basically, if two processes have no need to ever send each other signals or
write to the same files, they probably shouldn't run under the same user id
(except if they need to run as root, of course).

Now that capabilities exist in the Linux kernel, Debian packages should
probably make use of them more often; perhaps even fewer programs would need
to run as root do their work.

Most packages that contain programs run 'at system level' ('daemons') should
probably create their own user id that the program can run under (luckily,
many packages already do this).

I file this report as 'important' because the way things are now, a
vulnerability in an unprivileged (non-root) service can be used to
compromise other unrelated services running under the same userid.

Regards,

Andrew

-- 
Andrew Korn (Korn Andras) [EMAIL PROTECTED]
 Finger [EMAIL PROTECTED] for pgp key. QOTD:
Dogs come when you call. Cats have answering machines.

-- System Information
Debian Release: woody
Kernel Version: Linux utopia 2.4.0-test11 #15 Mon Dec 4 15:10:19 CET 2000 i686 
unknown





Re: wnpp bug reports

2000-12-22 Thread Bob Hilliard
Josip Rodin [EMAIL PROTECTED] writes:

 
 On Fri, Dec 22, 2000 at 12:58:54PM -0500, Bob Hilliard wrote:
   Is there any way to submit an ITP bug on WNPP, so that the bug
  number appears in the copy to -devel?
 
 Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields.

 When I have done this, the report shows up on -devel the same as
I submitted it - the Bug Number doesn't appear.

-- 
   _
  |_)  _  |_   Robert D. Hilliard  [EMAIL PROTECTED]
  |_) (_) |_)  1294 S.W. Seagull Way   [EMAIL PROTECTED]
   Palm City, FL  USA  GPG Key ID: 390D6559 
   PGP Key ID: A8E40EB9





Re: NSA's Secure Linux Distribution

2000-12-22 Thread Britton

On Fri, 22 Dec 2000, Jacob Kuntz wrote:

 from the secret journal of Britton ([EMAIL PROTECTED]):
 
  Pardon my paranoia, but even if it was worth making all the changes they
  are talking about (which are pretty extensive), I'd want to see anything
  coming from the NSA audited carefully before being included.
 
  Britton Kerin

 you're pardoned. i'm sure we're all a little wary of No Such Agency right
 now, with carnivore and all.

 but what fact are these fears based in? would the nsa really plop a backdoor

It wouldn't be paranoia if it had a basis in fact :)

 in an opensource project, hoping it missed and accepted with the rest of the
 code? i doubt it. their whole (advertised) motive was to protect against the
 possibility of Trusted (AIX|Solaris|PalmOS|whatever closed os) going belly
 up.

Agreed.  But past things like the weird unexplained DES s-boxes show that
NSA is at least not afraid of doing things that are blatantly suspicious.
And a lot of insiders there have the attitude that no one outside a
project ever really looks closely enough at things to detect problems
unless something is noticably broken.  With Linux and open source that
assumption is probably more wrong than ever before, but still with a grain
of truth in it.

 of course i plan on running this monster on a throwaway machine before i
 make form any real opinions.

Good thought.  I guess if it seems to work we could offer an alternate
kernel package, and perhaps one huge package with all their patched
utilities or something?  Trouble is a lot of them are kind of buried in
other debian packages and would not be easy to substitute for.

 jacob kuntz
 [EMAIL PROTECTED]
 underworld.net/~jake

Britton




Subject: http://www.lists and 5000 best domain names free to register

2000-12-22 Thread trademark
Dear debian-devel@lists.debian.org

We inform you in priority as domain
specialist for promoting and affiliation,
the ccTLD (Top Level Domain).cf just opens for public sales.

http://www.lists.cf
http://www.business.cf
http://www.internet.cf are certainly available

Do not loose time and money, register immediately
the best names for you, your company and your trademarks.

More we pay you 8 $US per domain name definitively registered through your 
promotion or your affiliates.

To take more information and make really money go to: 
http://members.tripod.de/bestdomain
(you will get a confidential access to get your stats every day)


Yours faithfully
Registration Department

If you wish to be removed from our information service: 
[EMAIL PROTECTED] 

PRIVACY POLICY: 

IF YOU DO NOT WANT TO RECEIVE FUTURE COMMUNICATIONS FROM THIS EMAIL 
ADDRESS, PLEASE COLLABORATE WITH US BY NOT PRESSURING THE SERVERS OR 
PROVIDERS.IN THIS WAY EVERYONE THAT DESIRES CAN BE DROPPED OFF THE LIST.




Close list

2000-12-22 Thread Carl B. Constantine
I'm getting tired of getting spam through mail lists I subscribe to that
have an open post policy. Can we please close the debian-devel and other
such lists that should be closed. I don't think trademark domains is doing
anything for debian development.

-- 
Carl B. Constantine ([EMAIL PROTECTED])Phone: 250.953.2650
Open Source Solutions Inc.   Fax: 250.953.2659
4252 Commerce Circle, Victoria, BC.  V8Z 4M2  http://www.os-s.com/

 I feel like a genocidal maniac when emacs asks me if I want
   to kill 10789 characters.




Re: Close list

2000-12-22 Thread Joey Hess
Carl B. Constantine wrote:
 I'm getting tired of getting spam through mail lists I subscribe to that
 have an open post policy. Can we please close the debian-devel and other
 such lists that should be closed. I don't think trademark domains is doing
 anything for debian development.

This is ill-advised proposal #403021; check the list archives for 
flamewar #403021b; the conclusion is always: no.

-- 
see shy jo




Re: Close list

2000-12-22 Thread David N. Welton
Carl B. Constantine [EMAIL PROTECTED] writes:

 I'm getting tired of getting spam through mail lists I subscribe to
 that have an open post policy. Can we please close the debian-devel
 and other such lists that should be closed. I don't think
 trademark domains is doing anything for debian development.

Before you go starting another flame war, did you go back and look
through the list history for 'closed list' et similae?  Maybe you
could do that, and respond to the concerns raised in *those* flame
wars...

-- 
David N. Welton
 Personal:   http://www.efn.org/~davidw/  
Free Software:   http://people.debian.org/~davidw/
   Apache Tcl:   http://tcl.apache.org




Re: looking for replacement for run (because of critical bug in

2000-12-22 Thread Erik Steffl
Marc Haber wrote:
 
 Hi,
 
 I am maintainer for run and console-log, and waiting for NM to
 complete. Unfortunately, run has a nasty bug that causes console-log
 to hang which in turn may prevent a clean shutdown. Upstream doesn't
 maintain run any more (and I shouldn't have packaged it in the first
 place), and isn't interested in fixing that bug. I don't have the
 expertise to fix this one as it is buried deep inside interprocess
 communication and vanishes under the debugger and when debugging
 outputs are included, and asking for help on debian-devel multiple
 times didn't show a helper.
 
 I am now seriously thinking of having run pulled from the project
 since its quality surely isn't up to Debian's standards.
 
 To keep console-log, I need a program that can daemonize a normal
 program, i.e. put it in the background, maintain a pid file unter
 /var/run and optionally restart the program when it dies. Is something
 that can do this in Debian at the moment, or is there maybe somebody
 who can help in debugging run?

  what about that start-stop-daemon or something like that used to start
and stop daemons and various services, check the /etc/init.d scripts
what/how they use, I do not have debian handy at the moment but I think
it might do what you want.

erik




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread Jacob Kuntz
from the secret journal of esoR ocsirF ([EMAIL PROTECTED]):
 
 A possability might be to have a signature key. This is not
 significantly different than the extra header idea but it would allow
 *any* MUA to work with it. Could be something like a GPG fingerprint or
 whatever. Just a thought.
 

first thoughtungh. overhead./

-- 
Jacob Kuntz
underworld.net/~jake
[EMAIL PROTECTED]

Strategery -- George W. Bush
Lockbox -- Al Gore




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread Daniel Stone
 from the secret journal of Ben Collins ([EMAIL PROTECTED]):
  Solution: just deal with the few spam we get so as not to hinder real
  discussions.
  
  Ben
 
 amen.

OK, if you can do that, I'm absolutely thrilled to do it, PLEASE make
debian-devel spam-free. But the problem is that you CAN'T. Because there's
too much of it. What are we going to do, kill everything with more than 2
exclamation marks? Come on, don't tell me you're _that_ naive.




Re: wnpp bug reports

2000-12-22 Thread Mark Brown
On Fri, Dec 22, 2000 at 06:03:28PM -0500, Bob Hilliard wrote:
 Josip Rodin [EMAIL PROTECTED] writes:

  Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields.

  When I have done this, the report shows up on -devel the same as
 I submitted it - the Bug Number doesn't appear.

If you CC it it will - that's just a regular mailing list posting.  If
you use X-Debbugs-Cc it will go through the BTS first.

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


pgpEPFtochrQo.pgp
Description: PGP signature


Re: testing to be implemented on ftp-master

2000-12-22 Thread Joey Hess
Adrian Bunk wrote:
 BTW: Are there any rules when a developer has to use which urgency or can
  he if he wants to simply do all his uploads with the urgency set to
  high? I read the Packaging Manual and I did only find a very vague
  how important it is to upgrade to this version from previous ones
  that can be interpreted in many ways.

The urgency field really hasn't been used at all. Now at least two
things are using it:

1. Testing
2. Apt-listchanges (sorts by urgency)

If I see a developer consitently and unnecessarily using  normal urgency
in apt-listchanges when I upgrade, I think I would eventually get sick of
it and complain to them.

-- 
see shy jo




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread safemode
Daniel Stone wrote:

  from the secret journal of Ben Collins ([EMAIL PROTECTED]):
   Solution: just deal with the few spam we get so as not to hinder real
   discussions.
  
   Ben
 
  amen.

 OK, if you can do that, I'm absolutely thrilled to do it, PLEASE make
 debian-devel spam-free. But the problem is that you CAN'T. Because there's
 too much of it. What are we going to do, kill everything with more than 2
 exclamation marks? Come on, don't tell me you're _that_ naive.


He said deal with it and ignore it, not anything from your quote suggests that
he said something about stopping it.




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread Ben Collins
On Sat, Dec 23, 2000 at 12:00:26PM +1100, Daniel Stone wrote:
  from the secret journal of Ben Collins ([EMAIL PROTECTED]):
   Solution: just deal with the few spam we get so as not to hinder real
   discussions.
   
   Ben
  
  amen.
 
 OK, if you can do that, I'm absolutely thrilled to do it, PLEASE make
 debian-devel spam-free. But the problem is that you CAN'T. Because there's
 too much of it. What are we going to do, kill everything with more than 2
 exclamation marks? Come on, don't tell me you're _that_ naive.

By deal with it I mean, get over it. It's only a few spam, you can hit
the delete key as easily as anything else.

BTW, I'm on a 28.8, and I get over 1000 emails a day from all the lists I
am sub'd to. So I do see a lot of spam, even beyond Debian's lists. If I
can ignore it, so can everyone else, IMNHO.

Ben

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




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread Robert van der Meulen
Quoting Ben Collins ([EMAIL PROTECTED]):
 BTW, I'm on a 28.8, and I get over 1000 emails a day from all the lists I
 am sub'd to. So I do see a lot of spam, even beyond Debian's lists. If I
 can ignore it, so can everyone else, IMNHO.
Ignoring spam has made the internet the spam-ridden place it is right now.
As long as people do not do anything about it, spam will be as commonplace
and as 'ignorable' as spam by snailmail.
I do not like that, and lots of people don't. Apart from the annoyances,
spammers almost regularly clobber up mailservers, network links, and
are being _very_ intrusive.
Spam is not an ignorable problem, and every spam-account i can manage to get
killed, will get killed.
If your opinion is that we shouldn't actively try to bring down the spam to
a minimum, and just delete it - that's your opinion, but definately not
mine, and not a lot of others' too ;)

Greets,
Robert

-- 
|  [EMAIL PROTECTED] - Cistron Internet Services - www.cistron.nl|  
|  php3/c/perl/html/c++/sed/awk/linux/sql/cgi/security |
| My statements are mine, and not necessarily cistron's.   |
  If you want divine justice, die. -- Nick Seldon




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread Ben Collins
On Sat, Dec 23, 2000 at 02:21:46AM +0100, Robert van der Meulen wrote:
 Quoting Ben Collins ([EMAIL PROTECTED]):
  BTW, I'm on a 28.8, and I get over 1000 emails a day from all the lists I
  am sub'd to. So I do see a lot of spam, even beyond Debian's lists. If I
  can ignore it, so can everyone else, IMNHO.
 Ignoring spam has made the internet the spam-ridden place it is right now.
 As long as people do not do anything about it, spam will be as commonplace
 and as 'ignorable' as spam by snailmail.
 I do not like that, and lots of people don't. Apart from the annoyances,
 spammers almost regularly clobber up mailservers, network links, and
 are being _very_ intrusive.
 Spam is not an ignorable problem, and every spam-account i can manage to get
 killed, will get killed.
 If your opinion is that we shouldn't actively try to bring down the spam to
 a minimum, and just delete it - that's your opinion, but definately not
 mine, and not a lot of others' too ;)

My opinion is that trying to block spam is a losing battle. Trying to
attack it at it's roots by closing open relays, filing suit on people
breaking the law, etc..is the right thing.

It's like arresting drug users, as opposed to arresting the drug
smugglers. You should kill the root, not the offspring.

Ben

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




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread John Galt

You going to send them the bill then?  At the bottom off the mailinglist
subscription page:

http://www.debian.org/MailingLists/subscribe

is the mailinglist policy.  Basically, the policy says either pay us
$1,000 up front or $1,999 after.  Martin (Joey, whatever you prefer...),
Remco, Alexander, Anand (the listed mailing lists administration
members): I think that you have some volunteers to send dunning notices
within this thread (myself included).  If you already are, could you post
a summary of your actions and results on a periodic basis to somewhere
that we can refer the close the list thread starters to?

On Sat, 23 Dec 2000, Robert van der Meulen wrote:

 Quoting Ben Collins ([EMAIL PROTECTED]):
  BTW, I'm on a 28.8, and I get over 1000 emails a day from all the lists I
  am sub'd to. So I do see a lot of spam, even beyond Debian's lists. If I
  can ignore it, so can everyone else, IMNHO.
 Ignoring spam has made the internet the spam-ridden place it is right now.
 As long as people do not do anything about it, spam will be as commonplace
 and as 'ignorable' as spam by snailmail.
 I do not like that, and lots of people don't. Apart from the annoyances,
 spammers almost regularly clobber up mailservers, network links, and
 are being _very_ intrusive.
 Spam is not an ignorable problem, and every spam-account i can manage to get
 killed, will get killed.
 If your opinion is that we shouldn't actively try to bring down the spam to
 a minimum, and just delete it - that's your opinion, but definately not
 mine, and not a lot of others' too ;)
 
 Greets,
   Robert
 
 

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




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread John Galt

I was kind of feeling sorry about including you as a CC in the last
post--partial oversight, partial personal policy (I never quite know how
to deal with tertiary CCs: I generally detest people who adulterate a
message they're replying to, but I also think that responsibility for
replies stops about third-hand).  This eases my conscience
somewhat: Sending bills and dunning letters IAW a pre-existing policy
sounds like it fits your kill the root, not the offspring ethos...  So
are you a part of the problem in this case or willing to be part of the
solution?  

On Fri, 22 Dec 2000, Ben Collins wrote:

 On Sat, Dec 23, 2000 at 02:21:46AM +0100, Robert van der Meulen wrote:
  Quoting Ben Collins ([EMAIL PROTECTED]):
   BTW, I'm on a 28.8, and I get over 1000 emails a day from all the lists I
   am sub'd to. So I do see a lot of spam, even beyond Debian's lists. If I
   can ignore it, so can everyone else, IMNHO.
  Ignoring spam has made the internet the spam-ridden place it is right now.
  As long as people do not do anything about it, spam will be as commonplace
  and as 'ignorable' as spam by snailmail.
  I do not like that, and lots of people don't. Apart from the annoyances,
  spammers almost regularly clobber up mailservers, network links, and
  are being _very_ intrusive.
  Spam is not an ignorable problem, and every spam-account i can manage to get
  killed, will get killed.
  If your opinion is that we shouldn't actively try to bring down the spam to
  a minimum, and just delete it - that's your opinion, but definately not
  mine, and not a lot of others' too ;)
 
 My opinion is that trying to block spam is a losing battle. Trying to
 attack it at it's roots by closing open relays, filing suit on people
 breaking the law, etc..is the right thing.
 
 It's like arresting drug users, as opposed to arresting the drug
 smugglers. You should kill the root, not the offspring.
 
 Ben
 
 

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




update excuses.. how to read them

2000-12-22 Thread Bernd Eckenfels
Hello,

if i take for example:

http://ftp-master.debian.org/~ajt/update_excuses.html

adns 1.0-3 (low) 
 Maintainer: Bernd Eckenfels [EMAIL PROTECTED] 
 adns is 27 days out of date! 
 out of date on alpha: libadns0, libadns0-dev (from 0.8-2) 
 out of date on i386: libadns0, libadns0-dev (from 0.8-2) 
 there are up to date bins in i386 also 
 out of date on m68k: libadns0, libadns0-dev (from 0.8-2) 
 there are up to date bins in m68k also 
 out of date on powerpc: libadns0, libadns0-dev (from 0.8-2) 
 there are up to date bins in powerpc also 
 out of date on sparc: libadns0, libadns0-dev (from 0.8-2) 
 there are up to date bins in sparc also 
 not considered 

Does that mean that it is not considered because on alpha there are no
up-to-date bins?

The line out of date can be ignored as long as there is also a line there
are up to date bins in * also?

Is there a build-info for all the other platforms, too? How can I see why
the alpha failed to build my package?

The 
 valid candidate (will be installed unless it's dependent upon other
 buggy pkgs)

is printed, even if the package is already installed in woody?

Greetings
Bernd
-- 
  (OO)  -- [EMAIL PROTECTED] --
 ( .. )  [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/
  o--o *plush*  2048/93600EFD  [EMAIL PROTECTED]  +497257930613  BE5-RIPE
(OO)  When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!




Re: Boost Windows Reliability!!!!!

2000-12-22 Thread Daniel Stone
 On Sat, Dec 23, 2000 at 02:21:46AM +0100, Robert van der Meulen wrote:
  Quoting Ben Collins ([EMAIL PROTECTED]):
   BTW, I'm on a 28.8, and I get over 1000 emails a day from all the lists I
   am sub'd to. So I do see a lot of spam, even beyond Debian's lists. If I
   can ignore it, so can everyone else, IMNHO.

I can ignore it, too. It was my fault for misreading; I stand corrected.

  Ignoring spam has made the internet the spam-ridden place it is right now.
  As long as people do not do anything about it, spam will be as commonplace
  and as 'ignorable' as spam by snailmail.
  I do not like that, and lots of people don't. Apart from the annoyances,
  spammers almost regularly clobber up mailservers, network links, and
  are being _very_ intrusive.
  Spam is not an ignorable problem, and every spam-account i can manage to get
  killed, will get killed.
  If your opinion is that we shouldn't actively try to bring down the spam to
  a minimum, and just delete it - that's your opinion, but definately not
  mine, and not a lot of others' too ;)
 
 My opinion is that trying to block spam is a losing battle. Trying to
 attack it at it's roots by closing open relays, filing suit on people
 breaking the law, etc..is the right thing.
 
 It's like arresting drug users, as opposed to arresting the drug
 smugglers. You should kill the root, not the offspring.

Which isn't to say you leave the offspring alone. You slay them, too. You
have to do both - not just one or the other. EOT for me.




Re: Close list

2000-12-22 Thread Miles Bader
Carl B. Constantine [EMAIL PROTECTED] writes:
 I'm getting tired of getting spam through mail lists I subscribe to
 that have an open post policy.  Can we please close the debian-devel
 and other such lists that should be closed.  I don't think trademark
 domains is doing anything for debian development.

No, lets not.

Right now I'm subscribed to debian-devel, but often in the past I've
read it occasionally in the archives, and sent mail as I thought
appropriate.  I know there are other people who do this.

The fact is that the spam level on debian-devel right now is in the
noise (it's certainly exceeded by the volume of pointless and/or
downright stupid posts).

-Miles 
-- 
Love is a snowmobile racing across the tundra.  Suddenly it flips over,
pinning you underneath.  At night the ice weasels come.  --Nietzsche




Re: finishing up the /usr/share/doc transition

2000-12-22 Thread Roland Bauerschmidt
On Fri, Dec 22, 2000 at 01:04:26PM -0800, Joey Hess wrote:
 base/update

I uploaded a NMU for this already.

Roland

-- 
Roland Bauerschmidt [EMAIL PROTECTED]




Re: Close list

2000-12-22 Thread Carl B. Constantine
On 12/22/2000 19:44, Miles Bader at [EMAIL PROTECTED] wrote:

 No, lets not.
 
 Right now I'm subscribed to debian-devel, but often in the past I've
 read it occasionally in the archives, and sent mail as I thought
 appropriate.  I know there are other people who do this.
 
 The fact is that the spam level on debian-devel right now is in the
 noise (it's certainly exceeded by the volume of pointless and/or
 downright stupid posts).

Yo ppl, it's not hard to archive a closed list, most list software supports
archive directly. Sheesh! You make it sound like it's the end of the world
for crying out loud. Give me a break!

No one should be allowed to post to ANY mail list that is NOT subscribed to
that list! all we need is for more idiot spammers to harvest the address and
spam ad infinitum. Then maybe you'll change your minds.

*sigh*

Back to regularly scheduled Debian/woody discussion.

-- 
Carl B. Constantine ([EMAIL PROTECTED])Phone: 250.953.2650
Open Source Solutions Inc.   Fax: 250.953.2659
4252 Commerce Circle, Victoria, BC.  V8Z 4M2  http://www.os-s.com/

 I feel like a genocidal maniac when emacs asks me if I want
   to kill 10789 characters.




Re: Close list

2000-12-22 Thread Miles Bader
Carl B. Constantine [EMAIL PROTECTED] writes:
 Yo ppl, it's not hard to archive a closed list, most list software supports
 archive directly. Sheesh! You make it sound like it's the end of the world
 for crying out loud. Give me a break!

I was complaining about not being able to post to the list when I wasn't
subscribed.

 No one should be allowed to post to ANY mail list that is NOT subscribed to
 that list!

Why?

 all we need is for more idiot spammers to harvest the address and
 spam ad infinitum. Then maybe you'll change your minds.

Well, so far this hasn't happened.  Until it _does_ happen, there's
absolutely no reason to restrict posting to the list.

-Miles
-- 
Love is a snowmobile racing across the tundra.  Suddenly it flips over,
pinning you underneath.  At night the ice weasels come.  --Nietzsche




Re: Close list

2000-12-22 Thread Carl B. Constantine
This discussion is being taken off list to avoid yet another flame war (not
my intention to start another flamewar).

-- 
Carl B. Constantine ([EMAIL PROTECTED])Phone: 250.953.2650
Open Source Solutions Inc.   Fax: 250.953.2659
4252 Commerce Circle, Victoria, BC.  V8Z 4M2  http://www.os-s.com/

 I feel like a genocidal maniac when emacs asks me if I want
   to kill 10789 characters.




Re: update excuses.. how to read them

2000-12-22 Thread Anthony Towns
On Sat, Dec 23, 2000 at 04:04:03AM +0100, Bernd Eckenfels wrote:
 if i take for example:
 http://ftp-master.debian.org/~ajt/update_excuses.html
 adns 1.0-3 (low) 
  Maintainer: Bernd Eckenfels [EMAIL PROTECTED] 
  adns is 27 days out of date! 
  out of date on alpha: libadns0, libadns0-dev (from 0.8-2) 
  out of date on i386: libadns0, libadns0-dev (from 0.8-2) 
  there are up to date bins in i386 also 
  out of date on m68k: libadns0, libadns0-dev (from 0.8-2) 
  there are up to date bins in m68k also 
  out of date on powerpc: libadns0, libadns0-dev (from 0.8-2) 
  there are up to date bins in powerpc also 
  out of date on sparc: libadns0, libadns0-dev (from 0.8-2) 
  there are up to date bins in sparc also 
  not considered 
 Does that mean that it is not considered because on alpha there are no
 up-to-date bins?

Since libadns0 and libadns0-dev seem to be out of date on all architectures,
it probably means they're not being built anymore, and need to be removed
from unstable. Whether there are up to date bins on an arch is more just
to give a hint at what might be causing the problem, rather than anything
particularly important.

 Is there a build-info for all the other platforms, too? How can I see why
 the alpha failed to build my package?

It may well be excluded on alpha: there are (according to the above) *no*
other abcde binaries on alpha, whether up to date or not.

 The 
  valid candidate (will be installed unless it's dependent upon other
  buggy pkgs)
 is printed, even if the package is already installed in woody?

The way it goes is:

* package files are generated, mirroring happens etc
* testing scripts run:
- excuses generated
- attempt to add all valid candidates to woody (some fail,
  some succeed)
- dinstall is told what to put into woody
* time passes
* packages files are generates, mirroring happens etc
* wash, rinse, repeat

So I don't think valid candidate should appear for any version of
a package already in woody at the time you see it, unless you get in
between mirroring and the testing scripts getting run. Unless you're
poking around at the dinstall database on auric, of course.

Cheers,
aj

-- 
Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/
I don't speak for anyone save myself. GPG signed mail preferred.

 ``Thanks to all avid pokers out there''
   -- linux.conf.au, 17-20 January 2001


pgpn3kZIaCHdt.pgp
Description: PGP signature