EPEL GHC 7.0.4 and cabal-install for 5
Hi, This a headsup that there is a ghc refresh update for EPEL 5 now in testing: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12484/ghc-7.0.4-45.3.el5,cabal-install-0.10.2-6.1.el5 This updates ghc from 6.12.3 to a bit more recent stable release, which is also the currently the version in EPEL6. Later I am thinking to refresh EPEL6 to ghc-7.4.2. (Current F20 has 7.6.3.) If we had scl for EPEL it would be good to ship multiple ghc versions over the EPEL lifetime, since building newer packages with the older ghc versions is often problematic. Eg the latest pandoc releases needs ghc-7.4 to build. But some people might still want to stay with the older version for their projects. Do test if you are interested or using EPEL5 ghc. Thanks, Jens ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Python 3 for 7?
On Tue, Jan 14, 2014 at 09:13:12PM +0100, Jochen Schmitt wrote: > On Tue, Jan 14, 2014 at 12:35:00PM -0700, Stephen John Smoogen wrote: > > > 1) Does providing python-3.4 mean that 3.4 will be the only python every > > provided by EPEL? > > On Fedora ew have a python package which points to the 2.7 series and a > python3 package which points to the 3.3 series of python. I think we > should take this solution for EPEL because I think that python-2.7.x is > the standard python version which should not been overriden. > > > 2) If it doesn't then how are upgrades from 3.4 to 3.5 to 3.6 going to be > > handled? > > I think we need a conservative update handling to avoid incompatibilities > caused due an python update. > We could also take the python2.6 package in EPEL5 as inspiration here and ship a python3.4. This would allow us to ship a python3.5, python3.6, etc set of packages in the future. -Toshio pgph0RCvaj5ko.pgp Description: PGP signature ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Python 3 for 7?
On Tue, Jan 14, 2014 at 12:35:00PM -0700, Stephen John Smoogen wrote: > 1) Does providing python-3.4 mean that 3.4 will be the only python every > provided by EPEL? On Fedora ew have a python package which points to the 2.7 series and a python3 package which points to the 3.3 series of python. I think we should take this solution for EPEL because I think that python-2.7.x is the standard python version which should not been overriden. > 2) If it doesn't then how are upgrades from 3.4 to 3.5 to 3.6 going to be > handled? I think we need a conservative update handling to avoid incompatibilities caused due an python update. Best Regards: Jochen Schmitt ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Python 3 for 7?
On 14 January 2014 09:57, Orion Poplawski wrote: > It seems like it would be nice to have python 3 in EPEL 7. Anyone willing > to > maintain it there? > > It seems to build fine: > http://copr-fe.cloud.fedoraproject.org/coprs/orion/Python3_EPEL7/builds/ > > Well a couple of other things would be needed beyond just maintenance: 1) Does providing python-3.4 mean that 3.4 will be the only python every provided by EPEL? 2) If it doesn't then how are upgrades from 3.4 to 3.5 to 3.6 going to be handled? -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Python 3 for 7?
On Tue, Jan 14, 2014 at 09:57:18AM -0700, Orion Poplawski wrote: > It seems like it would be nice to have python 3 in EPEL 7. Anyone willing to It may be very helpful to have Python 3 in EPEL-7. I'm planing to provide the current version of blender on EPEL-7 and this version requires Python 3. Best Regards: Jochen Schmitt ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL Python 3 for 7?
It seems like it would be nice to have python 3 in EPEL 7. Anyone willing to maintain it there? It seems to build fine: http://copr-fe.cloud.fedoraproject.org/coprs/orion/Python3_EPEL7/builds/ -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL 7 status
On 14/01/14 14:27, Dennis Gilmore wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El Tue, 14 Jan 2014 14:18:38 + Paul Howarth escribió: On 10/01/14 23:52, Dennis Gilmore wrote: Hi All, Se we have composes working automatically now, the job had been failing. I'm trying to get epel 7 to the point where the packaging tools are available on epel7. hopefully that will be by the end of today. In order to submit builds for epel7 you need to have fedpkg-1.15-1 installed, versions prior will fail due to not understanding the epel7 branch. https://fedoraproject.org/wiki/EPEL/epel7 lists all the packages in RHEL 7 Beta. Please put branching request in https://fedoraproject.org/wiki/EPEL/epel7/Requests if you think of a better way to file requests please speak up. We will do some checking that the package is not in RHEL before branching but please check the list if you are not sure. I'm getting along nicely with most of my packages, but I'm having trouble pushing a single fast-forward commit for one of my packages: $ git status # On branch epel7 # Your branch is ahead of 'origin/epel7' by 1 commit. # (use "git push" to publish your local commits) # nothing to commit, working directory clean $ fedpkg push Total 0 (delta 0), reused 0 (delta 0) remote: W refs/heads/epel7 perl-Compress-Raw-Lzma pghmcfc DENIED by refs/heads/epel[0-9] remote: error: hook declined to update refs/heads/epel7 To ssh://pghm...@pkgs.fedoraproject.org/perl-Compress-Raw-Lzma ! [remote rejected] epel7 -> epel7 (hook declined) error: failed to push some refs to 'ssh://pghm...@pkgs.fedoraproject.org/perl-Compress-Raw-Lzma' Could not execute push: Command '['git', 'push']' returned non-zero exit status 1 Any ideas? The branch is done in git but I didn't get the email about it being added to pkgdb, and a pkgdb query doesn't show the epel7 branch. Something gone wrong during branching? Im guessing you put EL-6 as the acl source in your request, and the package currently does not exist in EPEL so you needed to use devel as the source to copy the acls from. I thought it was clear what you needed to do, but apparently not so please help to make the wording better so that everyone gets it. you will need to put in a new request with the correct acl source Whoops. I did see that and understood it too. Virtually all of my packages go all the way back to EL-5 and there are very few without an EL-6 branch so I forgot to check in this case and just put EL-6 out of habit. Sorry about that, branch re-requested. Regards, Paul. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL 7 status
On 10/01/14 23:52, Dennis Gilmore wrote: Hi All, Se we have composes working automatically now, the job had been failing. I'm trying to get epel 7 to the point where the packaging tools are available on epel7. hopefully that will be by the end of today. In order to submit builds for epel7 you need to have fedpkg-1.15-1 installed, versions prior will fail due to not understanding the epel7 branch. https://fedoraproject.org/wiki/EPEL/epel7 lists all the packages in RHEL 7 Beta. Please put branching request in https://fedoraproject.org/wiki/EPEL/epel7/Requests if you think of a better way to file requests please speak up. We will do some checking that the package is not in RHEL before branching but please check the list if you are not sure. I'm getting along nicely with most of my packages, but I'm having trouble pushing a single fast-forward commit for one of my packages: $ git status # On branch epel7 # Your branch is ahead of 'origin/epel7' by 1 commit. # (use "git push" to publish your local commits) # nothing to commit, working directory clean $ fedpkg push Total 0 (delta 0), reused 0 (delta 0) remote: W refs/heads/epel7 perl-Compress-Raw-Lzma pghmcfc DENIED by refs/heads/epel[0-9] remote: error: hook declined to update refs/heads/epel7 To ssh://pghm...@pkgs.fedoraproject.org/perl-Compress-Raw-Lzma ! [remote rejected] epel7 -> epel7 (hook declined) error: failed to push some refs to 'ssh://pghm...@pkgs.fedoraproject.org/perl-Compress-Raw-Lzma' Could not execute push: Command '['git', 'push']' returned non-zero exit status 1 Any ideas? The branch is done in git but I didn't get the email about it being added to pkgdb, and a pkgdb query doesn't show the epel7 branch. Something gone wrong during branching? Paul. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL epel beta report: 20140114 changes
Compose started at Tue Jan 14 08:15:02 UTC 2014 Broken deps for x86_64 -- MySQL-zrm-2.2.0-15.el7.noarch requires perl(XML::RSS) MySQL-zrm-2.2.0-15.el7.noarch requires perl(Data::Report::Plugin::Text) MySQL-zrm-2.2.0-15.el7.noarch requires perl(Data::Report::Plugin::Html) MySQL-zrm-2.2.0-15.el7.noarch requires perl(Data::Report) >= 0:0.05 ansible-1.4.3-1.el7.noarch requires python-paramiko ansible-1.4.3-1.el7.noarch requires python-httplib2 bodhi-server-0.9.7-1.el7.noarch requires python-simplemediawiki bodhi-server-0.9.7-1.el7.noarch requires fedmsg >= 0:0.3.3 1:centerim-4.22.10-14.el7.x86_64 requires perl(Time::ParseDate) cinnamon-2.0.14-7.el7.x86_64 requires zukitwo-gtk3-theme cinnamon-2.0.14-7.el7.x86_64 requires zukitwo-gtk2-theme cinnamon-2.0.14-7.el7.x86_64 requires tint2 cinnamon-2.0.14-7.el7.x86_64 requires gnome-themes cinnamon-2.0.14-7.el7.x86_64 requires blueman fluid-0.2.0-1.el7.x86_64 requires qt5-qtquickcontrols golang-github-gorilla-context-devel-0-0.19.git708054d.el7.noarch requires golang hawaii-widget-styles-0.2.0-1.el7.x86_64 requires qt5-qtquickcontrols imapsync-1.580-1.el7.noarch requires perl(Data::Uniqid) imapsync-1.580-1.el7.noarch requires perl(Authen::NTLM) koji-vm-1.8.0-2.el7.noarch requires python-virtinst mimedefang-2.74-1.el7.x86_64 requires perl(MIME::Words) mimedefang-2.74-1.el7.x86_64 requires perl(MIME::Tools) >= 0:5.410 mimedefang-2.74-1.el7.x86_64 requires perl(MIME::Parser) perl-Test-WWW-Selenium-1.36-1.el7.noarch requires perl(namespace::clean) perl-Test-WWW-Selenium-1.36-1.el7.noarch requires perl(Devel::REPL::Plugin) php-symfony-monologbridge-2.3.9-0.el7.noarch requires php-Monolog < 0:2.0 php-symfony-monologbridge-2.3.9-0.el7.noarch requires php-Monolog >= 0:1.3 php-symfony-swiftmailerbridge-2.3.9-0.el7.noarch requires php-pear(pear.swiftmailer.org/Swift) < 0:5.1.0 php-symfony-swiftmailerbridge-2.3.9-0.el7.noarch requires php-pear(pear.swiftmailer.org/Swift) >= 0:4.2.0 proftpd-utils-1.3.4d-5.el7.x86_64 requires perl(Mail::Sendmail) python-fedora-flask-0.3.32.3-4.el7.noarch requires python-flask python-sphinxcontrib-httpdomain-1.1.8-3.el7.noarch requires python-sphinx10 qelectrotech-0.30-1.el7.x86_64 requires electronics-menu snmptt-1.4-0.7.beta2.el7.noarch requires perl-Net-SNMP snmptt-1.4-0.7.beta2.el7.noarch requires perl(Config::IniFiles) Broken deps for ppc64 -- MySQL-zrm-2.2.0-15.el7.noarch requires perl(XML::RSS) MySQL-zrm-2.2.0-15.el7.noarch requires perl(Data::Report::Plugin::Text) MySQL-zrm-2.2.0-15.el7.noarch requires perl(Data::Report::Plugin::Html) MySQL-zrm-2.2.0-15.el7.noarch requires perl(Data::Report) >= 0:0.05 TurboGears-1.1.3-8.el7.noarch requires python-simplejson >= 0:1.9.1 ansible-1.4.3-1.el7.noarch requires python-paramiko ansible-1.4.3-1.el7.noarch requires python-httplib2 bodhi-client-0.9.7-1.el7.noarch requires python-simplejson bodhi-server-0.9.7-1.el7.noarch requires python-simplemediawiki bodhi-server-0.9.7-1.el7.noarch requires fedmsg >= 0:0.3.3 1:centerim-4.22.10-14.el7.ppc64 requires perl(Time::ParseDate) cinnamon-2.0.14-7.el7.ppc64 requires zukitwo-gtk3-theme cinnamon-2.0.14-7.el7.ppc64 requires zukitwo-gtk2-theme cinnamon-2.0.14-7.el7.ppc64 requires tint2 cinnamon-2.0.14-7.el7.ppc64 requires gnome-themes cinnamon-2.0.14-7.el7.ppc64 requires blueman fluid-0.2.0-1.el7.ppc64 requires qt5-qtquickcontrols golang-github-gorilla-context-devel-0-0.19.git708054d.el7.noarch requires golang hawaii-widget-styles-0.2.0-1.el7.ppc64 requires qt5-qtquickcontrols imapsync-1.580-1.el7.noarch requires perl(Data::Uniqid) imapsync-1.580-1.el7.noarch requires perl(Authen::NTLM) koji-vm-1.8.0-2.el7.noarch requires python-virtinst mimedefang-2.74-1.el7.ppc64 requires perl(MIME::Words) mimedefang-2.74-1.el7.ppc64 requires perl(MIME::Tools) >= 0:5.410 mimedefang-2.74-1.el7.ppc64 requires perl(MIME::Parser) perl-Test-WWW-Selenium-1.36-1.el7.noarch requires perl(namespace::clean) perl-Test-WWW-Selenium-1.36-1.el7.noarch requires perl(Devel::REPL::Plugin) php-symfony-monologbridge-2.3.9-0.el7.noarch requires php-Monolog < 0:2.0 php-symfony-monologbridge-2.3.9-0.el7.noarch requires php-Monolog >= 0:1.3 php-symfony-swiftmailerbridge-2.3.9-0.el7.noarch requires php-pear(pear.swiftmailer.org/Swift) < 0:5.1.0 php-symfony-swiftmailerbridge-2.3.9-0.el7.noarch requires php-pear(pear.swiftmailer.org/Swift) >= 0:4.2.0 p
