Search results

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

{{DISPLAYTITLE:Move /usr/bin/python into a separate package}} * changes to isolated/leaf package without the impact on other packages/rest of the distribution

In this guide we introduce solo keys and how to use them. There use cases we 'll mention are, using your keys for web authentication, upgrading your ...work by default. When upgrading to Fedora MATE 32 the <code>systemd</code> package was listed as a replacement therefore systemd is now responsible for having

This is necessary so that we can automatically rebuild a package without having to bump the release in the specfile. Any Fedora packager can rebuild a package into f39-app using 'fepdkg build --target=f39-app'.

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

| name = Fedora Test Days ...dora-test-day #fedora-test-day] ([https://web.libera.chat/?channels=fedora-test-day webirc])

...d normal disks (or with FW RAID turned off) shouldn't be affected. In most cases, you can use the UEFI boot menu as a workaround. Different systems (differe <li>First, make sure your libhif package version is the same as described above or newer:

Move the GOLD linker from the main binutils package into its own sub-package. ===[[Changes/F31 Mass Python 2 Package Removal | F31 Mass Python 2 Package Removal]]===

...したら、次の手続き [[Join the package collection maintainers|How to join the Fedora Package Collection Maintainers]] に従ってください。これは、Fedora の� ...work. Modern RPM-based systems, including Fedora, are set up to build and test RPM packages purely from within a non-privileged account. そして、コ�

* changes to isolated/leaf package without the impact on other packages/rest of the distribution ...hich branches and methods are executed, and evaluate total coverage of the test suite more strictly.

* changes to isolated/leaf package without the impact on other packages/rest of the distribution ...orked almost completely from scratch. As a result, comments in many corner cases that were previously lost are now included in the formatted output.

| name = Fedora Test Days ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

* changes to isolated/leaf package without the impact on other packages/rest of the distribution ...as] are a way for a Python package (called "distribution" or "distribution package" upstream) to declare that extra dependencies are required for additional f

= Package information on ELF objects = ...buted without any of the rpm metadata. `systemd-coredump` uses this to log package versions when reporting crashes.

...as possible, allowing for local users or products to override this base in cases they need to do so. ===[[Changes/Local Test Cloud | Local Test Cloud]]===

...only affects virtual machines and cloud instances. In particularly serious cases, the delay can be such that timeouts kick in and the system fails to boot f ...are suffering from this issue. It can also be a viable workaround in some cases, though of course not all.

...the bare package manager. Please be sure to read [[Upgrading Fedora using package manager]] for an overview of the entire process as well as the release-spec ...very special'''. Far beyond the general warning that upgrading with just a package manager is not recommended, the /usr move makes upgrading to Fedora 17 or l

...ration/delivery. In a continuous process, changes are checked not just for package changes, but in an integrated way, and constantly. If failure is detected, ...ur processes to take advantage of modern, hybrid cloud footprints. In some cases we are necessarily premise-bound — for instance, Power and s390x. However

<!-- Make sure the pages is named as "Test Day:YYYY-MM-DD topic" --> | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]