Debian Weekly News - email

Subject: Release Plans (1999-05-10)
Date: Mon, 10 May 1999 19:06:58 +0200 (CEST)
From: Richard Braakman <>

(Please send followups to debian-devel, not debian-devel-announce.)

This mail is a summary of issues that affect the next release.  Comments
and feedback are welcome.  It's supposed to be a complete list, so please
contact me if your favourite issue is not listed here.

I realize that I have, so far, not acted as Release Manager in the way
I intended.  I apologize for this, and I promise to do better from now on.

A number of release goals have been proposed.  I don't intend to start
the freeze until all release goals are in place.

  * No release-critical bugs.
Wichert's list shows more than 100 of these.  I'll go through it soon,
and probably downgrade a number of them, and mark some packages for
removal when the Time Comes.  (I'll ask Wichert to count those
separately).  Still, it's going to take some time to fix them all,
and this will probably be the main factor in setting the freeze date.

  * Working disk sets for all released architectures.
I don't know much about the plans for the boot-floppies yet.  Could
someone volunteer as a contact person, or tell me the best list to read?

  * glibc 2.1 upgrade
As far as I know, this project is largely complete.  There are one or two
bugs left in the backward compatibility code, and there's the question
of what to do with /dev/pts.

  * glibc 2.1 source compatibility
A larger task is to ensure that all packages still compile on a glibc
2.1 development system.  The sparc people may have a list of problem

  * PAM
Progress has been made toward a fully PAMified system, with X and
the shadow suite being the main exceptions.  I don't intend to
delay the release for this, but I think it has a good chance of
being completed in time anyway.

  * perl 5.005
I've been assured that a working upgrade plan now exists and is being
worked on, one that will not involve recompiling a lot of packages.
I'll still be happier if perl 5.005 is introduced at the start of
the next release cycle, though.  There's a lot of perl code in Debian
that hasn't been tested with the new version.

  * FHS compliance
This will involve a number of changes that will affect all packages.
There's no consensus yet on how to do this, and I consider it to be
still in the "early plans" stage.  In the meantime, we've been moving
toward FHS compatibility in little ways.

I wasn't there to see it, but I hear that the GNOME staging area has
now been folded into potato and is ready for the freeze.

The freeze is at least one month away, and possibly a lot more than
that.  I'm not going to set a date until the number of
release-critical bugs has been reduced considerably.

  debian-release mailing list:
I think this is a good idea, and I will certainly join such a list.

  Return of the Revenge of Slink:
A Debian 2.1r3 release should be made soon, to fix a number of
outstanding bugs.  I'll write a separate mail about this.

  Potato Architectures:
As far as I know it will be the same set as in slink, i.e. i386, m68k,
sparc, and alpha.  If any other architectures want to make a release
they will have to decide soon.

  Help wanted:
I'd like someone in charge of chasing release-critical bugs.  This
means mailing maintainers to ask for plans and estimated fix times,
adding comments to Wichert's bugscan list, and telling me which bugs
are probably bogus.

Richard Braakman

Date: Mon, 10 May 1999 18:48:37 -0500
From: BugScan reporter <>
Subject: Release-critical Bugreport for May 10, 1999

Bug stamp-out list for May 10 12:03 (CST)

Total number of release-critical bugs: 112


Package: adduser (main)
Maintainer: Guy Maor <>
  37069  adduser: Adduser generates gids over 65535

Package: automake (main)
Maintainer: Kevin Dalley <>
  8828   automake can't 'make clean' with depends on generated files

Package: base (pseudo)
Maintainer: Enrique Zanardi <>
  34719  base: /dev/ptmx should not exist unless /dev/pts is properly configured

Package: base-passwd (main)
Maintainer: Galen Hazelwood <>
  36007  update-passwd did many stupid things

Package: bash (main)
Maintainer: Guy Maor <>
  34125  Latest bash breaks mandb
  34138  bash: bug doesn't work anymore
  34717  bash: contains /bin/sh link
  35214  bash: Incorrect 'case' pattern matching when LANG=fr

