wpkg --upgrade-urgent
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. |
|
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-urgent command is used to upgrade a target system with all the packages that have an urgency of High or more. 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-urgent command of wpkg is the same as the --upgrade except that only urgent packages, as defined by the Urgency field, are upgraded. Therefore the --interactive command line flag works the same way and like with the --upgrade command, you should run --update once before.
To see a list of the packages that will be upgraded, you may use the --upgrade-info command line option. This option shows you which packages are going to be upgraded with the --upgrade and which are upgraded with both: --upgrade and --upgrade-urgent.