[RFU] tighten build-depend on libslang2-dev >= 2.0.7

[G. Milde]

On 22.05.07, Rafael Laboissiere wrote:
> * Jörg Sommer <joerg at alea.gnuu.de> [2007-05-22 11:14]:

> > Rafael Laboissiere schrieb am Tue 22. May, 10:11 (+0200):
> > 
> > > I would like to reach consensus on this issue, otherwise we will have to
> > > resort to a vote.
> > 
> > I would leave the current situation (with build-dependency) as it is.

> Okay the outcome of the vote is: 
>     * 2 [GM, RL] for tightening the dependency to >= 2.0.7
>     * 1 [JS] for leaving the situation as it is currently

> Notes:    
>     + The packages in unstable and experimental are built anyway with
>       2.0.7-1, the version of libslang2 currently in unstable.
>     + If we backport, we can always drop the versioned build-dependency
>     + If it comes out that libslang2 2.0.7 is terribly buggy, then we will
>       revert the change and we will add a note in README.Debian about the 
>       segfault problem.

In the meantime, I filed two bugreports (one to libslang2 and one to jed)
explaining the problem. 

I could live with leaving the jed bug open as long as libslang2 2.0.6 is
in testing. Once testing is up to S-Lang 2.0.7, we could tag it "fixed in
testing/unstable".

Advantages: 
  * We do not introduce "artificial" requirements but leave the work to the
    Debian standard tools.
  * The open bugreport tells users that there is a problem.
  * More important, it helps useres stubling over it to find out the
    reason (and the fix, which is upgrading libslang2). 
    For me the most frustrating part of the problem was not finding out
    what happended (as there were no bug reports for S-Lang or Jed).
    

> If nobody objects to the above, I will upload 0.99.18+dsfg.1-7 soon.  Take
> this as an RFU.

I change my vote from "tightening" to "undecided" as long as the
bugreport is not closed without addressing the problem.

Guenter