| 1 |
aptitude (0.6.1.4-1) unstable; urgency=low |
| 2 |
|
| 3 |
Summary: the behavior of "full-upgrade"/"dist-upgrade" has changed |
| 4 |
in a way that could break scripts. See below for details. |
| 5 |
|
| 6 |
This version changes the behavior of the full-upgrade/dist-upgrade |
| 7 |
command when additional arguments are present. Previous versions of |
| 8 |
aptitude used the command-line arguments to extend the default upgrade |
| 9 |
set, so that |
| 10 |
|
| 11 |
# aptitude full-upgrade wesnoth |
| 12 |
|
| 13 |
would install "wesnoth" while attempting to upgrade all other |
| 14 |
upgradable packages. |
| 15 |
|
| 16 |
In version 0.6.1.4, aptitude now uses the list of packages as the |
| 17 |
explicit list of upgrades to perform. Thus, the same command |
| 18 |
|
| 19 |
# aptitude full-upgrade wesnoth |
| 20 |
|
| 21 |
will upgrade wesnoth and not perform any other actions. If wesnoth |
| 22 |
isn't installed, nothing will happen. To get the old behavior, add |
| 23 |
"?upgradable" as the first argument following "full-upgrade" and add |
| 24 |
"+" to the end of each package that had no qualifiers: |
| 25 |
|
| 26 |
# aptitude full-upgrade "?upgradable" wesnoth+ |
| 27 |
|
| 28 |
-- Daniel Burrows <[email protected]> Sun, 17 Jan 2010 22:27:30 -0800 |