<ewemoa>amz3: search engines seem to suggest something about certificates -- the truth is i tried to use a program i know works elsewhere (leiningen) and it doesn't work for my local guixsd installation so i tried to find a minimal example
<ewemoa>ah, i see rekado mentioned in java.scm...may be he would know something
<rekado_>do you have nss-certs installed and the various SSL_* env vars set?
<rekado_>the URL to the lein script uses curl, so that's unrelated to IcedTea6/7.
<ewemoa>rekado_: i didn't have nss-certs installed so i installed that -- set | grep SSL shows SSL_CERT_DIR and SSL_CERT_FILE set to /etc/ssl/certs and /etc/ssl/certs/ca-certificates.crt respectively now -- running the simple java program in the pastebin still gives the error about trustAnchors parameter must be non-empty
<iyzsong>there had someone talked about certificates-java issue with mark_weaver, IIRC it's just not packaged yet.
<ewemoa>rekado_: thanks for the lead -- specifying -Djavax.net.ssl.trustStore=/etc/ssl/certs/ca-certificates.crt leads to a different error, so i'm looking into that now
<ewemoa>iyzsong: thanks for the info -- may be if that gets packaged, it will solve this difficulty...
<rekado_>I'm unaware of a discussion about anything relating to certs in Java that would require packaging. Do you have any link to the discussion? I only remember something about SSL certs in general.
<rekado_>davexunit: the configure script checks the output of "ls -t $srcdir/configure conftest.file"; in my case $srcdir happens to be "..", so there is no "configure" there, so the output of the command differs unexpectedly.
<rekado_>not sure why srcdir is ".." rather than ".", though.
<rekado_>Oddly, they seem to be okay with sending email (and I extracted my most recent contribution from an email to bio-packaging); I can only guess that it's the unfamiliarity with another approach + the perceived high barrier that keeps them from submitting a proper patch via email.
<amz3>rekado_: there is an opensource software that does Pull Request and is written in Python
<rekado_>Personally, I find sending patches via email so much more easy than using Github.
<davexunit>Steap: the github style review process is a bad one. I do github based reviews all the time.
<amz3>github is a no go, but I'm not sure why web Pull Requests are bad, it can lead to a lot of noise I understand that.
<davexunit>amz3: they discourage clean patch sets in favor of a base patch set plus a ton of "fixup" commits in response to feedback
<rekado_>davexunit: I mean, some people currently have .spec files in their public repos (and they have no idea where to send them to to have their package adopted by Fedora/CentOS/etc). I think we *do* want those contributions, even if they don't result in an increase of regular contributors.
<davexunit>of course, you can use git push --force to rewrite the history
<davexunit>"And the fact that other projects apparently have so low expectations of commit messages that these things get used is just sad. People should try to compare the quality of the kernel git logs with some other projects, and cry themselves to sleep."