Search Criteria
Package Details: buffalo-bin 0.18.14-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/buffalo-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | buffalo-bin |
| Description: | A Go web development ecosystem, designed to make your project easier |
| Upstream URL: | https://gobuffalo.io |
| Licenses: | MIT |
| Conflicts: | buffalo-git |
| Submitter: | theguy147 |
| Maintainer: | Shane4STER |
| Last Packager: | Shane4STER |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-04-21 16:23 (UTC) |
| Last Updated: | 2023-08-04 18:43 (UTC) |
Dependencies (6)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go)
- gcc (gccrs-gitAUR, gcc11AUR, gcc-gitAUR) (optional) – for sqlite3 support
- git (git-gitAUR) (optional) – VCS support
- nodejs (nodejs-gitAUR, nodejs-lts-fermiumAUR, nodejs-sharedAUR, nodejs-lts-hydrogen, nodejs-lts-iron) (optional) – frontend support
- npm (corepackerAUR) (optional) – asset pipeline
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (optional) – frontend dependency management
Latest Comments
theguy147 commented on 2021-01-21 22:11 (UTC) (edited on 2021-01-21 22:12 (UTC) by theguy147)
You're right there seems to be a dependency to python inside the node dependencies, specifically in
node-gyp.Looking at their Github page [1] they support python v2.7, v3.5, v3.6, v3.7 and v3.8. "Unfortunately" Arch already ships python version 3.9 which I suppose is not supported by them yet although the issue could be something else as well. They might try to fallback to python 2.7 which does not work on your system (and on mine either at this point).
It appears to me that this issue will have to be fixed on their side. You could try and speed this up by creating an issue on their GitHub. Until then you could try the fixes mentioned at the buffalo project for this exact issue: [2].
[1] https://github.com/nodejs/node-gyp [2] https://github.com/gobuffalo/buffalo/issues/1065
blackout24 commented on 2021-01-21 21:51 (UTC)
Hi, some part of the node stack seems to rely on python2. As soon as I "pacman -Rscn python2" a "buffalo new foobar" fails: https://pastebin.com/Ed3C8KPi
theguy147 commented on 2021-01-14 22:08 (UTC) (edited on 2021-01-14 22:11 (UTC) by theguy147)
hey @blackout24, are you sure that
buffalo new foobaryields this error? I just tried it and didnt get an error. Also I wasn't aware that python is a dependency for buffalo. If so I probably should add it to the PKGBUILD but grepping through the buffalo repository I didnt find any mention of the python executable. Please let me know what Im missing here so I can help.EDIT: Also if buffalo is still using python2 in any way after its End-Of-Life this should probably be reported upstream (incl. a more verbose error description with the exact error messages)
blackout24 commented on 2021-01-14 19:31 (UTC)
Setting up a new application with "buffallo new <app>" seems to rely on calling /usr/bin/python and then interpreting some python2 code (uses print "string" instead of print("string)" which fails because /usr/bin/python is python3 on Arch. Any idea how to mitigate?
theguy147 commented on 2020-04-21 16:25 (UTC)
i agree and i just submitted a request to do so
anatolik commented on 2020-02-27 04:46 (UTC)
This package should be called
buffalo-bin