Package: boot-floppies (main)
Maintainer: Enrique Zanardi <>
  36875  resc1440tecra.bin does not install tecra kernel
  36947  boot-floppies: base.tgz not found - no error message

Package: cfs (non-US)
Maintainer: Patrick J. Edwards <>
  14321  cfs: cmkdir does not work

Package: cmucl (main)
Maintainer: Peter Van Eynde <>
  34554  cmucl doesn't work with glibc 2.1

Package: communicator-smotif-45 (non-free)
Maintainer: Adam Heath <>
  34806  Communicator 4.5 (Mail) crashes suddenly

Package: cqcam (main)
Maintainer: Martin Schulze <>
  35391  Please recompile cqcam with GTK+ 1.2

Package: crossfire-server (main)
Maintainer: Darren Benham <>
  37203  Misconfigured path for map files??

Package: debiandoc-sgml (main)
Maintainer: Ardo van Rangelrooij <>
  37268  content negotiation failing -- 'foo..html'

Package: dfm (contrib)
Maintainer: Michael Bramer <>
  35394  Please recompile dfm with GTK+ 1.2

Package: diald (main)
Maintainer: Philippe Troin <>
  32592  diald: Problems with dynamic addressing and 2.2.1 kernel

Package: dpkg (main)
Maintainer: Ian Jackson and others <>
  17624  dpkg: installs regular dir when .deb contains symlink !
  1797   upgrade/downgrade dependency calculation problem
  21182  dpkg: dpkg can go into an infinite loop with --force-configure-any
  28519  dpkg: creates circular symlinks [POSSIBLE WORKAROUND]
  28817  dpkg takes no care over libdpkg
  30090  weirdass dpkg coredumps and xbase upgrade insanity
  33618  dpkg: most recent hamm version, but *multiple* packages insist it be upgraded!
  36385  consensus on stuff left to be fixed in slink
  36431  consensus on stuff left to be fixed in slink
  36972  dpkg: dpkg can remove vital files/symlinks without warning administrator
  37017  dpkg: .deb should contain authentication data
  37254  dpkg: update-alternatives madness
  9771   install-info name conflict

Package: dpkg-dev (main)
Maintainer: Ian Jackson and others <>
  25405  xpm: builds libc5 package on powerpc

Package: dpkg-multicd (main)
Maintainer: Martin Schulze <>
  36948  boot-floppies: no (or bad) check for free disk space

Package: dwww (main)
Maintainer: Jim Pick <>
  37378  dwww: menu-method out of date

Package: e2fsprogs (main)
Maintainer: Yann Dirson <>
  35595  e2fsprogs 1.14 (e2fsck) Locks during Boot Process

Package: emacs20 (main)
Maintainer: Rob Browning <>
  33237  /etc/alternatives/emacs not managed properly - /usr/bin/emacs doesn't run emacs20

Package: expect5.24 (main)
Maintainer: David Engel <>
  34283  expect5.24: alternatives bug on upgrade to slink

Package: fetchmail (main)
Maintainer: Paul Haggart <>
  36677  Package fetchmail_5.0.1-1.dsc not extractable

Package: fileutils (main)
Maintainer: Galen Hazelwood <>
  31717  fileutils: 'mv regularfile symlink' problems
  36770  fileutils: install has problems with permissions

Package: fortune-mod (main)
Maintainer: Brian Bassett <>
  37091  fortune-mod: open call has hardcoded access mode

Package: (pseudo)
Maintainer: Guy Maor <>
  33979 slink currupt packages
  34901  The xmodmap package still exists
  35295  Please install new version of Release-Notes
  36611  The conf package should die
  36978  Please replace netstd_3.07-2.deb in ../deb_files
  36981  Please install new version of README-upgrade

Package: ftpwatch (main)
Maintainer: Hakan Ardo <>
  35159  ftpwatch: depends on ncftp

Package: gdb (main)
Maintainer: Vincent Renardias <>
  32586  gdb ignores breakpoints
  33868  gdb: Gdb segfaults on loading executable
  36341  gdb: Gives a parse error when casting an expression
  37420  gdb: Breakpoints don't work.

