Re: Bug#999544: Package new upstream version
[context for the list: I'm working on upgrading the golang-v2ray-core
package to the latest upstream. i'm kind of stuck on a problem I can't
figure out.]
Thanks, those patch are great. I think it might be better to use build
tags to disable that functionality than to rip it out with a patch, but
I'm happy to carry the patch set for now.
It also seems to work, to the extent that the patch applies and I can
get further in the build. I had to disable protobuf regeneration because
that was failing with an error:
Regenerate v2ray.com/core/app/reverse/config.proto
github.com/v2fly/v2ray-core/v4/app/reverse/config.pb.go: while trying to create directory ./github.com/v2flyRegenerate v2ray.com/core/app/browserforwarder/config.proto
: Permission denied
This could just be a tooling issue on our side, but there's a newer
protobuf dep in experimental that we can use for now, so I dodged that
problem by targeting experimental for now.
The next hurdle is that the build fails on what looks like a go mod
issue:
make[1]: Entering directory '/<<PKGBUILDDIR>>'
DH_GOPKG="v2ray.com/core/main" dh_auto_build -- -ldflags "-s -w -buildid= -X v2ray.com/core.codename=user -X v2ray.com/core.build=20220505-203716 -X v2ray.com/core.version=4.45.0"
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 2 -ldflags "-s -w -buildid= -X v2ray.com/core.codename=user -X v2ray.com/core.build=20220505-203716 -X v2ray.com/core.version=4.45.0" v2ray.com/core/main v2ray.com/core/main/confloader v2ray.com/core/main/confloader/external v2ray.com/core/main/distro/all v2ray.com/core/main/distro/debug v2ray.com/core/main/json v2ray.com/core/main/jsonem
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
src/v2ray.com/core/main/main.go:17:2: cannot find package "github.com/v2fly/v2ray-core/v4" in any of:
/usr/lib/go-1.18/src/github.com/v2fly/v2ray-core/v4 (from $GOROOT)
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/v2fly/v2ray-core/v4 (from $GOPATH)
... there's a bunch more of those, naturally.
Dear Debian go folks, how do we typically solve those issues?
Do we have any other "go mod" package around? How do they handle those
problems?
Build log is attached, code lives in the debian/experimental branch on
salsa:
https://salsa.debian.org/go-team/packages/golang-v2ray-core/-/tree/debian/experimental
Thanks!
--
Power is always dangerous.
Power attracts the worst and corrupts the best.
- Edward Abbey
Reply to: