02:47:00 Anyone done an "onu"-style ON gate install on OmniOS 151044? 02:47:35 I want to build just illumos gate and overlay that in a test BE. 05:18:25 See my email (if it got approved). make sure ONNV_BUILDNUM in your env matches your current set (e.g. export ONNV_BUILDNUM=151044 ) 08:46:27 gwr - just sent an email to your thread too. This definitely should work (I do it most days). 15:00:48 Thanks. I was starting to wonder what was actually _meant_ to work, as attempts using /opt/onbld/env/omnios-illumos-gate were not going smoothly for me, and I didn't see anything about this procedure on https://omnios.org/dev/build_instructions. Thanks. 15:01:12 I'll try it again and follow up with some details about what I see. 15:01:31 Thanks, and we can get any documentation updated and things fixed if necessary. 15:01:52 I did an onu to gate bits this morning (on bloody, but that should not matter) so it works in principle at least! 15:02:09 I also might on occasion want to do an illumos build on my OmniOS server to be installed on an OI system. 15:03:08 As long as the VERSION that ends up in the packages is "newer" somehow than the existing OI packages, that should work 15:03:15 I know some people just use 9999.99.99.9 or whatever 15:03:39 The template under /opt/onbld/env picks it up from /etc/release IIRC 15:03:50 That _almost_ works for me but complained about lixml2 version (2.10.3 vs 2.10 IIRC). I guess for that to work properly I'd need an adjunct proto for OI, right? 15:04:12 but you might want to modify that anyway to adjust things like multi proto, debug/non-debug etc. 15:04:36 Every time I try to do anything clever, the pkg stuff says "no" to me :) 15:04:38 Yes, I'd guess so in that case, until they upgrade their package 15:05:43 I don't know enough about pkg to tell it "go ahead anyway, I consider those two versions close enough"? 15:06:26 If something has a dependency on libxml >= 2.10.3, then 2.10 is not going to satisfy it 15:06:41 you can use a package transform to rewrite the dependencies.. 15:07:12 it's actually not too difficult to do that to adjust a package or two in the nightly repo 15:07:32 It's actually not an adjunct you need here, come to think of it 15:07:38 cool, but that's beyond my abilities. A read through the pkg man pages did not reveal to me the magic :) 15:07:58 you need to persuade the pacakge dependency resolver to require a lower version 15:08:11 Happy to gist it if you get to needing it 15:08:44 It would be helpful. At least one of the VMs I use a lot is OI (so I can use the full X stuff) 15:08:56 and I'd rather not bother with a zone. 15:09:04 (on the build server) 15:09:22 I'll write something up and drop a link here 15:09:45 Thanks for looking into illumos 14306 (fenix) btw 15:09:47 BUG 14306: Can't get SID for ID=0 type=0, status=-9977 (New) 15:09:47 ↳ https://www.illumos.org/issues/14306 | https://code.illumos.org/c/illumos-gate/+/2630 15:10:26 Yeah, I have some more work to fix the reporting (so it can actually tell you what ID caused the problem) 15:11:41 Then we really should have a 2nd bug to fix up the cases where this complains. 15:12:55 So looking at OmniOS onu, it's a lot different from the old Sun one. 15:13:21 We don't use an on-nightly publisher? 15:13:51 Instead redirecting the omnios publisher, and turning off the signed requirement etc? 15:14:18 I think most of the important changes got upstreamed (in terms of functionality anyway). 15:14:32 Some people use on-nightly and make sure that omnios is non-sticky etc. 15:27:42 gwr: https://gist.github.com/citrus-it/d4f4479436cb7fcfe819ec4a07bf7d8f 15:28:18 you can also adjust publisher name, or the -151045 bit and so on in the same mog file 15:28:39 to massage things as needed to make OI happier 15:29:34 Thanks. Will try when I'm next ready to do things to an OI VM. 15:29:36 The example for this is example 10 in https://man.omnios.org/pkgrecv#EXAMPLES which is.. not the most obvious place to look 15:34:39 How is the publisher name specified for the build? I don't see it. 15:41:44 It should be in the Makefile.master 15:41:44 1162:PKGPUBLISHER_REDIST= on-nightly 15:42:11 and optionally overidden in the environment or .env file 15:42:35 that might be a reason you have to use the `onu` from gate, actually 16:05:50 andyf, danmcd, can one of you poke https://www.illumos.org/issues/15302 for me, please? While it isn't urgent now, I expect it to come up again with future server purchases. 16:05:52 → BUG 15302: broadcom 3108 kernel driver update (New) 16:14:42 nomad: You may wish to make sure #illumos knows about this. I don't think I'm going to have cycles for this unless one of our paying customers is asking. 16:15:15 And there might be folks in places like Nexenta/Tintri that have interest in getting this done. 16:21:54 * nomad nods 16:22:13 Thing is, we're paying omniosce, not illumos 16:22:24 I'll mention it there but was hoping for some big names to push it. 16:23:34 For things like device drivers, they need to go in upstream illumos first anyway, so it's best to alert the wider community. 16:24:01 I had hoped opening the ticket would count as alerting them. 16:24:19 Last time a lift was done here, danmcd, I think you got code from the vendor. 16:24:39 Somebody like Nexenta might have more luck doing that again 16:24:50 Yeah, via Joyent. Joyent got the code via the vendor, and passed it off to me@nexenta. 16:24:58 Otherwise the option is most likely to consider porting the driver over from somewhere like FreeBSD 16:25:21 There were some nontrivial updates from other people, and from what I can tell we won't need new code but updated code, which we probably can lift from FreeBSD.