Package: gicon (main)
Maintainer: Martin Schulze <>
  35912  gicon must be recompiled with GTK+ 1.2

Package: guile1.3 (main)
Maintainer: Craig Brozefsky <>
  34941  Cannot start gnucash

Package: kernel-image-2.0.36 (main)
Maintainer: Herbert Xu <>
  34348  Adaptec 294x boot hangs after "419 instructions downloaded"
  37074  Slink boot floppies hang machine after initalizing the Adaptec  AHA2940UW

Package: kernel-image-2.2.1 (main)
Maintainer: Johnie Ingram <>
  36230  Compiler failure

Package: latex2html (main)
Maintainer: Manoj Srivastava <>
  35837  TeX dir has changed

Package: libc6 (main)
Maintainer: Joel Klecker <>
  33832  libc6: dlopen problem.  causes libraries to get opened about 4x (patch included)
  34953  The elm problem
  35315  libc6: unterminated ttyname breaks screen [fix included]
  36016  I tried a partial upgrade and hosed my system
  36050  Suspect problems in libc6
  36584  nss' compat does not work with shadow nis

Package: libgtk-imlib-perl (main)
Maintainer: Paolo Molaro <>
  35918  libgtk-imlib-perl must be recompiled against GTK+ 1.2

Package: libgtk-perl (main)
Maintainer: Paolo Molaro <>
  33704  Dependancy on libgtk1.1 is not and cannot be satisfied!

Package: libtool (main)
Maintainer: Ossama Othman <>
  37286  Again big-endian trouble with libtool

Package: lintian (main)
Maintainer: Richard Braakman <>
  35423  lintian: dies on manpages check (file-info)

Package: lsof (main)
Maintainer: Jim Mintha <>
  31935  lsof: addings for glibc-2.1 and linux-2.2

Package: makedev (main)
Maintainer: Bdale Garbee <>
  37204  makedev,sysklogd: /dev/xconsole reveals privileged information to non-root users

Package: man-db (main)
Maintainer: Fabrizio Polacco <>
  35326  man-db: Newest man-db breaks the pager on all terminals -- no scrollback, stray lines, etc.

Package: mount (main)
Maintainer: Vincent Renardias <>
  34292  mount sometimes trashes /etc/mtab

Package: netstd (main)
Maintainer: Herbert Xu <>
  34849  netstd: Version of netstd in potato is missing security fixes from slink version

Package: nfs-server (main)
Maintainer: Herbert Xu <>
  36732  problem between nfs-server 2.2beta37-1 (slink) and netstd 3.07-2 (hamm)
  37180  nfs-server: rpc.mountd hangs regulary

Package: (pseudo)
Maintainer: Heiko Schlittermann <>
  35578  No passiv ftp possible on
  35579  backlock in Incoming of

Package: omniorb (main)
Maintainer: Brent A. Fulgham <>
  36096  CORBA_sysdep.h does not define byte order

Package: pcmcia-modules-2.0.34 (main)
  33929  pcmcia-modules-2.0.34: unresolved symbols in slink, disastrous upgrade from hamm SOLUTION: drop kernel 2.0.34 from slink

Package: pgp5i (non-US)
Maintainer: Tommi Virtanen <>
  31577  pgp5i: pgps encrypts if text has 8bit characters

Package: pilot-link (main)
Maintainer: Dermot Bradley <>
  31806  pilot-link: Can't build from source

Package: ppp (main)
Maintainer: Philip Hands <>
  35064  /root/.ppprc

Package: pvm (main)
Maintainer: Drake Diedrich <>
  37290  pvm_3.4.0-3(unstable): build error due to root-owned files

Package: python-base (main)
Maintainer: Gregor Hoffleit <>
  36687  python-base: esmtp broken in

Package: rexec (main)
Maintainer: Herbert Xu <>
  36466  rexec: always prompts for username/passwd

