On Tue, Jan 19, 1999 at 03:25:17PM -0600, Adam Heath wrote:
> These 'pkgs' will have to remain in the system forever. If someone skips
> slink, and goes to potato when that is released, the same problem will occur.
We have to get rid of old practices at some point. We do not need to make the
sa
Yes, emacs19 is in Incoming for frozen and unstable, in fact, the
second version is there because people actually snarfed the first one
(which was unstable-only) and filed bug reports (yay.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO
Hi,
Thanks and bravo! I'm getting tired of fighting with dselect,
which insists on replacing my emacs 19.34-13 with emacs20.
Bob
> Hi,
>
> I meant emacs19, and I think it is felt to be a bug fix
> release, (not working with the other debian emacsen setup is a pretty
> major bug) s
Hi,
I meant emacs19, and I think it is felt to be a bug fix
release, (not working with the other debian emacsen setup is a pretty
major bug) so it shall be in hamm (I think the release manager has
already blessed this).
manoj
--
"Your development gets rotten if you take too
Hi,
Did you really mean 18 or is that a typo for 19?
Is it going to hamm or slink? It seems to me that emacs19 should
be in 2.0, but the release policy would seem to require it to go in
slink.
Bob
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> emacs18 is also present in Incomi
Hi,
The emacsen problem is due to the fact that as distributed,
elib is buggy. If you remove elib (which also nukes cvs-pvl ;-(),
emacsen-common +emacs20 shall work.
emacs18 is also present in Incoming now, and has the same
problem with elib (I locally hacked the Makefile to ma
-BEGIN PGP SIGNED MESSAGE-
Hi there,
I somewhere read that you need more beta testing of frozen, so I
updated my system yesterday. Here's my report:
System: P100, 64 MB RAM, IBM 4,3 GB (DCAA), Quantum 1,2 GB (Fireball),
Fritz! ISDN, Spea Mercury P64
OS: WinNT and Debian 1.3.
7 matches
Mail list logo
