Opened 6 years ago
Closed 22 months ago
#57405 closed defect (wontfix)
atom @1.31.2 build failed on Mojave
| Reported by: | rlhamil | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.5.4 |
| Keywords: | mojave | Cc: | michaellass (Michael Lass) |
| Port: | atom |
Description
main.log attached
Attachments (3)
Change History (12)
Changed 6 years ago by rlhamil
| Attachment: | main.log-atom.txt added |
|---|
comment:1 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | set to kurthindenburg |
|---|---|
| Status: | new → assigned |
comment:2 Changed 6 years ago by michaellass (Michael Lass)
| Cc: | michaellass added |
|---|
comment:3 Changed 6 years ago by michaellass (Michael Lass)
Changed 6 years ago by rlhamil
| Attachment: | main.log-atom-debug.txt added |
|---|
Changed 6 years ago by rlhamil
| Attachment: | 2018-10-22T11_30_52_311Z-debug.log.txt added |
|---|
comment:4 follow-up: 5 Changed 6 years ago by rlhamil
Cleaned, ran port -d install, attached main.log (debug version) and the file you mentioned. In the latter, it looks like it gave up, but I don't see that it's informative as to why.
comment:5 Changed 6 years ago by michaellass (Michael Lass)
Replying to rlhamil:
In the latter, it looks like it gave up, but I don't see that it's informative as to why.
Indeed not very informative. Right now I have no idea what is going on here. You may try to build atom outside of macports as described here to see if it is an upstream issue or an issue with the Portfile. If it is upstream you may open an issue on github.
@kurthindenburg: Any other ideas? I'm not sure if this issue is Mojave-related as it does not occur on my system.
comment:6 Changed 6 years ago by rlhamil
Both by hand and via MacPorts, it took multiple tries to get it done, and didn't work at all at first. That could have been either a problem upstream, or with the network near my end - this seems to do a lot of downloading in the process of building, not just at the beginning. Even once it was working (and following the log file), it would seem to hang, but interrupting the build and restarting it made progress.
Very temperamental. Not sure how much of that is the downloads during build, and how much of that (seeming to stop making progress) might be race conditions or some other issue, whether platform specific or otherwise.
Can the build bots build this? Given how slow (as well as temperamental) the build is, it would help!
comment:7 Changed 3 years ago by kurthindenburg (Kurt Hindenburg)
| Owner: | kurthindenburg deleted |
|---|
I haven't maintained atom in a while - it is too much a nightmare to get working across all the versions.
comment:8 Changed 3 years ago by michaellass (Michael Lass)
For some time I updated the Portfile locally to get newer versions building. However, I never was sure about some of the changes and implications to other versions of macOS or different configurations. In case anyone wants to use or build up on that, I just pushed it to github:
https://github.com/michaellass/macports-ports/commit/29205c000bd5dfc887e467cfab1b49da3f685c75
I stopped using atom a while ago and to me the project looks pretty much dead by now, so I won't do any further updates on this.
comment:9 Changed 22 months ago by kencu (Ken)
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
atome no longer exists as a port
I cannot reproduce this issue on my side. The log looks to me like extracting a downloaded file does not work. Maybe there was a temporary issue with one of the download sources. Could you retry building atom after cleaning the build directory (
sudo port clean atom)?If the error is reproducible: Does the log file at
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_editors_atom/atom/work/.home/.npm/_logs/*-debug.logcontain any useful information?