Bug#670066: Bug #670066 python-openturns is unusable

[D. Barbier]

On 2012/5/15 D. Barbier wrote:
> On 2012/5/15 trophime wrote:
>> On Tue, 2012-05-15 at 01:43 +0200, D. Barbier wrote:
>>> On 2012/5/14 Aron Xu wrote:
>>> > The test build failed on amd64 and i386, at the same place. Attached
>>> > is my change to your git tree and the build log produced on amd64.
>>>
>>> Hello,
>>>
>>> Here is an updated status; I did not encounter your problems because
>>> my upstream tarball was buggy, we should now be in sync:
>>>   * a patch is needed to build with g++ 4.7
>>>   * few runtime tests fail with g++ 4.7, this is why it now
>>> Build-Depends: g++-4.6
>>>   * add Build-Depends: bc, it is needed by a single test
>>>   * fix handling of the rotRPackage R package during tests
>>>
>>> It builds fine in pbuilder, but I did not yet check upgrade path from
>>> openturns 0.15.  I believe that it could be uploaded in experimental
>>> or unstable when this is done.
>>>
>>> Denis
>>
>> Hi,
>> I had to explicitly specify python version in debian/rules to avoid an
>> FTBS when python 3.2 is installed. Please find attached the patch.
>
> Thanks Christophe,
>
> Patch applied.

Hello,

When testing upgrades from current openturns packages, I realized that
libopenturns0 and libopenturnss0.1 are not coinstallable because of
several file conflicts, and added the following changes:
  * rotRPackage is moved into its own binary package r-openturns-utils
  * install openturns.conf into /etc/openturns-1.0/openturns/
  * install wrappers into /usr/lib/openturns-1.0/

All changes have now been pushed into OT svn repository.  IMHO it can
be uploaded after editing debian/changelog.
The remaining questions are: should it be uploaded into unstable or
experimental?  What else is needed?

Denis