10:52:55 Hi, I have an asus nuc13 rugged here that prints two acpica notices to the log every 30 seconds. Seems like this is a bug in the bios, I already installed the latest version. Is there a way to ignore those messages? 10:52:57 2025-04-26T10:48:12.634269+00:00 nucgw acpica: [ID 792839 kern.notice] Firmware Error (ACPI): Could not resolve [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20180629/psargs-503) 10:52:57 2025-04-26T10:48:12.634282+00:00 nucgw acpica: [ID 780431 kern.notice] Failed at AML Offset 0005A, Opcode 002D: ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20180629/psparse-676) 14:37:20 [illumos-gate] 17295 libc: sigev_thread.c dprintf() cleanup -- Hans Rosenfeld 15:46:25 Hi everyone, I'm looking to contribute to Illumos and found this bite-sized issue (#17292, misspellings should know about "busses") and have an initial patch that fixes these across manual pages: https://code.illumos.org/c/illumos-gate/+/4232 15:46:26 → CODE REVIEW 4232: 17292 Update misspellings 'busses' in manual pages (NEW) | https://www.illumos.org/issues/17292 15:47:07 I'm not sure how to comment on Gerrit, otherwise I'd leave some shell output showing that there are no more doc files that require this change 16:23:02 naltun: Thanks for putting that up. I've made you the assignee of the issue. In general to leave a comment on gerrit if you hit the top-level Reply button, you should see a text box. When you're happy with it you can hit the "SEND" button there. 16:23:47 Similarly as you leave comments on a review on individual files by clicking the lines, a box will appear. You can type in the comment and hit "save". Those are all saved and will be batched up until you do the top-level reply. 16:24:29 that allows you to take your time commenting on things and getting us to the point that it all makes sense and will then send one batch of notifications. 20:23:26 Hi, I have detected a problem in OI that might be related to one of the latest changes in illumos-gate. 20:24:34 what's up? 20:24:48 Running GNU gettext tests today revealed a lot more failing tests compared to the original release: 20:24:50 Testsuite summary for gettext-tools 0.24 20:24:52 ============================================================================ 20:24:54 # TOTAL: 597 20:24:56 -# PASS: 561 20:24:58 +# PASS: 513 20:25:00 # SKIP: 23 20:25:02 # XFAIL: 0 20:25:04 -# FAIL: 13 20:25:06 +# FAIL: 61 20:25:08 # XPASS: 0 20:25:10 # ERROR: 0 20:25:12 ============================================================================ 20:25:26 your best bet is probably to email advocates@ in reply to the change that caused the regression 20:25:39 Cc the person who made it 20:25:54 if you don't know, file a bug and email the developer list I think 20:26:13 Building packages that use msgfmt show these errors: 20:26:14 [5/152] Building translation po/ar/LC_MESSAGES/appstream-ar.mo 20:26:14 FAILED: po/ar/LC_MESSAGES/appstream.mo 20:26:14 /usr/gnu/bin/msgfmt -o po/ar/LC_MESSAGES/appstream.mo ../../AppStream-1.0.4/po/ar.po 20:26:14 ../../AppStream-1.0.4/po/ar.po:30:9: invalid multibyte sequence 20:27:38 It builds fine running illumos-df7ed227f7 but fails with illumos-88d39f6f84 20:28:34 So my suspect is commit cfafba391b1ed9379fb2227b7c6cede40d4bf24e 20:28:52 17390 libc: iconv doesn't handle conversion to/from the same encoding when alias names are used 20:29:13 I would file a bug saying what you said above, and email Hans, Robert, and advocates@ 20:33:01 I have already tried to contact Hans on #illumos-de. 20:36:31 right no, I meant literally file a bug linked to that bug (or reply to the original, I guess), and then write an email To: all three of those addresses bringing it up (Robert is included on the vaguest offchance that getlocalename_l has woken up something weird) 20:36:59 definitely don't wait for any individual bit to work :) 20:41:21 #17400