Please sync cyphesis-cpp 0.5.15-1 (universe) from Debian unstable (main)

There were two set of changes made in 0.5.8-2ubuntu1:

- Teach the upstream build about python2.5.
- Source changes to build with python2.5.

You are correct that the first set has been implemented upstream. I think you have however missed to check in detail the second one.
I checked those and I still see one change that has not been implemented upstream.
Can you check what this change is and then we discuss further what to do about it?

This are the other changes... but I builded it in pbuilder and any error comes.

Yes, these are the ubuntu changes. My question was: which one of these was not implemented upstream and why can we drop it?

I and Cesare (norsetto) worked together is this one and conclued the only Ubuntu change that has not been applied upstream is related to the addition/removal of members in the initialization of the Operation_seq struct in rulesets/Py_Operation.cpp.

We believe however that upstream is correct since these extra members are not used as the relevant flags (Py_TPFLAGS_HAVE_SEQUENCE_IN and
Py_TPFLAGS_HAVE_INPLACEOPS) are not set as explained in the api documentation (http://docs.python.org/api/type-structs.html).

Cesare: if you're OK with it, can you ACK it and document it on https://wiki.ubuntu.com/MOTU/Council/KmosReport?action=edit ?

I'm OK and I also think we should sync, but I would like to have a justification for the request from Marco?

Hi!

1- The changes doko have done in the package should be reverted with this sync.
2- The bashism fixing.
3- Compile with gcc 4.3.
4- Add chrpath to Build-Depends and use it to remove rpath in binaries.
5- New upstream man pages included.
6- Add Portuguese translation to debconf.
7- Oldest version in Hardy.

I think this is enough to get it synced at this time (before FF).

Do you realise that for each sync request an archive admin has to spend his time to check it and manually sync it?
What is it that makes this a MUST have for hardy?

I know the process of a archive admin to process the request syncs, but it's the only way to get things updated, fixed, when we don't need a ubuntu delta (else if I'm an MORU I can upload it myself, I don't like to bring work to others). I really don't know what's in fault to mention to have it ACK'ed.

And why would an update be necessarily good?
I see here still servers running the 0.5.8 version: http://www.worldforge.org/dev/metaserver.
Even though this was released 1.5 years ago I don't see any request for an update in Launchpad?

ACKed.

Marco: you're right: this is the only way to get something synced, but it's better to be prepared to answer the question "why should we do this?" - one good source for information is diffing the upstream changelog. As it happens the new releases fix memory leaks and a bunch of other bugs.

synced, thanks