The last few days I have done some upgrade testing in Debian, to @@ -14,7 +14,7 @@ am working on a script to automate the test.
The idea is to create a Lenny chroot and use tasksel to install a Gnome or KDE desktop installation inside the chroot before upgrading it. To ensure no services are started in the chroot, a policy-rc.d -script is inserted. To make sure tasksel believe it to install a +script is inserted. To make sure tasksel believe it is to install a desktop on a laptop, the tasksel tests are replaced in the chroot (only acceptable because this is a throw-away chroot).
@@ -107,13 +107,13 @@ regularly and post the result on the web. The Gnome upgrade currently work, while the KDE upgrade fail because of the bug in kdebase-workspace-data -I am not quite sure what kind of extract from the huge upgrade log -it make sense to include in this blog post, so I will refrain from -trying. I can report that for Gnome, aptitude report 760 packages -upgraded, 448 newly installed, 129 to remove and 1 not upgraded and -1024MB need to be downloaded while for KDE the same numbers are 702 -packages upgraded, 507 newly installed, 193 to remove and 0 not -upgraded and 1117MB need to be downloaded
+I am not quite sure what kind of extract from the huge upgrade logs +(KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog +post, so I will refrain from trying. I can report that for Gnome, +aptitude report 760 packages upgraded, 448 newly installed, 129 to +remove and 1 not upgraded and 1024MB need to be downloaded while for +KDE the same numbers are 702 packages upgraded, 507 newly installed, +193 to remove and 0 not upgraded and 1117MB need to be downloaded
I am very happy to notice that the Gnome desktop + laptop upgrade is able to migrate to dependency based boot sequencing and parallel