wpkg --upgrade

Submitted by Alexis Wilke on Sat, 03/30/2013 - 07:22
Options Comments
--admindir Define the administration directory, where the database of the installed packages resides.
--debug Define a set of flags of things to print out for debug purposes.
--dry-run Run all validations then exit.
--force-architecture Ignore architecture mismatch errors.
--force-breaks Allow the installation of packages that break others.
--force-configure-any Automatically configure packages that were only unpackaged earlier.
--force-conflicts Accept packages even if they are in conflict with others.
--force-depends Accept installing packages with missing dependencies.
--force-depends-version Accept installing packages with dependencies having incompatible versions.
--instdir Define the installation directory, where the data files are installed on the target.
--interactive Allow wpkg to interactively request a username and password when necessary to access a remote drive.
--no-act Run all validations then exit.
--no-force-all Prevent any --force-... command line option from being used.
--no-force-architecture Prevent package with an incompatible architectures from being installed.
--no-force-breaks Prevent the installation of package if marked as breaking each others.
--no-force-configure-any Do no automatically configure packaages. If a dependency is an unpacked package, then the verification fails.
--no-force-conflicts Prevent incompatible packages from being installed along each others.
--no-force-depends Prevent packages with missing dependencies from being installed.
--no-force-depends-version Prevent installing packages if dependency versions are not compatible.
--quiet Request for minimal output. For the --verify function this is the default behavior.
--refuse-all Prevent all problems from ever being bypassed.
--refuse-architecture Prevent package with an incompatible architecture from being installed.
--refuse-breaks Prevent the installation of package if marked as breaking each others.
--refuse-configure-any Do no automatically configure packaages. If a dependency is an unpacked package, then the verification fails.
--refuse-conflicts Prevent incompatible packages from being installed along each others.
--refuse-depends Prevent packages with missing dependencies from being installed.
--refuse-depends-version Prevent installing packages if dependency versions are not compatible.
--root Define the installation root path.
--simulate Run all validations then exit.
--verify-fields Ensure fields validity before processing.
--verbose Display log information of level INFO.

 

The packager --upgrade command is used to upgrade a target system that has packages installed from a remote repository marked as a source. Packages from such a repository where previously installed with the --install command as in:

wpkg --install package-name (this is not working yet)
wpkg --install URI-to-repository/path/to/package/full-package-name.deb

where package-name is just and only the name of a package as it appears in the Package field of the package control file. (i.e. the name without the version and architecture of the package,) or they were automatically installed as dependencies of packages required by explicitly installed packages.

The target is defined by the --root directory (or --instdir and --admindir directories.) The upgrade takes the current repository indexes in account to calculate what needs to be upgraded. Everything is automatic and assuming you did not create a repository with conflicting versions, everything should work without any errors.

The --upgrade command of wpkg is very similar to the upgrade command of the apt-get tool in Debian. In fact, it works very much the same, except that it is not interactive by default (contrary to the apt-get tool which by default asks you whether to do the upgrade, although you can use the --interactive option in a configuration file or an environment variable.) You can make this feature interactive by using the option by the same name:

wpkg --upgrade --interactive --root ~/target

Note that the --upgrade command does not take any parameters. However, you probably will want to specify a root directory.

Also, the command is very similar to running --install with all the names of all the packages that are currently out of date except for those that have their selection set to Hold (which is why the --force-hold is forbidden along the --upgrade command.)

Note that in order for you to upgrade everything to the latest possible version, you do want to run wpkg --update once just before the --upgrade.

IMPORTANT NOTE

The --force-hold option is actually forbidden with the --upgrade and --upgrade-urgent commands. This is because all installed packages with an --upgrade are all considered implicit and therefore the --force-hold does not make sense in that situation. Other --force-... options will certainly be added to this list in the future (i.e. --force-overwrite and --force-overwrite-dir are likely going to be forbidden too.)