archives?
Am I just crazy or did all of the archives die recently? I've tried amd64.debian.net, debian.csail.mit.edu and ftp.de.debian.org and all of their dists directories appear to be empty for each of the various amd64 distributions. apt-get and dselect are very unhappy of course. And I don't see amd64 yet on my own official Debian mirror, so that hasn't happened yet. Just curious... -- Mark Nippere-contacts: 4475 Carter Creek Parkway [EMAIL PROTECTED] Apartment 724 http://nipsy.bitgnome.net/ Bryan, Texas, 77802-4481 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GG/IT d- s++:+ a- C++$ UBL$ P---+++ L+++$ !E--- W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- I have crossed oceans of time to find you. -- Dracula, Bram Stoker's Dracula, 1992 end random quote of the moment -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: archives?
On Wed, Jun 08, 2005 at 10:09:23AM -0500, Mark Nipper wrote: Am I just crazy or did all of the archives die recently? I've tried amd64.debian.net, debian.csail.mit.edu and ftp.de.debian.org and all of their dists directories appear to be empty for each of the various amd64 distributions. apt-get and dselect are very unhappy of course. And I don't see amd64 yet on my own official Debian mirror, so that hasn't happened yet. Hmm, both debian-pure64 and debian-amd64 seem to have lost the contents of the dists subdir, although all the packages appear to be in the pool dir. That seems odd, and probably isn't supposed to be happening. So no you are not crazy, but perhaps a computer or admin somewhere is. :) Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: archives?
On (08/06/05 10:09), Mark Nipper wrote: Am I just crazy or did all of the archives die recently? I've tried amd64.debian.net, debian.csail.mit.edu and ftp.de.debian.org and all of their dists directories appear to be empty for each of the various amd64 distributions. apt-get and dselect are very unhappy of course. And I don't see amd64 yet on my own official Debian mirror, so that hasn't happened yet. Just curious... Yep. They seem to be unobtainable at present. No doubt all will resolve. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: archives?
On 10314 March 1977, Mark Nipper wrote: Am I just crazy or did all of the archives die recently? I've tried amd64.debian.net, debian.csail.mit.edu and ftp.de.debian.org and all of their dists directories appear to be empty for each of the various amd64 distributions. apt-get and dselect are very unhappy of course. And I don't see amd64 yet on my own official Debian mirror, so that hasn't happened yet. Its me going crazy, fixing a stupid problem, now waiting that the mirrors all sync up with the push I just sent, then sending out another push which contains the dist/ again. Should be fixed within an hour. Or day. Or year. :)) -- bye Joerg [Es geht doch nichts ueber deutsche Uebersetzungen] hurd:/# updatedb hurd:/# /servers/socket/2: Der Übersetzer ist gestorben -- Message-ID: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Library packages with only static archives
Drew Hess [EMAIL PROTECTED] writes: binutils-dev only supplies a static archive for libiberty. On AMD64, this means that you can't use libiberty functions in shared libraries, because libiberty.a isn't compiled with -fPIC. Seems to me that all library packages on AMD64 should come with shared libs. d You can't ever use a non PIC library with PIC code. It seems to work on several archs but has sideffects and randomly fails when symbols move around between versions. If a shared library needs some static code then a libiberty-pic package or a shared libiberty is needed. Please do file serious bugs for anyone using libiberty.a in shared libs. This a serious policy violation. MfG Goswin
Re: Library packages with only static archives
Thanks. Until it's fixed by the maintainer, I made my own version of the package which builds and installs libiberty.so. It's a bit of a hack, but I can submit the patch if it helps. d On Tue, 14 Dec 2004 00:41:40 +0100, Goswin von Brederlow [EMAIL PROTECTED] wrote: Drew Hess [EMAIL PROTECTED] writes: There aren't any Debian policy violations that I'm aware of... but I would like to use libiberty in my own shared library, and I can't on debian-amd64. I have followed up on a binutils bug that was submitted 2 years ago re: lack of shared libiberty on other archs, but I'm hoping that raising this issue on debian-amd64 will expedite a fix. d What you can do meanwhile is to force users of your lib to link in libiberty.a on their own. If you have a *.la file you can add the lib there. It is not policy in debian to do so but the mechanism is there. MfG Goswin
Library packages with only static archives
binutils-dev only supplies a static archive for libiberty. On AMD64, this means that you can't use libiberty functions in shared libraries, because libiberty.a isn't compiled with -fPIC. Seems to me that all library packages on AMD64 should come with shared libs. d
