Package: beagle
Version: 0.2.7-1
Severity: important

        Hi,

 It seems the old and new version of beagle were mixed when adding the
 Conflicts/Replaces for the Python transition.

 The current python-beagle package in unstable, 0.2.7-3, has:
 Replaces: python2.4-beagle (<< 0.2.6-2)
 Conflicts: python2.4-beagle (<< 0.2.6-2)

 Either you meant <= or you meant << 0.2.7-1, the later probably being
 safer for derivatives.

 This is perhaps a "serious" bug because the old package Provides
 python-beagle and Conflicts with python-beagle (unversionned).  I hope
 that package managers will handle this nicely.  I'm not 100% sure a
 dummy package isn't needed in this case.

 FYI, I'm still with python2.4-beagle 0.2.6-2.

   Bye,
-- 
Loïc Minier <[EMAIL PROTECTED]>

Reply via email to