Bug#513625: aptitude upgrade action described incorrectly for the version of aptitude that will be installed
On Sat, Aug 22, 2009 at 01:08:10AM +0200, Nicolas François wrote:
> Dear aptitude maintainers,
I am not but ...
> This bug was filed for the Lenny release notes.
> On Fri, Jan 30, 2009 at 07:58:34PM +0000, peter green wrote:
> > package: release-notes
> > severity: minor
> > The lenny release notes say
> > > First, run:
> > > # aptitude upgrade
> > > This has the effect of upgrading those packages which can be
> > > upgraded without requiring any other packages to be removed or
> > > installed.
> > However (assuming the user has followed the instructions) they will
> > be running lenny's aptitude which will install new packages (but
> > won't remove packages) when doing upgrade.
> I had a look at the aptitude's manpage, and could not find a documentation
> for "aptitude upgrade"
> Is it correct to recommend it in the release notes?
> Would it be correct to describe it with the following paragraph?
> This has the effect of upgrading those packages which can be
> upgraded without requiring any other packages to be removed.
Well, I should say good enough for lenny but for squeeze we need to do
s/aptitude upgrade/aptitude safe-upgrade/g
s/aptitude dist-upgrade/aptitude full-upgrade/g
(Yes, it is not just "aptitude upgrade". Next example too needs change)
These upgrade and dist-upgrade options were the option in old days as I
remember. These options are still valid in lenny but they are deprecated
now according to the manual.
Since these are run in old system (possibly semi upgraded to testing by
some), it may be safe to keep them as is for lenny release note. But If you
are prepairing for squeeze, we need to change.