Bug 224357 - www/gitlab: Does not build with Node 8.x
Summary: www/gitlab: Does not build with Node 8.x
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Po-Chuan Hsieh
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-15 04:17 UTC by Marcel Bischoff
Modified: 2017-12-16 06:17 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (tz)


Attachments
Poudriere build log (19.38 KB, text/plain)
2017-12-15 04:17 UTC, Marcel Bischoff
no flags Details
Poudriere build log with yarn/node8 (24.35 KB, text/plain)
2017-12-15 15:37 UTC, Marcel Bischoff
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel Bischoff 2017-12-15 04:17:14 UTC
Created attachment 188855 [details]
Poudriere build log

I have defined Node 8.x as a dependency for www/npm. Because of this, GitLab refuses to build in Poudriere. Please see the attached build log.
Comment 1 Jochen Neumeister freebsd_committer freebsd_triage 2017-12-15 06:40:00 UTC
New Maintainer of gitlab is "Matthias" <idefix@fechner.net>: https://svnweb.freebsd.org/changeset/ports/455591

I will CC him :-)
Comment 2 Po-Chuan Hsieh freebsd_committer freebsd_triage 2017-12-15 13:10:10 UTC
It's not related to gitlab.
Since you use node 8 for npm, you must also use node 8 for yarn.

===>   gitlab-10.1.5_1 depends on package: yarn>=0.17.0 - not found
===>   Installing existing package /packages/All/yarn-1.3.2_2.txz
[build] Installing yarn-1.3.2_2...
[build] `-- Installing node-9.2.1...
pkg-static: node-9.2.1 conflicts with node8-8.9.3 (installs files into the same place).  Problematic file: /usr/local/bin/node

Failed to install the following 1 package(s): /packages/All/yarn-1.3.2_2.txz
Comment 3 Marcel Bischoff 2017-12-15 15:37:12 UTC
Created attachment 188862 [details]
Poudriere build log with yarn/node8

Unfortunately this is not correct. It still results in a build error because at some later point Node 9 is wanted. Please see the new build log.
Comment 4 Marcel Bischoff 2017-12-15 15:44:02 UTC
So I guess the culprit is now rubygem-rails4. And this one doesn't even have an option for choosing a different Node.

The whole process for Node.js style packages is broken. FreeBSD prides itself for being a rock-solid production system yet somehow requires me to run non-LTS software because ports automatically depend on the newest version of some package. This is akin to running 12-CURRENT on a production system.

As this appears to be some deeper, structural problem: where can I best take it to address this?
Comment 5 Po-Chuan Hsieh freebsd_committer freebsd_triage 2017-12-16 00:02:15 UTC
That's still the same problem.

[build] |   | `-- Installing rubygem-execjs-2.7.0...
[build] |   |   `-- Installing node-9.2.1...
pkg-static: node-9.2.1 conflicts with node8-8.9.3 (installs files into the same place).  Problematic file: /usr/local/bin/node

Failed to install the following 1 package(s): /packages/All/rubygem-rails4-4.2.10.txz
*** Error code 70

I've added NODE8 option to devel/rubygem-execjs.