Top Menu

Jump to content
  • Package manager
    • View all projects
Home
    • Work packages
    • News
    • Getting started
    • Introduction video
    • Welcome to OpenProject

      Get an overview

      Get a quick overview of project management and team collaboration with OpenProject.
      You can restart this video from the help menu

    • Help and support
    • Upgrade to Enterprise Edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Create a new account
      Forgot your password?

Side Menu

  • Overview
  • Activity
  • Work packages
  • News
  • Forums
  • Repository
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leafCaches and Metadata locations
        • Hierarchy leafConfiguring pkgmanager
        • Hierarchy leafHelp
        • Hierarchy leafInstalling new software
        • Expanded. Click to collapseCollapsed. Click to showPackaging new software
          • Hierarchy leafPackage structure and metadata
          • Hierarchy leaftxz format
        • Hierarchy leafRemoving software
        • Hierarchy leafUpgrading software
You are here:
  • Wiki
  • Upgrading software

Content

Upgrading software

  • More
    • Table of contents

Upgrading existing software

# network update
pkgmanager --upgrade package-name

# local update
pkgmanager --upgrade /path/to/package-name.txz

This commands are used to upgrade a specific package or a set of packages to most actual versions given by path or remote repository. Be aware that automatic dependency resolving is only active if you are working with a remote repository which is supposed to ship dependent packages. Dependent packages from remote repositories will be installed automatically. Recommended packages are installed by default too. If this is not desired see additional switch section.

Upgrading all system

pkgmanager --upgrade all

This command will upgrade to current of currently connected network repositories. Before the procedure starts you'll be prompted if you wish to proceed.

The process interrupts for prompt if package overlapping can't be clearly resolved and a user decision is needed. Use batch mode to overwrite any overlapping without prompt.

Dependency management

Once a package is upgraded with a newer version, all packages depending on them are usually updated too. If not a warning will be issued that a package with outdated dependencies is present. Usually it means that it has to be reinstalled from the remote repository or rebuild if it is a local build to fit in.
While the package is beeing upgraded it resolve it's dependencies in to a install-or-upgrade list which will apply if there is a missing or outdated dependency. The download source of the dependency is resolved according to the repository priority.

Loading...