13:38 <stenur> yes sometimes silly; also some options of mutool do not really seem to do useful work, i once had an upstream issue but there was maaaaaaany interest, and a bug report took months.

13:40 <stenur> Regarding tz i just used -f. I just wondered what was going on, file permissions etc did not unravel why it refused to simply update. Overwriting files is just normal business for pkgadd -u right, so maybe a bell rang. If not, also good.

13:58 <farkuhar> stenur: Overwriting files IS normal business for pkgadd -u, but it aborts if the files being overwritten aren't recognized as belonging to the package you're upgrading. That's why I think it's a bug or a database corruption when 'pkginfo -o' reported no owner for the file in question.

14:38 <stenur> farkuhar: sounds logical, but is not true for the package in question

15:59 <stenur> farkuhar: indeed glibc 2.34 installed its own zdump! So that was that.

16:21 <farkuhar> stenur: glad to hear you found the conflict! I wonder what other packages glibc might clobber with its overly-ambitious footprint.

16:36 <beerman> 😂

16:51 <stenur> You seem to need --disable-timezone-tools for configure in 2.34.

16:52 <stenur> No i did not check the footprint for my glibc overlay. Nor gcc.

16:54 <stenur> Just wondering why they default to something that for decades was handled different by downstream users; why they do it at all (though or even though maintainer overlap)

17:00 <braewoods> stenur: now it can finally take its own core dump.

17:03 <stenur> braewoods: ??

17:11 <braewoods> stenur: bad joke, nevermind