fedora-infrastructure

#7542 newer python-werkzeug in epel7-infra
Closed: Fixed by kevin. Opened by pingou.

Closed: Fixed
Reopen Issue
  • Describe what you need us to do:
    I'd like to hear more feedback on this idea.

Basically the version of python-werkzeug in RHEL7/CentOS7 is currently problematic. Among other, it replaces "+" by " " in http forms, that breaks uploading ssh keys/deploy keys (which often contains "+").

I could get all the unit-tests to pass on my RHEL7 box using a newer version of python-werkzeug (0.9.6, scratch-build: https://koji.fedoraproject.org/koji/taskinfo?taskID=32535657)

Since python-werkzeug is in RHEL proper we can't quite fix it in EPEL, unless we go the compat-package way (which for a 0.9.1 vs 0.9.6 is a little bit of a pity...).
A simpler but not ideal option is just to put that newer version in our epel7-infra tag.

I'd like to know what folks think is the best approach for this.

Thanks

Can we just poke RHEL Extras folks to upgrade it? It's a backwards-compatible change, so just get them to update it? We shouldn't need to work around them in this case.

Updates to packages inside of RHEL need to go through a large change control process which would take months to get done. This would be a stop-gap so you can continue to work until such a change was accepted or not.

Well, no time like the present. Bug report filed: https://bugzilla.redhat.com/show_bug.cgi?id=1672360

+1 to add python-werkzeug to epel7-infra until the bug is resolved in RHEL (if ever).

@mizdebsk Don't be so hopeless! If you assume that it can't change and don't try, it becomes self-fulfilling. I made the bug report so people can "pile on" and affirm it's needed.

@pingou Do you still need more feedback, or is this issue resolved and we can close the ticket?

Metadata Update from @mizdebsk:
- Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)

@mizdebsk if everyone agree then we should just do it but so far you've been the only one giving a clear answer :)

Metadata Update from @pingou:
- Issue priority set to: Waiting on Assignee (was: Waiting on Reporter)

Why don't we just add it now to infra tags and when/if they update it in rhel, we can drop it from infra?

If you do this, make sure that the Release is lower than what RHEL will ship it as (so Release: 0%{?dist}.1 or something similar).

@ngompa why? It should only ever be in infra tags, not epel... the only folks who would have it would be those that specifically built into epel7-infra right?

@kevin agreed, it should not matter

@kevin I'm just thinking of "clean upgrades" when handling via Ansible or other automation. Messing with EVRs directly is clumsy in automation tooling, so minimizing that would be useful.

ok, we have added this to epel7-infra. When/if rhel7 updates we can drop ours.

Thanks everyone.

:wine_glass:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.