<g_bor[m]>I have a confgi with opensmtp and postgresql. It was working for a while, but now suddenly all files in /var/lib/postgres got chowned to smtpd:smtpq, and postgres no longer starts, unable to accessing its files...
<pkill9>oh actually the weechat package definition adds the main dependencies for plugins
<pkill9>kmicu: i was just thinking of plugins that require python libraries
<shtwzrd>civodul: aha! Yes this sounds like my issue. I'm re-running now and will see if my stack looks similar, but this seems likely. I'll keep trying to re-run it, not using this machine for anything else atm. Thanks for your help :)
<pkill9>weechat itself calls the interpreter though, so wrapping the plugins themselves wouldn't work anyways
<civodul>shtwzrd: yeah, i'm sorry for the breakage
<kmicu>pkill9: Heh, you could start using glirc and write everything in Lua and Haskell tho not sure that fits your definition of simpler 😺
<kmicu>(Or use basic features of weechat and configure the rest in weechat.el so elisp x)
<pkill9>what's weechat.el? emacs interface for weechat?
<kmicu>Yep. We can use Emacs and its ecosystem as shell to weechat so a lot of weechat plugins are no longer necessary.
<civodul>nckx: like i wrote, the dates in the future and also lack of info prior to Oct. 2019
<nckx>civodul: Missed that message. Since they're blank I read the future dates as boilerplate ‘fill this in as we go’, or some idiosyncracy of their export software? It's not like we're signing off on the 30/09 number. The missing prior info is a bit unhelpful but, well, I don't really know how the FSF usually does this. I can always ask for more info if you want, you're probably busy packing.
<nckx>To give them the benefit of the doubt: you asked for ‘an overview of our bucket’ which leaves a lot of room for interpretation.
<civodul>nckx: right, initially i just wanted the current balance
<nckx>jonsger: No worries 🙂 's Just my own frustration at the state of my contributions. My two current jobs (skiing & motorcycling instructor), as rad as they are, combine extremely badly with the quick-package-while-nobody's-looking lyfestyle & I miss that.
<nckx>So here I am fixing home pages & helping folks on IRC during meals.
<zimoun>Unrelated, but trying to debug, "guix build -L my/suff my-pkg -K" fails and then "guix environment --container -L my/stuff my-pgk" and "cd /tmp/guix-build-blabla" and the usual "cmake ../source/" success. And one main difference is the flag: build uses -I/gnu/store/...-depends-1.67/include and environment uses -isystem/gnu/store/...-profile/include (pointing to the same store item than -I). I was expected exactly the same thing... Well,
<zimoun>is it expected or am I doing something wrong?
<bavier>zimoun: -i declares a "system include" which is searched prior to other include directories
<bavier>this can make a difference if a header of the same name is present in multiple places in the search path
<bavier>and may affect the preprocessor macros defined for later headers
<zimoun>nckx: #:configure-flags '("-DCMAKE_CXX_FLAGS=-Wno-error") seems to prepend and there is not effect. I have not found the rule in 'man gcc' when -W and -Wno- is given in the same time. Probably -W wins.
<nckx>I think it's just flag order (last one wins), but I'm not certain.
*civodul shamelessly borrows from the illustrations rekado_ made last year
<nckx>Of course things might get ‘interesting’ when you combine general (-Werror) and more specific (-Wno-foo-error) ones.
<zimoun>nckx: I never debug builds that way neither. But I do not understand why "guix build" fails. I thought it was about -Wconversion (turned on error with -Werror) but then inside "guix environment --container" compiling does no fail, so I was just asking myself why?
<nckx>Ah, fun 🙂 Does the build print the full command lines? Is -isystem really the only difference? If you're really stuck, paste a link to the full ‘guix build’ log here or send it to help-guix@.
<cschorn>how do i change config files in a per user environment? I am trying to use local apache/php on ubuntu for development
<lispmacs[work]>I remember reading a while back about some kind of package that allowed you to turn multi-step processes into guix packages. I was interested in that again but can't remember the name of the project...
<cbaines>lispmacs[work], maybe the Guix Workflow Language?
<zimoun>bavier, nckx: I have solved the issue and finally I did what I did not want... open the CMakeFile os the package. So, the CMakeFile owns an option to turn off the option, i.e., remove -Werror of the flag. Well, the problem with myself is not solved... I do not understand something, but the package builds. Thank you for the help.
<lfam>Specifically the xmlsec-nss package, but I have the same issue with the default xmlsec package, using gnutls, as well as a private xmlsec-openssl package
<bavier>zimoun: sometimes digging in is all that can be done. Glad it works, the rest can be figured out some other time
<lfam>Now I'm reading the build log of xmlsec-nss, but I'm grasping at straws because I don't know in what cases the executable would ignore RUNPATH
<lfam>The other thing is that while searching for things like "xmlsec runpath" I find a few bug reports on the subject filed with the xmlsec project, and the maintainer there just posts a link about how shared libraries work