downgrading jed0.99.18 to /testing fails
Rafael Laboissiere
rafael at debian.org
Mon Jun 12 13:13:31 UTC 2006
* G. Milde <g.milde at web.de> [2006-06-12 14:52]:
> I had (in my chroot debian base system) jed, jed-common and jed-extra in the
> /experimental version (0.99.18).
>
> Downgrading just jed to /testing with apt-get went fine:
>
> # apt-get install jed/testing
> ...
> dpkg - warning: downgrading jed from 0.99.18-2 to 0.99.16-6.
> ...
> Unpacking replacement jed ...
> Setting up jed (0.99.16-6) ...
>
> but jed is now broken:
>
> # jed
>
> starts jed but stops with the error message
>
> S-Lang Error: Byte compiled file appears corrupt
I do not think that we should bother with eventual problems with users
downgrading individual pacakges, but anyway...
> Do we need a conflict of jed 0.99.18 with earlier versions, something like
>
> Conflicts: jed (<=0.99.17)
> Replaces: jed (<=0-99.17)
>
> ?
This is superfluous because, by default, any new version of a package
will conflict & replace the previous ones.
> Would this help? (As the point is that we need to downgrade jed-common
> together with jed in order to let it work properly.)
> So, maybe
>
> Conflicts: jed-common (<=0.99.17)
> Replaces: jed-common (<=0-99.17)
> ?
In which package we are proposing the above?
At any rate, I think that the right thing to do is to put the following
in jed-common_0.99.18:
Conflicts: jed (<< 0.99.18), xjed (<< 0.99.18)
--
Rafael
More information about the Pkg-jed-devel
mailing list