On Sun, Dec 24, 2006 at 10:48:52AM +0100, Andreas Barth wrote: > * Roberto C. Sanchez ([EMAIL PROTECTED]) [061224 02:10]: > > A Google search for "debian upgrade reports" (no quotes) returns a page > > [0] that is out of date since it is a template for a woody -> sarge
--> [0] is http://release.debian.org/upgrade-report.html > > upgrade. I would like to recommend that it either be updated or > > replaced with a redirection to a more current page (if one such page > > does exist). > > And recommendation which new page to choose for this? It looks like no upgrade report template has been written for Etch. The Release Managers (well, Steve) have asked [1] to submit upgrade reports as bugs to the 'upgrade-reports' virtual package [2] but no template has been provided. I'm not sure who manages release.debian.org (a virtual host in gluck's), but it's contents are certainly not writable by the members of the web group (webwml) but by the 'debian-release' group. That being said, attached is a patch to the current upgrade-report.html page to add additional information (and do not make it depend on a specific Debian release). I think it's worthwhile mentioning that the user's should use script if they want to provide accurate information (the Release Notes already say this, but stressing this here too might lead to more useful bug reports) Regards Javier [1] http://lists.debian.org/debian-devel-announce/2006/11/msg00004.html [2] http://bugs.debian.org/upgrade-reports
--- upgrade-report.html.orig 2007-01-04 16:39:08.000000000 +0100 +++ upgrade-report.html 2007-01-04 16:47:05.000000000 +0100 @@ -9,30 +9,44 @@ <body> <div id="outer"> <div id="inner"> -<h1 align="center">Reports on upgrading from woody to sarge</h1> +<h1 align="center">Reports on upgrading between Debian releases</h1> <p>Please use this template when filling out upgrade reports, and file the report as a bug report against the "upgrade-reports" pseudo package, -by sending it to <a -href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>.</p> +by sending it to <a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>. You can also use the <em>reportbug</em> tool to submit your +reports.</p> <p>We also encourage all successful upgrade reports to be sent using this template so that we can get as much information as possible on the largest number of configurations.</p> <p>Consider reading the <a -href="http://www.debian.org/releases/sarge/releasenotes";>release -notes</a> for sarge before upgrading. They contain useful hints how to -do the upgrade and information about known problems.</p> - +href="http://www.debian.org/releases/testing/releasenotes";>release +notes</a> for the latest testing release before upgrading. They contain useful hints how to +do the upgrade and information about known problems. If you are upgrading from +an <em>old</em> stable release you should read the release notes for +all the stable releases between your release and the release you are +upgrading to. Release notes will only cover upgrades from the previous +release to the latest release.</p> + +<p>It is <strong>extremely</strong> recommended that you use the +<em>/usr/bin/script</em> program to record a transcript of the upgrade session. +If you used it, please provide the full typescript (compressed) attached to the +bug report. You fill find information on how to use that program in the +release notes</p> <hr> <pre> Package: upgrade-reports +Version: N/A +Severity: <the severity for this bug> +My previous release is: <codename or version of the release you are upgrading from> +I am upgrading to: <codename or version of the release you are upgrading to> Archive date: <Timestamp, available as project/trace/ftp-master.debian.org on your mirror or .disk/info on your CD/DVD set> -Upgrade date: <Date and time of install> -uname -a: <The result of running uname -a on a shell prompt> +Upgrade date: <Date and time of the upgrade> +uname -a before upgrade: <The result of running uname -a on a shell prompt> +uname -a after upgrade: <The result of running uname -a on a shell prompt> Method: <How did you upgrade? Which program did you use?> Contents of /etc/apt/sources.list:
signature.asc
Description: Digital signature
