02:33 <jaeger> Do we have a fix for cryptsetup and libuuid broken by the util-linux update? I would probably just disable static cryptsetup for my own uses but I doubt everyone would agree with that

02:51 <jaeger> Just discovered that building util-linux 2.40 with autotools instead of meson fixes this problem

03:02 <jaeger> http://sprunge.us/uwktCU

03:03 <jaeger> I'm going to revert it to autotools for now, if we have/find a solution for the meson build differences we can update it

03:41 <jaeger> bit of anecdotal data, from an archlinux container:

03:41 <jaeger> [root@04deb1311f69 ~]# pacman -Q util-linux-libs

03:41 <jaeger> util-linux-libs 2.40-1

03:41 <jaeger> [root@04deb1311f69 ~]# objdump -t /usr/lib/libuuid.so | grep -i uuid_generate

03:41 <jaeger> [root@04deb1311f69 ~]#

03:41 <jaeger> Also missing there

09:36 <beerman> I'd rather have kept the broken cryptsetup than reverting to use autotools there

09:58 <beerman> I did the honors to open a ticket with util-linux to check up why the static uuid reports to not have the clear function

11:20 <jue> jaeger: thanks for your fix to util-linux

11:20 <jue> the whole 2.40 release seems to be hardly broken at all

11:21 <jue> while building with autotools the new lastlog2/pam_lastlog2 library fails with missing sysmbol ->

11:22 <jue> PAM unable to dlopen(/lib/security/pam_lastlog2.so): /lib/security/pam_lastlog2.so: undefined symbol: ll2_write_entry

11:23 <jue> though, that works with the meson build :(

11:27 <beerman> the only problem I can see with util-linux (which is outstanding) is the broken build with cryptsetup which seems to fail to find uuid_clear for me

11:27 <beerman> I opened a ticket for that: https://github.com/util-linux/util-linux/issues/2895

11:27 <jue> lvm2 fails as well

11:27 <beerman> let me check

11:28 <jue> the static libraries are broken at all, IMO

11:30 <jue> the PAM error, I've reported above, is not important, cause our default PAM setup don't include lastlog2 in /etc/pam.d/login

11:46 <beerman> yeah, I see the problem with lvm2, might be worth another bug report, I opened one for the compat-32 build yesterday which got a quick patch that works

13:34 <farkuhar> jue: the pam_lastlog2 issue might be present in both meson and autotools, according to https://github.com/util-linux/util-linux/pull/2894

13:52 <jaeger> jue: no problem

13:57 <farkuhar> one of my builds of util-linux#2.40 generated a bunch of man-pages that don't appear in the footprint, and some of them would have clobbered the man-pages owned by other ports. Hence it wasn't enough to set PKGMK_IGNORE_NEW=yes, I had to force the update by hand.

13:59 <jaeger> beerman: it's kinda interesting that you ran into uuid_clear rather than uuid_generate, I wonder if that's simply a parallelism difference

13:59 <beerman> I changed cryptsetup to meson and this seems to report a different problem, but I suspect them all to have the same cause. Not sure yet, let's see how the ticket plays out

17:05 <jue> farkuhar: as I wrote, pam_lastlog2 works for me with the meson build

17:16 <farkuhar> jue: same here, successful build with meson. On the other hand, having asciidoctor installed is what triggers the creation of man-pages that would clobber the footprints of other ports: http://sprunge.us/S1GXW5