Package: rsync (main)
Maintainer: Philip Hands <>
  36179  directory specification is ignored
  36216  [ rsync 2.3.1 release - security fix]

Package: setserial (main)
Maintainer: Gordon Russell <>
  31542  setserial: uses obsolete ioctls on 2.1|2 kernels
  32434  setserial: the use of rc.boot is obsolete
  34637  setserial hangs for a bit on Sun architectures

Package: sgml-base (main)
Maintainer: Manoj Srivastava <>
  28704  sgml-base: sgml entity handling should conform to Cees de Groot's proposed std

Package: silo (main)
Maintainer: Davide Barbieri <>
  34896  silo looks for kernel image in wrong place on sun4u

Package: smail (main)
Maintainer: Soenke Lange <>
  35092  smail crashes!
  36349  smail: Sig11

Package: smalleiffel (main)
Maintainer: Oliver Elphick <>
  36973  smalleiffel: bad source package

Package: ssh (non-US)
Maintainer: Philip Hands <>
  36478  root can access client X display
  36632  ssh: Cannot connect to remote host using .shosts with RSA host authentication.

Package: ssleay (non-US)
Maintainer: Christoph Martin <>
  36769  Sparc considered as little endian

Package: tcpdump (main)
Maintainer: Peter Tobias <>
  36692  ARM port issues

Package: telnet98 (non-US)
Maintainer: Ian Lynagh <>
  30927  telnet98: Telnet98 segfaults

Package: tetex-bin (main)
Maintainer: Christoph Martin <>
  36671  tetex-bin: xdvi fails on gzipped files

Package: textutils (main)
Maintainer: Galen Hazelwood <>
  36795  textutils: tail argument parsing is fubar

Package: vice (contrib)
Maintainer: Giuliano Procida <>
  37201  ROM images in source package

Package: watchdog (main)
Maintainer: Johnie Ingram <>
  34895  type conversion problem

Package: wu-ftpd-academ (main)
Maintainer: Heiko Schlittermann <>
  34206  User ftp must not be created without my permission
  34418  wu-ftpd-academ: this ain't a licence!

Package: xaw3dg (main)
Maintainer: joost witteveen <>
  35105  xcontrib: viewres fails miserably

Package: xlockmore (main)
Maintainer: Herbert Xu <>
  35468  xlockmore-4.1[23] -mode bug segfaults

Package: xmcd (main)
Maintainer: Wichert Akkerman <>
  35177  xmcd: bad default device and $XMCD_LIBDIR dependency

Package: xserver-neomagic (non-free)
Maintainer: Ian Lynagh <>
  34815  xserver-neomagic: XBF-NeoMagic core dumps with new libraries

Package: xserver-xsun (main)
Maintainer: Branden Robinson <>
  35613  xserver-xsun: X server doesn't check /dev/fb? perms correctly [PATCH]

Package: yorick (main)
Maintainer: David H. Munro <>
  37405  yorick_1.4-12(unstable): Uses i386 assembler

This post is automatically generated. Please send comments to .

Date: 10 May 1999 11:04:19 -0000
Subject: Uploaded rsync 2.3.1-0.slink.1 (source i386) to uk


Format: 1.5
Date: Sat,  8 May 1999 10:53:53 +0100
Source: rsync
Binary: rsync
Architecture: source i386
Version: 2.3.1-0.slink.1
Distribution: stable
Urgency: high
Maintainer: Philip Hands <>
 rsync      - fast remote file copy program (like rcp)
 rsync (2.3.1-0.slink.1) stable; urgency=high
   * New upstream release (security fix)
 6a8e3606d4447a84402738c3dff56e16 625 net optional rsync_2.3.1-0.slink.1.dsc
 907a0ae01417d54e53cb84b069ba1620 307130 net optional rsync_2.3.1.orig.tar.gz
 f0c1e8a59d845f9e730077ab58d4b857 4570 net optional rsync_2.3.1-0.slink.1.diff.gz
 1596e1746d1685a69972851b62eb66c1 91358 net optional rsync_2.3.1-0.slink.1_i386.deb

