= Proposed Self Contained: Preupgrade Assistant = https://fedoraproject.org/wiki/Changes/Preupgrade_Assistant
Change owner(s): Petr Hracek phracek@redhat.com
The Preugrade Assistant is a tool to help people upgrade from one release to another and be sure to track important manual configuration changes they performed.
== Detailed Description == The idea behind the The Preupgrade Assistant came from the notion that even during the rather short release cycles in Fedora occasionally there are changes that are incompatible between releases and which are either hard or nearly impossible to cover during a standard package upgrade. Examples would be major version upgrades of applications or services that change configuration file syntax or on-disk date format changes.
The Preupgrade Assistant works by analyzing the source system and will generate a report which will offer information and configuration files for typically changed settings and services. It offers a plugin architecture where component or functional area owners can contribute and write their on plugins in python, bash or perl that can generate additional information for the report.
== Scope == The Preupgrade Assistant is a standalone tool that doesn't affect any other component in the system. The scope for Fedora 22 is to provide the basic framework and initial plugins for general use. Additional component or functional area plugins rely on component owners to actively help working on them.
* Proposal owners: Provide the basic framework and initial plugins for general use * Other developers: Provide additional component or functional area plugins (optional) * Release engineering: N/A (not a System Wide Change) * Policies and guidelines: N/A (not a System Wide Change) _______________________________________________ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
On Thu, Dec 11, 2014 at 15:06:25 +0100, Jaroslav Reznik jreznik@redhat.com wrote:
= Proposed Self Contained: Preupgrade Assistant = https://fedoraproject.org/wiki/Changes/Preupgrade_Assistant
Change owner(s): Petr Hracek phracek@redhat.com
The Preugrade Assistant is a tool to help people upgrade from one release to another and be sure to track important manual configuration changes they performed.
Will this handle packages that have been dropped but not obsoleted in the next release?
On 12/11/2014 05:17 PM, Bruno Wolff III wrote:
On Thu, Dec 11, 2014 at 15:06:25 +0100, Jaroslav Reznik jreznik@redhat.com wrote:
= Proposed Self Contained: Preupgrade Assistant = https://fedoraproject.org/wiki/Changes/Preupgrade_Assistant
Change owner(s): Petr Hracek phracek@redhat.com
The Preugrade Assistant is a tool to help people upgrade from one release to another and be sure to track important manual configuration changes they performed.
Will this handle packages that have been dropped but not obsoleted in the next release?
Yes definitely. The tool or respectively contents (which are part of this tool) can be used for informing user that some package has been dropped and how to replace them. User should provide a steps how to do that.
E.g. In F22 is dropped package A and in F23 it is going to replaced with package B. A content informs user in F22 that package does not exist anymore and it is going to replaced with package B from F23.
I am going to extend the wiki with preupgrade-assistant soon.
On 2014-12-12, Petr Hracek phracek@redhat.com wrote:
On 12/11/2014 05:17 PM, Bruno Wolff III wrote:
Will this handle packages that have been dropped but not obsoleted in the next release?
Yes definitely. The tool or respectively contents (which are part of this tool) can be used for informing user that some package has been dropped and how to replace them. User should provide a steps how to do that.
E.g. In F22 is dropped package A and in F23 it is going to replaced with package B. A content informs user in F22 that package does not exist anymore and it is going to replaced with package B from F23.
I think the question was about packages without replacement.
E.g. a package provided in F22 is not distributed with F23 anymore but no F23 package provides or obseletes the F22 package name. (Because there is simply no functional replacement, e.g. the package was dropped because of lack of maintanance.)
Such non-upgraded package can cause dependency breakage because it can require an RPM symbol which is not available in the newer Fedora (e.g. a soname which has changed).
Actually Fedora lacks any systematic approach to this problem. I'm not sure whether "yum distro-sync" or fedup removes such packages, but I know some users complained about it.
-- Petr
On 12/12/2014 10:01 AM, Petr Pisar wrote:
On 2014-12-12, Petr Hracek phracek@redhat.com wrote:
On 12/11/2014 05:17 PM, Bruno Wolff III wrote:
Will this handle packages that have been dropped but not obsoleted in the next release?
Yes definitely. The tool or respectively contents (which are part of this tool) can be used for informing user that some package has been dropped and how to replace them. User should provide a steps how to do that.
E.g. In F22 is dropped package A and in F23 it is going to replaced with package B. A content informs user in F22 that package does not exist anymore and it is going to replaced with package B from F23.
I think the question was about packages without replacement.
E.g. a package provided in F22 is not distributed with F23 anymore but no F23 package provides or obseletes the F22 package name. (Because there is simply no functional replacement, e.g. the package was dropped because of lack of maintanance.)
Such non-upgraded package can cause dependency breakage because it can require an RPM symbol which is not available in the newer Fedora (e.g. a soname which has changed).
Actually Fedora lacks any systematic approach to this problem. I'm not sure whether "yum distro-sync" or fedup removes such packages, but I know some users complained about it.
-- Petr
I think that it can be solved together with FedUp tool. This is a bit tricky. This can be removed either before or after an upgrade with --force option. Currently now preupgrade-assistant reports to users risks and what he/she should do with system. The aim of preupgrade-assistant is to help user with upgrades and this task (like obsolete packages) is one part.
This has to be discussed with FedUp maintainer definitelly if we want to upgrade Fedora successful. I know that Fedora can be upgrade properly but If users have e.g. database and wants to upgrade them then It would be good to provide the steps for successful upgrade.
On 12/11/2014 03:06 PM, Jaroslav Reznik wrote:
= Proposed Self Contained: Preupgrade Assistant = https://fedoraproject.org/wiki/Changes/Preupgrade_Assistant
Change owner(s): Petr Hracek phracek@redhat.com
The Preugrade Assistant is a tool to help people upgrade from one release to another and be sure to track important manual configuration changes they performed.
I wish self contained features would provided frequently updated Copr repository. To test/contribute to this feature before merged to Fedora.
On 12/15/2014 09:18 AM, Miroslav Suchý wrote:
On 12/11/2014 03:06 PM, Jaroslav Reznik wrote:
= Proposed Self Contained: Preupgrade Assistant = https://fedoraproject.org/wiki/Changes/Preupgrade_Assistant
Change owner(s): Petr Hracek phracek@redhat.com
The Preugrade Assistant is a tool to help people upgrade from one release to another and be sure to track important manual configuration changes they performed.
I wish self contained features would provided frequently updated Copr repository. To test/contribute to this feature before merged to Fedora.
Great point. I will do that.
-
Bruno Wolff III -
Jaroslav Reznik -
Miroslav Suchý -
Petr Hracek -
Petr Pisar