Search results

= Packaging kernel modules for Fedora Extras = ...s Steering Commitee (FESCo) worked out below standard for packaging kernel-modules in Fedora. This Standard hopefully solves many pitfalls earlier standards i

= Packaging kernel modules for Fedora Extras = ...s Steering Commitee (FESCo) worked out below standard for packaging kernel-modules in Fedora. This standard hopefully solves many pitfalls earlier standards i

{{header|docs}} Process additions for developers need to minimally interrupt an already working and complex workflow.

...n Fedora 26 Boltron, splitting the minimal system further into independent modules allowing for greater flexibility when composing and maintaining the base sy ...nge focuses on modular content structure; [[Changes/ModularRelease]] deals with details regarding modular delivery.

= NSS load p11-kit modules by default = When NSS database is created, PKCS#11 modules configured in the system's p11-kit will be automatically registered and vis

...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ich now defaults to /var/lib/selinux/. The new store supports priority for modules and changes fromat from .pp to CIL language

{{#fedoradocs: https://docs.fedoraproject.org/en-US/server-working-group/}} ...|Server SIG and Server WG are [https://docs.fedoraproject.org/en-US/server-working-group/ reorganized into one team].}}

...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

...o pip3</code> in Fedora is not safe. Pip shares its installation directory with dnf, can remove dnf-managed files and generally break the Python 3 interpre ...system. '''Never ever ever ever use <code>pip</code> or <code>pip3</code> with <code>sudo</code>.''' Use <code>pip --user</code> or [https://developer.fed

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...on of the application server previously known as JBoss Application Server. With the version 8 it makes it possible to run your Java EE 7 applications and m

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ges to the infrastructure and technology implementations will be available with sufficient time to harden the components in time for the 27 release.

...28, Fedora will provide a new set of repositories for software and updates with alternative versions from those shipped in the default release. ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

...ss that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved GFS2 is part of the upstream kernel, but is still listed as experimental. The plan is that this will become sta

...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->

...requires on packages that provide cmake(foo) or place files into the CMake Modules directory. * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

| style="color: #407a40" | #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetin | style="color: #407a40" | Sparks to follow up with the News people about Zikula

| A kernel regression and perf testing DO session | Automate Building Custom Atomic Host with Ansible