Bug 199665 - ports-mgmt/pkg: dependency problem when upgrading a single package
Summary: ports-mgmt/pkg: dependency problem when upgrading a single package
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-pkg (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-24 15:33 UTC by seth.lyons
Modified: 2018-01-12 14:17 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description seth.lyons 2015-04-24 15:33:46 UTC 
when doing "pkg install" for a single package, the packages that it depends on also get installed/upgraded.  however, already installed packages that depend on the newly upgraded dependencies don't get upgraded and are therefore broken.

example:  ruby 2.0 is installed with puppet-3.6.2.  when running "pkg install puppet" to upgrade puppet to 3.7.4, ruby gets upgraded to ruby 2.1.  however, all of the packages on the system that were built on ruby 2.0 *do not* get rebuilt and no longer work since they're linked to ruby 2.0 libraries that no longer exist.

there is also an issue for this on github:  https://github.com/freebsd/pkg/issues/964
Comment 1 Baptiste Daroussin freebsd_committer freebsd_triage 2015-04-24 16:37:29 UTC 
upgrading a single package is not yet fully supported, be will be one day
Comment 2 seth.lyons 2015-04-24 16:54:40 UTC 
i see.  is there an estimated date when that functionality will exist?

so in a situation where we need to upgrade only a single package, what is the recommended way to do that...through ports?  or something else?
Comment 3 Walter Schwarzenfeld 2018-01-12 06:17:17 UTC 
Please feedback (and/or close).
Comment 4 Baptiste Daroussin freebsd_committer freebsd_triage 2018-01-12 14:17:21 UTC 
The is no ETA at all to allow that sorry.