Bug 210370 - ports-mgmt/pkg: Installing ports like ImageMagick7 in some cases requires multiple runs of `pkg install`
Summary: ports-mgmt/pkg: Installing ports like ImageMagick7 in some cases requires mul...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Baptiste Daroussin
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2016-06-18 08:21 UTC by Ben Lavery-Griffiths
Modified: 2016-06-25 12:03 UTC (History)
3 users (show)

See Also:
vlad-fbsd: maintainer-feedback+


Attachments
script(1) output of needing to install twice (106.74 KB, text/plain)
2016-06-18 08:21 UTC, Ben Lavery-Griffiths
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Lavery-Griffiths 2016-06-18 08:21:42 UTC
Created attachment 171536 [details]
script(1) output of needing to install twice

On a clean install of FreeBSD 10.3, when installing ImageMagick7 via pkg(1) it is necessary to run `pkg install ImageMagick7` twice in order to actually install it.  The first time only the dependancies are installed, the second time only ImageMagick7 is installed.

I haven't noticed this with other packages, so presume it is not an issue with pkg(1) - I am running pkg v1.8.5.

This was brought to my attention via this question on StackExchange:
http://unix.stackexchange.com/questions/290529/installed-imagemagick7-7-0-1-5-on-freebsd-10-3-but-there-is-no-import-command/290540
Comment 1 VK 2016-06-18 11:20:43 UTC
Hm indeed. In my case it says 104 packages will be affected, but after the fetch stage it installs 22. The second run of 'pkg install imagemagick7' installs 79 packages. The third run installs ImageMagick7.

CC'ing pkg@ as this looks like a pkg problem to me.
Comment 2 Baptiste Daroussin freebsd_committer freebsd_triage 2016-06-18 15:29:58 UTC
The reason it has happened is probably you have no run pkg upgrade before install imagemagick7

You may also have things installed that were conflicts with it and then the solver tries to handle that conflict.

In next pkg release the conflicts will be explicitly shown to the users
Comment 3 Baptiste Daroussin freebsd_committer freebsd_triage 2016-06-19 16:15:39 UTC
actually the bug is on pkg side, working on a fix
Comment 4 VK 2016-06-19 18:02:17 UTC
Adjusting summary to reflect the problem properly. Maintainer feedback given for pkg, reassigning to Baptiste, kwm@ in CC.

Thanks! :)
Comment 5 Baptiste Daroussin freebsd_committer freebsd_triage 2016-06-25 12:03:36 UTC
fixed in pkg 1.8.6