Search results

...Fedora uses wined3d and users can optionally install DXVK (be it wine-dxvk package or by any other means). With this change accepted, wine would use DXVK inst DXVK is available as a wine-dxvk package since Fedora 31. wine-dxvk package uses alternatives system for following wine dll files: d3d9, d3d10.dll and

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...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 ...months. but 3/4 of them are Short Term Supported for 6 months only. This package is designed to harbore them. Currently it is build on openJDK 10. LTSs (nex

A general rule that applies in most cases is as follows: The [http://dnf.readthedocs.org/en/latest/automatic.html dnf-automatic] RPM package as a [[dnf|DNF]] component provides a service which is started automaticall

...ported to Python 3. These are parts of the minimal buildroot, the default package manager, programs present on the LiveCD etc. More information on the packag * DNF is the default package manager instead of Yum, which only works with Python 2

* changes to isolated/leaf package without the impact on other packages/rest of the distribution Right now `fedora-obsoletes-package` retires packages which cause an issue during an upgrade. We do nothing abo

...It is also important to allow packagers to locally and manually invoke a ''test suite''. Each dist-git repo that has integration tests should package those tests in one or more subpackages

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

| name = Fedora Test Days | website = [[http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day Fedora Calendar]]

* changes to isolated/leaf package without the impact on other packages/rest of the distribution ...18. Next LTS is JDK15, expected in 2020. This proposal, is proposing new package - java-11-openjdk, based on this LTS OpenJDK 11, which will be tech preview

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...It is also important to allow packagers to locally and manually invoke a ''test suite''. ...ttps://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst DEP 8 specification].

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...lso important to allow Fedora packagers to locally and manually invoke a ''test suite''. ...playbooks in the <code>tests/</code> folder that can be invoked to run the test suites.

* changes to isolated/leaf package without the impact on other packages/rest of the distribution ...n the operating system and what the user has installed on top of it; if we package software as xdg-app bundles depending on a standard runtime or as Docker co

For example: This change allows package upgrades to be performed automatically and rolled-back at will. Does this improve some specific package or set of packages?