Bug#861620: marked as done (release-notes: some global reviewing)
Your message dated Fri, 09 Jun 2017 23:03:00 +0000
with message-id <firstname.lastname@example.org>
and subject line Re: Bug#861620: release-notes: some global reviewing
has caused the Debian Bug report #861620,
regarding release-notes: some global reviewing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact email@example.com
Debian Bug Tracking System
Contact firstname.lastname@example.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <email@example.com>
- Subject: release-notes: some global reviewing
- From: Holger Wansing <firstname.lastname@example.org>
- Date: Mon, 1 May 2017 19:28:32 +0200
- Message-id: <email@example.com>
While reviewing the german translation of the release-notes, I found some
glitches in the english original as well:
chapter 2.2: what's new: software updates
the table mentions MySQL as "being upgraded", while the version in
Stretch is "removed".
So MySQL has to be deleted from this table.
chapter 4.4.5: upgrading the system
here installation of CDs is used several times. Should be changed
into CD/DVD/BD (and from there on use simply "disc").
chapter 5.1.4: Deprecated components for Stretch
"Users will need to migrate to other alternatives to prevent trouble when updating to 10."
Should better read "when updating to Debian 10" at the end.
appendix A.2: Checking your sources list
About checking the sources.list before (!) upgrading to Stretch, this contains:
"If any of the lines in your /etc/apt/sources.list refer to 'stable', you
are effectively already “using” stretch."
I think, this can hardly be misunderstood as "The upgrade to stretch is
already completed on my machine", at least from beginners.
My proposal would be:
"If any of the lines in your /etc/apt/sources.list refer to 'stable',
it effectively points to Stretch already."
Additionally, this chapter mentions lines with
in sources.list, which should be changed from stable to jessie.
I propose to add a note like:
"Lines in sources.list starting with "deb ftp:" and pointing to
debian.org addresses have to be changed into "deb http:" lines.
See <chapter about ftp services shutdown>.
I have prepared a patch for all the above.
Created with Sylpheed 3.5.0 under
D E B I A N L I N U X 8 . 0 " J E S S I E " .
Registered Linux User #311290 - https://linuxcounter.net/
--- en/issues.dbk (Revision 11482)
+++ en/issues.dbk (Arbeitskopie)
@@ -124,7 +124,7 @@
With the next release of &debian; &nextrelease; (codenamed
&Nextreleasename;) some features will be deprecated. Users
will need to migrate to other alternatives to prevent
- trouble when updating to &nextrelease;.
+ trouble when updating to &debian; &nextrelease;.
This includes the following features:
--- en/old-stuff.dbk (Revision 11482)
+++ en/old-stuff.dbk (Arbeitskopie)
@@ -30,7 +30,7 @@
<title>Checking your sources list</title>
If any of the lines in your <filename>/etc/apt/sources.list</filename> refer to
-'stable', you are effectively already <quote>using</quote> &releasename;. This
+'stable', it effectively points to &releasename; already. This
might not be what you want if you are not ready yet for the upgrade. If
you have already run
<literal>apt-get update</literal>, you can still get back without problems
@@ -49,6 +49,13 @@
<quote><literal>stable</literal></quote>. If you find any, change
<literal>stable</literal> to <literal>&oldreleasename;</literal>.
+ Lines in sources.list starting with "deb ftp:" and pointing to debian.org
+ addresses should be changed into "deb http:" lines.
+ See <xref linkend="deprecation-of-ftp-apt-mirrors" />.
If you have any lines starting with <literal>deb file:</literal>, you will have
to check for yourself if the location they refer to contains an
--- en/upgrading.dbk (Revision 11482)
+++ en/upgrading.dbk (Arbeitskopie)
@@ -963,10 +963,10 @@
conflicting obsoleted packages.
-When upgrading from a set of CD-ROMs (or DVDs), you will be asked to insert specific CDs
-at several points during the upgrade. You might have to insert the same CD
+When upgrading from a set of CDs/DVDs/BDs, you will probably be asked to insert specific discs
+at several points during the upgrade. You might have to insert the same disc
multiple times; this is due to inter-related packages that have been spread out
-over the CDs.
+over the discs.
New versions of currently installed packages that cannot be upgraded without
--- en/whats-new.dbk (Revision 11482)
+++ en/whats-new.dbk (Arbeitskopie)
@@ -309,11 +309,6 @@
- <row id="new-mysql">
--- End Message ---
--- Begin Message ---
- To: firstname.lastname@example.org
- Subject: Re: Bug#861620: release-notes: some global reviewing
- From: Niels Thykier <email@example.com>
- Date: Fri, 09 Jun 2017 23:03:00 +0000
- Message-id: <firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
On Mon, 1 May 2017 22:00:02 +0200 Baptiste Jammet <email@example.com>
> Dixit Holger Wansing, le 01/05/2017Â :
> >While reviewing the german translation of the release-notes, I found
> >some glitches in the english original as well:
> >I have prepared a patch for all the above.
> (OK for me)
Applied the patch.
> We should also keep in sync the two sentences about LSB:
> 2.2 What's new
> Debian supports Linux Standard Base (LSB) version 4.1, with one
> Â Â Â explicit and Debian-specific derogation from the LSB 4.1
> specification: Qt3 is not included.
> and later:
> 5.1.7.Â Most LSB compatibility packages have been removed
> Maybe just drop the 2.2 part?
Agreed, I have dropped the 2.2 part.
--- End Message ---