Version: 2.6.3ia
Charset: noconv


Subject: Re: Homapages in list of maintainers
From: Taketoshi Sano <>
Date: 10 May 1999 19:02:44 +0900

Hi, I'm one of the members in Debian JP,
and a self candidate to a maintainer in Debian.

In article <>
 Atsuhito Kohda <> writes:

> From: Andreas Tille <>
> Subject: Re: Homapages in list of maintainers
> Date: Fri, 7 May 1999 11:27:03 +0200 (METDST)

>> By the way: is there really a need to split Debian JP from
>> Debian??  Sounds curious for me.

> No, completely no :-) My poor English may confuse you but
> the aim of Debian JP is
> - to help Debian to be more internationalized,
> - and so Debian JP will contribute packages created by maintainers
>   of Debian JP to Debian.
> But some barriers prevent us from becoming official maintainers
> so the merging Debian JP into Debian does not work well now.

I have heard that some self-candidates from Debian JP felt
that the Debian Project rejects them as a maintainer,

one of them had not receive no answers for long time,

   more than a month is too long enough for ordinary people.

one of them did not have no English-written certificate,

   He was a high school student at that time, and did not have
   the passport. He cannot get Driver's License since the laws
   in Japan prohibit those under 18-years-old to get the license,
   as well as many high school in Japan also prohibit their student
   to get the license as the school rules.
   (In fact, the Driver's License itself is no-use because
    that is all written in Japanese, so the required is not only
    the license itself, but also International License with extra fee.)
   He got the chance to meet fellow Debian maintainers face to face
   after all, but it takes some extra period and effort unnecessary.

and one of them had not enough time to wait the oversea call at home.

   He worked at laboratory, and during the experimentation,
   he can't respond any call. The experimentation sometimes continues
   all over the night. He can make time to debianize some software
   and he already uploads some interesting packages to Debian JP,
   but he can't upload to Debian now although he himself wishes to do it.
   He wishes that let him know at least the time of calling in advance,
   so he can prepare to respond the call. Currently, nothing is to be
   known when the telephone rings, even at day, night, or midnight.

   "developers-reference" told us

       A phone number where we can call you. Remember that
       the new maintainer team usually calls during
       evening hours to save on long distance tolls.
       Please do not give a work number, unless you are generally
       there in the evening.

   but When is the "evening hours" ? or Where this "the evening hours"
   have meaning at ? We don't know where the person at new-maintainer
   lives in. If he lives in, say, NewYork city, "the evening hours"
   may be 17:00-21:00 there, and 07:00-11:00 morning here.
   Without the announce in advance, those who lives in Japan have
   some difficulty to continue to wait a telephone call hopelessly
   for a few months at such working time.

Some days ago, the dispute arose on Debian JP project,
about the release of next JP Packages. We think that the JP Packages
should (at least) be slim as much as we can, and our goal is
the abolishment of JP Packages (all JP Packages either go into
Debian or get being unnecessary, that means we do not require
the separate localized packages to handle with our language).

Some members including current Debian maintainers (whom we call
as "official maintainers") insist that the action should have
taken now to speed up the contribution of JP packages into Debian.

The proposed action is to make an explicitly declaration that
"official" maintainers can freely take and move the JP packages
debianized by non "official" maintainers.

Why is this needed ? There is a barrier or filter to be a maintainer
on Debian currently, and it is easy to take and move than to wait
patiently the willing JP member to be registered as a maintainer.

BTW, related to that dispute, an "official" maintainer said
the "filter" works effectively. Is this the common idea to
Debian people ? Does Debian needs the filter to trap and drop
the willing self-candidate who have made and maitained
a qualified package already ?

"developers-reference" told us:

  The process of registering as a developer is a process of
  verifying your identity and intentions. As the number
  of people working on Debian GNU/Linux has grown to over 400 people
  and our systems are used in several very important places we have to
  be careful about being compromised. Therefore, we need to verify new
  maintainers before we can give them accounts on our servers and
  letting them upload packages.

