02:48:02 [illumos-gate] 17419 zen_umc logical channel IDs incorrectly determined on some platforms -- Luqman Aden 12:15:15 [illumos-gate] 17436 Want option to do broadcast reads with udf -- Luqman Aden 20:14:44 sommerfeld: I'm trying an exploratory port of idmapd to your sqlite3 bits 20:15:07 sommerfeld: one thing I seem to notice is that they have entirely separated the namespace with the '3' suffix, so if you were brave, you could probably link to both 20:41:50 richlowe: yes, I had noticed that and considered that as one way to do conversions. 20:43:13 my general thought is that the way to go is to shift the main consumer from sqlite to sqlite3 and ship a separate converter program (that can eventually be exiled to a separate package that can be uninstalled..) 20:45:40 that makes sense. It also means if I succeed in this, it would be generally useful 20:46:24 but that is involving me learning both sqlite APIs, so I wouldn't bet on success. 20:51:48 that's roughly what we did - we shipped 11.4 GA with the binaries (svc.configd, imapd, etc.) linked only against sqlite3 and had a python script we ran before the binaries to read the sqlite2 db and write it back out as sqlite3 (the python script wrapped around the sqlite CLI tool for each version, didn't try using the API) 20:53:00 in 11.4.57 we removed all that and set the minimum version IPS would allow an upgrade from to be 11.4.0, figuring 4.5 years was enough for most of our customers to have upgraded from 11.3, and the rest would just have to live with doing it in two steps 21:04:27 alanc: How do you express the minimum version for upgrade stuff? 21:05:48 depend type=origin in our system/core-os package 21:06:08 ah fascinating 21:06:52 which obviously works better when you ensure all your customers get the OS via IPS packages you built, and not a variety of different methods from different distros 21:07:26 yeah, you'd have to do it at the distribution level, but that's also where it's most useful 21:08:18 specifically, we now have: depend type=origin fmri=pkg:/system/core-os⊙144 root-image=true 21:08:30 (looks like you still call it SUNWcs) 21:08:50 it's because we're slack, and also can't remember what it was that knew that name 21:20:29 there was some stuff in the slim_source install gate, but I don't remember if there was anything else 21:29:42 richlowe: I think it's 100% slackness at this point 21:30:11 witness the slackness at https://www.illumos.org/issues/13625 21:30:12 → BUG 13625: rename SUNWcs and SUNWcsd (New) 21:37:49 we merged SUNWcsd into other packages, mostly system/kernel as you suggest there 21:38:24 and split out the optional filesystems into their own packages, as Andy suggests there 21:55:18 Yeah that seems reasonable 23:02:40 who should I ask for bulk builds these days? (want to move 17416/17421 along)