Upcoming Debian Releases
The following message is a list of items to be completed for the upcoming
releases of Debian GNU/Linux. If something is missing, incorrect, or you want
to take responsibility for one or more items, please send email to:
Brian White <email@example.com>
This document was last modified at Time-stamp: <97/01/21 13:53:54 bcwhite>
If you're replying about some of the ideas mentioned in this document, it is
often wise to change the subject to reflect that idea. This helps target
those people who are most likely to partake in discussions about it.
For each upcoming release, the name of the task and the person who has claimed
responsibility for it (or "???" if nobody) is listed. An asterisk (*) in front
means the job has yet to be completed and must be done before that release can
be made "stable". A dash (-) in front means it has not yet been completed,
but if not completed in time will just be pushed to the next release.
Footnotes are indicated by "[n]" and give more information on that item.
If you know of packages that do not conform to any of these tasks, please
report it as a bug against those packages. If that task is marked as critical
(i.e. with an asterisk "*"), then please let me know and I will mark the bug
Critical bugs are those that you would seriously consider delaying the
upcoming release because they are not fixed.
Sat, Feb 1, 1997 -- Deadline for objectives for Bo
Mon, Feb 3, 1997 -- Bugs older than 10 months (will be 12 months by release)
will be marked as critical. People might want to start
fixing/closing/forwarding these now to avoid the eventual
Thu, Feb 27, 1997 -- Bo will be frozen.
Fri, Mar 28, 1997 -- Bo will be released.
- When will Debian "officialy" be multi-architecture?
- What should we do about packages that still have "critical" bugs at
* Add dependancy checking on packages going into "fixed" (???)
* No bug reports older than 12 months at release time (firstname.lastname@example.org)
* Shared libraries should provide ".shlibs" files (???)
Move all shared libraries into "libs" (email@example.com) 
Move interpreters out of "devel" (firstname.lastname@example.org) 
* Shadow password support (email@example.com)
* Fix pkgs referencing "/etc/site-start.el"(Frederic.Lepied@sugix.frmug.org)
* Fix remaining "release critical" bugs (firstname.lastname@example.org)
- Move config information from install scripts to "cfgtool" (???)
- Appropriate pkgs should call "install-mime" in postinst (email@example.com)
- Convert remaining a.out packages (???)
- Boot disks should contain drivers for more systems/cards (???)
- Integration of modules, kernel, boot-floppies, & pcmcia (???) 
- Include the multi-thread support patch for the Objective-C runtime lib (???)
Add support for resolutions beyond 1280x1024 to X config utility (???) 
- Fix packages that break with new libc5.4
- Packages to call "install-menu" during postinst (firstname.lastname@example.org)
- Fix "installed size" entries in packages (email@example.com)
- Improvements to 'dselect' (firstname.lastname@example.org,email@example.com) 
- Package grouping to simplify install (firstname.lastname@example.org,email@example.com)
- 'dselect' to determine what to install/remove (???) 
- general "threading" policy (???) 
- configuring so non-ASCII characters, etc. (???) 
- All packages to be in new source format
- Make all web servers apply to the new standard, Bruce had released
- Make all startup messages apply to the new standard
- Use ttyS* devices instead of cua* devices (???) 
* No bug reports older than 9 months at release time
1 - Friday I used the boot floppies in the rex tree and I could load any
modules (NFS being the show stopper). In the Linux Journal review of
Debian (Nov Issue), explictly mentions this problem with 1.1 and it
hasn't been solved yet :( -- Chris Fearnley <firstname.lastname@example.org>
2 - Dselect is our number one public relations problem. It's infelicities
lead others to believe that the package management has flaws and some
can't even get through it. One issue that was raised in a bug report was
to NOT pop up the help screen everytime dselect notices a
dependency/recommendation/conflict problem. I concur. I remember that
that bug report suggested that dselect should not pop up the conflict
resolution manager with its suggestions. I now disagree with that. The
feedback that Debian /cares/ about you not breaking your system (and
offers to suggest a resolution) is more important than the small
frustration in a case one was about to select those packages anyway.
Finally, I believe that dselect is too complex for a program that will
only be used by novices once every six months! Perhaps having only
+ install, upgrade
- unselect, ignore (NOT current semantics so maybe a bad idea?)
r remove from system
And some way to override defaults? Would this be sufficient?
3 - I.e.: say I just want to install a package for a single library-- but I
also want the developer version and the static version... As it stands, I
can either su to root, find the packages and 'dpkg -I' or start dselect,
select the packages, install and wait *forever* as dselect does it's
thing. Instead of having dselect check every single package-- would it
be possible to have a "fast" mode that just installs/uninstalls what the
user selected? -- Bill Bumgarner <email@example.com>
4 - Here's a quick-n-dirty division of the current devel into the above
classes: -- Lars Wirzenius <firstname.lastname@example.org>
CGI-modules blt id-utils libc4 libelf libg++27 libident
libobjects libpam libwww-perl tcl74 tcl75 tclX tk40 tk41
expect gcl guile intercal j1 perl perl-suid perl-tk
postgres95 python python-base python-curses python-dev
python-doc python-examples python-gdbm python-misc
python-mpz python-net python-stdwin python-tk gclinfo
autoconf automake bin86 binutils bison byacc c2man
cflow dchanges ddd-smotif dejagnu dist dld dlltools
electric-fence flex ftnchek gcc gdb gettext gmp gnat
ilu indent libc4-dev libc5-dbg libc5-dev libc5-pic
libdb1-dev libelf-dev libgdbm1-dev libreadline2-dev
make ncurses3.0-dev ncurses3.0-pic p2c perl-debug pmake
ratfor77 slang-devel strace tcl74-dev tcl75-dev
tk40-dev tk41-dev xxgdb glibcdoc cpp m4 cvs rcs
5 - There is a brand new config utility in the XFree86 3.2 release which will
be release end of October (their codefreeze was some time ago). All
efforts put into any package from the standrad X packages (xbase,
xdevel,xfnt*,...) should rather go into providing the new packages.
Note I do not say that we should have this ready for 1.2 (though I hope
we have it very soon), but fixing things in obsolete packages isn't how
we should spend our time.
6 - It's a real pain when you want to do thread programming right now,
especially since things like X haven't been compiled with the thread safe
headers (getc and putc, etc.). We had to recompile some of X ourselves
in order to make things even somewhat stable.
-- Rob Browning <email@example.com>
There was some talk about threads and Debian a while back, and I just
wanted to see what the current sentiment was. I know that pthreads is
part of libc, but it's not (as I recall) currently provided with the
system. What's more, it has some outstanding bugs, and at least last
time I checked, the version that comes with libc is a bit behind the
Anyway, the other major contender seems to be LinuxThreads. It's a
kernel level implementation so you don't need all the glue code that
pthreads has, and it supports multiple CPU's. It also seems to be under
more active development.
Anyway, I just wanted to see if we had any general plans toward making
Debian thread safe. Aside from just picking a library, it would also
mean (at least with pthreads, I'm not sure about LinuxThreads),
recompiling other code (especially the X libraries) with the thread safe
headers (i.e. getc and putc are normally thread hostile macros).
I believe that libc6 is comes with linuxthreads and by default compiles
to be threadsafe where possible (and provides thread-safe versions of
functions where thread-safe conflicts with ANSI/POSIX.
-- Steve Dunham <firstname.lastname@example.org>
7 - These packages shouldn't modify the site-start.el file anymore and
instead put a file in /etc/emacs/site-start.d with the naming convention
XYpackage.el where XY is the scheduling init level.
-- Frederic Lepied <Frederic.Lepied@sugix.frmug.org>
8 - Of course it doesn't change anything for people using a US keyboard, but
it would be a good step forward in conviviality for people having a
French keyboard (At least).
For those who don't see what I mean, typing "!dev!hdq&" instead of
"/dev/hda1" is not fun... _(:
NB: To tell the truth, that was the biggest problem I had, each time I
installed Debian... _(: -- Vincent Renardias <email@example.com>
9 - One of the things that most people outside the US and UK have to deal
with is configuring everything so that non-ASCII characters and other
locale specific stuff works right. For example, bash needs a ~/.inputrc
so that you write åäö on the command line, instead of getting
beeps. Emacs needs some other stuff. -- Lars Wirzenius <firstname.lastname@example.org>
10 - /dev/ttySxx devices are fully POSIX-compliant TTY devices. If you are
only going to be using one set of tty devices, you should be using
/dev/cuaXX devices are different from /dev/ttySXX in two ways --- first
of all, they will allow you to open the device even if CLOCAL is not set
and the O_NONBLOCK flag was not given to the open device. This allows
programs that don't use the POSIX-mondated interface for opening
/dev/ttySxx devices to be able to use /dev/cuaXX to make outgoing phone
calls on their modem (cu stands for "callout", and is taken from SunOS).
The second way in which /dev/cuaXX differs from /dev/ttySXX is that if
they are used, they will trigger a simplistic kernel-based locking
scheme: If /dev/ttySXX is opened by one or more processes, then an
attempt to open /dev/cuaXX will return EAGAIN. If /dev/cuaXX is opened
by one or more processes, then an attempt to open /dev/ttySXX will result
the open blocking until /dev/cuaXX is closed, and the carrier detect line
While this will allow for simple lockouts between a user using a modem
for callout and a getty listening on the line for logins, it doesn't work
if you need to arbitrate between multiple programs wanting to do dialout
--- for example, users wanting to do dialout and UUCP.
I originally implemented the cuaXX/ttySXX lockout mechanism back before
FSSTND established a standard convention for the use of tty lock files.
Now that it's there, people should use the tty lock files and not try
using /dev/cuaXX. The only reason why /dev/cuaXX hasn't disappeared yet
is for backwards compatibility reasons.
-- Tony Nugent <email@example.com>
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com