I’m looking to help upgrade the rclone and restic packages in clear, but I’m not able to get them to build using autospec due to failed go dependencies. eg.
[FATAL] Cannot resolve dependency name: go-bazil.org-fuse
For my own learning purposes, and hopefully to help contribute to the project in future, is there something special I need to do to resolve this?
Add go-bazil.org-fuse to buildreq_ban file
Currently is a new feature for autospec that is in development.
Whenever a “Cannot resolve dependency name…” error is raised by autospec, it means that a build dependency has been autodetected that does not exist in the Clear Linux OS repo. Sometimes this occurs due to (a) a misdetected dependency, and other times, it is (b) a hint that a package is missing and should be added to the repo before continuing the build.
In this specific situation, scenario (b) applies. The new packages are detected because autospec recently gained more robust dependency detection for Golang packages, and the Clear Linux OS team has not yet added all Golang dependency (or godep) packages to satisfy those requirements.
So, until we actually add all of these packages, we will have to force autospec to build the package. My recommendation is to follow these steps:
buildreq_ban file. Easiest is to copy/paste the results/root.log file into buildreq_ban, and filter out all of its content except for the package names in question. Eventually, the team will add these packages, but it will not happen in the near future.echo make > build_pattern
make_args with: || go build -mod vendor
install_macro file containing: true
I tried to use autospec for some packages that only has make and no make install. And I ended up writing patches for the Makefile, but never realized that I can modify install_macro with true. It would be really helpful if practical examples like this are added to autospec documentation.
Boy do I have a list for this… Yes, we’re well aware of hacks like this, we’re also somewhat ashamed of them too. 