Re: [EPEL-devel] crlibm and libscs for EPEL 7?

[Dominik 'Rathann' Mierzejewski]

On Saturday, 10 October 2015 at 01:01, Rich Rauenzahn wrote:
> On 10/9/2015 1:54 AM, Dominik 'Rathann' Mierzejewski wrote:
> >You could ask to become the maintainer in EPEL: 
> >https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer
> >
> >>That looks like quite an involved process with an uncertain outcome ...
> >The process may look involved at first, but it's usually not that much
> >work after the initial formalities. Why do you think the outcome is
> >uncertain?
> 
> There are a lot of caveats listed in the requirements to be approved as a
> package maintainer after the initial formalities (some of which I started!).
> Finding a sponsor, contributing in "other ways" than just supporting the
> specific packages that I need.  I don't want to commit to things I wouldn't
> be able to follow through on.

That's quite understandable. Speaking as a sponsor myself, the minimum
I require from the people I sponsor is that they make at least two
non-trivial informal package reviews to show that they understand the
Packaging Guidelines and that they submit one package of their own.

In this case showing the crlibm and libscs spec files for EPEL7 branch
and doing a couple of informal reviews should be enough for sponsorship.
Unfortunately I don't have time for another sponsoree at the moment.

> >>Is that the only viable option at the moment?  Adopt it myself?
> >I'm afraid that's how it works for most packages. People who use the
> >software and have the skills to maintain it usually do it.
> >
> >You can also pay someone to maintain it for you. ;)
> 
> Don't have that ability (pay) in the position I'm in at my company, and

I was half-kidding there.

> realistically, I can just check the rpm I built into our ansible repository.
> Or rewrite my software to not use pyinterval.

Of course, but in my opinion, it's better to share.

> I've re-built/modified some rpm packages, but don't profess to be anywhere
> near an expert level.  More in the amateur realm, but enough to modify an
> existing rpm to build on newer platforms or to swap out versions of source.

Don't worry. Nobody is born with rpm packaging knowledge. Many of us are
(still) amateurs and there are a lot of people ready to lend a hand in
this community, so don't be afraid to get your feet wet, please.

Regards,
Dominik
-- 
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: [EPEL-devel] crlibm and libscs for EPEL 7?

[Rich Rauenzahn]

On 10/9/2015 1:54 AM, Dominik 'Rathann' Mierzejewski wrote:
You could ask to become the maintainer in EPEL: 
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer 


That looks like quite an involved process with an uncertain outcome ...

The process may look involved at first, but it's usually not that much
work after the initial formalities. Why do you think the outcome is
uncertain?


There are a lot of caveats listed in the requirements to be approved as 
a package maintainer after the initial formalities (some of which I 
started!).  Finding a sponsor, contributing in "other ways" than just 
supporting the specific packages that I need.  I don't want to commit to 
things I wouldn't be able to follow through on.



Is that the only viable option at the moment?  Adopt it myself?

I'm afraid that's how it works for most packages. People who use the
software and have the skills to maintain it usually do it.

You can also pay someone to maintain it for you. ;)


Don't have that ability (pay) in the position I'm in at my company, and 
realistically, I can just check the rpm I built into our ansible 
repository.  Or rewrite my software to not use pyinterval.


I've re-built/modified some rpm packages, but don't profess to be 
anywhere near an expert level.  More in the amateur realm, but enough to 
modify an existing rpm to build on newer platforms or to swap out 
versions of source.


I'll give it more consideration and get back to you.

Rich
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: [EPEL-devel] crlibm and libscs for EPEL 7?

[Orion Poplawski]

On 10/08/2015 05:59 PM, Rich Rauenzahn wrote:

On Wed, Oct 7, 2015 at 1:16 PM, Orion Poplawski  wrote:

On 10/07/2015 02:05 PM, Rich Rauenzahn wrote:

Tim got back to me quickly.  He doesn't have the time or need to
maintain them for EPEL 7.  He offers to pass on the ownership to
another packager.


You could ask to become the maintainer in EPEL:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer


That looks like quite an involved process with an uncertain outcome ...

Is that the only viable option at the moment?  Adopt it myself?

Rich


Well, obviously not - any interested Fedora packager could take it over. 
 But it is the way you can take control and contribute to the community.


--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA DivisionFAX: 303-415-9702
3380 Mitchell Lane  or...@cora.nwra.com
Boulder, CO 80301  http://www.cora.nwra.com
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: [EPEL-devel] crlibm and libscs for EPEL 7?

[Rich Rauenzahn]

On Wed, Oct 7, 2015 at 1:16 PM, Orion Poplawski  wrote:
> On 10/07/2015 02:05 PM, Rich Rauenzahn wrote:
>> Tim got back to me quickly.  He doesn't have the time or need to
>> maintain them for EPEL 7.  He offers to pass on the ownership to
>> another packager.
>
> You could ask to become the maintainer in EPEL:
> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer

That looks like quite an involved process with an uncertain outcome ...

Is that the only viable option at the moment?  Adopt it myself?

Rich
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: [EPEL-devel] crlibm and libscs for EPEL 7?

[Orion Poplawski]

On 10/07/2015 02:05 PM, Rich Rauenzahn wrote:
> Tim got back to me quickly.  He doesn't have the time or need to
> maintain them for EPEL 7.  He offers to pass on the ownership to
> another packager.

You could ask to become the maintainer in EPEL:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer

-- 
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301   http://www.nwra.com
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: [EPEL-devel] crlibm and libscs for EPEL 7?

[Rich Rauenzahn]

Tim got back to me quickly.  He doesn't have the time or need to
maintain them for EPEL 7.  He offers to pass on the ownership to
another packager.

What next?

On Wed, Oct 7, 2015 at 11:46 AM, Stephen John Smoogen  wrote:
> On 7 October 2015 at 12:27, Rich Rauenzahn  wrote:
>> Hi,
>>
>> I have a project that requires pyinterval, which requires crlibm which
>> requires libscs.  These were available on EPEL 6, but aren't currently
>> for 7.
>>
>> I've managed to rpmbuild crlibm and libscs directly from the EPEL6
>> source rpms.  (A couple of texlive rpm dependencies for crlibm aren't
>> documented properly, though.)
>>
>> Is it possible to get these published again by EPEL?  Do we know why
>> they are no longer published in 7?  How can I help?
>>
>
> Packages in EL7 are brought in when the package owner is willing to
> support them there. Usually the owner doesn't want to support it in
> EPEL until someone requests it of them because they want to know it is
> actually being used
>
> In this case the two packages are owned by the same packager Tim
> Niemueller who can be reached at t...@niemueller.de
>
> I would email him and see if he is willing to put it in EPEL-7. If he
> is then it should just need a branch request from him and a package
> build. If he isn't then you can look to find someone who is willing to
> own the package in EPEL.
>
>> Rich
>> ___
>> epel-devel mailing list
>> epel-devel@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/epel-devel
>
>
>
> --
> Stephen J Smoogen.
> ___
> epel-devel mailing list
> epel-devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/epel-devel
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel