stable
FEDORA-EPEL-2020-0b41dd16a1 created by ellert a year ago for Fedora EPEL 7

BDII 5.2.26

This update has been submitted for testing by ellert.

a year ago

This update's test gating status has been changed to 'ignored'.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'ignored'.

a year ago

This update has been pushed to testing.

a year ago

This update can be pushed to stable now if the maintainer wishes

a year ago

This update has been submitted for stable by bodhi.

a year ago

This update has been pushed to stable.

a year ago

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 @andreamanzi

Once an update is in stable, it can not be unpushed. This seems to have tripped on that the default for encode() and decode() is 'ascii' in python 2.7 and not 'utf-8' as it is in python 3. There are two possible fixes to this: Change the code to use encode('utf-8') and decode('utf-8') to explicitly request the utf-8 encoding. Or change the specfile so that bdii uses python 3 also for EPEL 7 (as it already does for EPEL 8 and Fedora).

Since there are changes in the upstream git that indicate that upstream will change to python 3 for all releases, I have adopted this change for EPEL 7. The update is here:

FEDORA-EPEL-2021-2978244eeb

Let me know if this addresses the issue or not. If you can find users to provide karma for the update, it can go stable quicker.

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


Please login to add feedback.

Metadata
Type
enhancement
Karma
0
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
14 days
Dates
submitted
a year ago
in testing
a year ago
in stable
a year ago

Automated Test Results