I understand (or at least hope to understand) this and I think also
some verification mechanism is required. But I doubt the enoughness
and effectiveness of the current processing mechanism.

"developers-reference" told us also:

  Once this information is received and processed, you should be
  contacted with information about your new Debian maintainer account.
  If you don't hear anything within 7-14 days, please send a followup
  message asking if your original application was received.
  Do not re-send your original application, that will just confuse the
  new-maintainer team. Please be patient, especially near release points;
  mistakes do occasionally happen, and people do sometimes run out of
  volunteer time.

so according to this, I should be waiting at least more 11 days patiently
before sending a followup.

I think, and hope that the Debian is "open" project.

  Taketoshi Sano: <>

Date: Mon, 10 May 1999 10:06:39 -0400
From: "Collins M.  Ben " <>
Subject: glibc 2.1.1 status

Just so everyone knows...I am bringing my sun4m home so that I can test
and debug this glibc 2.1.1 problem further. In the mean time I am going to
upload glibc 2.1.1-5 with a preinst script that _will_ fail in sun4m and
non kernel 2.2 systems.

For the interested, I don't see any vfork() calls in init, so I'm not so
sure this is the problem. I am starting to think that there is a missing
signal (or an errant one). Give me some time (or if you are impatient, try
some debugging on your own and share your results).

For all of you bitten by this mishap I apologize, please email me
privately if you need assistance getting your system back up.


Date: Mon, 10 May 1999 17:02:46 -0700
From: "Ivan E. Moore II" <>
Subject: KDE Debian packages

For those of you interested...KDE is available via apt-get at the following

add this to your /etc/apt/sources.list file

deb slink rkrusty
deb potato rkrusty

depending on your version.

They are still being worked on and fixed up as the ones on are
not up to speed and have other issues I won't go into.  I am also in the process
of fixing up the debian stuff in the KDE CVS tree itself so soon they will be up
to snuff and everything should be working the way they should.  If your
interested in keeping up to speed on this process, a mailing list has been
created for that purpose. Send mail to with a body of
subscribe kde

Currently there are i386 and alpha versions available.  (And partial powerpc
versions).  Sparc should be coming along soon as well.  I have also available
other extra packages such as kpilot, khotkeys and kthememgr.  (tho kthememgr is


Ivan E. Moore II                                      Rev. Krusty              
GPG KeyID=0E1A75E3
GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3

Date: Tue, 11 May 1999 06:57:53 +0200
Subject: Uploaded zmailer 2.99.50.s17-1 (source i386) to erlangen


Format: 1.5
Date: Tue, 11 May 1999 06:46:18 +0200
Source: zmailer
Binary: zmailer
Architecture: source i386
Version: 2.99.50.s17-1
Distribution: unstable
Urgency: high
Maintainer: Remco van de Meent <>
 zmailer    - Mailer for Extreme Performance Demands
 zmailer (2.99.50.s17-1) unstable; urgency=high
   * New upstream release
   * SECURITY FIX !! Quote from upstream:
         There is a SECURITY FAULT in all ZMailer smtpservers that allow
         running router in interactive mode to assist/do address analysis
         with user inputs.  This fault exists in *ALL* versions of ZMailer
         previous to this one! (even 2.2.1 !)
 08c56c5d3b0e5fbed56663484614101a 646 mail optional zmailer_2.99.50.s17-1.dsc
 a70a190ebb9cee5cd2a3de82c6e4bd1d 3897834 mail optional zmailer_2.99.50.s17.orig.tar.gz
 6b0d5a3eed119bb38a67f916f91bde62 103506 mail optional zmailer_2.99.50.s17-1.diff.gz
 6e91bce37013775c9bc2374064c6e95e 764500 mail optional zmailer_2.99.50.s17-1_i386.deb

Version: 2.6.3ia
Charset: noconv


To receive this newsletter weekly in your mailbox, subscribe to the debian-news mailing list.

Back issues of this newsletter are available.

This issue of Debian Weekly News was edited by Joey Hess.