[EPEL-devel] Python 2 macros on EL 6
Hi,
%{python2_sitelib} doesn't exist on epel6 ?
from https://copr-be.cloud.fedoraproject.org/results/sergiomb/builds_fo
r_Stable_Releases/epel-6-i386/00173942-subdownloader/build.log.gz
I got:
RPM build errors:
File must begin with "/": %{python2_sitelib}/subdownloader
which means %{python2_sitelib} is wasn't defined .
Thanks,
--
Sérgio M. B.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Simplifying use of Python 3 macros?
On Mon, Apr 11, 2016 at 3:35 PM, Dave Johansen
wrote:
> On Mon, Apr 11, 2016 at 1:09 PM, Jason L Tibbitts III
> wrote:
>
>> > "DJ" == Dave Johansen writes:
>>
>> DJ> Is there anything that could be done in EPEL to make the Python 3
>> DJ> macros be usable without requiring %{python3_pkgversion}?
>>
>> Well, there has been some on and off work focused on making python
>> packaging less hideous. A spec would look sort of like this:
>>
>> https://pagure.io/python-macros/blob/master/f/test1.spec
>>
>> And I think that would work down into EPEL.
>>
>
> Good to hear that progress is being made.
>
>
>> But otherwise, there's not much we can do about that _pkgversion macro,
>> since EPEL may even get multiple python versions at some point. The
>> fancy macros actually handle that, but they aren't really a thing you
>> could use right now.
>>
>
> For the time being, could the python34 package add a Provides for python3
> so the _pkgversion macro isn't necessary?
>
Or maybe even better, could there be a python3 package in EPEL that is just
a set of Requires to act as a sort of "alias" to the python3x packages?
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 912 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2013-11893 libguestfs-1.20.12-1.el5 677 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-1626 puppet-2.7.26-1.el5 526 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-3849 sblim-sfcb-1.3.8-2.el5 169 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-edbea40516 mcollective-2.8.4-1.el5 141 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-582c8075e6 thttpd-2.25b-24.el5 33 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-bafacd5846 proftpd-1.3.3g-5.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing fts-3.4.3-1.el5 Details about builds: fts-3.4.3-1.el5 (FEDORA-EPEL-2016-27980fa037) File Transfer Service V3 Update Information: New upstream release ___ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
[EPEL-devel] Xfce 4.12 mega update coming to EL-7
All, After a trial run involving a COPR repo [1], I had written earlier indicating that I started doing real builds of Xfce 4.12 packages for EL-7 [2]. This is now complete and I have now submitted a update - a mega update containing 53 packages total. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-262a3f39e1 Three points about the update - - libxfce4ui obsoletes libxfcegui4 (plugins using libxfcegui4 were never built for EL-7) - xfce4-pulseaudio-plugin obsoletes xfce4-mixer and xfce4-volumed (xfce4-volumed is not even in the repos) - xfce4-pulseaudio-plugin uses pavucontrol as sound mixer which is unavailable in EL-7 at the moment. I have tested both upgrading a user configured Xfce 4.10 install and by creating a new user. I did not notice any issues so far. Please enable epel-testing repo on a test machine, test these packages and give karma on bodhi. I have set the stable karma to 12. Unless the karma reaches 12, I intend to leave the update in testing for **three weeks**. Mukundan. [1] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/NCCH5INLQM6J2VGFOTLGQZTKNG7Y3OOQ/ [2] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/XQNR2S7SYWSVRQBOPOGMU5MLMHKO6TAQ/ -- GPG Key - E5C8BC67 --- signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
[EPEL-devel] %autosetup now in EPEL5 and EPEL6 proper
Just FYI, EPEL5 and EPEL6 now have functioning %autosetup implementations. For EPEL6 there are no caveats; for EPEL6, if you have patches numbered higher than Patch9: then you will need to set %el5_patches_limit appropriately. But, uh, why would you do that? All documented at https://fedoraproject.org/w/index.php?title=EPEL:Packaging shortly. - J< ___ epel-devel mailing list epel-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
