[Parted-maintainers] Bug#697588: Breaks python-parted

[Colin Watson]

reassign 697588 pyparted
affects 697588 libparted0debian1
thanks

On Mon, Jan 07, 2013 at 12:02:23PM +0100, Sebastian Ramacher wrote:
> On 2013-01-07 11:24:07, Sjoerd Simons wrote:
> > After updating libparted0debian1 python-parted stops working..
> > 
> > With libparted0debian1 2.3-11 everyting is happy:
> > 
> > $ python -c 'from parted import Device'
> > $
> > 
> > after upgrading to 2.3-11.1:
> > 
> > $ python -c 'from parted import Device'
> > Traceback (most recent call last):
> >   File "<string>", line 1, in <module>
> >   File "/usr/lib/python2.7/dist-packages/parted/__init__.py", line 60, in <module>
> >     from partition import Partition
> >   File "/usr/lib/python2.7/dist-packages/parted/partition.py", line 260, in <module>
> >     partitionFlag[__flag] = _ped.partition_flag_get_name(__flag)
> > ValueError: Invalid flag provided.
> 
> Rebuilding pyparted against parted 2.3-11.1 fixes that.
> 
> According to codesearch.debian.net pyparted is the only package the
> uses PED_PARTITION_LAST_FLAG, so it should be the only affected package.

Mmm.  Normally I'd say that this is parted's fault anyway because it
broke ABI (and in an NMU, too ...), but really, this is not something
python-parted should ever have been relying on.  Although it's not
written out explicitly, I can't really believe that a sensible person
would have interpreted the existence of PED_PARTITION_LAST_FLAG after
due thought as a promise that no further flags would ever be added; it's
obviously just a "current final element in enumeration" #define for
internal use.  There's a similar problem with PED_DISK_LAST_FLAG too.

I'll fix this in pyparted (since it's maintained by the parted
maintainer team) and add a Breaks in libparted0debian1.

Thanks,

-- 
Colin Watson                                       [cjwatson at debian.org]