12:07:55 <Woodstock> is gerrit broken again?
12:25:40 <andyf> I can get to it ok
13:26:36 <tsoome> I have seen few messages but it appears to be ok still
17:52:53 <sommerfeld> https://www.illumos.org/issues/16880#change-47687 is a post from someone who just registered on illumos.org which has a final sentence that looks like SEO link spam 
17:52:54 <fenix> → BUG 16880: pkglint fails on OpenIndiana with openssl mediator set to 3.1 (New)
18:22:00 <bahamat> ptribble: Are you around, by chance?
18:22:12 <ptribble> hi bahamat!
18:22:18 <bahamat> Hi!
18:22:54 <bahamat> Ok, so we're using your JDK17 for Jenkins. The latest update requires at least JDK 17.0.11, and the binaries you have are 17+35.
18:23:12 <bahamat> I was hoping you'd be able to build a 17.0.11-ga for us fairly easily?
18:23:48 <bahamat> And to complicate things, it needs to be able to run on 20181206T011455Z.
18:24:22 <bahamat> I'll check what the illumos symbol version is on that right now, but I don't remember what it is...
18:24:36 <danmcd> I'll figure that out bahamat
18:24:44 <bahamat> thanks
18:24:49 <ptribble> I presume 17+35 actually works? (Other than age.)
18:25:33 <danmcd> illumos-gate commit for the above SmartOS is 2f3d18f2c9
18:25:50 <bahamat> Yeah, it seemed to. The error I was getting is "sun.security.pkcs11.wrapper.PKCS11Exception: CKR_GENERAL_ERROR"
18:26:12 <danmcd> Libc was SYMBOL_VERSION ILLUMOS_0.28 { 
18:26:33 <bahamat> When I asked in jenkins on matrix they said that there's been a bunch of updates and mine is too old.
18:27:51 <bahamat> Yeah, I can confirm that there were at least some of our agents running on your jdk17+35 that were working until this latest Jenkins upgrade.
18:29:04 <ptribble> So I'm building on something a bit newer, I think with ILLUMOS_0.40, but java is very conservative about the libc functionality it requires
18:31:23 <bahamat> Actually, I retract my confirmation...I'm not completely sure.
18:32:23 <bahamat> A couple I checked were actually on java11...
18:33:42 <bahamat> danmcd: What libc version is 20210826T002459Z?
18:33:53 <rmustacc> If you look at the java binary with pvs it'll tell you what it requires.
18:34:04 <danmcd> Hang on...
18:34:29 <rmustacc> pvs -d /usr/lib/libc.so.1 will get you that, probably pipe to head.
18:34:41 <danmcd> SYMBOL_VERSION ILLUMOS_0.39 { 
18:34:43 <bahamat> [root@jenkins-462d490c-21-4-0 /opt/tools/java/openjdk17/bin]# pvs java
18:34:43 <bahamat>         libc.so.1 (ILLUMOS_0.26, SUNW_0.7);
18:35:13 <rmustacc> Yeah, makes sense that it has 0.26 given that was an accidental weak version.
18:35:14 <danmcd> ( 20210826 libc is 0.39 )
18:38:31 <bahamat> OK, I actually have some with 17-internal+0-adhoc.ptribble.jdk17-jdk-17-35 and some with 17.0.11-internal+0-adhoc..jdk-il-jdk-17.0.11-ga
18:38:54 <bahamat> And pvs reports ILLUMOS_0.26 for both of them
18:39:24 <rmustacc> Which means it's probably less than that but oops accidental weak version.
18:39:46 <bahamat> But maybe I can just copy it over and use it?
18:40:17 <rmustacc> Should, yes.
18:40:27 <rmustacc> At least from a libc perspective.
18:40:43 <rmustacc> There are probably other shared objects outside of illumos it links against you may need to consider.
18:40:59 <bahamat> Ok, let's give that a shot and see what happens...
18:47:11 <ptribble> My 17+35 was really intended for people to build their own
18:47:24 <ptribble> I've put a copy of 17.0.13 at https://pkgs.tribblix.org/openjdk/
18:47:33 <bahamat> Damn, no, that doesn't work.
18:47:36 <bahamat> ld.so.1: java: fatal: libc.so.1: version 'ILLUMOS_0.37' not found (required by file /opt/tools/java/jdk17-jdk-17.0.11-ga/bin/../lib/pkgsrc/libiconv.so.2)
18:48:45 <bahamat> Yeah, the thing is I need to be able to run it on ILLUMOS_0.28
18:49:19 <ptribble> And as far as I can tell (looking at all the objects) that 17.0.13 build only needs ILLUMOS_0.26
18:49:53 <bahamat> Ok, let me try that then
18:49:55 <rmustacc> It's the libiconv that's pulling it in, not Java.
18:50:29 <rmustacc> Beacuse that was built with stack protection.
18:50:48 <rmustacc> So where did you get that libiconv bahamat?
18:51:11 <bahamat> Either the PI, pkgsrc-tools, or statically linked with java
18:51:27 <rmustacc> Not statically linked.
18:51:41 <rmustacc> The path says it's /opt/tools, so probalby tools pkgsrc.
18:51:49 <rmustacc> Which to me says that you're trying to use too new a tools pkgsrc.
18:52:06 <rmustacc> If it was staically linked, it wouldn't be calling out a different shared object.
18:52:19 <ptribble> That looks like a pkgsrc build shipped with some extra local copies of the 3rd-party libraries from pkgsrc
18:52:53 <bahamat> rmustacc: But libiconv hasn't changed version
18:53:02 <rmustacc> I do'nt understand what you mean?
18:53:30 <rmustacc> ld.so.1 says libiconv.so.2 requires 0.37 which is the version that introduced the stack protector in libc.
18:54:01 <rmustacc> If you look at what java depends on, it depends on libiconv.so.2 and the libiconv.so.2 is what's too new to run on your platform.
18:54:10 <bahamat> OK, so that jdk17 came from pkgsrc
18:54:45 <bahamat> That's what you meant.
18:54:59 <bahamat> ptribble: that version of jdk17.0.13 works for me!
18:55:07 <bahamat> Awesome, thank you!!
18:55:27 <danmcd> Thanks ptribble, rmustacc, and bahamat!
18:55:42 <ptribble> Excellent!
18:56:57 <bahamat> And that was definitely faster than me picking apart dobuild until I got it to work on SmartOS :-D
19:22:22 <jperkin> bahamat: I assume you were using the 17.0.11 from https://us-central.manta.mnx.io/pkgsrc/public/pkg-bootstraps/index.html which was built on 20210826, and presumably on a platform older than that?
19:23:25 <jperkin> or did I somehow bundle the wrong libs?
19:24:09 <jperkin> I use that as the bootstrap for the openjdk21 build on the same OS so it should work..
19:28:07 <richlowe> so I have a set of changes that make java optional that come from arm64-gate, and just optionally amputate (because who's going to port java for me?)
19:28:12 <richlowe> would people like those upstream?
19:28:50 <richlowe> I don't like flags that slice off bits of build, but the java situation seems special, except for Peter being a super hero
19:42:18 <richlowe> it looks like: https://github.com/richlowe/illumos-gate/commit/68dcbda34eb6f913c8ef70b9e8c9bace07504f9e
19:43:35 <richlowe> why that's showing some of sommerfeld's changes I don't know :\
19:45:18 <ptribble> That neatly identifies our dependencies on java, too
19:48:16 <danmcd> @richlowe our use of java isn't for SmartOS per se... it's for Jenkins agents.
19:48:48 <danmcd> All of this was because bahamat couldn't get one of her Triton component builds to work.
19:49:32 <ptribble> Although it may be worth asking (again) how much of the java stuff in gate is actually useful
19:51:13 <danmcd> Oh yes... SmartOS jettisoned that WELL before I starting working there.
19:51:31 <ptribble> I *thought* I had removed it all from Tribblix, besides resource pools, but looking at that change I missed some of the bits in the dtrace tests
19:53:37 <ptribble> As for illumos on arm64, I would like to have java there too.
19:54:30 <ptribble> And it's probably easier to support than sparc, because openjdk already have a fully supported aarch64 implementation
20:24:38 <tsoome> btw, we do have rising problem with java in illumos-gate, some of the code is already deprecated and once they stop supporting those functions....  I have been looking on some cases and those are definitely fixable, but require time (as usual).
20:25:42 <tsoome> and of course testing those bits is even more interesting.
20:32:57 <ptribble> I wouldn't worry about deprecated methods too much, unless they're actually deprecated for removal
20:33:39 <ptribble> What will hit eventually is the phasing out of JNI
20:34:42 <rmustacc> If we look at the java usage the bigger things will be where do we actually rely on it from the core implementation ala poold.
20:34:59 <rmustacc> I suspect the use of dtrace_jni and similar is minimal in practice.
20:36:16 <richlowe> ptribble: the real crime is availdevs, if someone with the energy just wanted to delete it
20:36:39 <richlowe> as best as we can tell, it's only used by installers that don't exist (and perhaps never existed, really)
20:37:03 <richlowe> (I filed the bug already at least once)
20:37:09 <richlowe> it's just always having something else to do in the way
20:47:58 <ptribble> And it can't possibly work on any current distro, because it's 32-bit and no distro ships a 32-bit java
20:50:35 <tsoome> then it is axe time:D
21:15:07 <richlowe> the problem with gardening, is sometimes you have to tend to what's alive before you can dead head
22:01:22 <jclulow> https://www.illumos.org/issues/15147 for availdevs
22:01:23 <fenix> → BUG 15147: remove /usr/lib/zfs/availdevs (In Progress)
22:01:31 <jclulow> It's assigned to you richlowe lol
22:02:49 <jclulow> ptribble: It doesn't actually use Java; it's so much worse than that.
22:03:22 <richlowe> jclulow: I can drop that for anyone who wants to delete the damn thing before I get to it!
22:03:44 <ptribble> I just looked at the code, it's ... a terrible concept
22:08:05 <jclulow> Yes
22:18:40 <sommerfeld> richlowe: huh?  (didn't see anything of mine in that commit link you posted)
22:24:09 <bahamat> jperkin: Circling back...your build is fine. I copied it from a 2022 PI to a 2018 PI
22:33:47 <richlowe> sommerfeld: in my viewing it, (parts of) your ipv6 scope changes appeared in the diffs
22:36:56 <sommerfeld> Didn't see that when I looked at.  Huh.