Yum does not install specific RPM version with custom repo
0
We use RPMS for our packaging and yum to update our environments.
We have an rpm package-5.1.1-3 installed in our production server and in our yum repository we have 2 newer versions such as package-5.1.3-3 and package-5.2-27.
Using yum, we tried to install package-5.1.3-1 but yum installed package-5.2-27.
It caused serious problems in production.
If we remove 5.2-27 package from our custom yum repository and try installing 5.1.3-1, it's installing as expected.
I think yum should allow installation of specific version of RPMS and I remember doing this few times. I tried to debug but no success.
Package already installed:
root@snelloru]# rpm -qa|grep package
pacakge-database-5.1.1-3
package-5.1.1-3
Installing higher version(5.1.3-1)
yum install package-5.1.3-1
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Setting up Install Process
Package matching package-5.1.3-1.x86_64 already installed. Checking for update.
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: package = 5.1.1-3 for package: package-database
---> Package package.x86_64 0:5.1.3-1 set to be updated
--> Running transaction check
---> Package package-database.x86_64 0:5.2-23 set to be updated
--> Processing Dependency: package = 5.2-23 for package: package-database
--> Running transaction check
---> Package package.x86_64 0:5.1.3-1 set to be updated
---> Package package.x86_64 0:5.2-23 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================
Package Arch Version Repository Size
===============================================================
package x86_64 5.2-23 repo 22 M
package-database x86_64 5.2-23
Output of yum list --showduplicates package package-database
root@snelloru]# yum list --showduplicates package package-database
Loaded plugins: allowdowngrade, security
rightscale-epel | 951 B 00:00
Installed Packages
package.x86_64 5.1.1-3 installed
package-database.x86_64 5.1.1-3 installed
Available Packages
package.x86_64 5.1-126 repo
package.x86_64 5.1.1-3 repo
package.x86_64 5.1.2-3 repo
package.x86_64 5.1.3-1 repo
package.x86_64 5.2-25 repo
package.x86_64 5.2-26 repo
package.x86_64 5.2-27 repo
package-database.x86_64 5.1-126 repo
package-database.x86_64 5.1.1-3 repo
package-database.x86_64 5.1.2-3 repo
package-database.x86_64 5.1.3-1 repo
package-database.x86_64 5.2-2 repo
package-database.x86_64 5.2-3 repo
package-database.x86_64 5.2-4 repo
package-database.x86_64 5.2-24 repo
package-database.x86_64 5.2-25 repo
package-database.x86_64 5.2-26 repo
package-database.x86_64 5.2-27 repo
My observation:
If we try to install package of same version which is already installed in the server but with different release number, its working as expected.
For example if we have 5.2-10 installed in the server and if we try to install 5.2-20 its working as expected though we have higher releases like 5.2-25..5.2-28 are present in repo.
Its not working only when we have different version of rpm is installed
Any ideas on this??
centos yum rpm rpmbuild
asked Jun 25 '14 at 18:59
SridharSridhar
10414
add a comment |
0
We use RPMS for our packaging and yum to update our environments.
We have an rpm package-5.1.1-3 installed in our production server and in our yum repository we have 2 newer versions such as package-5.1.3-3 and package-5.2-27.
Using yum, we tried to install package-5.1.3-1 but yum installed package-5.2-27.
It caused serious problems in production.
If we remove 5.2-27 package from our custom yum repository and try installing 5.1.3-1, it's installing as expected.
I think yum should allow installation of specific version of RPMS and I remember doing this few times. I tried to debug but no success.
Package already installed:
root@snelloru]# rpm -qa|grep package
pacakge-database-5.1.1-3
package-5.1.1-3
Installing higher version(5.1.3-1)
yum install package-5.1.3-1
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Setting up Install Process
Package matching package-5.1.3-1.x86_64 already installed. Checking for update.
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: package = 5.1.1-3 for package: package-database
---> Package package.x86_64 0:5.1.3-1 set to be updated
--> Running transaction check
---> Package package-database.x86_64 0:5.2-23 set to be updated
--> Processing Dependency: package = 5.2-23 for package: package-database
--> Running transaction check
---> Package package.x86_64 0:5.1.3-1 set to be updated
---> Package package.x86_64 0:5.2-23 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================
Package Arch Version Repository Size
===============================================================
package x86_64 5.2-23 repo 22 M
package-database x86_64 5.2-23
Output of yum list --showduplicates package package-database
root@snelloru]# yum list --showduplicates package package-database
Loaded plugins: allowdowngrade, security
rightscale-epel | 951 B 00:00
Installed Packages
package.x86_64 5.1.1-3 installed
package-database.x86_64 5.1.1-3 installed
Available Packages
package.x86_64 5.1-126 repo
package.x86_64 5.1.1-3 repo
package.x86_64 5.1.2-3 repo
package.x86_64 5.1.3-1 repo
package.x86_64 5.2-25 repo
package.x86_64 5.2-26 repo
package.x86_64 5.2-27 repo
package-database.x86_64 5.1-126 repo
package-database.x86_64 5.1.1-3 repo
package-database.x86_64 5.1.2-3 repo
package-database.x86_64 5.1.3-1 repo
package-database.x86_64 5.2-2 repo
package-database.x86_64 5.2-3 repo
package-database.x86_64 5.2-4 repo
package-database.x86_64 5.2-24 repo
package-database.x86_64 5.2-25 repo
package-database.x86_64 5.2-26 repo
package-database.x86_64 5.2-27 repo
My observation:
If we try to install package of same version which is already installed in the server but with different release number, its working as expected.
For example if we have 5.2-10 installed in the server and if we try to install 5.2-20 its working as expected though we have higher releases like 5.2-25..5.2-28 are present in repo.
Its not working only when we have different version of rpm is installed
Any ideas on this??
centos yum rpm rpmbuild
asked Jun 25 '14 at 18:59
SridharSridhar
10414
You can ask for a specific packave version, but only if it is still available in the repository. Given that distribution repositories are cleaned out aggressively, old versions don't stay around long (if at all). Why do you want to go to an old version in the first place?
– vonbrand
Jun 25 '14 at 20:01
I am not trying to install any package from distribution. Its our own software package. We generate packages everyday keep them in RPM repository and install them using YUM. We have all older versions stored in our repo and I am expecting yum to install older version when it is present in the RPM repository.
– Sridhar
Jun 25 '14 at 20:27
Do you need to feed it the--allow-downgradeflag because it's already aware of the newer version? Also,yum-versionlockmay become necessary on that machine forever after.
– warren
Jun 25 '14 at 22:36
add a comment |
0
0
0
2
We use RPMS for our packaging and yum to update our environments.
We have an rpm package-5.1.1-3 installed in our production server and in our yum repository we have 2 newer versions such as package-5.1.3-3 and package-5.2-27.
Using yum, we tried to install package-5.1.3-1 but yum installed package-5.2-27.
It caused serious problems in production.
If we remove 5.2-27 package from our custom yum repository and try installing 5.1.3-1, it's installing as expected.
I think yum should allow installation of specific version of RPMS and I remember doing this few times. I tried to debug but no success.
Package already installed:
root@snelloru]# rpm -qa|grep package
pacakge-database-5.1.1-3
package-5.1.1-3
Installing higher version(5.1.3-1)
yum install package-5.1.3-1
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Setting up Install Process
Package matching package-5.1.3-1.x86_64 already installed. Checking for update.
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: package = 5.1.1-3 for package: package-database
---> Package package.x86_64 0:5.1.3-1 set to be updated
--> Running transaction check
---> Package package-database.x86_64 0:5.2-23 set to be updated
--> Processing Dependency: package = 5.2-23 for package: package-database
--> Running transaction check
---> Package package.x86_64 0:5.1.3-1 set to be updated
---> Package package.x86_64 0:5.2-23 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================
Package Arch Version Repository Size
===============================================================
package x86_64 5.2-23 repo 22 M
package-database x86_64 5.2-23
Output of yum list --showduplicates package package-database
root@snelloru]# yum list --showduplicates package package-database
Loaded plugins: allowdowngrade, security
rightscale-epel | 951 B 00:00
Installed Packages
package.x86_64 5.1.1-3 installed
package-database.x86_64 5.1.1-3 installed
Available Packages
package.x86_64 5.1-126 repo
package.x86_64 5.1.1-3 repo
package.x86_64 5.1.2-3 repo
package.x86_64 5.1.3-1 repo
package.x86_64 5.2-25 repo
package.x86_64 5.2-26 repo
package.x86_64 5.2-27 repo
package-database.x86_64 5.1-126 repo
package-database.x86_64 5.1.1-3 repo
package-database.x86_64 5.1.2-3 repo
package-database.x86_64 5.1.3-1 repo
package-database.x86_64 5.2-2 repo
package-database.x86_64 5.2-3 repo
package-database.x86_64 5.2-4 repo
package-database.x86_64 5.2-24 repo
package-database.x86_64 5.2-25 repo
package-database.x86_64 5.2-26 repo
package-database.x86_64 5.2-27 repo
My observation:
If we try to install package of same version which is already installed in the server but with different release number, its working as expected.
For example if we have 5.2-10 installed in the server and if we try to install 5.2-20 its working as expected though we have higher releases like 5.2-25..5.2-28 are present in repo.
Its not working only when we have different version of rpm is installed
Any ideas on this??
centos yum rpm rpmbuild
asked Jun 25 '14 at 18:59
SridharSridhar
10414
We use RPMS for our packaging and yum to update our environments.
We have an rpm package-5.1.1-3 installed in our production server and in our yum repository we have 2 newer versions such as package-5.1.3-3 and package-5.2-27.
Using yum, we tried to install package-5.1.3-1 but yum installed package-5.2-27.
It caused serious problems in production.
If we remove 5.2-27 package from our custom yum repository and try installing 5.1.3-1, it's installing as expected.
I think yum should allow installation of specific version of RPMS and I remember doing this few times. I tried to debug but no success.
Package already installed:
root@snelloru]# rpm -qa|grep package
pacakge-database-5.1.1-3
package-5.1.1-3
Installing higher version(5.1.3-1)
yum install package-5.1.3-1
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Setting up Install Process
Package matching package-5.1.3-1.x86_64 already installed. Checking for update.
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: package = 5.1.1-3 for package: package-database
---> Package package.x86_64 0:5.1.3-1 set to be updated
--> Running transaction check
---> Package package-database.x86_64 0:5.2-23 set to be updated
--> Processing Dependency: package = 5.2-23 for package: package-database
--> Running transaction check
---> Package package.x86_64 0:5.1.3-1 set to be updated
---> Package package.x86_64 0:5.2-23 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================
Package Arch Version Repository Size
===============================================================
package x86_64 5.2-23 repo 22 M
package-database x86_64 5.2-23
Output of yum list --showduplicates package package-database
root@snelloru]# yum list --showduplicates package package-database
Loaded plugins: allowdowngrade, security
rightscale-epel | 951 B 00:00
Installed Packages
package.x86_64 5.1.1-3 installed
package-database.x86_64 5.1.1-3 installed
Available Packages
package.x86_64 5.1-126 repo
package.x86_64 5.1.1-3 repo
package.x86_64 5.1.2-3 repo
package.x86_64 5.1.3-1 repo
package.x86_64 5.2-25 repo
package.x86_64 5.2-26 repo
package.x86_64 5.2-27 repo
package-database.x86_64 5.1-126 repo
package-database.x86_64 5.1.1-3 repo
package-database.x86_64 5.1.2-3 repo
package-database.x86_64 5.1.3-1 repo
package-database.x86_64 5.2-2 repo
package-database.x86_64 5.2-3 repo
package-database.x86_64 5.2-4 repo
package-database.x86_64 5.2-24 repo
package-database.x86_64 5.2-25 repo
package-database.x86_64 5.2-26 repo
package-database.x86_64 5.2-27 repo
My observation:
If we try to install package of same version which is already installed in the server but with different release number, its working as expected.
For example if we have 5.2-10 installed in the server and if we try to install 5.2-20 its working as expected though we have higher releases like 5.2-25..5.2-28 are present in repo.
Its not working only when we have different version of rpm is installed
Any ideas on this??
centos yum rpm rpmbuild
centos yum rpm rpmbuild
asked Jun 25 '14 at 18:59
SridharSridhar
10414
asked Jun 25 '14 at 18:59
SridharSridhar
10414
edited Jun 26 '14 at 17:38
Sridhar
asked Jun 25 '14 at 18:59
SridharSridhar
10414
asked Jun 25 '14 at 18:59
SridharSridhar
10414
asked Jun 25 '14 at 18:59
SridharSridhar
10414
10414
You can ask for a specific packave version, but only if it is still available in the repository. Given that distribution repositories are cleaned out aggressively, old versions don't stay around long (if at all). Why do you want to go to an old version in the first place?
– vonbrand
Jun 25 '14 at 20:01
I am not trying to install any package from distribution. Its our own software package. We generate packages everyday keep them in RPM repository and install them using YUM. We have all older versions stored in our repo and I am expecting yum to install older version when it is present in the RPM repository.
– Sridhar
Jun 25 '14 at 20:27
Do you need to feed it the--allow-downgradeflag because it's already aware of the newer version? Also,yum-versionlockmay become necessary on that machine forever after.
– warren
Jun 25 '14 at 22:36
add a comment |
You can ask for a specific packave version, but only if it is still available in the repository. Given that distribution repositories are cleaned out aggressively, old versions don't stay around long (if at all). Why do you want to go to an old version in the first place?
– vonbrand
Jun 25 '14 at 20:01
I am not trying to install any package from distribution. Its our own software package. We generate packages everyday keep them in RPM repository and install them using YUM. We have all older versions stored in our repo and I am expecting yum to install older version when it is present in the RPM repository.
– Sridhar
Jun 25 '14 at 20:27
Do you need to feed it the--allow-downgradeflag because it's already aware of the newer version? Also,yum-versionlockmay become necessary on that machine forever after.
– warren
Jun 25 '14 at 22:36
You can ask for a specific packave version, but only if it is still available in the repository. Given that distribution repositories are cleaned out aggressively, old versions don't stay around long (if at all). Why do you want to go to an old version in the first place?
– vonbrand
Jun 25 '14 at 20:01
You can ask for a specific packave version, but only if it is still available in the repository. Given that distribution repositories are cleaned out aggressively, old versions don't stay around long (if at all). Why do you want to go to an old version in the first place?
– vonbrand
Jun 25 '14 at 20:01
I am not trying to install any package from distribution. Its our own software package. We generate packages everyday keep them in RPM repository and install them using YUM. We have all older versions stored in our repo and I am expecting yum to install older version when it is present in the RPM repository.
– Sridhar
Jun 25 '14 at 20:27
I am not trying to install any package from distribution. Its our own software package. We generate packages everyday keep them in RPM repository and install them using YUM. We have all older versions stored in our repo and I am expecting yum to install older version when it is present in the RPM repository.
– Sridhar
Jun 25 '14 at 20:27
Do you need to feed it the
--allow-downgrade flag because it's already aware of the newer version? Also, yum-versionlock may become necessary on that machine forever after.– warren
Jun 25 '14 at 22:36
Do you need to feed it the
--allow-downgrade flag because it's already aware of the newer version? Also, yum-versionlock may become necessary on that machine forever after.– warren
Jun 25 '14 at 22:36
add a comment |
1 Answer
1
active
oldest
votes
0
Try: yum upgrade-to package-5.1.3
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
Thanks Eran, its working as expected but I am not confidant enough to use upgrade-to instead of install, as updrage will delete obsolete packages. We use yum to install our packages in production environments. Is this is normal behavior or yum to always pick latest version even if you specify version number???
– Sridhar
Jun 26 '14 at 17:42
yum install will install the scpecific version you are asking for. In your example above, package-5.1.3-1 is already installed, so yum tried to upgrade. Note, however, that if you have a package foo that depends on bar, and you have 1.0 and 2.0 versions for both, if you run yum install foo-1.0 it will install bar-2.0 as dependency and not 1.0 because you didn't specify version for bar, so yum picks up the latest. In this case, use yum install bar-1.0 foo 1.0.
– Eran Ben-Natan
Jun 29 '14 at 5:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f773442%2fyum-does-not-install-specific-rpm-version-with-custom-repo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Try: yum upgrade-to package-5.1.3
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
Thanks Eran, its working as expected but I am not confidant enough to use upgrade-to instead of install, as updrage will delete obsolete packages. We use yum to install our packages in production environments. Is this is normal behavior or yum to always pick latest version even if you specify version number???
– Sridhar
Jun 26 '14 at 17:42
yum install will install the scpecific version you are asking for. In your example above, package-5.1.3-1 is already installed, so yum tried to upgrade. Note, however, that if you have a package foo that depends on bar, and you have 1.0 and 2.0 versions for both, if you run yum install foo-1.0 it will install bar-2.0 as dependency and not 1.0 because you didn't specify version for bar, so yum picks up the latest. In this case, use yum install bar-1.0 foo 1.0.
– Eran Ben-Natan
Jun 29 '14 at 5:21
add a comment |
0
Try: yum upgrade-to package-5.1.3
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
Thanks Eran, its working as expected but I am not confidant enough to use upgrade-to instead of install, as updrage will delete obsolete packages. We use yum to install our packages in production environments. Is this is normal behavior or yum to always pick latest version even if you specify version number???
– Sridhar
Jun 26 '14 at 17:42
yum install will install the scpecific version you are asking for. In your example above, package-5.1.3-1 is already installed, so yum tried to upgrade. Note, however, that if you have a package foo that depends on bar, and you have 1.0 and 2.0 versions for both, if you run yum install foo-1.0 it will install bar-2.0 as dependency and not 1.0 because you didn't specify version for bar, so yum picks up the latest. In this case, use yum install bar-1.0 foo 1.0.
– Eran Ben-Natan
Jun 29 '14 at 5:21
add a comment |
0
0
0
Try: yum upgrade-to package-5.1.3
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
Try: yum upgrade-to package-5.1.3
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
edited Jun 26 '14 at 14:51
Jens Erat
12.8k114660
12.8k114660
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
answered Jun 26 '14 at 14:23
Eran Ben-NatanEran Ben-Natan
29117
29117
Thanks Eran, its working as expected but I am not confidant enough to use upgrade-to instead of install, as updrage will delete obsolete packages. We use yum to install our packages in production environments. Is this is normal behavior or yum to always pick latest version even if you specify version number???
– Sridhar
Jun 26 '14 at 17:42
yum install will install the scpecific version you are asking for. In your example above, package-5.1.3-1 is already installed, so yum tried to upgrade. Note, however, that if you have a package foo that depends on bar, and you have 1.0 and 2.0 versions for both, if you run yum install foo-1.0 it will install bar-2.0 as dependency and not 1.0 because you didn't specify version for bar, so yum picks up the latest. In this case, use yum install bar-1.0 foo 1.0.
– Eran Ben-Natan
Jun 29 '14 at 5:21
add a comment |
Thanks Eran, its working as expected but I am not confidant enough to use upgrade-to instead of install, as updrage will delete obsolete packages. We use yum to install our packages in production environments. Is this is normal behavior or yum to always pick latest version even if you specify version number???
– Sridhar
Jun 26 '14 at 17:42
yum install will install the scpecific version you are asking for. In your example above, package-5.1.3-1 is already installed, so yum tried to upgrade. Note, however, that if you have a package foo that depends on bar, and you have 1.0 and 2.0 versions for both, if you run yum install foo-1.0 it will install bar-2.0 as dependency and not 1.0 because you didn't specify version for bar, so yum picks up the latest. In this case, use yum install bar-1.0 foo 1.0.
– Eran Ben-Natan
Jun 29 '14 at 5:21
Thanks Eran, its working as expected but I am not confidant enough to use upgrade-to instead of install, as updrage will delete obsolete packages. We use yum to install our packages in production environments. Is this is normal behavior or yum to always pick latest version even if you specify version number???
– Sridhar
Jun 26 '14 at 17:42
Thanks Eran, its working as expected but I am not confidant enough to use upgrade-to instead of install, as updrage will delete obsolete packages. We use yum to install our packages in production environments. Is this is normal behavior or yum to always pick latest version even if you specify version number???
– Sridhar
Jun 26 '14 at 17:42
yum install will install the scpecific version you are asking for. In your example above, package-5.1.3-1 is already installed, so yum tried to upgrade. Note, however, that if you have a package foo that depends on bar, and you have 1.0 and 2.0 versions for both, if you run yum install foo-1.0 it will install bar-2.0 as dependency and not 1.0 because you didn't specify version for bar, so yum picks up the latest. In this case, use yum install bar-1.0 foo 1.0.
– Eran Ben-Natan
Jun 29 '14 at 5:21
yum install will install the scpecific version you are asking for. In your example above, package-5.1.3-1 is already installed, so yum tried to upgrade. Note, however, that if you have a package foo that depends on bar, and you have 1.0 and 2.0 versions for both, if you run yum install foo-1.0 it will install bar-2.0 as dependency and not 1.0 because you didn't specify version for bar, so yum picks up the latest. In this case, use yum install bar-1.0 foo 1.0.
– Eran Ben-Natan
Jun 29 '14 at 5:21
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f773442%2fyum-does-not-install-specific-rpm-version-with-custom-repo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You can ask for a specific packave version, but only if it is still available in the repository. Given that distribution repositories are cleaned out aggressively, old versions don't stay around long (if at all). Why do you want to go to an old version in the first place?
– vonbrand
Jun 25 '14 at 20:01
I am not trying to install any package from distribution. Its our own software package. We generate packages everyday keep them in RPM repository and install them using YUM. We have all older versions stored in our repo and I am expecting yum to install older version when it is present in the RPM repository.
– Sridhar
Jun 25 '14 at 20:27
Do you need to feed it the
--allow-downgradeflag because it's already aware of the newer version? Also,yum-versionlockmay become necessary on that machine forever after.– warren
Jun 25 '14 at 22:36