IRC channel logs


back to list of logs

***JBB-xmpp is now known as `FV
***`FV is now known as JBB-xmpp
***Server sets mode: +nt
<gnu_srs1>youpi: You changed in unbound/ from $host to $host_os. Upstream is worried about that change.
<gnu_srs1>Can we keep $host and add *-gnu*) as the last case statement?
<youpi>gnu_srs1: no
<youpi>because with $host you have linux-gnu, kfreebsd-gnu etc.
<youpi>which would be caught by this
<gnu_srs1>if all other archs are stated earlier and gnu last not problem, right?
<gnu_srs1>But I see the problem. How do we convince upstream to change to host_os then?
<youpi>by explaining them the concern mentioned above
<youpi>and let them choose the way they prefered to handle it
<youpi>either making sure of the order, or using $host_os
<gnu_srs1>As I wrote: using $host and have '-gnu*) as the _last_ statement would work. But that would exclude the last * in *linux*|Linux|*)
<gnu_srs1>youpi, seems like unbound builds fine w/o the compat/getentropy patches now when getrandom/getentropy is supported.
<gnu_srs1>No need for the -hurd.x builds any longer :)
<gnu_srs1>However this is strange: dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
<gnu_srs1>I thought file locking should be available by now.
<youpi>gnu_srs1: that was one of the point of adding getrandom/entropy support :)
<youpi>I wondered about that perl warning indeed
<gnu_srs1>I have not seen that warning since I added file locking.
<gnu_srs1>dpkg -S /usr/share/perl5/Dpkg/ libdpkg-perl: dpkg-1.17.7 was built on 2019-06-03 22:45:30, before file locking was upstreamed.