cmd/version: add support for openbsd/386

[ivandeex]

The associated forum post URL from https://forum.rclone.org

N/A

What is your current rclone version (output from rclone version)?

master branch

What problem are you are trying to solve?

rclone version is a stub for openbsd/386.

When I merged #5402 I thought that upstream issue tklauser/go-sysconf#21 depends on the core golang schedule.
Now that @tklauser closed it in less than a week I see that in fact https://github.com/tklauser/go-sysconf depends on fast-moving https://pkg.go.dev/golang.org/x/sys?tab=versions

How do you think rclone should be changed to solve that?

• Submit pull request for shirou/gopsutil to upgrade to tklauser/go-sysconf v0.3.8
• Submit pull request for rclone to upgrade gopsutil when v3.21.8 is out, then remove the build hack

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

[tklauser]

The associated forum post URL from https://forum.rclone.org

N/A

What is your current rclone version (output from rclone version)?

master branch

What problem are you are trying to solve?

rclone version is a stub for openbsd/386.

When I merged #5402 I thought that upstream issue tklauser/go-sysconf#21 depends on the core golang schedule.
Now that @tklauser closed it in less than a week I see that in fact https://github.com/tklauser/go-sysconf depends on fast-moving https://pkg.go.dev/golang.org/x/sys?tab=versions

FWIW, during the Go development freeze (see https://github.com/golang/go/wiki/Go-Release-Cycle for details), x/sys is usually frozen as well (i.e. id depends on the core Go development schedule) because is vendored into cmd/vendor. Thus the CL above was blocked from being merged for a week. We were lucky that the development cycle opened just today 😄.

How do you think rclone should be changed to solve that?

1. Submit pull request for https://github.com/shirou/gopsutil to upgrade to https://github.com/tklauser/go-sysconf/releases/tag/v0.3.8

I've submitted shirou/gopsutil#1117 a few minutes ago bumping go-sysconf in gopsutil.

[ivandeex]

@tklauser Got you. Thanks a lot.

[tklauser]

@ivandeex FYI, gopsutil v3.21.8 was released some hours ago and should contain the bumped go-sysconf (shirou/gopsutil#1117), hopefully allowing this issue to be fixed.