<beerman>
jaeger: did you check if $PKG actually has the missing files though? Because thats the case for me, bsdtar looses randomly data it seems for go
<jaeger>
The created package contains all files
<jaeger>
pkgadd loses them
<beerman>
:|
<beerman>
ok
<jaeger>
tar and bsdtar both extract them ok (not sure how bsdtar does because libarchive)
<jaeger>
pkgadd and my libarchive lister fail
<beerman>
well, i exchanged bsdtar with gnu tar and 3 times in a row I get a consistent footprint and working package..
<beerman>
or 4? i dunno, I reran it a couple of times now, this 100% better than before
<stenur>
have not seen anything libarchive on FreeBSD lists
SiFuh_ has joined #crux-devel
SiFuh has quit [Remote host closed the connection]
<beerman>
this time bsdtar and a bunch of missing files
<beerman>
No idea what bsdtar is missing here though
stenur has quit [Remote host closed the connection]
stenur has joined #crux-devel
darfo has quit [Quit: Leaving]
darfo has joined #crux-devel
farkuhar has quit [Ping timeout: 260 seconds]
<jaeger>
As a possibly interesting data point I can easily reproduce the issue in an arch install... so both the linux distros I've tested (crux and arch) exhibit the issue, macos doesn't
<jaeger>
I'll test centos as well when I have time
<beerman>
nice to finally know whats actually messing with go
<jaeger>
Another interesting data point - it seems to follow the package