[go-nuts] Re: go mod dependency hell is real

Update ugorji to v1.7 works for me -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web

[go-nuts] Re: go mod dependency hell is real

On Tuesday, September 10, 2019 at 2:48:25 PM UTC+2, Darko Luketic wrote: > > What used to work pre go 1.13 now doesn't work anymore > > go mod is one big mess no one needs and complicates everything > I'm now getting ambiguity. How do I resolve it? > Nothing compiles anymore > > ✘ darko@wrk 

Re: [go-nuts] Re: go mod dependency hell is real

On Sat, 14 Sep 2019, 07:32 Antoine Mercadal, wrote: > Hey, > > Then why is it called mvs? I don't understand what package system would > give me 1.3.49, if I require 1.2.0 and my dependency requires 1.1.0. > Any time you don't understand why the versions have resolved in a particular way, I'd

Re: [go-nuts] Re: go mod dependency hell is real

On 14 Sep 2019, at 08:32, Antoine Mercadal wrote: > > Hey, > > Then why is it called mvs? I don't understand what package system would give > me 1.3.49, if I require 1.2.0 and my dependency requires 1.1.0. > > I'll read a bit more about it, but you may have decreased my level of go > module

Re: [go-nuts] Re: go mod dependency hell is real

Is this the issue you came across the other day, Jean? On Fri, Sep 13, 2019, 11:32 PM Antoine Mercadal wrote: > Hey, > > Then why is it called mvs? I don't understand what package system would > give me 1.3.49, if I require 1.2.0 and my dependency requires 1.1.0. > > I'll read a bit more about

Re: [go-nuts] Re: go mod dependency hell is real

Hey, Then why is it called mvs? I don't understand what package system would give me 1.3.49, if I require 1.2.0 and my dependency requires 1.1.0. I'll read a bit more about it, but you may have decreased my level of go module hate by a bit, sir :) Thanks, -- Antoine Mercadal > On Sep 13,

Re: [go-nuts] Re: go mod dependency hell is real

On 14 Sep 2019, at 01:52, anto...@aporeto.com wrote: but require 1.2.0 will not work if another dependency requires the same package at version 1.1.0 thanks to mvs. So either I'm wrong and I did not understand mvs, in that case I would like to get enlighten, or I

[go-nuts] Re: go mod dependency hell is real

Hi, but require 1.2.0 will not work if another dependency requires the same package at version 1.1.0 thanks to mvs. So either I'm wrong and I did not understand mvs, in that case I would like to get enlighten, or I got that right and that comforts me in my deep hate of mvs. On Tuesday,

[go-nuts] Re: go mod dependency hell is real

Hey Sam and Pudds, thanks for feedback and help. v1.1.7 helped. I must say go.mod is growing on me, but it's still hindering productivity or let's say a step back. If you use Goland, which probably most mousepushers like me use, since everything is under ~/go/pkg/ even with modules enabled in

Re: [go-nuts] Re: go mod dependency hell is real

Hello Darko, Rather than that 'replace' you found, a better solution is probably adding a 'require' for a more recent release of github.com/ugorji/go. Adding this to my go.mod worked for me in a simple test just now to resolve a similar error to what you reported: require

Re: [go-nuts] Re: go mod dependency hell is real

Note that replace directives are not transitive, so every single user of your library will need to do this. You can put it into your go.mod file to get your library building and get tests passing, but your users will still have to do this work as well so you'll probably want to document that they

[go-nuts] Re: go mod dependency hell is real

The answer is apparently https://github.com/gin-gonic/gin/issues/2039#issuecomment-527997733 Add this to your go.mod file: > replace github.com/ugorji/go v1.1.4 => github.com/ugorji/go > v0.0.0-20190204201341-e444a5086c43 On Tuesday, September 10, 2019 at 2:48:25 PM UTC+2, Darko Luketic wrote: