Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

installing an older version of an existing package fails silently #73

Closed
andrewh1978 opened this issue Oct 28, 2016 · 2 comments
Closed
Assignees

Comments

@andrewh1978
Copy link

Installing a newer version works, but installing an older version does nothing:

[root@test ~]# pkgin se nodejs
sqlrelay-nodejs-0.65.0  node.js API for SQL Relay
nodejs-6.7.0 <       V8 JavaScript for clients and servers
nodejs-4.6.0 =       V8 JavaScript for clients and servers
nodejs-0.8.28 >      V8 JavaScript for clients and servers
nodejs-0.12.17 >     V8 JavaScript for clients and servers
nodejs-0.10.48 >     V8 JavaScript for clients and servers

=: package is installed and up-to-date
<: package is installed but newer version is available
>: installed package has a greater version than available package
[root@test ~]# pkgin -y in nodejs-6.7.0
calculating dependencies... done.

1 packages to be upgraded:

nodejs-4.6.0

1 packages to be installed (0B to download, 871K to install):

nodejs-6.7.0

downloading packages...
removing packages to be upgraded...
removing nodejs-4.6.0...
pkg_install warnings: 0, errors: 0
installing packages...
installing nodejs-6.7.0...
pkg_install warnings: 0, errors: 0
reading local summary...
processing local summary...
[root@test ~]# pkgin se nodejs
sqlrelay-nodejs-0.65.0  node.js API for SQL Relay
nodejs-6.7.0 =       V8 JavaScript for clients and servers
nodejs-4.6.0 >       V8 JavaScript for clients and servers
nodejs-0.8.28 >      V8 JavaScript for clients and servers
nodejs-0.12.17 >     V8 JavaScript for clients and servers
nodejs-0.10.48 >     V8 JavaScript for clients and servers

=: package is installed and up-to-date
<: package is installed but newer version is available
>: installed package has a greater version than available package
[root@test ~]# pkgin -y in nodejs-4.6.0
calculating dependencies... done.
nothing to do.
[root@test ~]# pkgin se nodejs
sqlrelay-nodejs-0.65.0  node.js API for SQL Relay
nodejs-6.7.0 =       V8 JavaScript for clients and servers
nodejs-4.6.0 >       V8 JavaScript for clients and servers
nodejs-0.8.28 >      V8 JavaScript for clients and servers
nodejs-0.12.17 >     V8 JavaScript for clients and servers
nodejs-0.10.48 >     V8 JavaScript for clients and servers

=: package is installed and up-to-date
<: package is installed but newer version is available
>: installed package has a greater version than available package
@jperkin
Copy link
Contributor

jperkin commented Sep 19, 2017

This diff appears to resolve the problem:

--- impact.c.orig	2016-02-08 16:27:12.000000000 +0000
+++ impact.c
@@ -241,8 +241,8 @@ deps_impact(Plisthead *impacthead, Pkgli
 				 * local pkgname didn't match deps, remote pkg
 				 * has a lesser version than local package.
 				 */
-				if (version_check(plist->full,
-					remotepkg) == 1) {
+				if (pdp->level > 0 &&
+				    version_check(plist->full, remotepkg) == 1) {
 					/*
 					 * proposing a downgrade is definitely
 					 * not useful, not sure what I want to

I think this is correct (ignore the downgrade problem if the package has been directly specified), but I'm going to leave it to bake in the SmartOS 2017Q3 builds first before committing here.

@jperkin jperkin self-assigned this Sep 19, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Sep 26, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Sep 26, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Dec 12, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Dec 19, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Dec 21, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Dec 30, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Dec 30, 2017
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Jan 16, 2018
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Jan 26, 2018
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Apr 3, 2018
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Apr 3, 2018
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue May 18, 2018
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue May 25, 2018
jperkin pushed a commit to TritonDataCenter/pkgsrc that referenced this issue Jun 11, 2018
@jperkin
Copy link
Contributor

jperkin commented Aug 18, 2023

Likely fixed a long time ago, but certainly should be in 23.8.0.

@jperkin jperkin closed this as completed Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants