Update go.mod to v5

[bminer]

Closes #125

[bminer]

Once merged, please tag the release v6.0.0. Thank you!

[bminer]

After I thought about this a little bit, I think we could safely change this to v5 and release under tag v5.0.2.

Running go get github.com/godbus/dbus/v5 would never match 5.0.0 or 5.0.1 because they are technically invalid semver tags according to Go.

[bminer]

Let me know what the best course of action is here.

[jsouthworth]

Just so I'm clear, are you proposing using v5 instead of v6 in the .mod file and having me tag that as v5.0.2?

If that is the case then that seems the right way to go.

[titanous]

Would it be possible to get the v5 change/tag pushed soon? This currently breaks downstream consumers using go mod.

[bminer]

@jsouthworth - Yes. v5 in the go.mod. Tag as 5.0.2. All users should then see dbus/v5 as v5.0.2.

[jsouthworth]

@bminer can you update the PR with v5. Then I'll merge and tag a release.

[bminer]

Yes. Doing it now...

[jsouthworth]

Thanks @bminer, the release has now been tagged.

[bminer]

Thank you, sir!

[jsouthworth]

Unfortunately, it looks like there is still something missing here. I set up a simple test and end up with:

module jsouthworth.net/go/test

go 1.12

require (
	github.com/godbus/dbus v4.1.0+incompatible // indirect
	github.com/godbus/dbus/v5 v5.0.2 // indirect
)

This is probably because we have imports in the submodules that don't reference v5.

[bminer]

@jsouthworth - Could be another submodule like you say, but you can always try go mod tidy and see if it fixes things.