Search results

=== Proper Flags in RPM .spec for Dell Firmware? === ...ius and JarodWilson explored the issue, which seemed to pivot about redhat-rpm-config breaking the ability of rpmbuild to cross-build packages for non-Fed

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> ** Create rpm-ostree repositories with the workstation content (Done: David)

= RPM 4.15 = Update RPM to the 4.15.0 release.

It is worth rebuilding the RPM DB to prevent RPMDB checksum error when doing a distribution sync: {{command|sudo rpm --rebuilddb}}

...ease visit the [[Docker|Fedora Wiki Docker page]] or the upstream [https://docs.docker.com/ Docker Documentation]. $ rpm -q docker

| docs-web || 69 || no || no || no | docs-tools || 62 || no || no || no

{{#fedoradocs: https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/}} ...more information about creating a modular operating system on the [https://docs.pagure.org/modularity/ Modularity Website].

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> ...technically cause a visible change in the resulting package. If queried, rpm will show the group as "Unspecified" for every binary package in the distri

<!-- From an original by Adam Lingas, posted to fedora-docs-list, and final edit/arrangement by Karsten Wade --> * Enhanced software update and maintenance, from RPM 4.6 to PackageKit

...Atomic Desktop (Silverblue, Atomic Sway, etc) installation to Kinoite with rpm-ostree by simply running rpm-ostree rebase fedora:fedora/VersionNumber/x86_64/kinoite

* http://fedora.redhat.com/docs/selinux-faq/ === Excellence: RPM + yum ===

= Bodhi Non-RPM Artifacts <!-- The name of your change proposal --> = * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> * Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/126 #126]

= RPM 4.14 <!-- The name of your change proposal --> = Update RPM to the 4.14.0 release.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[ http://taiga.fedorainfracloud.org/project/mjw-better-rpm-debuginfo-package-creation/

...adger1999||Discuss||[[User:Toshio/Type_Specific_Guidelines]] Talking with docs about this idea. Will send mail to packaging-list for input when we have s ...[Python virtual provides draft]] Panu has been looking at this as part of rpm itself.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[ in the system installed from RPM, such application will be run with the JVM set in alternatives,

* RPM/Packaging. ...e about the CommOps team on [https://docs.fedoraproject.org/en-US/commops/ docs.fedoraproject.org/en-US/commops].

...''Jargon Buster'', available in American English and Portuguese at http://docs.fedoraproject.org/jargon-buster/. General Fedora-specific terms are covere ''[[Docs/Drafts/Glossary| All Contributors]] ''

Implement feature in RPM which will enforce strict dependencies between subpackages automatically (r * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->