Re: Out of date upgrade-reports page

[Luk Claes]

Noah Meyerhans wrote:
> (resurrecting this thread...)
> 
> On Sun, Jan 07, 2007 at 06:33:14PM +0100, Luk Claes wrote:
> 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
>>>
>> ...
>>> 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)
>> Patch committed.
> 
> The page still contains at least two references to woody. See attached
> proposed patch.

I removed the references to woody, I'm not convinced about the other proposed
changes, so didn't apply them.

> Is that page intended to be used as a template while etch is still
> "testing", or after the etch release when people are upgrading from
> oldstable to stable?  If the latter, then it should also be updated to
> refer to the latest stable release notes, rather than
> http://www.debian.org/releases/testing/releasenotes  (I can see how
> one might argue that we no longer need the upgrade reports after etch
> is released, but I don't know that I agree.)

It's always possible to change the template after release ;-)

Cheers

Luk

-- 
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint:   D5AF 25FB 316B 53BB 08E7   F999 E544 DE07 9B7C 328D



signature.asc
Description: OpenPGP digital signature

Re: Out of date upgrade-reports page

[Noah Meyerhans]

(resurrecting this thread...)

On Sun, Jan 07, 2007 at 06:33:14PM +0100, Luk Claes wrote:
> >>> 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
> > 
> ...
> > 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)
> 
> Patch committed.

The page still contains at least two references to woody. See attached
proposed patch.

Is that page intended to be used as a template while etch is still
"testing", or after the etch release when people are upgrading from
oldstable to stable?  If the latter, then it should also be updated to
refer to the latest stable release notes, rather than
http://www.debian.org/releases/testing/releasenotes  (I can see how
one might argue that we no longer need the upgrade reports after etch
is released, but I don't know that I agree.)

noah


--- /org/release.debian.org/www/upgrade-report.html 2007-01-07 
10:30:24.0 -0700
+++ upgrade-report.html 2007-02-14 15:39:31.0 -0700
@@ -23,10 +23,10 @@
 href="http://www.debian.org/releases/testing/releasenotes";>release
 notes 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 old stable release you should read the release notes for
+an old (pre-sarge) 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.
+stable release to the latest stable release.

 It is extremely recommended that you use the
 /usr/bin/script program to record a transcript of the upgrade session.
@@ -55,8 +55,8 @@
 - Were there any non-Debian packages installed before the upgrade?  If
   so, what were they?

-- Was the system pre-update a pure woody system? If not, which packages
-  were not from woody?
+- Was the system pre-update a pure sarge system? If not, which packages
+  were not from sarge?

 - Did any packages fail to upgrade?



signature.asc
Description: Digital signature

Re: Out of date upgrade-reports page

[Luk Claes]

Javier Fernández-Sanguino Peña wrote:
> 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
> 
...
> 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)

Patch committed.

Cheers

Luk

-- 
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint:   D5AF 25FB 316B 53BB 08E7   F999 E544 DE07 9B7C 328D



signature.asc
Description: OpenPGP digital signature

Re: Out of date upgrade-reports page

[Javier Fernández-Sanguino Peña]

On Thu, Jan 04, 2007 at 04:49:50PM +0100, Javier Fernández-Sanguino Peña wrote:
> 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)

Could someone (in the release tema) please either upload my patch or fix this
some other way?

Regards

Javier


signature.asc
Description: Digital signature

Re: Out of date upgrade-reports page

[Javier Fernández-Sanguino Peña]

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/msg4.html
[2] http://bugs.debian.org/upgrade-reports
--- upgrade-report.html.orig	2007-01-04 16:39:08.0 +0100
+++ upgrade-report.html	2007-01-04 16:47:05.0 +0100
@@ -9,30 +9,44 @@
 
 
 
-Reports on upgrading from woody to sarge
+Reports on upgrading between Debian releases
 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 [EMAIL PROTECTED].
+by sending it to [EMAIL PROTECTED].  You can also use the reportbug tool to submit your
+reports.
 
 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.
 
 Consider reading the http://www.debian.org/releases/sarge/releasenotes";>release
-notes for sarge before upgrading.  They contain useful hints how to
-do the upgrade and information about known problems.
-
+href="http://www.debian.org/releases/testing/releasenotes";>release
+notes 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 old 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.
+
+It is extremely recommended that you use the
+/usr/bin/script 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
 
 
 
 Package: upgrade-reports
+Version: N/A
+Severity: 
 
+My previous release is: 
+I am upgrading to: 
 Archive date: 
-Upgrade date: 
-uname -a: 
+Upgrade date: 
+uname -a before upgrade: 
+uname -a after upgrade: 
 Method: 
 
 Contents of /etc/apt/sources.list:


signature.asc
Description: Digital signature

Re: Out of date upgrade-reports page

[Roberto C. Sanchez]

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
> > 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?
> 
I am not sure.  I Google searched, but could not find one, which is why
I added "(if one such page does exist)" at the end.  If one doesn't,
one of the release team members could probably just update with
information relevant to the Sarge -> Etch upgrade.

Regards,

-Roberto

-- 
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: Out of date upgrade-reports page

[Andreas Barth]

* 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
> 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?

Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Out of date upgrade-reports page

[Roberto C. Sanchez]

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
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).

Regards,

-Roberto

[0] http://release.debian.org/upgrade-report.html

-- 
Roberto C. Sanchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature