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
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 The
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 or
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 (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] .
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] .
