From Fedora Project Wiki
(https://fedorahosted.org/fesco/ticket/1628)
m (Change status or related components to dnf)
 
(15 intermediate revisions by 3 users not shown)
Line 57: Line 57:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1377324 #1377324]


== Detailed Description ==
== Detailed Description ==
Line 65: Line 65:
== Benefit to Fedora ==
== Benefit to Fedora ==


New major version of DNF brings many new features and bug fixes. Moreover, the support period of older versions is reaching its end.
DNF-2 is the upstream DNF version, the only version actively developed. Currently the upstream contains many user requested features, increased compatibility with yum and over 30 bug fixes. To DNF-1 back porting of patches from upstream is difficult and only critical security and usability fixes will be cherry-picked to Fedora.


== Scope ==
== Scope ==
Line 78: Line 78:


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
Enduser compatibility should be preserved as much as possible. We do not expect any manual user intervention.  
Plugins based on DNF-1 providing commands will abort run of DNF. Any Python script or extension using 5 changed methods in DNF-2 will not work correctly. Components using DNF private Python functions could experience some issues. User or applications calling DNF CLI API can experience differences if any of 2 changed options were used. The code changes are needed for applications affected by mentioned changes. For main applications requiring DNF the patches were provided.
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


== How To Test ==
== How To Test ==
* early adopters are welcomed to use [https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/dnf-nightly/ this COPR repo] for testing
* you can install DNF-2 from [https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/dnf-nightly/ this COPR repo] for testing
* testing scenarios:
* testing scenarios:
** anaconda installation
** anaconda installation
Line 89: Line 89:
** dnf-plugins: copr, system-upgrade, download
** dnf-plugins: copr, system-upgrade, download
** third party software: mock, yumex
** third party software: mock, yumex
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  


Line 107: Line 106:
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (unaffected)
 
Users can notice usability improvements of DNF like better messages during resolution errors, showing whether package was installed as weak dependency, better handling of obsolete packages, less tracebacks, etc. One command line option and one configuration option changed semantic so DNF could behave differently in some way (these changes are compatible with yum but incompatible with DNF-1). See "Upgrade/compatibility impact" section when DNF could crash if components are not adjusted to DNF-2 changes.


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
Table showing all packages which requires dnf, python3-dnf or python2-dnf in Fedora 26:
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
 
== Contingency Plan ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism:
** revert to DNF-1.1.x (epoch bump)
** revert to dnf-plugins-core-0.1.x (epoch bump)
** revert to dnf-plugins-extras-0.0.x (epoch bump)
** revert to dnf-plugin-system-upgrade-0.7.x (epoch bump)
** consequent rollback of already ported components
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: F26 Alpha Freeze  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? Yes
 
== Documentation ==
[http://dnf.readthedocs.io/en/latest/dnf-1_vs_dnf-2.html documented differences between 1.x and 2.0]
 
== Packages that requires dnf, python3-dnf or python2-dnf in Fedora 24 ==
{| class="wikitable sortable"
{| class="wikitable sortable"
! Package !! DNF-2.0 compatibility patch !! Status  
! Package !! DNF-2.0 compatibility patch !! Status  
Line 140: Line 118:
|-
|-


| auter || || Not informed
| auter || || Informed
|-
|-


| calamares || || Not informed
| calamares || || Informed
|-
|-


| copr-frontend || || Not informed
| copr-frontend || || Informedd
|-
|-


| devassistant-core || || Not informed
| devassistant-core || || Informed
|-
|-


| dnf-automatic || In upstream || Compatible
| dnf-automatic || In the upstream || Compatible
|-
|-


| dnf-plugin-spacewalk || || Not informed
| dnf-plugin-spacewalk || || Informed
|-
|-


| dnf-plugin-subscription-manager || || Not informed
| dnf-plugin-subscription-manager || || Informed
|-
|-


| dnf-plugin-system-upgrade || Patch will be provided by DNF team || In progress
| dnf-plugin-system-upgrade || https://github.com/rpm-software-management/dnf-plugins-extras/pull/66 || In progress
|-
|-


| dnf-yum || In upstream || Compatible
| dnf-plugins-core || In the upstream || working with DNF-2
|-
|-


| dnfdaemon || https://github.com/timlau/dnf-daemon/pull/6 || Merged
| dnf-plugins-extras || In the upstream || working with DNF-2
|-
|-


| etckeeper-dnf || || Not informed
| dnf-yum || In the upstream || Compatible
|-
|-


| fedora-upgrade || || Not informed
| dnfdaemon || https://github.com/timlau/dnf-daemon/pull/6 || working with DNF-2
|-
|-


| fontpackages-tools || || Not informed
| etckeeper-dnf || || Informed
|-
|-


| freight-tools || || Not informed
| fedora-upgrade || || Informed
|-
|-


| freight-tools-agent || || Not informed
| freight-tools || || Informed
|-
|-


| freight-tools-proxy || || Not informed
| freight-tools-agent || || Informed
|-
|-


| libreport-python || || Not informed
| freight-tools-proxy || || Informed
|-
|-


| libreport-python3 || || Not informed
| libreport-python || || Informed
|-
|-


| libtaskotron-fedora || || Not informed
| libreport-python3 || || Informed
|-
|-


| lorax || || Not informed
| libtaskotron-fedora || || Informed
|-
|-


| policycoreutils-devel || || Not informed
| lorax || || Informed
|-
|-


| python-dnf-langpacks || || Retired in Fc25
| policycoreutils-devel || || Informed
|-
|-


| python3-dnf-langpacks || || Retired in Fc25
| python3-dnf-plugin-system-upgrade || https://github.com/rpm-software-management/dnf-plugins-extras/pull/66 || In progress
|-
|-


| python3-dnf-plugin-system-upgrade || Patch will be provided by DNF team || In progress
| rhn-client-tools || || Informed
|-
|-


| rhn-client-tools || || Not informed
| rolekit || || Informed
|-
|-


| rolekit || || Not informed
| supermin || || Informed
|-
|-


| supermin || || Not informed
| system-config-language || || Informed
|-
|}
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
 
== Contingency Plan ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism:
** revert to DNF-1.1.x (epoch bump)
** revert to dnf-plugins-core-0.1.x (epoch bump)
** revert to dnf-plugins-extras-0.0.x (epoch bump)
** revert to dnf-plugin-system-upgrade-0.7.x (epoch bump)
** consequent rollback of already ported components in the table where the change for dnf-2.0 was needed
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: F26 Alpha Freeze  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? Yes


| system-config-language || || Not informed
== Documentation ==
|}
[http://dnf.readthedocs.io/en/latest/dnf-1_vs_dnf-2.html documented differences between 1.x and 2.0]


== Release Notes ==
== Release Notes ==
Line 231: Line 224:
-->
-->


[[Category:ChangeReadyForFesco]]
[[Category:ChangeAcceptedF26]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 15:19, 22 November 2016


DNF 2.0

Summary

DNF rebase to version 2.0.

Owner

Current status

Detailed Description

DNF-2.0 is the next upcoming major version of DNF package manager. Unfortunately, it brings some incompatibilities with previous version of DNF (DNF-1) which were either needed to preserve compatibility with YUM CLI or where bigger redesigns were needed. A list of identified incompatible changes can be found here[1].

Benefit to Fedora

DNF-2 is the upstream DNF version, the only version actively developed. Currently the upstream contains many user requested features, increased compatibility with yum and over 30 bug fixes. To DNF-1 back porting of patches from upstream is difficult and only critical security and usability fixes will be cherry-picked to Fedora.

Scope

  • Proposal owners:
    • complete release notes 
    • deliver DNF-2.0 stack to Rawhide
  • Other developers:
    • Owners of 3rd party DNF plugins or components depending on DNF should check and adjust their packages otherwise they may not work with DNF-2.0.
  • Release engineering:
    • All release engineering tools that depends on DNF should be tested against DNF-2.0.

Upgrade/compatibility impact

Plugins based on DNF-1 providing commands will abort run of DNF. Any Python script or extension using 5 changed methods in DNF-2 will not work correctly. Components using DNF private Python functions could experience some issues. User or applications calling DNF CLI API can experience differences if any of 2 changed options were used. The code changes are needed for applications affected by mentioned changes. For main applications requiring DNF the patches were provided.

How To Test

  • you can install DNF-2 from this COPR repo for testing
  • testing scenarios:
    • anaconda installation
    •  upgrade from previous Fedora version
    • core functionality: install, upgrade, remove, repoquery
    •  dnf-plugins: copr, system-upgrade, download
    • third party software: mock, yumex

User Experience

Users can notice usability improvements of DNF like better messages during resolution errors, showing whether package was installed as weak dependency, better handling of obsolete packages, less tracebacks, etc. One command line option and one configuration option changed semantic so DNF could behave differently in some way (these changes are compatible with yum but incompatible with DNF-1). See "Upgrade/compatibility impact" section when DNF could crash if components are not adjusted to DNF-2 changes.

Dependencies

Table showing all packages which requires dnf, python3-dnf or python2-dnf in Fedora 26:

Package DNF-2.0 compatibility patch Status
anaconda-core https://github.com/rhinstaller/anaconda/pull/763 Agreed to merge after DNF release
auter Informed
calamares Informed
copr-frontend Informedd
devassistant-core Informed
dnf-automatic In the upstream Compatible
dnf-plugin-spacewalk Informed
dnf-plugin-subscription-manager Informed
dnf-plugin-system-upgrade https://github.com/rpm-software-management/dnf-plugins-extras/pull/66 In progress
dnf-plugins-core In the upstream working with DNF-2
dnf-plugins-extras In the upstream working with DNF-2
dnf-yum In the upstream Compatible
dnfdaemon https://github.com/timlau/dnf-daemon/pull/6 working with DNF-2
etckeeper-dnf Informed
fedora-upgrade Informed
freight-tools Informed
freight-tools-agent Informed
freight-tools-proxy Informed
libreport-python Informed
libreport-python3 Informed
libtaskotron-fedora Informed
lorax Informed
policycoreutils-devel Informed
python3-dnf-plugin-system-upgrade https://github.com/rpm-software-management/dnf-plugins-extras/pull/66 In progress
rhn-client-tools Informed
rolekit Informed
supermin Informed
system-config-language Informed

Contingency Plan

  • Contingency mechanism:
    • revert to DNF-1.1.x (epoch bump)
    • revert to dnf-plugins-core-0.1.x (epoch bump)
    • revert to dnf-plugins-extras-0.0.x (epoch bump)
    • revert to dnf-plugin-system-upgrade-0.7.x (epoch bump)
    • consequent rollback of already ported components in the table where the change for dnf-2.0 was needed
  • Contingency deadline: F26 Alpha Freeze
  • Blocks release? Yes

Documentation

documented differences between 1.x and 2.0

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/DNF-2.0&oldid=480718"