jed: loosen build-depend on libslang2-dev >= 2.0.7

[Rafael Laboissiere]

* Jörg Sommer <joerg at alea.gnuu.de> [2007-05-21 11:16]:

> Rafael Laboissiere schrieb am Mon 21. May, 10:05 (+0200):
> > * G. Milde <milde at users.sourceforge.net> [2007-05-21 09:09]:
> > 
> > > This is IMO a S-Lang problem. Either should libslang 2.0.6 be patched or
> > > replaced by 2.0.7. We could depend on libslang2 > 2.0.6-4 to leave these
> > > alternatives open.
> > 
> > I do not think that there is a way to depend on libslang2 >> 2.0.6-4, since
> > uploading such a version to the unstable would not work, since 2.0.7-1 is
> > already uploaded.  Besides, I doubt that the libslang2 maintainer would
> > maintain such a fork.
> > 
> > In sum: either we fix this with a tighter dependency or we let as it is now.
> 
> Let it as it is.

Unfortunately, we did not reach consensus on this issue.  I have no strong
feelings about tightening the build-dependency to >= 2.0.7.  I tend to agree
with Günter that the segfault problem warranties a bug report with severity
level "important" against the jed package.  However, I am also sympathetic
with Jörg's argument about possible bugs introduced in 2.0.7 (although he
confirmed it is mainly FUD).

At any rate, only a build-dependency is .  Notice that even when building
against libslang2 2.0.7-1 (the version currently in unstable), we end up
with:

  Depends: libslang2 (>= 2.0.6-3)

as calculated by dpkg-shlibdeps (cf /var/lib/dpkg/info/libslang2.shlibs).

Also, the backporting problems argument seems quite weak to me, because we
can always drop the versioned dependency when building the package.

I would like to reach consensus on this issue, otherwise we will have to
resort to a vote.

-- 
Rafael