Re: broken ia32-libc6 / libc6-i386

2006-04-26 Thread Goswin von Brederlow
Harald Dunkel <[EMAIL PROTECTED]> writes: > Hi Goswin, > > Goswin von Brederlow wrote: >> >> Why do you reply to an old mail that has nothing to with your problem? >> > > Sorry, I don't know how this happened. > >>> >>> Would it be possible to provide the changelog by default, >>> esp. for such

Re: broken ia32-libc6 / libc6-i386

2006-04-26 Thread Harald Dunkel
Hi Goswin, Goswin von Brederlow wrote: > > Why do you reply to an old mail that has nothing to with your problem? > Sorry, I don't know how this happened. >> >> Would it be possible to provide the changelog by default, >> esp. for such a radical change? > > You know, you could just download t

Re: broken ia32-libc6 / libc6-i386

2006-04-26 Thread Goswin von Brederlow
Harald Dunkel <[EMAIL PROTECTED]> writes: > Hi folks, Hi. Why do you reply to an old mail that has nothing to with your problem? > AFAICS ia32-libs shrunk for about 725KByte between 1.8 and > 1.9. But using aptitude I can review the changelog. It is > not available. How does aptitude look for

Re: broken ia32-libc6 / libc6-i386

2006-04-25 Thread Harald Dunkel
Hi folks, AFAICS ia32-libs shrunk for about 725KByte between 1.8 and 1.9. But using aptitude I can review the changelog. It is not available. What has been dropped? Would it be possible to provide the changelog by default, esp. for such a radical change? Many thanx Harri signature.asc Desc

Re: broken ia32-libc6 / libc6-i386

2006-03-12 Thread Hamish Moffatt
On Mon, Mar 13, 2006 at 02:24:22PM +1100, Hamish Moffatt wrote: > ia32-libc6 and libc6-i386 both contain /lib/ld-linux.so.2; neither of > these seem to be obselete and both of them seem to be required on my > system.. Specifically, qemu (for example) depends on ia32-libc6, which depends on lib32g

broken ia32-libc6 / libc6-i386

2006-03-12 Thread Hamish Moffatt
ia32-libc6 and libc6-i386 both contain /lib/ld-linux.so.2; neither of these seem to be obselete and both of them seem to be required on my system.. What's the newer naming? What's the correct resolution of the conflict? thanks, Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROT