The following Fedora EPEL 7 Security updates need testing:
Age URL
304 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087
dokuwiki-0-0.24.20140929c.el7
96 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-925e9374c9
python-pymongo-3.0.3-1.el7
66 https://bodhi.fedor
The following Fedora EPEL 6 Security updates need testing:
Age URL
200 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-6828
chicken-4.9.0.1-4.el6
182 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031
python-virtualenv-12.0.7-1.el6
176 https://bodhi.fedoraproject.o
The following Fedora EPEL 5 Security updates need testing:
Age URL
809 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2013-11893
libguestfs-1.20.12-1.el5
574 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-1626
puppet-2.7.26-1.el5
423 https://bodhi.fedoraproject.org/upda
> -Original Message-
> From: Nick Coghlan [mailto:ncogh...@gmail.com]
> Sent: Wednesday, January 06, 2016 05:42
> To: Fedora Python SIG
> Cc: EPEL Development List
> Subject: Re: [EPEL-devel] Which python3 versions to package for EPEL7?
>
> On 6 January 2016 at 13:48, Toshio Kuratomi wrot
On Thu, Jan 7, 2016 at 12:24 AM, Orion Poplawski
wrote:
> On 01/06/2016 10:51 AM, Kevin Fenzi wrote:
>
> > Also, now that 35 is out, do we want to switch epel7 to python35 before
> > we go building out things much more?
> >
> > kevin
>
> Actually, I think it would be nice to test out the dual nat
On 01/06/2016 10:51 AM, Kevin Fenzi wrote:
> On Wed, 6 Jan 2016 20:41:54 +1000
> Nick Coghlan wrote:
>
>> On 6 January 2016 at 13:48, Toshio Kuratomi
>> wrote:
>>> Despite the confusion, my feeling is that we want the newer
>>> versions. People who want to run python3 are willing to live more
>>
On Wed, 6 Jan 2016 20:41:54 +1000
Nick Coghlan wrote:
> On 6 January 2016 at 13:48, Toshio Kuratomi
> wrote:
> > Despite the confusion, my feeling is that we want the newer
> > versions. People who want to run python3 are willing to live more
> > on the bleeding edge. What I've observed is that
On Wed, 6 Jan 2016 02:27:31 -0500 (EST)
Ding Yi Chen wrote:
> When I am building evas-generic-loaders-1.16.0-1.el7.src.rpm,
> I see this:
> Error: No Package found for LibRaw-devel
>
> LibRaw-devel for epel7 is retired, but is available in
> @rhel-7-workstation-optional-beta-rpms What should I d
On 6 January 2016 at 13:48, Toshio Kuratomi wrote:
> Despite the confusion, my feeling is that we want the newer versions.
> People who want to run python3 are willing to live more on the bleeding
> edge. What I've observed is that they want newer versions of libraries as
> well. Building packag
Hello Peter,
>> I would like to upgrade to the latest stable Mono version, which is
>> 4.2 at the moment. That is in rawhide already, F23 has Mono 4.0.
>
> Is there a LTS release in the mono 4.x release?
Unfortunately no.
There is just an alpha, a beta and a stable channel:
http://developer.xamari
> we are discussing in this bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1220138 the work that
> would be required to upgrade Mono in Epel.
>
> I am aware that this is a major upgrade, and according to [1] it
> should be avoided.
> But Mono is that old in Epel7 already, so the discussion curre
Hello,
we are discussing in this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1220138 the work that
would be required to upgrade Mono in Epel.
I am aware that this is a major upgrade, and according to [1] it
should be avoided.
But Mono is that old in Epel7 already, so the discussion currently
Hi,
...
Depending on: pulseaudio (4), status change: 2015-12-08 (4 weeks ago)
qmmp (maintained by: kvolny)
I can rebuild qmmp without the PA plugin, it works fine with pure ALSA, but
before I'll do that, I'd like to be sure that no one is going to adopt PA
and it will be really drop
13 matches
Mail list logo
