On 8/10/24 16:41, Carl George wrote:
> What has not been completed yet:
>
> - publish the epel/10 repo
Do we have an ETA for an EPEL10 compose (if only in koji)? Thanks!
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of IT Systems
ut 70 packages during the allotted time of the hackfest,
and as I write this we just passed 100 builds. Things seem to be
working well. Please let me know if you notice any issues, aside from
known items on the "not completed yet" list above.
Happy packaging!
On Sat, Aug 10, 2024 at 12
d as I write this we just passed 100 builds. Things seem to be
working well. Please let me know if you notice any issues, aside from
known items on the "not completed yet" list above.
Happy packaging!
On Sat, Aug 10, 2024 at 12:29 AM Orion Poplawski wrote:
On 7/4/24 01:45, Carl George
that.
**Please do not start creating EPEL 10 builds until we announce that
we are ready for packagers to start building.**
I'm seeing some builds and bugzilla requests for branching/builds. What
is the current status?
--
Orion Poplawski
he/him/his - surely the least important thing about me
EPEL8 now has a stripped down version of pyproject-rpm-macros. Notably,
it does NOT support/provide %pyproject_generate_buildrequires, but it
does support the basic build/install related macros.
Also note that this only supports building with python 3.8+.
--
Orion Poplawski
he/him/his
seems like we really should be pulling in python2 from the module?
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane
cally
just waiting on one issue to get resolved at the moment:
https://github.com/Cisco-Talos/clamav/issues/842
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
n ansible, and optionally higher while giving due diligence
to avoiding breaking changes.
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane
tiple release tracks
(no idea).
I don't really have a particular agenda here, just trying to solicit
people's thoughts. Personally I like minimal installs so I have been
only using ansible-core + collections on the systems I maintain and
would like to continue to see them be usable to
s like webengine isn't in there, or I'm missing what's
needed to build it. I also don't need it for my purposes.
[1] - https://copr.fedorainfracloud.org/coprs/orion/python-qt5-epel/
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Mana
s like webengine isn't in there, or I'm missing what's
needed to build it. I also don't need it for my purposes.
[1] - https://copr.fedorainfracloud.org/coprs/orion/python-qt5-epel/
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Mana
anto do it "the right way", not a kludge?
For producing versions for other python 3.X versions, there is this:
https://fedoraproject.org/wiki/EPEL/Python3X
and you can check out the various python3*-foo-epel packages.
I don't know of a 3.7, but there is 3.8 and 3.9.
HTH,
Is is worth packaging PHP stuff in EPEL8+?
It seems very modular in RHEL and Remi's repos, but EPEL isn't doing modules.
If it is worthwhile, is anyone interested in helping out? I was hoping to get
mediawiki 1.35 into EPEL8.
Orion
--
Orion Poplawski
IT Syste
On 5/24/22 11:53, Maxwell G via epel-devel wrote:
On Monday, May 23, 2022 11:18:38 PM CDT Orion Poplawski wrote:
I've been coming to the thinking that naming the SRPMS
python3X-%{srcname}-epel is a better choice. This makes modifying
original Fedora specs simpler.
I think that makes
st give up and start
using pip and virtual envs.
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
B
doraproject.org/rpms/pyproject-rpm-macros
I've been playing around with a hacked version of pyproject-rpm-macros
which at least allows some basic functionality in EPEL8. Comments welcome.
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/284
--
Orion Poplawski
he/hi
is the build no longer exists.
I would have thought it was a good idea to update all packages to the
latest 2.9? How do I request it?
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&component=vnstat&version=epel7
--
Orion Poplawski
he/him/his - surely the least impo
Is there a timeline for supporting building modules for EPEL9? At the
moment I get:
Could not execute module_build: The build failed with:
None of the base module (platform or bootstrap) streams in the
buildrequires section could be found
--
Orion Poplawski
he/him/his - surely the least
thing simpler as nothing has to be a module or
special in any way.
--
Orion Poplawski
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https:
On 2/13/20 02:21, Tomas Orsava wrote:
> On 2/13/20 5:18 AM, Orion Poplawski wrote:
>> On 1/30/20 8:39 AM, Miro Hrončok wrote:
>>> On 30. 01. 20 16:32, Orion Poplawski wrote:
>>>> Folks -
>>>>
>>>> Looks like RHEL 8.2 will have python 3.8 in
the
moment, though still somewhat curious if I could get access.
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@n
system and pointed me to the LinuxONE community cloud where I launched
the above instance.
Thanks,
Orion
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mit
ality.
Agreed.
Linters do make sense in upstream CI. But not in Fedora.
Not inside Fedora *packages*, but
if these tools are not available to those using RHEL, Fedora or EPEL
is that a suitable platform for CI or for developers ?
No, but that's why it will be provided in EPEL :)
--
Orion
umber-devel 0
wpebackend-fdo-devel 1
xkbcomp-devel 0
xorg-x11-drv-evdev-devel 0
That's a lot. Now, many of these are pretty obscure and do not have any
users - but I'm also seeing a number that are going to hit me and the
scitech sig:
blis-devel 2
flexiblas-devel 33
gsl-devel 51
suitespa
On 1/14/22 05:02, Josh Boyer wrote:
On Fri, Jan 14, 2022 at 5:31 AM Miro Hrončok wrote:
On 14. 01. 22 5:11, Orion Poplawski wrote:
While working on EPEL9, it seems that even more packages are missing from RHEL9
than were in RHEL8. The latest I found was cppunit, which appears to be
On 1/14/22 19:45, epel-devel@lists.fedoraproject.org wrote:
On 1/14/22 03:29, Miro Hrončok wrote:
On 14. 01. 22 5:11, Orion Poplawski wrote:
While working on EPEL9, it seems that even more packages are missing
from RHEL9 than were in RHEL8. The latest I found was cppunit, which
appears to be
h great success, and
the consequence of that is we're able to get content into EPEL faster
than ever before. We're even going to be ready for the RHEL 9.0 GA,
which is something we've never had before.
I seem to have missed how to do this, could you point me to the right
process?
On 1/14/22 03:29, Miro Hrončok wrote:
On 14. 01. 22 5:11, Orion Poplawski wrote:
While working on EPEL9, it seems that even more packages are missing
from RHEL9 than were in RHEL8. The latest I found was cppunit, which
appears to be completely missing from the CS9 repos despite having
been
On 1/14/22 03:29, Miro Hrončok wrote:
On 14. 01. 22 5:11, Orion Poplawski wrote:
While working on EPEL9, it seems that even more packages are missing
from RHEL9 than were in RHEL8. The latest I found was cppunit, which
appears to be completely missing from the CS9 repos despite having
been
r EPEL9.
Packaging for EPEL9 is starting to feel more and more like cleaning the
Augean stables with RedHat piling up more manure.
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office
=80607754
Thanks.
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https
%python3_version, and in RHEL8 "python3dist".
But %python3_version requires python to evaluate.
Presumably we're using %python3_version to allow for multiple python
versions, but I think we've given up on that in single spec files.
Thoughts?
--
Orion Poplawski
he/him/hi
On 9/23/21 9:00 AM, Miro Hrončok wrote:
On 23. 09. 21 5:41, Orion Poplawski wrote:
-Requires: %{name}%{?_isa} = %{version}-%{release}
+Requires: utf8proc%{?_isa} >= %{version}-%{release}
I'd assume that anybody (even you) might need to rebuild this package in
EPEL at any time for
ame libpinyin
%global _debugsource_template %{nil}
But, that's just my preferences. I think yours should be fine.
Thanks, good ideas.
I'm thinking we might want to break this out from a question in the FAQ
to it's own page.
+1
Troy
--
Orion Poplawski
he/him/his - surely the least
.md README.md
-%{_libdir}/libutf8proc.so.*
-
-%files devel
+%files -n utf8proc-devel
%{_includedir}/utf8proc.h
%{_libdir}/libutf8proc.so
%changelog
+* Wed Sep 22 2021 Orion Poplawski - 2.1.1-5
+- EPEL -devel only package
+
* Mon Aug 05 2019 Lubos Uhliarik - 2.1.1-5
- Resolves: #1696354 - E
nch but then retire it just to create a bugzilla component? Or
something else?
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane
provides pulseaudio-daemon needed by
xfce4-pulseaudio-plugin-0.4.3-5.el8.x86_64
Thanks for working on Xfce for EPEL, much appreciated.
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office
ity-fedora"
This isn't a great look. I've submitted a pull request for the epel8
comps here:
https://pagure.io/fedora-comps/pull-request/608
to remove the missing components. Perhaps we want to make a push to add
some of these missing items first? I don't use
On 12/13/20 10:37 AM, Orion Poplawski wrote:
On 12/11/20 5:04 PM, Miro Hrončok wrote:
On 12/12/20 12:12 AM, Troy Dawson wrote:
We discussed this in the EPEL Steering Committee this week, and your
way has alot less "mess with the server and modules" work.
It would probably get us up
type of scripts, patches, and other things are needed.
Let me know if you have a devel package in mind and I can give it a try.
Can we just jump in and try this out? I'd like to get qpdf-devel
available. If so, I guess I would do:
fedpkg request-repo --exception qpdf-devel
right?
the proper python
* How do we want to handle the %py3_dist macro? Create a new
%py38_dist? Modify %py3_dist to use another macro rather than hard
coding "python3dist("?
Comments?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office
On 12/9/20 9:27 AM, Orion Poplawski wrote:
After updating to CentOS 8.3, my plasma (KDE) desktop is not starting. It
seems like X is not starting. Is anyone else seeing this and knows what's
happening? I haven't had a chance to dig much deeper myself yet...
Orion
This was likely
After updating to CentOS 8.3, my plasma (KDE) desktop is not starting. It
seems like X is not starting. Is anyone else seeing this and knows what's
happening? I haven't had a chance to dig much deeper myself yet...
Orion
--
Orion Poplawski
Manager of NWRA Technical Systems
e for
opening a bugzilla to request a package in EPEL when the component
(specifically, rcs) isn't listed because prior to RHEL8 it was in core
RHEL?
Then file it in the Fedora product.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office
On 7/7/20 12:09 PM, Neal Gompa wrote:
> On Tue, Jul 7, 2020 at 1:57 PM Orion Poplawski wrote:
>>
>> On 6/15/20 1:47 PM, Ben Cotton wrote:
>>> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
>>>
>>> == Upgrade/compatibility imp
/metalink?repo=playground-epel8 [2]-
Done arch=x86_64 [3]+ Done infra=stock
I don't know what to do to fix this. Can someone please explain what
the problem is on a high level and then what to do about it so that I
can learn from this?
What's the output of:
curl --trace-ascii -
&#
Anyone interested in maintaining some Gnome 2 libraries (at least
libgnomeui and deps) in EPEL8? I might if no one else is as someone at
work needs it, but I'm hoping that someone with more Gnome experience
would be willing.
Thanks.
--
Orion Poplawski
Manager of NWRA Technical Sy
that I
don't believe mock has.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
smime.p7s
Descript
ne.
Maybe there's some kind of process for getting stuff into CentOS Stream? So far the
interaction with upstream seems to be limited to "create an issue on Bugzilla".
That would be my suggestion:
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=cmake
--
Or
On 5/6/20 4:31 AM, Miro Hrončok wrote:
On 06. 05. 20 3:39, Orion Poplawski wrote:
This is related to my breaking of various packages by dropping
python34-six. Should we:
- re-add python34-six
For now, yes please. This will need a big announcement and coordination,
in the meantime, users
python34-slacker-0:0.12.0-4.el7.noarch
python34-urllib3-0:1.25.6-1.el7.noarch
python36-collada-0:0.4-16.el7.noarch
slack-cleaner-0:0.5.0-2.el7.noarch
Upstream python 3.4 is EOL.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415
On 5/1/20 8:39 AM, Kevin Fenzi wrote:
On Thu, Apr 30, 2020 at 08:39:48PM -0600, Orion Poplawski wrote:
Anyone willing to take over ngircd for EPEL?
https://bugzilla.redhat.com/show_bug.cgi?id=1830182
Sure. I can do that. Will add it to my list.
kevin
Anyone willing to take over ngircd for EPEL?
https://bugzilla.redhat.com/show_bug.cgi?id=1830182
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO
python38-rpm-macros brought into EPEL8.2 buildroot causing problems. See:
https://pagure.io/epel/issue/103
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
zabbix22 (epel7)]$ fedpkg retire 'Zabbix 2.2 is no longer maintained
upstream'
Fedora release (epel7) is in state 'current' - retire operation is not
allowed.
What's up?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Of
On 4/8/20 7:20 PM, Orion Poplawski wrote:
There does not appear to be an explicit conflict policy for EPEL8:
https://fedoraproject.org/wiki/EPEL/FAQ#Does_EPEL_replace_packages_provided_within_Red_Hat_Enterprise_Linux_or_layered_products.3F
I got a report against python3-s3transfer and
hine so it does seem available to everyone.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
smime.p7s
D
On 1/30/20 8:39 AM, Miro Hrončok wrote:
On 30. 01. 20 16:32, Orion Poplawski wrote:
Folks -
Looks like RHEL 8.2 will have python 3.8 in addition to python
3.6. From
the 8.2 beta:
Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta (RPMs)
Name Stream Profiles
vel at the same time, perhaps we
can define the python3_other* macros again for python38 and just go that way?
Thoughts?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or..
On 12/9/19 7:25 PM, Orion Poplawski wrote:
On 12/7/19 1:53 AM, Mattia Verga wrote:
I've also seen that there are some files in the newly created epel8
branch: .cvsignore, Makefile and package.cnf.
I would like to do a `git merge master` to sync epel8 branch with
fedora rawhide, but doing
ve to checkout every
single files one by one from Rawhide?
'git merge master' will not remove or change those files.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane
dle that. I'm also not so sure
that there won't be some kind of push for python 3.8 in EL7 at some
point since EOL is 6/30/2024.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell
/updates/new
https://fedoraproject.org/wiki/Package_update_HOWTO
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https
On 11/22/19 4:03 AM, Paul Howarth wrote:
> On Thu, 21 Nov 2019 21:56:46 -0700
> Orion Poplawski wrote:
>
>> DEBUG util.py:596: No available modular metadata for modular package
>> 'python2-rpm-macros-3-38.module+el8.1.0+3111+de3f2d8e.noarch', it
>> canno
i/taskinfo?taskID=39186949
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
smime.p7s
Descripti
On 11/16/19 8:25 AM, Miro Hrončok wrote:
> On 16. 11. 19 3:53, Orion Poplawski wrote:
>> I'm wondering if anyone can shed any light on possible roadmaps for
>> transitioning to newer python 3.X in RHEL8/EPEL8. What we have now appears
>> to be:
>>
>> A
ion
3
It seems any transition is going to have to be a hard break and/or we're
going to need modules. Is there any hope for parallel installable
python3Y stacks in RHEL8? Are we just going to have python36 forever?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772
you need. We're not going to builds things just to
do it. Thanks.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301
the epel8 one.
kevin
I guess I don't see why anyone needs to muck with packages.cfg. If you
want to build something for epel8-playground, just build it from the
epel8-playground branch.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office
its deps) until we
sort this out.
Thanks!
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
smime.
On 10/8/19 7:32 PM, Orion Poplawski wrote:
I retired this:
https://bodhi.fedoraproject.org/overrides/python-rpm-macros-3-31.el7
To allow epel 7 builds get the RHEL7.7 3-32.el7 version.
As a heads up - this will cause %py3_build to use /usr/bin/python3
rather than /usr/bin/python3.6 - which
I retired this:
https://bodhi.fedoraproject.org/overrides/python-rpm-macros-3-31.el7
To allow epel 7 builds get the RHEL7.7 3-32.el7 version.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane
On 8/14/19 6:40 PM, Stephen John Smoogen wrote:
On Wed, 14 Aug 2019 at 18:07, Orion Poplawski wrote:
I see virt modules (from dnf module info virt):
820190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1
820190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1
at would
acquire the state of the "perl" module and could contain the EPEL perl
packages. This would require coordination among the EPEL perl packagers
to maintain the epel-perl module but would also allow it to
automatically track the state of the RHEL module - and allow it to have
On 9/20/19 7:41 AM, Troy Dawson wrote:
> On Fri, Sep 20, 2019 at 6:12 AM Troy Dawson wrote:
>>
>> On Thu, Sep 19, 2019 at 9:09 PM Orion Poplawski wrote:
>>>
>>> On 9/3/19 3:01 PM, Troy Dawson wrote:
>>>> # KDE now available on EPEL 8 playground
>&
On 9/3/19 3:01 PM, Troy Dawson wrote:
# KDE now available on EPEL 8 playground
Many thanks to all those who have helped make this happen.
Thanks!
[3] - Currently gdm does not like to start plasma, use sddm instead
Is there a bug for this I can follow?
--
Orion Poplawski
Manager of NWRA
The epel8 branches were not properly created for hypre and superlu_dist.
They were apparently made in the PDC, but they don't exist in pagure.
What to do now? Thanks.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 30
edora land on EL-7 seems pretty
much impossible due to rpm changes so the useful lifetime of EL-7 for a
Fedora and EPEL contributor is already essentially at an end. Centos 8
can't come fast enough...
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Bo
On 8/16/19 8:16 PM, Orion Poplawski wrote:
On 8/16/19 12:16 AM, willi.feh...@t-online.de wrote:
Dear EPEL developers,
I would like to request a handful of packages for EPEL-8.
Name of the packages and short description and a reason why the
package is needed.
*Fail2Ban:*
Fail2Ban is an
systems from
brute-force attacks. It's already available in EPEL-7 and it's actively
used so I guess it make sense to push an .el8 package.
This is on my incredibly long list of things to do. Any help is
appreciated...
--
Orion Poplawski
Manager of NWRA Technical Systems
On 8/16/19 7:45 PM, Scott Talbert wrote:
Is automatic python dependency generation supposed to work on EPEL 8?
It seems to be working for me - not sure what the "official" stance is.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/C
those arches.
ExcludeArch: aarch64 s390x
seems to be the thing to do.
We have a limited arch policy for EPEL6/7, but I'm not sure if we want
to continue that for EPEL8.
https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
--
Orion Poplawski
Manager of NWRA Technic
t;> Which is showing as active.
>>
>> Thanks,
>> Richard
Sometimes things go awry... What I've found is that expiring the override and
then re-submitting it (with a later date as required) often works. I just did
this with the hdf5 update and it appears to be working now
What to do about missing gcc-objc from RHEL8? Are there alternative compilers
yet that we can access? Will we have to package gcc-objc for EPEL8 separately?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380
On 8/14/19 3:35 PM, Orion Poplawski wrote:
> On 8/14/19 3:26 PM, Orion Poplawski wrote:
>> On 8/14/19 2:54 PM, Stephen John Smoogen wrote:
>>> On Wed, 14 Aug 2019 at 16:01, Orion Poplawski wrote:
>>>>
>>>> My zabbix40 build for epel8 failed:
>>>
On 8/14/19 3:26 PM, Orion Poplawski wrote:
> On 8/14/19 2:54 PM, Stephen John Smoogen wrote:
>> On Wed, 14 Aug 2019 at 16:01, Orion Poplawski wrote:
>>>
>>> My zabbix40 build for epel8 failed:
>>>
>>> https://koji.fedoraproject.org/koji/taski
On 8/14/19 2:54 PM, Stephen John Smoogen wrote:
> On Wed, 14 Aug 2019 at 16:01, Orion Poplawski wrote:
>>
>> My zabbix40 build for epel8 failed:
>>
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678
>>
>> DEBUG util.py:585: BUILDSTDERR: Er
_64-baseos-rpmsRed Hat Enterprise Linux 8 for x86_64
- BaseOS (RPM 2,097
rhel-8-for-x86_64-supplementary-rpms Red Hat Enterprise Linux 8 for x86_64
- Supplementa 20
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FA
- thus all efforts on EPEL are highly appreciated.
>
>
> Regards,
> Robert
A hearty second! EPEL is key to our use of EL. Thanks Stephen, Kevin, and
everyone else.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-41
I've got a package of Zabbix 4.0.5 going to epel-testing:
https://bodhi.fedoraproject.org/updates/zabbix40-4.0.5-1.el7
feedback appreciated.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell
x27;s still on Bodhi 0.9, and I have never seen or
> worked on that codebase. Unfortunately, it has Python 2.6 and not any
> verison of Python 3, to my knowledge.
EPEL 6 does have python 3.4, I would just let that rot as is.
--
Orion Poplawski
Manager of NWRA Technical Systems
s repo will be up forever, but it should last
> until we get KDE in EPEL8, whenever that happens.
>
> Troy
>
Thanks for your work on this. My observation is - do want KDE to be a module
for EPEL8? I'm actually slightly surprised to find that Gnome does not appear
to be modu
karma ? please
Thanks
I pushed it to batched.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
smime.
installed.
Anyone know how to resolve this short of uninstalling python34-virtualenv?
Should be fixed with:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-813cc12887
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX
urce of my prob:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33463886
Chris
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder
s.warn(msg)
and ended up with a file egg-info instead of a directory.
I've rebuilt python3-six with the test requirements installed for both
versions now. I'll add python3-six-1.11.0-3.el7.src.rpm to the update.
--
Orion Poplawski
Manager of NWRA Technical Systems 720
oth python3 versions. We are
not (yet) dropping python34. It's just that the default
/usr/bin/python3 is switching to python 3.6, and packages that only
build for one python3 version are now shipping for 3.6.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772
python34-six-1.11.0-2.el7.noarch | grep egg
/usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boul
ch), mock exited with status 30; see
root.log for more information
0 free 0 open 0 done 2 failed
32993375 build (epel7, python-apprise-0.7.3-1.el7.nuxref.src.rpm) failed
Chris
On Sat, Feb 23, 2019 at 4:29 PM Orion Poplawski <mailto:or...@nwra.com>> wrote:
On 2
Zabbix 3.0 is now available for EPEL7 via the zabbix30-* packages. Enjoy.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301
1 - 100 of 254 matches
Mail list logo
