R 2.12.1 is built now for Fedora and EPEL. It is in "updates-testing"
(or it will be within the next 24 hours).
In accordance with the new policies on Fedora Updates, these new
packages will not be pushed as official updates until they either
receive positive testing from users, or sit in updates-testing for two
weeks.
You can help us test these packages, and move them forward. Here's how:
1. Go to the Fedora Updates web application (its real name is "Bodhi"):
https://admin.fedoraproject.org/updates/
Once you're there, click the login blue box at the top left, and login
with your Fedora Account. If you don't have a Fedora Account, you can
give feedback, but it doesn't count towards giving the update positive
karma. For that reason, I would strongly recommend that you take 45
seconds and create a Fedora Account. :)
2. Click on the link for the Fedora R test update that matches your release:
Fedora 13:
https://admin.fedoraproject.org/updates/rkward-0.5.4-2.fc13,rpy-2.0.8-6.fc1…
Fedora 14:
https://admin.fedoraproject.org/updates/rkward-0.5.4-2.fc14,rpy-2.1.9-1.fc1…
EPEL-4 (RHEL-4):
https://admin.fedoraproject.org/updates/R-2.12.1-1.el4
EPEL-5 (RHEL-5):
https://admin.fedoraproject.org/updates/R-2.12.1-1.el5
3. Now, on your Fedora (or RHEL) system, run this command (as root, or
with root privs) to install the test update:
yum --enablerepo=updates-testing update R
That should update R to the test update (if you don't want the full R
suite, you can replace "R" in that string with "R-core").
4. Test it! Make sure it does all the things you would expect it to.
5. Go back to the web page for the R update (step 2), and at
the bottom, click "Add a comment >>"
(If you didn't login, it will ask you for an email address and make you
complete a captcha to make sure you are a unique individual.)
In that text box which opens up, write a little bit about the testing
you did and if it works okay for you or not. Then (this is the important
part), click the "Works for me" or "Does not work" radio button below
it, and click the Add Comment button.
6. That's it! If it worked, you've given that update a +1 karma vote.
(If it didn't work, you've given it a -1 karma vote). Now, if three
people (with Fedora Accounts) give a +1, and the package update gets to
+3, the Fedora Update system will automatically move the update from
testing to a real update, and everyone will get it.
Thanks in advance,
Tom Callaway, Fedora/EPEL R maintainer
R 2.12.0 is built now for Fedora and EPEL. It is in "updates-testing"
(or it will be within the next 24 hours).
I did not do this build for Fedora 12, as that release will be
End-Of-Life in a month.
In accordance with the new policies on Fedora Updates, these new
packages will not be pushed as official updates until they either
receive positive testing from users, or sit in updates-testing for two
weeks.
You can help us test these packages, and move them forward. Here's how:
1. Go to the Fedora Updates web application (its real name is "Bodhi"):
https://admin.fedoraproject.org/updates/
Once you're there, click the login blue box at the top left, and login
with your Fedora Account. If you don't have a Fedora Account, you can
skip this step.
2. Click on the link for the Fedora R test update that matches your release:
Fedora 13:
https://admin.fedoraproject.org/updates/rpy-2.0.8-5.fc13,R-2.12.0-1.fc13
Fedora 14:
https://admin.fedoraproject.org/updates/rpy-2.1.7-1.fc14,R-2.12.0-1.fc14
EPEL-4 (RHEL-4):
https://admin.fedoraproject.org/updates/R-2.12.0-1.el4.1
EPEL-5 (RHEL-5):
https://admin.fedoraproject.org/updates/R-2.12.0-1.el5
3. Now, on your Fedora (or RHEL) system, run this command (as root, or
with root privs) to install the test update:
yum --enablerepo=updates-testing update R
That should update R to the test update (if you don't want the full R
suite, you can replace "R" in that string with "R-core").
4. Test it! Make sure it does all the things you would expect it to.
5. Go back to the web page for the R update (step 2), and at
the bottom, click "Add a comment >>"
(If you didn't login, it will ask you for an email address and make you
complete a captcha to make sure you are a unique individual.)
In that text box which opens up, write a little bit about the testing
you did and if it works okay for you or not. Then (this is the important
part), click the "Works for me" or "Does not work" radio button below
it, and click the Add Comment button.
6. That's it! If it worked, you've given that update a +1 karma vote.
(If it didn't work, you've given it a -1 karma vote). Now, if three
people give a +1, and the package update gets to +3, the Fedora Update
system will automatically move the update from testing to a real update,
and everyone will get it.
Thanks in advance,
~spot, Fedora/EPEL R maintainer
The R-multcomp maintainer asked me to look into why it was failing to
build in rawhide. When I looked into it, I discovered that something is
broken in how R CMD CHECK --no-install works in 2.10.1. I couldn't tell
you what is broken exactly, but I took the time today to package up all
the Suggests (and their depchain) and tested the package without
--no-install (and without --no-latex) and it works fine again.
I asked Orion (the R-multcomp maintainer) if he was interested in
maintaining/co-maintaining/reviewing these new R packages, but he wasn't
interested. In fact, he said he was more inclined to orphan R-multcomp.
Is there any interest in helping me maintain and review these new R
packages in Fedora? The packages are already done, its just the reviews
and upkeep that I'd need help with.
Here's the packages:
http://auroralinux.org/people/spot/review/R-multcomp/
These are the R packages I made today:
coin, colorspace, ipred, lme4, mboost, mlbench, modeltools, multicore,
party, robustbase, sandwich, strucchange, vcd, xtable
If any of these look interesting to you, speak up! If no one cares, I
might just let R-multcomp orphan off, but if there are some willing
helpers, I'll keep it alive with its new dependencies.
~spot
R 2.11.1 is built now for Fedora and EPEL. It is in "updates-testing"
(or it will be within the next 24 hours).
It will likely be the last R update for Fedora 11.
In accordance with the new policies on Fedora Updates, these new
packages will not be pushed as official updates until they either
receive positive testing from users, or sit in updates-testing for two
weeks.
You can help us test these packages, and move them forward. Here's how:
1. Go to the Fedora Updates web application (its real name is "Bodhi"):
https://admin.fedoraproject.org/updates/
Once you're there, click the login blue box at the top left, and login
with your Fedora Account. If you don't have a Fedora Account, you can
skip this step.
2. Click on the link for the Fedora R test update that matches your release:
Fedora 11:
https://admin.fedoraproject.org/updates/rpy-2.0.8-3.fc11,R-2.11.1-1.fc11
Fedora 12:
https://admin.fedoraproject.org/updates/rpy-2.0.8-3.fc12,R-2.11.1-1.fc12
Fedora 13:
https://admin.fedoraproject.org/updates/rpy-2.0.8-4.fc13,R-2.11.1-1.fc13
EPEL-4 (RHEL-4):
https://admin.fedoraproject.org/updates/R-2.11.1-1.el4
EPEL-5 (RHEL-5):
https://admin.fedoraproject.org/updates/R-2.11.1-1.el5
3. Now, on your Fedora (or RHEL) system, run this command (as root, or
with root privs) to install the test update:
yum --enablerepo=updates-testing update R
That should update R to the test update (if you don't want the full R
suite, you can replace "R" in that string with "R-core").
4. Test it! Make sure it does all the things you would expect it to.
5. Go back to the web page for the R update (step 2), and at
the bottom, click "Add a comment >>"
(If you didn't login, it will ask you for an email address and make you
complete a captcha to make sure you are a unique individual.)
In that text box which opens up, write a little bit about the testing
you did and if it works okay for you or not. Then (this is the important
part), click the "Works for me" or "Does not work" radio button below
it, and click the Add Comment button.
6. That's it! If it worked, you've given that update a +1 karma vote.
(If it didn't work, you've given it a -1 karma vote). Now, if three
people give a +1, and the package update gets to +3, the Fedora Update
system will automatically move the update from testing to a real update,
and everyone will get it.
Thanks in advance,
~spot, Fedora/EPEL R maintainer
Hi all,
As announced on my blog, I have released the new version of R2spec
(version 3.0.0) containing R2rpm.
Below[2] is the full changelog for this release.
Thanks for your comments/feedbacks on this release.
Feel free to test it again and add karma on Bodhi [1]
Thanks to all of you again,
Pierre
[1]
https://admin.fedoraproject.org/updates/R2spec-3.0.0-1.fc13https://admin.fedoraproject.org/updates/R2spec-3.0.0-1.fc12https://admin.fedoraproject.org/updates/R2spec-3.0.0-1.fc11https://admin.fedoraproject.org/updates/R2spec-3.0.0-1.el4https://admin.fedoraproject.org/updates/R2spec-3.0.0-1.el5
[2]
Changelog:
----------
Version 3.0.0 -- 05th May 2019
- Features added
* R2spec can now be called from an external script
* Use template via jinja2 to generate the spec files (Based on an idea
of Allen S. Rout)
* Create the R2rpm script which directly builds the rpm
* Add a man page for R2rpm
* Add the -p option which enable to build a spec from a package name
* Parse the PACKAGES file from the repositories to find the
information for the packages
* Make the print of the TODO optional in the API
* Give the opportunity to use mock to build the RPMs (rpmbuild being
the default)
* Enable to specify the mock command in the conf file
* Enable to change the argument given to rpmbuild via the conf file
(to build srpm instead of rpm for example)
- Bugs correction
* Fix the addition of the R- prefix to the dependencies
* Rewrite the reading of the DESCRIPTION file from R
* Do not enforce the spec and the source directory, reads the
rpmmacros instead
Thanks to José Matos for this function
* Fix the summary if it ends with a dot "."
* Capitalize the summary by default
* Change UTF-8 to utf-8 to make emacs happy
* Fix the spec file for the dependencies of this new release
* Fix some bugs while trying to generate the RPM/SPEC from a tarball