(Ready) |
m (Make some formatting changes) |
||
Line 1: | Line 1: | ||
= Set skip_if_unavailable default to false = | |||
== Summary == | == Summary == | ||
Dnf team wants to change a default setting for the repo option skip_if_unavailable to FALSE. | Dnf team wants to change a default setting for the repo option `skip_if_unavailable` to `FALSE`. | ||
== Owner == | == Owner == | ||
* Name: [[User:jmracek| Jaroslav Mracek]] | * Name: [[User:jmracek| Jaroslav Mracek]] | ||
* Email: jmracek@redhat.com | * Email: jmracek@redhat.com | ||
* Release notes owner: | * Release notes owner: | ||
== Current status == | == Current status == | ||
Line 64: | Line 25: | ||
== Detailed Description == | == Detailed Description == | ||
Dnf team wants to change a default setting for the repo option skip_if_unavailable to FALSE. The option is responsible for behavior when metadata of a repository is unavailable. When it is set to false, it will stop on the first unavailable repository with raising an error. The default behavior could be overwritten by a configuration of each repository or in dnf by configuration in /etc/dnf/dnf.conf. | Dnf team wants to change a default setting for the repo option `skip_if_unavailable` to `FALSE`. The option is responsible for behavior when metadata of a repository is unavailable. When it is set to false, it will stop on the first unavailable repository with raising an error. The default behavior could be overwritten by a configuration of each repository or in dnf by configuration in /etc/dnf/dnf.conf. | ||
The behavior is not new, because it was used already by YUM, and the behavior is really essential because all Fedora ropos are already shipped with skip_if_unavailable=FALSE. | The behavior is not new, because it was used already by YUM, and the behavior is really essential because all Fedora ropos are already shipped with `skip_if_unavailable=FALSE`. | ||
The change will be applied in libdnf library, and the changed behavior will be visible for all direct and indirect users of the library: dnf, microdnf, PackageKit, ... . | The change will be applied in libdnf library, and the changed behavior will be visible for all direct and indirect users of the library: dnf, microdnf, PackageKit, ... . | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
It should provide a better security because some Important updates from third-party repositories could be present in temporary unavailable repository, but user can easily overlook it during | It should provide a better security because some Important updates from third-party repositories could be present in temporary unavailable repository, but user can easily overlook it during `dnf update` because the issue is reported as a warning. | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** Backport the following upstream pull requests into the DNF stack on Fedora: https://github.com/rpm-software-management/libdnf/pull/701 | |||
Backport the following upstream pull requests into the DNF stack on Fedora: | |||
https://github.com/rpm-software-management/libdnf/pull/701 | |||
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Line 122: | Line 48: | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
* Policies and guidelines: N/A | * Policies and guidelines: N/A | ||
* Trademark approval: not needed for this Change | |||
* Trademark approval: | |||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == |
Revision as of 20:04, 18 April 2019
Summary
Dnf team wants to change a default setting for the repo option skip_if_unavailable
to FALSE
.
Owner
- Name: Jaroslav Mracek
- Email: jmracek@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 31
- Last updated: 2019-04-18
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Dnf team wants to change a default setting for the repo option skip_if_unavailable
to FALSE
. The option is responsible for behavior when metadata of a repository is unavailable. When it is set to false, it will stop on the first unavailable repository with raising an error. The default behavior could be overwritten by a configuration of each repository or in dnf by configuration in /etc/dnf/dnf.conf.
The behavior is not new, because it was used already by YUM, and the behavior is really essential because all Fedora ropos are already shipped with skip_if_unavailable=FALSE
.
The change will be applied in libdnf library, and the changed behavior will be visible for all direct and indirect users of the library: dnf, microdnf, PackageKit, ... .
Benefit to Fedora
It should provide a better security because some Important updates from third-party repositories could be present in temporary unavailable repository, but user can easily overlook it during dnf update
because the issue is reported as a warning.
Scope
- Proposal owners:
- Backport the following upstream pull requests into the DNF stack on Fedora: https://github.com/rpm-software-management/libdnf/pull/701
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A
- Trademark approval: not needed for this Change
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
Broken repositories are recognized early, enabling the users to act upon them by double-checking their repository configuration or filing bugs, instead of assuming no upgrades are available.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)