10:31 <cruxbot> [contrib.git/3.6]: remind: update to 04.00.01

10:31 <cruxbot> [contrib.git/3.6]: pmwiki: update to 2.3.5

10:31 <cruxbot> [core.git/3.6]: vim: update to 8.2.5054

10:31 <cruxbot> [opt.git/3.6]: gvim: update to 8.2.5054

10:31 <cruxbot> [opt.git/3.6]: nss: update to 3.79

10:31 <cruxbot> [opt.git/3.6]: libunbound: update to 1.16.0

10:31 <cruxbot> [opt.git/3.6]: xfsprogs: update to 5.18.0

13:52 <farkuhar> ppetrov^: regarding "jasper breaks if texlive is installed", did you mean that it fails to build, or that you get runtime errors after installing?

13:53 <ppetrov^> fails to build

13:53 <ppetrov^> i removed texlive and all was fine

13:54 <farkuhar> can you post a link to your build log? I upgraded to the latest jasper just fine, without uninstalling texlive first.

13:55 <ppetrov^> well, i try to rebuild now

13:56 <ppetrov^> https://pastebin.com/MSArHiW4

14:00 <farkuhar> ppetrov^: thanks. I believe the texlive port needs some tweaking to ensure that formats are correctly generated and symlinks installed in $PATH. The port that i'm using is a slight reworking of the one in contrib, with some steps moved out of build() and into post-install.

14:01 <ppetrov^> thanks, i was wondering if I messed up something

14:02 <ppetrov^> libmnl here created some man pages that overlap with stuff already installed. I will investigate what causes it and report here...

14:29 <SiFuh> No it doesn't

14:29 <SiFuh> Only yours does

14:29 <SiFuh> Hahaha

14:51 <ppetrov^> yes, hilarious

19:11 <ppetrov^> ok, lubmnl had some problem with doxygen being installed and a bunch of man pages were included in the package

19:12 <ppetrov^> when i removed doxygen at build time, all was fine

19:13 <stenur> granted i built libmnl last in April, but always had doxygen

19:14 <ppetrov^> i just report what happens on my install... the deeper reasons i do not know

19:15 <stenur> sure

19:16 <ppetrov^> or maybe SiFuh was right and it happens only here... :p

21:39 <farkuhar> grep -lrs LIST_ENTRY in the libmnl source tree returns only one hit: examples/netfilter/nfct-daemon.c. Maybe the port maintainer can add a test for the presence of doxygen, and if so, run sed '/GENERATE_MAN/ s/YES/NO/' doxygen.cfg.in, which will avoid the filesystem conflict that ppetrov^ discovered.

21:42 <farkuhar> but if disabling the creation of all manpages is too drastic, it looks like that same doxygen.cfg.in gives you finer control over which manpages are generated.