Re: Install iso images on cdimage.debian.org
FYI, the 12 May net-install .iso doesn't seem to contain a kernel-image to install. The installer dies during the installation of the base-system because of this. Scott mtms wrote: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/amd64 http://cdimage.debian.org/pub/cdimage-testing/daily/amd64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dpkg SEGFAULT with upgrade using gcc-3.4 (or 4.0) repos
Hello all, So I've just gotten bit by a SEGFAULT during a dpkg upgrade using the 3.4 (or I guess gcc-4.0 archive). This occurred after --force'ing the /usr/lib64 issue with the libc6 upgrade. The messages can be found below. Any suggestions about how to fix this? Thanks a bunch, Scott Preparing to replace dpkg 1.10.25.0.0.1.gcc4 (using .../dpkg_1.10.27.0.0.1.gcc4_amd64.deb) ... Unpacking replacement dpkg ... E: Sub-process /usr/bin/dpkg received a segmentation fault. ... uller(root):/var/cache/apt/archives# dpkg --version Debian GNU/Linux `dpkg' package management program version 1.10.27 (amd64). This is free software; see the GNU General Public Licence version 2 or later for copying conditions. There is NO warranty. See dpkg --licence for copyright and license details. ... uller(root):/var/cache/apt/archives# gdb /usr/bin/dpkg GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-linux...(no debugging symbols found) Using host libthread_db library /lib/libthread_db.so.1. (gdb) run -i dpkg_1.10.27.0.0.1.gcc4_amd64.deb Starting program: /usr/bin/dpkg -i dpkg_1.10.27.0.0.1.gcc4_amd64.deb (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. 0x002a956e39ba in strncasecmp () from /lib/libc.so.6 -- Scott M. RansomAddress: NRAO Phone: (434) 296-0320 520 Edgemont Rd. email: [EMAIL PROTECTED] Charlottesville, VA 22903 USA GPG Fingerprint: 06A9 9553 78BE 16DB 407B FFCA 9BFA B6FF FFD3 2989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg SEGFAULT with upgrade using gcc-3.4 (or 4.0) repos
Javier Kohen just asked (I'm not subscribedto this list anymore, so I saw his post on google news) what version of libc6 I'm using. I _think_ (since dpkg is not allowing me to check) that I'm using libc6_2.3.2.ds1-20.0.0.2.gcc4_amd64.deb, although libc6_2.3.2.ds1-20.0.0.3.gcc4_amd64.deb was in the process of being installed (I'm not sure if it was unpacked yet or not). And as far as backtracing the dpkg SEGFAULT in gdb, I had tried that, but as he mentioned, since there are no debugging symbols, there is nothing but memory addresses. Scott On Wednesday 16 March 2005 01:32 pm, Scott Ransom wrote: Hello all, So I've just gotten bit by a SEGFAULT during a dpkg upgrade using the 3.4 (or I guess gcc-4.0 archive). This occurred after --force'ing the /usr/lib64 issue with the libc6 upgrade. The messages can be found below. Any suggestions about how to fix this? Thanks a bunch, Scott Preparing to replace dpkg 1.10.25.0.0.1.gcc4 (using .../dpkg_1.10.27.0.0.1.gcc4_amd64.deb) ... Unpacking replacement dpkg ... E: Sub-process /usr/bin/dpkg received a segmentation fault. ... uller(root):/var/cache/apt/archives# dpkg --version Debian GNU/Linux `dpkg' package management program version 1.10.27 (amd64). This is free software; see the GNU General Public Licence version 2 or later for copying conditions. There is NO warranty. See dpkg --licence for copyright and license details. ... uller(root):/var/cache/apt/archives# gdb /usr/bin/dpkg GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as x86_64-linux...(no debugging symbols found) Using host libthread_db library /lib/libthread_db.so.1. (gdb) run -i dpkg_1.10.27.0.0.1.gcc4_amd64.deb Starting program: /usr/bin/dpkg -i dpkg_1.10.27.0.0.1.gcc4_amd64.deb (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. 0x002a956e39ba in strncasecmp () from /lib/libc.so.6 -- Scott M. RansomAddress: NRAO Phone: (434) 296-0320 520 Edgemont Rd. email: [EMAIL PROTECTED] Charlottesville, VA 22903 USA GPG Fingerprint: 06A9 9553 78BE 16DB 407B FFCA 9BFA B6FF FFD3 2989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Still confused about pure64 package changelogs
Have you ever used apt-listchanges? Sound like just what you are looking for. Scott Package: apt-listchanges Version: 2.57 Priority: optional Section: utils Maintainer: Matt Zimmerman [EMAIL PROTECTED] Depends: python (= 2.3), apt (= 0.5.3), python-apt, debconf, ucf (= 0.28), debianutils (= 2.0.2) Suggests: x-terminal-emulator, www-browser Architecture: all Filename: pool/unstable/main/amd64/a/apt-listchanges/apt-listchanges_2.57_all.deb Size: 47688 MD5sum: a45613f74fe271afb4e6e8f10e09627e Description: Display change history from .deb archives apt-listchanges is a tool to show what has been changed in a new version of a Debian package, as compared to the version currently installed on the system. It does this by extracting the relevant entries from the Debian changelog file, and the NEWS.Debian file. . It can be run on several .deb archives at a time to get a list of all of the changes that would be effected by installing or upgrading a group of packages. It can be configured to do this automatically during upgrades using apt. installed-size: 336 On Mon, Jan 31, 2005 at 04:04:14PM -0800, Larry Doolittle wrote: Let me assure everyone before I start that I'm really happy with debain pure64. Fast and solid. Most of the time, when I see a package ready to download with apt-get upgrade, I can go to packages.debian.org, and find out what changed and why. Every now and then, that doesn't work. Today, for instance, I see netbase is ready to upgrade, from version 4.19 to version 4.20. The trouble is, looking at packages.debian.org, the changelog only goes up to 4.19. Now, netbase is kind of an important package, and I'd like a way to read about the changes before I load it up. Another particular example is kernel-image-2.6.10-9-amd64-k8, which doesn't even show up on packages.debian.org. In that case, I downloaded the source package, and buried in there I did indeed find a changelog that appeared up-to-date (although with a typo in it). Do these changelogs appear on the net anywhere, in a way such that I can avoid downloading the source every time? This isn't Gentoo! - Larry -- -- Scott M. RansomAddress: NRAO Phone: (434) 296-0320 520 Edgemont Rd. email: [EMAIL PROTECTED] Charlottesville, VA 22903 USA GPG Fingerprint: 06A9 9553 78BE 16DB 407B FFCA 9BFA B6FF FFD3 2989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
python2.3 missing a key lib
Hello All, In the 3.4 archive python2.3 is missing a key library (readline.so): uller:~$ dpkg -l python2.3 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii python2.3 2.3.4-18 An interactive high-level object-oriented uller:~$ python Python 2.3.4 (#2, Dec 9 2004, 18:54:17) [GCC 4.0.0 20041205 (experimental) (Debian 4.0-0pre2)] on linux2 Type help, copyright, credits or license for more information. import readline Traceback (most recent call last): File stdin, line 1, in ? ImportError: No module named readline Note that the module /usr/lib/python2.3/lib-dynload/readline.so _is_ there in the i386 version of the package. Should this be listed as a bug in the python2.3 package itself? Scott PS: Thanks for all of your hard work! Things are working amazingly well! -- Scott M. RansomAddress: NRAO Phone: (434) 296-0320 520 Edgemont Rd. email: [EMAIL PROTECTED] Charlottesville, VA 22903 USA GPG Fingerprint: 06A9 9553 78BE 16DB 407B FFCA 9BFA B6FF FFD3 2989
