Bug 1550104 - python changes
Summary: python changes
Keywords:
Status: CLOSED EOL
Alias: None
Product: Spacewalk
Classification: Community
Component: Release
Version: 2.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: spacewalk-review
TreeView+ depends on / blocked
 
Reported: 2018-02-28 14:03 UTC by Miroslav Suchý
Modified: 2020-03-06 14:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-06 14:47:53 UTC
Embargoed:


Attachments (Terms of Use)

Comment 1 Tomáš Kašpárek 2018-03-02 10:06:23 UTC
None of these PRs applies to us as the PR changes things which apply for RHEL. Fedora Requires and BuildRequires are already using correct pythonX-%{name} syntax.

PRs should be closed.

Comment 2 Miroslav Suchý 2018-03-13 13:51:43 UTC
????
e.g. here
  https://github.com/spacewalkproject/spacewalk/blob/master/client/rhel/rhn-client-tools/rhn-client-tools.spec#L109
I still see python-coverage instead of python2-coverage

Comment 3 Tomáš Kašpárek 2018-03-13 15:05:57 UTC
(In reply to Miroslav Suchý from comment #2)
> ????
> e.g. here
>  
> https://github.com/spacewalkproject/spacewalk/blob/master/client/rhel/rhn-
> client-tools/rhn-client-tools.spec#L109
> I still see python-coverage instead of python2-coverage

I see python3 package has correct require of python3-coverage, python2 package should not probably be built at all for F28.

Reopening BZ to see whether it makes sense to stop building python2 subpackages.

Comment 4 Michael Mráka 2020-03-06 14:47:53 UTC
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.


Note You need to log in before you can comment on or make changes to this bug.