Re: Upcoming 2.1 Release Architectures
On Wed, Oct 14, 1998 at 10:15:51AM -0400, Brian White wrote: Could I get some official word on which architectures wish to be included in the 2.1 release of Debian? Thanks! Brian ( [EMAIL PROTECTED] ) PowerPC has more or less given up on making 2.1. We're moving well, but I'm of the inclination we shouldn't release until we have a truly stabilized libc - or at least until we're a lot closer. Dan
Re: glibc 2.0.94 for testing
On Wed, Jul 29, 1998 at 04:27:15PM +0200, Anders Hammarquist wrote: Haven't noticed that one (at least not on the alpha under 2.1.106), but I probably don't want to know... Hmm. I know it appears on intel... Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Where did all the packages go???
On Wed, Jul 29, 1998 at 10:01:48AM -0500, John Goerzen wrote: OK, so it appears that hamm has disappeared from the archive (the sparc part of it anyway.) So I update my apt sources list to look in slink. No problem. But now, I get a lot of packages listed as obsolete/local. Looking at the archive, things like dpkg-dev have even disappeared. Where are they??? --- Obsolete and local packages present on system --- *** Req base adduser 3.8 none *** Req base base-files 2.0 none *** Req base comerr2g 1.10-10 none *** Req base modconf 0.2.17 none *** Req base ncurses-base 1.9.9g-8.6 none *** Req base syslinux 1.30-6 none On devel someone was talking about getting the symlinks fixed...These packages just need to be uploaded to slink. I did a few of them... Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: glibc 2.0.94 for testing
On Tue, Jul 28, 1998 at 10:11:40PM +0200, Anders Hammarquist wrote: Everything involving unpacking a .deb. Well, that overstating it a bit I think. What breaks is that dpkg-deb[1] runs chown(2) on everything it extracts from the archive, including symlinks. In recent 2.1 kernels, there is an lchown(2) call, and chown(2) follows symlinks (unlike 2.0 kernels where chown(2) will chown the symlink). If the symlink dpkg-deb tries to chown is broken, it exits, as chown(2) returned ENOENT. That's not the only issue. A random fflush() that probably shouldn't even be there causes dpkg to horribly die on debs on ext2 filesystems using recent dev kernels. Don't ask. Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
