Re: Old Library dependencies Re: Release Plans (19990513)
Hartmut Koptein wrote: Remove as many dependencies on old libraries as possible, this includes: libjpegg6a, libncurses3.4, newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, libpng0g and various older gtk/gnome libraries. Lintian has a depends-on-obolete-package tag. I will add newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, and libpng0g to its list. This way, the Lintian page for that tag will form a useful index. Why not libjpegg6a and libncurses3.4? I didn't have to add them, they were already there :) What about xbase, emacs19, altgcc, freetype1, libc5, libg++27, libpaper, tclx76 and possible some more? Most of those aren't obsolete in this sense. emacs19 is still standard! There's also no point in adding packages that aren't in the distribution anymore, since they will show up in the dependency check. But I'll add xbase. Richard Braakman
Re: Old Library dependencies Re: Release Plans (19990513)
Steve Dunham wrote: Library dependencies: Remove as many dependencies on old libraries as possible, this includes: libjpegg6a, libncurses3.4, newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, libpng0g and various older gtk/gnome libraries. I hesitate to add this as a release goal, except for dependencies on packages which have been removed or which no longer have source. For other packages it should be worked on, but it is not critical for potato. Lintian has a depends-on-obolete-package tag. I will add newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, and libpng0g to its list. This way, the Lintian page for that tag will form a useful index. Richard Braakman
Re: Old Library dependencies Re: Release Plans (19990513)
Remove as many dependencies on old libraries as possible, this includes: libjpegg6a, libncurses3.4, newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, libpng0g and various older gtk/gnome libraries. Lintian has a depends-on-obolete-package tag. I will add newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, and libpng0g to its list. This way, the Lintian page for that tag will form a useful index. Why not libjpegg6a and libncurses3.4? What about xbase, emacs19, altgcc, freetype1, libc5, libg++27, libpaper, tclx76 and possible some more? Thnx, Hartmut
Re: Old Library dependencies Re: Release Plans (19990513)
On Mon, May 17, 1999 at 11:36:41AM +0200, Hartmut Koptein wrote: Remove as many dependencies on old libraries as possible, this includes: libjpegg6a, libncurses3.4, newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, libpng0g and various older gtk/gnome libraries. Lintian has a depends-on-obolete-package tag. I will add newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, and libpng0g to its list. This way, the Lintian page for that tag will form a useful index. Why not libjpegg6a and libncurses3.4? What about xbase, emacs19, altgcc, freetype1, libc5, libg++27, libpaper, tclx76 and possible some more? Aren't most of these already on that list? libghttp0 could be added, too. -- enJoy -*/\*- http://jagor.srce.hr/~jrodin/
Release Plans (19990513)
(Please send followups to this mail to debian-devel, not debian-devel-announce) This is what I learned from the responses to the previous announcement. Boot disks: Creating disk sets with the much larger 2.2 kernels is proving difficult. This is likely to delay the freeze unless the boot-floppies team gets some help. CD Images: The tools that create the CD images could use some fixing. Join the debian-cd list if you wish to help. Architectures: PowerPC will also release with potato. That makes the full list: i386 m68k alpha sparc powerpc PAM: Ben Collins sponsored full pamification as a release goal. The main packages that need work are the shadow suite, and xdm. Perl 5.005: Two people volunteered as coordinator for this, and promptly got into an argument :-) I'll pick wait and see on this one. Richard Braakman
Re: Release Plans (19990513)
On Thu, May 13, 1999 at 02:28:16PM +0200, Richard Braakman wrote: PAM: Ben Collins sponsored full pamification as a release goal. The main packages that need work are the shadow suite, and xdm. /me blinks... has nis (the package) been PAMified? I positively hate PAM because it's an all or nothing solution. After helping some people set nis up on a couple of RH boxes, we all agreed RH sucks big time. They PAMified what they considered important, and their nis package wasn't on that list. End result: you have lots of PAMified stuff, but you can't use most of PAM's features. Marcelo
Re: Release Plans (19990513)
Marcelo E. Magallon [EMAIL PROTECTED] writes: On Thu, May 13, 1999 at 02:28:16PM +0200, Richard Braakman wrote: PAM: Ben Collins sponsored full pamification as a release goal. The main packages that need work are the shadow suite, and xdm. /me blinks... has nis (the package) been PAMified? I positively hate PAM because it's an all or nothing solution. After helping some people set nis up on a couple of RH boxes, we all agreed RH sucks big time. They PAMified what they considered important, and their nis package wasn't on that list. End result: you have lots of PAMified stuff, but you can't use most of PAM's features. I'm not entirely sure what you're talking about here. I use NIS and PAM all the time on RedHat (and Debian - although half of our stuff is not yet pamified). What exactly has to be pamified in the nis package? (In RH 6.0, setting up an NIS client is as easy as typing the domain name into a text widget during the install.) In fact, on Debian I use my own pamified versions of rsh because the non-pam versions _don't_ work with NIS. (They don't grok netgroups in hosts.equiv.) Steve [EMAIL PROTECTED]
Old Library dependencies Re: Release Plans (19990513)
Richard Braakman [EMAIL PROTECTED] writes: (Please send followups to this mail to debian-devel, not debian-devel-announce) This is what I learned from the responses to the previous announcement. Boot disks: CD Images: Architectures: PAM: Perl 5.005: Library dependencies: Remove as many dependencies on old libraries as possible, this includes: libjpegg6a, libncurses3.4, newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, libpng0g and various older gtk/gnome libraries. Problematic packages can be found using apt-cache showpkg libjpegg6a (replace libjpegg6a with the outdated library). A whole list of packages can be done with a script like: (LIBS=libpng0g newt0.25 ncurses3.4 libpgsql libjpegg6a tcl7.6 libwraster1 for pkg in $LIBS; do apt-cache showpkg $pkg|sed -e '/^Reverse D/,/^[^ ]/p;d'|grep -v Depend done)| sort -u (We should filter out an exceptions list too - these lists will have to be seperately generated for each architecture.) It might also be a good idea to add a filter to dinstall to keep new packages that depend on one of these libraries from being uploaded (with a suitable exceptions list). A raw list of bad packages is at the end of this message. Steve [EMAIL PROTECTED] abiword,libpng0g angband,ncurses3.4 boot-floppies,newt0.25 cqcam,libjpegg6a cti-ifhp,ncurses3.4 dbf2pg,libpgsql fbtv,libjpegg6a ftape-util,tk4.2 gettyps,ncurses3.4 gicon,libjpegg6a gnotes,libjpegg6a gtksql,libpgsql gzilla,libjpegg6a hdlant,ncurses3.4 hfsutils-tcltk,libjpegg6a imagemagick,libjpegg6a imaptool,libjpegg6a ircii,ncurses3.4 itcl3.0,ncurses3.4 jpeginfo,libjpegg6a kerberos4kth-clients,ncurses3.4 kerberos4kth-services,ncurses3.4 kerberos4kth-user,ncurses3.4 knews,libjpegg6a libch,libpgsql libhdf4g,libjpegg6a libjpeg6a,libjpegg6a libjpegg-dev,libjpegg6a libmagick4g,libjpegg6a libmagick4g-lzw,libjpegg6a libpgsql2,libpgsql libterm-readline-gnu-perl,ncurses3.4 libtiff3,libjpegg6a malaga-bin,tk4.2 mgt,ncurses3.4 mosaic,libjpegg6a mosaic,libpng0g mush,ncurses3.4 netris,ncurses3.4 netstd,ncurses3.4 nn,ncurses3.4 oneliner,ncurses3.4 perlmagick,libjpegg6a pfe,ncurses3.4 prc-tools,ncurses3.4 rat,ncurses3.4 rscheme,ncurses3.4 scilab,ncurses3.4 scottfree,ncurses3.4 sniffit,ncurses3.4 socks4-clients,ncurses3.4 speak-freely,ncurses3.4 streamer,libjpegg6a tcd,ncurses3.4 tcl7.6-dev,tcl7.6 tcl76,tcl7.6 tela,ncurses3.4 telnet98,ncurses3.4 telnetd98,ncurses3.4 tf,ncurses3.4 tk4.2,tcl7.6 tk4.2-dev,tk4.2 tk42,tk4.2 tkdesk,tcl7.6 tkdesk,tk4.2 tkgofer,ncurses3.4 tkgofer,tcl7.6 tkgofer,tk4.2 tkstep4.2,tcl7.6 trn,ncurses3.4 ultra-utils,ncurses3.4 uudeview,tcl7.6 uudeview,tk4.2 vice,ncurses3.4 webcam,libjpegg6a wmss,libwraster1 worklog,ncurses3.4 www-pgsql,libpgsql x11iraf,ncurses3.4 xacc,libjpegg6a xawtv,libjpegg6a xfig,libjpegg6a xlife,ncurses3.4 xloadimage,libjpegg6a xpaint,libjpegg6a xpcd,libjpegg6a yagirc,libjpegg6a
Re: Old Library dependencies Re: Release Plans (19990513)
Steve Dunham [EMAIL PROTECTED] writes: Remove as many dependencies on old libraries as possible, this includes: libjpegg6a, libncurses3.4, newt0.25, libpgsql, tk4.2, tcl7.6, libwraster1, libpng0g and various older gtk/gnome libraries. Looking at some of these, it occurs to me that one thing that may cause this to happen accidentally is when a -dev package includes a soname---because developers have to take an additional explicit step to be sure to compile with the new version---as an example, the existence of libpng0g-dev (rather than libpng-dev) would make it easy for people to miss the new -dev library. Should we try and remove sonames from -dev package names? Mike.
Re: Release Plans (19990513)
I'm not entirely sure what you're talking about here. I use NIS and PAM all the time on RedHat (and Debian - although half of our stuff is not yet pamified). What exactly has to be pamified in the nis package? (In RH 6.0, setting up an NIS client is as easy as typing the domain name into a text widget during the install.) IIRC, the nis server was running Debian and the nis client was running RH 5.2; until I switched everything to unix_auth, the client wouldn't verify passwords using the NIS server. On a different setup, both the system and the server were running RH 5.2, and NIS wouldn't work until unix_auth was used in /etc/pam.d/login; what's the point of using PAM if you end up using unix_auth? Marcelo
PAM notes... [was Re: Release Plans (19990513)]
On Thu, May 13, 1999 at 10:13:59AM -0600, Marcelo E. Magallon wrote:
I'm not entirely sure what you're talking about here.
I use NIS and PAM all the time on RedHat (and Debian - although half
of our stuff is not yet pamified). What exactly has to be pamified in
the nis package? (In RH 6.0, setting up an NIS client is as easy as
typing the domain name into a text widget during the install.)
IIRC, the nis server was running Debian and the nis client was running RH
5.2; until I switched everything to unix_auth, the client wouldn't verify
passwords using the NIS server. On a different setup, both the system and
the server were running RH 5.2, and NIS wouldn't work until unix_auth was
used in /etc/pam.d/login; what's the point of using PAM if you end up using
unix_auth?
The unix modules do not imply using /etc/{shadow,passwd}, they mean you
will be using the native libc calls which in turn use /etc/nsswitch.conf.
NIS should work fine with PAM without _any_ changes as long as you have
nis listed in nsswitch.conf for the proper listings (just the same as you
would have to do without PAM).
IOW, PAM does not have anything to do with NIS support. Please NOTE!!! Do
not use pwdb as defaults in the pam.d for packages which support PAM, we
ran into this problem with ssh/PAM, it does initially break NIS support
unless you also modify /etc/pwdb.conf, and this has been looked down on,
and should _not_ be used as default for our packages.
Re: Release Plans (19990513)
On Thu, May 13, 1999 at 07:03:37AM -0600, Marcelo E. Magallon wrote: On Thu, May 13, 1999 at 02:28:16PM +0200, Richard Braakman wrote: PAM: Ben Collins sponsored full pamification as a release goal. The main packages that need work are the shadow suite, and xdm. /me blinks... has nis (the package) been PAMified? I positively hate PAM because it's an all or nothing solution. After helping some people set nis up on a couple of RH boxes, we all agreed RH sucks big time. They PAMified what they considered important, and their nis package wasn't on that list. End result: you have lots of PAMified stuff, but you can't use most of PAM's features. The reason for this is because RH uses libpwdb with their PAM apps and pam_pwdb as a module. This means you have to setup /etc/nsswitch.conf _and_ /etc/pwdb.conf to use NIS. We don't use libpwdb in our pam, and pam_pwdb.so is not to be used as a default module for PAM applications. Instead pam_unix_*.so is used and works fine with NIS.
