jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
darfo has quit [Ping timeout: 265 seconds]
darfo has joined #crux-devel
genpaku has quit [Read error: Connection reset by peer]
genpaku has joined #crux-devel
SiFuh has quit [Ping timeout: 252 seconds]
SiFuh has joined #crux-devel
chrcav has quit [Ping timeout: 265 seconds]
chrcav has joined #crux-devel
<jaeger> I'm going to go ahead and push the libbsd update today to move it to a nonstandard path
<SiFuh> jaeger: which path did you decide?
<jaeger> Currently /usr/opt/libbsd, I still prefer to leave /usr/local and /opt out of package management
<SiFuh> It will do for the time being though.
chrcav has quit [Ping timeout: 252 seconds]
chrcav has joined #crux-devel
<jaeger> hrm... anyone having trouble with dhcpcd 9.4.1 getting a lease successfully?
<jaeger> I'm getting problems with it on a VM but it's working fine on other hosts... very odd
<jaeger> downgrading that VM to 9.4.0 works
jue has joined #crux-devel
jue has joined #crux-devel
jue has quit [Changing host]
<darfo> i'm using qemu 7.1.0 and dhcpcd works but that is with a -net user network not a real one
<darfo> d'oh. I see that is a fresh install of 3.7 so dhcpcd is version 9.4.0.105
<jaeger> I've tested this same VM on both a crux libvirt install and ovirt... same result. 9.4.0 works, 9.4.1 doesn't
<jaeger> both using qemu, though
<darfo> i upgraded to dhcpcd to 9.4.1 and it is failing for me to now
<darfo> curious, ps -ef|grep dhcpcd shows way less threads with 9.4.1 than with 9.4.0.105
<jue> yep, the problem is that we accidently committed an update to 9.4.1, the version from the ISO works with our glibc
<jaeger> I just tested on a physical machine too, same issue
<jaeger> ok, so 9.4.1 and glibc have some problem?
<jue> yes, that's the reason why I've created the 'special' version 9.4.0.105, which includes the fix
<jue> the version number is a bit odd, it's the 105th commit since 9.4.0, which I've extracted from the REF's
<jue> I'll revert the last commit
<jaeger> ok
<jue> done, should work again ;)
<jaeger> cool, thanks
<jaeger> just glad I'm not going crazy :)
jue has quit [Ping timeout: 246 seconds]
<stenur> i btw got only one mail for four bug reports; maybe someone was currently working on the server, that can well be. just to mention it.
<jaeger> I only see one attempted mail to you in the mail log for today
<jaeger> for what that's worth
<jaeger> I cherry-picked the latest mesa-32 and llvm-32 updates from 3.7 into 3.6, just FYI
<jaeger> I've still got a 3.6 system with wine-staging on it that I'll be using for a while
groovy2shoes has joined #crux-devel
<jaeger> beerman: mind if I update the .signature for libgnome-keyring?
<farkuhar> earlier today i tried to reproduce the dhcpcd 9.4.1 failure, but still got a lease for my laptop on that network. Now from my desktop, on a different network, upgrading to 9.4.1 leads to breakage. Both connections were wired ethernet. I wonder if the DHCP server on the first network was responding in a way that didn't trigger the 9.4.1 bug.
<jaeger> Could be, I suppose... what are you using as the servers on those networks?