On Mon, 3 Jun 2013 13:20:21 +
Finnur Örn Guðmundsson wrote:
> Hi all,
>
> Not sure if this should go here or to the epel-users list but here
> goes
>
> Just tried to install munin-node on a new RHEL6 machine and got this
> error:
>
> Error: Package: munin-node-2.0.14-1.el6.noarch (epel
On Wed, 3 Jul 2013 18:58:56 -0700
"T.C. Hollingsworth" wrote:
> Hi all! I filed a ticket [1] in rel-eng's trac about this because I'm
> fairly certain something weird happened here, but just in case I'm
> missing something...
>
> nodejs-npmlog-0.0.3-1.el6 [2] is supposed to have been pushed as
On Wed, 10 Jul 2013 16:14:44 +0200
Trond Hasle Amundsen wrote:
> Susi Lehtola writes:
>
> > my builds consistently fail on el5 ppc.
> >
> > DEBUG util.py:264: Error Downloading Packages:
> > DEBUG util.py:264:tzdata-2013c-1.el5.ppc: failed to retrieve
> > tzdata-2013c-1.el5.ppc.rpm from b
On Tue, 30 Jul 2013 08:44:42 -0700
"T.C. Hollingsworth" wrote:
> On Mon, Jul 29, 2013 at 8:22 PM, Chen, Wei D
> wrote:
> > Is it possible for us to open RHN channel within koji build server?
> > if true, how to? would you kindly give us some example?
>
> No. Again, Fedora EPEL packages can onl
On Tue, 6 Aug 2013 12:30:32 -0400 (EDT)
Sam Kottler wrote:
> Hi,
>
> We've had this conversation at least once before, but I figured I
> would bring it up again [1].
>
> You can see in Mike's original post that there a number of reasons we
> should bump to the 2.7 series in EPEL, but primarily
On Fri, 16 Aug 2013 09:29:28 -0600
Orion Poplawski wrote:
> Are there any requirements that the version of a package in say EPEL
> 5 needs to be less than the version in RHEL6? Since upgrades are not
> supported between EL versions, I was wondering if this was a
> requirement or not. Is this no
On Wed, 28 Aug 2013 13:05:22 +
"Guo, Dan (WorldQuant)" wrote:
> Greeting,
>
> I just found out this list and subscribe to it. my subscription is
> new.
Your post was stopped in moderation because you weren't subscribed with
the same address you were posting with. Make sure the one you subsc
On Mon, 16 Sep 2013 10:43:50 -0700
Dave Johansen wrote:
> http://developerblog.redhat.com/2013/09/12/rhscl1-ga/
> I know that the devtoolset requires an additional subscribe to get
> access, but is there a way to make use of it in the Koji build process
> so that those who are subscribed to the d
On Mon, 16 Sep 2013 20:32:41 -0700
Dave Johansen wrote:
> How can I get involved in that process? I would definitely like to
> help out with enabling the support for them in the EPEL.
Join the packaging list and see this post just today:
https://lists.fedoraproject.org/pipermail/packaging/2013-
Some questions for you:
- Is the source available for anyone to download/use?
I can't seem to see it off hand on ftp.redhat.com.
- How do you propose handing the difference in lifecycle? SCL is saying
3 years next to RHEL's 10. What happens at those points? Everyone
breaks and needs to r
On Sun, 22 Sep 2013 10:42:27 +0530
Kunal Pednekar wrote:
> Hi Team,
>
> I tried to install packages after downloading EPEL. But I am getting
> following error:
...snip...
> [root@ess19 ~]# yum install foo
> Loaded plugins: presto, refresh-packagekit, security, tmprepo
> Error: Cannot retrieve
On Mon, 23 Sep 2013 10:08:23 -0500
Troy Dawson wrote:
> perl-libintl provides perl(Locale::Recode)
>
> Why? I don't know. Doesn't seem to follow the normal perl naming
> convention.
>
> Anyway, it looks like this was put into EPEL5, but never EPEL6.
> http://koji.fedoraproject.org/koji/packa
On Mon, 2 Dec 2013 09:45:44 +0400
Peter Lemenkov wrote:
> Hello All!
>
> 2013/12/2 Dave Johansen :
> > I recently submitted ODB 2.2 to the EPEL for EL 5/6 and version 2.3
> > has been released (
> > http://codesynthesis.com/pipermail/odb-announcements/2013/37.html
> > ). The wiki seems to in
It's not at all too soon, and I was/am planning on writing up a more
detailed email on it very soon.
Look for that in the next few days...
kevin
signature.asc
Description: PGP signature
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
Greetings.
Several folks have been asking about epel7 and we should get the ball
rolling now that there is a public rhel7 beta.
I'd like to propose a similar plan to the one we used for epel6, which
the possible exception of branching method.
For epel6 we asked maintainers who didn't want to
On Thu, 12 Dec 2013 18:36:48 -0700
"T.C. Hollingsworth" wrote:
...snip...
>
> Yeah, opt-in sounds like a much better idea. :-)
Yeah, it does mean slower, but I think it's good to only have those
things in that are for sure maintained.
> > So, I was thinking this time perhaps we could:
> >
>
On Thu, 12 Dec 2013 18:52:38 -0700
"T.C. Hollingsworth" wrote:
> On Thu, Dec 12, 2013 at 6:01 PM, Christopher Meng
> wrote:
> > branch from EPEL6?
>
> He said F19. :-) That makes a lot more sense IMHO.
Right. New epel7 branches would get the content from the f19 branch to
start with. You can
FYI, the "Removed Package" stuff was due to it diffing against the last
epel-6 beta package set. ;)
This is fixed and shouldn't happen in tomorrow's compose.
kevin
signature.asc
Description: PGP signature
___
epel-devel mailing list
epel-devel@lists
On Mon, 16 Dec 2013 09:06:06 -0800
Jeff Sheltren wrote:
> On Sun, Dec 15, 2013 at 9:48 PM, Dennis Gilmore
> wrote:
>
> >
> > done https://fedoraproject.org/wiki/EPEL/epel7
> >
> >
> Thanks Dennis, for setting all this up! Where does this leave us
> now? Can people start submitting builds alre
On Wed, 25 Dec 2013 12:03:47 +0100
Karel Volný wrote:
>
> Hi,
>
> Dne pátek, 13. prosince 2013 17:42:24 CEST, Kevin Fenzi napsal(a):
> > On Thu, 12 Dec 2013 18:36:48 -0700
> > "T.C. Hollingsworth" wrote:
> ...
> >> Yeah, opt-in sounds like a muc
On Thu, 26 Dec 2013 16:53:19 -0800
Michael Stahnke wrote:
> What's the process opt-in at this point? I'm a bit unclear. I see that
> epel-release was built for EPEL7 (and that the git branch is epel7
> instead of el7).
There's no process yet because we don't have some things we still need
done y
On Thu, 2 Jan 2014 23:29:49 +0800
Christopher Meng wrote:
> Hi,
>
> I wonder if I need to add epel7 to the branch list or the system will
> do for me?
>
> I want to package for epel7 also.
When we are ready for branches we will announce and that will include
the process and what you need to do
On Fri, 3 Jan 2014 01:08:54 +0800
Christopher Meng wrote:
> On Jan 3, 2014 1:02 AM, "Kevin Fenzi"
> > When we are ready for branches we will announce and that will
> > include the process and what you need to do.
>
> Thanks, but what I've seen is that someone
On Wed, 15 Jan 2014 10:32:18 -0500
Stephen Gallagher wrote:
> Perhaps this would be a good time to reopen the conversation of
> minor-release policy changes?
Sure.
> RHEL releases approximately every six months with a minor release. It
> seems fair to allow major EPEL upgrades to occur in sync
On Fri, 17 Jan 2014 08:00:58 -0500
Stephen Gallagher wrote:
> My thoughts are these (in no particular order).
> * Treat this branch like Rawhide. All builds targeted at this are
> composed to a repo. Signing is nice, but not mandatory in my opinion.
It's pretty much impossible to sign rawhide s
On Thu, 20 Feb 2014 07:54:07 -0700
Dave Johansen wrote:
> I'm trying to do a build on koji and ran into an error during the mock
> buildroot setup
> ( http://koji.fedoraproject.org/koji/taskinfo?taskID=6488038 ).
>
> I posted previously on the Fedora devel mailing list but haven't
> figured it o
On Fri, 21 Feb 2014 08:28:24 -0700
Dave Johansen wrote:
>
> Doh! The original email in this chain was a copy and paste/stupid user
> error on my part. No, I no longer get that issue with the llvm build
> and like Kevin pointed out, just waiting worked.
>
> But I sent two emails this month with
On Sun, 23 Feb 2014 18:10:10 +0100
Dominik 'Rathann' Mierzejewski wrote:
> Hello everyone,
> are the EPEL7 branch requests on
> https://fedoraproject.org/wiki/EPEL/epel7/Requests still being
> processed or are we back to the standard branch requests in the
> original review bugs?
Yes they are.
On Thu, 06 Mar 2014 19:42:15 -0500
Jason Edgecombe wrote:
> Hi,
>
> I would like the i3, i3-doc, i3-ipc, i3lock, and i3status packages
> from EPEL for RHEL6 be ported to EPEL for RHEL7beta. I'm not a
> package maintainer. How do I request that the packages be ported?
File a bug(s) against them
On Fri, 14 Mar 2014 19:28:22 -0700
Dave Johansen wrote:
> I just tried building qt-creator for EPEL 7 beta, but it failed
> because the appdata-tools package doesn't seem to be available. Is
> that not part of EL/EPEL 7 beta? Should I just remove the use of it
> from the .spec? Or is there a bett
On Mon, 17 Mar 2014 15:52:05 +0100
Simone Caronni wrote:
> Hello,
>
> maybe I missed this, but I would like to know what's the status of
> EPEL 7 32 bit (i686) support.
It does not exist. ;)
There is an effort by some CentOS folks to build i686...
> I see that in Koji all libraries are x86_
On Tue, 18 Mar 2014 05:54:43 -0500
Jim Perrin wrote:
> In preparation for the launch of EL7 and due to community demand, the
> CentOS Project will be providing additional arch support not included
> in RHEL. Specifically we intend to continue producing for the i686
> architecture, as well as addi
On Tue, 18 Mar 2014 13:40:42 +0100
Simone Caronni wrote:
> as a contributor I would really like to have i686 as one of the main
> architectures. With the current situation, there's no chance to
> rebuild many of the packages that could benefit of RHEL 7 multilib
> support. RHEL 7 supports 32 bit
On Fri, 21 Mar 2014 16:25:50 +0400
Peter Lemenkov wrote:
> 2014-03-21 16:07 GMT+04:00 Matthew Miller :
>
> >> It doesn't exist, it's an idea that Robyn has floated
> >> semi-seriously as a way to provide a repo that moves faster than
> >> EPEL. Rather than try to jam fast-moving stuff in to EPEL
On Mon, 24 Mar 2014 17:15:35 +0100
Jochen Schmitt wrote:
> Hello,
>
> I would like, if anyoune have tried to get an "Free RHEL Entitlement
> for EPEL Developers" in the last few months and tell my anything
> about how long the processing time have taken.
>
> I have tried it in January of this y
On Sat, 29 Mar 2014 08:34:11 -0400
"Aaron W. Hsu" wrote:
> I submitted a package request a few days ago for libupnp in the EPEL 7
> Beta repository. I notice that other packages have made it into the
> repository, but the libupnp library has not.
>
> I presume there was a reason for the package
On Sat, 29 Mar 2014 21:06:08 -0400
"Aaron W. Hsu" wrote:
> On Sat, 2014-03-29 at 09:22 -0600, Kevin Fenzi wrote:
> > On Sat, 29 Mar 2014 08:34:11 -0400
> > "Aaron W. Hsu" wrote:
> >
> > > I submitted a package request a few days ago for lib
On Thu, 17 Apr 2014 22:49:04 -0600
Orion Poplawski wrote:
> So, we're just about ready to have python3-3.4 built in rawhide. This
> package builds fine in EPEL7 too. So, I'm proposing to build (and
> hopefully with help from others) maintain python3-3.4 for EPEL. Other
> options/considerations
On Thu, 17 Apr 2014 22:46:37 -0500
Greg Swift wrote:
> sorry that got sent prematurely. Here is the full version:
>
> hey all. So I was talking to Dominic Cleal this week at the Summit
> and he pointed out that python-augeas is getting pulled into RHEL 7
> proper. Its not in the beta, but it i
On Sun, 27 Apr 2014 09:31:01 +
EPEL Beta Report wrote:
> Compose started at Sun Apr 27 08:15:03 UTC 2014
FYI, ,composes are failing due to a conflict between two packages. :(
Will dig into it more tomorrow...
kevin
signature.asc
Description: PGP signature
__
On Sun, 27 Apr 2014 13:34:32 -0600
Kevin Fenzi wrote:
> On Sun, 27 Apr 2014 09:31:01 +
> EPEL Beta Report wrote:
>
> > Compose started at Sun Apr 27 08:15:03 UTC 2014
>
> FYI, ,composes are failing due to a conflict between two packages. :(
>
> Will dig in
On Tue, 29 Apr 2014 16:54:31 -0700
Toshio Kuratomi wrote:
...snip...
> What do people think? Is this something we can do within the
> policies of EPEL? Does it make sense to go forward with this? Is it
> better to go with one of the alternatives?
...snip...
I like the plan. I'm happy to help
On Thu, 1 May 2014 23:52:34 +0200
Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 30 April 2014 at 15:02, Jim Perrin wrote:
...snip...
> [snip - about kmail]
> >
> > I guess I have two specific questions for this.
> >
> > 1. Can epel track and provide the same source versions of packages
On Thu, 22 May 2014 09:43:54 -0600
Stephen John Smoogen wrote:
> It was pointed out in IRC that the list of packages at
> https://fedoraproject.org/wiki/EPEL/epel7/Requests was getting rather
> long. The problem currently is that we have moved to a package
> database and the existing scripts are
On Wed, 04 Jun 2014 10:08:59 +0200
Volker Fröhlich wrote:
> On 06/04/2014 09:29 AM, Ville Skyttä wrote:
> > The EL5 PPC koji builder seems to be unable to find at least some
> > packages at the moment:
> >
> > http://koji.fedoraproject.org/koji/getfile?taskID=6923025&name=mock_output.log&offset=
On Mon, 2 Jun 2014 16:26:55 +0200
Till Maas wrote:
> Hi,
>
> libntlm is not available for ppc in RHEL7 and it is a dependency for a
> package I would like to build for EPEL7. Therefore I intend to create
> a package according to
> https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packag
Greetings.
One thing I missed in the RHEL7 release was that there is a repository
now called 'rhel-extras'.
For RHEL6 this contains upgrade packages (for in place rhel6->rhel7
upgrades).
For RHEL7 this contains (for now) docker and a number of flask packages
that docker-registry needs.
The
Just a quick update:
* I am working to get the final rhel7 content lined up for building
against in koji, as soon as that goes live I'll drop a note here.
* When do we want to look at leaving beta status for epel7?
I'd suggest we should definitely give CentOS time to release, but
should we ha
On Mon, 16 Jun 2014 21:03:57 +0200
Simone Caronni wrote:
> Hello,
>
> On 16 June 2014 20:15, Kevin Fenzi wrote:
>
> > * When do we want to look at leaving beta status for epel7?
> > I'd suggest we should definitely give CentOS time to release, but
> &g
On Mon, 16 Jun 2014 21:12:57 +0200
Simone Caronni wrote:
>
> Another thing, there are packages that are spread into multiple
> upstream optional channels that make it impossible to include some
> packages in the distribution.
>
> One thread here:
>
> https://lists.fedoraproject.org/pipermail/e
On Tue, 17 Jun 2014 16:14:55 +0200
Simone Caronni wrote:
> Mock is using CentOS:
>
> $ pwd
> /var/cache/mock/epel-6-x86_64/yum_cache/updates/packages
> $ ls -al *centos*
> -rw-rw-r--. 1 root mock 20960 May 20 15:33
> centos-release-6-5.el6.centos.11.2.x86_64.rpm
> -rw-rw-r--. 1 root mock 962780
ok, not much discussion here, but it seems like everyone is ok with
just saying rhel-extras is something we don't conflict with.
Thanks,
kevin
signature.asc
Description: PGP signature
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
ht
We've switched over to using the final rhel7 content finally.
Sorry for the delay.
As you can see from the epel7 build tag in koji:
http://koji.fedoraproject.org/koji/taginfo?tagID=259
we have the following rhel7 channels that we are building against and
will not conflict with:
rhel7-server
On Wed, 25 Jun 2014 08:23:24 -0700
Jeff Sheltren wrote:
> Awesome, thanks!
>
> Is there a plan/schedule for getting epel-7 builds into the normal
> git/koji/bodhi workflow? Is that waiting on a CentOS release, or are
> there other issues?
Well, at least centos release... but additionally:
*
On Wed, 25 Jun 2014 09:41:32 -0600
Stephen John Smoogen wrote:
> On 25 June 2014 09:28, Kevin Fenzi wrote:
>
> > On Wed, 25 Jun 2014 08:23:24 -0700
> > Jeff Sheltren wrote:
> >
> > > Awesome, thanks!
> > >
> > > Is there a plan/schedule for g
On Fri, 27 Jun 2014 15:01:26 -0500
Jim Perrin wrote:
> During some of the testing for centos7 (and in the process cleaning up
> some things for c6 as well), we noticed that there are a number of
> packages that are excluded from epel when using the priorities plugin
> with yum.
>
> While none of
With the release of CentOS7 today and based on no one chiming in with
other things we need to wait for, I guess we should look at leaving
beta. :)
Things we need to do:
* Untag all packages that have broken deps and notify maintainers.
* Check for overlapping packages and untag any needed.
On Fri, 11 Jul 2014 21:51:43 +0300
Devrim Gündüz wrote:
>
> Hi,
>
> Recently, I asked for epel7 branch of libgeotiff twice -- That is the
> final dependency towards pushing gdal to EPEL 7, so I can push
> PostGIS.
>
> However, even though it seems that the requests have been processed, I
> can
The set of Xfce packages is Not yet finished for epel7.
It's a work in progress.
nonamed...@fedoraproject.org is heading up the effort.
So, yes, it's expected that things are not fully working yet, it's
still being worked on.
kevin
signature.asc
Description: PGP signature
On Tue, 15 Jul 2014 21:24:20 -0500
nonamedotc wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 07/15/2014 10:02 AM, Martin Sourada wrote:
> >>
> > If I recall correctly (it's been a while since I last touched this
> > package), the -gnome and -compat packages are used to provid
On Sat, 12 Jul 2014 00:31:39 -0500
Michael Cronenworth wrote:
> Task: http://koji.fedoraproject.org/koji/taskinfo?taskID=7131137
>
> Result: FAILED: BuildError: Unknown origin for
> fedpkg-minimal-0.5.1.0-2.el7.noarch:
> file:///var/tmp/koji/tasks/256/7130256/repo_400839_premerge/
>
> I thoug
Greetings.
Just a quick status update: we haven't left beta status yet, but we do
hope to before too long. Mostly it's a matter of releng folks getting
time to do so. Next week is not looking too likely, but the week after
is possible. :)
Also, we have a number of packages that are in epel7 rig
On Mon, 21 Jul 2014 07:57:47 +1000
Dan Callaghan wrote:
> Excerpts from Kevin Fenzi's message of 2014-07-20 03:08:03 +1000:
> > TurboGears-1.1.3-8.el7.src.rpm
>
> I have an open ticket to unblock the missing deps for this...
> hopefully rel-eng will have a chance to take care of that sometime
>
On Mon, 21 Jul 2014 10:51:04 +0800
Christopher Meng wrote:
> yumex has wrong dep python-pexpect, it's pexpect in RHEL for a long
> time, although this package in RHEL7 has the same version of the one
> in RHEL6.
Yeah, also mentioned in:
https://bugzilla.redhat.com/show_bug.cgi?id=1117544
kevin
On Sun, 20 Jul 2014 21:06:47 -0700
Kyle Lanclos wrote:
> Christopher Meng wrote:
> > I guess you even don't know how to use Bugzilla.
>
> Quite right. It's something I encounter once or twice a year, if that.
>
> > Standard procedure:
>
> I followed the procedure outlined in the FAQ:
>
>
On Thu, 07 Aug 2014 15:39:04 +0200
Andreatta Sébastien wrote:
> Hi,
>
> Could you please tell us when the testing-epel7 will be available ?
EPEL7 has been available in 'beta' mode since RHEL7 beta came out.
https://fedoraproject.org/wiki/EPEL/epel7beta-faq
kevin
signature.asc
Description:
On Sat, 9 Aug 2014 11:54:58 -0700
Mark Sieklucki wrote:
> Is there any update on when EPEL 7 is going to leave beta?
>
> Last post I found about this is over a month old and basically says
> "we should plan on leaving beta" but doesn't give any further details:
> https://lists.fedoraproject.org/
On Tue, 12 Aug 2014 21:05:07 +0200
Stephen John Smoogen wrote:
> At FLOCK this year, I did a short workshop on what was labeled
> EPEL.Next. At that we went over a bit of what EPEL has done in the
> past, what its current challenges are, and what could be its future.
> Toshio Kuratomi was great i
On Thu, 14 Aug 2014 17:51:04 -0600
Stephen John Smoogen wrote:
> I am proposing that the EPEL community hold a meeting in #epel on
> Friday August 22, 2014 16:00:00 UTC to go over various community
> items:
Sure. I will be there. :)
Thanks for trying to organize things again.
> Suggested top
On Sun, 17 Aug 2014 18:52:53 +0200
Till Maas wrote:
> On Thu, Aug 14, 2014 at 05:51:04PM -0600, Stephen John Smoogen wrote:
> > I am proposing that the EPEL community hold a meeting in #epel on
> > Friday August 22, 2014 16:00:00 UTC to go over various community
> > items:
> >
> > Suggested topi
Here's a list of the packages we untagged while moving out of beta.
Please make sure the deps are all satisfied on these before pushing
them into epel7.
Thanks,
kevin
--
php-phpseclib-net-sftp-0.3.5-2.el7.src.rpm
caja-extensions-1.8.0-1.el7.src.rpm
nodejs-express-3.5.2-1.el7.src.rpm
nodejs-j
Greetings.
Today, EPEL (Extra Packages for Enterprise Linux) is happy to announce
that epel-7 is leaving it's Beta phase and is entering release.
epel-7 contains over 3100 high quality source packages, building over
5600 rpms.
Please see
https://fedoraproject.org/wiki/EPEL
For more information
On Fri, 29 Aug 2014 03:45:12 -0400 (EDT)
Jens Petersen wrote:
> Hi,
>
> I read the log from last weeks EPEL meeting [1].
> It is great to see discuss happening on (codename:) EPIC. :-)
>
> At Flock at the EPEL.next session there was mention of using
> branches/tags per minor EL version for EPIC
On Fri, 29 Aug 2014 16:08:34 -0600
Stephen John Smoogen wrote:
> So in todays (2014-08-29) meeting, we wanted to move the various
> policy discussions to email so that people could take their time to
> reply and also to allow for people who could not attend time to
> respond.
Right.
> Going fr
On Thu, 4 Sep 2014 18:20:19 -0600
Stephen John Smoogen wrote:
> So this is my general proposal for per point release.
>
>
> Problem trying to be solved:
>
> EPEL's original goal around a 5-7 year product has run into issues
> where various packages end up having shorter lifetimes than can be
>
On Tue, 09 Sep 2014 19:07:57 +0100
Karanbir Singh wrote:
> On 09/09/2014 04:50 PM, Jim Perrin wrote:
>
>
> > Alternatively, is cloud-init an actual shipped RH package that
> > should be excluded/blacklisted from epel?
>
> its certainly used in the RHEL image
Odd. I am not seeing it in any of
On Thu, 11 Sep 2014 09:27:32 +0100
Karanbir Singh wrote:
> that would work. There is the whole fundamental issue to then work
> through as to how far the epel branch's can diverge from the fedora
> codebase ? Secondly, could we find a mechanism that takes this model
> and applies it across the bo
On Tue, 16 Sep 2014 20:09:05 -0600
Orion Poplawski wrote:
> This has always been a funny one, and I've brought it up in the past,
> in the x86_64 repo:
>
> package: grib_api-devel-1.12.3-1.el6.i686 from epelx
>unresolved deps:
> gcc-gfortran(x86-32)
>
> Apparently there is now 32-bit
On Fri, 3 Oct 2014 09:46:48 +0200
Gianluca Sforna wrote:
> Hi all,
> since EPEL 5 ships an ancient version of mantis, I'd like to align it
> to the 1.2 series used in Fedora and make it easier to keep up with
> the various security issue fixed upstream.
>
> Since it is not really a drop in repla
On Wed, 8 Oct 2014 22:30:32 -0700
Brandon Vincent wrote:
> All,
>
> Over the past month, I have tried contacting Keiran Smith (affix) in
> regards to nagios with no success [1].
>
> Is anyone aware to his present status in regards to the Fedora Project
> or possibly have an alternative method t
On Sat, 11 Oct 2014 15:41:32 -0500
Mukundan Ragavan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
> Hi All,
>
> I would like some clarification from folks here regarding updating
> gparted on EPEL-5 and EPEL-6.
>
> The version of gparted shipped in EPEl-5 is 0.4.8 and EPEL-6
On Tue, 28 Oct 2014 09:58:14 -0600
Stephen John Smoogen wrote:
> I have had a conflict come up for the Friday meeting at 1600 UTC.
> Would it be possible to move the meeting to 1700 or 1800 UTC?
Either of those times would be fine with me.
kevin
signature.asc
Description: PGP signature
_
On Wed, 12 Nov 2014 10:02:37 +0100
Przemysław Hejman wrote:
> Hi guys,
>
> I’ve recently tried to deploy some apps with saltstack on CentOS 6.4.
> I’m using saltstack bootstrap script, which installs EPEL. The
> problem is, that yum fails with update because it cannot reach the
> HTTPS reposito
On Thu, 13 Nov 2014 01:37:13 +0200
Anssi Johansson wrote:
> I believe the problem is not really SSLv3, but that the Fedora
> Project uses 4096 bit keys, which the old nss can't handle. I was
> unable to locate any other web server that used 4096 bit keys when I
> was diagnosing the issue back the
On Tue, 11 Nov 2014 14:00:18 -0600
Rex Dieter wrote:
> OK (attached).
The macros.epel file is missing?
kevin
pgpwyHWUBWXXS.pgp
Description: OpenPGP digital signature
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedora
On Wed, 17 Dec 2014 10:27:23 +0100
Sandro Bonazzola wrote:
> Hi,
> a few weeks ago I contacted jwhite, packager of spice-html5 package
> for Fedora and EPEL 6 asking a port to EPEL 7. He built the package
> http://kojipkgs.fedoraproject.org/packages/spice-html5/0.1.5/1.el7/
> but the build is not
On Wed, 17 Dec 2014 08:54:01 -0700
Orion Poplawski wrote:
> On 12/17/2014 08:17 AM, Sandro Bonazzola wrote:
> > Can anybody grant him permission?
>
> Well, Eduardo Javier Echeverria Alvarado (echevemaster) would be
> correct person to do it. Not sure if anyone else can.
>
> Looks like the bran
On Fri, 6 Feb 2015 17:18:02 +0100
Dominik 'Rathann' Mierzejewski wrote:
> Small correction:
>
> On Friday, 06 February 2015 at 16:32, Dominik 'Rathann' Mierzejewski
> wrote:
> > Dear EPEL developers,
> > I'm trying to package some scientific software written in python
> > which depends on python
On Mon, 2 Mar 2015 06:59:29 -0500 (EST)
Bohuslav Kabrda wrote:
> - Original Message -
> > Excerpts from Orion Poplawski's message of 2015-02-28 04:36 +10:00:
> > > all python34 packages are retired
> >
> > Except there is no way to retire an individual subpackage, is there?
>
On Fri, 27 Feb 2015 19:15:46 -0700
Orion Poplawski wrote:
> Could we get a Distribution component for Fedora EPEL in Bugzilla?
> Might be useful for things like
> https://bugzilla.redhat.com/show_bug.cgi?id=1197264
Well, we could make such a thing, but not sure it's really suited to
these kind
On Tue, 3 Mar 2015 07:46:00 -0500 (EST)
Bohuslav Kabrda wrote:
> > ^ Is this step part of a coordinated mass-rebuild, or is this just a
> > period of time after we make the announcement: "Hey Packagers: be
> > sure to rebuild for python35"?
>
> That's a good question. I guess we should standardi
On Tue, 3 Mar 2015 08:31:20 -0500 (EST)
Bohuslav Kabrda wrote:
> Today, I've made some changes to the proposal to accomodate comments
> from the previous meeting and from discussion on this list. The diff
> is here:
>
> https://fedoraproject.org/w/index.php?title=User%3ABkabrda%2FEPEL7_Python3&d
On Mon, 9 Mar 2015 11:49:56 +
Peter Robinson wrote:
...snip...
> > 1) Who is championing an architecture?
>
> Primarily IBM, but this will widen with the OpenPOWER foundation and
> it's members widening and HW from that initiative starting to become
> available. In the case of aarch64, if t
On Mon, 16 Mar 2015 14:05:28 +
"Samia, Michel" wrote:
> Hello Ralph Bean,
>
> It looks like your commit [1] broke lots of packages in epel. It
> caused that python-urllib3 was removed from all EPEL6 mirrors.
> Unfortunately, lots of packages in EPEL, for example those mentioned
> in [2], req
On Tue, 17 Mar 2015 21:36:41 -0700
Dave Johansen wrote:
> What is the current update policy for EPEL? The stated one seems to be
> along the lines of "no major changes" (
> http://fedoraproject.org/wiki/Updates_Policy ) but it seems more like
> "whatever the packager is willing to maintain" is th
On Wed, 18 Mar 2015 08:00:35 -0700
Dave Johansen wrote:
> Is that really true? The Qt 5 package in EPEL 6 has been updated
> several times and I don't recall ever seeing an
> email/announcement/etc.
Were the upgrades incompatible? You have to manually intervene?
kevin
pgp8riuWG8Exs.pgp
Descri
On Sat, 21 Mar 2015 03:50:40 -0600
Eric Smith wrote:
> Bug #1203649 was reported against dragonegg, which is tied to the
> specific version of gcc it is built against, because it uses the gcc
> plugin interface. EL7.1 has a newer gcc, so dragonegg has to be
> rebuilt. I did a new build (fedpkg bu
On Wed, 01 Apr 2015 16:38:45 +0100
Paul Howarth wrote:
> On 01/04/15 16:26, Ken Dreyer wrote:
> > On my PPC64 build of Ceph today [1], I'm seeing this really odd
> > error regarding libxml2-devel:
> >
> > from root.log:
> > ...
> > DEBUG util.py:388: Error: Package:
> > libxml2-devel-2.9.1-5.el7
On Wed, 1 Apr 2015 15:19:35 -0600
Ken Dreyer wrote:
> I attempted two new builds, and each failed on ppc64 with the same
> libxml2-devel error :(
>
> http://koji.fedoraproject.org/koji/taskinfo?taskID=9395052 is the
> latest one.
>
> What can I try next?
ok. This is a deeper problem. ;(
I am
On Wed, 1 Apr 2015 17:08:50 -0600
Kevin Fenzi wrote:
> On Wed, 1 Apr 2015 15:19:35 -0600
> Ken Dreyer wrote:
>
> > I attempted two new builds, and each failed on ppc64 with the same
> > libxml2-devel error :(
> >
> > http://koji.fedoraproject.org/koji/taskinfo
1 - 100 of 375 matches
Mail list logo
