Re: from 1.3 to hamm

1997-06-28 Thread joost witteveen
> I've successfully completed the 1.2 to 1.3 update on all my current > packages (love that dselect). And now I see some updates and bug-fixes I > would like to use starting to show up in hamm (I already have xfree and > xemacs19), however, I see that more of them are being compiled with the > new

from 1.3 to hamm

1997-06-28 Thread David Morris
I've successfully completed the 1.2 to 1.3 update on all my current packages (love that dselect). And now I see some updates and bug-fixes I would like to use starting to show up in hamm (I already have xfree and xemacs19), however, I see that more of them are being compiled with the new glibc6.

Re: from 1.3 to hamm

1997-06-27 Thread Marcelo E. Magallon
> Maybe I don't understand the stable/unstable concept of debian, but I > don't see any reason why they don't go to stable. An easy one: stable is just that, stable. It won't change. Unless a bug is found, nothing goes into stable after the release date. For example, right now XFree 3.2 is in stab

Re: from 1.3 to hamm

1997-06-27 Thread Martin . Bialasinski
On 26 Jun, joost witteveen wrote: > > No packages updates at all require an installed libc6, as long as > you mean updates from stable (not many at the moment!). > Right. Right as well on "not many". Why is the new upstream version of fetchmail or xisp only in unstable for example. This way one h