Remove Python 3 version of module to fix RC bug? (python-exif)
I just now don't have the time to look at bug #775609 (python3-exif doesn't work, RC). If nobody steps in, I would upload a new package w/o Python 3 support for jessie. Wheezy hat python-exif, but not python3-exif, so there is no regression for users of wheezy. Anyway, upstream made a new release with Python 3 fixed, so I would package this right after Jessie release and provide a backport. Questions: - is removing the Python 3 package the right thing to do? - how to do this? just remove it from debian/control? Thanks in advance! (If somebody has time to really fix the bug, this would be very much appreciated, of course!) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150125115004.GA14958@fama
Re: Remove Python 3 version of module to fix RC bug? (python-exif)
Hi, To remove the binary package two things are needed: - do not build the binary package anymore. Removing it from d/control does the trick, but will leave a lot of cruft from the source package. For example, d/python3-exif.install will be unused as well as the sed line in d/rules. You will also need to remove python3-* from Build-deps. - remove the leftover binary package. In this case this should be automatic: auto-cruft should detect that python3-exif is NBS (Not Built from Source) and this should automatically propagate to testing (as there are no reverse dependencies for python3-exif). You can have a look at https://wiki.debian.org/ftpmaster_Removals for more info. Cheers -- Etienne Millon signature.asc Description: Digital signature
