On Sun, Feb 14, 2016 at 01:22:00AM +0100, Dmitrij D. Czarkoff wrote: > Antoine Jacoutot said: > > I wouldn't call this particularly uncommon... > > You said that "This should never happen" -- ok but why, because it does; so > > what would trigger a rebuild like this? I don't know the first thing about > > the go build system. > > Generally go tries to rebuild dependencies when they are not found. > I don't really understand why this detection produces such unpredictable > results with this port. Interestingly, I can reliably reproduce the > issue when I install go-xlsx package from mirror. When I build the > package, the issue is gone. I'll try to find out during this weekend.
Great, thanks. -- Antoine
