Search results

Fedora Core 5 introduced a new SELinux feature: loadable policy modules. ...integrate the policy with the monolithic base policy, as was the case for Fedora Core 4 and earlier releases.

Fedora Account Name: kwade Fedora Account Name: pfrields

* where in Fedora, a module has python3-foo subpackage, in EPEL the subpackage must be python # in the minimal buildroot; %%python3_pkgversion is also available in Fedora, so it's possible to have a common

== Fedora Package Collection CVS FAQ == export CVSROOT=:ext:USERNAME@cvs.fedora.redhat.com:/cvs/pkgs

...and the application - are the two types of artifacts we want to build for Fedora. ...installed on a system: for example, there might be both a Fedora 23 and a Fedora 24 runtime installed. A runtime looks like a mini-system image with librari

{{DISPLAYTITLE:Fedora Packaging Guidelines for Modules}} ...ry to add it to Platform first. By filing a ticket with https://github.com/fedora-modularity/hp/issues

...n || Miller, Matthew || https://mattdm.org/fedora/2017flock/2017-State-of-Fedora.pdf || ...system for Linux (WSL) || Jennings, Seth || https://www.variantweb.net/pub/fedora-wsl.pdf ||

...der free and open source licenses, many of which are also now available in Fedora. == Why Fedora? ==

...qa team. The tools promoted to manage that are taskotron and resultsdb in Fedora, but there is a different set used internally. We'll have to do some work ...r orchestration system and the CI system. We'll use resultsdb directly in Fedora. For internal PnT Devops use, we'll set up an adapter service to shuttle r

* Targeted release: [[Releases/36 | Fedora Linux 36 ]] * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/795 #795]

* Targeted release: Fedora 12 ...ast FIPS validated version of the cryptographic module if they so require. Fedora based distributions such as RHEL would greatly benefit from this feature in

= Whats new in Fedora Core 5, from SELinux???? = = SELinux in Fedora Core 5 =

...uilding or running any such kernel, one should NOT expect support from the Fedora kernel team; you're pretty much on your own here if something doesn't work <code> # sudo dnf install fedpkg fedora-packager rpmdevtools ncurses-devel pesign grubby</code>

= Fedora Release Notes Process = building <code>fedora-release-notes</code> package:

= Fedora Perl SIG Mission = To assist packagers in bringing Perl-related packages to Fedora and assisting in their continued maintenance by providing timely reviews, a

* Targeted release: [[Releases/18 | Fedora 18 ]] * Rebuild other packages: Use Fedora::Rebuild dependency solver or ordered sets computed by Paul

...preparation process for FDP only. If you are interested in packaging for Fedora Extras, refer to [[Extras/NewPackageProcess]] instead.}} ''ASSUMPTIONS:'' Your document is in Fedora Docs CVS, and can be built already (i.e. "make" works correctly). You must

...he kmod package needs to be adjusted to work in rpmfusion-devel (builds on Fedora 8) ...ttps://bugzilla.redhat.com/show_bug.cgi?id=kBuild-review Review kBuild for Fedora]

* Targeted release: [[Releases/33 | Fedora 33 ]] == Benefit to Fedora ==

{{DISPLAYTITLE:Fedora Packaging Guidelines for Perl}} ...PAT_5.8.7)</code>, etc., because backward compatibility was guaranteed for Fedora Perl 5.8.x.