[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#573486: marked as done (RM: emacs22/22.3+1-1.2)

Your message dated Tue, 18 May 2010 20:26:49 +0100
with message-id <1274210809.3289.1923.camel@kaa.jungle.aubergine.my-net-space.net>
and subject line Re: Bug#573486: RM: emacs22/22.3+1-1.2
has caused the Debian Bug report #573486,
regarding RM: emacs22/22.3+1-1.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
573486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573486
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: rm

Please remove emacs22 from testing. It's superseded by emacs23
and the last remaining dep in Squeeze (python2.5-doc) should
transition to testing in three days.

Cheers,
        Moritz

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=de_DE.ISO-8859-15@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
On Tue, 2010-05-18 at 21:08 +0200, Sven Joachim wrote:
> On 2010-05-17 21:06 +0200, Adam D. Barratt wrote:
> > However, as emacs22 is still in unstable and does not have any RC bugs,
> > it migrated back in to testing this morning.  One or other of those
> > things should probably be fixed. :-)
> 
> I just filed #582156 to prevent re-migration, so you can try again.
> Removal from unstable will probably have to wait because hyperlatex
> still depends on emacs22, and that bug (#571122) appears to be
> non-trivial to fix; at least I have no idea what is going on there.

Thanks.  I've added a new removal hint, so this should be completed
tonight.

Regards,

Adam

--- End Message ---
Reply to: