Project

General

Profile

Actions
Copy link

User story #3116

closed

Techniques Package Management don't let the user defines the version to install

Added by Nicolas CHARLES almost 12 years ago. Updated almost 12 years ago.

Status:
Rejected
Priority:
2
Assignee:
-
Category:
Techniques
Target version:
2.5.0~rc1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

The techniques Package management for RHEL/CentOS/SuSE/RPM systems and Package management for Debian / Ubuntu / APT systems don't let user select specific version.
This prevents some case to be handled :
- on systems with differents version of a package installed, but not the one we want (for instance, package installed in version 1.2.3 and 1.2.5, and the one we want is 1.2.4)
- on system with not previous known state for a package (might be installed or not), we can't simply say : install on version 1.2.4 : install checks that the package is installed (but don't update); update updates it (but don't install it)

Having a repository with only the right version of the package won't work, as it wouldn't update from 1.2.5 to 1.2.4

Related issues 2 (0 open — 2 closed)

Has duplicate Rudder - User story #1017: Extend PT to install packages to handle version constraintsRejected2011-03-02Actions
Is duplicate of Rudder - User story #3147: Enable the user to specify a package version in the rpmPackageInstallation and aptPackageInstallation TechniqueReleasedMatthieu CERDA2013-01-07Actions
Actions
Copy link
 #1

Updated by Nicolas PERRON almost 12 years ago

  • Target version changed from 2.5.0~beta1 to 2.5.0~rc1
Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 12 years ago

  • Status changed from New to Rejected

This has been duplicated by #3147, but I'm closing this ticket because the other one has pull requests attached.

Actions
Copy link

Also available in: Atom PDF