Please backport efax-gtk 3.2.2-1

I just updated the release in Maverick so that we could consider it (we don't do backports from a higher Debian version)

I have a few questions however:

1) were any changes needed to the source to have it build in lucid?
2) Is this a bugfix or feature request?

Please advise.
Steve

Hello Steve,
Thank you for your attention.
It's a feature request to follow a new feature of ghostscript. Without a new feature for efax, efax is broken due to the new feature of ghostscript...
More information here : http://comments.gmane.org/gmane.comp.printing.ghostscript.cvs/9046
efax-gtk 3.2.1 and further have this new feature.

Good information - but if it is a bugfix, a Stable Release update will help a wider range of users while backports only help those who have backports enabled.

As far for me, I have suscribed to this bug #587064 because it addressed my current problem with efax-gtk. I assumed that Alessio asked for a backport because he thought that it was not possible to correct the issue with a stable release update. So, if it's possible as you suggest, of course it would be better than a backport !

I've opened a backport request, because I've thought it was a simple way to test if 3.2.2-1 is working well for Lucid users and because I've take a look at the changelog between 3.2.2-1 and 3.0.17-1 and I've see that there are lot of changes (so I think a SRU is a bit complicated); bug #536639 was marked "Fix committed" because 3.2.2 was released, but it corrects the issue only in Maverick...Steve I don't know very well SRU flow, so can you please open a SRU for e-fax in Lucid? Or I should reopen bug #536639 ?