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

pkg upgrade/install <package> doesn't upgrade deps (even pkg install did with 1.2.x...) #964

Open
nox42 opened this issue Aug 15, 2014 · 6 comments
Labels
Milestone

Comments

@nox42
Copy link

nox42 commented Aug 15, 2014

I did a poudriere bulk -c to build (among other things) multimedia/mpv for a 9.2 box that has somewhat older packages; pkg install mpv there then only upgraded mpv itself even tho at least libdvdread needed to be upgraded as well (shilib bump) - i was told this is because 1.3.6 no longer cares about shlib versions and to try pkg upgrade instead of pkg install - but that also didn't upgrade libdvdread. I'm told this is a bug, and I agree. :)

@bdrewery bdrewery added this to the 1.3 milestone Aug 15, 2014
@bdrewery
Copy link
Member

I have this case on my system now. I have an older apr installed. Installing apache24 does not propose to upgrade apr. Once apache is installed it is missing several apr libraries.

@bdrewery
Copy link
Member

I just installed 1.2 and it does not automatically handle this situation. It does not upgrade apr when I try to install apache24. It could be due to the remote not having proper shlib versions, but I doubt it.

I will build my own repo with fixed shlibs and see if it makes a difference.

I do agree this is a defect that should be fixed though. Just as pkg delete was fixed to be recursive to keep a consistent system, pkg install needs to consider what else is needed to have a working package installed.

@bdrewery
Copy link
Member

I ran into this today with 1.3.8:

# pkg install -f subversion openssl nginx
Updating local repository catalogue...
local repository is up-to-date.
All repositories are up-to-date.
The following 4 packages will be affected (of 0 checked):
New packages to be INSTALLED:
        rubygem-gettext: 2.3.1
Installed packages to be UPGRADED:
        openssl: 1.0.1_13 -> 1.0.1_15
        nginx: 1.6.0_2,2 -> 1.6.2,2
        subversion: 1.8.9_5 -> 1.8.10_3
The process will require 1 MB more space.
5 MB to be downloaded.
Proceed with this action? [y/N]: y
Checking integrity... done (0 conflicting)
[1/4] Upgrading openssl from 1.0.1_13 to 1.0.1_15: 100%
===> Creating users and/or groups.
Using existing group 'www'.
Using existing user 'www'.
[2/4] Upgrading nginx from 1.6.0_2,2 to 1.6.2,2: 100%
[3/4] Upgrading subversion from 1.8.9_5 to 1.8.10_3: 100%
[4/4] Installing rubygem-gettext-2.3.1: 100%
# service nginx restart
Performing sanity check on nginx configuration:
Shared object "libGeoIP.so.1" not found, required by "nginx"

@bdrewery bdrewery changed the title pkg upgrade <package> doesn't upgrade deps (even pkg install did with 1.2.x...) pkg upgrade/install <package> doesn't upgrade deps (even pkg install did with 1.2.x...) Oct 3, 2014
@kpaasial
Copy link

This is still an issue with pkg version 1.3.8_3. I switched a system that was using my own package repository to use the official packages. My own packages were built with OPTIONS_UNSET=X11. After doing 'pkg update -f', 'pkg install -f vim' the editors/vim package was installed but none of the new dependencies including a whole bunch of X11 libraries were not installed resulting in a broken installation. Only when I reinstalled another package by force, devel/pcre, the missing dependencies were detected and pkg prompted me to install them.

@ari
Copy link

ari commented Oct 27, 2014

I've had the same issues and posted about it here: http://markmail.org/message/anqqpncruvgwz53m

This is a pretty serious bug for us since it doesn't have a simple workaround other than always upgrading every installed package on a system at the same time, or manually trawling through all the dependencies.

@linearray
Copy link

yep, same here with 1.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants