-
Notifications
You must be signed in to change notification settings - Fork 185
after cli.GlobalString was removed Google Cloud Print Connector cannot be built #466
Comments
Ditto. Running under Fedora 30...
It used to work... |
👋 Hi @okhadkevich & @rickrich, similarly to this PR #283, this repo needs to get updated with the latest changes we made to Here's an example of someone making this update: purpleidea/mgmt#571. |
Hmm. I'm trying to migrate this at jkcdarunday@ae788e8. It currently compiles but I should do some tests first before I turn it into a PR. |
With your changes @jkcdarunday , I'm now getting:
Thanks |
@franzhildenburg |
Still doesn't work! |
I think you have to rename the "imports" that refer to "github.com/google/cloud-print-connector" to make it work under jkcdarunday's fork. E.g. in jkcdarunday/cloud-print-connector/blob/master/gcp-connector-util/init.go, rename "github.com/google/cloud-print-connector/lib" to "github.com/jkcdarunday/cloud-print-connector/lib". |
So I should file a bug report on jkcdarunday fork, then? Where are the Issues for jkcdarunday fork? $ pwd No "blob" at all!
|
You shouldn't be running |
When I'm testing the fork, what I do is the ff.: # The ff. will fail but will pull cloud-print-connector and to your $GOPATH
go get -v github.com/google/cloud-print-connector/...
# Checkout forked branch
cd $GOPATH/src/github.com/google/cloud-print-connector/
git remote add jkcdarunday https://github.com/jkcdarunday/cloud-print-connector
git fetch --all
git checkout -b migrate-urfave-cli jkcdarunday/migrate-urfave-cli
# Build
mkdir build
go build -o build/ ./... |
I have an error when building Google Cloud Print Connector:
$ go get github.com/google/cloud-print-connector/...
github.com/google/cloud-print-connector/lib
go/src/github.com/google/cloud-print-connector/lib/config_unix.go:235:15: context.GlobalString undefined (type *cli.Context has no field or method GlobalString)
I have asked a question at urfave/cli#926 and I have got an answer
urfave/cli#926 (comment)
Is there any chance to fix this problem?
The text was updated successfully, but these errors were encountered: