Bug 193716 - ports-mgmt/portmaster attempts to install port before required port
Summary: ports-mgmt/portmaster attempts to install port before required port
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 15:53 UTC by scottro11
Modified: 2018-11-09 00:58 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description scottro11 2014-09-17 15:53:19 UTC
While fixing some leftover Ruby18 issues on an old server, we ran, among other things, 

portmaster rubygem-coffee-script

This failed with

===>  Staging for rubygem-coffee-script-2.3.0
===>   rubygem-coffee-script-2.3.0 depends on package:
rubygem-coffee-script-source>=1.7.0 - not found
===>   Found rubygem-coffee-script-source-1.4.0, but you need to upgrade to
rubygem-coffee-script-source>=1.7.0.
*** [run-depends] Error code 1

Stop in /usr/ports/devel/rubygem-coffee-script.

===>>> make failed for devel/rubygem-coffee-script
===>>> Aborting update

===>>> Update for rubygem-coffee-script-2.2.0_1 failed
===>>> Aborting update

It then gives a message that to continue,one can run 
portmaster <flags> devel/rubygem-coffee-script devel/rubygem-coffee-script-source

which would have the same problem. The workaround in this case, is to do it manually, but it seems that portmaster is trying to update ruby-gem-coffee-script before updating ruby-gem-coffeescript-source.  I did drop the port maintainer a quick email, and they agree it may be a bug.
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2014-09-17 15:53:19 UTC
Maintainers CC'd
Comment 2 John Marino freebsd_committer freebsd_triage 2014-09-17 16:18:49 UTC
I recall Bryan wants all portmaster PRs assigned to him.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2015-04-25 16:10:29 UTC
Assignee is no longer the maintainer.
Comment 4 John Marino freebsd_committer freebsd_triage 2016-02-10 18:47:18 UTC
PM has a new maintainer, reassign PR.
Comment 5 scottro11 2016-02-10 19:12:43 UTC
For what it's worth, the original bug is from September, 2014 and I haven't installed Ruby on anything since then.
Comment 6 Stefan Eßer freebsd_committer freebsd_triage 2017-12-18 16:34:23 UTC
I've taken over maintainership of this port and cannot reproduce the problem on my system (which has no ruby ports/packages installed and I have no access to the old packages that you were updating from).

Did you observe this or some similar problem recently (in a way that lets me reproduce and diagnose this problem), or do you agree, that this PR can be closed?