Bug#790816: RFS: roxterm/3.0.1-1

[Tony Houghton <h@realh.co.uk>]

On 04/07/15 22:29, Vincent Cheng wrote:

> (If you have time, please upload an updated package to mentors so it's
> easier to discuss any further changes.)

I've done that, hopefully it will be available by the time you read
this. The Breaks/Replaces I've decided on are as follows:

Package: roxterm-data
Replaces: roxterm-common
Breaks: roxterm-common (<< 3.0.0)

    I don't think it needs to explicitly Break any other packages,
    because their removal/replacement will be forced along with
    roxterm-common.

Package: roxterm
Replaces: roxterm-gtk3 (<< 3.0.0), roxterm-gtk2 (<< 3.0.0)
Breaks: roxterm-gtk3 (<< 3.0.0), roxterm-gtk2 (<< 3.0.0)

    I originally also had it Break the old -dbg packages, but I think
    that's superfluous for the same reason as above.

Package: roxterm-dbg
Replaces: roxterm-gtk3-dbg (<< 3.0.0), roxterm-gtk2-dbg (<< 3.0.0)
Breaks: roxterm-gtk3-dbg (<< 3.0.0), roxterm-gtk2-dbg (<< 3.0.0)


roxterm-gtk2, roxterm-gtk3, roxterm-gtk2 and roxterm-gtk3 are now all
dummy packages, they don't Break or Replace anything because the
packages they depend on should take care of everything, and as virtual
packages they don't contain files that clash with others.

Nothing explicitly breaks the old virtual package roxterm, I can't see a
need for that with all the other relationships I have.

I've tested what should be the most difficult upgrade scenario in the
piuparts chroot and it went smoothly.

Other changes:

I think debian/rules was passing CFLAGS etc to ./mscript.py configure
incorrectly so I've fixed that.

During testing I had a problem with changes wrt the tarball in a pot
file while trying to repeat a build so I've added a
debian/source/options with extend-diff-ignore for .pot and .po.