Comments

43 Comments
karma

The new package installs fine, cannot test it at the moment on every BDII flavors but it should work ok

Hi Matthias

see the comment i added on the previous upgrade

FEDORA-EPEL-2020-0b41dd16a1

cheers

Andrea

Hi Matthias,

sure sorry i got confused, the unpush is possible until the push to stable is pending.

For sure we are planning to have the BDII available only on py3, but since we haven't done yet proper testing we would like to avoid switching now to fix this issue.

Given also that the tag available in github (https://github.com/EGI-Foundation/bdii/tree/v5.2.26) and in UMD, does not contain the patch for py3 compatibility that is causing this problem, we believe the best solution for now would be remove that patch ( at least from EPEL7) and keep using py2.

Let me know what do you think

thanks

Andrea

Hi Matthias, looks like there is a problem with the latest push, see (https://github.com/EGI-Foundation/bdii/issues/37) do you think it's possible to unpush the update? it's in stable since 2 weeks so hopefully no many have upgraded thanks Andrea

Hi Denis unfortunately i have a problem with the latest soci. Sometimes our server crashes with a SIGABRT and this is what i see within gdb

0 0x00007f453bd52337 in raise () from /lib64/libc.so.6

1 0x00007f453bd53a28 in abort () from /lib64/libc.so.6

2 0x00007f453c6627d5 in _gnu_cxx::_verbose_terminate_handler() () from /lib64/libstdc++.so.6

3 0x00007f453c660746 in ?? () from /lib64/libstdc++.so.6

4 0x00007f453c65f6f9 in ?? () from /lib64/libstdc++.so.6

5 0x00007f453c660364 in __gxx_personality_v0 () from /lib64/libstdc++.so.6

6 0x00007f453c0f98a3 in ?? () from /lib64/libgcc_s.so.1

7 0x00007f453c0f9dd7 in _Unwind_Resume () from /lib64/libgcc_s.so.1

8 0x00007f452c934100 in soci::details::once_temp_type::~once_temp_type() () from /lib64/libsoci_core.so.4.0

like an exception is thrown from that destructor, but even if we catch it in our code its not handled

Have you ever seen this in your experience with SOCI 4? thanks a lot Andrea

ok, i'm running tests and everything looks ok so far

i have just updated the FTS update to remove autopush BTW

thanks Andrea

Hi Denis,

thanks a lot for your reply and for your action. i tried also a local build and my component was fine with that version, but i would like to do more testing of course to see that everything is fine.

We are also about to release a new version of the component and indeed i wanted to tell you to wait to rebuild until we are ready, but you were too fast:-)

i will let you know in case i find issues with my testing, but in principle i'm fine to just release a new build. If we are the only users of this package (strange!) we don't need to spend time on compatibility packages and the like.

thanks

Andrea

Hello,

are you going to provide also a compat package for version 3.2? i don't think you can push a major upgrade of a library on EPEL as there is also a mojor soname bump

thanks

Andrea

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

works fine for me

works fine for me

i can install nagios-plugins-fts-3.5.0-3.el7.noarch from EPEL testing without problems. where do you see dependency problems?

works fine

works fine

karma

works fine

karma

works fine

works fine for me

This update has been unpushed.