Christian PERRIER wrote:
> I suspect the patch might benefit from a quick review.
>> <para>
>> The next time you run <command>apt-get update</command>, the
>> system will become aware of the packages in the
>> - <literal>&releasename;-backports</literal> section and will consider
>> them
>> - when looking for packages to upgrade.
>> + <literal>&releasename;-backports</literal> section. Note however that
>> by default newer
>> + versions of packages will not be installed, only new updates to
>> backported versions.
>> </para>
Er, yeah, that's confusing - especially if you read "updates to
backported versions" as meaning "updates switching to backported
versions". Maybe:
The next time you run <command>apt-get update</command>, the
system will become aware of the packages in the
<literal>&releasename;-backports</literal> section. Note however that
by default newer versions from this section will only be installed to
update packages that are already using backports.
But this is really hard to summarise clearly and concisely, and it
isn't news, so I'm not sure we need to spell it all out here.
Couldn't we avoid the misleading implication some easier way?
The next time you run <command>apt-get update</command>, the
system will become aware of the packages in the
<literal>&releasename;-backports</literal> section and they will
be available for installation in the same way as the old
debian-backports archive.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
