Outdated abiword version

Current state of affairs:

Latest release in 2.2 branch is 2.2.11 which contains several important (security) fixes.

Latest stable release is 2.4.0.

I've assigned in Ubuntu to Sebastian. Seb, how is your pre-release life looking? Would it be utter insanity to try to get AbiWord 2.4.0 into Breezy? Should we assign to one of the backports guys?

We are pretty frozen now and my list of bug to fix for 5.10 is almost clean, I can update abiword de 2.4.0 today without any problem if that's what we want. Mark, do you want to push it? Has Matt been pinged about this, packages update need approval atm.

I haven't discussed it with MDZ. It's not in the desktop install by
default, so I think I could swing it, if you can get packages that you
are happy with. Is it a complex package? If it's quite straightforward,
and you are confident about your 5.10 bug list not being in jeapardy, go
ahead and create the packages.

Update: 2.4.1 is out, it fixes the same security issue as in 2.2.11. Tarball at http://www.abisource.com/downloads/abiword/2.4.1/source/abiword-2.4.1.tar.bz2

I heard Joshua M. Kwan (joshk) is already working on .deb packages.

Really make sure you get 2.4.1 as 2.4.0 as a few serious bugs + security problems.

If you need hand for that, let me know. As a wannabe MOTU and upstream maintainer I have knowledge of that :-) Not that I don't trust seb :-))

The new package has been uploaded to Debian today. I've built it with the small Ubuntu changes, the package is ready for upload if you want to push it.

MDZ: can we go ahead with AbiWord 2.4.1? It's got a bunch of security
fixes we would need in any event. Seb has built the package and all
seems well with it.

On Sat, Oct 08, 2005 at 11:33:46PM +0100, Mark Shuttleworth wrote:
> MDZ: can we go ahead with AbiWord 2.4.1? It's got a bunch of security
> fixes we would need in any event. Seb has built the package and all
> seems well with it.

No objections from me.

--
 - mdz

OK Seb, DOIT ;-)

Just a quick note about these security fixes: they are also in 2.2.11

Thanks for pushing 2.4.1 to Breezy

can't be an upstream bug because bug is about the version in the distribution.