Differences between revisions 3 and 4
Revision 3 as of 2009-02-18 23:17:58
Size: 3578
Editor: FranklinPiat
Comment: rewrite
Revision 4 as of 2009-03-16 03:33:51
Size: 3590
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||<tablestyle="width: 100%;" style="border: 0px hidden">~-[:DebianWiki/EditorGuide#translation:Translation(s)]: none-~||<style="text-align: right;border: 0px hidden"> (!) [:/Discussion:Discussion]|| ||<tablestyle="width: 100%;" style="border: 0px hidden">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: none-~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]||
Line 16: Line 16:
 1. Test the system after the upgrade, then display hints for emulating a freshly installed system. See section "Preparing for the next release" of the Release-Notes (like lenny/i386 [http://www.debian.org/releases/lenny/i386/release-notes/ch-upgrading.html#for-next notes]).  1. Test the system after the upgrade, then display hints for emulating a freshly installed system. See section "Preparing for the next release" of the Release-Notes (like lenny/i386 [[http://www.debian.org/releases/lenny/i386/release-notes/ch-upgrading.html#for-next|notes]]).
Line 18: Line 18:
{{{}}} (!) This tool is complementary to the [http://www.debian.org/releases/lenny/releasenotes Releases-Notes], not a replacement. Also, the output should reviewed with care as it may contain false-negative and/or false-positive warning. {{{}}} (!) This tool is complementary to the [[http://www.debian.org/releases/lenny/releasenotes|Releases-Notes]], not a replacement. Also, the output should reviewed with care as it may contain false-negative and/or false-positive warning.
Line 67: Line 67:
 * {{{Vcs-Browser:}}} [http://git.debian.org/?p=collab-maint/upgrade-advisor.git]  * {{{Vcs-Browser:}}} [[http://git.debian.org/?p=collab-maint/upgrade-advisor.git]]
Line 74: Line 74:
  * Lenny [http://www.debian.org/releases/lenny/releasenotes]
  * Etch [http://www.debian.org/releases/etch/releasenotes]
  * Lenny [[http://www.debian.org/releases/lenny/releasenotes]]
  * Etch [[http://www.debian.org/releases/etch/releasenotes]]

Translation(s): none

(!) ?Discussion


This is the homepage of upgrade-advisor.

Introduction to upgrade-advisor

Running upgrade-advisor pre-upgrade will:

  1. Report post-upgrade recommendations from a previous upgrade (from previous release to current release).
  2. Test the system prior to the upgrade, then display some hints to ensure seamless upgrade.

Running upgrade-advisor post-upgrade will:

  1. Test the system after the upgrade, then display hints for emulating a freshly installed system. See section "Preparing for the next release" of the Release-Notes (like lenny/i386 notes).

(!) This tool is complementary to the Releases-Notes, not a replacement. Also, the output should reviewed with care as it may contain false-negative and/or false-positive warning.

Contributing

Contributing a plug-in

You can contribute a plug-in, that warns users before they upgrade their systems.

Here's a sample plugin :

check_update_grub_path() {
    [ $CURRENT_OS -lt $ETCH ] && return 0
    title "Checking update-grub path in /etc/kernel-img.conf"

    if grep -E "[[:blank:]=]+/sbin/update-grub" \
           /etc/kernel-img.conf > /dev/null 2>&1; then
        gecho "The path to update-grub in /etc/kernel-img.conf is wrong." | alert
        gecho "$RELNOTES/ch-upgrading.en.html#s-for_next" | extra
    fi
}

  • If you are the maintainer of a package, you can commit your plug-in directly to the git repository.
  • Otherwise, it is best to discuss before commiting it (send a mail to the maintainer).

Get the source

    sudo apt-get install git-core
    git clone git://git.debian.org/git/collab-maint/upgrade-advisor.git

    #You don't have to build the package to test it:
    ./upgrade-advisor/upgrade-advisor pre-upgrade

Bugs and feedback

Feedback for false positive and false negative is especially welcome.

Status:

  • Upgrade advisor is currently in development. You are welcome to test it and report bugs and wishlist (with patch?).

See also