I like to have everything on my system in a package. So, I looked around and
found no recipe or rpm for Rstudio. This is really a shame because every
tutorial on R kinda tells you to install it. Even the Coursera classes in the
Data Science track make you install it and send a screenshot to prove it.
So, I spent some time getting it packaged and working. I am placing the spec
file and necessary patch here so that google finds it and saves other people the
trouble. I'm not wanting to submit the package to Fedora because its more work
than I have time for. If anyone else wants to take it from here and submit
and/or maintain it, feel free.
I need/want/would like to build new node 6 for EL6, but gcc is too old.
For that reason, I'd like to use devtoolset-4-gcc, but the build fails
(obviously) because the package doesn't exist.
So, is there a way to make that work somehow?
I am not sure about enabling external repos during build, maybe someone
will be wiser.
Here's the build:
apitrace 5.0 bundles libbacktrace, which looks like is living within the
gcc sources. libbacktrace is not build as a shared library from the gcc
sources, and not packaged.
Is it feasible to build libbacktrace as a shared library and ship it in
a corresponding package? Or should I rather go for a bundling exception
This is a reminder that the webkitgtk and webkitgtk3 packages will be
retired from rawhide shortly after F26 is branched from rawhide. This
is due to numerous security issues affecting those packages (I just
counted 204 CVEs), many of which could allow remote code execution.
Bugs have already been filed against all directly-affected packages
Note: to count the vulnerabilities, I just manually added up the CVEs
listed at , ignoring the oldest advisory WSA-2015-0001, and
discounting five of the older vulnerabilities in WSA-2015-0002.
Greetings. Is https://github.com/fedora-selinux/selinux-policy-contrib
the right place to contribute to the Fedora SELinux policy?
I added a pull request for a small update needed for a new release of
cups-pdf, but I am not sure someone is monitoring that. There is another
one from rhatdan there so I presume is the right place.
Has anyone heard from kanarip or able to contact him?
I've been attempting to contact for this bug:
If there's no response in one week an issue will be filed with FESCo
following the nonrepsonsive maintainer policy to review the ownership
status of the packages.
For ruby maintainers please note that this has a significant impact on
you, if you want to keep track of this, as he owns puppet, rubygems
and ruby ...
= Proposed System Wide Change: perl Package to Install Core Modules =
* Petr Písař <ppisar AT redhat DOT com>
dnf install perl will install all core Perl modules that come with
Perl upstream sources.
== Detailed Description ==
Upstream releases Perl interpreter together many Perl modules. This
set of modules is called core modules. Fedora splits the modules into
subpackages so that installing perl package results in stripped-down
set of modules. Fedora documents this as a feature and provides
perl-core to metapackage that allows installing all the core modules
as is intended by upstream.
Unfortunately this seems to be confusing to Perl users because Fedora
is the only distribution doing so.
To align Fedora's behaviour to upstream and other distributions this
change will rename perl package to perl-interpreter and perl-core
package to perl'. This will allow installing all core Perl modules
with dnf install perl while still retain the possibility to install
only a minimal perl interpreter (/usr/bin/perl) with dnf install
This change will also update Fedora Packaging Guidelines for Perl to
all spec files that require perl to use perl-interpreter instead.
There is only 81 binary packages affected. They will rebuilt.
Otherwise no mass rebuild won't be necessary.
To ease sharing spec files with older Fedoras, perl-interpreter
provide will add to perl package there.
== Scope ==
* Proposal owners:
- Submit Fedora Packaging Guidelines for Perl update to Fedora
- Update and rebuild perl source package.
- Add Provides: perl-interpreter to perl package in older Fedoras.
- Replace BuildRequires and Requires for perl with perl-interpreter in
all spec files.
- Rebuild packages with replaced Requires to propagate the change to
- Replace perl-core with perl in compose groups definition.
* Other developers:
Get familiar with new Fedora Packaging Guidelines for Perl.
* Release engineering:
No action needed. Request to check of an impact with Release
* List of deliverables:
Anything what contains perl package
* Policies and guidelines:
Fedora Packaging Guidelines for Perl update request (
https://pagure.io/packaging-committee/issue/690 ) to use perl and
perl-interpreter instead of perl-core and perl.
N/A (not needed for this Change)
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic