Troy Dawson wrote:
> * digikam - Don't know why it won't build, help would be appreciated
> https://koji.fedoraproject.org/koji/taskinfo?taskID=44213799
Looks like it wants opencv >= 3.3
-- Rex
___
epel-devel mailing list --
The core issue is libglvnd, as far as I can tell, issue being tracked at:
https://pagure.io/releng/issue/7898
Initial problem was that epel7 included an older libglvnd, so I'd hoped if
we got that removed and blocked, the problem would be resolved.
Unfortunately, problems persist. koji/mock
Manuel Wolfshant wrote:
>> Here's a reference to one thread on the topic:
>> https://lists.fedoraproject.org/pipermail/epel-devel/2014-May/009527.html
>>
>> and a similar post about requirements:
>> http://www.karan.org/blog/2013/12/15/where-is-the-i686-in-rhel-7/
>
> Those posts are deprecated
Ken Taylor wrote:
> On 05/18/2018 04:47 PM, Rex Dieter wrote:
>> Ken Taylor wrote:
>>
>>> It would be nice if both architectures could be made available in the
>>> epel wine package
>> I'll say it one more (last) time: epel(*) cannot build i686 packages
&g
Ken Taylor wrote:
> It would be nice if both architectures could be made available in the
> epel wine package
I'll say it one more (last) time: epel(*) cannot build i686 packages
(*) In it's current setup. There's been previous talk about using centos7
i686 for this purpose... but so far
Ricardo J. Barberis wrote:
> El Viernes 18/05/2018 a las 00:33, Rex Dieter escribió:
>> Ken Taylor wrote:
>> > On 05/16/2018 11:00 PM, Rex Dieter wrote:
>> >> Ken Taylor wrote:
>> >>> I installed the wine 3 package from epel-testing this morning o
Ken Taylor wrote:
> On 05/16/2018 11:00 PM, Rex Dieter wrote:
>> Ken Taylor wrote:
>>
>>> I installed the wine 3 package from epel-testing this morning on a
>>> newly installed CentOS 7.5 machine. The installation seemed to go fine.
>>> If I may ask
Ken Taylor wrote:
> I installed the wine 3 package from epel-testing this morning on a
> newly installed CentOS 7.5 machine. The installation seemed to go fine.
> If I may ask two questions...
>
> Does this version of wine support 32 bit Windows programs on CentOS 7.5?
No. rhel7 (and epel7 by
Sérgio Basto wrote:
> On Tue, 2018-03-27 at 13:46 -0500, Rex Dieter wrote:
>> Sérgio Basto wrote:
>>
>> > On Tue, 2018-03-27 at 11:53 -0500, Rex Dieter wrote:
>> > > Sérgio Basto wrote:
>> > >
>> > > > On Mon, 2018-03-26
Sérgio Basto wrote:
> On Tue, 2018-03-27 at 11:53 -0500, Rex Dieter wrote:
>> Sérgio Basto wrote:
>>
>> > On Mon, 2018-03-26 at 15:33 -0500, Rex Dieter wrote:
>> > > Sérgio Basto wrote:
>> > >
>> > > > On Tue, 2018-03-06 at 16:15 -
Sérgio Basto wrote:
> On Mon, 2018-03-26 at 15:33 -0500, Rex Dieter wrote:
>> Sérgio Basto wrote:
>>
>> > On Tue, 2018-03-06 at 16:15 -0600, Rex Dieter wrote:
>> > > I'd be ok with an epel7-only python3-sip
>> > >
>> > >
Stephen John Smoogen wrote:
> On 10 August 2017 at 11:22, Rex Dieter
> <rdie...@math.unl.edu> wrote:
>
>> Stephen John Smoogen wrote:
>>
>> > RHEL-7.4 was released today and so the build roots for EPEL packages
>> > will be updated as soo
Stephen John Smoogen wrote:
> RHEL-7.4 was released today and so the build roots for EPEL packages will
> be updated as soon as the automatic reposync is done.
So, this was posted awhile ago (Aug 1), and as far as I can tell, buildroots
are still not updated.
Can anyone provide an update or
enmarantis...@gmail.com wrote:
> Qt has recently decided to make 5.9 their new LTS release, but epel 6 is
> still on version 5.6, is it the final version or will 5.9 be packaged
> sometime in the future?
Definite maybe, but no immediate plans. What rhel7 does will likely affect
the decision on
I think I already know answer is no, but is it possible to use devtoolset-3-
gcc in epel-6 builds now or in the future?
I'm asking in the context of being able to support Qt-5.6 (tls) for epel-6
which will need this.
See also:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/
--
Dave Johansen wrote:
On Wed, Mar 18, 2015 at 10:39 AM, Kevin Fenzi
ke...@scrye.com wrote:
On Wed, 18 Mar 2015 08:00:35 -0700
Dave Johansen davejohan...@gmail.com
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
Jeff Sheltren wrote:
On Fri, Oct 31, 2014 at 5:42 AM, Rex Dieter
rdie...@math.unl.edu wrote:
Rex Dieter wrote:
+%epel %{?rhel}%{!?:rhel:7}
typo alert ^^ (in the second part), but hopefully you get the idea.
Or, if you'd rather not depend on %rhel macro, and just hard-code to 7
Rex Dieter wrote:
I'd like to be able to conditionalize some package features depending on
if
epel repo is enabled or not. One way to accomplish that goal is if epel-
release defined some macro, say, something like %{epel}, similar to
%{feodra} or %{rhel}
(I don't care what the macro
Rex Dieter wrote:
Rex Dieter wrote on Oct 16:
I'd like to be able to conditionalize some package features depending on
if
epel repo is enabled or not. One way to accomplish that goal is if epel-
release defined some macro, say, something like %{epel}, similar to
%{feodra} or %{rhel
Chuck Anderson wrote:
On Mon, Oct 20, 2014 at 08:56:35PM -0500, Rex Dieter wrote:
Jeff Sheltren wrote:
On Mon, Oct 20, 2014 at 3:11 PM, Rex Dieter
rdie...@math.unl.edu wrote:
ping, any comment or objection?
I'll work on a patch for epel-release to implement a %{epel} macro
Rex Dieter wrote on Oct 16:
I'd like to be able to conditionalize some package features depending on
if
epel repo is enabled or not. One way to accomplish that goal is if epel-
release defined some macro, say, something like %{epel}, similar to
%{feodra} or %{rhel}
(I don't care what
Jeff Sheltren wrote:
On Mon, Oct 20, 2014 at 3:11 PM, Rex Dieter
rdie...@math.unl.edu wrote:
ping, any comment or objection?
I'll work on a patch for epel-release to implement a %{epel} macro, in
case anyone was waiting for implementation details.
Seems like it can't hurt much to have
Stephen John Smoogen wrote:
2:koffice-kivio-1.6.3-25.20090306svn.el5.i386
This one is arguably a false-positive, rhel5 x86_64 fails to multilib
libpython properly (ie, there is no python-libs.i686 in x86_64 repo)
package: 2:koffice-kivio-1.6.3-25.20090306svn.el5.i386 from epelx
unresolved
Robert Moser II wrote:
Currently qt5-qtbase-* packages are at version 5.3.1, while the rest of
the
qt5 packages are at 5.2.1. Are the remaining packages going to be updated
to 5.3.1?
Looks like my work on doing 5.3.1 builds on epel7 got interrupted, and
forgot to finish. I'll do so asap.
24 matches
Mail list logo
