netscape on Debian, libc5 or libc6?
Hi, I have followed the netscape installation instructions (generic linux) and all is unpacked and the install script completes OK. But netscape will not run. It is missing the libraries libg++.so.27 and libstdc++.so.27. These are present on my Debian system (2.0) in usr/lib/libc5-compat. Therefore, I assumed that netscape is libc5 only, and redirected library loads to /usr/lib/libc5-compat (using LD_LIBRARY_PATH). This found the libc5 versions of most libraries, and the libg++.so.27 and libstdc++.so.27 that are ONLY in the libc5 directory. But this showed that a library libXpm.so.4 was not found. This appears to be only in the libc6 set (/usr/X11R6/lib). All this tracked using 'ldd netscape'. This is very confusing. Is netscape libc5 or libc6? If netscape is libc5, then is there a libc5 version of libXpm.so.4 somewhere? Am I totally off the track here? Cheers, Chris. -- +-+ | Dr. Chris Ryan | | CSIRO Exploration and Mining email: [EMAIL PROTECTED]| | 51 Delhi Road (PO box 136) phone: +61-2-9490 8673| | North Ryde NSW 2113fax: +61-2-9490 8909| | Australia. | | | | WWW (Cu-Au group): http://www.syd.dem.csiro.au/research/hydrothermal/ | | WWW (Proton Probe):| | http://www.syd.dem.csiro.au/research/hydrothermal/chris/PM_main.html | | WWW (Mantle Petrology group): http://www.syd.dem.csiro.au/research/mantle/ | | WWW (Me): http://www.syd.dem.csiro.au/unrestricted/people/RyanChris/ | | | +-+
Re: netscape on Debian, libc5 or libc6?
Hi, I have followed the netscape installation instructions (generic linux) and all is unpacked and the install script completes OK. But netscape will not run. It is missing the libraries libg++.so.27 and libstdc++.so.27. These are present on my Debian system (2.0) in usr/lib/libc5-compat. Therefore, I assumed that netscape is libc5 only, and redirected library loads to /usr/lib/libc5-compat (using LD_LIBRARY_PATH). This found the libc5 versions of most libraries, and the libg++.so.27 and libstdc++.so.27 that are ONLY in the libc5 directory. But this showed that a library libXpm.so.4 was not found. This appears to be only in the libc6 set (/usr/X11R6/lib). All this tracked using 'ldd netscape'. This is very confusing. Is netscape libc5 or libc6? If netscape is libc5, then is there a libc5 version of libXpm.so.4 somewhere? Am I totally off the track here? The netscape they officially support is libc5. Though you'll easily find a libc6-based one on their ftp site. I'd say go for glibc version. (Yeah, I know, another 16 megs... I did the same mistake myself anyway. ;)
Re: netscape on Debian, libc5 or libc6?
Hi Phil, I finally got netscape going. It does use the libc5 libraries. I needed to install the xpm4.7 package to provide the missing libXpm.so.4 library (from /oldlibs/), and set LD_LIBRARY_PATH to search /usr/lib/libc5-compat first. But it then worked fine. Cheers, Chris. Multi wrote: Chris Ryan wrote: Hi, I have followed the netscape installation instructions (generic linux) and all is unpacked and the install script completes OK. But netscape will not run. It is missing the libraries libg++.so.27 and libstdc++.so.27. These are present on my Debian system (2.0) in usr/lib/libc5-compat. Therefore, I assumed that netscape is libc5 only, and redirected library loads to /usr/lib/libc5-compat (using LD_LIBRARY_PATH). This found the libc5 versions of most libraries, and the libg++.so.27 and libstdc++.so.27 that are ONLY in the libc5 directory. But this showed that a library libXpm.so.4 was not found. This appears to be only in the libc6 set (/usr/X11R6/lib). All this tracked using 'ldd netscape'. This is very confusing. Is netscape libc5 or libc6? If netscape is libc5, then is there a libc5 version of libXpm.so.4 somewhere? Am I totally off the track here? Cheers, Chris. -- +-+ | Dr. Chris Ryan | | CSIRO Exploration and Mining email: [EMAIL PROTECTED]| | 51 Delhi Road (PO box 136) phone: +61-2-9490 8673| | North Ryde NSW 2113fax: +61-2-9490 8909| | Australia. | | | | WWW (Cu-Au group): http://www.syd.dem.csiro.au/research/hydrothermal/ | | WWW (Proton Probe):| | http://www.syd.dem.csiro.au/research/hydrothermal/chris/PM_main.html | | WWW (Mantle Petrology group): http://www.syd.dem.csiro.au/research/mantle/ | | WWW (Me): http://www.syd.dem.csiro.au/unrestricted/people/RyanChris/ | | | +-+ -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null hey, im totally new on debian. my first installation is five mins ago. I did this installation of 'hamm' because of the same troubles, you reported. In some german newsgroups i was told, that these libs are only available in libc6 systems. So i scratched my old SuSE for debian. Now netscape seems to work. But now i have probs with that damn x-libs :))) the older versions of netscape worked fine on the same system. So I assume that the new 4.50 version is really libc6. If you have enough space for backups, just try that upgrade script, i has read of some mails above.If it will work proper and update your system to libc6 the new netscape should work :)) I have tried to run binaries from my old system, and after installing the old libc5 they worked fine. I dont know how, but switching betwen both libs seems to be no problem. but don't forget to backup !!!( as I do in general :) phil plz excuse, that english isnt my mother-tongue :) -- +-+ | Dr. Chris Ryan | | CSIRO Exploration and Mining email: [EMAIL PROTECTED]| | 51 Delhi Road (PO box 136) phone: +61-2-9490 8673| | North Ryde NSW 2113fax: +61-2-9490 8909| | Australia. | | | | WWW (Cu-Au group): http://www.syd.dem.csiro.au/research/hydrothermal/ | | WWW (Proton Probe):| | http://www.syd.dem.csiro.au/research/hydrothermal/chris/PM_main.html | | WWW (Mantle Petrology group): http://www.syd.dem.csiro.au/research/mantle/ | | WWW (Me): http://www.syd.dem.csiro.au/unrestricted/people/RyanChris/ | | | +-+
Libc5 and libc6 conflict
Hello, I installed Debian Linux 2.0.29 and wanted to add support for ppp. I ran deselect and it refused to install the necessary libc6 library because it was in conflict with the required libc5 library. How can I nevertheless install ppp support. Thank you, Yves Van de Weyer.
Re: Libc5 and libc6 conflict
On Mon, Aug 10, 1998 at 03:05:26PM +0200, Yves Van de Weyer wrote: Hello, I installed Debian Linux 2.0.29 and wanted to add support for ppp. 2.0.29 is NOT a debian version it is the version of the Linux kernel itself. However...if your kernel version is 2.0.29 and you havn't upgraded it on your own...then you are most probably using debian version 1.3 (AKA bo) The current stable version is 2.0 (hamm) I ran deselect and it refused to install the necessary libc6 library because it was in conflict with the required libc5 library. How can I nevertheless install ppp support. ok...this is somewhat complicated. libc is one of the single most importnat componants of your system. It looks like you are trying to install hamm ppp on your bo system. libc5 and libc6 are incompatible. This is in such a way that libc6 can NOT be used to run libc5 binary programs and vica versa, however... it is possible to install BOTH libc5 and libc6 at the same time...but you need a newer version of libc5. I would recommend that you get a hamm (2.0) CD and follow the instructions to upgrade to hamm. (it can be done by hand but...if you screw it up then your system will be completely unusable) If you don't want to do that then check out: http://www.debian.org/2.0/HOWTO.upgrade.html BTW you said you used dselect...from that web page: Q: Why not just use dselect's ftp method like normal? A: It will not order the package installation correctly so can't gaurantee a smooth upgrade. Work is being done on APT, a new front-end to dpkg. with apt, all future upgrades will be easier than ever and not suffer from this type of inconveniance you will be glad you did :) hamm is much more current than bo -Steve -- /* -- Stephen Carpenter [EMAIL PROTECTED] --- [EMAIL PROTECTED] */ E-mail Bumper Stickers: A FREE America or a Drug-Free America: You can't have both! honk if you Love Linux
Re: Linked against libc5 AND libc6?
Frankly the only solution is to find a libc5 version of everything you need, or a libc6 version of everything you need. Sorry. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Linked against libc5 AND libc6?
Hmm ... ok, that makes sense. When I do an ldd on erpcd on a libc5 system it only says it's linked against libc5 ... and libdb is linked against libc6 on hamm systems. tesla:/usr/annex # ldd erpcd libdb.so.2 = /lib/libdb.so.2 libc.so.5 = /lib/libc.so.5 tesla:/usr/annex # cat /etc/debian_version 1.3 Any way out of this mess? I don't have a libc5 version of libdb 2 ... I had to make a rather ugly hack to get this to run on the bo system :) Well, you could take the libdb.so.2 you built on the bo system and stick it in /usr/lib/libc5-compat on the hamm system (don't forget to run ldconfig after). The loader is intelligent in the way that if there are two copies of the library, it will link in the one which uses the same version of libc as the binary. Then perhaps you should petition someone to do a libc5 version of DB 2 for the oldlibs section. Regards, /Anders -- -- Of course I'm crazy, but that doesn't mean I'm wrong. Anders Hammarquist | Mud at Kingdoms| [EMAIL PROTECTED] NetGuide Scandinavia | telnet kingdoms.se 1812| Fax: +46 31 50 79 39 http://www.netg.se | | Tel: +46 31 50 79 40 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Linked against libc5 AND libc6?
Hi there, I've got an odd problem ... I'll ask the questions first: What can I do about a binary that is linked against libc5 and libc6? It (of course) segfaults every time I try to run it. Now, the explanation: We recently purchased a Bay Networks 8000 Remote Access Concentrator. This box needs a UNIX (or NT) machine behind it for authentication purposes. Bay distributes a CD with the software on it - amazingly, Linux binaries were pre-built (good thing since the source wouldn't compile, but that's a question for a different list). The pre-built binaries are linked against libc5 and libc6. I'm not too sure why they did this, but I had to set up a bo box to get this to work. (Perhaps they were thinking that a libc6 box wouldn't have libc5.so installed?) kepler:/usr/annex $ ldd erpcd libdb.so.2 = /lib/libdb.so.2 (0x4000a000) libc.so.5 = /lib/libc.so.5 (0x40018000) libc.so.6 = /lib/libc.so.6 (0x400d6000) ld-linux.so.2 = /lib/ld-linux.so.2 (0x40179000) At any rate, I'm wondering if there's anything I can do to prevent this thing from trying to load either of the shared libs. I don't understand shared libraries and all that underlying stuff to well yet, so go easy on me :) If it's a flat No Way In Hell, that's ok - I'll just have to get this source to compile under libc5 OR libc6, right? Sorry for being ignorant on this stuff - I'm trying to learn it. Thanks in advance ... -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Linked against libc5 AND libc6?
Nathan E Norman wrote: kepler:/usr/annex $ ldd erpcd libdb.so.2 = /lib/libdb.so.2 (0x4000a000) libc.so.5 = /lib/libc.so.5 (0x40018000) libc.so.6 = /lib/libc.so.6 (0x400d6000) ld-linux.so.2 = /lib/ld-linux.so.2 (0x40179000) Do an ldd on libdb.so.2. I find the most common cause of this double linkage is that one of the other libs is linked against libc6 when the actual app was linked on libc5 (this was the problem w/ quake mentioned on the mailing list ad infinitum). Otherwise get the source and compile it on either libc5 or a libc6 system. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Linked against libc5 AND libc6?
-BEGIN PGP SIGNED MESSAGE- On Thu, 2 Jul 1998, Nathan E Norman wrote: kepler:/usr/annex $ ldd erpcd libdb.so.2 = /lib/libdb.so.2 (0x4000a000) libc.so.5 = /lib/libc.so.5 (0x40018000) libc.so.6 = /lib/libc.so.6 (0x400d6000) ld-linux.so.2 = /lib/ld-linux.so.2 (0x40179000) The executable might not have been built against both libcs, but your environment might be confusing it. Do you have your $LD_LIBRARY_PATH environment variable set in your shell? If so, try unsetting it, and running ldd on the executable. I've run into this problem several times with libc5 apps. Most recently effected was Netscape 4.04, dynamically linked against Motif. For some reason, ld.so wasn't finding libXm.so, so I set the LD_LIBRARY_PATH to point to the directory containing it. This was the same directory that contained libc.so.6. This caused Netscape to try linking against both libc5 and libc6, which caused ugly things to happen. I wouldn't be surprised if your environment is causing similar things to happen. Noah PGP public key available at http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html or by 'finger -l [EMAIL PROTECTED]' -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBNZvhHIdCcpBjGWoFAQG0RAP/TxPPX3PKei8BcO+0nZ0ckq3asr4jw1Sq jXgF/5BplrBrwMNypDS2mSvDKnujjLJN1NM9goj7n12S5pn2jqwgL4emr5Xlt2Bu A7Yf+PKTWnpzFXUgJMWPChWxI9Uk0ni6e7QuLCz0/uWfndZcvE2ttKXUD10ZJs3x /iQkeiQ8K/A= =au/T -END PGP SIGNATURE- -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Linked against libc5 AND libc6?
On Thu, 2 Jul 1998, Shaleh wrote: : Nathan E Norman wrote: : kepler:/usr/annex $ ldd erpcd : libdb.so.2 = /lib/libdb.so.2 (0x4000a000) : libc.so.5 = /lib/libc.so.5 (0x40018000) : libc.so.6 = /lib/libc.so.6 (0x400d6000) : ld-linux.so.2 = /lib/ld-linux.so.2 (0x40179000) : : Do an ldd on libdb.so.2. I find the most common cause of this double : linkage is that one of the other libs is linked against libc6 when the : actual app was linked on libc5 (this was the problem w/ quake mentioned : on the mailing list ad infinitum). Otherwise get the source and compile : it on either libc5 or a libc6 system. Hmm ... ok, that makes sense. When I do an ldd on erpcd on a libc5 system it only says it's linked against libc5 ... and libdb is linked against libc6 on hamm systems. tesla:/usr/annex # ldd erpcd libdb.so.2 = /lib/libdb.so.2 libc.so.5 = /lib/libc.so.5 tesla:/usr/annex # cat /etc/debian_version 1.3 Any way out of this mess? I don't have a libc5 version of libdb 2 ... I had to make a rather ugly hack to get this to run on the bo system :) Thanks for the explanation of the crosslinking. That makes a lot more sense now that I think about it. -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: libc5 vs. libc6
Brian Morgan wrote: I'm having trouble setting up xwindows in debian 2.0. I install Xwindows as an option when installing debian 2.0 (kernel 2.0.33), but get error messages all over the place about missing libraries when I type xdm or startx. In running dselect, I see that I have libc6 installed, but everytime I try to load x11 components, it tells me to install libc5 instead, which gets rid of many major components of the base system, and x11 STILL doesn't work. Furthermore, once I've removed libc6, I can't get dselect to install from ftp (probably because dpkg-ftp requires libc6), so I can't do any further updates. I'm going to reinstall debian 2.0 and try again to get x11 running. Any suggestions on how to do this the right way? Brian Morgan How are you installing Debian 2.0? Via ftp? Make sure you are installing the libc6 version of XWindow (3.3.2.1-1). This is available on ftp.debian.org at 'dists/hamm/main' (using ftp of dselect). Are you installing debian 2.0 from the install disks, or are you trying to upgrade an existing Debian 1.3.1 to 2.0? If you are doing the latter, you should start with the autoup script from the Developer's Corner on www.debian.org. Read the HowTo that is there as well. -- Ed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
libc5 vs. libc6
I'm having trouble setting up xwindows in debian 2.0. I install Xwindows as an option when installing debian 2.0 (kernel 2.0.33), but get error messages all over the place about missing libraries when I type xdm or startx. In running dselect, I see that I have libc6 installed, but everytime I try to load x11 components, it tells me to install libc5 instead, which gets rid of many major components of the base system, and x11 STILL doesn't work. Furthermore, once I've removed libc6, I can't get dselect to install from ftp (probably because dpkg-ftp requires libc6), so I can't do any further updates. I'm going to reinstall debian 2.0 and try again to get x11 running. Any suggestions on how to do this the right way? Brian Morgan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
bo to hamm and libc5 vs libc6
My ultimate purpose is to get Xwindows to work for my Matrox Millenium II. Ben Pfaff and Ossama Othman, both of whom successfully use the Matrox Millenium II video card, both suggestion what amounts to an update of the SVGA server. I was unable to get this to work. Ossama Othman, noted in his message that he stared from hamm before upgrading (I am working from bo debian 1.31). The xserver_SVGA and XFSetup 3.3.2 both ended with a complaint that a file could not be found. I assume there is some file in one of the the latest X hamm packages. That is not in the bo packages. Therefore I decided to update to xserver-svga_3_3_2-2 and also xbase_3_3_2-2. I figured I would also get the VGA server since it might be used in the setup program. Somewhere down the dependency tree from xbase_3_3_2-2 I needed libc6 (latest hamm package libc6_2_0_7pre1-4). However dpkg won't install libc6 because it conflicts with libc5 and it wont remove libc5 because almost every package I have depends upon it. Is it necessary to upgrade my whole system to hamm, just to get the Matrox Millenium II to work? Do I have to replace libc5 with libc6? Is there any way to have them both on the same system? Has anyone tried just upgrading the SVGA server from bo 1.31 to hamm? My only purpose is to get Xwindows to work on my Matrox Millenium II by the most straightforward and expedient way I can figure. -Thanks, Chip 'forever in text mode' Grandits -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bo to hamm and libc5 vs libc6
Hi Chip,
I believe that the XFree86 sites/mirrors contain sets of binaries for both
glibc/libc6 and for libc5. Someone correct me if I am wrong. If you are
willing to install things manually instead of using Debian's nifty
packages, then you can download the XF86-3.3.2 binaries and just untar
them into /usr/X11R6. From what I recall, the XF86 binaries are archived
relative to this directory. You might want to check this before you
extract the archives there. Relevant files to get may include:
X332SVGA.tgz
X332VG16.tgz
X332set.tgz
X332config.tgz
X332lib.tgz
X332bin.tgz
X332prog.tgz
(and maybe some fonts if don't already have them)
Actually I just confirmed that these are linked against libc5. Here is
the output from ldd:
myhost:~/bin ldd ./XF86_SVGA
libm.so.5 = /lib/libm.so.5 (0x4000b000)
libdl.so.1 = /lib/libdl.so.1 (0x40014000)
libc.so.5 = /lib/libc.so.5 (0x40017000)
You can grab these binaries from the 3.3.2/binaries/Linux-ix86
directory, not the glibc one. If you also download the {pre,post}inst.sh
shell scripts and run them, then make sure you don't link the server to
X. Remember that Debian's X is an suid wrapper for the X server.
Remember to check that your /etc/X11/Xserver file reflects the location of
the server you will be using, in this case /usr/X11R6/bin/XF86_SVGA.
Also, remember to use the 24bpp fix if you have problems at 24bpp. One
last thing, XF86Setup probably defaults to installing XF86Config somewhere
in /usr/X11R6/lib. When it asks you to save the XF86Config file, you
might want to save it in /etc/X11/XF86Config which is the Debian default.
Again, someone please correct me if I made a mistake somewhere in this
message since I haven't done this in a while. Thanks.
I know this isn't the nicest solution but if there isn't a bo package for
XF86-3.3.2 then you might want to just download the binaries as I outlined
above.
Good luck
-Ossama
__
Ossama Othman [EMAIL PROTECTED]
--- PGP Keys ---
Public: http://astrosun.tn.cornell.edu/staff/othman/OO_PUBLIC.asc
REVOKED: http://astrosun.tn.cornell.edu/staff/othman/OO_REVOKED.asc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Libc5 vs Libc6: help me, please!
Nuno Carvalho [EMAIL PROTECTED] writes: When I try to install libc6 I get messages of dependencies with libc5! :-( I can't remove the libc5 package! How should I install libc6 ? The way I did it was to upgrade my libc5 to the latest package version (i.e. from hamm) first. (libc6 conflicts with earlier libc5 but not latest packaging.) Since writing this message, I find that there's a libc5-libc6 mini-FAQ. See http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html or get it from ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini-HOWTO.txt. pjm. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Libc5 vs Libc6: help me, please!
Nuno Carvalho wrote: Hi, I'm trying to install KDE, and some others things, but it needs libc6. When I try to install libc6 I get messages of dependencies with libc5! :-( I can't remove the libc5 package! No, you must first upgrade libc5. The full instructions are in the libc5-libc6 mini HOWTO, currently to be found in Developers' Corner at hhtp://www.debian.org. You can also use autoup.sh (same location) to do the process automatically. (If you download by ftp, get the packages first.) How should I install libc6 ? Thank's! Regards, Nuno Carvalho P.S. I don't have too much experience with librarys! :-(( --- Nuno Emanuel F. Carvalho Department of Informatics Engineering University of Coimbra PORTUGAL [EMAIL PROTECTED] http://student.dei.uc.pt/~nemanuel --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] g -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Libc5 vs Libc6: help me, please!
Hi, I'm trying to install KDE, and some others things, but it needs libc6. When I try to install libc6 I get messages of dependencies with libc5! :-( I can't remove the libc5 package! How should I install libc6 ? Thank's! Regards, Nuno Carvalho P.S. I don't have too much experience with librarys! :-(( --- Nuno Emanuel F. Carvalho Department of Informatics Engineering University of Coimbra PORTUGAL [EMAIL PROTECTED] http://student.dei.uc.pt/~nemanuel --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc5 (not libc6) by default? (was: CDE)
Alex Yukhimets [EMAIL PROTECTED] writes: I'm sure there is not the problem that the package is not *.deb. The problem here is that it was not linked with specific major version of libc. If you try to do ldd /path/to/some/CDE/executable/or/library I bet that you'll get dependence on libc6. Same thing happens to my Motif: libXm.so.2.0 seems to depend on libc6 while both of them used libc5 headers. The solution is to configure shared lib loader to use libc5 by default. If somebody can tell me how to do it, I would be very gratefull. Two things you can try: 1. Put /usr/X11R6/lib right at the end of /etc/ld.so.conf. (Is this done in the upgrade process? I'm sure it's made things work for me that didn't previously.) 2. Check for the path hardcoded into the binary; try: strings /path/to/dtlogin | grep '/usr/X11R6/lib' Nothing should be printed. This caused a problem with the Debian packages of fvwm2 and other programs a few months ago. I don't know how you'll get it to load libc5 by default; I haven't had this problem. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ GNU GPL: The Source will be with you... always. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 (not libc6) by default? (was: CDE)
On Tue, 10 Feb 1998, Alex Yukhimets wrote: I just tried installing the RedHat CDE package into a Debian unstable system. It was compiled with an oldish version of libc5 and not libc6 which the unstable release is based on. I was successful in converting the rpm files to deb files using alien. Unfortunately, when I tried to start CDE using dtlogin, I received a core dump. I received no response from RedHat technical support. I'm sure there is not the problem that the package is not *.deb. The problem here is that it was not linked with specific major version of libc. If you try to do ldd /path/to/some/CDE/executable/or/library I bet that you'll get dependence on libc6. Same thing happens to my Motif: libXm.so.2.0 seems to depend on libc6 while both of them used libc5 headers. The solution is to configure shared lib loader to use libc5 by default. If somebody can tell me how to do it, I would be very gratefull. No that wasn't the problem. ldd does show a dependency on libc5. -- Jean Pierre -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Upgrading from libc5 to libc6
I'm upgrading a fairly new bo system to hamm following the libc5 to libc6 howto. I've run into a problem when it comes to install libc6_2.0.6-3.deb as it reports a conflict with libc5. So I did as the HOWTO says and downloaded the older version of libc5 from the link in the HOWTO - libc5_5.4.33-3.deb and installed that, and repeated to install the new libc6, but still got the conflict. Where should I go from here, would it be safe to force the install? Is it safe to shutdown my system considering I've already upgraded ldso, but have been unable to upgrade to libc6 yet. Thanks for any info jason [EMAIL PROTECTED] Get free e-mail and a permanent address at http://www.netaddress.com -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
libc5 (not libc6) by default? (was: CDE)
I just tried installing the RedHat CDE package into a Debian unstable system. It was compiled with an oldish version of libc5 and not libc6 which the unstable release is based on. I was successful in converting the rpm files to deb files using alien. Unfortunately, when I tried to start CDE using dtlogin, I received a core dump. I received no response from RedHat technical support. Its a real pity that Debian doesn't have support for the primary window enviornment used by all commercial UNIX vendors. Maybe we should try to work directly with TriTeal, the suppliers of CDE for RedHat, a seperate package for Debian. I'm sure there is not the problem that the package is not *.deb. The problem here is that it was not linked with specific major version of libc. If you try to do ldd /path/to/some/CDE/executable/or/library I bet that you'll get dependence on libc6. Same thing happens to my Motif: libXm.so.2.0 seems to depend on libc6 while both of them used libc5 headers. The solution is to configure shared lib loader to use libc5 by default. If somebody can tell me how to do it, I would be very gratefull. Thanks. Alex Y. -- _ _( )_ ( (o___ +---+ | _ 7 |Alexander Yukhimets| \()| http://pages.nyu.edu/~aqy6633/ | / \ \ +---+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: another question about upgrading libc5 to libc6
Scott Ellis wrote: Maybe someone else has an easier way? Yes, there is now a script a http://stormcrow.ml.org/pub/debian/autoup/autoup.sh that will download all the necessary core packages mentioned in my upgrade howto, remove all the old -dev packages, and install the new stuff in the exact order necessary. Huh.. I just tried this on a machie at home, and the script failed because debian/hamm/hamm/binary-i386/base/ contains no libc5*.deb files. On any mirror that I could find. Tim -- (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps Very Pete Townshendish. Who? Exactly. -- Anon ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: another question about upgrading libc5 to libc6
Hello everyone, my experience with the upgrade howto from debian proved to be an invaluable asset. U had to dpkg --purge the development packages manually using dpkg. That was ok. I downloaded the entire hamm distribution and I have installed the base, admin and am starting on the lib and development directories. I must say that this went very smoothly. I have not tried to compile anything yet. I want to recompile my kernel with libc6 to see how it goes. I am quite familiar with dpkg and like it. Thanks to everybody who helped me in the last few days. I'm quite unsure to do the upgrade because of all the trouble that people were having when upgrading. Oh well I just wanted to let debian-user know of one success story. Paul On Wed, 28 Jan 1998, Tim Sailer wrote: Scott Ellis wrote: Maybe someone else has an easier way? Yes, there is now a script a http://stormcrow.ml.org/pub/debian/autoup/autoup.sh that will download all the necessary core packages mentioned in my upgrade howto, remove all the old -dev packages, and install the new stuff in the exact order necessary. Huh.. I just tried this on a machie at home, and the script failed because debian/hamm/hamm/binary-i386/base/ contains no libc5*.deb files. On any mirror that I could find. Tim -- (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps Very Pete Townshendish. Who? Exactly. -- Anon ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: another question about upgrading libc5 to libc6
On Wed, 28 Jan 1998, Tim Sailer wrote: Huh.. I just tried this on a machie at home, and the script failed because debian/hamm/hamm/binary-i386/base/ contains no libc5*.deb files. On any mirror that I could find. Try looking in oldlibs/ Tip: in directory binary-i386, type dir */package* to show the subdir that holds the package. Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: another question about upgrading libc5 to libc6
On Wed, 28 Jan 1998, Tim Sailer wrote: Scott Ellis wrote: Maybe someone else has an easier way? Yes, there is now a script a http://stormcrow.ml.org/pub/debian/autoup/autoup.sh that will download all the necessary core packages mentioned in my upgrade howto, remove all the old -dev packages, and install the new stuff in the exact order necessary. Huh.. I just tried this on a machie at home, and the script failed because debian/hamm/hamm/binary-i386/base/ contains no libc5*.deb files. On any mirror that I could find. I think libc5 got moved from base to oldlibs -- Scott K. Ellis [EMAIL PROTECTED] http://www.gate.net/~storm/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: another question about upgrading libc5 to libc6
Joost Kooij wrote: On Wed, 28 Jan 1998, Tim Sailer wrote: Huh.. I just tried this on a machie at home, and the script failed because debian/hamm/hamm/binary-i386/base/ contains no libc5*.deb files. On any mirror that I could find. Try looking in oldlibs/ Tip: in directory binary-i386, type dir */package* to show the subdir that holds the package. :) Yes, I actually knew that, but the script didn't. I guess that was the point I was trying to make. Sorry about being obscure. Tim -- (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps Very Pete Townshendish. Who? Exactly. -- Anon ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
upgrading from libc5 to libc6
hello everyone, I have a bo system and want a hamm system. I got the howto to do the upgrade, but i can't find libc6_2.0.5c-0.1 that it says you need. It does not say anywhere where to get it. Any help would be greatly appreciated. Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: upgrading from libc5 to libc6
On Tue, 27 Jan 1998, Paul McDermott wrote: hello everyone, I have a bo system and want a hamm system. I got the howto to do the upgrade, but i can't find libc6_2.0.5c-0.1 that it says you need. It does not say anywhere where to get it. Any help would be greatly appreciated. libc6 is now up to version 2.0.6-3. I recomend checking out http://stormcrow.ml.org/pub/debian/autoup/ for a script to perform the core actions described in the howto automagically. -- Scott K. Ellis [EMAIL PROTECTED] http://www.gate.net/~storm/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
another question about upgrading libc5 to libc6
Hello everybody, i am currently following the mini howto on how to upgrade from libc5 to libc6. Everything is going smoothly, up to this point. In part 3 under development it says to purge libc5 *--dev* I know how to use dpkg, and there is an option --purge. My question is how do you perge all of libc5 development packages. Thanking you in advance. Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: another question about upgrading libc5 to libc6
Hello everybody, i am currently following the mini howto on how to upgrade from libc5 to libc6. Everything is going smoothly, up to this point. In part 3 under development it says to purge libc5 *--dev* I know how to use dpkg, and there is an option --purge. My question is how do you perge all of libc5 development packages. Thanking you in advance. I think that you have to do it in a fairly manual way. For instance: # dpkg -l \*-dev [...a list of all the -dev packages...] # dpkg --purge all-the-packages-listed-above Maybe someone else has an easier way? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: another question about upgrading libc5 to libc6
On 27 Jan 1998, Ben Pfaff wrote: Hello everybody, i am currently following the mini howto on how to upgrade from libc5 to libc6. Everything is going smoothly, up to this point. In part 3 under development it says to purge libc5 *--dev* I know how to use dpkg, and there is an option --purge. My question is how do you perge all of libc5 development packages. Thanking you in advance. I think that you have to do it in a fairly manual way. For instance: # dpkg -l \*-dev [...a list of all the -dev packages...] # dpkg --purge all-the-packages-listed-above Maybe someone else has an easier way? Yes, there is now a script a http://stormcrow.ml.org/pub/debian/autoup/autoup.sh that will download all the necessary core packages mentioned in my upgrade howto, remove all the old -dev packages, and install the new stuff in the exact order necessary. -- Scott K. Ellis [EMAIL PROTECTED] http://www.gate.net/~storm/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: version 0.8 of libc5 to libc6 auto-upgrade script
On Mon, 19 Jan 1998, Alexander Kushnirenko wrote: Hi, Craig! I updated libc5 to libc6 on 2 computers (Debian 1.3 was installed in Nov-97 and Feb-97) using your script. Worked fine for me. glad to hear it. Updating the rest of the packages with dselect is still quite painful. worse than ever now :-). there are over 1700 packages in hamm (counting main, contrib, non-free, and non-US)...several hundred more than in bo. Thank you, you're welcome. upgrading to hamm isn't for everyone yet (not for the faint of heart), but i'm glad my script helps those who chose to take the plunge. if you ran into any problems at all, please report them to debian-testing@lists.debian.org i would recommend to anyone who does choose to upgrade to hamm that they take notes and report any problems to that address. craig -- craig sanders -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: version 0.8 of libc5 to libc6 auto-upgrade script
On Tue, Jan 20, 1998 at 10:05:03PM +1100, Craig Sanders wrote: worse than ever now :-). there are over 1700 packages in hamm (counting main, contrib, non-free, and non-US)...several hundred more than in bo. Just FYI, there are only 460 odd in main in buzz! That's progress ... Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
On Mon, 19 Jan 1998, Tom Ed White wrote: Is it possible to use libc5 and libc6 together? There are a couple of programs in hamm that I would like to try, but I heard somewhere that the two libs can't both be installed. http://www.gate.net/~storm/FAQ/ -- Scott K. Ellis [EMAIL PROTECTED] http://www.gate.net/~storm/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: version 0.8 of libc5 to libc6 auto-upgrade script
Hi, Craig! I updated libc5 to libc6 on 2 computers (Debian 1.3 was installed in Nov-97 and Feb-97) using your script. Worked fine for me. Updating the rest of the packages with dselect is still quite painful. Thank you, Sasha. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
version 0.8 of libc5 to libc6 auto-upgrade script
I just ran this script on an old system (somewhere between rex and bo) with lots of -dev packages installed. found and fixed two bugs. - libc6 conflicts with libpthread0 - i made a typo... PKGS_GPP instead of PKGS_LIBGPP. - some old version of perl's postrm didn't delete a .packlist file from /usr/lib/perl5/i486-linux/5.003/auto/Mail/.packlist. check for it and delete if found before installing perl. apart from those problems, it ran through cleanly. i think it's nearly finished (but i said that around version 0.2 didn't I :-) ---cut here--- #! /bin/sh DPKG=`which dpkg` LDCONFIG=`which ldconfig` # uncomment for debugging #set -x #DPKG=echo dpkg #LDCONFIG=echo LDCONFIG # upgrade a libc5 (bo) machine to libc6 (hamm). # based on Scott Ellis' excellent Debian libc5 to libc6 Mini-HOWTO # document at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html # Author: Craig Sanders [EMAIL PROTECTED] # # Copyright Status: This script is hereby placed in the public domain # # Revision History: # v0.0: 1998-01-08 (morning) # - a rough transcript of scott's doc and my own experiences # v0.1: 1998-01-08 (night) # - a few bugfixes # - i got unlazy and put in the right subdirectories for each package. # should run a lot faster. # - now checks for failure at critical points and exits with a different # exit code for each failure. # - now uses 'binary-$(dpkg --print-installation-architecture)' instead # of 'binary-i386'. # v0.2: 1998-01-09 # - fixed the perl-base/perl install (thanks Lindsay!) # - improved the DEVPACKAGES=$(dpkg --get-selections...) and added -dbg # packages. # v0.3: 1998-01-09 (p.m.) # - fixed some directories # - changed -iB to -iBE so that if the script fails and is run again # it will not disturb things already in place. # - added a final dpkg --configure --pending. # - sanity check that we are in the right place added # v0.4: 1998-01-10 (Igor Grobman) # - made it possible to place all packages in current dir. # - added -pic packages to removal list. # - make sure dpkg-dev does not get selected for removal. # - moved dpkg-ftp and dpkg-mounted to the end. #v0.5: 1998-01-10 (Igor Grobman) # - added a note about upgrading libraries #v0.6: 1998-01-11 (Craig Sanders) # - restructured code to avoid code duplication. # - cleaned up a few things # - prints advisory notes telling user what's happening. # - added some more instructions on what to do about development packages. # - added code to guess some obvious locations for the mirror, otherwise # ask user. #v0.7: 1998-01-11 (Craig Sanders) # - uh oh. i hard-coded in binary-i386. quick...better release another # version before James notices. #v0.8: 1998-01-11 (Craig Sanders) # - added libpthread0 to the remove list. # - fixed PKGS_LIBGPP (i mistyped it as PKGS_GPP) # - some old version of perl's postrm didn't delete a .packlist file # from /usr/lib/perl5/i486-linux/5.003/auto/Mail/.packlist. check for # it and delete if found before installing perl. # # TODO: (probably by somebody else. this script is mostly good enough imo) # - this script _still_ needs more error checking :-) ARCH=binary-$(dpkg --print-installation-architecture) PKGS_LIBC6=base/ldso_*.deb base/libc5_*.deb base/libc6_*.deb \ base/timezones_*.deb admin/locales_*.deb PKGS_NCURSES=libs/ncurses3.0_*.deb base/ncurses3.4_*.deb PKGS_LIBRL=oldlibs/libreadline2_*.deb PKGS_LIBRLG=base/libreadlineg2_*.deb PKGS_BASH=base/bash_*.deb PKGS_LIBGPP=devel/libg++272_*.deb PKGS_DPKG=base/dpkg_*.deb utils/dpkg-dev_*.deb PKGS_LIBGDBM=base/libgdbm1_*.deb devel/libgdbmg1_*.deb PKGS_PERLBASE=base/perl-base_*.deb PKGS_PERL=interpreters/perl_*.deb PKGS_MOREDPKG=base/dpkg-ftp_*.deb admin/dpkg-mountable_*.deb cat __EOF__ This script will install the packages necessary to ensure a safe upgrade to hamm. You need to either have a local or remote mirror mounted, or have the latest versions of the following packages from hamm available in the current directory: ldso, libc5, libc6, timezones, locales, ncurses3.0, ncurses3.4, libreadline2, libreadlineg2, bash, libg++272, dpkg, dpkg-dev, dpkg-ftp, dpkg-mountable, libgdbm1, libgdbmg1, perl-base, and perl. If you are using a mirror, press 'm'. __EOF__ echo -n if you have the files in the current dir, press 'c': (m/c) read answer case $answer in m|M) # local mirror available # ask where the mirror is (this could do with some error checking) echo echo enter the full path to your local mirror of debian: echo e.g. /debian/dists/unstable/main/$ARCH/ echo TRY=/debian/dists/unstable/main/$ARCH ~ftp/debian/dists/unstable/main/$ARCH for i in $TRY ; do if [ -d $i ] ; then DEFAULT=$i fi done [ -n $DEFAULT ] echo or just hit enter to use $i. read DM [ -z $DM ] DM
Re: libc5 to libc6 auto-upgrade script
Igor Grobman wrote: This version should be close to good enough. The major change since the last one that was posted is the ability to upgrade from files in the current dir instead of a local mirror requirement. llug.sep.bnl.gov is a public nfs mount for debian. You can point the scripts there if they are net connected too. Tim -- (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps Nothing is work unless you'd rather be doing something else. - George Halas ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Compiling with libc5 under libc6 based system
I have upgraded my system to libc6 with not much troubles. Now, it seems that some programs have to be compiled under libc5 anyway. Therefore altgcc and altdev-libc5 have been loaded into the system. Now i need some documentation about how to instruct 'make' to use the alternative environment. Is there any on line reference out there? Thank you for your suggestions Paolo Pumilia --- CSTC - -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Compiling with libc5 under libc6 based system
Linux-Debian == Linux-Debian Team [EMAIL PROTECTED] writes: Linux-Debian I have upgraded my system to libc6 with not much Linux-Debian troubles. Now, it seems that some programs have to Linux-Debian be compiled under libc5 anyway. Therefore altgcc and Linux-Debian altdev-libc5 have been loaded into the system. Now Linux-Debian i need some documentation about how to instruct Linux-Debian 'make' to use the alternative environment. Is there Linux-Debian any on line reference out there? Thank you for your Linux-Debian suggestions It's actually quite simple. All you need to do is set your PATH to have /usr/i486-linuxlibc1/bin at the beginning, and then make, gcc, et all will use the -altdev packages. -- Brought to you by the letters T and M and the number 18. I put my feet on the Ottoman.. Empire. -- Moxy Fruvous Ben Gertzfield http://www.imsa.edu/~wilwonka/ Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 to libc6 auto-upgrade script
I hope this is the final version for a while. The script works here on a freshly installed bo. Watch out for line folding. --- cut here --- #! /bin/sh # upgrade a libc5 (bo) machine to libc6 (hamm). # based on Scott Ellis' excellent Debian libc5 to libc6 Mini-HOWTO # document at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html # Author: Craig Sanders [EMAIL PROTECTED] # # Copyright Status: This script is hereby placed in the public domain # # Revision History: # v0.0: 1998-01-08 (morning) # - a rough transcript of scott's doc and my own experiences # v0.1: 1998-01-08 (night) # - a few bugfixes # - i got unlazy and put in the right subdirectories for each package. # should run a lot faster. # - now checks for failure at critical points and exits with a different # exit code for each failure. # - now uses 'binary-$(dpkg --print-installation-architecture)' instead # of 'binary-i386'. # v0.2: 1998-01-09 # - fixed the perl-base/perl install (thanks Lindsay!) # - improved the DEVPACKAGES=$(dpkg --get-selections...) and added -dbg # packages. # v0.3: 1998-01-09 (p.m.) # - fixed some directories # - changed -iB to -iBE so that if the script fails and is run again # it will not disturb things already in place. # - added a final dpkg --configure --pending. # - sanity check that we are in the right place added # # TODO: (probably by somebody else. this script is mostly good enough imo) # - error checking # first, build up a list of installed -dev packages so that we can # remove them. remove wg-15-locale too. # # this is necessary even on machines which aren't doing libc6 # development because libc5 can't be upgraded to latest version without # removal of libc5-dev which also necessitates removal of other -dev # packages like libdb1-dev and libdl1-dev if they are installed. DEVPACKAGES=$( dpkg --get-selections | grep -v deinstall | cut -f1 | grep -- -dev$\|-dbg$ ) dpkg --remove -B $DEVPACKAGES wg15-locale || exit 1 # now install the new versions of things. Just the bare minimum to let # the user safely run dselect for the rest of the upgrade. # change this to prompt the user for the location of the debian archive. cd /debian/dists/unstable/main/binary-$(dpkg --print-installation-architecture) # sanity check that we are in the right place [ -f base/libc6_* ] || exit 9 # libc # dpkg -iBE base/ldso_*.deb base/libc5_*.deb base/libc6_*.deb \ base/timezones_*.deb admin/locales_*.deb || exit 2 # libreadline, ncurses, and bash # dpkg -iBE libs/ncurses3.0_*.deb base/ncurses3.4_*.deb || exit 3 dpkg -iBE oldlibs/libreadline2_*.deb || exit 4 dpkg -iBE base/libreadlineg2_*.deb || exit 5 # paranoia says run ldconfig NOW. don't laugh, i've needed to do this on # some libc5-libc6 upgrades. i know that the postinst scripts for the # libs are supposed to do it but ldconfig dpkg -iBE base/bash_*.deb || exit 6 # new dpkg # dpkg -iBE devel/libg++272_*.deb || exit 7 dpkg -iBE base/dpkg_*.deb utils/dpkg-dev_*.deb # strictly speaking, dpkg-ftp and dpkg-mountable are not essential to # upgrade right now but they're both very useful. dpkg -iBE base/dpkg-ftp_*.deb admin/dpkg-mountable_*.deb # perl # dpkg -iBE base/libgdbm1_*.deb devel/libgdbmg1_*.deb || exit 8 # paranoia says run ldconfig now. ldconfig dpkg -iBE base/perl-base_*.deb || exit 9 dpkg -iBE interpreters/perl_*.deb # paranoia says to run this at the end dpkg --configure --pending # paranoia says: run sync, so lets do it :-) sync ; sync ; sync # the user can now run dselect and select any -dev packages they want # (and other packages too, of course :-) more __EOF__ libc6 is now installed. Now run dselect to upgrade the rest of your system. When that's done, reboot with shutdown -r now for the utmp/wtmp wrapper functions in the upgraded libc5 to take effect. BTW, if you aren't using it already, check out dselect's mountable access method. It's much faster than the standard mounted method, and it logs everything that happens in /var/log/dpkg-mountable. You'll want to set Allow overwriting repeated files? to yes, and for extra speed set Enable MD5 checksumming? to no. Finally, remember to fix up wtmp and utmp, otherwise last and who and sac etc wont work. here's what Miquel van Smoorenburg [EMAIL PROTECTED] had to say about this recently in debian-user mailing list: 1. You need to update ALL your packages to hamm 2. Reboot if you haven't done that already 3. You need to move the wtmp file and truncate the utmp file: cd /var/log mv wtmp wtmp.libc5 touch wtmp cd /var/run cp /dev/null utmp 4. You might want to reboot again to make sure This is because the struct utmp and thus the utmp and wtmp databases are different between libc5 and libc6 __EOF__ ---cut here--- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen [EMAIL PROTECTED] Perth, Western
Re: libc5 to libc6 auto-upgrade script
On Fri, 9 Jan 1998, Lindsay Allen wrote: I hope this is the final version for a while. The script works here on a freshly installed bo. Watch out for line folding. # sanity check that we are in the right place [ -f base/libc6_* ] || exit 9 9 is already used for perl_base failure. either renumber all the exit codes or just use 100. this check should probably be done even before the script removes the -dev and -dbg packages. craig -- craig sanders -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 to libc6: purge or install
On Tue, 23 Dec 1997, Jameson Burt wrote: This seems the correct approach. So, the libc5-libc6-Mini-HOWTO should say not just The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. o ldso_1.9.5-1 o libc6_2.0.4-1 but should also include something like o ldso_1.9.5-1 o libc5_5.4.38 from unstable hamm ** o libc6_2.0.4-1 The need for the above appeared to me again today, in my office, when a colleague tried to install Debian Linux. As recommended in the HOWTO, he did not use dselect. However, haveing followed the libc5-libc6-Mini-HOWTO two times, he is about to try installing Debian Linux for the third time in one day. The first recommended package ldso_1.9.6-2 installed properly. The second package libc6_2.0.5c-0.1 failed to install, responding that dpkg COULD NOT REMOVE libc5! He knew not to use a -force option, so he used a --purge option on libc5. He followed this by again having dpkg install libc6_2.0.6c-0.1. All seemed well, except that the purging of libc5 removed /lib/libreadline.so.2, so he could no longer log on --time to reinstall Debian Linux. I plan on mentioning this when I update the howto over the holidays. I am also going to plaster said howto with large warnings for DO NOT PURGE LIBC5 WHEN UPGRADING. DO NOT USE --force FOR ANY REASON when doing the libc5-libc6 upgrade. (not shouting at you, just at anyone else out there considering it) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 to libc6: purge or install
Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their operating systems. A few changes could save a few more people. When a person ruins zher operating system by badly adding packages from hamm, zhe consumes weeks of time. You might save tens of people a hundred wasted hours each. Didn't save me. I followd the instructions on an old test system here and STILL managed to blow it up. I was tired and cranky ... got to the part where I manuall did a dpkg on libc6 ... but it conflicts with libc5 ... (dpkg -i libc6_2.0.4-1.i386.deb) so without thinking I did a dpkg -r --force depends libc5 thinking that my next command would be to install libc6 ... there was no next command on that system. the libc5 from hamm doesn't conflict with libc6. So, you should have installed the libc5 from hamm, before installing libc6. I'm sure that is mentioned in the libc5-libc6-mini-howto. This seems the correct approach. So, the libc5-libc6-Mini-HOWTO should say not just The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. o ldso_1.9.5-1 o libc6_2.0.4-1 but should also include something like o ldso_1.9.5-1 o libc5_5.4.38 from unstable hamm ** o libc6_2.0.4-1 The need for the above appeared to me again today, in my office, when a colleague tried to install Debian Linux. As recommended in the HOWTO, he did not use dselect. However, haveing followed the libc5-libc6-Mini-HOWTO two times, he is about to try installing Debian Linux for the third time in one day. The first recommended package ldso_1.9.6-2 installed properly. The second package libc6_2.0.5c-0.1 failed to install, responding that dpkg COULD NOT REMOVE libc5! He knew not to use a -force option, so he used a --purge option on libc5. He followed this by again having dpkg install libc6_2.0.6c-0.1. All seemed well, except that the purging of libc5 removed /lib/libreadline.so.2, so he could no longer log on --time to reinstall Debian Linux. -- Jim Burt, NJ9L, Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.mnsinc.com/jameson [EMAIL PROTECTED] If merely 'feeling good' could decide, drunkenness would be the supremely valid human experience. --William James, Varieties of Religious Experience -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Installing Unstable, avoid upgrading from libc5 to libc6?
-BEGIN PGP SIGNED MESSAGE- Timothy D.Webster wrote: Used wget to mirror debian ftp site, only i386, no source. Did you mirror binary-i386 and binary-all? (You need both). If you mirrored just binary-i386, did you use wget --retr-symlinks? (You don't need binary-all if you get the files the symlinks point to instead of the symlinks). -BEGIN PGP SIGNATURE- Version: 2.6.3i Charset: latin1 iQCVAgUBNJ/rjSqK7IlOjMLFAQHDFgQAgNdDStAE3fRCI3nwKIyzH3RbDLEdE6Oj QasA/eBNtGyP+uDIA4QlsSkNX8NU24qiNigZ3YPpW11tNyYObaNKX3sMb1pkvclH CYdjEj0AfnlWdruEmgoLgSjDzc2kLoj/QG4FGUentzpSozCHSv6crstXNtgVhoQL VFlQNAIZeak= =kXW4 -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
upgrading from libc5 to libc6?
hi everybody is there a howto on upgrading from libc5 to libc6. When I do a dpkg -i of libc6.deb it tells me that it conflicts with libc5. Any suggestions? Where is the howto? I've been looking in the archives but could not see any reference to it. Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RE: upgrading from libc5 to libc6?
Look at http://www.gate.net/~storm for the libc5 to libc6 howto. On 17-Dec-97 [EMAIL PROTECTED] wrote: hi everybody is there a howto on upgrading from libc5 to libc6. When I do a dpkg -i of libc6.deb it tells me that it conflicts with libc5. Any suggestions? Where is the howto? I've been looking in the archives but could not see any reference to it. Paul -- Please do not look directly into laser with remaining eye. E-Mail: Mark Ciciretti [EMAIL PROTECTED] Date: 17-Dec-97 Time: 12:52:02 -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: upgrading from libc5 to libc6?
On Wed, 17 Dec 1997, Paul McDermott wrote: hi everybody is there a howto on upgrading from libc5 to libc6. When I do a dpkg -i of libc6.deb it tells me that it conflicts with libc5. Any suggestions? Where is the howto? I've been looking in the archives but could not see any reference to it. http://www.gate.net/~storm/FAQ/ -- Scott K. Ellis [EMAIL PROTECTED] http://www.gate.net/~storm/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Installing Unstable, avoid upgrading from libc5 to libc6?
I have been trying to install unstable, rather than stable. In hopes that I might be able to avoid some of the libc5 to libc6 upgrade head aches. Used wget to mirror debian ftp site, only i386, no source. Everything works fine; Access: OK, I linked ln -s debian/hamm/hamm debian/hamm/stable Update: OK finds and extracts /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/Packages.gz /var/lib/dpkg/methods/mnt/debian/hamm/contrib/binary-i386/Packages.gz /var/lib/dpkg/methods/mnt/debian/hamm/non-free/binary-i386/Packages.gz Select: OK Install: FAILS!!! Can anyone tell me what these errors mean, and how to fix my installation procedure??? Tim. Help!! See below Looking for part 1 of dpkg-perl ... find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/iconc_9.1-1.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/icont_9.1-1.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/iconx_9.1-1.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/ilu-base_2.0.0.0-2.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/ilu-dev.0.0.0-2.deb: No such file or directory /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/dpkg-perl_0.1-2.deb Running dpkg -iB for dpkg-perl ... find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/ilu-doc.0.0.0-2.deb: No such file or directory etc 5113 files and directories currently installed.) Preparing to replace dpkg-perl 0.1-2 (using .../devel/dpkg-perl_0.1-2.deb) ... find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/libpwdb-dev_0.54preD-1.deb: No such file or directory Unpacking replace dpkg-perl ... etc installation script returned error exit status 1. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Subject: Installing Unstable, avoid upgrading from libc5 to libc6?
I have been trying to install unstable, rather than stable. In hopes that I might be able to avoid some of the libc5 to libc6 upgrade head aches. Used wget to mirror debian ftp site, only i386, no source. Everything works fine; Access: OK, I linked ln -s debian/hamm/hamm debian/hamm/stable Update: OK finds and extracts /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/Packages.gz /var/lib/dpkg/methods/mnt/debian/hamm/contrib/binary-i386/Packages.gz /var/lib/dpkg/methods/mnt/debian/hamm/non-free/binary-i386/Packages.gz Select: OK Install: FAILS!!! Can anyone tell me what these errors mean, and how to fix my installation procedure??? Tim. Help!! See below Looking for part 1 of dpkg-perl ... find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/iconc_9.1-1.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/icont_9.1-1.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/iconx_9.1-1.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/ilu-base_2.0.0.0-2.deb: No such file or directory find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/ilu-dev.0.0.0-2.deb: No such file or directory /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/dpkg-perl_0.1-2.deb Running dpkg -iB for dpkg-perl ... find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/ilu-doc.0.0.0-2.deb: No such file or directory etc 5113 files and directories currently installed.) Preparing to replace dpkg-perl 0.1-2 (using .../devel/dpkg-perl_0.1-2.deb) ... find: /var/lib/dpkg/methods/mnt/debian/hamm/stable/binary-i386/devel/libpwdb-dev_0.54preD-1.deb: No such file or directory Unpacking replace dpkg-perl ... etc installation script returned error exit status 1. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Debian libc5 to libc6 Mini-HOWTO - purging -dev packages
Section 3. of the Mini-HOWTO says: If you wish to do libc6 development, you should first purge all the '-dev' packages on your system Please confirm that this does not include dpkg-dev_1.4.0.19.deb, which was installed under Section 2.3. Bob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO - purging -dev packages
On Wed, 10 Dec 1997, Robert D. Hilliard wrote: Section 3. of the Mini-HOWTO says: If you wish to do libc6 development, you should first purge all the '-dev' packages on your system Please confirm that this does not include dpkg-dev_1.4.0.19.deb, which was installed under Section 2.3. Correct, you don't need to purge dpkg-dev -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
libc5 to libc6
Hi, A friend wants to upadate from libc5 to 6 . I have done that some time ago and can't rember the exact order . Can somebody let me know of the http address for libc5 tp libc6 HOWTO ? Thanks George --- George Kapetanios Churchill College Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED] U.K. WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 to libc6
G. Kapetanios hat gesagt: // G. Kapetanios wrote: Hi, A friend wants to upadate from libc5 to 6 . I have done that some time ago and can't rember the exact order . Can somebody let me know of the http address for libc5 tp libc6 HOWTO ? - From the Howto: - 1.2. Finding updates The latest version of this Mini-HOWTO should be available in the following locations: o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.txt o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.sgml o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini-HOWTO.txt o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini- HOWTO.html.tar.gz -- Yours a href=http://www.koeln-online.de/einblick/; Frank Barknecht Das Koelner Stadt- und Unimagazin - /a -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RE: libc5 to libc6: purge or install *-dev?
On Sun, 16 Nov 1997, George Bonser wrote: Didn't save me. I followd the instructions on an old test system here and STILL managed to blow it up. I was tired and cranky ... got to the part where I manuall did a dpkg on libc6 ... but it conflicts with libc5 ... (dpkg -i libc6_2.0.4-1.i386.deb) so without thinking I did a dpkg -r --force depends libc5 thinking that my next command would be to install libc6 ... there was no next command on that system. Well, this seems to be a great example of the Golden Rule For Moving From Libc5 To Libc6: Do NOT use --force on dpkg, the conflicts are there for a good reason! snip Seems kind of a chicken and egg problem to me right now but I will get it sorted out, cant install libc6 'cause it conficts with libc5, can't remove libc5, I am considering the Kavorkian method of point-and-click system admin at this point. As with many libraries that exist in a libc5-version and a libc6-version: First upgrade the libc5-version to the one in unstable and then install the libc6-version. If you'd just point dselect to unstable, you'd have no problem with this. If you do it with dpkg only, you'll have to figure out all dependencies and conflicts by yourself. I am sure this is in the libc5-libc6-Mini-HOWTO. Or else it should be. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
libc5 to libc6: purge or install *-dev?
The key document for upgrading from stable bo to unstable hamm is libc5-libc6-Mini-HOWTO.txt. I have botched the upgrade from rex to bo, and the upgrade from bo to hamm. I botched the upgrades because I installed programs from the unstable version over several months successfully, then one day installed a key program like dpkg without looking for or noticing any upgrade notes. The web page entrance into the packages, http://www.debian.org/packages.html says could therefore break your system This message could be more helpful. How about a link to libc5-libc6-Mini-HOWTO.txt Also, how about putting in the file /debian/hamm/.message a warning as one enters this unstable directory via ftp. Again, such a warning ought to mention libc5-libc6-Mini-HOWTO.txt. Since this file is so crucial to moving from bo to hamm, please consider making a link to it with a more eye-catching name like README.UPGRADE-WARNING. Another useful comment in libc5-libc6-Mini-HOWTO.txt might be something like You will probably not completely ruin your current Debian distribution by installing from the hamm distribution, unless you install ldso, bash, libc, or dpkg. In the debian-users mail-list, one person followed libc5-libc6-Mini-HOWTO.txt by trying to purge all *-dev packages, but zhe ran across so many dependencies that zhe stopped. I tried the same with futility. Is it really necessary to purge the *-dev packages? Can't everyone just find the appropriate package to upgrade these *-dev packages, then install them as a way to rid the old *-dev packages? Also, not all packages in development directories have *-dev endings. Should your comment in section 3 of your document refer not just to *-dev packages but also to any package in a development directory? For example, I suppose no major problems arise from the old devel/libc5-dbg_5.4.33-6.deb If other development packages are not so critical, you might state that. Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their operating systems. A few changes could save a few more people. When a person ruins zher operating system by badly adding packages from hamm, zhe consumes weeks of time. You might save tens of people a hundred wasted hours each. -- Jim Burt, NJ9L, Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.mnsinc.com/jameson If merely 'feeling good' could decide, drunkenness would be the supremely valid human experience. --William James, Varieties of Religious Experience -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RE: libc5 to libc6: purge or install *-dev?
Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their operating systems. A few changes could save a few more people. When a person ruins zher operating system by badly adding packages from hamm, zhe consumes weeks of time. You might save tens of people a hundred wasted hours each. Didn't save me. I followd the instructions on an old test system here and STILL managed to blow it up. I was tired and cranky ... got to the part where I manuall did a dpkg on libc6 ... but it conflicts with libc5 ... (dpkg -i libc6_2.0.4-1.i386.deb) so without thinking I did a dpkg -r --force depends libc5 thinking that my next command would be to install libc6 ... there was no next command on that system. Believe me, I am spitting nails right now. Since I can not seem to find any way of installing the new distribution from scratch, only upgrading from stable, I am more than a little frustrated. I am reloading the stable base on that system and am going to upgrade the default installed packages to the versions on the ftp site and move my dpkg status file from yesterday back to the current one and hope for the best. In other words, I am installing base OVER my current install, will upgrade the base packages back to where they were, move the status file and hope I am back to where I was before I screwed up. Seems kind of a chicken and egg problem to me right now but I will get it sorted out, cant install libc6 'cause it conficts with libc5, can't remove libc5, I am considering the Kavorkian method of point-and-click system admin at this point. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 to libc6: purge or install *-dev?
Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their operating systems. A few changes could save a few more people. When a person ruins zher operating system by badly adding packages from hamm, zhe consumes weeks of time. You might save tens of people a hundred wasted hours each. Didn't save me. I followd the instructions on an old test system here and STILL managed to blow it up. I was tired and cranky ... got to the part where I manuall did a dpkg on libc6 ... but it conflicts with libc5 ... (dpkg -i libc6_2.0.4-1.i386.deb) so without thinking I did a dpkg -r --force depends libc5 thinking that my next command would be to install libc6 ... there was no next command on that system. the libc5 from hamm doesn't conflict with libc6. So, you should have installed the libc5 from hamm, before installing libc6. I'm sure that is mentioned in the libc5-libc6-mini-howto. -- joost witteveen, [EMAIL PROTECTED] Potentially offensive files, part 5: /dev/random. `head -c 4 /dev/random` may print 4-letter words (once every approx 4e8 tries). -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RE: libc5 to libc6: purge or install *-dev?
Þann 16-Nov-97 skrifar Jameson Burt: Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their operating systems. A few changes could save a few more people. When a person ruins zher operating system by badly adding packages from hamm, zhe consumes weeks of time. You might save tens of people a hundred wasted hours each. That's a really good point, one that was needed... But *notice*, that it is also possible to break your system by upgrading in unstable (hamm)... Here are two issues, from hamm Locales, when a program that is using glibc does setlocale, it does not get it's locale information from the localedata that comes with glibc (namely /usr/share/i18n/locales), but rather takes it from the older libc5 localeinfo /usr/share/locales (not that *that* really matters, but it raises a question as to wether *other* functions in glibc have an _overrride_ value). Many Unix programs are really careless about memory allocations, now many programs will get 'SIGSEGV' and break, and the error occurs inside free(), as free is called with a stray pointer either from a library or from the program... this is because glibc has runtime options that allows well constructed programs to use malloc and have it fast, but also to set it secure for other programs. And a lot of libraries and programs aren't well constructed... and the default is for malloc to be _fast_ :( ...and two issues concerning GNU C++, The C++ package in hamm is not compiled with setlocale functioning. So, if you do setlocale in your program, and then 'printf(%.2f, value)' your value will not print 100,00 even if your decimal point is set to ','... as it should do. And using 'malloc' inside a C++ program, will corrupt it and _may_ cause it to SIGSEGV at some point... Orn Einar Hansen [EMAIL PROTECTED] [EMAIL PROTECTED] voice+fax; +46 035 217194 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 to libc6: purge or install *-dev?
Maybe I have an old version ... at the very end it finally mentiones the conflict. the last item in the howto. I think it should be moved up to where the lists of packages you need are mentioned. On 16-Nov-97 joost witteveen wrote: I'm sure that is mentioned in the libc5-libc6-mini-howto. -- joost witteveen, [EMAIL PROTECTED] Potentially offensive files, part 5: /dev/random. `head -c 4 /dev/random` may print 4-letter words (once every approx 4e8 tries). -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Debian libc5 to libc6 Mini-HOWTO (regular posting)
Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] $Id: libc5-libc6-Mini-HOWTO.sgml,v 2.9 1997/10/14 02:46:50 storm Exp $ 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Updated note about /etc/nsswitch.conf o Note about vthunk change with glibc 2.0.5c. o Seperated bash upgrade from required upgrade. o Note on how to upgrade via dpkg-ftp. o Notes about NIS and libgdbm (perl) issues. o Note about libc6-based e2fsck being bad for large partitions. 1.2. Finding updates The latest version of this Mini-HOWTO should be available in the following locations: o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.txt o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.sgml o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini-HOWTO.txt o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini- HOWTO.html.tar.gz 1.3. Copyright and Disclaimer This Mini-HOWTO is covered by the copyright of and may be further redistibuted under the same terms as other HOWTOs from the LDP. As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. o ldso_1.9.5-1 o libc6_2.0.4-1 2.2. Upgrading bash While you can install many libc6 package with just ldso and libc6, you will probably want to upgrade a few other packages as well. Since bash-2.01 fixes problems experienced with Netscape and helper applications, it is one of the more likely packages to need updated. However, it is also one of the few packages that is capable of rendering your system useless if upgraded incorrectly. Install the packages below one at a time in exactly the order listed. IMPORTANT: If you use dselect to do the initial upgrade of these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.3. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 2.4. Other Possible Conflicts Since perl is used in many package installation scripts, problems with with library upgrades may temporarily break perl, which may break other package installations. To be safe, install the new libgdbm1 and then the new libgdbmg1 packages by hand before upgrading perl. 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading to libc6_2.0.5c-0.1 Due to a change in the vthunk handling code in libc6 and libg++, you must upgrade to at least libg++272_2.7.2.8-0.1 when upgrading libc6. 4.2. Upgrading bash
libc5 vs libc6
I'm trying to delete older version(s) of tcl and Tk and install Tcl8.0 and Tk8.0 using dselect (kernel rev. 2.0.30). The problem is that Tk8 requires libc6 which conflicts with libc5 which is required by half the other applications I've got installed. Any hints? -- Phil -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 vs libc6
Phil Nitschke [EMAIL PROTECTED] writes: I'm trying to delete older version(s) of tcl and Tk and install Tcl8.0 and Tk8.0 using dselect (kernel rev. 2.0.30). The problem is that Tk8 requires libc6 which conflicts with libc5 which is required by half the other applications I've got installed. You're wrong about libc6 conflicting with libc5: blp:/raid/home/blp$ dpkg -s libc6 Package: libc6 Status: install ok installed Priority: required Section: base Installed-Size: 1421 Maintainer: Helmut Geyer [EMAIL PROTECTED] Source: glibc Version: 2.0.5c-0.1 Pre-Depends: ldso (= 1.8.10-1) Conflicts: libpthread0 (= 0.5-10) Description: The GNU C library version 2 (run-time files). Includes shared libraries needed to run programs. However, libc6-dev and libc5-dev conflict. Your programs shouldn't depend on these, however; only development libraries should. -- Ben Pfaff [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Senders of unsolicited commercial e-mail will receive free 32MB core files! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 vs libc6
Phil Nitschke wrote: I'm trying to delete older version(s) of tcl and Tk and install Tcl8.0 and Tk8.0 using dselect (kernel rev. 2.0.30). The problem is that Tk8 requires libc6 which conflicts with libc5 which is required by half the other applications I've got installed. This is know problem. All you need to do is get the libc5 from hamm which will fix this conflict. Later, David -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting, updated)
Scott Ellis [EMAIL PROTECTED] writes: 2.4. Other Possible Conflicts Since perl is used in many package installation scripts, problems with with library upgrades may temporarily break perl, which may break other package installations. To be safe, install the new libgdbm1 and then the new libgdbmg1 packages by hand before upgrading perl. can you also suggest to upgrade perl by hand!? I followed your tips, but installation breaks due to perl. After upgrading perl manually everything works fine (except the reported bugs ;-) ). Yours Christian -- Christian Leutloff, Aachen, Germany [EMAIL PROTECTED] http://www.oche.de/~leutloff/ Debian GNU/Linux 1.3.1! Mehr unter http://www.de.debian.org/ pgpGNPYmX28XC.pgp Description: PGP signature
Debian libc5 to libc6 Mini-HOWTO (regular posting, updated)
Notes on handling the new libc5 upgrade in the latest stable update are at the end. Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] $Id: libc5-libc6-Mini-HOWTO.sgml,v 2.9 1997/10/14 02:46:50 storm Exp $ 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Updated note about /etc/nsswitch.conf o Note about vthunk change with glibc 2.0.5c. o Seperated bash upgrade from required upgrade. o Note on how to upgrade via dpkg-ftp. o Notes about NIS and libgdbm (perl) issues. o Note about libc6-based e2fsck being bad for large partitions. 1.2. Finding updates The latest version of this Mini-HOWTO should be available in the following locations: o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.txt o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.sgml o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini-HOWTO.txt o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini- HOWTO.html.tar.gz 1.3. Copyright and Disclaimer This Mini-HOWTO is covered by the copyright of and may be further redistibuted under the same terms as other HOWTOs from the LDP. As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. o ldso_1.9.5-1 o libc6_2.0.4-1 2.2. Upgrading bash While you can install many libc6 package with just ldso and libc6, you will probably want to upgrade a few other packages as well. Since bash-2.01 fixes problems experienced with Netscape and helper applications, it is one of the more likely packages to need updated. However, it is also one of the few packages that is capable of rendering your system useless if upgraded incorrectly. Install the packages below one at a time in exactly the order listed. IMPORTANT: If you use dselect to do the initial upgrade of these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.3. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 2.4. Other Possible Conflicts Since perl is used in many package installation scripts, problems with with library upgrades may temporarily break perl, which may break other package installations. To be safe, install the new libgdbm1 and then the new libgdbmg1 packages by hand before upgrading perl. 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading to libc6_2.0.5c-0.1 Due to a change in the vthunk handling code in libc6 and libg++, you must
Debian libc5 to libc6 Mini-HOWTO (regular posting, updated)
-BEGIN PGP SIGNED MESSAGE- Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] $Id: libc5-libc6-Mini-HOWTO.sgml,v 2.8 1997/10/11 03:02:12 storm Exp $ 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Note about vthunk change with glibc 2.0.5c. o Seperated bash upgrade from required upgrade. o Note on how to upgrade via dpkg-ftp. o Notes about NIS and libgdbm (perl) issues. o Note about libc6-based e2fsck being bad for large partitions. 1.2. Finding updates The latest version of this Mini-HOWTO should be available in the following locations: o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.txt o http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.sgml o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini-HOWTO.txt o ftp://ftp.debian.org/pub/debian/doc/libc5-libc6-Mini- HOWTO.html.tar.gz 1.3. Copyright and Disclaimer This Mini-HOWTO is covered by the copyright of and may be further redistibuted under the same terms as other HOWTOs from the LDP. As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. o ldso_1.9.5-1 o libc6_2.0.4-1 2.2. Upgrading bash While you can install many libc6 package with just ldso and libc6, you will probably want to upgrade a few other packages as well. Since bash-2.01 fixes problems experienced with Netscape and helper applications, it is one of the more likely packages to need updated. However, it is also one of the few packages that is capable of rendering your system useless if upgraded incorrectly. Install the packages below one at a time in exactly the order listed. IMPORTANT: If you use dselect to do the initial upgrade of these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.3. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 2.4. Other Possible Conflicts Since perl is used in many package installation scripts, problems with with library upgrades may temporarily break perl, which may break other package installations. To be safe, install the new libgdbm1 and then the new libgdbmg1 packages by hand before upgrading perl. 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading to libc6_2.0.5c-0.1 Due to a change in the vthunk handling code in libc6 and libg++, you must upgrade to at least libg++272_2.7.2.8-0.1 when upgrading libc6. 4.2. Upgrading bash
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
It is in general a good advice to install first the actual lib* package, and then the appropriate lkib*g package. So it is necessary for svgalib and others. Perhaps something like this could be included in the HOWTO Thank you Marcus -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
On Tue, 7 Oct 1997 [EMAIL PROTECTED] wrote: It is in general a good advice to install first the actual lib* package, and then the appropriate lkib*g package. So it is necessary for svgalib and others. Perhaps something like this could be included in the HOWTO I'll try to make mention of it. However, it is policy that the newer libfoog package should conflict with old versions of libfoo that put their libraries in /usr/lib instead of /usr/lib/libc5-compat. Any package that doesn't do this has a bug. In addition, the both packages are installed at the same time, you'll get the right thing even if it does complain about overwrites, and most other libraries can stand to be broken for a few minutes. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
On Tue, Oct 07, 1997 at 10:29:11AM -0400, Scott Ellis wrote: On Tue, 7 Oct 1997 [EMAIL PROTECTED] wrote: It is in general a good advice to install first the actual lib* package, and then the appropriate lkib*g package. So it is necessary for svgalib and others. Perhaps something like this could be included in the HOWTO I'll try to make mention of it. However, it is policy that the newer libfoog package should conflict with old versions of libfoo that put their libraries in /usr/lib instead of /usr/lib/libc5-compat. Any package that doesn't do this has a bug. In addition, the both packages are installed at the same time, you'll get the right thing even if it does complain about overwrites, and most other libraries can stand to be broken for a few minutes. I have to admit that I don't know what I'm really doing, but it works: I try to install the (old) libc5-compat, and if it installs I install the libc6 one after. If it depends on libc6 and errors, I install the libc6 and then the libc5 library a second time. Seems to work fine... Once again, I don't know what I do but I'm impressed that all works relativly flawless. Thank you, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Debian libc5 to libc6 Mini-HOWTO (regular posting)
Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] $Id: libc5-libc6-Mini-HOWTO.sgml,v 2.6 1997/09/27 16:41:16 storm Exp storm $ 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Note on how to upgrade via dpkg-ftp. o Notes about NIS and libgdbm (perl) issues. o Note about libc6-based e2fsck being bad for large partitions. o Reorganized slightly and added more information about possible problems. o Moved ldso above libc6, incase they have an ancient ldso. o Raised versions required for bash and libreadline(g)2 to the official maintainer versions to avoid possible version mismatch breakage. o Added a note saying that allowing dselect to upgrade the listed packages might result in an unbootable system. o Added ncurses3.0 to list of packages after realizing that libreadline2 depended on it. This may not be necessary, as everyone should already have ncurses3.0 installed. 1.2. Finding updates The latest version of this Mini-HOWTO in HTML format should be located at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html. The SGML source should also be available as libc5-libc6-Mini-HOWTO.sgml in the same directory. 1.3. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. IMPORTANT: If you use dselect to do the initial upgrade to these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ldso_1.9.5-1 o libc6_2.0.4-1 o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.2. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 2.3. Other Possible Conflicts Since perl is used in many package installation scripts, problems with with library upgrades may temporarily break perl, which may break other package installations. To be safe, install the new libgdbm1 and then the new libgdbmg1 packages by hand before upgrading perl. 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading bash The package bash_2.01-1 requires that you have libreadlineg2_2.1-3 or greater installed. If you install the new bash package before installing the new libreadlineg2, you will break your system. bash_2.01-2 has the appropriate predepends lines, but may not yet be to your mirror. 4.2. /sbin/e2fsck The e2fsck program in e2fsprogs_1.10-4 has a bug in it which will cause it to destroy data on partitions above 2GB in size. The version in e2fsprogs_1.10-5 has fixed this bug. IMPORTANT: If you run the older libc6-based e2fsck on a 2 GB
Debian libc5 to libc6 Mini-HOWTO (regular posting, updated)
-BEGIN PGP SIGNED MESSAGE- Note that some of the updated material (information about perl and NIS) is very rough, and I should be cleaning up the information in the next draft. If you have any questions, feel free to contact me and I'll try to be more specific. - - begin howto - Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] $Id: libc5-libc6-Mini-HOWTO.sgml,v 2.5 1997/09/16 03:31:27 storm Exp $ 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Notes about NIS and libgdbm (perl) issues. o Note about libc6-based e2fsck being bad for large partitions. o Reorganized slightly and added more information about possible problems. o Moved ldso above libc6, incase they have an ancient ldso. o Raised versions required for bash and libreadline(g)2 to the official maintainer versions to avoid possible version mismatch breakage. o Added a note saying that allowing dselect to upgrade the listed packages might result in an unbootable system. o Added ncurses3.0 to list of packages after realizing that libreadline2 depended on it. This may not be necessary, as everyone should already have ncurses3.0 installed. 1.2. Finding updates The latest version of this Mini-HOWTO in HTML format should be located at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html. The SGML source should also be available as libc5-libc6-Mini-HOWTO.sgml in the same directory. 1.3. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. IMPORTANT: If you use dselect to do the initial upgrade to these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ldso_1.9.5-1 o libc6_2.0.4-1 o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.2. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 2.3. Other Possible Conflicts Since perl is used in many package installation scripts, problems with with library upgrades may temporarily break perl, which may break other package installations. To be safe, install the new libgdbm1 and then the new libgdbm1g packages by hand before upgrading perl. 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading bash The package bash_2.01-1 requires that you have libreadlineg2_2.1-3 or greater installed. If you install the new bash package before installing the new libreadlineg2, you will break your system. bash_2.01-2 has the appropriate predepends lines, but may not yet be to your mirror. 4.2. /sbin/e2fsck
Debian libc5 to libc6 Mini-HOWTO (regular posting)
-BEGIN PGP SIGNED MESSAGE- Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] $Id: libc5-libc6-Mini-HOWTO.sgml,v 2.4 1997/08/28 22:02:32 storm Exp $ 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Note about libc6-based e2fsck being bad for large partitions. o Reorganized slightly and added more information about possible problems. o Moved ldso above libc6, incase they have an ancient ldso. o Raised versions required for bash and libreadline(g)2 to the official maintainer versions to avoid possible version mismatch breakage. o Added a note saying that allowing dselect to upgrade the listed packages might result in an unbootable system. o Added ncurses3.0 to list of packages after realizing that libreadline2 depended on it. This may not be necessary, as everyone should already have ncurses3.0 installed. 1.2. Finding updates The latest version of this Mini-HOWTO in HTML format should be located at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html. The SGML source should also be available as libc5-libc6-Mini-HOWTO.sgml in the same directory. 1.3. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. IMPORTANT: If you use dselect to do the initial upgrade to these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ldso_1.9.5-1 o libc6_2.0.4-1 o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.2. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading bash The package bash_2.01-1 requires that you have libreadlineg2_2.1-3 or greater installed. If you install the new bash package before installing the new libreadlineg2, you will break your system. bash_2.01-2 has the appropriate predepends lines, but may not yet be to your mirror. 4.2. /sbin/e2fsck The e2fsck program in e2fsprogs_1.10-4 has a bug in it which will cause it to destroy data on partitions above 2GB in size. The version in e2fsprogs_1.10-5 has fixed this bug. IMPORTANT: If you run the older libc6-based e2fsck on a 2 GB or greater partition, YOU WILL LOSE DATA. 4.3. /usr/bin/gencat Note also that both the man-db and the libc6-dev packages currently include /usr/bin/gencat. The version of gencat in libc6-dev has been reported to cause segfault problems with man-db, you may wish to reinstall man-db after libc6-dev if you experience these problems. - -- Scott K. Ellis
Debian libc5 to libc6 Mini-HOWTO
-BEGIN PGP SIGNED MESSAGE- Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] $Id: libc5-libc6-Mini-HOWTO.sgml,v 2.4 1997/08/28 22:02:32 storm Exp $ 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Note about libc6-based e2fsck being bad for large partitions. o Reorganized slightly and added more information about possible problems. o Moved ldso above libc6, incase they have an ancient ldso. o Raised versions required for bash and libreadline(g)2 to the official maintainer versions to avoid possible version mismatch breakage. o Added a note saying that allowing dselect to upgrade the listed packages might result in an unbootable system. o Added ncurses3.0 to list of packages after realizing that libreadline2 depended on it. This may not be necessary, as everyone should already have ncurses3.0 installed. 1.2. Finding updates The latest version of this Mini-HOWTO in HTML format should be located at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html. The SGML source should also be available as libc5-libc6-Mini-HOWTO.sgml in the same directory. 1.3. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. IMPORTANT: If you use dselect to do the initial upgrade to these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ldso_1.9.5-1 o libc6_2.0.4-1 o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.2. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading bash The package bash_2.01-1 requires that you have libreadlineg2_2.1-3 or greater installed. If you install the new bash package before installing the new libreadlineg2, you will break your system. bash_2.01-2 has the appropriate predepends lines, but may not yet be to your mirror. 4.2. /sbin/e2fsck The e2fsck program in e2fsprogs_1.10-4 has a bug in it which will cause it to destroy data on partitions above 2GB in size. The version in e2fsprogs_1.10-5 has fixed this bug. IMPORTANT: If you run the older libc6-based e2fsck on a 2 GB or greater partition, YOU WILL LOSE DATA. 4.3. /usr/bin/gencat Note also that both the man-db and the libc6-dev packages currently include /usr/bin/gencat. The version of gencat in libc6-dev has been reported to cause segfault problems with man-db, you may wish to reinstall man-db after libc6-dev if you experience these problems. - -- Scott K. Ellis
Debian libc5 to libc6 Mini-HOWTO (regular posting)
-BEGIN PGP SIGNED MESSAGE- Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] v2.1, August 22, 1997 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Note about libc6-based e2fsck being bad for large partitions. o Reorganized slightly and added more information about possible problems. o Moved ldso above libc6, incase they have an ancient ldso. o Raised versions required for bash and libreadline(g)2 to the official maintainer versions to avoid possible version mismatch breakage. o Added a note saying that allowing dselect to upgrade the listed packages might result in an unbootable system. o Added ncurses3.0 to list of packages after realizing that libreadline2 depended on it. This may not be necessary, as everyone should already have ncurses3.0 installed. 1.2. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. IMPORTANT: If you use dselect to do the initial upgrade to these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ldso_1.9.5-1 o libc6_2.0.4-1 o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-4 o libreadlineg2_2.1-4 o bash_2.01-2 2.2. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading bash The package bash_2.01-1 requires that you have libreadlineg2_2.1-3 or greater installed. If you install the new bash package before installing the new libreadlineg2, you will break your system. bash_2.01-2 has the appropriate predepends lines, but may not yet be to your mirror. 4.2. /sbin/e2fsck The e2fsck program in e2fsprogs_1.10-4 has a bug in it which will cause it to destroy data on partitions above 2GB in size. The version in e2fsprogs_1.10-5 has fixed this bug. IMPORTANT: If you run the older libc6-based e2fsck on a 2 GB or greater partition, YOU WILL LOSE DATA. 4.3. /usr/bin/gencat Note also that both the man-db and the libc6-dev packages currently include /usr/bin/gencat. The version of gencat in libc6-dev has been reported to cause segfault problems with man-db, you may wish to reinstall man-db after libc6-dev if you experience these problems. - -- Scott K. Ellis | Argue for your limitations, and [EMAIL PROTECTED] | sure enough, they're yours. | -- Illusions -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBNAWWkKCk2fENdzpVAQH1swP/ffZzw213MhQRrqIJxwfjLIErbs4UzVLP
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
On Aug 28, Scott K. Ellis wrote Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] v2.1, August 22, 1997 You might also want to mention perl and libgdbm. I can't tell you exactly what went wrong, but both machines I upgraded had a core-dumping perl. With lots of install scripts written in perl that makes a fine mess. I think the first time perl crashed it was because the old perl couldn't handle the new locale files. The second time was due to a wrong libgdbm-something. -- Bart Schuller [EMAIL PROTECTED] At Lunalabs, where the Lunatech Research http://www.lunatech.com/ future is made today.. Partner of The Perl Institute http://www.perl.org/Linux http://www.li.org/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
-BEGIN PGP SIGNED MESSAGE- On Thu, 28 Aug 1997, Bart Schuller wrote: You might also want to mention perl and libgdbm. I can't tell you exactly what went wrong, but both machines I upgraded had a core-dumping perl. With lots of install scripts written in perl that makes a fine mess. I think the first time perl crashed it was because the old perl couldn't handle the new locale files. The second time was due to a wrong libgdbm-something. I'd be happy to if you can provide me with some details, I haven't experienced that particular problem myself. If you can give me package version numbers (and assuming that the current packages in the archive are broken), I'd be happy to write about it. I've got a spare partition that I don't mind breaking to test stuff, but I need versions and installation order. - -- |Your friends will know you better in the Scott K. Ellis | first minute you meet than your acquaintances [EMAIL PROTECTED] | will know you in a thousand years. | -- Illusions -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBNAWxYqCk2fENdzpVAQEKEgQAnmOwA/pDP0EqD8yOhbJ4Sox0oUsRCb/V Ld6V4fv33HnW45HACmZn0tYzbpRAoU7FpgGtvkU9AHM+JYJDW20I9MPvSLrQTyWH bFDB9LSiALdEDrnFUhX3TdIfMayNmNhq4DxMt447HWJ368wUkl5r45he0k9PMbyf A6XJaYCH/80= =gfdJ -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Debian libc5 to libc6 Mini-HOWTO (regular posting, updated)
-BEGIN PGP SIGNED MESSAGE- Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] v2.0, August 19, 1997 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 1.1. Recent Changes: o Reorganized slightly and added more information about possible problems. o Moved ldso above libc6, incase they have an ancient ldso. o Raised versions required for bash and libreadline(g)2 to the official maintainer versions to avoid possible version mismatch breakage. o Added a note saying that allowing dselect to upgrade the listed packages might result in an unbootable system. o Added ncurses3.0 to list of packages after realizing that libreadline2 depended on it. This may not be necessary, as everyone should already have ncurses3.0 installed. 1.2. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. IMPORTANT: If you use dselect to do the initial upgrade to these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ldso_1.9.5-1 o libc6_2.0.4-1 o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-3 o libreadlineg2_2.1-3 o bash_2.01-1 2.2. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns 4.1. Upgrading bash The package bash_2.01-1 requires that you have libreadlineg2_2.1-3 or greater installed. If you install the new bash package before installing the new libreadlineg2, you will break your system. bash_2.01-2 has the appropriate predepends lines, but may not yet be to your mirror. 4.2. /usr/bin/gencat Note also that both the man-db and the libc6-dev packages currently include /usr/bin/gencat. The version of gencat in libc6-dev has been reported to cause segfault problems with man-db, you may wish to reinstall man-db after libc6-dev if you experience these problems. - -- |In order to live freely and happily, Scott K. Ellis | you must sacrifice boredom. [EMAIL PROTECTED] | It is not always an easy sacrifice. |-- Illusions -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBM/pT9qCk2fENdzpVAQFNggP/XPw2QZ5AU0cGb4sYAy2a1JcaiKPjKzKr xRQcLDI688KtGkBjoZTkkY6BTll+/yyyJBzTV58TuXzibwfjQ3ElNbdXeYI8zppL DF8VYXtJmpLdJ6ieFtlndL+2egKM61ISCT9m686a7DbNLrX0eKGrKydeH2FCiRtl cKBJ9pkOiLM= =WYUb -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
Scott, I had some problems. Specifically: [EMAIL PROTECTED](p1):bhmit1$ /bin/bash /bin/bash: error in loading shared libraries : undefined symbol: rl_get_string_value_hook o libc6_2.0.4-1- check o ldso_1.9.5-1 - check o ncurses3.4_1.9.9g-3 - check o libreadline2_2.1-2.1 - check o libreadlineg2_2.1-2.1- check o bash_2.01-0.1- failed in post install from above error I also installed libdl1-dev_1.9.5-1.deb because of an ldconfig error: ldconfig: warning: can't open /usr/lib/libreadline.so (No such file or directory), skipping [ started after libreadline, fixed after libreadlineg ] ldconfig: warning: can't open /usr/lib/libhistory.so (No such file or directory), skipping [ same as above ] ldconfig: warning: can't open /usr/lib/libdl.so (No such file or directory), skipping [ started after ldso I think, probably an earlier problem with my system. It was fixed by installing libdl1-dev ] Note, I didn't purge the -dev libraries. If I want to compile anything, I can live with libc5 for now. Everything seems to work after replacing /bin/bash with a backup version I have. The main goal of all this was to get netscape 4 helper apps working (didn't want to use the ash route). If you need anymore info, please ask. Brandon - Brandon Mitchell E-mail: [EMAIL PROTECTED] Homepage: http://www.geocities.com/SiliconValley/7877/home.html We all know Linux is great...it does infinite loops in 5 seconds. --Linus Torvalds -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
-BEGIN PGP SIGNED MESSAGE- On Sat, 16 Aug 1997, Brandon Mitchell wrote: Scott, I had some problems. Specifically: [EMAIL PROTECTED](p1):bhmit1$ /bin/bash /bin/bash: error in loading shared libraries : undefined symbol: rl_get_string_value_hook o libc6_2.0.4-1 - check o ldso_1.9.5-1 - check o ncurses3.4_1.9.9g-3- check o libreadline2_2.1-2.1 - check o libreadlineg2_2.1-2.1 - check o bash_2.01-0.1 - failed in post install from above error I also installed libdl1-dev_1.9.5-1.deb because of an ldconfig error: Okay, I'm pretty much stumped by this problem. I can't manage to get it to reproduce itself. If possible, could you back out those packages to the stable ones (where applicable, remove the others) and try again with the new bash and libreadline packages that were recently uploaded (bash_2.01-2 and libreadline*-4 I think) and see if you have the same problem? If the problem goes away, I'll modify the mini-howto to specify the later versions of the packages. [I'd also appreciate it if someone with better knowledge of the appropriate packages could take a look at this, where is that symbol hiding and what might have broken it?] ldconfig: warning: can't open /usr/lib/libreadline.so (No such file or directory), skipping [ started after libreadline, fixed after libreadlineg ] ldconfig: warning: can't open /usr/lib/libhistory.so (No such file or directory), skipping [ same as above ] ldconfig: warning: can't open /usr/lib/libdl.so (No such file or directory), skipping [ started after ldso I think, probably an earlier problem with my system. It was fixed by installing libdl1-dev ] Those ldconfig warnings are usually a symptom of a package being out of sync with its coresponding '-dev' package. It can be safely ignored until you upgrade the '-dev' package, just don't compile programs with those libs until then. - -- Scott K. Ellis|The reason angels can fly is that [EMAIL PROTECTED]| they take themselves so lightly. |-- G.K. Chesterson -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBM/aEaKCk2fENdzpVAQEg4gQArKmlKQMVHtChlF+i1e1sHa6um59aE2+/ G3IhECVtFUbHV4R1cXJWpnAVyaicJTcNAnnvfTBs5Se+mJNWDQNsoGrnS92eGziO 2+K9UzjFwnKm6zWjBEuBVG+YDJKRop4H1141H/32ZSozj2tr1FPJap37zv9halob taLGrPFvyJk= =wLx/ -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian libc5 to libc6 Mini-HOWTO (regular posting)
ldconfig: warning: can't open /usr/lib/libreadline.so (No such file or directory), skipping [ started after libreadline, fixed after libreadlineg ] ldconfig: warning: can't open /usr/lib/libhistory.so (No such file or directory), skipping [ same as above ] ldconfig: warning: can't open /usr/lib/libdl.so (No such file or directory), skipping [ started after ldso I think, probably an earlier problem with my system. It was fixed by installing libdl1-dev ] About 3 weeks when I changed to libc5, I did get errors such as these. It was a simple matter of changing the symlinks by hand to point to the newer version number. I am not sure if this is what is happening in your case, but your output looks almost what I remember getting. -- Ioannis Tambouras [EMAIL PROTECTED], West Palm Beach, Florida Signed pgp-key on key server. Signed pgp-key on key server. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Debian libc5 to libc6 Mini-HOWTO (regular posting, updated)
-BEGIN PGP SIGNED MESSAGE- Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] v1.6, August 17, 1997 Recent Changes: o Moved ldso above libc6, incase they have an ancient ldso. o Raised versions required for bash and libreadline(g)2 to the official maintainer versions to avoid possible version mismatch breakage. o Added a note saying that allowing dselect to upgrade the listed packages might result in an unbootable system. o Added ncurses3.0 to list of packages after realizing that libreadline2 depended on it. This may not be necessary, as everyone should already have ncurses3.0 installed. 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the Linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 2. Requirements 2.1. Minimum Requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. IMPORTANT: If you use dselect to do the initial upgrade to these packages, there is a very good possibility of breaking bash and therefore making your system unusable. o ldso_1.9.5-1 o libc6_2.0.4-1 o ncurses3.0_1.9.9e-2 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-3 o libreadlineg2_2.1-3 o bash_2.01-1 2.2. Other Suggested Packages These packages are not absolutely essential for the functioning of the packages in unstable, but are still very useful. The new dpkg-dev may be necessary for unpacking source archives from unstable, and the new dpkg-ftp is needed if you wish to use the ftp method of dselect to upgrade your system to the unstable distribution. o libg++272_2.7.2.5-2 o dpkg_1.4.0.19 o dpkg-dev_1.4.0.19 o dpkg-ftp_1.4.9 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns Note also that both the man-db and the libc6-dev packages currently include /usr/bin/gencat. The version of gencat in libc6-dev has been reported to cause segfault problems with man-db, you may wish to reinstall man-db after libc6-dev if you experience these problems. 5. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you mileage may vary. Please send any comments or corrections to [EMAIL PROTECTED] - -- | You are never given a wish without also Scott K. Ellis |being given the power to make it true. [EMAIL PROTECTED] |You may have to work for it, however. | -- Illusions -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBM/csw6Ck2fENdzpVAQFOjwP9FCB2X967RwVrt6sTis3BFJpNN36o9X+v SLT56Cp179FiuM2p+DIRzUxbZEQoLZJMvMe842kpL16hd3iVGcxkG5hyyiNWiZeU CvVYKRqmi3sSP7+MJBCPDxNK6gCGvP0ER5zR4x6o/eOx/6TefKpOBIJA+cNuomi8 gv+TSk/7tvU= =6uh0 -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
? about Debian libc5 to libc6 Mini-HOWTO
Two days or so ago the Debian libc5 to libc6 Mini-HOWTO was posted here. I was wondering if it is okay to 1. use dselect and connect to a local ftp mirror 2. When prompted for Enter space seperated list of distributions to get during setting up the FTP Access Method, enter hamm/hamm 3. update the package list 4. unselect everything that is selected by default 5. select the packages that are listed in the Mini-HOWTO 6. and install My main concern is that each of these packages have many depencies. Should I accept the default dependencies or should I override them so I ONLY install the packages listed in the Mini-HOWTO? - [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: ? about Debian libc5 to libc6 Mini-HOWTO
-BEGIN PGP SIGNED MESSAGE- On Sat, 16 Aug 1997, Ricardo Muggli wrote: Two days or so ago the Debian libc5 to libc6 Mini-HOWTO was posted here. I was wondering if it is okay to 1. use dselect and connect to a local ftp mirror 2. When prompted for Enter space seperated list of distributions to get during setting up the FTP Access Method, enter hamm/hamm 3. update the package list 4. unselect everything that is selected by default 5. select the packages that are listed in the Mini-HOWTO 6. and install My main concern is that each of these packages have many depencies. Should I accept the default dependencies or should I override them so I ONLY install the packages listed in the Mini-HOWTO? The packages listed to be installed are complete to themselves, they need to be installed manually. If you use dselect-ftp to upgrade them, you stand a high risk of breaking bash and making your system unbootable. The list I posted, when installed one-at-a-time in the exact order listed, doesn't mess up your system. I wrote the list after several people encountered problems upgrading. The base problem is with new libreadline packages screwing up if installed in the wrong order. I've run the install as listed on a clean v1.3.1 system and it worked flawlessly. - -- | The bond that links your true family is not Scott K. Ellis | one of blood, but of respect and joy in each [EMAIL PROTECTED] | other's life. Rarely do members of one | family grow up under the same roof. | -- Illusions -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBM/YleqCk2fENdzpVAQFVqwP+Nm+DeIPW4lRLnPxUzuxw/L+SVL8KQUy+ IxYsuCoVnhBh/LtRui/LA39GBUkbjWy7rEl37cMEnND9D2Z0ttNkW526mBL4V+hG 1SnrKjUJeSpEiDfs/u4ERZbtbz09G9P0ONoFliK0WwvYgQYrnfeD6dpEyo5bL6bu c893FCeflvE= =2IG6 -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: ? about Debian libc5 to libc6 Mini-HOWTO
Two days or so ago the Debian libc5 to libc6 Mini-HOWTO was posted here. I was wondering if it is okay to 1. use dselect and connect to a local ftp mirror 2. When prompted for Enter space seperated list of distributions to get during setting up the FTP Access Method, enter hamm/hamm 3. update the package list 4. unselect everything that is selected by default 5. select the packages that are listed in the Mini-HOWTO 6. and install Dselect will not order the packages correctly. Installing out of order may result in an unusable system (reparable by a second installation and rescue disk or a complete reinstall). I believe the instructions are given in an order that will not result in a dependency problem. Also, I believe the mirror's format has changed, so pointing dselect to unstable may not work as expected. All of this is from other messages, I plan on actually doing the upgrade later tonight myself. Brandon - Brandon Mitchell E-mail: [EMAIL PROTECTED] Homepage: http://www.geocities.com/SiliconValley/7877/home.html We all know Linux is great...it does infinite loops in 5 seconds. --Linus Torvalds -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Debian libc5 to libc6 Mini-HOWTO (regular posting)
-BEGIN PGP SIGNED MESSAGE- Debian libc5 to libc6 Mini-HOWTO Scott K. Ellis, [EMAIL PROTECTED] v1.3, August 14, 1997 1. Introduction The Debian project is currently in the process of putting together the next release of the Debian system. This version will utilize the new libc6, a replacement for the prior libc5 which includes many enhancements and brings the linux C library back into sync with the GNU project. We are doing this in a way to allow you to continue to utilize your older software by providing development and operating environments for both C libraries. However, all packages in the new release will be linked with the new C library. This has made it slightly more difficult to install packages from the unstable branch of our development tree into a working system. There is a slight possibility of making your system unbootable in the process, this guide is intended to help you avoid such problems. 2. Minimum requirements The minimum list of packages to install to be able to run unstable- branch packages is below. Install these packages one at a time in exactly the order listed. When versions are mentioned, that is a minimum suggested version, any later version should also be acceptable. o libc6_2.0.4-1 o ldso_1.9.5-1 o ncurses3.4_1.9.9g-3 o libreadline2_2.1-2.1 o libreadlineg2_2.1-2.1 o bash_2.01-0.1 3. Development If you wish to do libc6 development, you should first purge all the '-dev' packages on your system, the new development system will use packages with the suffix '-dev' for libc6 development and '-altdev' for libc5 development. You will wish to install the latest libc5 package, and altgcc if you wish continue to do libc5 development as well. Some libraries haven't been recompiled for the new libc6 yet, check that all your vital libraries are available before upgrading. Linking libc5-based libraries with libc6-based programs will have unpredictable results. 4. Concerns Note also that both the man-db and the libc6-dev packages currently include /usr/bin/gencat. The version of gencat in libc6-dev has been reported to cause segfault problems with man-db, you may wish to reinstall man-db after libc6-dev if you experience these problems. 5. Disclaimer As always, this document comes with NO WARRANTY. These comments are based on my personal experience and experimentation. While this worked for me off a freshly installed v1.3.1 system, you milage may vary. Please send any comments or corrections to [EMAIL PROTECTED] - -- |The mark of your ignorance is the depth of Scott K. Ellis| your belief in injustice and tragedy. [EMAIL PROTECTED]| What the caterpillar calls the end of the world, | the master calls a butterfly. | -- Illusions -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBM/PGC6Ck2fENdzpVAQFzRwP7Bx5JP0We8k2vBeXS+49kwHKX6K/KPLPC CtGsvae3V628PIS+6dQZlMhU2rNTRNjhTa2SHbzkrefv7kEJMLnJVja8IIlzxr4y 5Yhh0iKvc6S5Cp2tXzCSYQ6piYJg2nhR2sq2b67FmOmPR/0uPAwlYnhyQuplbjGS 4JXjP7055as= =hQzr -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
Paul == Paul Miller [EMAIL PROTECTED] writes: Paul How can I install *BOTH* libc5 and libc6?? Can't we all just Paul get along? -Paul As people have said, you can install them both--the packages named 'libc5' and 'libc6'. The complications are in the '-dev' packages and the compilation environment. libc5-dev and libc6-dev cannot coexist. The current gcc package conflicts with libc5-dev, so if you want to keep up with unstable, you'll have to install libc6-dev to compile any C programs. If you want to do that, *and* also be able to compile in a libc5 environment, there are a few packages meant to allow that by having an alternative gcc and C library on the system: libc5-altdev, altgcc, and libdl1-altdev (the only ones I've seen). I haven't tried these. Hope this clarifies things a little, anyway - -- Ed Donovan [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
The burning quesiton on my mind is with regard to mixed applications. Lyx, in particular, relies on xpm and xforms, which are compiled with libc5. Can I stil compile lyx with libc6? rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
The burning quesiton on my mind is with regard to mixed applications.
Lyx, in particular, relies on xpm and xforms, which are compiled with
libc5. Can I stil compile lyx with libc6?
You almost certainly can compile them
You probably will not run into problems using the resulting binary,
but 'people that know' tell me that misterious, hidden problems
will/may appear somewhere, due to the mixing.
You shouldn't use programmes that use xforms anyway, as it's non-free
software. This means a lot less freedom to you (you cannot recompile
xforms for libc6, for example).
--
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
You almost certainly can compile them OK. libc6 was one of the suspects when trying to compile lyx. ultimately I had to do a clean install (we hadn't found out about the hardware problems yet, either). You shouldn't use programmes that use xforms anyway, as it's non-free software. This means a lot less freedom to you (you cannot recompile xforms for libc6, for example). Currently, there's no real substitute for lyx. Lyx will be moved away from xforms, but it has more pressing matters. There's a couple of different packages under consideration. rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
You almost certainly can compile them
OK. libc6 was one of the suspects when trying to compile lyx.
ultimately I had to do a clean install (we hadn't found out about the
hardware problems yet, either).
Note, BTW (just realise this) that if lynx has non-POSIX stuff in it
(forgetting to #include errno.h etc), you'll have to use minor
ajustments (and those are unrelated to xforms not being libx6).
But after that, it should compile fine.
And, currently all the xlib's are libc5, while many X packages
have already been recompiled for libc6 -- all of those packages appear
to work fine. So, I don't expect problems for you, but that certainly
isn't a guarantee.
You shouldn't use programmes that use xforms anyway, as it's non-free
software. This means a lot less freedom to you (you cannot recompile
xforms for libc6, for example).
[..]
Lyx will be moved away from xforms, but it has more pressing matters.
Hey, that's good news -- I didn't know that yet. Last time I checked,
I remember them saying something that they will always continue to
use xforms, but if they intend to move away from xforms now, I might
start getting interested in Lyx.
Thanks,
--
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
libc5 and libc6
How can I install *BOTH* libc5 and libc6?? Can't we all just get along? -Paul -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
How can I install *BOTH* libc5 and libc6?? Can't we all just get along?
Just install them. There's no problem.
--
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 and libc6
On Wed, 16 Jul 1997 23:17:08 -0400, Paul Miller wrote: How can I install *BOTH* libc5 and libc6?? Can't we all just get along? dpkg -i libc6 ; They coexsist fine, and I'm happy to say I'm now running apache 1.2.0 (a libc6 compile) -- Elite MicroComputers 908-541-4214 http://www.psychosis.com/emc/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
