Bug 1409812 - Plans for EPEL
Summary: Plans for EPEL
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Sys-Mmap
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jason Tibbitts
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-03 13:55 UTC by Andrew Bauer
Modified: 2017-01-04 01:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-04 01:38:19 UTC
Type: Bug


Attachments (Terms of Use)

Description Andrew Bauer 2017-01-03 13:55:13 UTC
Description of problem:
hi,
The perl-Sys-Mmap package currently exists in Fedora repos, but not EPEL. 

Per the instructions in the "Getting_a_Fedora_package_in_EPEL" wiki guide, I am filing a bug report to learn whether the current maintainer is willing, or has plans, to build this package for the EPEL 6 & 7 repos. 

If needed, I am willing to participate in any level that is necessary. Thank you.

Comment 1 Jason Tibbitts 2017-01-03 17:23:10 UTC
You forgot to say why.  Does something else need this package?

I can probably do EL7; I don't think it would take too much extra effort.  Probably not EL6, though; packaging there is a bit different.  In any case, you're welcome to request those branches yourself if you're a packager.

Comment 2 Andrew Bauer 2017-01-03 18:11:28 UTC
Hi Jason,
The short answer to the "why" question is because zoneminder depends on it. 
I've given a more in-depth answer over in the fedora devel list if you are interested:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/G4LBTRW52OAGEO3AFE6APZUHXUGHBIUQ/

I am just learning the ropes of the Fedora system so my apologies if I am doing something incorrectly or in an atypical fashion. Rest assured, I am quite serious about getting all of zoneminder's (non-ffmpeg) dependencies into both EPEL & Fedora. I do have someone willing to sponsor me if needed.

I've been managing my own packages, including perl-Sys-Mmap, in a small repo at zmrepo.zoneminder.com, and I just uploaded perl-Sys-Mmap to my Copr repo as well:
https://copr.fedorainfracloud.org/coprs/kni/zoneminder_deps/build/495048/

Don't know if any of that helps. Small tweaks were made, but  I don't recall having to do anything special to get it to install or build properly on el6.

I think I know where to request a new branch. Since I'm not yet an official packager, I don't know if I can, but I will certainly try. thank you.

Comment 3 Jason Tibbitts 2017-01-03 19:12:11 UTC
Yeah, zoneminder is why I originally added it, since I used to maintain zoneminder in Fedora.  But I ended up writing my own far simpler security system and handing zoneminder off to someone else.  To be honest I'm happy to hand off the rest of the stack as well.

But zoneminder is exactly the kind of thing that I thing should not be in EPEL, since it doesn't (or at least didn't) necessarily support transparent upgrades between versions.  That means you can never do a version bump.  Proper support means you have to backport security fixes, and that's not a good thing at all.

EL6 support is an issue for me because I usually keep my spec files up to current Fedora guidelines, and the RPM in EL6 is too old.  I did a bunch of work in epel-rpm-macros to clean up some of those differences, but it can't support the current Perl packaging guidelines, for example.

In any case, if you want to be a packager then I can make that happen.

Comment 4 Andrew Bauer 2017-01-03 21:29:44 UTC
Seems we are on the same page.

After a discussion with a couple other Fedora packagers, we all agreed that zoneminder should live outside of Fedora. I have since opened a new package request with RPMFusion for zoneminder, and it is currently under peer review over there.

Several of ZoneMinder's dependencies, on the other hand, seem to best belong in the Fedora and EPEL repos, so here I am.

If all goes as planned, eventually I will be able to relegate zmrepo to testing, bleeding edge stuff only.

I would much appreciate it if you could make me a packager, but I completely understand if normal policy dictates I work with a sponsor first. 

There is a lot to talk about when it comes to improving zoneminder, but perhaps we should have that discussion elsewhere if you are ever interested. I'm part of the upstream project, and during the day I'm usually in the zoneminder irc channel on freenode.

Comment 5 Jason Tibbitts 2017-01-03 21:55:13 UTC
Is your FAS account "kni"?

To be completely honest I'm just not interested in zoneminder any longer as I have no use for it.  I ended up with a far simpler solution which isn't really "general purpose" but which works for me.  I have newer Axis cameras and just have them configured to stream uploads via http when their motion detection is triggered.  A small flask app presents the recordings.  It certainly could be better and absolutely requires Axis cameras supporting a particular firmware level, but... it works and is a tiny fraction of the code.  Eventually I will release the code but at this point I'm too lazy.

Comment 6 Andrew Bauer 2017-01-03 22:16:31 UTC
Yes, that's my FAS account name. Thank you.

Hey, I get it. Simple is definitely one of the things zoneminder is not. I'd like to say it has become simpler, but it is still not simple.

That's the direction the surveillance industry is headed... where all the "thinking" happens in the camera, rather than the server. Makes the overall system infinitely scalable. Some of the fancier cameras can even do analytics in the camera.

With the newer versions of ONVIF, manufacturers are standardizing on ways to read the motion detection meta data from their cameras. Should make implementing a single driver easier, but it is one of many things I need to make time for. Always too many ideas in my head and not enough time to do them all.

Comment 7 Fedora Admin XMLRPC Client 2017-01-04 01:37:37 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 8 Jason Tibbitts 2017-01-04 01:37:53 UTC
OK, you're now a packager.  I'll go and orphan the perl-Sys-Mmap package now so you can take the Fedora branches and request the EPEL branches you want.  (You can do that from https://admin.fedoraproject.org/pkgdb/package/rpms/perl-Sys-Mmap/).

I'm pretty much always in #fedora-devel on freenode (as "tibbs") and there are plenty of people who are there who can help you out if you have questions.  Or you can always email me.


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