Bug 1189917 - pyutil in EPEL
Summary: pyutil in EPEL
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pyutil
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 560457
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-05 20:01 UTC by Vladimir Stackov
Modified: 2016-07-19 12:46 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 12:46:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vladimir Stackov 2015-02-05 20:01:49 UTC
Greetings,

I would like to see pyutil in in Extra Packages for Enterprise Linux
(EPEL) [1] and opening this bug as you didn't yet let the EPEL team
know via the Contributor Status [2] page if you are planning to build
this package in EPEL.

Are you interested in maintaining your packages in EPEL? EPEL is an add-on
repo for RHEL and compatible spinoffs such as CentOS. EPEL uses the same
CVS and the same build servers as Fedora and a lot of Fedora maintainers
are EPEL maintainers as well; the main difference is just that packages
in EPEL are updated more carefully and supported for a longer timeframe.
See [3] and [4]  for details. In short: EPEL tries to ship a package once
and update it to later versions only when there is a strong need to.

For branching your packages for EPEL follow the standard Fedora
procedure [5] -- instead of F20 or F21 targets just use EL6 and EPEL7 as
branch names.

If you are not interested in EPEL please let the EPEL contributors know
and update the information on [2] to avoid further reports like this --
that just takes a minute or two and would be a great help for the EPEL
team. Please note that EPEL maintainers that might want to see your
package in EPEL will likely start to maintain the package in EPEL sooner
or later and thus become co-maintainers [6] of your packages for EPEL.

I appreciate your help with EPEL.

[1] http://fedoraproject.org/wiki/EPEL

[2] http://fedoraproject.org/wiki/EPEL/ContributorStatus

[3] http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies

[4] http://fedoraproject.org/wiki/EPEL/FAQ

[5] http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure

[6] http://fedoraproject.org/wiki/Extras/Policy/EncourageComaintainership

Comment 1 anish 2015-02-06 05:21:55 UTC
Hi

thanks, created change request on https://bugzilla.redhat.com/show_bug.cgi?id=560457

Comment 2 Vladimir Stackov 2015-02-13 19:26:09 UTC
Any estimations? If you don't have enough time I could co-maintain EPEL branches.

Comment 3 anish 2015-02-13 19:33:35 UTC
Pyutil depends on python-zbase32  https://bugzilla.redhat.com/show_bug.cgi?id=1190308
and  python-zbase32 depends on python-setuptools https://bugzilla.redhat.com/show_bug.cgi?id=1190752

So until python-setuptools has not been build we cant build pyutil

Comment 4 Jaroslav Reznik 2015-03-03 16:50:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 6 Fedora End Of Life 2016-07-19 12:46:56 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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