Please allow jedstate_0.5.4.transitional.1-1 and jed-extra_2.2.1-1.etch.1

[Steve Langasek]

On Tue, Feb 06, 2007 at 04:50:16PM +0100, Rafael Laboissiere wrote:
> * Rafael Laboissiere <rafael at debian.org> [2007-02-06 10:10]:

> > * Rafael Laboissiere <rafael at debian.org> [2007-02-06 00:06]:

> > > * Rafael Laboissiere <rafael at debian.org> [2007-02-05 23:29]:

> > > > Request (short):

> > > >     Please, allow jedstate_0.5.4.transitional.1-1 and
> > > >     jed-extra_2.2.1-1.etch.1 in testing.

> > > Update: the version of jedstate currently in unstable is 
> > > 0.5.4.transitional.1-2 (I added a postinst script to the pacakge).

> > New update: the version of jed-extra in unstable is now 2.2.1-1.etch.2.  I
> > added two lines of autoloads in an itialization file (needed for
> > gdbmrecent).  The diffs are attached below.

> This is the last update, really (or hopefully).

> After discussion in the pkg-jed-devel mailing list, we decided to improved
> the situation in the following way: the changes made in jed-extra
> 2.2.1-1.etch.2 are reverted in 2.2.1-1.etch.3, what makes this later version
> virtually the same as 2.2.1-1.etch.1.  On the other hand, the jedstate
> package now in unstable (0.5.4.transitional.1-3) is now rather "functional"
> than "transitional", in the sense that it ensures that the gdbmrecent module
> will really work.  

> In sum, this fixes RC Bug#406815 and removes the obsolete and unmaintained
> jedstate code from Debian, so please allow:

>     * jedstate_0.5.4.transitional.1-3
>     * jed-extra_2.2.1-1.etch.3

> in testing.

I've unblocked jed-extra, and am in the process of reviewing jedstate.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/