From nobody Sat Jan 28 15:46:39 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P3zMd3DFDz3b9GM for ; Sat, 28 Jan 2023 15:46:53 +0000 (UTC) (envelope-from maxsteciuk@gmail.com) Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P3zMc0czSz40Wp for ; Sat, 28 Jan 2023 15:46:52 +0000 (UTC) (envelope-from maxsteciuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=MzIThnV9; spf=pass (mx1.freebsd.org: domain of maxsteciuk@gmail.com designates 2607:f8b0:4864:20::82c as permitted sender) smtp.mailfrom=maxsteciuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qt1-x82c.google.com with SMTP id v19so6529286qtq.13 for ; Sat, 28 Jan 2023 07:46:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version:from :from:to:cc:subject:date:message-id:reply-to; bh=FuSBZ8x3sS+r/pXaiFu+CW9gHTXl5NwBs//zA+WneGo=; b=MzIThnV9m2OTz56hW+FSOBTv/4rDYDuD9xg54lSeNKF/+ZjTyrJ78qvovfvgudTalx ozT90YZm/YNASJDPKiWilnQxacif3t7a67cU2OSn7FqXrhVtsRlHiykJf0MiliEpATjc 0fr8JrCSo0vPDX3umf1JzFY/HPy4IxAVipVrFrtaucA85kHL0OMpPamVw3/kyfZsFAWR A1PFkZfR1N8yvJs4iOcaHttYX+ThkV5KgWOQyjlfNXuuA+6LhMb2RQPvWXz/o1O9/t1t KCDV3pkeRfyh71KuP4iH6hMGmoOQDx/SIuZsZ+UA8nXNTdAzWl8dpzOsyL/coG5WH359 z5eQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FuSBZ8x3sS+r/pXaiFu+CW9gHTXl5NwBs//zA+WneGo=; b=UiZwMaL0faBUzETf3SLzOT2M6xl4xZBMuwYqBo73Lbq0EdU7Kp29OukpnrOYbeCjAe 5l8RV8RpxydQxuVjRio2K35wMch7uaQe8iHr+48p6KGEviBHr0OwbbPYhZsYENGhlHT/ v7Ur5P2P3xZlH+uYqIe9p+8em2s4vyuxvcAhAlzpyVa4Rh38u5g4fofZGlF2otJgU6JC MFX7s4NxW6TTZbWTic6uBiwXWfGutRaWSmBLETyIMEtuS5VV4dJcjZNZbeV7bTRCO0ci RQfAAx17muuxSnqjcfwf8p9doZ+7q3K9f0AgqmyU+elMFcfZZiNxCz+wFGCM8MgNouae 9oWg== X-Gm-Message-State: AO0yUKXVxprd+B8l/7HunmC9HrlTyO7Wmxz3DQwChl6418LbaVQ11n9r 2V6xdkELDOxAruCLZKZ0uzYaw0ub8M4= X-Google-Smtp-Source: AK7set+r5PN3oqJ+8rKWNPV3nbfbXi8CvX3Pu2x3rNCltMM48dV/MPcTUEEQEF6wcqm4256XnjVejQ== X-Received: by 2002:ac8:7f89:0:b0:3b8:588c:40e9 with SMTP id z9-20020ac87f89000000b003b8588c40e9mr802276qtj.19.1674920810860; Sat, 28 Jan 2023 07:46:50 -0800 (PST) Received: from smtpclient.apple (pool-100-2-131-189.nycmny.fios.verizon.net. [100.2.131.189]) by smtp.gmail.com with ESMTPSA id i18-20020ac80052000000b003b82489d8acsm2960540qtg.21.2023.01.28.07.46.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Jan 2023 07:46:50 -0800 (PST) From: Maksym Stetsyuk Content-Type: multipart/alternative; boundary="Apple-Mail=_3E78583A-6512-4506-9331-028899E1E0CE" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\)) Subject: Re: 14.0-CURRENT fails Norelsys NS1081 Date: Sat, 28 Jan 2023 10:46:39 -0500 References: To: Innocenti Maresin , freebsd-current@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3731.300.101.1.3) X-Spamd-Result: default: False [1.10 / 15.00]; MIME_BAD_ATTACHMENT(1.60)[ico:image/vnd.microsoft.icon]; URI_COUNT_ODD(1.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[0.997]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain,multipart/related]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::82c:from]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org] X-Rspamd-Queue-Id: 4P3zMc0czSz40Wp X-Spamd-Bar: + X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_3E78583A-6512-4506-9331-028899E1E0CE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello, I also experienced the same issue on the 13.1 branch. I found the = following bug report opened with proposed patch. After rebuilding with = the patch NS1081 was successfully attached and I was able to mount it. = Could you please let us know if the patch is going to be applied to the = 13.1-STABLE? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263868=EF=BF=BC Thanks Max > On Jan 27, 2023, at 23:27, Innocenti Maresin = wrote: >=20 > By the way, the same error happened to > FreeBSD-13.1-STABLE-amd64-20230120-4a8af507ebe5-253535, > hence it does not seem to be specifically a CURRENT issue. >=20 > --Incnis Mrsi >=20 --Apple-Mail=_3E78583A-6512-4506-9331-028899E1E0CE Content-Type: multipart/related; type="text/html"; boundary="Apple-Mail=_8071450C-E193-44AD-BB57-95F92E5A4391" --Apple-Mail=_8071450C-E193-44AD-BB57-95F92E5A4391 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hello,

I also = experienced the same issue on the 13.1 branch. I found the following bug = report opened with proposed patch. After rebuilding with the patch = NS1081 was successfully attached and I was able to mount it. Could you = please let us know if the patch is going to be applied to the = 13.1-STABLE?

3D"fbsd_favicon.ico"

Thanks<= /div>
Max

On Jan 27, 2023, = at 23:27, Innocenti Maresin <innocenti.maresin@gmail.com> = wrote:

By the = way, the same error happened = to
FreeBSD-13.1-STABLE-amd64-20230120-4a8af507ebe5-253535,
hence = it does not seem to be specifically a CURRENT issue.

--Incnis = Mrsi


= --Apple-Mail=_8071450C-E193-44AD-BB57-95F92E5A4391 Content-Transfer-Encoding: base64 Content-Disposition: inline; filename=fbsd_favicon.ico Content-Type: image/vnd.microsoft.icon; x-unix-mode=0666; name="fbsd_favicon.ico" Content-Id: <2FED738C-2C2C-43D3-BF5D-8138E55165FA> AAABAAIAEBAAAAEAIABoBAAAJgAAACAgAAABACAAqBAAAI4EAAAoAAAAEAAAACAAAAABACAAAAAA AEAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAADwMCACMDAQAk AAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANDAYyKyxGlykrgdMn LJrpJkKo6SBjmdQiS1ebDAoHNgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAvLy5uQEKY7xYc z/8EEdz/AhnX/wIl6v8HQPf/G3P+/1eIxfMyMjZ3AAAAAgAAAAAAAAAAAAAAAAAAAAA5OTNrUlOs /gADwf8ADMj/ARvM/wIozf8DM9v/Azrj/wBA7v8UX/7/d5fm/zc2OHYAAAAAAAAAAAAAAAAQEAks c3Oa5wcKuP8AD8//Ah3T/wIn1P8CH7r/ARO9/wEStv8BHsT/ATHS/yhV5/+Kk8XuDw0INQAAAAAA AAAAWlpXikVHtf8ACMj/Ah7b/wIl3f8ADMT/AACS/wAAsf8AALD/AACo/wAAk/8EFan/jMn//2Fq Y5YAAAAAAAAACW9uh8USH8T/ABzd/wIp5f8BDtb/AADG/wAAoP8AAKP/AAC7/wAAuP8AAJT/AAB1 /0Z11f+PrazPAAAADgcGABdqbJ/cAh7e/wAn6f8CJOf/AADa/wAA1/8AALb/AACm/wAAof8AAK7/ AACr/wAAd/8KEpf/gpm75QgGACEEAwAXc3mo3DBn7/84dvT/AB/p/wAA5f8AAOX/AADJ/wAAuP8A AKX/AACR/wAAj/8BAX3/CAt3/258peQKCQMfAAAAB3+AlsGcv/7/2PH+/0579f8AEvL/AADy/wAA 2v8AAML/AACt/wAAmf8MC4P/JSRx/0dOiP9yeozMAAAADQAAAABWVVeB1t///+bv/v/c7f7/h6H8 /z5f/P8hNez/JiXP/ykpvv8/P7H/Jiil/xwdl/+Eh8H/XV5ajwAAAAAAAAAAFBMiU8vM5f/2+/// +fz+/+Pl/P/I2vz/ttL7/7jJ9f/Oz+//p63l/0pY9v8AAL7/Skqv/yUlL10AAAAAAAAAAAsLV6U5 PL//5OX9//7////z9v7/6PP9//Dy/P/y+v7/x8/v/7bD7v/6/P//XWfv/wcJsf8eHmGrAAAAAQAA BCQAAILnJi3V/6ay///m6+77///9/////////////////8TE8v+RmeP/4uvy++Xr//9ZX+D/AAGI 7AAABigAAAMiDQ921GRpt987RWqOJCcuTIKCgYzAwMDH2NjX39PT1+C/wMPJk5KPjC0xNkpGTWWK bHC43AsNedkAAAQmAAAAAQEBAxoBAQIWAAAAAAAAAAAFBQUAFhYWCiMjIxslJSQbGxsaCwwMCwAB AQEAAAAAAAAAARQAAAMbAAAAAvw////wD///4AP//8AD//+AAf//gAH//wAA//8AAP//AAD//wAA //+AAf//gAH//4AA//8AAP//AAD//xw4//8oAAAAIAAAAEAAAAABACAAAAAAAIAQAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAACAAAAAwAAAAMAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAgAAAAcAAAASAAAAIQAAADAAAAA7AAAAOwAAADMAAAAiAAAAEgAAAAcAAAACAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAABAAAABEAAAAvCgkDZycmKJwwMVHAMjRo3Dc8deQ9QnjlNEpx3iFJXsUZ MjegCwoIbQAAADIAAAARAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAqFRUNeFNUYtJUWKb8SE7P/zA23P8nMNz/KTTf /ytB7P8faPj/JJb+/zOw9/87osv+PGd32BoVFIIAAAAwAAAADgAAAAEAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAQAgIAS1FRTr11eLn+MDbS/wcNzf8A Bcv/AAjS/wAPzv8AFMn/ABjg/wAc5P8CKOj/CUDu/xx7+/87u///bKzZ/1FRXcsHBQJYAAAAEwAA AAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAFQ0NCGOIiZLmW1/L /wUHtf8AALz/AAjK/wAQ0f8CFtX/AhzP/wIhzv8CJd//Airh/wIt5P8CMOj/ADHr/wRG8P8sjP3/ kbj//3+Kpe8UEg9xAAAAGAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAA4L CwhhoaGm61JVwv8AAJ3/AAW8/wEMyP8BEcj/AhbK/wIbzv8CIcj/AibO/wIq2v8DMN3/AzTh/wM6 5f8DP+r/AkDt/wBC8P8tbPL/lbj//4+Zs/QWFRFxAAAAEwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAJAAAAR6KioeFsbsL/AACT/wEHv/8BDMb/ARHH/wIWyf8CHMz/AiDQ/wIlw/8CLM7/ AzLY/wM43P8DPuH/A0Pm/wRI6v8ETO3/BE/w/wBH5v8pYOj/orr//5CWquwIBwRWAAAADAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAwAAACVnZ2CyqKnW/wAAg/8AB8H/AQ3J/wESy/8CF87/AhzQ/wIh 0v8CJ9b/Ai7J/wMw0f8DK9L/AifK/wIjxP8CKMn/AzXX/wND4/8IT+z/DU3g/wc/2v9DZ+X/ucX+ /2Zma8UAAAAuAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAOFRUTatPT1vozM5H/AACq/wEOz/8BEs7/ AhfR/wId1P8CIdb/Aina/wIq2v8CHKv/AAil/wAAs/8AAKz/AACn/wAApP8AAKb/AAKw/wMVw/8L MsL/FULR/xI30/91h+3/wcrg/yQjIX4AAAARAAAAAAAAAAAAAAAAAAAAAQAAACWFhX/AoKDP/wAA iv8ADsj/ARPT/wIY1f8CHdj/AiPb/wIq3v8CItj/AAe+/wAAh/8AAJP/AAC5/wAAtP8AALH/AACt /wAAqP8AAKb/AACp/wAAiP8HEZ//HDvY/0h87f/N8f//hoyL0QAAADAAAAACAAAAAAAAAAAAAAAF BwcFUcfHx/I3OKL/AAWk/wETzP8CGNn/Ah3a/wIi3f8CK+H/AiDa/wACxv8AALn/AACT/wAAj/8A ALH/AAC9/wAAtv8AALP/AACu/wAAqv8AAKX/AAB//wAAgf8KErH/Uanz/7D////H2tr+FRMTZwAA AAcAAAAAAAAAAAAAAAtERD+GxMPf/wUNnP8AErn/AhnU/wIe3v8CI+D/Airk/wIl4f8AA8z/AADL /wAAwf8AAJ3/AACY/wAAm/8AALn/AAC//wAAuP8AALP/AACv/wAAqf8AAHr/AAB5/wAAh/8dPrn/ iPT//9r9//9LSUmZAAAAEQAAAAAAAAAAAAAAFnJya6iXmNX/AAes/wIZ1v8CHuD/AiPi/wIp5f8D Lef/AQvV/wAAz/8AANP/AADI/wAAp/8AAKT/AACd/wAAnv8AALn/AADA/wAAuf8AALP/AACw/wAA h/8AAG3/AACC/wAAjf9Ad9f/zf///3Z1d7wAAAAeAAAAAAAAAAAAAAAhj46Iv36B0f8ADMT/Ah7h /wIj4/8CKOb/AzDq/wIj5f8AANX/AADY/wAA2f8AAND/AACx/wAArf8AAKj/AACg/wAAnP8AAK// AAC8/wAAuv8AALT/AACg/wAAbP8AAHn/AACG/wgTpv+u4v//mp+e1wAAACwAAAABAAAAAQAAACec m5fLbXTU/wAY1v8AJ+T/ACrm/wIv6v8DNu7/ARPh/wAA3P8AAN7/AADf/wAA1/8AALz/AAC3/wAA sf8AAKr/AACh/wAAl/8AAJr/AACq/wAAtf8AALT/AACD/wAAbf8AAHz/AACJ/4Ge7f+ss6/hAAAA NgAAAAIAAAABAAAAJpqYlst5gt3/AC3d/xBM6f8VT+z/Aj3u/wI27/8ABeH/AADi/wAA5P8AAOX/ AADf/wAAxv8AAL//AAC5/wAAsP8AAKj/AACf/wAAlP8AAIr/AACO/wAAnv8AAKH/AQFw/wICbv8A AHX/aoXY/660r98AAAA0AAAAAgAAAAAAAAAfgoGBvKar7P8dX+T/X570/4u2+P9EhPb/AEPx/wAI 5v8AAOj/AADq/wAA6v8AAOj/AADS/wAAx/8AAMD/AAC3/wAArv8AAKT/AACa/wAAkf8AAIX/AAB8 /wIDfv8GB3H/DQxj/wcJcf9yjdH/oaKe0gAAACkAAAABAAAAAAAAABRnZmajzs32/1qF5/9/vvf/ 6/f+/8Xh/v88gfb/AB3s/wAI7v8AAvD/AADw/wAA7v8AAN3/AADO/wAAxv8AALz/AACy/wAAqP8A AJ7/AACU/wEBi/8EBIL/Cwt1/x0dav85OG//LzmB/5On0/95d3S2AAAAHAAAAAAAAAAAAAAACj8/ PX7Y1/H/lqju/5S19P/q9v7/8vv//6PN/P9OevX/FDr1/wAS9v8AB/b/AAL0/wEB5/8BAdT/AQHL /wAAwP8AALX/AQGr/wEBof8EBJj/CgqP/xkYhf8xMH3/QEBz/0NCbP9QW5H/usDX/09OTJQAAAAP AAAAAAAAAAAAAAADCgoISLa1xOrY3///qb31/9jj/P/r9v7/1e3+/6jI+/+Cnfr/Rm78/xU4/P8A GPf/AAvw/wgJ2/8ICM7/BwfE/wcHuf8JCa//DQ2m/xkZoP82Npj/OjqP/x0dhP88PJ//S0ui/29+ p//Cw8b4HR0cXwAAAAUAAAAAAAAAAAAAAAAAAAAie3t/t/Pz///J2Pr/09/7//b5/v/9////2ev+ /8LJ+/+nt/3/hKr+/2mN+/89Y/f/L0bq/z482P84OM//ODjH/0FBwv9YWMH/fHu+/0lMsv8HDLr/ AACe/x8flf+BgtP/rbDY/5CPicsDAwMvAAAAAQAAAAAAAAAAAAAAAAMDAhIhISF31NPi+/P4///X 4/z/8fT+///////1+///3uT9/9LP/P/AzPz/sc/8/6vM/P+jw/r/q730/7m57v+6uev/v7/q/8PC 4/9rcMn/P070/w4a6v8ABcP/AACY/zs6ov+ZmNr/Li4yjQYGBRgAAAAAAAAAAAAAAAAAAAAAAAAA GB8fSpZ/f9D/+Pj7//D1///n7f3/9ff+//H5/v/q7v3/4+H7/9Hf/P/S3/z/zt77/8Xg+//D4Pz/ zd/5/9rc9f/m5fb/oqXf/4OW7P+aq///QlH9/wAL4f8AA7r/AgOS/2Bgv/8sLF2kAAAAGwAAAAAA AAAAAAAAAAAAAAQBAQI/MzOa4A0OmP+foNj///////L1/v/v8v3/8fb+//L0/f/r7fz/2+/9/+Lt /P/s6vv/5+v7/+Ds/P/c7fz/3/D8/9vg9f+hs+//9Pr///n7///L0v//V2L4/wAH0/8AAKn/HByY /1BQqegAAAlJAAAABQAAAAAAAAAAAAAADxMTRYkXF6f/AACQ/xQbw/+2ufT///////j5/v/19/3/ +Pr+//f5/v/u+P7/7vf+//X1/f/29Pz/9vT8//b2/P//////jY7W/2B51/////////////L2///N 0///Y2vw/wQLxP8AAJP/LS2t/xwcUZYAAAASAAAAAAAAAAEAAAAmBwdzxgEClP8AA6T/BA/T/0BN 9//V2/3////+///////8/v///f////r+///4/f//+vz+//v7/v/8/P7/+/v9//Pz+v92dc3/AAes /5yt6f/7/////////+To//+wtf7/Tlbi/wEGrP8FBZP/FRV/0QAAAC0AAAABAAAABAAAB0IAAIfq AACR/woSu/9rcuz/tLv//8DR//+4yuv65OTl+P////////////////7////9//////7///39/v/g 4fb/1tf1/9DS9P+urer/xMf1/7zR6/nB0uv59vz///b3//+zt/f/MjnK/wABlf8DA4nwAAALSwAA AAMAAAAEAAAKRwABhe8SFqv/dnvn/9XY//+Rn/L7P1WXwxchNHhHR0V8oaGgxNzc3fD+/v7///// //////////////////v8///8/f///////+zs5vK3trDFWVhWfBwlNHROYI2+oq7u+djc//+QlfD/ Exew/wAAhvUAAAxOAAAAAwAAAAIAAAAjBARIqiYqmOlKT6XYJixvpwEFJGYAAAAnCAcGESMjIhYw MDAzRUVFW3R0dIiWlparqampwLe4uM25ubnNrq6swZycmq59fXyMVFRTWkNDQy4zMzMTDAwLEAAA ACUCBR5gIylpoUBFo9QaHpfpAABMswAAACoAAAACAAAAAAAAAAcAAAAcAAAANQAAAC4AAAAXAAAA CAAAAAIAAAAAAwMDABQUFAEeHh4HKioqDjMzMxk0NDQlNjY2Lzg3Ny83NzcmNjY2GjExMQ4oKCgG ISEhAAgICAAAAAAAAAAAAQAAAAcAAAAUAAAAKwAAADYAAAAgAAAACgAAAAEAAAAAAAAAAAAAAAEA AAACAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQADQ0NABEREQAQEBAAERERABIS EgAQEBAABgYGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAgAAAAEAAAAAAAAA AP/8P///wAP//wAA//4AAD/4AAAf8AAAD+AAAAfgAAAHwAAAA8AAAAOAAAABgAAAAYAAAAGAAAAB gAAAAAAAAAAAAAAAgAAAAIAAAAGAAAABgAAAAcAAAAHAAAADwAAAA4AAAAGAAAABAAAAAAAAAAAA AAAAAAAAAIDABwDH///j --Apple-Mail=_8071450C-E193-44AD-BB57-95F92E5A4391-- --Apple-Mail=_3E78583A-6512-4506-9331-028899E1E0CE-- From nobody Sun Jan 29 00:54:47 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4CWt0Q86z3blxM for ; Sun, 29 Jan 2023 00:54:50 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4CWs4Rvqz3pmH for ; Sun, 29 Jan 2023 00:54:49 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=DWHJ6McK; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=McdMIlk5; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 66.111.4.28 as permitted sender) smtp.mailfrom=yuri@aetern.org; dmarc=none Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 5CD9E5C0194 for ; Sat, 28 Jan 2023 19:54:49 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 28 Jan 2023 19:54:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to; s=fm3; t=1674953689; x=1675040089; bh=H3r2lU2nOD xfWLLkVRM+ROHliXdAYH+3RiC39XDn6EI=; b=DWHJ6McKtg/MDQg/+7yB3hXTiQ 8viVCuuUqCM3KUFkVEZimpynAFvA2979zfUS9wbH21X7jQR9YAG8oFbrdq2PROeC 106tUmROvLmV3jGd3/guTM3Px5OZ5mwszTFp1NAr0ddcAS1afeUcw4mjB/Hoo9Lg 7+lCglIf0IXbd3f3Nuaeg6jpGH3Gr2IbS7PC3G4lgifqXygLhMA6V2qC2Q7vzcNC RUodOXCcecf8o222skE7twk2sbqGC4WwmtrADGgOG7N0kWZWxm+mdKAY0SXqpBru ZKS0s1eE7utJNxbtHUF2LIFTR6HqB/dADptiGN0lOvz6rGAF0/oHz43LMDqA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1674953689; x=1675040089; bh=H3r2lU2nODxfWLLkVRM+ROHliXdA YH+3RiC39XDn6EI=; b=McdMIlk5zPK18+1/nCUNot/wtp2Tj6hymnuHQAaCmbsc kDenQiLI31NgVLYUv8E1YL+HaSvVBK1L56n/sjYN8B3N9eRZsMma4Bpl/9EejnZq UIKpgi0ajiC8fzlMBrxACx8ex5styy9nH9Cr914MBQ1nVAhEINulV/72hKIfjuoq djU/kOeYMjPP6AAMcsVph0DfKOACbCgAIiAhwEh8mNgP1djsB64TOEPsClqUd5Xh SRkOpo6xxqp0MRyRSecHJzQxnI2/KdIwQ13m5F2ButPvyCSldsU+px4e7S4fi0tm tUZjKHo3MBSuuliT+sGb2WPAopTCcPV9ytjtPLjURg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddvledgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfvhffutgfgsehtkeertd dtfeejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeenucgg tffrrghtthgvrhhnpedufeevkeffgfduueeikeelvefhjefgfeetteffffejveetjeekfe efvdfftedtueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpeihuhhrihesrggvthgvrhhnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 28 Jan 2023 19:54:48 -0500 (EST) Message-ID: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> Date: Sun, 29 Jan 2023 01:54:47 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Content-Language: en-US To: current@freebsd.org From: Yuri Subject: vt and keyboard accents Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4P4CWs4Rvqz3pmH X-Spamd-Bar: - X-Spamd-Result: default: False [-1.60 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.28:c]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.28:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.28:from]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; local_wl_from(0.00)[yuri@aetern.org]; DMARC_NA(0.00)[aetern.org] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-ThisMailContainsUnwantedMimeParts: N Looking into an issue with accents input for vt and cz (so /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are working and other result weird unrelated characters output. Checking kbdcontrol -d output, there is an obvious difference with keymap contents -- all mappings are trimmed down to 1 byte after reading: kbdcontrol: dacu 180 ( 180 180 ) ( 'S' 'Z' ) ( 'Z' 'y' ) ( 's' '[' ) ( 'z' 'z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' '9' ) ( 'C' 006 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' ) ( 'O' 211 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' ) ( 'a' 225 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 ) ( 'i' 237 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 ) ( 'y' 253 ) keymap: dacu 0xb4 ( 0xb4 0xb4 ) ( 'S' 0x015a ) ( 'Z' 0x0179 ) ( 's' 0x015b ) ( 'z' 0x017a ) ( 'R' 0x0154 ) ( 'A' 0xc1 ) ( 'L' 0x0139 ) ( 'C' 0x0106 ) ( 'E' 0xc9 ) ( 'I' 0xcd ) ( 'N' 0x0143 ) ( 'O' 0xd3 ) ( 'U' 0xda ) ( 'Y' 0xdd ) ( 'r' 0x0155 ) ( 'a' 0xe1 ) ( 'l' 0x013a ) ( 'c' 0x0107 ) ( 'e' 0xe9 ) ( 'i' 0xed ) ( 'n' 0x0144 ) ( 'o' 0xf3 ) ( 'u' 0xfa ) ( 'y' 0xfd ) Source of the problem is the following definition in sys/sys/kbio.h: struct acc_t { u_char accchar; u_char map[NUM_ACCENTCHARS][2]; }; While the keymaps were converted to have the unicode characters for vt in the commit below, the array to store them (map) was missed, or was there a reason for this? --- commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4 Author: Stefan Eßer Date: Sun Aug 17 19:54:21 2014 +0000 Attempt at converting the SYSCONS keymaps to Unicode for use with NEWCONS. I have spent many hours comparing source and destination formats, and hope to have caught the most severe conversion errors. --- I have tried the following patch and it allows me to enter all accents documented in the keymap, though I must admit I'm not sure it does not have hidden issues: diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h index 7f17bda76c5..fffeb63e226 100644 --- a/sys/sys/kbio.h +++ b/sys/sys/kbio.h @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t; struct acc_t { u_char accchar; - u_char map[NUM_ACCENTCHARS][2]; + int map[NUM_ACCENTCHARS][2]; }; From nobody Sun Jan 29 07:16:36 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4N0S21d7z3bQKs for ; Sun, 29 Jan 2023 07:16:40 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4N0R6gjHz4KKg for ; Sun, 29 Jan 2023 07:16:39 +0000 (UTC) (envelope-from hps@selasky.org) Authentication-Results: mx1.freebsd.org; none Received: from [10.3.0.5] (unknown [46.212.121.255]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id D5A772600D6; Sun, 29 Jan 2023 08:16:36 +0100 (CET) Message-ID: Date: Sun, 29 Jan 2023 08:16:36 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: vt and keyboard accents Content-Language: en-US To: Yuri , current@freebsd.org References: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> From: Hans Petter Selasky In-Reply-To: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4P4N0R6gjHz4KKg X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 1/29/23 01:54, Yuri wrote: > Looking into an issue with accents input for vt and cz (so > /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are > working and other result weird unrelated characters output. > > Checking kbdcontrol -d output, there is an obvious difference with > keymap contents -- all mappings are trimmed down to 1 byte after reading: > > kbdcontrol: > dacu 180 ( 180 180 ) ( 'S' 'Z' ) ( 'Z' 'y' ) ( 's' '[' ) > ( 'z' 'z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' '9' ) > ( 'C' 006 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' ) > ( 'O' 211 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' ) > ( 'a' 225 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 ) > ( 'i' 237 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 ) > ( 'y' 253 ) > > keymap: > dacu 0xb4 ( 0xb4 0xb4 ) ( 'S' 0x015a ) ( 'Z' 0x0179 ) > ( 's' 0x015b ) > ( 'z' 0x017a ) ( 'R' 0x0154 ) ( 'A' 0xc1 ) > ( 'L' 0x0139 ) > ( 'C' 0x0106 ) ( 'E' 0xc9 ) ( 'I' 0xcd ) > ( 'N' 0x0143 ) > ( 'O' 0xd3 ) ( 'U' 0xda ) ( 'Y' 0xdd ) > ( 'r' 0x0155 ) > ( 'a' 0xe1 ) ( 'l' 0x013a ) ( 'c' 0x0107 ) > ( 'e' 0xe9 ) > ( 'i' 0xed ) ( 'n' 0x0144 ) ( 'o' 0xf3 ) > ( 'u' 0xfa ) > ( 'y' 0xfd ) > > Source of the problem is the following definition in sys/sys/kbio.h: > > struct acc_t { > u_char accchar; > u_char map[NUM_ACCENTCHARS][2]; > }; > > While the keymaps were converted to have the unicode characters for vt > in the commit below, the array to store them (map) was missed, or was > there a reason for this? > > --- > commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4 > Author: Stefan Eßer > Date: Sun Aug 17 19:54:21 2014 +0000 > > Attempt at converting the SYSCONS keymaps to Unicode for use with > NEWCONS. > I have spent many hours comparing source and destination formats, > and hope > to have caught the most severe conversion errors. > --- > > I have tried the following patch and it allows me to enter all accents > documented in the keymap, though I must admit I'm not sure it does not > have hidden issues: > > diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h > index 7f17bda76c5..fffeb63e226 100644 > --- a/sys/sys/kbio.h > +++ b/sys/sys/kbio.h > @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t; > > struct acc_t { > u_char accchar; > - u_char map[NUM_ACCENTCHARS][2]; > + int map[NUM_ACCENTCHARS][2]; > }; > Hi, Using "int" for unicode characters is probably good for now. Your patch looks good, but please also consider the "umlaut" case while at it (multiple characters that become one)! --HPS From nobody Sun Jan 29 07:19:58 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4N46318Tz3bQxR for ; Sun, 29 Jan 2023 07:19:50 +0000 (UTC) (envelope-from ihor@antonovs.family) Received: from mail.antonovs.family (mail.antonovs.family [100.25.240.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.antonovs.family", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4N454B10z4LMF for ; Sun, 29 Jan 2023 07:19:49 +0000 (UTC) (envelope-from ihor@antonovs.family) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=antonovs.family header.s=20200215 header.b=ARzNo67x; spf=pass (mx1.freebsd.org: domain of ihor@antonovs.family designates 100.25.240.195 as permitted sender) smtp.mailfrom=ihor@antonovs.family; dmarc=pass (policy=none) header.from=antonovs.family DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antonovs.family; s=20200215; t=1674976784; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MBSLPHpIMGtNs4BqqBn2EfrP36swYJBA7TP4L9GyD3Q=; b=ARzNo67xtDSMzFrUo+O35eH1dhAfjWAeY61pj5GqrGzXw0swrOJX3GztKgQcUOcEIOIfaf OQHTQpstgng+mw3Y7wf/hAoekh7BqmAjYIWq+r4D2dfrYnm3arfjSebu63YOz2UI0mhaej vLKexEYH0r5MoCSsvgTO5MlVUqLYRww= Received: by mail.antonovs.family (OpenSMTPD) with ESMTPSA id 6871e7af (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Sun, 29 Jan 2023 07:19:44 +0000 (UTC) Message-ID: <725699bf-8460-2418-c0e7-c0d6ea4050c0@antonovs.family> Date: Sun, 29 Jan 2023 07:19:58 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Version of OpenSSL included in upcoming 14.0-RELEASE Content-Language: en-US To: freebsd-current@freebsd.org References: <20230128.163414.1398367828069957995.yasu@FreeBSD.org> From: User Ngor In-Reply-To: <20230128.163414.1398367828069957995.yasu@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.96 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.995]; NEURAL_HAM_SHORT(-0.97)[-0.966]; DMARC_POLICY_ALLOW(-0.50)[antonovs.family,none]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[antonovs.family:s=20200215]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[antonovs.family:+]; ASN(0.00)[asn:14618, ipnet:100.24.0.0/13, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4P4N454B10z4LMF X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 1/28/23 07:34, Yasuhiro Kimura wrote: > ... > > Though I'm not familiar with the incompatibility between OpenSSL 1.1.1 > and 3.0, I believe it is too optimistic to regard that build of > 14-CURRENT succeeds without any error just by updating > /usr/src/crypto/openssl from 1.1.1 to 3.0. So it will take for a while > (a few weeks?) to finish it. > > And it also affects build of ports. To be honest, it is rather my main > concern as ports committer. I checked Bugzilla and found following PR. > openssl 3 does have some breaking changes that mostly will be visible to ports. Alpine Linux switched to openssl v3 not so long ago, I will see if they posted any kind of summary.. -- Ihor Antonov From nobody Sun Jan 29 07:52:08 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4Np555cgz3blkC for ; Sun, 29 Jan 2023 07:52:45 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oo1-xc2a.google.com (mail-oo1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4Np52JFmz3C6C for ; Sun, 29 Jan 2023 07:52:45 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oo1-xc2a.google.com with SMTP id y26-20020a4ad65a000000b005173859761dso487079oos.1 for ; Sat, 28 Jan 2023 23:52:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fv9Nr0lm/pu4oVPmdUAE9gassrSYhhk1+nu8LolCops=; b=Tp/cKhOfDayRhTXi4FYi064y3BQSxBPWSIqszwg9DVT2ayMCSo9rW9H4lLjqdAS2hA WNdcmkoWJ4kbTlsXICBM+T2udANCNUtHc/+/xvJeHiyDNtmWKN0kwiRKvWe4WHyUCnfF Uet0+v70HZcFlB7UV5ymEGv37/gMTF850e3DtSeLp2IwA4QpYsoQe6zkXw+P1HOj+6Ug rfhidHVOX32plqCaEhkNCxvqK13nKOERYiMeCowYgvZBAZ7LjLPeqgw+VZPegZl5N+lo Ly74ZhML3Pyug0IrguT060ZC7QxXvDzdstrnYVeircFCRgXQWwCbJTy3HGkY7mJsAEz+ wSBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fv9Nr0lm/pu4oVPmdUAE9gassrSYhhk1+nu8LolCops=; b=pJ23xRMpFOSxQ+SMcZcZQ4Fc+L4lBCtRaM/F1sgNQV7mqeZqhidP7qdF7Tw2s5CRPP mweGX6hrN6A7rDtKMIAMjWzj/gZzcc8Vz9oc6SxhVhIOJBCqIdyRu18wd55QC5cYqKKZ 2Yb8Gz+DYgdeYlYUv4fm5gFJwsQm4o5FAA8kJYYxZ8k3mLVLnwHS8o1DO53Womd9237c aLOqrAsUWnHDmZ8nCaAA9Iu3ubmUgZ6kx4xH160uKe03X3WRTk2/1dxWfJb55DQN+RKb cyTXG/+6Wb4j0dsREguFJvIdHs8izzy82zSb7wPHWHw0+E6Knpjq2R8kgw5j5ZSg192l rk7g== X-Gm-Message-State: AFqh2kpRHNXVsXB3uOQnG4f7Dm2HWCO6mU/yh2XPpyefhuFvG23GDk5r kWrX//Njqr1sh4gyiVPWRlpMnU2Kr/IkRkKwc5p/9cPxGXQ= X-Google-Smtp-Source: AMrXdXt3YGn3Bwg739gr6Qs8ifDSI8tSuxgyIZRuC3ediZiCNFPz6fVX64FtrKKP1jPSsCeSIfIeK3bvvgKIDyl46NA= X-Received: by 2002:a4a:b790:0:b0:4ff:6314:ed87 with SMTP id a16-20020a4ab790000000b004ff6314ed87mr1498477oop.35.1674978764047; Sat, 28 Jan 2023 23:52:44 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> In-Reply-To: From: Mehmet Erol Sanliturk Date: Sun, 29 Jan 2023 10:52:08 +0300 Message-ID: Subject: Re: vt and keyboard accents To: Hans Petter Selasky Cc: Yuri , current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000003cc82805f3626254" X-Rspamd-Queue-Id: 4P4Np52JFmz3C6C X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000003cc82805f3626254 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Jan 29, 2023 at 10:16 AM Hans Petter Selasky wrote: > On 1/29/23 01:54, Yuri wrote: > > Looking into an issue with accents input for vt and cz (so > > /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are > > working and other result weird unrelated characters output. > > > > Checking kbdcontrol -d output, there is an obvious difference with > > keymap contents -- all mappings are trimmed down to 1 byte after readin= g: > > > > kbdcontrol: > > dacu 180 ( 180 180 ) ( 'S' 'Z' ) ( 'Z' 'y' ) ( 's' '[' ) > > ( 'z' 'z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' '9' ) > > ( 'C' 006 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' ) > > ( 'O' 211 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' ) > > ( 'a' 225 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 ) > > ( 'i' 237 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 ) > > ( 'y' 253 ) > > > > keymap: > > dacu 0xb4 ( 0xb4 0xb4 ) ( 'S' 0x015a ) ( 'Z' 0x0179 = ) > > ( 's' 0x015b ) > > ( 'z' 0x017a ) ( 'R' 0x0154 ) ( 'A' 0xc1 = ) > > ( 'L' 0x0139 ) > > ( 'C' 0x0106 ) ( 'E' 0xc9 ) ( 'I' 0xcd = ) > > ( 'N' 0x0143 ) > > ( 'O' 0xd3 ) ( 'U' 0xda ) ( 'Y' 0xdd = ) > > ( 'r' 0x0155 ) > > ( 'a' 0xe1 ) ( 'l' 0x013a ) ( 'c' 0x0107 = ) > > ( 'e' 0xe9 ) > > ( 'i' 0xed ) ( 'n' 0x0144 ) ( 'o' 0xf3 = ) > > ( 'u' 0xfa ) > > ( 'y' 0xfd ) > > > > Source of the problem is the following definition in sys/sys/kbio.h: > > > > struct acc_t { > > u_char accchar; > > u_char map[NUM_ACCENTCHARS][2]; > > }; > > > > While the keymaps were converted to have the unicode characters for vt > > in the commit below, the array to store them (map) was missed, or was > > there a reason for this? > > > > --- > > commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4 > > Author: Stefan E=C3=9Fer > > Date: Sun Aug 17 19:54:21 2014 +0000 > > > > Attempt at converting the SYSCONS keymaps to Unicode for use with > > NEWCONS. > > I have spent many hours comparing source and destination formats, > > and hope > > to have caught the most severe conversion errors. > > --- > > > > I have tried the following patch and it allows me to enter all accents > > documented in the keymap, though I must admit I'm not sure it does not > > have hidden issues: > > > > diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h > > index 7f17bda76c5..fffeb63e226 100644 > > --- a/sys/sys/kbio.h > > +++ b/sys/sys/kbio.h > > @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t; > > > > struct acc_t { > > u_char accchar; > > - u_char map[NUM_ACCENTCHARS][2]; > > + int map[NUM_ACCENTCHARS][2]; > > }; > > > > Hi, > > Using "int" for unicode characters is probably good for now. Your patch > looks good, but please also consider the "umlaut" case while at it > (multiple characters that become one)! > > --HPS > > I am not an expert on UNICODE . When character sets are considered , a homogeneous definition for all of the FreeBSD system would be more useful . There are mainly three types of Unicode : UTF-8 , UTF-16 , and UTF-32 where numbers are bit sizes of the characters . Some pages about Unicode where they have many linked sub pages : https://en.wikipedia.org/wiki/Category:Unicode Category:Unicode https://en.wikipedia.org/wiki/Unicode Unicode https://en.wikipedia.org/wiki/Comparison_of_Unicode_encodings Comparison of Unicode encodings https://en.wikipedia.org/wiki/List_of_binary_codes List of binary codes https://en.wikipedia.org/wiki/List_of_information_system_character_sets List of information system character sets and other related pages ... With my best wishes for all . Mehmet Erol Sanliturk --0000000000003cc82805f3626254 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Jan 29, 2023 at 10:16= AM Hans Petter Selasky <hps@selasky.= org> wrote:
On 1/29/23 01:54, Yuri wrote:
> Looking into an issue with accents input for vt and cz (so
> /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are > working and other result weird unrelated characters output.
>
> Checking kbdcontrol -d output, there is an obvious difference with
> keymap contents -- all mappings are trimmed down to 1 byte after readi= ng:
>
> kbdcontrol:
>=C2=A0 =C2=A0 dacu=C2=A0 180=C2=A0 ( 180 180 ) ( 'S' 'Z'= ; ) ( 'Z' 'y' ) ( 's' '[' )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'z' &#= 39;z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' &= #39;9' )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'C' 00= 6 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'O' 21= 1 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'a' 22= 5 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'i' 23= 7 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'y' 25= 3 )
>
> keymap:
>=C2=A0 =C2=A0 dacu 0xb4=C2=A0 =C2=A0 ( 0xb4=C2=A0 =C2=A00xb4=C2=A0 =C2= =A0 ) ( 'S'=C2=A0 =C2=A0 0x015a=C2=A0 ) ( 'Z'=C2=A0 =C2=A0 = 0x0179=C2=A0 )
> ( 's'=C2=A0 =C2=A0 0x015b=C2=A0 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'z&= #39;=C2=A0 =C2=A0 0x017a=C2=A0 ) ( 'R'=C2=A0 =C2=A0 0x0154=C2=A0 ) = ( 'A'=C2=A0 =C2=A0 0xc1=C2=A0 =C2=A0 )
> ( 'L'=C2=A0 =C2=A0 0x0139=C2=A0 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'C&= #39;=C2=A0 =C2=A0 0x0106=C2=A0 ) ( 'E'=C2=A0 =C2=A0 0xc9=C2=A0 =C2= =A0 ) ( 'I'=C2=A0 =C2=A0 0xcd=C2=A0 =C2=A0 )
> ( 'N'=C2=A0 =C2=A0 0x0143=C2=A0 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'O&= #39;=C2=A0 =C2=A0 0xd3=C2=A0 =C2=A0 ) ( 'U'=C2=A0 =C2=A0 0xda=C2=A0= =C2=A0 ) ( 'Y'=C2=A0 =C2=A0 0xdd=C2=A0 =C2=A0 )
> ( 'r'=C2=A0 =C2=A0 0x0155=C2=A0 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'a&= #39;=C2=A0 =C2=A0 0xe1=C2=A0 =C2=A0 ) ( 'l'=C2=A0 =C2=A0 0x013a=C2= =A0 ) ( 'c'=C2=A0 =C2=A0 0x0107=C2=A0 )
> ( 'e'=C2=A0 =C2=A0 0xe9=C2=A0 =C2=A0 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'i&= #39;=C2=A0 =C2=A0 0xed=C2=A0 =C2=A0 ) ( 'n'=C2=A0 =C2=A0 0x0144=C2= =A0 ) ( 'o'=C2=A0 =C2=A0 0xf3=C2=A0 =C2=A0 )
> ( 'u'=C2=A0 =C2=A0 0xfa=C2=A0 =C2=A0 )
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( 'y&= #39;=C2=A0 =C2=A0 0xfd=C2=A0 =C2=A0 )
>
> Source of the problem is the following definition in sys/sys/kbio.h: >
> struct acc_t {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 u_char=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 accchar;
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 u_char=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 map[NUM_ACCENTCHARS][2];
> };
>
> While the keymaps were converted to have the unicode characters for vt=
> in the commit below, the array to store them (map) was missed, or was<= br> > there a reason for this?
>
> ---
> commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4
> Author: Stefan E=C3=9Fer <se@FreeBSD.org>
> Date:=C2=A0 =C2=A0Sun Aug 17 19:54:21 2014 +0000
>
>=C2=A0 =C2=A0 =C2=A0 Attempt at converting the SYSCONS keymaps to Unico= de for use with
> NEWCONS.
>=C2=A0 =C2=A0 =C2=A0 I have spent many hours comparing source and desti= nation formats,
> and hope
>=C2=A0 =C2=A0 =C2=A0 to have caught the most severe conversion errors.<= br> > ---
>
> I have tried the following patch and it allows me to enter all accents=
> documented in the keymap, though I must admit I'm not sure it does= not
> have hidden issues:
>
> diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h
> index 7f17bda76c5..fffeb63e226 100644
> --- a/sys/sys/kbio.h
> +++ b/sys/sys/kbio.h
> @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t;
>
>=C2=A0 =C2=A0struct acc_t {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 u_char=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 accchar;
> -=C2=A0 =C2=A0 =C2=A0 =C2=A0u_char=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 m= ap[NUM_ACCENTCHARS][2];
> +=C2=A0 =C2=A0 =C2=A0 =C2=A0int=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0map[NUM_ACCENTCHARS][2];
>=C2=A0 =C2=A0};
>

Hi,

Using "int" for unicode characters is probably good for now. Your= patch
looks good, but please also consider the "umlaut" case while at i= t
(multiple characters that become one)!

--HPS




=
I am not an expert on UNICODE .

When character sets ar= e considered , a homogeneous definition for all of the FreeBSD system would= be more useful .
There are mainly three types of Unicode : UTF-8 , = UTF-16 , and UTF-32 where numbers are bit sizes of the characters .


Some pages about Unicode where they have many l= inked sub pages :



https://en.wikipedia.org/wiki/= Category:Unicode
Category:Unicode


Unicode

Comparison of Unic= ode encodings

List of binary codes

<= br>
List of information system character sets=


and other related pages ...


With my best wishes for all .

<= div style=3D"font-family:monospace;font-size:large" class=3D"gmail_default"= >
Mehmet Erol Sanliturk



<= /div>


=C2=A0
--0000000000003cc82805f3626254-- From nobody Sun Jan 29 08:48:38 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4Q2g525Gz3bt59 for ; Sun, 29 Jan 2023 08:48:43 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4Q2g2lW6z3J5g for ; Sun, 29 Jan 2023 08:48:43 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; none Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 80A183200094; Sun, 29 Jan 2023 03:48:40 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sun, 29 Jan 2023 03:48:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1674982120; x= 1675068520; bh=ZIFQTKfEHdyOHm3IS1Wx6pm6ftPqq3D3avGZsx/H/50=; b=y iKR7iduh2o1vsAYZHw6KwxsSi7gRpM5lF26kvNYzvI1WPR7MKQFpHWRoScEZvjqr eInGFrHXROy4gtzgEmr1ifcNK1ZuW5t3AerVJDj9AqcPNSVfWIKsgTMEc4icFqeB t8BNEMgiOVLwUkvaDlPZ52vyLDqK0iccTK75dewy/awDI2jwAxQll6u2dRIZvF74 Ed7MffzqZemMWztNfjO0LskH0dGJ4iSlx55Shr9fXnxdjpbhV07FIo+nJ0iqr2Qg E6dd17ABDO/9DuiY5XLY0elTYTZixml6wDPI96/IdSq+iR5tQrXaU/FuLH4uIyv/ QKyyfX3B/N6/v1ZYKawvA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1674982120; x=1675068520; bh=Z IFQTKfEHdyOHm3IS1Wx6pm6ftPqq3D3avGZsx/H/50=; b=VkyxdtraRF5sj+O2e 77YjKdT7O1YjxMdc7MkZLsyoIT+6MiIGSrRHSK6UjRnFQCh/I7FiaJSy/ejfGHBK NVL4VfbnFdKmjjB8Z3d+DjjDCnAFT7Xx+RwstO4paxkEIpVNtCHQOSEnenlvGkK9 Y6sFULUiFe7N5iPt9E80UwigR5+riC4uWGgIFlNpCUtnEeg6Z7z6zVeov5VDU269 tN5z7chPRZAGDGRtvOnU4Kj/vSrNzGPHcnBOe10x+/VPIMF36W69Lxo2qaFCgTTa w/6EqySZKJcra9wdwkrFdlan9+A8zpFWPkBUywNsXdKBzQ/o0dylk2l+KtcnK1QS PQctQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddvledguddvgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ekredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhephedtkeehfeelueehgfeuteegveeukedtuddtgeffhfeuue etleegieetveejueevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhephihurhhisegrvghtvghrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 29 Jan 2023 03:48:39 -0500 (EST) Message-ID: <842fe9a7-ec72-7557-72b0-4054cf770a5d@aetern.org> Date: Sun, 29 Jan 2023 09:48:38 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: vt and keyboard accents Content-Language: en-US To: Hans Petter Selasky , current@freebsd.org References: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4P4Q2g2lW6z3J5g X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hans Petter Selasky wrote: > On 1/29/23 01:54, Yuri wrote: >> Looking into an issue with accents input for vt and cz (so >> /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are >> working and other result weird unrelated characters output. >> >> Checking kbdcontrol -d output, there is an obvious difference with >> keymap contents -- all mappings are trimmed down to 1 byte after reading: >> >> kbdcontrol: >>    dacu  180  ( 180 180 ) ( 'S' 'Z' ) ( 'Z' 'y' ) ( 's' '[' ) >>               ( 'z' 'z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' '9' ) >>               ( 'C' 006 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' ) >>               ( 'O' 211 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' ) >>               ( 'a' 225 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 ) >>               ( 'i' 237 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 ) >>               ( 'y' 253 ) >> >> keymap: >>    dacu 0xb4    ( 0xb4   0xb4    ) ( 'S'    0x015a  ) ( 'Z'    0x0179  ) >> ( 's'    0x015b  ) >>                 ( 'z'    0x017a  ) ( 'R'    0x0154  ) ( 'A'    0xc1    ) >> ( 'L'    0x0139  ) >>                 ( 'C'    0x0106  ) ( 'E'    0xc9    ) ( 'I'    0xcd    ) >> ( 'N'    0x0143  ) >>                 ( 'O'    0xd3    ) ( 'U'    0xda    ) ( 'Y'    0xdd    ) >> ( 'r'    0x0155  ) >>                 ( 'a'    0xe1    ) ( 'l'    0x013a  ) ( 'c'    0x0107  ) >> ( 'e'    0xe9    ) >>                 ( 'i'    0xed    ) ( 'n'    0x0144  ) ( 'o'    0xf3    ) >> ( 'u'    0xfa    ) >>                 ( 'y'    0xfd    ) >> >> Source of the problem is the following definition in sys/sys/kbio.h: >> >> struct acc_t { >>          u_char          accchar; >>          u_char          map[NUM_ACCENTCHARS][2]; >> }; >> >> While the keymaps were converted to have the unicode characters for vt >> in the commit below, the array to store them (map) was missed, or was >> there a reason for this? >> >> --- >> commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4 >> Author: Stefan Eßer >> Date:   Sun Aug 17 19:54:21 2014 +0000 >> >>      Attempt at converting the SYSCONS keymaps to Unicode for use with >> NEWCONS. >>      I have spent many hours comparing source and destination formats, >> and hope >>      to have caught the most severe conversion errors. >> --- >> >> I have tried the following patch and it allows me to enter all accents >> documented in the keymap, though I must admit I'm not sure it does not >> have hidden issues: >> >> diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h >> index 7f17bda76c5..fffeb63e226 100644 >> --- a/sys/sys/kbio.h >> +++ b/sys/sys/kbio.h >> @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t; >> >>   struct acc_t { >>          u_char          accchar; >> -       u_char          map[NUM_ACCENTCHARS][2]; >> +       int             map[NUM_ACCENTCHARS][2]; >>   }; >> > > Hi, > > Using "int" for unicode characters is probably good for now. Your patch > looks good, but please also consider the "umlaut" case while at it > (multiple characters that become one)! I think umlauts are already part of "accents" (duml keyword), e.g. in cz.kbd: duml 0xa8 ( 0xa8 0xa8 ) ( 'A' 0xc4 ) ( 'E' 0xcb ) ( 'O' 0xd6 ) ( 'U' 0xdc ) ( 'a' 0xe4 ) ( 'e' 0xeb ) ( 'o' 0xf6 ) ( 'u' 0xfc ) So pressing Alt+Shift and "=/+" key, and then pressing one of AEOUaeou keys would produce ÄËÖÜäëöü, respectively, and it currently works as all of the ÄËÖÜäëöü characters can be written as single-byte unicode. And the following dcar (that is, "caron") characters are all broken as they need at least 2 bytes, pressing Shift and "=/+" key, and any of the LSTZlstzCEDNRcednrUu would print nothing at all, produce garbage, or print some control character (last byte only): dcar 0x02c7 ( 0x02c7 0x02c7 ) ( 'L' 0x013d ) ( 'S' 0x0160 ) ( 'T' 0x0164 ) ( 'Z' 0x017d ) ( 'l' 0x013e ) ( 's' 0x0161 ) ( 't' 0x0165 ) ( 'z' 0x017e ) ( 'C' 0x010c ) ( 'E' 0x011a ) ( 'D' 0x010e ) ( 'N' 0x0147 ) ( 'R' 0x0158 ) ( 'c' 0x010d ) ( 'e' 0x011b ) ( 'd' 0x010f ) ( 'n' 0x0148 ) ( 'r' 0x0159 ) ( 'U' 0x016e ) ( 'u' 0x016f ) From nobody Sun Jan 29 09:08:15 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4QTH0LLKz3bwsY for ; Sun, 29 Jan 2023 09:08:19 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4QTG6qX9z3LLm for ; Sun, 29 Jan 2023 09:08:18 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1674983299; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=LRmRU+SERpG8q8VGbDXw5HL4B/K6+yZkbyf+/0S4U1I=; b=chZJlIoLWHxN59Hz4J+fkr3Ep3CBvULc0mOBczRtS9i5p2aTcBnbzddHcf2c9mCJZjRToL y8YJGFcjVD3h8lbr2fq7d8xg4TRINqrQonijJpFz4C0WviPCDG2tZN2H1pRShrB/hOSiEw qUalL+kR3kC/DhhTBOMUokBK2ne+2zdPNSC0m3RdooIC3Il3R4z2EU/YP+MnugQE/Im1hT UHX+55QemRlyokR3O/IVWbbZTLI1gC6ouuDI97c+I2kFU4v/LIQgmQM9ms0HddkP4CfM3m 5QrRj0qfNuvMUAWeVM++kBExCNiwB56pkCiKDJ3X3cn42UZVjIDVNneNQM1CyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1674983299; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=LRmRU+SERpG8q8VGbDXw5HL4B/K6+yZkbyf+/0S4U1I=; b=JR7UiUAOpML7lote01ewDpoau4nyWbEianaW31hKM3eRXg8tSLcS4oQt/T4D6/MAz2emY+ 0JzUflvpuxKzM3HVdEmuYblfoeFKT+w38NFxZjJ7DEbQc0OdYYipuM+Uhu05+d8KTqG4hc 6oW9nkFQohh/sXbFDjB6teHLcMF94h0H8WOS4c6dmY/So7ruTMlPfW3mYcxvsBSzFxV3Q+ ipn05H5bnq2qq5VwKyCCKKbZ5a57dh3ds6KKbo75s3Vak7QbJjoyxt0STJuWpSSPI6+q/V QTjaRw8fH36SuMHacEQerFYkNys995RJGTEtKtm1LwTcyTo7O5v72IZHFuGEiA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1674983299; a=rsa-sha256; cv=none; b=XqKRs2+K7JC3JUJP80AiSgE2yP81Hfzr8642dR6vFOpuksZTMFHL8PzcEaE0GbagTRtpnx aYt2f4YruL6NAAkJOwfzTXeDbLQsTmMARCSlX4gkdZvhgAzFCN0zGwyrlNTaUq33gFp79n gqoJJRwzczabrbZLnGPuTnWx7Z0H5VJnPu+N8aP7JsiwDL7hn8GFZNaXTB7rFQOrK9ZuOO 3NhShBq0ckLi0QMpp6FZHyO0N1758/quPN5p09MhkxwrI+SbV7IHFIOHTv5Ravj+GWL5i7 tdo4AlS591pK5aKlJmtNl2B4Q9qS6KE+u9xg0x1nuXsoYnYd+DTXxWdCvJdDLg== Received: from [IPV6:2001:470:1f1c:a0::2] (tunnel642390-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:a0::2]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P4QTG4dQKzt4Y for ; Sun, 29 Jan 2023 09:08:18 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: Date: Sun, 29 Jan 2023 09:08:15 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: =?UTF-8?Q?Re=3a_poudriere_jail_-u=3a_install=3a_=e2=80=a6=3a_No_suc?= =?UTF-8?Q?h_file_or_directory_=28was=3a_install=3a_wdatwd=2e4=2egz=3a_No_su?= =?UTF-8?Q?ch_file_or_directory=29?= From: Graham Perrin To: FreeBSD CURRENT References: <9f93ec0a-662e-5378-b3a3-8e1e665f6186@freebsd.org> Content-Language: en-GB X-Priority: 5 (Lowest) Organization: FreeBSD In-Reply-To: <9f93ec0a-662e-5378-b3a3-8e1e665f6186@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------71sU0hnlNGs6ICgJNhzGsDUl" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------71sU0hnlNGs6ICgJNhzGsDUl Content-Type: multipart/mixed; boundary="------------4wiHP0IzUIT0HxUS9IS3xcja"; protected-headers="v1" From: Graham Perrin To: FreeBSD CURRENT Message-ID: Subject: =?UTF-8?Q?Re=3a_poudriere_jail_-u=3a_install=3a_=e2=80=a6=3a_No_suc?= =?UTF-8?Q?h_file_or_directory_=28was=3a_install=3a_wdatwd=2e4=2egz=3a_No_su?= =?UTF-8?Q?ch_file_or_directory=29?= References: <9f93ec0a-662e-5378-b3a3-8e1e665f6186@freebsd.org> In-Reply-To: <9f93ec0a-662e-5378-b3a3-8e1e665f6186@freebsd.org> --------------4wiHP0IzUIT0HxUS9IS3xcja Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMTgvMDEvMjAyMyAwNzo0OSwgR3JhaGFtIFBlcnJpbiB3cm90ZToNCj4g4oCmDQo+IGlu c3RhbGwgLU4gL3Vzci9zcmMvZXRjIMKgLW8gcm9vdCAtZyB3aGVlbCAtbSA0NDQgRVJSX3B1 dF9lcnJvci4zLmd6IA0KPiDCoC91c3IvbG9jYWwvcG91ZHJpZXJlL2phaWxzL21haW4vdXNy L3NoYXJlL29wZW5zc2wvbWFuL21hbjMvDQo+IC0tLSByZWFsaW5zdGFsbF9zdWJkaXJfc2Jp biAtLS0NCj4gaW5zdGFsbDogbW50b3B0cy4zLmd6OiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0 b3J5DQo+IC0tLSByZWFsaW5zdGFsbF9zdWJkaXJfc2VjdXJlIC0tLQ0KPg0KPiBtYWtlWzNd OiBzdG9wcGVkIGluIC91c3Ivc3JjDQo+IC0tLSByZWFsaW5zdGFsbF9zdWJkaXJfc2JpbiAt LS0NCj4NCj4gbWFrZVszXTogc3RvcHBlZCBpbiAvdXNyL3NyYw0KPg0KPiBtYWtlWzJdOiBz dG9wcGVkIGluIC91c3Ivc3JjDQo+IMKgwqDCoMKgwqAxNjYuNTUgcmVhbCDCoMKgwqDCoMKg wqDCoDU2LjEyIHVzZXIgwqDCoMKgwqDCoMKgwqAyNS4yMSBzeXMNCj4gKioqIFtpbnN0YWxs d29ybGRdIEVycm9yIGNvZGUgMg0KPg0KPiBtYWtlWzFdOiBzdG9wcGVkIGluIC91c3Ivc3Jj DQo+IDEgZXJyb3INCj4NCj4gbWFrZVsxXTogc3RvcHBlZCBpbiAvdXNyL3NyYw0KPg0KPiBt YWtlOiBzdG9wcGVkIGluIC91c3Ivc3JjDQo+IFswMDowMzozOF0gRXJyb3I6RmFpbGVkIHRv ICdtYWtlIGluc3RhbGx3b3JsZCcNCj4gcm9vdEBtb3dhMjE5LWdqcDQtODU3MHAtZnJlZWJz ZDp+ICMgDQoNCkkgcmVhbGlzZWQgdGhlIGNhdXNlIG9mIHRoZSBtYWluIChDVVJSRU5UKSBq YWlsIGZhaWxpbmcgdG8gdXBkYXRlIGZyb20gDQovdXNyL3NyYzoNCg0KV0lUSE9VVF9NQU5D T01QUkVTUz0gaW4gL2V0Yy9zcmMuY29uZg0KDQo= --------------4wiHP0IzUIT0HxUS9IS3xcja-- --------------71sU0hnlNGs6ICgJNhzGsDUl Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmPWN38FAwAAAAAACgkQt2dIb0oY1AsP ORAAjQho5ouOCGFN6ne/8S+l6hhp6gvDVqhpZTtQLpiOkiyUTpxpHSEM4Ac2dE7VCvXkFQ5PudGK 22OyAEVzsKvRYxepsCJ8OBlI3eubOx8uQ6mip4bF1jm0c/WmlkPzmJYfhL33JtWSzRKM6h0xvj9j z0TP2xibP7nNK+pyh5u+c8lnhkvmWQTm+aHYOoImTEP0PqVoHsFBlKKE3bVfnyraA/vqAnG//ymj q+JHv1d0M4NOOP5tkI4VBZbU1jsefAzF2kJYEjAxGJGjbE9zpo6gvhakuLgbFQKenbyLX5GfsAQg YwdMZHUO/XKmzqTt5hFFPVPRYJFZEEJl10bhOD91jD9in5tLditLKB1QITdHGQQSXBkWnhnmMMHy I9O2k/H6O7cXV6TRVhFi5tP5rpphnoOVBFcuAkzdA6WIXV354//j4lEnZuo0xqeP4SQHkftDDvL6 bnrZxGWqtF/mMP6eg64IW+tSMe9DCEm2j7zGne0x/Mn2tBZ6VeMqR7vEBmgYrjuT8F77XS35zzoj dVUJoif1qoRW1j+Cy1fU8hzF6Z+/h6euzUzTRWA8PW1XZnBcONaBl3uov/nLHZHc6uU8koAIVxY+ juNG5RcewgNzBZwqJcmkHqjtbWVw/5H7glHCj0IaoWUyzSrdsl/X83EOb2B7zvO6/TjHMBg40E/j OgA= =Dxs0 -----END PGP SIGNATURE----- --------------71sU0hnlNGs6ICgJNhzGsDUl-- From nobody Sun Jan 29 13:28:16 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4XFQ0dZyz3cWlK for ; Sun, 29 Jan 2023 13:28:26 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4XFP58wdz42CV for ; Sun, 29 Jan 2023 13:28:25 +0000 (UTC) (envelope-from hps@selasky.org) Authentication-Results: mx1.freebsd.org; none Received: from [10.3.0.5] (unknown [46.212.121.255]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id E4257260114; Sun, 29 Jan 2023 14:28:15 +0100 (CET) Message-ID: Date: Sun, 29 Jan 2023 14:28:16 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: vt and keyboard accents Content-Language: en-US To: Yuri , current@freebsd.org References: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> <842fe9a7-ec72-7557-72b0-4054cf770a5d@aetern.org> From: Hans Petter Selasky In-Reply-To: <842fe9a7-ec72-7557-72b0-4054cf770a5d@aetern.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4P4XFP58wdz42CV X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 1/29/23 09:48, Yuri wrote: > Hans Petter Selasky wrote: >> On 1/29/23 01:54, Yuri wrote: >>> Looking into an issue with accents input for vt and cz (so >>> /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are >>> working and other result weird unrelated characters output. >>> >>> Checking kbdcontrol -d output, there is an obvious difference with >>> keymap contents -- all mappings are trimmed down to 1 byte after reading: >>> >>> kbdcontrol: >>>    dacu  180  ( 180 180 ) ( 'S' 'Z' ) ( 'Z' 'y' ) ( 's' '[' ) >>>               ( 'z' 'z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' '9' ) >>>               ( 'C' 006 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' ) >>>               ( 'O' 211 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' ) >>>               ( 'a' 225 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 ) >>>               ( 'i' 237 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 ) >>>               ( 'y' 253 ) >>> >>> keymap: >>>    dacu 0xb4    ( 0xb4   0xb4    ) ( 'S'    0x015a  ) ( 'Z'    0x0179  ) >>> ( 's'    0x015b  ) >>>                 ( 'z'    0x017a  ) ( 'R'    0x0154  ) ( 'A'    0xc1    ) >>> ( 'L'    0x0139  ) >>>                 ( 'C'    0x0106  ) ( 'E'    0xc9    ) ( 'I'    0xcd    ) >>> ( 'N'    0x0143  ) >>>                 ( 'O'    0xd3    ) ( 'U'    0xda    ) ( 'Y'    0xdd    ) >>> ( 'r'    0x0155  ) >>>                 ( 'a'    0xe1    ) ( 'l'    0x013a  ) ( 'c'    0x0107  ) >>> ( 'e'    0xe9    ) >>>                 ( 'i'    0xed    ) ( 'n'    0x0144  ) ( 'o'    0xf3    ) >>> ( 'u'    0xfa    ) >>>                 ( 'y'    0xfd    ) >>> >>> Source of the problem is the following definition in sys/sys/kbio.h: >>> >>> struct acc_t { >>>          u_char          accchar; >>>          u_char          map[NUM_ACCENTCHARS][2]; >>> }; >>> >>> While the keymaps were converted to have the unicode characters for vt >>> in the commit below, the array to store them (map) was missed, or was >>> there a reason for this? >>> >>> --- >>> commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4 >>> Author: Stefan Eßer >>> Date:   Sun Aug 17 19:54:21 2014 +0000 >>> >>>      Attempt at converting the SYSCONS keymaps to Unicode for use with >>> NEWCONS. >>>      I have spent many hours comparing source and destination formats, >>> and hope >>>      to have caught the most severe conversion errors. >>> --- >>> >>> I have tried the following patch and it allows me to enter all accents >>> documented in the keymap, though I must admit I'm not sure it does not >>> have hidden issues: >>> >>> diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h >>> index 7f17bda76c5..fffeb63e226 100644 >>> --- a/sys/sys/kbio.h >>> +++ b/sys/sys/kbio.h >>> @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t; >>> >>>   struct acc_t { >>>          u_char          accchar; >>> -       u_char          map[NUM_ACCENTCHARS][2]; >>> +       int             map[NUM_ACCENTCHARS][2]; >>>   }; >>> >> >> Hi, >> >> Using "int" for unicode characters is probably good for now. Your patch >> looks good, but please also consider the "umlaut" case while at it >> (multiple characters that become one)! > > I think umlauts are already part of "accents" (duml keyword), e.g. in > cz.kbd: > > duml 0xa8 ( 0xa8 0xa8 ) ( 'A' 0xc4 ) ( 'E' 0xcb ) > ( 'O' 0xd6 ) > ( 'U' 0xdc ) ( 'a' 0xe4 ) ( 'e' 0xeb ) > ( 'o' 0xf6 ) > ( 'u' 0xfc ) > > So pressing Alt+Shift and "=/+" key, and then pressing one of AEOUaeou > keys would produce ÄËÖÜäëöü, respectively, and it currently works as all > of the ÄËÖÜäëöü characters can be written as single-byte unicode. > > And the following dcar (that is, "caron") characters are all broken as > they need at least 2 bytes, pressing Shift and "=/+" key, and any of the > LSTZlstzCEDNRcednrUu would print nothing at all, produce garbage, or > print some control character (last byte only): > > dcar 0x02c7 ( 0x02c7 0x02c7 ) ( 'L' 0x013d ) ( 'S' 0x0160 ) > ( 'T' 0x0164 ) > ( 'Z' 0x017d ) ( 'l' 0x013e ) ( 's' 0x0161 ) > ( 't' 0x0165 ) > ( 'z' 0x017e ) ( 'C' 0x010c ) ( 'E' 0x011a ) > ( 'D' 0x010e ) > ( 'N' 0x0147 ) ( 'R' 0x0158 ) ( 'c' 0x010d ) > ( 'e' 0x011b ) > ( 'd' 0x010f ) ( 'n' 0x0148 ) ( 'r' 0x0159 ) > ( 'U' 0x016e ) > ( 'u' 0x016f ) Hi Yuri, Do you happen to know if we currently support these Norwegian-only umlauts? For example written as "umlauts": å b̊ c̊ Only the single-characters å and Å are of interest in the Norwegian language. --HPS From nobody Sun Jan 29 15:06:12 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4ZQQ4PWSz3ck0Y for ; Sun, 29 Jan 2023 15:06:22 +0000 (UTC) (envelope-from qroxana@protonmail.com) Received: from mail-4027.protonmail.ch (mail-4027.protonmail.ch [185.70.40.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4ZQP1Fr8z4Cvn for ; Sun, 29 Jan 2023 15:06:21 +0000 (UTC) (envelope-from qroxana@protonmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=t3d0eNIP; spf=pass (mx1.freebsd.org: domain of qroxana@protonmail.com designates 185.70.40.27 as permitted sender) smtp.mailfrom=qroxana@protonmail.com; dmarc=pass (policy=quarantine) header.from=protonmail.com Date: Sun, 29 Jan 2023 15:06:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1675004778; x=1675263978; bh=blnO0T5tId1E1rbtVd/lm1J6MT+ZsaJejCL0QL7UlGc=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=t3d0eNIP+nAOMsLzTE7wNLl1k4yYgAonc+RRJDIRUx7s4nf4eUbfcw2O4fsvL47Oj b48iW4UaSq7o+yV5Ggb8KSs2EvHGyJ+vXowHP0hwdJbyYNMRbScUFasqN5rg81tQz7 tQGoyfOuHCuI79663FXWkQS9eS0HXwV4V7zTAj8MS6Fw1oQNAUPSs9UhQA7l3e2BIg WrpGsmaJ8FOedGBj7IhND6ajgCYLlycmSxXjJdNJZJJ98rqzAeKkClXBBVn5CLv050 SNEgZn7r1602TIYMxhT546XO+zzpT/wV1JWcBtTDNlU7SZKWzKlPoAG+Zuus6WgUcF 1dEhR0cBLGRYg== To: "freebsd-current@freebsd.org" From: qroxana Cc: Dimitry Andric Subject: Re: buildworld failed after deleting /usr/obj Message-ID: <44ybMtpAl4lOcN0PqhC63MaFz0G7l0mD_6RBWLaFNqw7gs2uCbYRhxwcvOv5chBBPH3vSQetkVbwtxWZR14fJyWIMZZet8yU_yiMPa7J_yQ=@protonmail.com> In-Reply-To: References: <7cKQCx9PEwnnJE5MatS6g5KkKh5prIZTrTlqGL2RfM7Z4TDJGCfEATg9ejghBWDhx7WqDtVpxAA6wEisDAP2Y6c8g-ht2KbUW4YN0eek43g=@protonmail.com> <3CCFF1C8-D618-453F-8412-3D65F551C43C@FreeBSD.org> Feedback-ID: 29996633:user:proton List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-2.92 / 15.00]; NEURAL_HAM_LONG(-0.99)[-0.987]; NEURAL_HAM_SHORT(-0.98)[-0.982]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail3]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_MEDIUM(0.05)[0.050]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; DKIM_TRACE(0.00)[protonmail.com:+]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.27:from] X-Rspamd-Queue-Id: 4P4ZQP1Fr8z4Cvn X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N ------- Original Message ------- On Monday, January 23rd, 2023 at 1:44 PM, qroxana = wrote: > ------- Original Message ------- > On Monday, January 23rd, 2023 at 10:02 AM, Dimitry Andric dim@FreeBSD.org= wrote: >=20 >=20 >=20 > > On 23 Jan 2023, at 04:05, qroxana qroxana@protonmail.com wrote: > >=20 > > > It seems ${MAKEOBJDIR} was not created for usr.bin/clang/llvm-objcopy= . > > >=20 > > > --- all_subdir_usr.bin --- > > > --- objwarn --- > > > Warning: Object directory not changed from original /usr/src/usr.bin/= clang/llvm-objcopy > >=20 > > This is usually an indication that your source directory contains objec= t > > files, e.g. is "dirty". Run "make clean" from the top level, or clean u= p > > your source checkout with something like "git clean". > >=20 > > -Dimitry >=20 >=20 > I had tried it with a clean source directory and empty /usr/obj >=20 > # find /usr/src/usr.bin/clang/llvm-objcopy > /usr/src/usr.bin/clang/llvm-objcopy > /usr/src/usr.bin/clang/llvm-objcopy/llvm-objcopy.1 > /usr/src/usr.bin/clang/llvm-objcopy/Makefile >=20 > and "make buildworld" still ended with the same error. >=20 > In /usr/src/Makefile.inc1, the _NO_INCLUDE_COMPILERMK=3Dt option prevents= creating > the obj directories for the stuff in usr.bin/clang/. >=20 > 1098 _obj: > 1099 @echo > 1100 @echo "-------------------------------------------------------------= -" > 1101 @echo ">>> stage 2.2: rebuilding the object tree" >=20 > 1102 @echo "-------------------------------------------------------------= -" > 1103 ${+}cd ${.CURDIR}; ${WMAKE} _NO_INCLUDE_COMPILERMK=3Dt obj >=20 > > --- all_subdir_usr.bin --- > > --- objwarn --- > > Warning: Object directory not changed from original /usr/src/usr.bin/cl= ang/llvm-objcopy >=20 >=20 > This happens in stage 4.4, and there's no ${MAKEOBJDIR} directory created > for usr.bin/clang/llvm-objcopy >=20 It appears buildworld doesn't create the obj directory for usr.bin/clang/ll= vm-objcopy in stage 2.2 after this commit. commit adc3c128c6603054586a993d117e5dd808deac17 Author: John Baldwin AuthorDate: Fri Nov 18 20:12:28 2022 -0800 Commit: John Baldwin CommitDate: Fri Nov 18 20:12:28 2022 -0800 src.opts.mk: Require C++20 for C++ support. =20 libc++ requires C++20, so mark C++ (MK_CXX) as broken if the compiler does not support C++20. =20 Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D36893 diff --git a/share/mk/src.opts.mk b/share/mk/src.opts.mk index f69208f21556..5089a034350d 100644 --- a/share/mk/src.opts.mk +++ b/share/mk/src.opts.mk @@ -348,6 +348,11 @@ __DEFAULT_YES_OPTIONS+=3DOPENMP __DEFAULT_NO_OPTIONS+=3DOPENMP .endif =20 +# libc++ requires C++20 +.if !${COMPILER_FEATURES:Mc++20} +BROKEN_OPTIONS+=3DCXX +.endif + .include =20 # From nobody Sun Jan 29 15:10:31 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4ZWK09v9z3ckbt for ; Sun, 29 Jan 2023 15:10:37 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4ZWJ5JL2z4FSV for ; Sun, 29 Jan 2023 15:10:36 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; none Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B2CEC5C0D93; Sun, 29 Jan 2023 10:10:34 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 29 Jan 2023 10:10:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1675005034; x= 1675091434; bh=Dr/druN9VwzKqvBK1NuqmQL3/EnYzOkdQq8eJGvtIFg=; b=s e4xP1RMAxkC/g19koHKOAwj5UjWcaYspexfuPXgMlaVLFuqZV58Bsb+dnZ8iQxav gz3bJtouxcGCeTyJsK+c40ut5N3CnuMa7iaZa5AaB6w2h+ENY4o2SxAhPS1bAbx/ 0R8feCbjvNI8b0VnUQCvmUC5o/ytjTaZ6HuP4VMBqTl7b2qWWHFEG+ztK4s6mM1y 5aO2L/60xzkxTUVhByiQHkwNVuXpfja5QVTN53gY1D/sZlBW4onAR++zByNFW2p4 MYtK5+uyQAtN65b6DhQ0EbexyBwmo2spixBTe1O46mdmVjPjBeB5gne6mPxJvzAr pyHH5RdJ8LXRwdUFFUXkw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1675005034; x=1675091434; bh=D r/druN9VwzKqvBK1NuqmQL3/EnYzOkdQq8eJGvtIFg=; b=T6hvKNOFLKy+Q1pPs sgRNbo8sK6Fw24FHeNEeeJwS2KswlPBeITnVLP03AZ240SOfL/4gzH7647iZOT6R DRvAxI2iE2A7Sm2LxQnPejVlrIXs/H+BQF6QIo+mSWlYRjw/kSO0AEnwxMxaOCxZ Lmyq4hDP1UgWT3CXSXl2VdjWqcScNeXGlUTNVmsMOcROAYU7y2woXRXgMoWH3kQf DTUiqg/EHNWQw/HLN5s3eUvQ2FJtYfs62zVJnLMlS7uTEM92+NWgHFeG1BYkJaNp ABmLijTof/Xe2eaRY/CeCIoUvr/JjbS0FgFgSAbRR8UYds2xUp6ToQ9Bv9gfS92x gJ8KQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeftddgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtfeejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeen ucggtffrrghtthgvrhhnpeehtdekheefleeuhefgueetgeevueektddutdegfffhueeute elgeeiteevjeeuveenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpeihuhhrihesrggvthgvrhhnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 29 Jan 2023 10:10:33 -0500 (EST) Message-ID: <37e0cdef-d3f9-e6d9-2368-5bff0bdbe6c1@aetern.org> Date: Sun, 29 Jan 2023 16:10:31 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: vt and keyboard accents Content-Language: en-US To: Hans Petter Selasky , current@freebsd.org References: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> <842fe9a7-ec72-7557-72b0-4054cf770a5d@aetern.org> From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4P4ZWJ5JL2z4FSV X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hans Petter Selasky wrote: > On 1/29/23 09:48, Yuri wrote: >> Hans Petter Selasky wrote: >>> On 1/29/23 01:54, Yuri wrote: >>>> Looking into an issue with accents input for vt and cz (so >>>> /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are >>>> working and other result weird unrelated characters output. >>>> >>>> Checking kbdcontrol -d output, there is an obvious difference with >>>> keymap contents -- all mappings are trimmed down to 1 byte after >>>> reading: >>>> >>>> kbdcontrol: >>>>     dacu  180  ( 180 180 ) ( 'S' 'Z' ) ( 'Z' 'y' ) ( 's' '[' ) >>>>                ( 'z' 'z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' '9' ) >>>>                ( 'C' 006 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' ) >>>>                ( 'O' 211 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' ) >>>>                ( 'a' 225 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 ) >>>>                ( 'i' 237 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 ) >>>>                ( 'y' 253 ) >>>> >>>> keymap: >>>>     dacu 0xb4    ( 0xb4   0xb4    ) ( 'S'    0x015a  ) ( 'Z'    >>>> 0x0179  ) >>>> ( 's'    0x015b  ) >>>>                  ( 'z'    0x017a  ) ( 'R'    0x0154  ) ( 'A'    >>>> 0xc1    ) >>>> ( 'L'    0x0139  ) >>>>                  ( 'C'    0x0106  ) ( 'E'    0xc9    ) ( 'I'    >>>> 0xcd    ) >>>> ( 'N'    0x0143  ) >>>>                  ( 'O'    0xd3    ) ( 'U'    0xda    ) ( 'Y'    >>>> 0xdd    ) >>>> ( 'r'    0x0155  ) >>>>                  ( 'a'    0xe1    ) ( 'l'    0x013a  ) ( 'c'    >>>> 0x0107  ) >>>> ( 'e'    0xe9    ) >>>>                  ( 'i'    0xed    ) ( 'n'    0x0144  ) ( 'o'    >>>> 0xf3    ) >>>> ( 'u'    0xfa    ) >>>>                  ( 'y'    0xfd    ) >>>> >>>> Source of the problem is the following definition in sys/sys/kbio.h: >>>> >>>> struct acc_t { >>>>           u_char          accchar; >>>>           u_char          map[NUM_ACCENTCHARS][2]; >>>> }; >>>> >>>> While the keymaps were converted to have the unicode characters for vt >>>> in the commit below, the array to store them (map) was missed, or was >>>> there a reason for this? >>>> >>>> --- >>>> commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4 >>>> Author: Stefan Eßer >>>> Date:   Sun Aug 17 19:54:21 2014 +0000 >>>> >>>>       Attempt at converting the SYSCONS keymaps to Unicode for use with >>>> NEWCONS. >>>>       I have spent many hours comparing source and destination formats, >>>> and hope >>>>       to have caught the most severe conversion errors. >>>> --- >>>> >>>> I have tried the following patch and it allows me to enter all accents >>>> documented in the keymap, though I must admit I'm not sure it does not >>>> have hidden issues: >>>> >>>> diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h >>>> index 7f17bda76c5..fffeb63e226 100644 >>>> --- a/sys/sys/kbio.h >>>> +++ b/sys/sys/kbio.h >>>> @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t; >>>> >>>>    struct acc_t { >>>>           u_char          accchar; >>>> -       u_char          map[NUM_ACCENTCHARS][2]; >>>> +       int             map[NUM_ACCENTCHARS][2]; >>>>    }; >>>> >>> >>> Hi, >>> >>> Using "int" for unicode characters is probably good for now. Your patch >>> looks good, but please also consider the "umlaut" case while at it >>> (multiple characters that become one)! >> >> I think umlauts are already part of "accents" (duml keyword), e.g. in >> cz.kbd: >> >>    duml 0xa8    ( 0xa8   0xa8    ) ( 'A'    0xc4    ) ( 'E'    0xcb    ) >> ( 'O'    0xd6    ) >>                 ( 'U'    0xdc    ) ( 'a'    0xe4    ) ( 'e'    0xeb    ) >> ( 'o'    0xf6    ) >>                 ( 'u'    0xfc    ) >> >> So pressing Alt+Shift and "=/+" key, and then pressing one of AEOUaeou >> keys would produce ÄËÖÜäëöü, respectively, and it currently works as all >> of the ÄËÖÜäëöü characters can be written as single-byte unicode. >> >> And the following dcar (that is, "caron") characters are all broken as >> they need at least 2 bytes, pressing Shift and "=/+" key, and any of the >> LSTZlstzCEDNRcednrUu would print nothing at all, produce garbage, or >> print some control character (last byte only): >> >>    dcar 0x02c7  ( 0x02c7 0x02c7  ) ( 'L'    0x013d  ) ( 'S'    0x0160  ) >> ( 'T'    0x0164  ) >>                 ( 'Z'    0x017d  ) ( 'l'    0x013e  ) ( 's'    0x0161  ) >> ( 't'    0x0165  ) >>                 ( 'z'    0x017e  ) ( 'C'    0x010c  ) ( 'E'    0x011a  ) >> ( 'D'    0x010e  ) >>                 ( 'N'    0x0147  ) ( 'R'    0x0158  ) ( 'c'    0x010d  ) >> ( 'e'    0x011b  ) >>                 ( 'd'    0x010f  ) ( 'n'    0x0148  ) ( 'r'    0x0159  ) >> ( 'U'    0x016e  ) >>                 ( 'u'    0x016f  ) > > Hi Yuri, > > Do you happen to know if we currently support these Norwegian-only umlauts? > > For example written as "umlauts": > > å b̊ c̊ > > Only the single-characters å and Å are of interest in the Norwegian > language. Looking at the share/vt/keymaps/no.kbd we don't, but if I understood you correctly and only å/Å are required, it should be easy to add: diff --git a/share/vt/keymaps/no.kbd b/share/vt/keymaps/no.kbd index 710563917fa4..94c3621396dc 100644 --- a/share/vt/keymaps/no.kbd +++ b/share/vt/keymaps/no.kbd @@ -33,7 +33,7 @@ 027 0xa8 '^' rs rs '~' '^' rs rs O 028 cr cr nl nl cr cr nl nl O 029 lctrl lctrl lctrl lctrl lctrl lctrl lctrl lctrl O - 030 'a' 'A' soh soh 0xe1 0xc1 soh soh C + 030 'a' 'A' soh soh 0xe1 0xc1 0xe5 0xc5 C 031 's' 'S' dc3 dc3 0xdf 0xdf dc3 dc3 C 032 'd' 'D' eot eot 0xf0 0xd0 eot eot C 033 'f' 'F' ack ack 0xaa 0xaa ack ack C Pressing Ctrl+AltGr+a will produce å now, with Shift for Å. From nobody Sun Jan 29 22:18:26 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4m1828Tvz3cGwC for ; Sun, 29 Jan 2023 22:18:36 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4P4m172f12z3nFh for ; Sun, 29 Jan 2023 22:18:35 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:300:2185:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org; dmarc=pass (policy=none) header.from=catflap.org X-Catflap-Envelope-From: X-Catflap-Envelope-To: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 30TMIR9E020884 for ; Sun, 29 Jan 2023 22:18:28 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 30TMIQmM020883 for freebsd-current@freebsd.org; Sun, 29 Jan 2023 22:18:26 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202301292218.30TMIQmM020883@donotpassgo.dyslexicfish.net> Date: Sun, 29 Jan 2023 22:18:26 +0000 Organization: Dyslexic Fish To: freebsd-current@freebsd.org Subject: 1 year src-patch anniversary! User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Sun, 29 Jan 2023 22:18:28 +0000 (GMT) X-Spamd-Result: default: False [-3.70 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_EXCLAIM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[jamie]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:20473, ipnet:2001:19f0::/38, country:US] X-Rspamd-Queue-Id: 4P4m172f12z3nFh X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 is a trivial fix to an admittedly trivial issue, but it's soon going to hit one year old, and has not had any feedback. Not even "this is rubbish. close ticket" | jamie@catwalk:~ % stat 'so good they named it twice' | stat: so good they named it twice: stat: No such file or directory As such, it's the oldest of my patches to be completely ignored, but then, most of my fixes I haven't even submitted, because, what's the point? I've instead spent time writing something so the patches are automatically aplied to my src tree, and distributed to all my servers. I know it's a volunteer effort, but I've been here 25 years, and whilst I could (and should) take on more port-maintainership, any other offers of help have fallen on deaf ears. *shrug* I miss Mark Linimon. From nobody Sun Jan 29 22:29:48 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4mG658f4z3cJCQ for ; Sun, 29 Jan 2023 22:29:50 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oa1-x2d.google.com (mail-oa1-x2d.google.com [IPv6:2001:4860:4864:20::2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4mG63YLVz3pwY for ; Sun, 29 Jan 2023 22:29:50 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-163bd802238so896420fac.1 for ; Sun, 29 Jan 2023 14:29:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0s2BmOD+kDAJwaDzIECFlqatxLPSdKSzGbF+BUhqAI4=; b=QxRoLFrokzrjxKKVzpSyvACZ3Z9AJs+s1sDgf1j694M1pkELdYZk3hXkGlSfq9aEBO WZWrlUQNrjb1kTTlIa6blU+AYKqYlDQSc3j4XyX2gqAtJnwgktji0rc9N7QL0lT3bcUU jV2HkkkLB2c/sod2Hr99XWsMmxR+eGLEVBWDZ61Q69iMDeM3CeKsMmn7iHU/WGBFUE4C Fizl6oFWPGH2+IgjAhMK45NuRBH1sY9d162k054JCK6H6zNnU5apThsXYtZp39gDjeJ1 m75spfPbjSjhnE1gs1+lMYjJuSB7hy73OtsanydpoRtsxLKmKcqq65QN1XV0LgdP2jUr KMAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0s2BmOD+kDAJwaDzIECFlqatxLPSdKSzGbF+BUhqAI4=; b=stwo+jhFK4/rWF0sS1gbnN9AO38riNxB6AayfpE4dq4ZIRYWA7U24ATzCfnKce5V9L EQAqCHS0nDN/6xlt27mkVeFJlHqLWDrGBI7z/c9jnVz6MbDOjpZmGYwHNSL9FU1Gskdf ZzYCSH7kBHvDFqMpvnU0V7NqbXganPCVSOOIWCjfZ7fBp6s2Eb0Fd/Fu4wxykTJn7uxC +Qhi38g0UhMY/YBgCaESmARd9dq1Ac7Xpl3iaEH0OZhUV5Gw2znCpllVeVVY4UGE3o9e LIxIptq5NTAo0JGZy3BlN6I6bqcehfUXe/hLrQWDD8WEyCN3gW+1YyFMosFfx4X5zLLL tF1w== X-Gm-Message-State: AO0yUKXUAAmoEOWytGW+ElyW9/jaab9EbFldEuSdLSuu6sq6hSoYuius zb2SSolw3iF3O1GIkPL4b2RDYXm6DzTQaVUAx4Y= X-Google-Smtp-Source: AK7set8vtrNSwLa18S9hZ56WuawH9injFGyYvDHmPuxd/fNAeufKN6FI+xwGY+jr2uhCe843UKzkoHzPwP7hZRsFUvI= X-Received: by 2002:a05:6870:a106:b0:163:5124:d21b with SMTP id m6-20020a056870a10600b001635124d21bmr871248oae.81.1675031389511; Sun, 29 Jan 2023 14:29:49 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: by 2002:a8a:ad6:0:b0:49c:e11d:f815 with HTTP; Sun, 29 Jan 2023 14:29:48 -0800 (PST) In-Reply-To: <202301292218.30TMIQmM020883@donotpassgo.dyslexicfish.net> References: <202301292218.30TMIQmM020883@donotpassgo.dyslexicfish.net> From: Mateusz Guzik Date: Sun, 29 Jan 2023 23:29:48 +0100 Message-ID: Subject: Re: 1 year src-patch anniversary! To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4P4mG63YLVz3pwY X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 1/29/23, Jamie Landeg-Jones wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 is a trivial fix > to an admittedly trivial issue, but it's soon going to hit one year old, > and has not had any feedback. Not even "this is rubbish. close ticket" > > | jamie@catwalk:~ % stat 'so good they named it twice' > | stat: so good they named it twice: stat: No such file or directory > > As such, it's the oldest of my patches to be completely ignored, but then, > most of my fixes I haven't even submitted, because, what's the point? > I've instead spent time writing something so the patches are automatically > aplied to my src tree, and distributed to all my servers. > > I know it's a volunteer effort, but I've been here 25 years, and whilst > I could (and should) take on more port-maintainership, any other offers > of help have fallen on deaf ears. > Well I was not aware of it. mail me with git format-patch result and I'll commit. -- Mateusz Guzik From nobody Sun Jan 29 22:31:13 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4mHl3RCsz3cJf2 for ; Sun, 29 Jan 2023 22:31:15 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4mHk641bz3r9m for ; Sun, 29 Jan 2023 22:31:14 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=h3H3SRf8; spf=pass (mx1.freebsd.org: domain of mjguzik@gmail.com designates 2607:f8b0:4864:20::234 as permitted sender) smtp.mailfrom=mjguzik@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-oi1-x234.google.com with SMTP id r205so8661151oib.9 for ; Sun, 29 Jan 2023 14:31:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GMeICICn1DWvkp07wnaX0K1A433dg4cPgO/8H59uPSw=; b=h3H3SRf8PlQR4GeGge6CVRa8Aw4L3Fbiqw1B/sY4vzlLF5lyIlUFiriidk8qHpznV6 r17QahwspNABzCO7GeWjaNc1rNMw+6pQwSmOFtyDiaIfDB3Re42ib/2CVbruzYDcFUlT 3v0kE46E32J19LKq/+WybC/qj8r870Tl0dn0sqPB73K6dPwQlWpuQ6Xn4LY3a6khxGuu XqLpzcx20jzb3rRoJ0i9vdG1l8GLKxY41I4PwOBr4P+yfe9pi7JZFfyrlCuKbH/wFDjf ea0FMcSzi4+WAF3dYZG9LmaCC04xGsVr86uzbLmjaQIKZyxO9p9jrilYoUzKWTb33DRE 2dgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GMeICICn1DWvkp07wnaX0K1A433dg4cPgO/8H59uPSw=; b=VlE6rgLYX5hPO2eneDYtI4djdJr8z/UQMwRLZOes//TmkU3UXUv8M5j4TBUCQb3/g3 Mwnx8Pm05mQx5Bdkmm6iFJ1UE3t+6q3i+Wfv8I7sfLDE2hrJOvC2UN9Bv24EcBY94/Bo ARD8ttB4V06XjUshgmATuaDltGlfUM6mB0doV1h2Pxs0LZcV1JpbiU5+a90Cr9vbw3jM Pfyq7yj29TDS0g3d9tt9CXMCX4WvTgHJto16Bje48jBWeJcAOgzJ6HaQkmHBnTby61bp 2OyBDbAjsuxuwAvgm71UII0lBHx6GxcrG/iXCH8q7RCB7RLQpkbCL/C1wUKWHteDGyqx fKqw== X-Gm-Message-State: AO0yUKUr0ccHLyETZl921ohzU9kBkPR0O//kcHPSSiXnLXBfcx1HVJkx qtJZshckz9DI7iW9XaajLwoag1Usy+MLdy8TqhYBJEe5 X-Google-Smtp-Source: AK7set8ZZqIuzFr1cW/92ErMPxNwrxLl4BYjcJp2rU9adWvRwp44WAQ+23wvEgL+Fz2FUvjz4zQRp1wzp7taEGsVOSk= X-Received: by 2002:a05:6808:1a9c:b0:378:348b:9346 with SMTP id bm28-20020a0568081a9c00b00378348b9346mr90965oib.81.1675031473920; Sun, 29 Jan 2023 14:31:13 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: by 2002:a8a:ad6:0:b0:49c:e11d:f815 with HTTP; Sun, 29 Jan 2023 14:31:13 -0800 (PST) In-Reply-To: References: <202301292218.30TMIQmM020883@donotpassgo.dyslexicfish.net> From: Mateusz Guzik Date: Sun, 29 Jan 2023 23:31:13 +0100 Message-ID: Subject: Re: 1 year src-patch anniversary! To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-1.89 / 15.00]; NEURAL_HAM_LONG(-0.99)[-0.988]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_SPAM_SHORT(0.20)[0.204]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; NEURAL_HAM_MEDIUM(-0.10)[-0.102]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::234:from]; DKIM_TRACE(0.00)[gmail.com:+]; SUBJECT_ENDS_EXCLAIM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org] X-Rspamd-Queue-Id: 4P4mHk641bz3r9m X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On 1/29/23, Mateusz Guzik wrote: > On 1/29/23, Jamie Landeg-Jones wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 is a trivial fix >> to an admittedly trivial issue, but it's soon going to hit one year old, >> and has not had any feedback. Not even "this is rubbish. close ticket" >> >> | jamie@catwalk:~ % stat 'so good they named it twice' >> | stat: so good they named it twice: stat: No such file or directory >> >> As such, it's the oldest of my patches to be completely ignored, but >> then, >> most of my fixes I haven't even submitted, because, what's the point? >> I've instead spent time writing something so the patches are >> automatically >> aplied to my src tree, and distributed to all my servers. >> >> I know it's a volunteer effort, but I've been here 25 years, and whilst >> I could (and should) take on more port-maintainership, any other offers >> of help have fallen on deaf ears. >> > > Well I was not aware of it. > > mail me with git format-patch result and I'll commit. > also make sure the commit message starts with: stat: -- Mateusz Guzik From nobody Mon Jan 30 02:54:48 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4t8C5PNHz3c4n7 for ; Mon, 30 Jan 2023 02:55:07 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4t8B4z6bz4Hp6 for ; Mon, 30 Jan 2023 02:55:06 +0000 (UTC) (envelope-from jhs@berklix.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of jhs@berklix.com has no SPF policy when checking 144.76.10.75) smtp.mailfrom=jhs@berklix.com; dmarc=none Received: from dell.no.berklix.net (p4fc4c2e9.dip0.t-ipconnect.de [79.196.194.233]) (authenticated bits=128) by land.berklix.org (8.16.1/8.16.1) with ESMTPSA id 30U2srNh026817 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Mon, 30 Jan 2023 02:54:54 GMT (envelope-from jhs@berklix.com) Received: from dell.no.berklix.net (localhost [127.0.0.1]) by dell.no.berklix.net (8.16.1/8.16.1) with ESMTPS id 30U2smWK061915 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 30 Jan 2023 03:54:48 +0100 (CET) (envelope-from jhs@dell.no.berklix.net) Received: (from jhs@localhost) by dell.no.berklix.net (8.16.1/8.14.5/Submit) id 30U2sm0k061914; Mon, 30 Jan 2023 03:54:48 +0100 (CET) (envelope-from jhs) Message-Id: <202301300254.30U2sm0k061914@dell.no.berklix.net> To: Jamie Landeg-Jones cc: freebsd-current@freebsd.org Subject: Re: 1 year src-patch anniversary! From: "Julian H. Stacey" Organization: http://berklix.com/jhs/ User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Sun, 29 Jan 2023 22:18:26 +0000." <202301292218.30TMIQmM020883@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <61912.1675047288.1@dell.no.berklix.net> Date: Mon, 30 Jan 2023 03:54:48 +0100 X-Spamd-Result: default: False [-0.15 / 15.00]; URI_HIDDEN_PATH(1.00)[http://www.berklix.com/~jhs/bin/.csh/customise]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.97)[-0.966]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.08)[-0.082]; R_SPF_NA(0.00)[no SPF record]; SUBJECT_ENDS_EXCLAIM(0.00)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; ASN(0.00)[asn:24940, ipnet:144.76.0.0/16, country:DE]; FREEFALL_USER(0.00)[jhs]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[berklix.com]; TO_DN_SOME(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4P4t8B4z6bz4Hp6 X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N Jamie Landeg-Jones wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 is a trivial fix > to an admittedly trivial issue, but it's soon going to hit one year old, > and has not had any feedback. Not even "this is rubbish. close ticket" > > | jamie@catwalk:~ % stat 'so good they named it twice' > | stat: so good they named it twice: stat: No such file or directory > > As such, it's the oldest of my patches to be completely ignored, but then, > most of my fixes I haven't even submitted, because, what's the point? > I've instead spent time writing something so the patches are automatically > aplied to my src tree, and distributed to all my servers. I wrote a tool in 1993 I still use http://www.berklix.com/~jhs/bin/.csh/customise to apply trees of generic & personal diffs to src & ports, for multi releases http://www.berklix.com/~jhs/src/ to apply diffs, where some are submitted, some committed for some versions, some diffs still needed for older versions, & some not submitted or committed. I guess many, especially non-commiters, maintain trees of uncommited diffs & there's probably other applicator scripts, numerous re-inventing of wheels for decades, 'cos send-pr / https://bugs.freebsd.org/bugzilla/enter_bug.cgi & volunteer unpaid commiters can't keep up with submissions. & non committers can't afford to wait months or years, remembering what's been seen commited to Release X.Y & what still needs to be kept to apply to other inc. older releases. Probably lots of re-invented wheels: trees of diffs & applicator scripts, but to different standards, not uniformly exportable, not immediately familiar to & usable by others. While retaining the model of "This generic src/ ports/ doc/ tree has been built from patches blessed by commiters as fit for all" FreeBSD hackers(especially non commiters who must wait for commits to reduce their heap of candidate diffs) would benefit from a unified set of tools & directory formats to allow individuals to maintain & export trees of candidate diffs etc to some common standards. It wouldnt obviate / replace send-pr & https://bugs.freebsd.org/bugzilla/enter_bug.cgi & git etc, but would be an optional normalied convenience, especially beneficial to those who are Not commiters but who have growing heaps of uncommited patches. Maybe a summer of code or other person might look at Jamie's & my applicator scripts, & diff tree shapes, not for our actual current diffs, but to design common unified standards to export trees of candidate diffs that can be applied by one common applicator tool ? Hacker who are not committers presumably accumulate an an ever growing heap of diffs, a burden best normalised & automated. > I know it's a volunteer effort, but I've been here 25 years, and whilst > I could (and should) take on more port-maintainership, any other offers > of help have fallen on deaf ears. > > *shrug* I miss Mark Linimon. Cheers, -- Julian Stacey http://StolenVotes.UK/jhs/ Arm Ukraine, Zap Putin. From nobody Mon Jan 30 05:52:41 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4y4v2L2Bz3bGWM for ; Mon, 30 Jan 2023 05:52:31 +0000 (UTC) (envelope-from ihor@antonovs.family) Received: from mail.antonovs.family (mail.antonovs.family [100.25.240.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.antonovs.family", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4y4t6MB7z3Gl2 for ; Mon, 30 Jan 2023 05:52:30 +0000 (UTC) (envelope-from ihor@antonovs.family) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=antonovs.family header.s=20200215 header.b="x/5w/xG/"; spf=pass (mx1.freebsd.org: domain of ihor@antonovs.family designates 100.25.240.195 as permitted sender) smtp.mailfrom=ihor@antonovs.family; dmarc=pass (policy=none) header.from=antonovs.family DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antonovs.family; s=20200215; t=1675057945; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Es0I/t49LZzjl/ITYe30U6gzRD8w+LcPrJrBt8zxhB4=; b=x/5w/xG/WXRnGd5WzDcXcX8E5oyWZ/25J/Q5fBY4v6cs4ijJ6CzNCC8bDVV2rMSr7rYPnL 44a8TgGcDQkBQVV2poMQfXlJwh7KPTPjS4GRZ7nrSTW4wwuA0VHBv/6qtg2ZyF+YLA+nLw nWctLqAv5NQfEV3ZvzYaRaYzIlrXvwA= Received: by mail.antonovs.family (OpenSMTPD) with ESMTPSA id 30ae20df (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Mon, 30 Jan 2023 05:52:25 +0000 (UTC) Message-ID: <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> Date: Mon, 30 Jan 2023 05:52:41 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Tooling Integration and Developer Experience Content-Language: en-US To: freebsd-current@freebsd.org References: <202301300254.30U2sm0k061914@dell.no.berklix.net> From: User Ngor In-Reply-To: <202301300254.30U2sm0k061914@dell.no.berklix.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.93 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.930]; DMARC_POLICY_ALLOW(-0.50)[antonovs.family,none]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[antonovs.family:s=20200215]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[antonovs.family:+]; ASN(0.00)[asn:14618, ipnet:100.24.0.0/13, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4P4y4t6MB7z3Gl2 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 1/30/23 02:54, Julian H. Stacey wrote: > Jamie Landeg-Jones wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 is a trivial fix >> to an admittedly trivial issue, but it's soon going to hit one year old, >> and has not had any feedback. Not even "this is rubbish. close ticket" >> >> | jamie@catwalk:~ % stat 'so good they named it twice' >> | stat: so good they named it twice: stat: No such file or directory >> >> As such, it's the oldest of my patches to be completely ignored, but then, >> most of my fixes I haven't even submitted, because, what's the point? >> I've instead spent time writing something so the patches are automatically >> aplied to my src tree, and distributed to all my servers. Forked from: 1 year src-patch anniversary. I feel Jamie's pain,  this kind of experience can be very discouraging to any contributor without commit bit. All developers like quick feedback loops. Nobody wants to wait a year. I think FreeBSD project looses a lot of potential contributors due to issues of this kind. I don't believe there is any ill intent, there is no elite cast of grumpy commit-bit holders who only work on what they are interested in, ignoring the project as a whole. Far from it. But I do hope that the situation can be improved and I want to offer my view and opinion. The Problem ----------- I do believe that the source of all problems is lack of integration in tooling and communication. Let me elaborate: FreeBSD project has a lot of tools, but the tools are not well integrated together: - There are too many places where a patch can be posted: phabricator, github,   bugzilla, mailing list. - There are too many places to have a conversation: mailing lists, phabricator   reviews, bugzilla comments, github issues and PRs, forum, multiple IRC   channels spanning multiple IRC servers, etc. - A posted patch is cat in the bag, there is no pre-commit CI to do some basic   sanity-checking, commit-bit holders need to do a lot of work to verify the commit   (run CI on it) - Tools are not integrated. There is no information flow between them, no   effective cross-referencing, lookup or discover, etc.   - Bugs in Bugzilla are not visible in Phabricator.   - Commits in Phabricator do not resolve bugs in Bugzilla   - Jenkins CI/CD and Phabricator don't know about each other. ... there are probably more examples, but this is enough to draw a few conclusions: 1. Information is fragmented and is easily lost or forgotten. 2. It takes manual human effort to update information in multiple systems. 3. Human attention (developers, contributors, etc.) to different systems is spread    unequally. This leads to poor developer experience, regardless of commit-bit status. A patch posted in bugzilla went unnoticed for a year until frustrated and desperate contributor started complaining about it in the mailing list, and was committed hours later. The is also a lack of designated maintainers (I am drawing the analogy from Linux kernel) A role who's job is to integrate: collect all patches, feedback, reports about a specific area (kernel subsystem, userland tool or whatnot), and update/curate the knowledge and communication around this area. In my 15+ year career in IT I've seen multiple projects fail due to communication and integration issues. Without concentrated effort and strong leadership these problems rarely go away on their own. Proposed Solutions ------------------ In the order of implementation: 1. Tooling integration:    This can be as easy as moving everything into Phabricator.    Phabricator, apart from features that we already use, has support for CI/CD,    bug reports, wiki, project planning and milestones, chat, etc.    Alternative platforms can be used as well: GitLab, SourceHut    The main idea: to prevent information fragmentation and improve    discoverability, cross-referencing abilities, search, etc.    The challenge: is inertia and migration of existing information out    of currently used tools.    The sentiment: we don't need more tools, we need fewer tools that work    better together. 2. Growing the community:    Integrated tooling improves productivity and allows focusing on quickening    the feedback loop: accepting/rejecting/commenting one-off contributions faster.    Regular contributors will be more visible and will get commit-bit faster.    With enough commit-bit holders focused maintainership practice can be started. In the end this is just my opinion, I hope it will spark some conversation. Thanks for reading this far :) -- Ihor Antonov From nobody Mon Jan 30 09:46:17 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P53WZ0QxVz3c5xC for ; Mon, 30 Jan 2023 09:57:30 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ictdccexch001.one.local", Issuer "Stormshield Servers CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P53WY40P6z3pwj for ; Mon, 30 Jan 2023 09:57:29 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=stormshield.eu header.s=signer header.b=d+lvMeUT; spf=pass (mx1.freebsd.org: domain of Stephane.ROCHOY@stormshield.eu designates 91.212.116.25 as permitted sender) smtp.mailfrom=Stephane.ROCHOY@stormshield.eu; dmarc=pass (policy=quarantine) header.from=stormshield.eu DKIM-Signature: v=1; a=rsa-sha256; d=stormshield.eu; s=signer; c=simple/simple; t=1675072648; h=from:subject:to:date:message-id; bh=6TroVSQi4Nm+D46fRwCsYEn08mbV0pIXxK0teVickXc=; b=d+lvMeUTr7UH00l7BjJz7rltRV0qysJny/+PjKNzoEA+u+Zm1wbQvszGnXyBU08eVzvTVm39QWs 5scHx2cVBDX1JDId0dAAImEJz+8a7g293O/BpIGgavyZ2bB1m9GizLJAThAmXhBRYHrTYHK/Zsnof gBTkQUVjQCsHd36AqTRjiE+59uspN7obWt2iEiLNrq+mOY6f1ZkaS8NVeDLC57Wd4tJPgVU/omy9Z tV/5Tz+qum8zhTh33eXInWi3RTSqElC0ss3ZPZYS9LGcbO1PkckwYEkKvpcjY6916ow1A90mp6jL8 zxu1EbAgEyUN3dtFmwL7bFb1PklEHq2jOa2w== Received: from cthulhu.stephaner.labo.int (10.2.16.1) by ICTDCCEXCH001.one.local (10.180.4.1) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21; Mon, 30 Jan 2023 10:57:28 +0100 Received: by cthulhu.stephaner.labo.int (Postfix, from userid 1001) id CD4BE1FDC9; Mon, 30 Jan 2023 10:46:17 +0100 (CET) References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> User-agent: mu4e 1.2.0; emacs 27.1 From: Stephane Rochoy To: Subject: Re: Tooling Integration and Developer Experience In-Reply-To: <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> Date: Mon, 30 Jan 2023 10:46:17 +0100 Message-ID: <86357sxsly.fsf@cthulhu.stephaner.labo.int> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Originating-IP: [10.2.16.1] X-ClientProxiedBy: ICTDCCEXCH001.one.local (10.180.4.1) To ICTDCCEXCH001.one.local (10.180.4.1) X-Spamd-Result: default: False [-3.96 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.964]; DMARC_POLICY_ALLOW(-0.50)[stormshield.eu,quarantine]; R_DKIM_ALLOW(-0.20)[stormshield.eu:s=signer]; R_SPF_ALLOW(-0.20)[+ip4:91.212.116.25]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[stormshield.eu:+]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; HAS_XOIP(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR] X-Rspamd-Queue-Id: 4P53WY40P6z3pwj X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N User Ngor writes: > On 1/30/23 02:54, Julian H. Stacey wrote: > The main idea: to prevent information fragmentation and=20 > improve > discoverability, cross-referencing abilities, search, etc. With regards to improving discoverability, Phabricator's Owner tool could be a good tactical move: it allow to bind code area to peoples in order to automatically add them to reviews. It would help the committer discover the patch, and the non-committer who to talk with. Note that Owner seems to already be in use. And Herald seems to be partially used for the same purpose, i.e., send me an email or add me as a reviewer if review is about a given code area. Regards, -- St=C3=A9phane Rochoy O: Stormshield From nobody Mon Jan 30 10:08:40 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P53mg4lwyz3c7nt for ; Mon, 30 Jan 2023 10:08:51 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P53mf6YPPz3s0g for ; Mon, 30 Jan 2023 10:08:50 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:14f8:200::1 is neither permitted nor denied by domain of pi@freebsd.org) smtp.mailfrom=pi@freebsd.org; dmarc=none Received: from pi by home.opsec.eu with local (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pMR5c-0004cf-1D for freebsd-current@freebsd.org; Mon, 30 Jan 2023 11:08:40 +0100 Date: Mon, 30 Jan 2023 11:08:40 +0100 From: Kurt Jaeger To: freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Message-ID: References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> X-Spamd-Result: default: False [-3.08 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.976]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; RCVD_TLS_LAST(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[pi]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[freebsd.org]; TO_DN_NONE(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4P53mf6YPPz3s0g X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hi! ihor@antonovs.family wrote: > This can be as easy as moving everything into Phabricator. There's the issue that Phabricator itself is no longer supported upstream: https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/ https://github.com/phacility/phabricator I have notes from Oct. 2021 which point to a fork: https://we.phorge.it/ That fork seems to be somewhat alive. Moving our phab instance to phorge is probably no trivial task. -- pi@opsec.eu +49 171 3101372 Now what ? From nobody Mon Jan 30 10:11:28 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P53qz0gKbz3c8Lg for ; Mon, 30 Jan 2023 10:11:43 +0000 (UTC) (envelope-from yklaxds@gmail.com) Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P53qy5s3Bz3t2L for ; Mon, 30 Jan 2023 10:11:42 +0000 (UTC) (envelope-from yklaxds@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vk1-xa2e.google.com with SMTP id t190so5449918vkb.13 for ; Mon, 30 Jan 2023 02:11:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=knFY6eghJW5rOZPbQoKUHia/OCG+LTIbOicyWEfxd9U=; b=UQFmAGVPbD/hnn9dU5DUe3AkkW1PINAQL534T+IgdQ4oSAnOImM9ifPuqv5s8Ma0zE PwWAT/5CwYwcV+xvkzDnHS6jDowzkK+2FiYQxU7wg/arUUDGXZ03MBUbFR7RIJxHeloG O9sARDaV2HujICevadJh3Wdx7t4hbh10ogJLEtsSZtAiV0NbwWeo/JDjKYODKeugUtpT GFfnTmFgeNv9SPcd/uUQPSi7b/wRtXQfwA1UuDbv/ZL0wmx0fz7MfEEFnPUkyCYuX2GK ggG8Q8ufnWXZfrxc2OOpqQxavdGwnXDbvw2MbQ8vCS9q2skeUJUEjpgAagNXzLWCbJVi UowA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=knFY6eghJW5rOZPbQoKUHia/OCG+LTIbOicyWEfxd9U=; b=J0nXw/jrisKH3v69dEOSae+Bjb9sdHYqhnH5TwoPqmOXGD6pDIsBjSurIenvx3oYt0 OEPLYa/FE9UPP5DwEiHYIEJwXN5Rgjpim6mcWhnZicfUxlp26WyjGTs/gbcjy/522wVF FXdj65RVpNeHMVYuhzIaZcL+MjL4yb1eHOw+CAxjxHWZPJ/Hun3fLyfpA+TwNq+zZiPh gmdKLi3nd9v3QxkAvOPD94rz4ViAdr94Bqz1lCRZntXOgYocnULRT8MzAjNdZIVh6bCH ZR/Fl8fk3WHfBgD+wqebUIfBgy44xh/yf5JKIkC/Bd4re7Yr4i7cTe7biqQsmASxa5wL BaGA== X-Gm-Message-State: AO0yUKUwTclEiJhA2RxAblnC3pNFN/qf7JVYOJctPCoK+EMKfEnukWHu qrNIgKQuH4Kc5GcuhWhM8Z4oi/9/H1ORbht7NEw4MUTzLhJL5iI9KwA= X-Google-Smtp-Source: AK7set91yj15FnQ9yViev95MOcdugt4LFliOf3A8OCOhXwjc3gGY+i+71pTm5g4eYaifdHaRDj9WlnKQNhuiOkzpCkk= X-Received: by 2002:a05:6122:e15:b0:3e8:8f:f3a7 with SMTP id bk21-20020a0561220e1500b003e8008ff3a7mr1820334vkb.30.1675073501940; Mon, 30 Jan 2023 02:11:41 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> In-Reply-To: <86357sxsly.fsf@cthulhu.stephaner.labo.int> From: ykla Date: Mon, 30 Jan 2023 18:11:28 +0800 Message-ID: Subject: Re: Tooling Integration and Developer Experience To: Stephane Rochoy Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000000e4e7605f378713b" X-Rspamd-Queue-Id: 4P53qy5s3Bz3t2L X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000000e4e7605f378713b Content-Type: text/plain; charset="UTF-8" Hi, I had a similar thing happen to me, the mailing list FreeBSD-doc seemed to exist as if no one existed, and there was no one posting in it except for the automated bug reports from the bots. I have not had any replies to my several posts either. So can the admins tell how many people actually subscribe to FreeBSD-doc, or is this just a place to report bugs and people should discuss FreeBSD doc-related issues elsewhere? Or is it that almost nobody cares about the FreeBSD documentation? ykla --0000000000000e4e7605f378713b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I had a similar thing ha= ppen to me, the mailing list FreeBSD-doc seemed to exist as if no one exist= ed, and there was no one posting in it except for the automated bug reports= from the bots. I have not had any replies to my several posts either. So c= an the admins tell how many people actually subscribe to FreeBSD-doc, or is= this just a place to report bugs and people should discuss FreeBSD doc-rel= ated issues elsewhere? Or is it that almost nobody cares about the FreeBSD = documentation?

ykla
--0000000000000e4e7605f378713b-- From nobody Mon Jan 30 10:33:33 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P54KC0S6Cz3cBrF for ; Mon, 30 Jan 2023 10:33:35 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P54KB286Jz3x9q for ; Mon, 30 Jan 2023 10:33:34 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:14f8:200::1 is neither permitted nor denied by domain of pi@freebsd.org) smtp.mailfrom=pi@freebsd.org; dmarc=none Received: from pi by home.opsec.eu with local (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pMRTh-0004ma-1G for freebsd-current@freebsd.org; Mon, 30 Jan 2023 11:33:33 +0100 Date: Mon, 30 Jan 2023 11:33:33 +0100 From: Kurt Jaeger To: freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Message-ID: References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-2.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.40)[-0.400]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[pi]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[freebsd.org]; TO_DN_NONE(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[] X-Rspamd-Queue-Id: 4P54KB286Jz3x9q X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Hello, > I had a similar thing happen to me, the mailing list FreeBSD-doc seemed to > exist as if no one existed, and there was no one posting in it except for > the automated bug reports from the bots. > I have not had any replies to my several posts either. > So can the admins tell how many people actually > subscribe to FreeBSD-doc, The list has 496 subscribers right now. (speaking as one of postmaster@). > or is this just a place to report bugs and people > should discuss FreeBSD doc-related issues elsewhere? Or is it that almost > nobody cares about the FreeBSD documentation? >From my observation, the last few month led to a huge pile of workload on many folks that are involved with FreeBSD stuff, so not many folks had time to reply/think things through/answer. I had the same problem... I see doc-stuff happen mostly on reviews.freebsd.org. (speaking as one of phabric-admins). Pau Amma is the most active docs-person as far as I can see. I have not calculated stats, just my gut feeling. -- pi@opsec.eu +49 171 3101372 Now what ? From nobody Mon Jan 30 10:40:37 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P54TN3RzYz3cCKB for ; Mon, 30 Jan 2023 10:40:40 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P54TN304lz40p1 for ; Mon, 30 Jan 2023 10:40:40 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi by home.opsec.eu with local (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pMRaX-0004pU-Vs; Mon, 30 Jan 2023 11:40:37 +0100 Date: Mon, 30 Jan 2023 11:40:37 +0100 From: Kurt Jaeger To: Stephane Rochoy Cc: freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Message-ID: References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86357sxsly.fsf@cthulhu.stephaner.labo.int> X-Rspamd-Queue-Id: 4P54TN304lz40p1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hi, > > On 1/30/23 02:54, Julian H. Stacey wrote: > > The main idea: to prevent information fragmentation and improve > > discoverability, cross-referencing abilities, search, etc. > > With regards to improving discoverability, Phabricator's Owner > tool could be a good tactical move: it allow to bind code area to > peoples in order to automatically add them to reviews. If you know phabricator in more detail, is there any kind of tool to understand the activity going on ? In bugs.freebsd.org, there is the dashboard: https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html I think we might need something similar to help us understand the current state of the phabricator instance and the work being done. Phab allows Dashboards, but no-one had the time to configure some queries to provide relevant stats. -- pi@opsec.eu +49 171 3101372 Now what ? From nobody Mon Jan 30 13:53:36 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P58m551Zwz3ckjF for ; Mon, 30 Jan 2023 13:53:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P58m52BNHz3Q1J for ; Mon, 30 Jan 2023 13:53:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-xe2a.google.com with SMTP id h19so10731597vsv.13 for ; Mon, 30 Jan 2023 05:53:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Z+BctaI5NlmnWNpQ3wEHnMuKx9jQL42iYMV0AXaAn0o=; b=bGy6FdTc45hs3sLtdqEtg+ARIoUUdvfC3mteCGcyQSgHb1/zg93r7QiybVdKttKF9b GwZX21UjR5jU+3tcmJxwgJ2ktSHln5AMEY3FS7rGSyNQryB14z96I2NNtzwQ21VgpBtr MACOIdiyg1AJqTk/VcXD7tF7B/DBhUGzIbT+Y14s3+Bu1J4I/nqIDN+Dt5wdHOJJtAB+ WooZ06eZ2+jqhWcFcvl72pPr6DXGGl/sBfZqNN+wJ70zjp2KT76sAk9UHp7GQhJMcdpO c/hfW5x+eTtLLd0AUpkJJD8tfJZ7WFLHL2o0EWnuEmBVRPsbFou/RfW5+ETIkjW8QHRa AM5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Z+BctaI5NlmnWNpQ3wEHnMuKx9jQL42iYMV0AXaAn0o=; b=W4w0dJomnc45dfzYjmJc3GaRDx93sLnK9htkr6lXP9QGcZtukBs/dixJUP3foQFqY/ FyoRvw4kiajrgbfk/GAI4DMk+4/BYghUCo3ZcE1tONkpm4dnze5hmbuiRDllBVMKNgKG e1jlQV63DsTaff/NqC32DmTOaMZ07pBTxm6Vzo9++jsnZdH0VZlOCsUdBreDXuDXmaro 14QbFsKnv99m4HX08Z3okeMwrPIvCu1+5X3LlRB4M5GKZ9vQYrR1BDaV1cKS5cr3XKjQ TuNyAapiNHh+TQgwb5DNlMzs5TSqrJ+4fwNWnlQgJrEgND6xqTGGSzj6l4xw1lhD6U5P vcqg== X-Gm-Message-State: AO0yUKVKl/sHEqgY7fKzDeGpxMDq0j83Qhs03hxbVDwRbuN7aUnJVnxq FE3ZFqluYzqWiFbt8r++x+mWZcD8I5JDrtcsD4HQxPycIQFkkw== X-Google-Smtp-Source: AK7set/iOfYGWTEaksqaJTSBeEBV7BB18SKz8/KdT5ldgz5c+jFg/HC0vOXE1iXlFt2V3GSZc78dFZtEwNfbRtLVd+Y= X-Received: by 2002:a67:bc06:0:b0:3f4:a031:f77c with SMTP id t6-20020a67bc06000000b003f4a031f77cmr750962vsn.25.1675086820425; Mon, 30 Jan 2023 05:53:40 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> In-Reply-To: From: Warner Losh Date: Mon, 30 Jan 2023 06:53:36 -0700 Message-ID: Subject: Re: Tooling Integration and Developer Experience To: Kurt Jaeger Cc: Stephane Rochoy , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000e659a605f37b8ae0" X-Rspamd-Queue-Id: 4P58m52BNHz3Q1J X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000e659a605f37b8ae0 Content-Type: text/plain; charset="UTF-8" On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote: > Hi, > > > > On 1/30/23 02:54, Julian H. Stacey wrote: > > > The main idea: to prevent information fragmentation and improve > > > discoverability, cross-referencing abilities, search, etc. > > > > With regards to improving discoverability, Phabricator's Owner > > tool could be a good tactical move: it allow to bind code area to > > peoples in order to automatically add them to reviews. > > If you know phabricator in more detail, is there any kind of tool > to understand the activity going on ? > > In bugs.freebsd.org, there is the dashboard: > > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html > > I think we might need something similar to help us understand > the current state of the phabricator instance and the work > being done. > > Phab allows Dashboards, but no-one had the time to configure some > queries to provide relevant stats. > Phab is a terrible tool for discovery. For example, how do I query all the reviews I've ticked 'OK' that are still open, by non-committers? How do I flag things as 'interesting to me'? I can tick a flag, but I can't query flags. Also, I can't get an email address for submitter either. That makes it more of a pain to land the commit. Buzilla is in many ways worse (it's absolutely terrible for doing code reviews, though it's queryability is much better). In some ways it's better for changes that are ready to go, since you can upload git format-patch output, but it too has discoverability issues. Github and gitlab pull requests are better in some ways, but worse in others. The review tool isn't as good as phab, and when you have a lot of them, they are hard to organize. But it's my preferred way to land patches because it's absolutely the easiest from a developer point of view to do so: It's one command (though the commands differ between the two). The foundation is funding the CI aspect of this: Getting jobs that developers and automation can run to gate in place. Until we have that in place and integrated together, things will be harder. But there's two other issues: The FreeBSD project has had a long history of being behind, regardless of the tools we use. There's a labor shortage to process these things as well. Second, lots of people want to talk, but few want to do the work. I tried leading an effort in this area,but grew weary of the passive-aggressive comments about how I basically sucked for not having it done already (from the same people that did 0 actual work on it). Warner --000000000000e659a605f37b8ae0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jan 30, 2023 at 3:40 AM Kurt = Jaeger <pi@freebsd.org> wrote:<= br>
Hi,

> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >=C2=A0 =C2=A0 The main idea: to prevent information fragmentation = and=C2=A0 =C2=A0 improve
> >=C2=A0 =C2=A0 discoverability, cross-referencing abilities, search= , etc.
>
> With regards to improving discoverability, Phabricator's Owner
> tool could be a good tactical move: it allow to bind code area to
> peoples in order to automatically add them to reviews.

If you know phabricator in more detail, is there any kind of tool
to understand the activity going on ?

In bugs.freebsd.org, there is the dashboard:

https://bugs.freebsd.org/bugzilla/page= .cgi?id=3Ddashboard.html

I think we might need something similar to help us understand
the current state of the phabricator instance and the work
being done.

Phab allows Dashboards, but no-one had the time to configure some
queries to provide relevant stats.

Phab= is a terrible tool for discovery. For example, how do I query all the revi= ews I've ticked 'OK' that are still open, by non-committers? Ho= w do I flag things as 'interesting to me'? I can tick a flag, but I= can't query flags. Also, I can't get an email address for submitte= r either. That makes it more of a pain to land the commit.

Buzilla is in many ways worse (it's absolutely terrible for do= ing code reviews, though it's queryability is much better). In some way= s it's better for changes that are ready to go, since you can upload gi= t format-patch output, but it too has discoverability issues.

Github and gitlab pull requests are better in some ways, b= ut worse in others. The review tool isn't as good as phab, and when you= have a lot of them, they are hard to organize. But it's my preferred w= ay to land patches because it's absolutely the easiest from a developer= point of view to do so: It's one command (though the commands differ b= etween the two).

The foundation is funding the CI = aspect of this: Getting jobs that developers and automation can run to gate= in place. Until we have that in place and integrated together, things will= be harder.

But there's two other issues: The = FreeBSD project has had a long history of being behind, regardless of the t= ools we use. There's a labor shortage to process these things as well. = Second, lots of people want to talk, but few want to do the work. I tried l= eading an effort in this area,but grew weary of the passive-aggressive comm= ents about how I basically sucked for not having it done already (from the = same people that did 0 actual work on it).

War= ner
--000000000000e659a605f37b8ae0-- From nobody Mon Jan 30 14:00:06 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P594B4G0Bz3bHVm for ; Mon, 30 Jan 2023 14:07:38 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from mcusim.org (mcusim.org [176.58.93.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P594B2KWQz3hNs; Mon, 30 Jan 2023 14:07:38 +0000 (UTC) (envelope-from dsl@mcusim.org) Authentication-Results: mx1.freebsd.org; none Received: from localhost (unknown [193.164.254.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mcusim.org (Postfix) with ESMTPSA id 902408A333; Mon, 30 Jan 2023 15:07:29 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mcusim.org; s=default; t=1675087649; bh=o93dmjfiLK1obY99IWV5urvPPRs1zqrHUayX+QrNJ78=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=xA61RPxTZL32qWYZAq5rqexAM5bvmhC8fvgfCjCT/RzNjH4zGlaIxIBSq8t6p8ouA igE9jFf8ik5ZOcmWXi6UNcQMTtvmHU2PI+IfHNW93P6AePt8Fzv6oIrOwA207oXrKh dBfK2/J9tXRCn+UjAC4Z8iQwnQBhk0ncBSyud9Ng= References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> User-agent: mu4e 1.6.10; emacs 28.2 From: Dmitry Salychev To: Kurt Jaeger Cc: Stephane Rochoy , freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Date: Mon, 30 Jan 2023 15:00:06 +0100 In-reply-to: Message-ID: <86edrcp13z.fsf@peasant.tower.home> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4P594B2KWQz3hNs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:176.58.93.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hi, Kurt Jaeger writes: > Hi, > >> > On 1/30/23 02:54, Julian H. Stacey wrote: >> > The main idea: to prevent information fragmentation and improve >> > discoverability, cross-referencing abilities, search, etc. >> >> With regards to improving discoverability, Phabricator's Owner >> tool could be a good tactical move: it allow to bind code area to >> peoples in order to automatically add them to reviews. > > If you know phabricator in more detail, is there any kind of tool > to understand the activity going on ? > > In bugs.freebsd.org, there is the dashboard: > > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html > > I think we might need something similar to help us understand > the current state of the phabricator instance and the work > being done. > > Phab allows Dashboards, but no-one had the time to configure some > queries to provide relevant stats. I'd prefer to have an automatic note via email from Phabricator if any file with my copyright was modified/patched/improved in a newly opened review. I don't think that people tend to ignore changes to those parts of code they've written (or touched at least). -- Dmitry Salychev From nobody Mon Jan 30 14:31:02 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P59bD3fdzz3bLVV for ; Mon, 30 Jan 2023 14:31:04 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ictdccexch001.one.local", Issuer "Stormshield Servers CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P59bD2Rzyz3lL0; Mon, 30 Jan 2023 14:31:04 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; d=stormshield.eu; s=signer; c=simple/simple; t=1675089063; h=from:subject:to:date:message-id; bh=/w/U4unJRw/JGiO8DjaPyLlj1n5AH2SQxGCRt4j+M8Y=; b=rfriXv4DxZWbi8dnkrIEeTEvcfASb/v2liiRRBCOlaWXAqM2n074Ohqr8RQK8w8K7s/gUlIGIo/ hHNo7jUod6hfUuedxGDGxmZWx3F9b71BbAe34Svq9LTP0b7lSeE2ZWeEkWq+tkA1D0URAuvCUWkDY zYtbHCfBHQ69UVWD91g63zrq3gXaMUPLc66EucXp5whBkbpxztLaOdT3fbzNfom6Q2CSdz/dcPPuR zQ1YedpgD3EKq5U3NQJADlhaEgZQvPgOZGOFiKIGft88R97xwkt1lfYtXjlZ3gfNG0f5fZETNZtWh ArZWFLORWRgi23avWBq6KcBTFGtGZVbTnobw== Received: from cthulhu.stephaner.labo.int (10.2.16.1) by ICTDCCEXCH001.one.local (10.180.4.1) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21; Mon, 30 Jan 2023 15:31:02 +0100 Received: by cthulhu.stephaner.labo.int (Postfix, from userid 1001) id C8B711FDC9; Mon, 30 Jan 2023 15:31:02 +0100 (CET) References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> User-agent: mu4e 1.2.0; emacs 27.1 From: Stephane Rochoy To: Kurt Jaeger CC: Stephane Rochoy , Subject: Re: Tooling Integration and Developer Experience In-Reply-To: Date: Mon, 30 Jan 2023 15:31:02 +0100 Message-ID: <861qncxffd.fsf@cthulhu.stephaner.labo.int> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Originating-IP: [10.2.16.1] X-ClientProxiedBy: ICTDCCEXCH001.one.local (10.180.4.1) To ICTDCCEXCH001.one.local (10.180.4.1) X-Rspamd-Queue-Id: 4P59bD2Rzyz3lL0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Kurt Jaeger writes: > If you know phabricator in more detail, is there any kind of > tool to understand the activity going on ? > > In bugs.freebsd.org, there is the dashboard: > > https://bugs.freebsd.org/bugzilla/page.cgi?id=3Ddashboard.html > > I think we might need something similar to help us understand > the current state of the phabricator instance and the work > being done. > > Phab allows Dashboards, but no-one had the time to configure=20 > some > queries to provide relevant stats. AFAIK, dashboards are just a way to gather data from the various applications. In our case, the relevant one is Differential which means we're limited to what its query engine [1] allow us to do. My guess is that playing with the "Repositories", "Statuses" and "Created After" fields should be OK to get to the "Bug Summary" but it would give you lists of bugs, not the amounts of bugs. The "Useful Queries" are more tricky. Maybe by putting tags (e.g., to identify required backports, etc=E2=80=A6) in use something could be done. If not, the Conduit API could be worth a look. [1] https://reviews.freebsd.org/differential/query/advanced/ Regards, -- St=C3=A9phane Rochoy O: Stormshield From nobody Mon Jan 30 14:28:50 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P59r52T7bz3bMQV for ; Mon, 30 Jan 2023 14:42:13 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from mcusim.org (mcusim.org [IPv6:2a00:dd80:3c::e63]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P59r50Sp1z3nTt; Mon, 30 Jan 2023 14:42:13 +0000 (UTC) (envelope-from dsl@mcusim.org) Authentication-Results: mx1.freebsd.org; none Received: from localhost (unknown [193.164.254.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mcusim.org (Postfix) with ESMTPSA id 5B8B68A466; Mon, 30 Jan 2023 15:42:04 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mcusim.org; s=default; t=1675089724; bh=73M7NTyzWmpHyYZGQbpyc4yAaElm59/XttrRV0Zqnqo=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=HThOYJDralsqN03ZNyjHPV/vNYC83/qEvZ/SwI1ch2w1El6D7lnh0qvZ09YHQux16 Q38QdmnKKQSha0IxBb9LdgG8vtSaBlyGB3P8HBLFi0o/tUEL5aC16lOj1rdGx+Vl4a 0fAq6HDAJhpfLgstPvvwJMvvmZU87Ql+h3HYeSNE= References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> User-agent: mu4e 1.6.10; emacs 28.2 From: Dmitry Salychev To: Warner Losh Cc: Kurt Jaeger , Stephane Rochoy , freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Date: Mon, 30 Jan 2023 15:28:50 +0100 In-reply-to: Message-ID: <867cx4ozic.fsf@peasant.tower.home> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4P59r50Sp1z3nTt X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:2a00:dd80:3c::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Warner Losh writes: > On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote: > > Hi, > > > > On 1/30/23 02:54, Julian H. Stacey wrote: > > > The main idea: to prevent information fragmentation and improve > > > discoverability, cross-referencing abilities, search, etc. > > > > With regards to improving discoverability, Phabricator's Owner > > tool could be a good tactical move: it allow to bind code area to > > peoples in order to automatically add them to reviews. > > If you know phabricator in more detail, is there any kind of tool > to understand the activity going on ? > > In bugs.freebsd.org, there is the dashboard: > > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html > > I think we might need something similar to help us understand > the current state of the phabricator instance and the work > being done. > > Phab allows Dashboards, but no-one had the time to configure some > queries to provide relevant stats. > > Phab is a terrible tool for discovery. For example, how do I query all the reviews I've ticked 'OK' that are still open, by non-committers? > How do I flag things as 'interesting to me'? I can tick a flag, but I can't query flags. Also, I can't get an email address for submitter either. > That makes it more of a pain to land the commit. > > Buzilla is in many ways worse (it's absolutely terrible for doing code reviews, though it's queryability is much better). In some ways it's > better for changes that are ready to go, since you can upload git format-patch output, but it too has discoverability issues. > > Github and gitlab pull requests are better in some ways, but worse in others. The review tool isn't as good as phab, and when you have a > lot of them, they are hard to organize. But it's my preferred way to land patches because it's absolutely the easiest from a developer > point of view to do so: It's one command (though the commands differ between the two). > > The foundation is funding the CI aspect of this: Getting jobs that developers and automation can run to gate in place. Until we have that > in place and integrated together, things will be harder. > > But there's two other issues: The FreeBSD project has had a long history of being behind, regardless of the tools we use. There's a labor > shortage to process these things as well. Second, lots of people want to talk, but few want to do the work. I tried leading an effort in this > area,but grew weary of the passive-aggressive comments about how I basically sucked for not having it done already (from the same > people that did 0 actual work on it). > > Warner I'd want to express an obvious idea (sorry for that!), but from the newcomer's point of view, it's significantly easier to take care of those parts of code which he wrote or patched himself at least. As the FreeBSD project carries its legacy which is rather burden in this particular case, why not to prepare a plan of the small steps in order (a) to improve committer awarness of the changes in "their" code and (b) not to consume a lot of people's time? You can think about it as tweaking of the existing tools like Phabricator and Bugzilla instead of adopting new ones. -- Dmitry Salychev From nobody Mon Jan 30 14:51:11 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5B2n0t5Bz3bP2g for ; Mon, 30 Jan 2023 14:51:29 +0000 (UTC) (envelope-from qroxana@protonmail.com) Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch [185.70.40.137]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5B2m1jDMz3sDt for ; Mon, 30 Jan 2023 14:51:28 +0000 (UTC) (envelope-from qroxana@protonmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=tIOOQxWB; spf=pass (mx1.freebsd.org: domain of qroxana@protonmail.com designates 185.70.40.137 as permitted sender) smtp.mailfrom=qroxana@protonmail.com; dmarc=pass (policy=quarantine) header.from=protonmail.com Date: Mon, 30 Jan 2023 14:51:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1675090285; x=1675349485; bh=TkUxn/Z6Ami9VBDBghZO8yhgaHwLutjcXUzNnheSCLg=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=tIOOQxWBiJT2WOnKWiNfXAiAhndmb/URC7cgebiwgH4AyGEt9LybD6+A4gYgqXDUl vwFzYy97JfqLGFojrNXutovvBJBtzfBILWbofQ3MIuHVivDm5uq6ziFKUEuYLu5wp6 pyE2o0OMrC02ajjPLdqI/4QuudmIDBte9iCWkvNSWUgRxn9s/l7cYN6CkiJhBJZ07A QbFs+QMqzYWaOU4F3NA7v4aoQTR5MttFJy2vM775pWL0LAflTXIpx89c2Zz7eK6fGZ I0F85Du0dR9onVxHbXfq8r+b+oGixIV2KSrBNls79lmb6duXj8xn1oX7y7/44E1/fy iVKTfIkMWb6bg== To: "freebsd-current@freebsd.org" From: qroxana Subject: sbin/mount: failed to mount NFS root Message-ID: Feedback-ID: 29996633:user:proton List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_5tWiq9c027rx8zK86mX9bZaNeOveYeugO37N0M4JeDg" X-Spamd-Result: default: False [1.75 / 15.00]; MIME_BASE64_TEXT_BOGUS(1.00)[]; NEURAL_SPAM_LONG(1.00)[0.999]; NEURAL_SPAM_SHORT(0.95)[0.951]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_MEDIUM(-0.30)[-0.301]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail3]; MIME_BASE64_TEXT(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; TO_DN_EQ_ADDR_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[protonmail.com:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; HAS_PHPMAILER_SIG(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.137:from] X-Rspamd-Queue-Id: 4P5B2m1jDMz3sDt X-Spamd-Bar: + X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --b1_5tWiq9c027rx8zK86mX9bZaNeOveYeugO37N0M4JeDg Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 L2V0Yy9yYyBmYWlsZWQgdG8gcnVuICJtb3VudCAtdXcgLyIgd2hlbiBib290aW5nIGZyb20gTkZT IHJvb3QsCnRoaXMgaGFwcGVuZWQgYWZ0ZXIgdGhlIGNvbW1pdCA5MDZjMzEyYmJmNzQ5M2NjYmNj ZTg4MzkzNmQ2N2U1YzY2YTljM2MyLAp0aGUgcHJldmlvdXMgY29tbWl0IHdvcmtzIGZpbmUuCgor IG1vdW50IC11dyAvCmFmIDEgc290eXBlIDEgbm90IHN1cHBvcnRlZAorIGVjaG8gJ01vdW50aW5n IHJvb3QgZmlsZXN5c3RlbSBydyBmYWlsZWQsIHN0YXJ0dXAgYWJvcnRlZCcKTW91bnRpbmcgcm9v dCBmaWxlc3lzdGVtIHJ3IGZhaWxlZCwgc3RhcnR1cCBhYm9ydGVkCkVSUk9SOiBBQk9SVElORyBC T09UIChzZW5kaW5nIFNJR1RFUk0gdG8gcGFyZW50KSEKMjAyMy0wMS0zMFQxMDowOTowNS4xMTY5 MjArMDA6MDAgLSBpbml0IDEgLSAtIC9iaW4vc2ggb24gL2V0Yy9yYyB0ZXJtaW5hdGVkIGFibm9y bWFsbHksIGdvaW5nIHRvIHNpbmdsZSB1c2VyIG1vZGUKRW50ZXIgZnVsbCBwYXRobmFtZSBvZiBz aGVsbCBvciBSRVRVUk4gZm9yIC9iaW4vc2g6Cgpjb21taXQgOTA2YzMxMmJiZjc0OTNjY2JjY2U4 ODM5MzZkNjdlNWM2NmE5YzNjMgpBdXRob3I6IEtpcmsgTWNLdXNpY2sgPG1ja3VzaWNrQEZyZWVC U0Qub3JnPgpEYXRlOiBTdW4gSmFuIDE1IDEwOjIwOjQ4IDIwMjMgLTA4MDAKCkRvY3VtZW50IHRo ZSBtbnRvcHRzKDMpIGZ1bmN0aW9ucy4KClRoZSBtbnRvcHRzKDMpIGZ1bmN0aW9ucyBzdXBwb3J0 IG9wZXJhdGlvbnMgYXNzb2NpYXRlZCB3aXRoIGEgbW91bnQKcG9pbnQuIFRoZSBtYWluIHB1cnBv c2Ugb2YgdGhpcyBjb21taXQgaXMgdG8gZG9jdW1lbnQgdGhlIG1udG9wdHMoMykKZnVuY3Rpb25z IHRoYXQgbm93IGFwcGVhciBpbiAxOCB1dGlsaXRpZXMgaW4gdGhlIGJhc2Ugc3lzdGVtLiBTZWUK bW50b3B0cygzKSBmb3IgdGhlIGRvY3VtZW50YXRpb24gZGV0YWlscy4KClRoZSBnZXRtbnRvcHRz KCkgZnVuY3Rpb24gYXBwZWFyZWQgaW4gNC40QlNELiBUaGUgYnVpbGRfaW92ZWMoKSwKYnVpbGRf aW92ZWNfYXJnZigpLCBmcmVlX2lvdmVjKCksIGNoZWNrcGF0aCgpLCBhbmQgcm1zbGFzaGVzKCkK ZnVuY3Rpb25zIHdlcmUgYWRkZWQgd2l0aCBubW91bnQoOCkgaW4gRnJlZUJTRCA1LjAuIFRoZSBn ZXRtbnRwb2ludCgpCmFuZCBjaGtkb3JlbG9hZCgpIGZ1bmN0aW9ucyBhcmUgYmVpbmcgYWRkZWQg aW4gdGhpcyBjb21taXQuCgpUaGVzZSBmdW5jdGlvbnMgc2hvdWxkIGJlIGluIGEgbGlicmFyeSBi dXQgZm9yIGhpc3RvcmljIHJlYXNvbnMgYXJlCmluIGEgZmlsZSBpbiB0aGUgc291cmNlcyBmb3Ig dGhlIG1vdW50KDgpIHByb2dyYW0uIFRodXMsIHRvIGFjY2Vzcwp0aGVtIHRoZSBmb2xsb3dpbmcg bGluZXMgbmVlZCB0byBiZSBhZGRlZCB0byB0aGUgTWFrZWZpbGUgb2YgdGhlCnByb2dyYW0gd2Fu dGluZyB0byB1c2UgdGhlbToKClNSQ1MrPSBnZXRtbnRvcHRzLmMKTU9VTlQ9ICR7U1JDVE9QfS9z YmluL21vdW50CkNGTEFHUys9IC1JJHtNT1VOVH0KLlBBVEg6ICR7TU9VTlR9CgpPbmNlIHRoZXNl IGNoYW5nZXMgaGF2ZSBiZWVuIE1GQydlZCB0byAxMyB0aGV5IG1heSBiZSBtYWRlIGludG8KYSBs aWJyYXJ5LgoKUmV2aWV3ZWQgYnk6IGtpYiwgZ2JlCk1GQyBhZnRlcjogMiB3ZWVrcwpTcG9uc29y ZWQgYnk6IFRoZSBGcmVlQlNEIEZvdW5kYXRpb24KRGlmZmVyZW50aWFsIFJldmlzaW9uOiBodHRw czovL3Jldmlld3MuZnJlZWJzZC5vcmcvRDM3OTA3 --b1_5tWiq9c027rx8zK86mX9bZaNeOveYeugO37N0M4JeDg Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PHNwYW4+L2V0Yy9yYyBmYWlsZWQgdG8gcnVuICJtb3VudCAtdXcgLyIgd2hlbiBib290aW5nIGZy b20gTkZTIHJvb3QsPC9zcGFuPjxkaXY+PHNwYW4+dGhpcyBoYXBwZW5lZCBhZnRlciB0aGUgY29t bWl0IDkwNmMzMTJiYmY3NDkzY2NiY2NlODgzOTM2ZDY3ZTVjNjZhOWMzYzIsPC9zcGFuPjwvZGl2 PjxkaXY+PHNwYW4+dGhlIHByZXZpb3VzIGNvbW1pdCB3b3JrcyBmaW5lLjwvc3Bhbj48L2Rpdj48 ZGl2Pjxicj48L2Rpdj48ZGl2PjxzcGFuPisgbW91bnQgLXV3IC88L3NwYW4+PC9kaXY+PGRpdj48 c3Bhbj5hZiAxIHNvdHlwZSAxIG5vdCBzdXBwb3J0ZWQ8L3NwYW4+PC9kaXY+PGRpdj48c3Bhbj4r IGVjaG8gJ01vdW50aW5nIHJvb3QgZmlsZXN5c3RlbSBydyBmYWlsZWQsIHN0YXJ0dXAgYWJvcnRl ZCc8L3NwYW4+PC9kaXY+PGRpdj48c3Bhbj5Nb3VudGluZyByb290IGZpbGVzeXN0ZW0gcncgZmFp bGVkLCBzdGFydHVwIGFib3J0ZWQ8L3NwYW4+PC9kaXY+PGRpdj48c3Bhbj5FUlJPUjogQUJPUlRJ TkcgQk9PVCAoc2VuZGluZyBTSUdURVJNIHRvIHBhcmVudCkhPC9zcGFuPjwvZGl2PjxkaXY+PHNw YW4+MjAyMy0wMS0zMFQxMDowOTowNS4xMTY5MjArMDA6MDAgLSBpbml0IDEgLSAtIC9iaW4vc2gg b24gL2V0Yy9yYyB0ZXJtaW5hdGVkIGFibm9ybWFsbHksIGdvaW5nIHRvIHNpbmdsZSB1c2VyIG1v ZGU8L3NwYW4+PC9kaXY+PGRpdj48c3Bhbj5FbnRlciBmdWxsIHBhdGhuYW1lIG9mIHNoZWxsIG9y IFJFVFVSTiBmb3IgL2Jpbi9zaDo8L3NwYW4+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+ PC9kaXY+PGRpdj48c3Bhbj5jb21taXQgOTA2YzMxMmJiZjc0OTNjY2JjY2U4ODM5MzZkNjdlNWM2 NmE5YzNjMjwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFuPkF1dGhvcjogS2lyayBNY0t1c2ljayAmbHQ7 PGEgdGFyZ2V0PSJfYmxhbmsiIHJlbD0ibm9yZWZlcnJlciBub2ZvbGxvdyBub29wZW5lciIgaHJl Zj0ibWFpbHRvOm1ja3VzaWNrQEZyZWVCU0Qub3JnIj5tY2t1c2lja0BGcmVlQlNELm9yZzwvYT4m Z3Q7PC9zcGFuPjwvZGl2PjxkaXY+PHNwYW4+RGF0ZTogJm5ic3A7IFN1biBKYW4gMTUgMTA6MjA6 NDggMjAyMyAtMDgwMDwvc3Bhbj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNw OyAmbmJzcDsgRG9jdW1lbnQgdGhlIG1udG9wdHMoMykgZnVuY3Rpb25zLjwvc3Bhbj48L2Rpdj48 ZGl2Pjxicj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAmbmJzcDsgVGhlIG1udG9wdHMoMykgZnVu Y3Rpb25zIHN1cHBvcnQgb3BlcmF0aW9ucyBhc3NvY2lhdGVkIHdpdGggYSBtb3VudDwvc3Bhbj48 L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAmbmJzcDsgcG9pbnQuIFRoZSBtYWluIHB1cnBvc2Ugb2Yg dGhpcyBjb21taXQgaXMgdG8gZG9jdW1lbnQgdGhlIG1udG9wdHMoMyk8L3NwYW4+PC9kaXY+PGRp dj48c3Bhbj4mbmJzcDsgJm5ic3A7IGZ1bmN0aW9ucyB0aGF0IG5vdyBhcHBlYXIgaW4gMTggdXRp bGl0aWVzIGluIHRoZSBiYXNlIHN5c3RlbS4gU2VlPC9zcGFuPjwvZGl2PjxkaXY+PHNwYW4+Jm5i c3A7ICZuYnNwOyBtbnRvcHRzKDMpIGZvciB0aGUgZG9jdW1lbnRhdGlvbiBkZXRhaWxzLjwvc3Bh bj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAmbmJzcDsgVGhlIGdldG1u dG9wdHMoKSBmdW5jdGlvbiBhcHBlYXJlZCBpbiA0LjRCU0QuIFRoZSBidWlsZF9pb3ZlYygpLDwv c3Bhbj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAmbmJzcDsgYnVpbGRfaW92ZWNfYXJnZigpLCBm cmVlX2lvdmVjKCksIGNoZWNrcGF0aCgpLCBhbmQgcm1zbGFzaGVzKCk8L3NwYW4+PC9kaXY+PGRp dj48c3Bhbj4mbmJzcDsgJm5ic3A7IGZ1bmN0aW9ucyB3ZXJlIGFkZGVkIHdpdGggbm1vdW50KDgp IGluIEZyZWVCU0QgNS4wLiBUaGUgZ2V0bW50cG9pbnQoKTwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFu PiZuYnNwOyAmbmJzcDsgYW5kIGNoa2RvcmVsb2FkKCkgZnVuY3Rpb25zIGFyZSBiZWluZyBhZGRl ZCBpbiB0aGlzIGNvbW1pdC48L3NwYW4+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48c3Bhbj4m bmJzcDsgJm5ic3A7IFRoZXNlIGZ1bmN0aW9ucyBzaG91bGQgYmUgaW4gYSBsaWJyYXJ5IGJ1dCBm b3IgaGlzdG9yaWMgcmVhc29ucyBhcmU8L3NwYW4+PC9kaXY+PGRpdj48c3Bhbj4mbmJzcDsgJm5i c3A7IGluIGEgZmlsZSBpbiB0aGUgc291cmNlcyBmb3IgdGhlIG1vdW50KDgpIHByb2dyYW0uIFRo dXMsIHRvIGFjY2Vzczwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAmbmJzcDsgdGhlbSB0 aGUgZm9sbG93aW5nIGxpbmVzIG5lZWQgdG8gYmUgYWRkZWQgdG8gdGhlIE1ha2VmaWxlIG9mIHRo ZTwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAmbmJzcDsgcHJvZ3JhbSB3YW50aW5nIHRv IHVzZSB0aGVtOjwvc3Bhbj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAm bmJzcDsgU1JDUys9IGdldG1udG9wdHMuYzwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFuPiZuYnNwOyAm bmJzcDsgTU9VTlQ9ICR7U1JDVE9QfS9zYmluL21vdW50PC9zcGFuPjwvZGl2PjxkaXY+PHNwYW4+ Jm5ic3A7ICZuYnNwOyBDRkxBR1MrPSAtSSR7TU9VTlR9PC9zcGFuPjwvZGl2PjxkaXY+PHNwYW4+ Jm5ic3A7ICZuYnNwOyAuUEFUSDogJHtNT1VOVH08L3NwYW4+PC9kaXY+PGRpdj48YnI+PC9kaXY+ PGRpdj48c3Bhbj4mbmJzcDsgJm5ic3A7IE9uY2UgdGhlc2UgY2hhbmdlcyBoYXZlIGJlZW4gTUZD J2VkIHRvIDEzIHRoZXkgbWF5IGJlIG1hZGUgaW50bzwvc3Bhbj48L2Rpdj48ZGl2PjxzcGFuPiZu YnNwOyAmbmJzcDsgYSBsaWJyYXJ5Ljwvc3Bhbj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxz cGFuPiZuYnNwOyAmbmJzcDsgUmV2aWV3ZWQgYnk6ICZuYnNwO2tpYiwgZ2JlPC9zcGFuPjwvZGl2 PjxkaXY+PHNwYW4+Jm5ic3A7ICZuYnNwOyBNRkMgYWZ0ZXI6ICZuYnNwOyAmbmJzcDsyIHdlZWtz PC9zcGFuPjwvZGl2PjxkaXY+PHNwYW4+Jm5ic3A7ICZuYnNwOyBTcG9uc29yZWQgYnk6IFRoZSBG cmVlQlNEIEZvdW5kYXRpb248L3NwYW4+PC9kaXY+PGRpdj48c3Bhbj4mbmJzcDsgJm5ic3A7IERp ZmZlcmVudGlhbCBSZXZpc2lvbjogPGEgdGFyZ2V0PSJfYmxhbmsiIHJlbD0ibm9yZWZlcnJlciBu b2ZvbGxvdyBub29wZW5lciIgaHJlZj0iaHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3JnL0QzNzkw NyI+aHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3JnL0QzNzkwNzwvYT48L3NwYW4+PC9kaXY+PHNw YW4+PC9zcGFuPjxicj4= --b1_5tWiq9c027rx8zK86mX9bZaNeOveYeugO37N0M4JeDg-- From nobody Mon Jan 30 15:08:46 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5BR035vyz3bRNK for ; Mon, 30 Jan 2023 15:09:00 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5BR00Xxgz3vx2 for ; Mon, 30 Jan 2023 15:09:00 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x436.google.com with SMTP id 203so6624071pfx.6 for ; Mon, 30 Jan 2023 07:09:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1dv3xdBxxZcb3q9bEXYCqfasTOh+GicsuEjoAM/xoqo=; b=cS/OalHpathujDbRLz9/CWfH1h5SFBJrOSLEye+YudjBbqJPKpVyRjoB3iSS/J0gV7 ql3qncy75lrx7ID+LpF7hyHXHj0qfY1n9O5PhuQCcWFyxes63MexzP75xa4wFhZMv7Tt Qq5g3JWWcBXftIcyVZoexA8Udvkhv9KAh10FM+yNzlzPV9RHvmjEwu7nBTInAqjY4olj j3sK3gNeDfVPE9klcw/NaNfRyvUgoewx6Q2a9np5wjWXhuHEJKV6zMDFDNgSroB0bfKf 92UFkTD6f35hU1lP89gFwr/P6DtaFM5Nw8R1KtaPUl9OdFpLQ2B6QDD3AhDLqMtEgXD2 SZYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=1dv3xdBxxZcb3q9bEXYCqfasTOh+GicsuEjoAM/xoqo=; b=sBWEoEM9V8sQ0jyhwabRJ1jYcM14SHCPR2j8MBJc299998vpFLviUcfA9vhF304XFW 2MqRjI1hKqWhqDKH62LBVkXSwh3g8sk/+14+FvsiMjpETUca/neJbuivk7sx5WA1pgDn BJ2Q7lKEWkb0HKbsk9hFG5OTu1p39MGF3nNM2sPOWsmO9l/G1cMLebA+DI/AiWhk6b9P OvtZt0/t8tX5Su94mClJS/HymxQ7P4jiwB1vjSO5rn3Wv3hHZ/7p2vrqWj/WL66QU2yY rvi7aJV8NRJfo5il8odfwNcB7PrQmiA+1IAtRBZKJ53Fjax4LyEdcT5gR2EYg1b8U4YG 4TsA== X-Gm-Message-State: AFqh2krhe9B38cXuZtmszUokcdt28LhhaLf2Oirn8ZYfKV96e4QKy7DI uk3SDFr4bBVrzDKbjX2+r58pz3VaB0C1XILMHg== X-Google-Smtp-Source: AMrXdXv3YjCpu5G5sAVIccJljfWMcwRPIF7gTcmfB4oNEd+9zXqYzeGFNg+cys5S1lDgC8aEz9pcIKgqph6dGMryH6A= X-Received: by 2002:aa7:820f:0:b0:58d:a713:d1dd with SMTP id k15-20020aa7820f000000b0058da713d1ddmr6386993pfi.59.1675091338811; Mon, 30 Jan 2023 07:08:58 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Mon, 30 Jan 2023 07:08:46 -0800 Message-ID: Subject: Re: sbin/mount: failed to mount NFS root To: qroxana Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4P5BR00Xxgz3vx2 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N I think this was fixed by a commit yesterday. rick On Mon, Jan 30, 2023 at 6:51 AM qroxana wrote: > > /etc/rc failed to run "mount -uw /" when booting from NFS root, > this happened after the commit 906c312bbf7493ccbcce883936d67e5c66a9c3c2, > the previous commit works fine. > > + mount -uw / > af 1 sotype 1 not supported > + echo 'Mounting root filesystem rw failed, startup aborted' > Mounting root filesystem rw failed, startup aborted > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > 2023-01-30T10:09:05.116920+00:00 - init 1 - - /bin/sh on /etc/rc terminated abnormally, going to single user mode > Enter full pathname of shell or RETURN for /bin/sh: > > > commit 906c312bbf7493ccbcce883936d67e5c66a9c3c2 > Author: Kirk McKusick > Date: Sun Jan 15 10:20:48 2023 -0800 > > Document the mntopts(3) functions. > > The mntopts(3) functions support operations associated with a mount > point. The main purpose of this commit is to document the mntopts(3) > functions that now appear in 18 utilities in the base system. See > mntopts(3) for the documentation details. > > The getmntopts() function appeared in 4.4BSD. The build_iovec(), > build_iovec_argf(), free_iovec(), checkpath(), and rmslashes() > functions were added with nmount(8) in FreeBSD 5.0. The getmntpoint() > and chkdoreload() functions are being added in this commit. > > These functions should be in a library but for historic reasons are > in a file in the sources for the mount(8) program. Thus, to access > them the following lines need to be added to the Makefile of the > program wanting to use them: > > SRCS+= getmntopts.c > MOUNT= ${SRCTOP}/sbin/mount > CFLAGS+= -I${MOUNT} > .PATH: ${MOUNT} > > Once these changes have been MFC'ed to 13 they may be made into > a library. > > Reviewed by: kib, gbe > MFC after: 2 weeks > Sponsored by: The FreeBSD Foundation > Differential Revision: https://reviews.freebsd.org/D37907 > From nobody Mon Jan 30 15:33:08 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5Bz76vH0z3bVF8 for ; Mon, 30 Jan 2023 15:33:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5Bz74d23z429M for ; Mon, 30 Jan 2023 15:33:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id v13so11292194eda.11 for ; Mon, 30 Jan 2023 07:33:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JUZNKvTjSvKDI12MelwQD9cB5Rbqw8EdsRBudWXIneY=; b=QhY79fyY+kObF29K6DkFMzEkSLSC+XajK/GGt7GpX52K560gczBPPPF2pG332aJldh 9E5s0mwbU15VrsBAkP/wVHluBtbvXBkqkrwzCZrxE5PkALbDW3tXCDt7V9jIoZ2Kh5qN SiXOZ9a10gPEidHhTPWDYDegFQiIkptoHa+vOCTSdSa9epPQePg+O6O3WPmBAaE07C8k X/SI2Lnw0D7qUUlMJjm8jn784RmW6vQVIMToQnQK7gYn2+RjbHbd6uO4GC006VUmfvNe WDog3EH35KL6J+PfxoW2BPhfSCw8+bTRIdKypns8WgKYRdoSD6N7dIjV7fSMOhD+NGbN DqUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JUZNKvTjSvKDI12MelwQD9cB5Rbqw8EdsRBudWXIneY=; b=DWa0XRxZLGv59ZHvJ+YruJMivkHO0Ku3MFAMivIskwvvlVJ1tihMEXEdJlUrtrFpCK dAEk3Yl3ckxKkFZ58j0HsK1kETp4XWjW4UT9+KhjfLFVjwKCZ/xaJ3dYRR7WjeJxbwvV nqCTYcWTq75T5PkCuyu2wq8ovmslHR7lpg8XpxF/HNx9/2HkGqvqXx0sFqLUM+55SLHc IYXK96qNahKfEvWh4KISpEK4gXjIWgmPvdbT263WpBMD+0+Y9kHXgjQo/NR6a09eVdlq w2pdDHPMmQrtvg4lz6OEb8VxN31Vm7DpYwTLY+nbM+42ITFgk0xt3nZb7oPS5NHAeZZS sCcw== X-Gm-Message-State: AO0yUKWkit0ojZ7/dIrB/Z+7FQtB+1F9dMwBHaamrf2bjSoJEXwgdcOK 5ui9z5Ho8qhkDu4FoebQHhV35vCLK1KfXimFyAsaxQ== X-Google-Smtp-Source: AK7set933+BTslcydArj6BIeGRg+eOzvy8zHs0k0jmB+cth03NrSEvb+dnxK5INeFb+B+BoTCuDHBhvlT2yyUoMGyfM= X-Received: by 2002:a05:6402:1241:b0:4a2:408e:ce5 with SMTP id l1-20020a056402124100b004a2408e0ce5mr1578032edw.24.1675092802180; Mon, 30 Jan 2023 07:33:22 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <86edrcp13z.fsf@peasant.tower.home> In-Reply-To: <86edrcp13z.fsf@peasant.tower.home> From: Warner Losh Date: Mon, 30 Jan 2023 08:33:08 -0700 Message-ID: Subject: Re: Tooling Integration and Developer Experience To: Dmitry Salychev Cc: Kurt Jaeger , Stephane Rochoy , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000070b97c05f37cef62" X-Rspamd-Queue-Id: 4P5Bz74d23z429M X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000070b97c05f37cef62 Content-Type: text/plain; charset="UTF-8" On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote: > > Hi, > > Kurt Jaeger writes: > > > Hi, > > > >> > On 1/30/23 02:54, Julian H. Stacey wrote: > >> > The main idea: to prevent information fragmentation and improve > >> > discoverability, cross-referencing abilities, search, etc. > >> > >> With regards to improving discoverability, Phabricator's Owner > >> tool could be a good tactical move: it allow to bind code area to > >> peoples in order to automatically add them to reviews. > > > > If you know phabricator in more detail, is there any kind of tool > > to understand the activity going on ? > > > > In bugs.freebsd.org, there is the dashboard: > > > > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html > > > > I think we might need something similar to help us understand > > the current state of the phabricator instance and the work > > being done. > > > > Phab allows Dashboards, but no-one had the time to configure some > > queries to provide relevant stats. > > I'd prefer to have an automatic note via email from Phabricator if any > file with my copyright was modified/patched/improved in a newly opened > review. > > I don't think that people tend to ignore changes to those parts of code > they've written (or touched at least). > You can easily create a herald rule to do this. I have one for all of src, but others have subsets like the boot loader. And anybody with an account can do that. Warner --00000000000070b97c05f37cef62 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jan 30, 2023 at 7:07 AM Dmitr= y Salychev <dsl@mcusim.org> wro= te:

Hi,

Kurt Jaeger <pi@free= bsd.org> writes:

> Hi,
>
>> > On 1/30/23 02:54, Julian H. Stacey wrote:
>> >=C2=A0 =C2=A0 The main idea: to prevent information fragmentat= ion and=C2=A0 =C2=A0 improve
>> >=C2=A0 =C2=A0 discoverability, cross-referencing abilities, se= arch, etc.
>>
>> With regards to improving discoverability, Phabricator's Owner=
>> tool could be a good tactical move: it allow to bind code area to<= br> >> peoples in order to automatically add them to reviews.
>
> If you know phabricator in more detail, is there any kind of tool
> to understand the activity going on ?
>
> In bugs.freebsd.org, there is the dashboard:
>
> https://bugs.freebsd.org/bugzilla= /page.cgi?id=3Ddashboard.html
>
> I think we might need something similar to help us understand
> the current state of the phabricator instance and the work
> being done.
>
> Phab allows Dashboards, but no-one had the time to configure some
> queries to provide relevant stats.

I'd prefer to have an automatic note via email from Phabricator if any<= br> file with my copyright was modified/patched/improved in a newly opened
review.

I don't think that people tend to ignore changes to those parts of code=
they've written (or touched at least).

<= div>You can easily create a herald rule to do this. I have one for all of s= rc, but others have subsets
like the boot loader. And anybody wit= h an account can do that.

Warner
=C2= =A0
--00000000000070b97c05f37cef62-- From nobody Mon Jan 30 15:42:12 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5C9b2DGbz3bm4G for ; Mon, 30 Jan 2023 15:42:27 +0000 (UTC) (envelope-from freebsd@igalic.co) Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5C9b1Mnjz43n8 for ; Mon, 30 Jan 2023 15:42:27 +0000 (UTC) (envelope-from freebsd@igalic.co) Authentication-Results: mx1.freebsd.org; none Date: Mon, 30 Jan 2023 15:42:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=igalic.co; s=protonmail; t=1675093343; x=1675352543; bh=j6mWgqSaZsxMYAPnaKf15xjK8bUbyaQrl3DSpiO77cY=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=FECKrQi3Ry5N2Mdwr5Q0zfSA56GWTgPUBMUF8Tjy1Vp11sbrFGfkdWJlCYkj4ls/7 oo3ZMRQ/lVKQYxaCN2RDyoBguL309i+SwKLA/ohiPDylcQjm2FtQM4JTS7Q/856uGA yxA+NLi0yMdg7ApwvFAJ11qhdaguMTtoBpoO8iqrSK/X6Xu/8C2cjBzFHBVNXQDqYd 4z7fbK3f+5fherZPhWs2IbW2MzR629blw0LOfd4Ry3Wrg8uewHPovHGd4KVD2AfTH6 muVJECPGlzHlcANCwGoWLD8eaJbFDQpEelDgGLqZfjmD3hsAqf2zfOg17EubocFzPV BRYgUUt5njIkg== To: imp@bsdimp.com, pi@freebsd.org From: =?utf-8?Q?Mina_Gali=C4=87?= Cc: stephane.rochoy@stormshield.eu, freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Message-ID: In-Reply-To: References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> Feedback-ID: 66573723:user:proton List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_Nc2Gv1GsqIgl0T8a3JMxA2ckAxoLPGeNk9triyfm98" X-Rspamd-Queue-Id: 4P5C9b1Mnjz43n8 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --b1_Nc2Gv1GsqIgl0T8a3JMxA2ckAxoLPGeNk9triyfm98 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 SGkgZm9sa3MsCgpJJ2QgbGlrZSB0byBmaXJzdCBvZiBhbGwgdGhhbmsgV2FybmVyIGZvciBhbGwg aGlzIGhhcmQgd29yay4gV29ya2luZyBvbiBpbmZyYXN0cnVjdHVyZSBjYW4gc2VlbSBsaWtlIHBy ZXR0eSB0aGFua2xlc3Mgd29yay4KCkFzIGFuIG91dHNpZGVyIHRvIEZyZWVCU0QsIGJ1dCBub3Qg YW4gb3V0c2lkZXIgdG8gdGhlIHdvcmtpbmdzIG9mIEZMT1NTIG9yZ2FuaXNhdGlvbnMsIEkganVz dCB3YW50IHRvIHJlbWluZCBldmVyeW9uZSBvZiBvbmUgY29yZSBpc3N1ZTogSXQncyB1c3VhbGx5 IGluc2lkZXJzLCBub3Qgb3V0c2lkZSBjb250cmlidXRvcnMsIHdobyBkbyB0aGUgdGhlIHRoYW5r bGVzcyBpbmZyYXN0cnVjdHVyZSB3b3JrLiBUaGF0IGNyZWF0ZXMgdHdvIGJvdHRsZW5lY2tzOiBQ ZW9wbGUgd2hvIGNhbiB3b3JrIG9uIGluZnJhc3RydWN0dXJlLCBhbmQgcGVvcGxlIHdobyBjYW4g cmV2aWV3IGluY29taW5nIHBhdGNoZXMgYW5kIG5vbWluYXRlIG5ldyBjb250cmlidXRvcnMgdG8g YmVjb21lIGNvbW1pdHRlcnMuCgpIYXZpbmcgYSBzcHJlYWQgb3V0IGluZnJhc3RydWN0dXJlIHRo YXQgbmVlZHMgdG8gYmUgc3VwcG9ydGVkIGFuZCB1cGdyYWRlZCBtZWFucyBjb21taXR0ZXIgdGlt ZSBpcyBoZWxkIHVwIGluIHNvZnR3YXJlIHVwZ3JhZGUgLyBtaWdyYXRpb24gdGFza3MsIGJ1dCBp dCBhbHNvIG1lYW5zIHRoYXQgb3V0c2lkZSBjb250cmlidXRvcnMgc3BlbmQgYW4gdW5uZWNlc3Nh cmlseSBsb25nIHRpbWUgZmluZGluZyB0aGUgcmlnaHQgYXZlbnVlIHRvIGNvbnRyaWJ1dGUgdG8g dGhlIHJpZ2h0IHBhcnQgb2YgdGhlIGNvZGUuCgpNaW5hIEdhbGnEhwpUcnkgUGtnQmFzZTogaHR0 cHM6Ly9hbHBoYS5wa2diYXNlLmxpdmUvCgotLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0t LS0tCk9uIDMwIEphbiAyMDIzLCAxMzo1MywgV2FybmVyIExvc2ggd3JvdGU6Cgo+IE9uIE1vbiwg SmFuIDMwLCAyMDIzIGF0IDM6NDAgQU0gS3VydCBKYWVnZXIgPHBpQGZyZWVic2Qub3JnPiB3cm90 ZToKPgo+PiBIaSwKPj4KPj4+ID4gT24gMS8zMC8yMyAwMjo1NCwgSnVsaWFuIEguIFN0YWNleSB3 cm90ZToKPj4+ID4gVGhlIG1haW4gaWRlYTogdG8gcHJldmVudCBpbmZvcm1hdGlvbiBmcmFnbWVu dGF0aW9uIGFuZCBpbXByb3ZlCj4+PiA+IGRpc2NvdmVyYWJpbGl0eSwgY3Jvc3MtcmVmZXJlbmNp bmcgYWJpbGl0aWVzLCBzZWFyY2gsIGV0Yy4KPj4+Cj4+PiBXaXRoIHJlZ2FyZHMgdG8gaW1wcm92 aW5nIGRpc2NvdmVyYWJpbGl0eSwgUGhhYnJpY2F0b3IncyBPd25lcgo+Pj4gdG9vbCBjb3VsZCBi ZSBhIGdvb2QgdGFjdGljYWwgbW92ZTogaXQgYWxsb3cgdG8gYmluZCBjb2RlIGFyZWEgdG8KPj4+ IHBlb3BsZXMgaW4gb3JkZXIgdG8gYXV0b21hdGljYWxseSBhZGQgdGhlbSB0byByZXZpZXdzLgo+ Pgo+PiBJZiB5b3Uga25vdyBwaGFicmljYXRvciBpbiBtb3JlIGRldGFpbCwgaXMgdGhlcmUgYW55 IGtpbmQgb2YgdG9vbAo+PiB0byB1bmRlcnN0YW5kIHRoZSBhY3Rpdml0eSBnb2luZyBvbiA/Cj4+ Cj4+IEluIGJ1Z3MuZnJlZWJzZC5vcmcsIHRoZXJlIGlzIHRoZSBkYXNoYm9hcmQ6Cj4+Cj4+IGh0 dHBzOi8vYnVncy5mcmVlYnNkLm9yZy9idWd6aWxsYS9wYWdlLmNnaT9pZD1kYXNoYm9hcmQuaHRt bAo+Pgo+PiBJIHRoaW5rIHdlIG1pZ2h0IG5lZWQgc29tZXRoaW5nIHNpbWlsYXIgdG8gaGVscCB1 cyB1bmRlcnN0YW5kCj4+IHRoZSBjdXJyZW50IHN0YXRlIG9mIHRoZSBwaGFicmljYXRvciBpbnN0 YW5jZSBhbmQgdGhlIHdvcmsKPj4gYmVpbmcgZG9uZS4KPj4KPj4gUGhhYiBhbGxvd3MgRGFzaGJv YXJkcywgYnV0IG5vLW9uZSBoYWQgdGhlIHRpbWUgdG8gY29uZmlndXJlIHNvbWUKPj4gcXVlcmll cyB0byBwcm92aWRlIHJlbGV2YW50IHN0YXRzLgo+Cj4gUGhhYiBpcyBhIHRlcnJpYmxlIHRvb2wg Zm9yIGRpc2NvdmVyeS4gRm9yIGV4YW1wbGUsIGhvdyBkbyBJIHF1ZXJ5IGFsbCB0aGUgcmV2aWV3 cyBJJ3ZlIHRpY2tlZCAnT0snIHRoYXQgYXJlIHN0aWxsIG9wZW4sIGJ5IG5vbi1jb21taXR0ZXJz PyBIb3cgZG8gSSBmbGFnIHRoaW5ncyBhcyAnaW50ZXJlc3RpbmcgdG8gbWUnPyBJIGNhbiB0aWNr IGEgZmxhZywgYnV0IEkgY2FuJ3QgcXVlcnkgZmxhZ3MuIEFsc28sIEkgY2FuJ3QgZ2V0IGFuIGVt YWlsIGFkZHJlc3MgZm9yIHN1Ym1pdHRlciBlaXRoZXIuIFRoYXQgbWFrZXMgaXQgbW9yZSBvZiBh IHBhaW4gdG8gbGFuZCB0aGUgY29tbWl0Lgo+Cj4gQnV6aWxsYSBpcyBpbiBtYW55IHdheXMgd29y c2UgKGl0J3MgYWJzb2x1dGVseSB0ZXJyaWJsZSBmb3IgZG9pbmcgY29kZSByZXZpZXdzLCB0aG91 Z2ggaXQncyBxdWVyeWFiaWxpdHkgaXMgbXVjaCBiZXR0ZXIpLiBJbiBzb21lIHdheXMgaXQncyBi ZXR0ZXIgZm9yIGNoYW5nZXMgdGhhdCBhcmUgcmVhZHkgdG8gZ28sIHNpbmNlIHlvdSBjYW4gdXBs b2FkIGdpdCBmb3JtYXQtcGF0Y2ggb3V0cHV0LCBidXQgaXQgdG9vIGhhcyBkaXNjb3ZlcmFiaWxp dHkgaXNzdWVzLgo+Cj4gR2l0aHViIGFuZCBnaXRsYWIgcHVsbCByZXF1ZXN0cyBhcmUgYmV0dGVy IGluIHNvbWUgd2F5cywgYnV0IHdvcnNlIGluIG90aGVycy4gVGhlIHJldmlldyB0b29sIGlzbid0 IGFzIGdvb2QgYXMgcGhhYiwgYW5kIHdoZW4geW91IGhhdmUgYSBsb3Qgb2YgdGhlbSwgdGhleSBh cmUgaGFyZCB0byBvcmdhbml6ZS4gQnV0IGl0J3MgbXkgcHJlZmVycmVkIHdheSB0byBsYW5kIHBh dGNoZXMgYmVjYXVzZSBpdCdzIGFic29sdXRlbHkgdGhlIGVhc2llc3QgZnJvbSBhIGRldmVsb3Bl ciBwb2ludCBvZiB2aWV3IHRvIGRvIHNvOiBJdCdzIG9uZSBjb21tYW5kICh0aG91Z2ggdGhlIGNv bW1hbmRzIGRpZmZlciBiZXR3ZWVuIHRoZSB0d28pLgo+Cj4gVGhlIGZvdW5kYXRpb24gaXMgZnVu ZGluZyB0aGUgQ0kgYXNwZWN0IG9mIHRoaXM6IEdldHRpbmcgam9icyB0aGF0IGRldmVsb3BlcnMg YW5kIGF1dG9tYXRpb24gY2FuIHJ1biB0byBnYXRlIGluIHBsYWNlLiBVbnRpbCB3ZSBoYXZlIHRo YXQgaW4gcGxhY2UgYW5kIGludGVncmF0ZWQgdG9nZXRoZXIsIHRoaW5ncyB3aWxsIGJlIGhhcmRl ci4KPgo+IEJ1dCB0aGVyZSdzIHR3byBvdGhlciBpc3N1ZXM6IFRoZSBGcmVlQlNEIHByb2plY3Qg aGFzIGhhZCBhIGxvbmcgaGlzdG9yeSBvZiBiZWluZyBiZWhpbmQsIHJlZ2FyZGxlc3Mgb2YgdGhl IHRvb2xzIHdlIHVzZS4gVGhlcmUncyBhIGxhYm9yIHNob3J0YWdlIHRvIHByb2Nlc3MgdGhlc2Ug dGhpbmdzIGFzIHdlbGwuIFNlY29uZCwgbG90cyBvZiBwZW9wbGUgd2FudCB0byB0YWxrLCBidXQg ZmV3IHdhbnQgdG8gZG8gdGhlIHdvcmsuIEkgdHJpZWQgbGVhZGluZyBhbiBlZmZvcnQgaW4gdGhp cyBhcmVhLGJ1dCBncmV3IHdlYXJ5IG9mIHRoZSBwYXNzaXZlLWFnZ3Jlc3NpdmUgY29tbWVudHMg YWJvdXQgaG93IEkgYmFzaWNhbGx5IHN1Y2tlZCBmb3Igbm90IGhhdmluZyBpdCBkb25lIGFscmVh ZHkgKGZyb20gdGhlIHNhbWUgcGVvcGxlIHRoYXQgZGlkIDAgYWN0dWFsIHdvcmsgb24gaXQpLgo+ Cj4gV2FybmVy --b1_Nc2Gv1GsqIgl0T8a3JMxA2ckAxoLPGeNk9triyfm98 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 SGkgZm9sa3MsPGJyPjxicj5JJ2QgbGlrZSB0byBmaXJzdCBvZiBhbGwgdGhhbmsgV2FybmVyIGZv ciBhbGwgaGlzIGhhcmQgd29yay4gV29ya2luZyBvbiBpbmZyYXN0cnVjdHVyZSBjYW4gc2VlbSBs aWtlIHByZXR0eSB0aGFua2xlc3Mgd29yay48YnI+PGJyPkFzIGFuIG91dHNpZGVyIHRvIEZyZWVC U0QsIGJ1dCBub3QgYW4gb3V0c2lkZXIgdG8gdGhlIHdvcmtpbmdzIG9mIEZMT1NTIG9yZ2FuaXNh dGlvbnMsIEkganVzdCB3YW50IHRvIHJlbWluZCBldmVyeW9uZSBvZiBvbmUgY29yZSBpc3N1ZTog SXQncyB1c3VhbGx5IGluc2lkZXJzLCBub3Qgb3V0c2lkZSBjb250cmlidXRvcnMsIHdobyBkbyB0 aGUgdGhlIHRoYW5rbGVzcyBpbmZyYXN0cnVjdHVyZSB3b3JrLiBUaGF0IGNyZWF0ZXMgdHdvIGJv dHRsZW5lY2tzOiBQZW9wbGUgd2hvIGNhbiB3b3JrIG9uIGluZnJhc3RydWN0dXJlLCBhbmQgcGVv cGxlIHdobyBjYW4gcmV2aWV3IGluY29taW5nIHBhdGNoZXMgYW5kIG5vbWluYXRlIG5ldyBjb250 cmlidXRvcnMgdG8gYmVjb21lIGNvbW1pdHRlcnMuPGJyPjxicj5IYXZpbmcgYSBzcHJlYWQgb3V0 IGluZnJhc3RydWN0dXJlIHRoYXQgbmVlZHMgdG8gYmUgc3VwcG9ydGVkIGFuZCB1cGdyYWRlZCBt ZWFucyBjb21taXR0ZXIgdGltZSBpcyBoZWxkIHVwIGluIHNvZnR3YXJlIHVwZ3JhZGUgLyBtaWdy YXRpb24gdGFza3MsIGJ1dCBpdCBhbHNvIG1lYW5zIHRoYXQgb3V0c2lkZSBjb250cmlidXRvcnMg c3BlbmQgYW4gdW5uZWNlc3NhcmlseSBsb25nIHRpbWUgZmluZGluZyB0aGUgcmlnaHQgYXZlbnVl IHRvIGNvbnRyaWJ1dGUgdG8gdGhlIHJpZ2h0IHBhcnQgb2YgdGhlIGNvZGUuPGJyPjxicj5NaW5h IEdhbGnEhzxicj5UcnkgUGtnQmFzZTogPGEgaHJlZj0iaHR0cHM6Ly9hbHBoYS5wa2diYXNlLmxp dmUvIj5odHRwczovL2FscGhhLnBrZ2Jhc2UubGl2ZS88L2E+PGJyPjxicj48YnI+PGJyPjxicj48 YnI+LS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLTxicj5PbiAzMCBKYW4gMjAyMywg MTM6NTMsIFdhcm5lciBMb3NoIDwgaW1wQGJzZGltcC5jb20+IHdyb3RlOjxibG9ja3F1b3RlIGNs YXNzPSJwcm90b25tYWlsX3F1b3RlIj48YnI+PGRpdiBkaXI9Imx0ciI+PGRpdiBkaXI9Imx0ciI+ PGJyPjwvZGl2Pjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+PGRpdiBkaXI9Imx0ciIgY2xh c3M9ImdtYWlsX2F0dHIiPk9uIE1vbiwgSmFuIDMwLCAyMDIzIGF0IDM6NDAgQU0gS3VydCBKYWVn ZXIgJmx0OzxhIGhyZWY9Im1haWx0bzpwaUBmcmVlYnNkLm9yZyI+cGlAZnJlZWJzZC5vcmc8L2E+ Jmd0OyB3cm90ZTo8YnI+PC9kaXY+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHls ZT0ibWFyZ2luOjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0 LDIwNCwyMDQpO3BhZGRpbmctbGVmdDoxZXgiPkhpLDxicj4NCjxicj4NCiZndDsgJmd0OyBPbiAx LzMwLzIzIDAyOjU0LCBKdWxpYW4gSC4gU3RhY2V5IHdyb3RlOjxicj4NCiZndDsgJmd0O8KgIMKg IFRoZSBtYWluIGlkZWE6IHRvIHByZXZlbnQgaW5mb3JtYXRpb24gZnJhZ21lbnRhdGlvbiBhbmTC oCDCoCBpbXByb3ZlPGJyPg0KJmd0OyAmZ3Q7wqAgwqAgZGlzY292ZXJhYmlsaXR5LCBjcm9zcy1y ZWZlcmVuY2luZyBhYmlsaXRpZXMsIHNlYXJjaCwgZXRjLjxicj4NCiZndDsgPGJyPg0KJmd0OyBX aXRoIHJlZ2FyZHMgdG8gaW1wcm92aW5nIGRpc2NvdmVyYWJpbGl0eSwgUGhhYnJpY2F0b3ImIzM5 O3MgT3duZXI8YnI+DQomZ3Q7IHRvb2wgY291bGQgYmUgYSBnb29kIHRhY3RpY2FsIG1vdmU6IGl0 IGFsbG93IHRvIGJpbmQgY29kZSBhcmVhIHRvPGJyPg0KJmd0OyBwZW9wbGVzIGluIG9yZGVyIHRv IGF1dG9tYXRpY2FsbHkgYWRkIHRoZW0gdG8gcmV2aWV3cy48YnI+DQo8YnI+DQpJZiB5b3Uga25v dyBwaGFicmljYXRvciBpbiBtb3JlIGRldGFpbCwgaXMgdGhlcmUgYW55IGtpbmQgb2YgdG9vbDxi cj4NCnRvIHVuZGVyc3RhbmQgdGhlIGFjdGl2aXR5IGdvaW5nIG9uID88YnI+DQo8YnI+DQpJbiA8 YSBocmVmPSJodHRwOi8vYnVncy5mcmVlYnNkLm9yZyIgcmVsPSJub3JlZmVycmVyIiB0YXJnZXQ9 Il9ibGFuayI+YnVncy5mcmVlYnNkLm9yZzwvYT4sIHRoZXJlIGlzIHRoZSBkYXNoYm9hcmQ6PGJy Pg0KPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9idWdzLmZyZWVic2Qub3JnL2J1Z3ppbGxhL3BhZ2Uu Y2dpP2lkPWRhc2hib2FyZC5odG1sIiByZWw9Im5vcmVmZXJyZXIiIHRhcmdldD0iX2JsYW5rIj5o dHRwczovL2J1Z3MuZnJlZWJzZC5vcmcvYnVnemlsbGEvcGFnZS5jZ2k/aWQ9ZGFzaGJvYXJkLmh0 bWw8L2E+PGJyPg0KPGJyPg0KSSB0aGluayB3ZSBtaWdodCBuZWVkIHNvbWV0aGluZyBzaW1pbGFy IHRvIGhlbHAgdXMgdW5kZXJzdGFuZDxicj4NCnRoZSBjdXJyZW50IHN0YXRlIG9mIHRoZSBwaGFi cmljYXRvciBpbnN0YW5jZSBhbmQgdGhlIHdvcms8YnI+DQpiZWluZyBkb25lLjxicj4NCjxicj4N ClBoYWIgYWxsb3dzIERhc2hib2FyZHMsIGJ1dCBuby1vbmUgaGFkIHRoZSB0aW1lIHRvIGNvbmZp Z3VyZSBzb21lPGJyPg0KcXVlcmllcyB0byBwcm92aWRlIHJlbGV2YW50IHN0YXRzLjxicj48L2Js b2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5QaGFiIGlzIGEgdGVycmlibGUgdG9vbCBmb3Ig ZGlzY292ZXJ5LiBGb3IgZXhhbXBsZSwgaG93IGRvIEkgcXVlcnkgYWxsIHRoZSByZXZpZXdzIEkm IzM5O3ZlIHRpY2tlZCAmIzM5O09LJiMzOTsgdGhhdCBhcmUgc3RpbGwgb3BlbiwgYnkgbm9uLWNv bW1pdHRlcnM/IEhvdyBkbyBJIGZsYWcgdGhpbmdzIGFzICYjMzk7aW50ZXJlc3RpbmcgdG8gbWUm IzM5Oz8gSSBjYW4gdGljayBhIGZsYWcsIGJ1dCBJIGNhbiYjMzk7dCBxdWVyeSBmbGFncy4gQWxz bywgSSBjYW4mIzM5O3QgZ2V0IGFuIGVtYWlsIGFkZHJlc3MgZm9yIHN1Ym1pdHRlciBlaXRoZXIu IFRoYXQgbWFrZXMgaXQgbW9yZSBvZiBhIHBhaW4gdG8gbGFuZCB0aGUgY29tbWl0LjwvZGl2Pjxk aXY+PGJyPjwvZGl2PjxkaXY+QnV6aWxsYSBpcyBpbiBtYW55IHdheXMgd29yc2UgKGl0JiMzOTtz IGFic29sdXRlbHkgdGVycmlibGUgZm9yIGRvaW5nIGNvZGUgcmV2aWV3cywgdGhvdWdoIGl0JiMz OTtzIHF1ZXJ5YWJpbGl0eSBpcyBtdWNoIGJldHRlcikuIEluIHNvbWUgd2F5cyBpdCYjMzk7cyBi ZXR0ZXIgZm9yIGNoYW5nZXMgdGhhdCBhcmUgcmVhZHkgdG8gZ28sIHNpbmNlIHlvdSBjYW4gdXBs b2FkIGdpdCBmb3JtYXQtcGF0Y2ggb3V0cHV0LCBidXQgaXQgdG9vIGhhcyBkaXNjb3ZlcmFiaWxp dHkgaXNzdWVzLiA8YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5HaXRodWIgYW5kIGdpdGxh YiBwdWxsIHJlcXVlc3RzIGFyZSBiZXR0ZXIgaW4gc29tZSB3YXlzLCBidXQgd29yc2UgaW4gb3Ro ZXJzLiBUaGUgcmV2aWV3IHRvb2wgaXNuJiMzOTt0IGFzIGdvb2QgYXMgcGhhYiwgYW5kIHdoZW4g eW91IGhhdmUgYSBsb3Qgb2YgdGhlbSwgdGhleSBhcmUgaGFyZCB0byBvcmdhbml6ZS4gQnV0IGl0 JiMzOTtzIG15IHByZWZlcnJlZCB3YXkgdG8gbGFuZCBwYXRjaGVzIGJlY2F1c2UgaXQmIzM5O3Mg YWJzb2x1dGVseSB0aGUgZWFzaWVzdCBmcm9tIGEgZGV2ZWxvcGVyIHBvaW50IG9mIHZpZXcgdG8g ZG8gc286IEl0JiMzOTtzIG9uZSBjb21tYW5kICh0aG91Z2ggdGhlIGNvbW1hbmRzIGRpZmZlciBi ZXR3ZWVuIHRoZSB0d28pLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+VGhlIGZvdW5kYXRpb24g aXMgZnVuZGluZyB0aGUgQ0kgYXNwZWN0IG9mIHRoaXM6IEdldHRpbmcgam9icyB0aGF0IGRldmVs b3BlcnMgYW5kIGF1dG9tYXRpb24gY2FuIHJ1biB0byBnYXRlIGluIHBsYWNlLiBVbnRpbCB3ZSBo YXZlIHRoYXQgaW4gcGxhY2UgYW5kIGludGVncmF0ZWQgdG9nZXRoZXIsIHRoaW5ncyB3aWxsIGJl IGhhcmRlci48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkJ1dCB0aGVyZSYjMzk7cyB0d28gb3Ro ZXIgaXNzdWVzOiBUaGUgRnJlZUJTRCBwcm9qZWN0IGhhcyBoYWQgYSBsb25nIGhpc3Rvcnkgb2Yg YmVpbmcgYmVoaW5kLCByZWdhcmRsZXNzIG9mIHRoZSB0b29scyB3ZSB1c2UuIFRoZXJlJiMzOTtz IGEgbGFib3Igc2hvcnRhZ2UgdG8gcHJvY2VzcyB0aGVzZSB0aGluZ3MgYXMgd2VsbC4gU2Vjb25k LCBsb3RzIG9mIHBlb3BsZSB3YW50IHRvIHRhbGssIGJ1dCBmZXcgd2FudCB0byBkbyB0aGUgd29y ay4gSSB0cmllZCBsZWFkaW5nIGFuIGVmZm9ydCBpbiB0aGlzIGFyZWEsYnV0IGdyZXcgd2Vhcnkg b2YgdGhlIHBhc3NpdmUtYWdncmVzc2l2ZSBjb21tZW50cyBhYm91dCBob3cgSSBiYXNpY2FsbHkg c3Vja2VkIGZvciBub3QgaGF2aW5nIGl0IGRvbmUgYWxyZWFkeSAoZnJvbSB0aGUgc2FtZSBwZW9w bGUgdGhhdCBkaWQgMCBhY3R1YWwgd29yayBvbiBpdCkuPGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2 PjxkaXY+V2FybmVyPGJyPjwvZGl2PjwvZGl2PjwvZGl2Pg0KPC9kaXY+ --b1_Nc2Gv1GsqIgl0T8a3JMxA2ckAxoLPGeNk9triyfm98-- From nobody Mon Jan 30 16:44:32 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5Dfq3PZNz3bw8p for ; Mon, 30 Jan 2023 16:49:23 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from mcusim.org (mcusim.org [176.58.93.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5Dfq1S4Pz4Dxl; Mon, 30 Jan 2023 16:49:23 +0000 (UTC) (envelope-from dsl@mcusim.org) Authentication-Results: mx1.freebsd.org; none Received: from localhost (unknown [193.164.254.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mcusim.org (Postfix) with ESMTPSA id CC4A38AA65; Mon, 30 Jan 2023 17:49:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mcusim.org; s=default; t=1675097361; bh=j5chiScGM4qfa/4WD3O6uzVtNWibvBwKqiIoUiLfTsk=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=cJLReaQof10ToZ1dYN4uvs3fm4HofN3NS7pF5UN7v1DjbyDat3jBNGehNnrTajUkB V8LAb4sZOG7vbr9Ap99ZJY68632iSKm8c8IY/JGcUUVb0gNpDqt9zFSPWcvJ2Q4ysh /iZFEgdph5L3OOpdzqwrMy6gt1KsphArCIs65Xxo= References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <86edrcp13z.fsf@peasant.tower.home> User-agent: mu4e 1.6.10; emacs 28.2 From: Dmitry Salychev To: Warner Losh Cc: Kurt Jaeger , Stephane Rochoy , freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Date: Mon, 30 Jan 2023 17:44:32 +0100 In-reply-to: Message-ID: <86zga0nf1q.fsf@peasant.tower.home> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4P5Dfq1S4Pz4Dxl X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:176.58.93.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Warner Losh writes: > On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote: > > Hi, > > Kurt Jaeger writes: > > > Hi, > > > >> > On 1/30/23 02:54, Julian H. Stacey wrote: > >> > The main idea: to prevent information fragmentation and improve > >> > discoverability, cross-referencing abilities, search, etc. > >> > >> With regards to improving discoverability, Phabricator's Owner > >> tool could be a good tactical move: it allow to bind code area to > >> peoples in order to automatically add them to reviews. > > > > If you know phabricator in more detail, is there any kind of tool > > to understand the activity going on ? > > > > In bugs.freebsd.org, there is the dashboard: > > > > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html > > > > I think we might need something similar to help us understand > > the current state of the phabricator instance and the work > > being done. > > > > Phab allows Dashboards, but no-one had the time to configure some > > queries to provide relevant stats. > > I'd prefer to have an automatic note via email from Phabricator if any > file with my copyright was modified/patched/improved in a newly opened > review. > > I don't think that people tend to ignore changes to those parts of code > they've written (or touched at least). > > You can easily create a herald rule to do this. I have one for all of src, but others have subsets > like the boot loader. And anybody with an account can do that. > > Warner Looks really useful, thanks for a hint. Is there any way to test regexp matching for files content? Btw, there could be a carefully selected set of pre-defined Herald rules added to any new committer's account. -- Dmitry Salychev From nobody Mon Jan 30 16:58:55 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5Dt34NNLz3bxVZ for ; Mon, 30 Jan 2023 16:59:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5Dt340hCz4GrM for ; Mon, 30 Jan 2023 16:59:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62d.google.com with SMTP id hx15so14109149ejc.11 for ; Mon, 30 Jan 2023 08:59:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YRd5Xr0RvTecNibA13NDeOUAzRWE5rNWiQkd/dkvwCU=; b=04LRJOxjAQLVwugcgHohFKQmzq9Qi+B19Nc+h9mEp+BPLh8sErEy4aR/EB54RnBhaS cwya2xXoIUgt0yrTFty8n1hIOiXFO7UDZchNkX+44UwTCbqAR50Ls/YtbQ8vQ4lewJNz LVrMj0leywwyXVqUqEdOt/P1bCmgkjwjrLsPoiv1inD7srA1ielVhhuJM6P4mnwCRqyZ 85es7OWYnXSj3sCvf8XFJ6fJov0NRuDGPegyFqUBplKf6QephW0oOmteFKWtg87LkUhf yjcUm2d9j4z6OrZrn7lWZq3Qfra1rE8pA1NolZtpkVsk2E+KUWuVXJuzsMBh4L+p4/uH Ch0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YRd5Xr0RvTecNibA13NDeOUAzRWE5rNWiQkd/dkvwCU=; b=nmv15PzARhvVr40MUMbu85iYAzK7cwzn//TQn0yHtnQ3sExRLmH2siUkRh6lHgJU5F dhMemAcWBdk8dxbEMR6NRP/q3IzLCmFvKIo5BviJ2a/5uA3QtRSoP2cNiWY4P/NLYFZ7 2hGdXsHmu7LKxt7LJbezIVQ8C1MwWylzEx8gyDe9CEXckdMywQMbOkhpENGSjpQIe/V8 nGGnYz4G7Guj7e0IcklRG0s+PGt26tDgDbXteWBixRNKitWix27LF/qaHFdn9mGqxgx+ RhrM2MGki3iKfdBCHmz72bziH6wPmTcMkswguA85+1seKrX5eu0rMzE8nR2Q37BaEDu5 +bKQ== X-Gm-Message-State: AFqh2krAJtkM03vXwzSR4A22z2n5zGk4Mh5cW6DItbUk/eMbaUGOLXOE KPHY8MGrWTBvbucfmzzq+UTk+DzLNU40tSJSto7FIA== X-Google-Smtp-Source: AMrXdXuQLtWWcfaorr3O9FUMKiJujGoGwZu7f4dCGTC/9OF0Sjy2m2YHlBgcenXXIQGy2vH5b8Mu5sWx7wp8f69QS0M= X-Received: by 2002:a17:906:2752:b0:86f:f0ce:a227 with SMTP id a18-20020a170906275200b0086ff0cea227mr8263653ejd.160.1675097946411; Mon, 30 Jan 2023 08:59:06 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <86edrcp13z.fsf@peasant.tower.home> <86zga0nf1q.fsf@peasant.tower.home> In-Reply-To: <86zga0nf1q.fsf@peasant.tower.home> From: Warner Losh Date: Mon, 30 Jan 2023 09:58:55 -0700 Message-ID: Subject: Re: Tooling Integration and Developer Experience To: Dmitry Salychev Cc: Kurt Jaeger , Stephane Rochoy , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000000f630c05f37e22b5" X-Rspamd-Queue-Id: 4P5Dt340hCz4GrM X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000000f630c05f37e22b5 Content-Type: text/plain; charset="UTF-8" I think just "sys/dev/dpaa2" is all you need when adding the Herald rule. :) More generally, no, there's no way that I've found to only match files that match certain regexp. Warner On Mon, Jan 30, 2023 at 9:49 AM Dmitry Salychev wrote: > > Warner Losh writes: > > > On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote: > > > > Hi, > > > > Kurt Jaeger writes: > > > > > Hi, > > > > > >> > On 1/30/23 02:54, Julian H. Stacey wrote: > > >> > The main idea: to prevent information fragmentation and > improve > > >> > discoverability, cross-referencing abilities, search, etc. > > >> > > >> With regards to improving discoverability, Phabricator's Owner > > >> tool could be a good tactical move: it allow to bind code area to > > >> peoples in order to automatically add them to reviews. > > > > > > If you know phabricator in more detail, is there any kind of tool > > > to understand the activity going on ? > > > > > > In bugs.freebsd.org, there is the dashboard: > > > > > > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html > > > > > > I think we might need something similar to help us understand > > > the current state of the phabricator instance and the work > > > being done. > > > > > > Phab allows Dashboards, but no-one had the time to configure some > > > queries to provide relevant stats. > > > > I'd prefer to have an automatic note via email from Phabricator if any > > file with my copyright was modified/patched/improved in a newly opened > > review. > > > > I don't think that people tend to ignore changes to those parts of code > > they've written (or touched at least). > > > > You can easily create a herald rule to do this. I have one for all of > src, but others have subsets > > like the boot loader. And anybody with an account can do that. > > > > Warner > > Looks really useful, thanks for a hint. Is there any way to test regexp > matching for files content? Btw, there could be a carefully selected set > of pre-defined Herald rules added to any new committer's account. > > -- > Dmitry Salychev > --0000000000000f630c05f37e22b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think just "sys/dev/dpaa2" is all you need whe= n adding the Herald rule. :)

More generally, no, there&#= 39;s no way that I've found to only match files that match certain rege= xp.

Warner

On Mon, Jan 30, 2023 at 9:49 AM Dm= itry Salychev <dsl@mcusim.org> = wrote:

Warner Losh <imp@bsd= imp.com> writes:

> On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev <dsl@mcusim.org> wrote:
>
>=C2=A0 Hi,
>
>=C2=A0 Kurt Jaeger <pi@freebsd.org> writes:
>
>=C2=A0 > Hi,
>=C2=A0 >
>=C2=A0 >> > On 1/30/23 02:54, Julian H. Stacey wrote:
>=C2=A0 >> >=C2=A0 =C2=A0 The main idea: to prevent information= fragmentation and=C2=A0 =C2=A0 improve
>=C2=A0 >> >=C2=A0 =C2=A0 discoverability, cross-referencing ab= ilities, search, etc.
>=C2=A0 >>
>=C2=A0 >> With regards to improving discoverability, Phabricator&= #39;s Owner
>=C2=A0 >> tool could be a good tactical move: it allow to bind co= de area to
>=C2=A0 >> peoples in order to automatically add them to reviews.<= br> >=C2=A0 >
>=C2=A0 > If you know phabricator in more detail, is there any kind o= f tool
>=C2=A0 > to understand the activity going on ?
>=C2=A0 >
>=C2=A0 > In bugs.freebsd.org, there is the dashboard:
>=C2=A0 >
>=C2=A0 > https://bugs.freebsd.o= rg/bugzilla/page.cgi?id=3Ddashboard.html
>=C2=A0 >
>=C2=A0 > I think we might need something similar to help us understa= nd
>=C2=A0 > the current state of the phabricator instance and the work<= br> >=C2=A0 > being done.
>=C2=A0 >
>=C2=A0 > Phab allows Dashboards, but no-one had the time to configur= e some
>=C2=A0 > queries to provide relevant stats.
>
>=C2=A0 I'd prefer to have an automatic note via email from Phabrica= tor if any
>=C2=A0 file with my copyright was modified/patched/improved in a newly = opened
>=C2=A0 review.
>
>=C2=A0 I don't think that people tend to ignore changes to those pa= rts of code
>=C2=A0 they've written (or touched at least).
>
> You can easily create a herald rule to do this. I have one for all of = src, but others have subsets
> like the boot loader. And anybody with an account can do that.
>
> Warner

Looks really useful, thanks for a hint. Is there any way to test regexp
matching for files content? Btw, there could be a carefully selected set of pre-defined Herald rules added to any new committer's account.

--
Dmitry Salychev
--0000000000000f630c05f37e22b5-- From nobody Mon Jan 30 16:59:21 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5Dt739vWz3bxYR for ; Mon, 30 Jan 2023 16:59:11 +0000 (UTC) (envelope-from ihor@antonovs.family) Received: from mail.antonovs.family (mail.antonovs.family [100.25.240.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.antonovs.family", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5Dt64zwnz4H19 for ; Mon, 30 Jan 2023 16:59:10 +0000 (UTC) (envelope-from ihor@antonovs.family) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=antonovs.family header.s=20200215 header.b=tzE5DhjP; spf=pass (mx1.freebsd.org: domain of ihor@antonovs.family designates 100.25.240.195 as permitted sender) smtp.mailfrom=ihor@antonovs.family; dmarc=pass (policy=none) header.from=antonovs.family DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antonovs.family; s=20200215; t=1675097945; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=isDO+tuXJI5pIkpvZlQN97pdyiDmNz+7EmPOfILAJVM=; b=tzE5DhjPfjSok4/anCMSqZXh5v811mptjwdaW4vAGcYSXfMK1ikwzCFD4nIgfru/KfgBCl 4qULateNgfXr9j8QGR5UYvuChjMj/XmFQMEhuhJFJt0SiPO0OaZeE8QafPG5yYV1gcCBW2 bukuVkTM+RshdEkDxyCusLYyAoApZD8= Received: by mail.antonovs.family (OpenSMTPD) with ESMTPSA id 5630c787 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Mon, 30 Jan 2023 16:59:05 +0000 (UTC) Message-ID: <5207abe0-9c2b-1424-ac58-d52e97ba7413@antonovs.family> Date: Mon, 30 Jan 2023 16:59:21 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Tooling Integration and Developer Experience Content-Language: en-US To: freebsd-current@freebsd.org References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> From: User Ngor In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.989]; DMARC_POLICY_ALLOW(-0.50)[antonovs.family,none]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[antonovs.family:s=20200215]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[antonovs.family:+]; ASN(0.00)[asn:14618, ipnet:100.24.0.0/13, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4P5Dt64zwnz4H19 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 1/30/23 10:08, Kurt Jaeger wrote: > Hi! > > ihor@antonovs.family wrote: > >> This can be as easy as moving everything into Phabricator. > There's the issue that Phabricator itself is no longer supported > upstream: > > https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/ > https://github.com/phacility/phabricator > > I have notes from Oct. 2021 which point to a fork: > > https://we.phorge.it/ > > That fork seems to be somewhat alive. Moving our phab instance > to phorge is probably no trivial task. > Should be no harder than regular update. They even have a HOWTO https://we.phorge.it/w/installation_and_setup/update_from_phabricator/ From operational point of view it requires the least amount of effort, comparing to full-scale migration to any other platform. The Phorge seems to be active, so we can ask them to improve query functionality..(I am an optimist) Overall short-term plan could look like this: 1. Upgrade to Phorge 2. Setup Maniphest for bugs and tasks 3. Migrate bugs into Maniphest 4. Enable Harbormaster (Build/CI) - this requires coordination with whoever is working on pre-commit CI. This should improve things quite a bit already. Long term we can add Ponder and Phriction (Wiki and Q&A) and move current wiki into it too. Infra operations are hard, and I have experience with it. I'd be happy to help. -- Ihor Antonov From nobody Mon Jan 30 17:06:21 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5F2h66Qrz3bygd for ; Mon, 30 Jan 2023 17:06:36 +0000 (UTC) (envelope-from yklaxds@gmail.com) Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5F2h475Kz4L5K; Mon, 30 Jan 2023 17:06:36 +0000 (UTC) (envelope-from yklaxds@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-xe2c.google.com with SMTP id j7so13167620vsl.11; Mon, 30 Jan 2023 09:06:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qxxVdtJql45H9c1FJpz32YKMsD/AXOqCznkVlhy2HdU=; b=HXrDT1OWLwvVz3wbtzauAJjq9xznNMIDcMCPOzMMF6wpH7tc+hcIsIoSWyNO/wEYof W1B6kE5SY69BkjJduFMSssHNf5/5m+tgBnF1OedkfkdFg/MmxNRpxDmwxJ0siY0+Kbz7 p3EOH+jx3/yGu9sRjfgZ+TYhDKfybbESypTbwA65TuXa7U9NE3wkMev++ffvcvcoRnf4 crpK0N4r4J8YaPL5CAJEAsnft/S3u97nmZz8dMs6SfVs9TbaOWAsGZweGGYK71T8KwK8 VC46IgtIKTVrB3y12Tj86q1zqd/eA86fQH1ejkVLUNm1k8odcdYkiG60fOr1AQbHi4rV Fa6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qxxVdtJql45H9c1FJpz32YKMsD/AXOqCznkVlhy2HdU=; b=bVtKCOuZr/C9OKbT16Y+L+vbfghdFmfP8nnL/5ySNc582+BBFOcNID9+AhJ2bsjHdY uQRMF9w35ZA0Io17OJKRUbc1CTQ6N4XnSaYZ6/APzqS6vzMvXzdDdFkKdSr7dZGJl+G0 u8MdalbVFoptXzenECsyCyjFVqdJnzA47e71ikBEgw/2WP5X6URieU3nqDaN8VNgguQp Dt/VHBVppHHWs5v+41zoDfbEkk7A0RcVVXz4b4eTWpkwyl7LNSnjKDIzizSLj7ufx6et mA5QJHfyYQsrDjP703z76whzVwNBBzTxdtkcrFbje44CYlt641bM/CIROfqrSaQgc8Jg ZDCQ== X-Gm-Message-State: AO0yUKUUC3zv+q93ZkuyG8TDi5JYne8/iSK8STkhDiN81t9W2jZ6H/gQ NMdCCJba26ihmpjpKFDUhoIdWr351dnfYj1mtw06cXLS/lbgR0Oitnw= X-Google-Smtp-Source: AK7set+0YvWFxY/ow2/rri2o5ipKNHMAWCl2sa5/fwbH1Emgxm2BzBS+psN6msRvoEi5EKma13dtXSz09Ca0im/j8tA= X-Received: by 2002:a67:c31e:0:b0:3ed:1e92:a87f with SMTP id r30-20020a67c31e000000b003ed1e92a87fmr1836364vsj.1.1675098395499; Mon, 30 Jan 2023 09:06:35 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> In-Reply-To: From: ykla Date: Tue, 31 Jan 2023 01:06:21 +0800 Message-ID: Subject: Re: Tooling Integration and Developer Experience To: Kurt Jaeger Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d3e25605f37e3c7c" X-Rspamd-Queue-Id: 4P5F2h475Kz4L5K X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000d3e25605f37e3c7c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, The documentation project on reviews.freebsd.org is also very inactive. For example, it's been almost 3 months since I submitted my revision - https://reviews.freebsd.org/D37322. After I submitted it, it was neither reviewed nor approved for a long time. Now, due to changes in the FreeBSD documentation, some of my changes conflict with the current documentation and are difficult to resolve. I suppose I could spend some time going over it again and again, but if no one accepts it, it is pointless. Maybe I shouldn't make such extensive changes to the documentation.Can you advise me on how I should go about doing this? Thanks a lot. ykla Kurt Jaeger =E4=BA=8E2023=E5=B9=B41=E6=9C=8830=E6=97=A5=E5= =91=A8=E4=B8=80 18:33=E5=86=99=E9=81=93=EF=BC=9A > Hello, > > > I had a similar thing happen to me, the mailing list FreeBSD-doc seemed > to > > exist as if no one existed, and there was no one posting in it except f= or > > the automated bug reports from the bots. > > I have not had any replies to my several posts either. > > > So can the admins tell how many people actually > > subscribe to FreeBSD-doc, > > The list has 496 subscribers right now. (speaking as one of postmaster@). > > > or is this just a place to report bugs and people > > should discuss FreeBSD doc-related issues elsewhere? Or is it that almo= st > > nobody cares about the FreeBSD documentation? > > From my observation, the last few month led to a huge pile of > workload on many folks that are involved with FreeBSD stuff, so > not many folks had time to reply/think things through/answer. > I had the same problem... > > I see doc-stuff happen mostly on reviews.freebsd.org. (speaking > as one of phabric-admins). Pau Amma is the most active docs-person > as far as I can see. I have not calculated stats, just my gut feeling. > > -- > pi@opsec.eu +49 171 3101372 Now what ? > > --000000000000d3e25605f37e3c7c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

The documentation = project on reviews.freebsd.org i= s also very inactive. For example, it's been almost 3 months since I su= bmitted my revision - https:= //reviews.freebsd.org/D37322. After I submitted it, it was neither revi= ewed nor approved for a long time. Now, due to changes in the FreeBSD docum= entation, some of my changes conflict with the current documentation and ar= e difficult to resolve. I suppose I could spend some time going over it aga= in and again, but if no one accepts it, it is pointless. Maybe I shouldn= 9;t make such extensive changes to the documentation.Can you advise me on h= ow I should go about doing this? Thanks a lot.

ykla

Kurt Jaeger <pi@freebsd.org&g= t; =E4=BA=8E2023=E5=B9=B41=E6=9C=8830=E6=97=A5=E5=91=A8=E4=B8=80 18:33=E5= =86=99=E9=81=93=EF=BC=9A
Hello,

> I had a similar thing happen to me, the mailing list FreeBSD-doc seeme= d to
> exist as if no one existed, and there was no one posting in it except = for
> the automated bug reports from the bots.
> I have not had any replies to my several posts either.

> So can the admins tell how many people actually
> subscribe to FreeBSD-doc,

The list has 496 subscribers right now. (speaking as one of postmaster@).
> or is this just a place to report bugs and people
> should discuss FreeBSD doc-related issues elsewhere? Or is it that alm= ost
> nobody cares about the FreeBSD documentation?

>From my observation, the last few month led to a huge pile of
workload on many folks that are involved with FreeBSD stuff, so
not many folks had time to reply/think things through/answer.
I had the same problem...

I see doc-stuff happen mostly on reviews.freebsd.org. (speaking
as one of phabric-admins). Pau Amma is the most active docs-person
as far as I can see. I have not calculated stats, just my gut feeling.

--
pi@opsec.eu=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +49 171 3101372=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Now what ?

--000000000000d3e25605f37e3c7c-- From nobody Mon Jan 30 17:32:35 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5FcS3B5Tz3c2Qs for ; Mon, 30 Jan 2023 17:32:24 +0000 (UTC) (envelope-from ihor@antonovs.family) Received: from mail.antonovs.family (mail.antonovs.family [100.25.240.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.antonovs.family", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5FcR69yBz3ByK for ; Mon, 30 Jan 2023 17:32:23 +0000 (UTC) (envelope-from ihor@antonovs.family) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=antonovs.family header.s=20200215 header.b=BSXQYsgV; spf=pass (mx1.freebsd.org: domain of ihor@antonovs.family designates 100.25.240.195 as permitted sender) smtp.mailfrom=ihor@antonovs.family; dmarc=pass (policy=none) header.from=antonovs.family DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antonovs.family; s=20200215; t=1675099939; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wPyJIoRui49R3lLyJHbxcgLmcBnJF2Yf4egG5yVWWZY=; b=BSXQYsgVjLYXjiXOLisFJz1/xPF3I9IVRhtsAbvp9rexyn3GgxakUKATAJjBNmLYj7xjTB Hkpn7Wk+D7DxSFB7PwXnkR7iRw8GvjMXRlUliRrVrMmyW1wOitRvkRCx+yBJxDPvaE43vR ka6wjat+L/u5SlhtTxQiuId3cU1MWUI= Received: by mail.antonovs.family (OpenSMTPD) with ESMTPSA id d2449899 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Mon, 30 Jan 2023 17:32:18 +0000 (UTC) Message-ID: Date: Mon, 30 Jan 2023 17:32:35 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Tooling Integration and Developer Experience Content-Language: en-US To: freebsd-current@freebsd.org References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> From: User Ngor In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; DMARC_POLICY_ALLOW(-0.50)[antonovs.family,none]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[antonovs.family:s=20200215]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[antonovs.family:+]; ASN(0.00)[asn:14618, ipnet:100.24.0.0/13, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4P5FcR69yBz3ByK X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 1/30/23 13:53, Warner Losh wrote: > On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote: > >> Hi, >> >>>> On 1/30/23 02:54, Julian H. Stacey wrote: >>>> The main idea: to prevent information fragmentation and improve >>>> discoverability, cross-referencing abilities, search, etc. >>> With regards to improving discoverability, Phabricator's Owner >>> tool could be a good tactical move: it allow to bind code area to >>> peoples in order to automatically add them to reviews. >> If you know phabricator in more detail, is there any kind of tool >> to understand the activity going on ? >> >> In bugs.freebsd.org, there is the dashboard: >> >> https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html >> >> I think we might need something similar to help us understand >> the current state of the phabricator instance and the work >> being done. >> >> Phab allows Dashboards, but no-one had the time to configure some >> queries to provide relevant stats. >> > Phab is a terrible tool for discovery. For example, how do I query all the > reviews I've ticked 'OK' that are still open, by non-committers? How do I > flag things as 'interesting to me'? I can tick a flag, but I can't query > flags. Also, I can't get an email address for submitter either. That makes > it more of a pain to land the commit. You can search flags here [1]. You can filter them by color and the object (i.e. differential revision or any other Phab thing). Flags are personal and not visible to anybody else For common use I think tags are better and are queryable in here [2]. Tags require projects, projects can be created by administrators, this is a bit counter-intuitive, but it works > But there's two other issues: The FreeBSD project has had a long history of > being behind, regardless of the tools we use. There's a labor shortage to > process these things as well. Second, lots of people want to talk, but few > want to do the work. I tried leading an effort in this area,but grew weary > of the passive-aggressive comments about how I basically sucked for not > having it done already (from the same people that did 0 actual work on it). > I'd love to help and do the grunt work. What is important is some form of consensus that project actually needs this. I don't know how this works, the is very little visibility from the Core on these matters. [1]https://reviews.freebsd.org/flag/ [2] https://reviews.freebsd.org/differential/query/advanced/ -- Ihor Antonov From nobody Mon Jan 30 18:29:13 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5Gt25f8xz3c9pp for ; Mon, 30 Jan 2023 18:29:14 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5Gt254Zqz3Ltv; Mon, 30 Jan 2023 18:29:14 +0000 (UTC) (envelope-from mhorne@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675103354; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ea/FQjWh963E3cTRs7YpdU1uE2Ihe/FnA2JWTtbC9vw=; b=bAWziErunZ/m3wPqwrbcdQTWTu/IbM1DR76PibUGuLqRKrPFNxZ7aWiQij09JX1LNoP2jJ bZJnBtyNKLQ+P3QmaV3BYUYWrB7Z1gXrZ+Nqwyx2pnJHs/JitN3Ct/j8yoz18PgTUmDZIa JEJC6X4+N9oVczmOJc0XKRPYGg/VcpiQAHgcCFXrsuQVAs+RG3DVWbqrkQCwHgvf8O1uA4 1HdKI9auFRZDbGDu3b6yU0q2uppSR52jxd6hhwZZILAbTXBXf7NFlVryneruBfym7oVgzD v9yaXYxdQ7Vhjh4dN0r5o5qj9HzFq5Tf7ShwSj4MOSn8J3ohR4EFGL54so3BYw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675103354; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ea/FQjWh963E3cTRs7YpdU1uE2Ihe/FnA2JWTtbC9vw=; b=xlJy6EHp1zsSgZYPfVXt0HD3gXjMfiawpnhoUAW05SGd956rpwxrK4t69XfTB6JRxyMPEc iaPLXhHjMJ2tN2qJKhiFyR4+bUqV4NbxJxibw8h4HrGA6DVpDfgBdiI0UkUQzgpvWD8Ns7 L6cpJ3MmatcZcPJbrZeq9/Jj0BToI/ptlYFMEHjoklj3a1JgHAMnrG3iP3xgyxRKFGYnu2 kplqQY6kI2nU88rH9qW9abxZNPAUh94V2AsP4eSLUAJm3zczBNtPkRoXeJloP4ArF1VCPG 6Hgr+o7nFPtXxsnMUZ3PcYn89GtzJPXEaEwh86vrabAP2+7BsHLmp1BntlZEgA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675103354; a=rsa-sha256; cv=none; b=WN6qKm8LGYmftes6GZJJ3jPlFX8Uy0iX53x15ttEfkeq/Nt4WHKbw0fWE/Cffcs0MAfGBk Lx56NPx8NBqnrCtapJwWHuSDJTWgpntIQD+NuLxHxLCwJYYIcqlCoKt4Ko3OKLFFTAeuLF Qe6e38kBgJnWgzuYq0o+Zn5uLH+rcQSJG4JLmlxJtYqanvkqf4P1yrrvQnAILGKL9dI1ec Zb1yUuKOnzq3GlCkWmjd6d79koAAgVAUVXpFuqcXVYlAOcpgvWfvRztg2V7r4cIiMXUoGx h+WxWd2iT8QkrlN0bdxk0/D51pW9pS5sozW2u1mffC0BeF+tvlZS33s3AHo1BQ== Received: from [192.168.1.151] (host-173-212-76-127.public.eastlink.ca [173.212.76.127]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: mhorne) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P5Gt22X5WzFkP; Mon, 30 Jan 2023 18:29:14 +0000 (UTC) (envelope-from mhorne@freebsd.org) Message-ID: <35e07b16-e635-a88c-f10b-cde0df05140b@freebsd.org> Date: Mon, 30 Jan 2023 14:29:13 -0400 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Tooling Integration and Developer Experience Content-Language: en-CA To: User Ngor , freebsd-current@freebsd.org, Warner Losh References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> From: Mitchell Horne In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 1/30/23 13:32, User Ngor wrote: > On 1/30/23 13:53, Warner Losh wrote: >> On Mon, Jan 30, 2023 at 3:40 AM Kurt Jaeger wrote: >> >>> Hi, >>> >>>>> On 1/30/23 02:54, Julian H. Stacey wrote: >>>>>     The main idea: to prevent information fragmentation and    improve >>>>>     discoverability, cross-referencing abilities, search, etc. >>>> With regards to improving discoverability, Phabricator's Owner >>>> tool could be a good tactical move: it allow to bind code area to >>>> peoples in order to automatically add them to reviews. >>> If you know phabricator in more detail, is there any kind of tool >>> to understand the activity going on ? >>> >>> In bugs.freebsd.org, there is the dashboard: >>> >>> https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html >>> >>> I think we might need something similar to help us understand >>> the current state of the phabricator instance and the work >>> being done. >>> >>> Phab allows Dashboards, but no-one had the time to configure some >>> queries to provide relevant stats. >>> >> Phab is a terrible tool for discovery. For example, how do I query all >> the >> reviews I've ticked 'OK' that are still open, by non-committers? How do I >> flag things as 'interesting to me'? I can tick a flag, but I can't query >> flags. Also, I can't get an email address for submitter either. That >> makes >> it more of a pain to land the commit. > You can search flags here [1]. You can filter them by color and the object > (i.e. differential revision or any other Phab thing). > Flags are personal and not visible to anybody else > > For common use I think tags are better and are queryable in here [2]. > Tags require projects, projects can be created by administrators, this is > a bit counter-intuitive, but it works > For what it's worth, I experimented with creating some "useful" queries a little while back. The advanced search function was clunky to use, and really leaves a lot to be desired in terms of specificity. As mentioned elsewhere, no regex, and some of the things you can filter for when creating Herald rules are unavailable to the advanced search. Which is a shame, because overall I am a fan of phabricator as a review tool. Anyway, here they are (you can click Use Results to save it): [Src] Needs Committer https://reviews.freebsd.org/differential/query/oCjMrczXbpBS/ [Src] Needs Reviewer https://reviews.freebsd.org/differential/query/65AoyPFlIhdE/ [Src] Stale Revisions (1yr+) https://reviews.freebsd.org/differential/query/bGPGaIhtb0PX/ [Src] Stalled Revisions (changes required, changes planned, WIP) https://reviews.freebsd.org/differential/query/WD_lfbHCq1P_/ Mitchell >> But there's two other issues: The FreeBSD project has had a long >> history of >> being behind, regardless of the tools we use. There's a labor shortage to >> process these things as well. Second, lots of people want to talk, but >> few >> want to do the work. I tried leading an effort in this area,but grew >> weary >> of the passive-aggressive comments about how I basically sucked for not >> having it done already (from the same people that did 0 actual work on >> it). >> > I'd love to help and do the grunt work. What is important is some form of > consensus that project actually needs this. I don't know how this works, > the is very little visibility from the Core on these matters. > > [1]https://reviews.freebsd.org/flag/ [2] > https://reviews.freebsd.org/differential/query/advanced/ > From nobody Mon Jan 30 21:09:21 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5LVT18NQz3cZ4S for ; Mon, 30 Jan 2023 21:12:33 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from mcusim.org (mcusim.org [IPv6:2a00:dd80:3c::e63]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5LVS6GvLz3wLG; Mon, 30 Jan 2023 21:12:32 +0000 (UTC) (envelope-from dsl@mcusim.org) Authentication-Results: mx1.freebsd.org; none Received: from localhost (unknown [193.164.254.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mcusim.org (Postfix) with ESMTPSA id 16BA28B689; Mon, 30 Jan 2023 22:12:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mcusim.org; s=default; t=1675113150; bh=wSfGNKYDNa/tGZLc7fsuk42JVvLVNj0StzzYs8aiibE=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=trxC6fZcT91uxRTpS6TP+7IGfxpuu6ZMnctXqm43ezV/TlTWNHFDHRDzigKHavuUp 9Ez8cPyCGDaspbf/92zjPYXdJOVmb9sqxa01cEJbGjn2wCn0OgUAz5RCJUHOhEOBTr YECPLlaJ9ux45YDgWZlsV2FKJ3POE1jM+xwzZMZA= References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <86edrcp13z.fsf@peasant.tower.home> <86zga0nf1q.fsf@peasant.tower.home> User-agent: mu4e 1.6.10; emacs 28.2 From: Dmitry Salychev To: Warner Losh Cc: Kurt Jaeger , Stephane Rochoy , freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Date: Mon, 30 Jan 2023 22:09:21 +0100 In-reply-to: Message-ID: <86sffrohfn.fsf@peasant.tower.home> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 4P5LVS6GvLz3wLG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:2a00:dd80:3c::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Maybe, but my laziness won't let me keep it that simple :) https://reviews.freebsd.org/H185 should do the trick, I think. Warner Losh writes: > I think just "sys/dev/dpaa2" is all you need when adding the Herald rule. :) > > More generally, no, there's no way that I've found to only match files that match certain regexp. > > Warner > > On Mon, Jan 30, 2023 at 9:49 AM Dmitry Salychev wrote: > > Warner Losh writes: > > > On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote: > > > > Hi, > > > > Kurt Jaeger writes: > > > > > Hi, > > > > > >> > On 1/30/23 02:54, Julian H. Stacey wrote: > > >> > The main idea: to prevent information fragmentation and improve > > >> > discoverability, cross-referencing abilities, search, etc. > > >> > > >> With regards to improving discoverability, Phabricator's Owner > > >> tool could be a good tactical move: it allow to bind code area to > > >> peoples in order to automatically add them to reviews. > > > > > > If you know phabricator in more detail, is there any kind of tool > > > to understand the activity going on ? > > > > > > In bugs.freebsd.org, there is the dashboard: > > > > > > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html > > > > > > I think we might need something similar to help us understand > > > the current state of the phabricator instance and the work > > > being done. > > > > > > Phab allows Dashboards, but no-one had the time to configure some > > > queries to provide relevant stats. > > > > I'd prefer to have an automatic note via email from Phabricator if any > > file with my copyright was modified/patched/improved in a newly opened > > review. > > > > I don't think that people tend to ignore changes to those parts of code > > they've written (or touched at least). > > > > You can easily create a herald rule to do this. I have one for all of src, but others have subsets > > like the boot loader. And anybody with an account can do that. > > > > Warner > > Looks really useful, thanks for a hint. Is there any way to test regexp > matching for files content? Btw, there could be a carefully selected set > of pre-defined Herald rules added to any new committer's account. > > -- > Dmitry Salychev -- Dmitry Salychev From nobody Mon Jan 30 21:18:32 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5Ldh1MQqz3cbKc for ; Mon, 30 Jan 2023 21:18:48 +0000 (UTC) (envelope-from carlavilla@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5Ldh0sftz40XB; Mon, 30 Jan 2023 21:18:48 +0000 (UTC) (envelope-from carlavilla@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675113528; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TcH6LivLfVFXGzcBIjQ+NEpHWS8Y8aEqK4UpWdBAxa8=; b=KoCNDdO+d0ZIEV2v/jRz5W+B9D2Uh3Z/I2+H64hBYeFzWa8UWbAAQqOjsj7FVwos6URHTk mPYPOmnffXvT/Z1IcWov5VwNplFZIpd0oZcR1g4U+441SqyLewvcQGWJPHGvx19nzfNhTc 8mesx+N8DSzcu0Th1pFJLAconhEs6e/Q1aJOHDWMvSbm2T7MSgrPLLDr+Zsc9RCDcrhia8 jBNSuZqiLttYaWVkyK9J825/q1QDWEAbQs7EJyAEHs3e0hxA1v3gv64liJtNqQqvwXaJew 8OGYPw0hgWVqhnD3sd+q2yTbErSN2eRi1Bc3vdn/Ia0b1bW2cY3O+OPzIbcumg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675113528; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TcH6LivLfVFXGzcBIjQ+NEpHWS8Y8aEqK4UpWdBAxa8=; b=tNyaRRCBGxWzzz4sbwKEkWQt+PWsh5wuiwLSM5rzcmONpgSPuYi5TheM9gXu6TdFS/E0fg imJYEKps/2rQq4hLcQiJZwmL29Rq4X+tn5cumAywHIpC3yUmUz6Gzoiw/9HeeOPYH4vfEe KCGfDASC/eiEKc4cozaLAnasHBpxrm2HEw/Iz69O1abxItN9wzw67C7vwkPV0BWeZ2O7SD OohJ5eFQez7n1dlVOxzzF/yOAaipKaKfOTcRz1FllPnxOAkcYeZfgxBBqidNklOfWe3z8M QTOSkabOM4ufXRfbU4gYvDDQPJ6oMVB59xcdpZA7e0+yEmWWxly0xYjwsAchxQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675113528; a=rsa-sha256; cv=none; b=qXwnExXq0hyAwdTzk18VEvd+684t6Bj4tQpMdsIgDsuV0zFv9HahPW3+bGsRfdLIkQSvnE ez7gNfsPYHru1eMIIPu0qfuCk2K4SvVxQdOBtpAF3V53euPPYobiU74rkl0UysqRltaSf3 b2JqaUGEpbfqEtkF3osTOeHhZ9uuZln06YhLj8qFVCwZyoYavcr1ez7IpE/hmvA9VWA19r BuPT7G5UZ5+ngLZqce7lROFsR5GAWACufqACufo8aW1nGGbzFahyp8fyjdWO6dfGPWCC6I yZRv0xPiyClt2W17tggyiNZQ0vgEkzDYq7rTn/RE9ZK7w2PEovPBGwT2BqN+Nw== Received: from mail-ot1-f46.google.com (mail-ot1-f46.google.com [209.85.210.46]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: carlavilla) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P5Ldg6tWbzJhR; Mon, 30 Jan 2023 21:18:47 +0000 (UTC) (envelope-from carlavilla@freebsd.org) Received: by mail-ot1-f46.google.com with SMTP id g21-20020a9d6495000000b0068bb336141dso3066116otl.11; Mon, 30 Jan 2023 13:18:47 -0800 (PST) X-Gm-Message-State: AO0yUKVJN4zJGA7qliA8vmX+8qchwcMDjBEoqmqtnCSy71GDneDJQqhR mBMFtLCmbzgzx/NX3gz0yGGdezhoCaB8ZSiLr3U= X-Google-Smtp-Source: AK7set9QivzyU2OChFo/2t/TvbE5rSP4w/Y/HP9sNFPiPH4uPca4xDdaL4ziGtvci3+yLQA6D0TIaDF/9vHkYNAyOwA= X-Received: by 2002:a05:6830:4112:b0:68b:d245:5db1 with SMTP id w18-20020a056830411200b0068bd2455db1mr236681ott.64.1675113524635; Mon, 30 Jan 2023 13:18:44 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> In-Reply-To: From: Sergio Carlavilla Date: Mon, 30 Jan 2023 22:18:32 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Tooling Integration and Developer Experience To: ykla Cc: Kurt Jaeger , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000982f4b05f381c284" X-ThisMailContainsUnwantedMimeParts: N --000000000000982f4b05f381c284 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El lun., 30 ene. 2023 18:06, ykla escribi=C3=B3: > Hi, > > The documentation project on reviews.freebsd.org is also very inactive. > For example, it's been almost 3 months since I submitted my revision - > https://reviews.freebsd.org/D37322. After I submitted it, it was neither > reviewed nor approved for a long time. Now, due to changes in the FreeBSD > documentation, some of my changes conflict with the current documentation > and are difficult to resolve. I suppose I could spend some time going ove= r > it again and again, but if no one accepts it, it is pointless. Maybe I > shouldn't make such extensive changes to the documentation.Can you advise > me on how I should go about doing this? Thanks a lot. > > ykla > > Kurt Jaeger =E4=BA=8E2023=E5=B9=B41=E6=9C=8830=E6=97=A5= =E5=91=A8=E4=B8=80 18:33=E5=86=99=E9=81=93=EF=BC=9A > >> Hello, >> >> > I had a similar thing happen to me, the mailing list FreeBSD-doc seeme= d >> to >> > exist as if no one existed, and there was no one posting in it except >> for >> > the automated bug reports from the bots. >> > I have not had any replies to my several posts either. >> >> > So can the admins tell how many people actually >> > subscribe to FreeBSD-doc, >> >> The list has 496 subscribers right now. (speaking as one of postmaster@)= . >> >> > or is this just a place to report bugs and people >> > should discuss FreeBSD doc-related issues elsewhere? Or is it that >> almost >> > nobody cares about the FreeBSD documentation? >> >> From my observation, the last few month led to a huge pile of >> workload on many folks that are involved with FreeBSD stuff, so >> not many folks had time to reply/think things through/answer. >> I had the same problem... >> >> I see doc-stuff happen mostly on reviews.freebsd.org. (speaking >> as one of phabric-admins). Pau Amma is the most active docs-person >> as far as I can see. I have not calculated stats, just my gut feeling. >> >> -- >> pi@opsec.eu +49 171 3101372 Now what ? >> . > > Hi, No, your patch is not pointless. I know that your patch was submitted one month ago, but we're in the review of the complete handbook. I'll try to use your patch in some parts of the review. Sorry if you think that your work is not take in consideration, this is not our idea. My public apologies, as I said, I'll try to use your patch in some places. Of course I'll mention you in the commit in these places. About huge patches, please, create minor patches and put me as a reviewer. And again, thanks for your work. > --000000000000982f4b05f381c284 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


El lun., 30 ene. 2023 18:06, ykla <yklaxds@gmail.com> escribi=C3=B3:
Hi,=C2=A0

The documentation project on reviews.freebsd.org is also very= inactive. For example, it's been almost 3 months since I submitted my = revision - https://reviews.freebsd.org/D37322. After I submitt= ed it, it was neither reviewed nor approved for a long time. Now, due to ch= anges in the FreeBSD documentation, some of my changes conflict with the cu= rrent documentation and are difficult to resolve. I suppose I could spend s= ome time going over it again and again, but if no one accepts it, it is poi= ntless. Maybe I shouldn't make such extensive changes to the documentat= ion.Can you advise me on how I should go about doing this? Thanks a lot.

ykla

Kurt Jaeger <pi@freebsd.org> =E4=BA=8E= 2023=E5=B9=B41=E6=9C=8830=E6=97=A5=E5=91=A8=E4=B8=80 18:33=E5=86=99=E9=81= =93=EF=BC=9A
Hel= lo,

> I had a similar thing happen to me, the mailing list FreeBSD-doc seeme= d to
> exist as if no one existed, and there was no one posting in it except = for
> the automated bug reports from the bots.
> I have not had any replies to my several posts either.

> So can the admins tell how many people actually
> subscribe to FreeBSD-doc,

The list has 496 subscribers right now. (speaking as one of postmaster@).
> or is this just a place to report bugs and people
> should discuss FreeBSD doc-related issues elsewhere? Or is it that alm= ost
> nobody cares about the FreeBSD documentation?

>From my observation, the last few month led to a huge pile of
workload on many folks that are involved with FreeBSD stuff, so
not many folks had time to reply/think things through/answer.
I had the same problem...

I see doc-stuff happen mostly on reviews.freebsd.org. (spea= king
as one of phabric-admins). Pau Amma is the most active docs-person
as far as I can see. I have not calculated stats, just my gut feeling.

--
pi@opse= c.eu=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +49 171 3101372=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Now what ?
.

Hi,

No, your patch is not pointless.

I know that your patch was submitted one month ago, but we'r= e in the review of the complete handbook.

=
I'll try to use your patch in some parts of the revie= w.

Sorry if you think th= at your work is not take in consideration, this is not our idea.

My public apologies, as I said, I&= #39;ll try to use your patch in some places. Of course I'll mention you= in the commit in these places.

About huge patches, please, create minor patches and put me as a = reviewer.

And again, tha= nks for your work.
--000000000000982f4b05f381c284-- From nobody Mon Jan 30 21:39:03 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5M5L21gnz3cfBk for ; Mon, 30 Jan 2023 21:39:18 +0000 (UTC) (envelope-from yetoohappy@gmail.com) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5M5K2Mmtz4421 for ; Mon, 30 Jan 2023 21:39:17 +0000 (UTC) (envelope-from yetoohappy@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=fbLXZh9d; spf=pass (mx1.freebsd.org: domain of yetoohappy@gmail.com designates 2a00:1450:4864:20::634 as permitted sender) smtp.mailfrom=yetoohappy@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x634.google.com with SMTP id qw12so20064232ejc.2 for ; Mon, 30 Jan 2023 13:39:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=W7T+rW9AGsJrd3v/xR99z0Q/MnJe692T10YyPBDJlwk=; b=fbLXZh9dp/2Ux9YBbQyPP/o4cWILkS1w1P5d89ExGBP4yhYhQR/saBw8jlX0cwwFTL DKPT5IA+plnOTMunCiXSu50dJshwgrtj7HQxOGkOiUdt/W2jKK8zFGcjxbqWqzI31ATq uvkSpjrdpc6JtF7klYeZwlycdUJtMEKK2ai2PPjaaT9GYgARBaFIMsxhGANE9rvSx+2H x56wBhf6kO8Wgo1ICMLE/VBACj1USGGam/7pMVN3KxTEuhTuZ8ZGAIlhNmCbq5RPnEHb m6UL6Rg2/UFlvO+Uu9ST0kGldyAVGNp0DegvpU8c5GIGLQGnFnGGNNZDAcxRcXmbTahn uSiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=W7T+rW9AGsJrd3v/xR99z0Q/MnJe692T10YyPBDJlwk=; b=QmobUuxv/9PNCOu4B35WY696dhO7m53BySxHEukv3uCY6Wvs5myp5S8Of9IistC9VM TxfvXOVbcH4Kgm7pjjTkyKbssT3B8HAODdRzjpBwGgiPLEQYJRjMoZhrgJIrLnXnLOqt iZIq29MGMvhWNABI+4/b7ojuyNbBUv3aWGVWuJaYgYCq7TuRrq66k7sKVBVXCzT2w68P qImpWgQEzm6rH6AaTijwtq5rS9ZG87yp+TJA+XKOsLBfuwBDEG0ecZD1JJ2ideEmPt3M Wrl0k/dZnwt2S38U9g7WFr19HgBuvoSG4n+aTrx3jTit8fz75QizhWCmKG12YuDLP+Ww /MTw== X-Gm-Message-State: AO0yUKW3SWI9ys6ESOR8ztr5nRfWhg3R1dKz/ebIGuEDPViWG3UcSf// 6Oq7YTT977jwttZjPNl7NNq4W5qBVBdtw7XY8ufQ941B X-Google-Smtp-Source: AK7set+wTP8yZwLGDYp7R8IZIs/6IgZ5yF14BA+NQw8rGfw8w4FVKk8PG4Nxx+uBfjS4hojbsQyH0L4Hq8CS3LqGzCY= X-Received: by 2002:a17:906:9e05:b0:883:ba3b:ebb8 with SMTP id fp5-20020a1709069e0500b00883ba3bebb8mr2007930ejc.308.1675114756044; Mon, 30 Jan 2023 13:39:16 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> In-Reply-To: <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> From: Yetoo Date: Mon, 30 Jan 2023 13:39:03 -0800 Message-ID: Subject: Re: Tooling Integration and Developer Experience Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000fdfe3705f3820b0b" X-Spamd-Result: default: False [-1.00 / 15.00]; MISSING_TO(2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996]; NEURAL_HAM_SHORT(-0.92)[-0.917]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_LONG(-0.08)[-0.082]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::634:from]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4P5M5K2Mmtz4421 X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N --000000000000fdfe3705f3820b0b Content-Type: text/plain; charset="UTF-8" My two cents... I think some of the integration issues can be resolved with some rule changes and showing those relevant rules that people will see every time they make a pull request, report, etc... as I think what will happen with each item is too uncertain even if there was automation. I think rules should enshrine a single place that will always get reports and places to review or pull request and/or discussion requires reports to be made there first. I think that single place should be bugzilla but I'm a bit biased toward bugzilla as I haven't created an account for freebsd phabricator. This would mean every review on phabricator or pull request on github would need an associated report on bugzilla as well as link to that report and link back on bugzilla in the url field (if only one allowed or easy per report, maybe make dedicated field for other trackers) or first comment or else bugzilla, github, and phabricator posts are closed. The problem of just having someone commenting a link where the pull requestin the middle of a long discussion is that it's hard to find. Perhaps this part can be automated first as it's draconian if rules/warnings can't be seen before and while editing. People can go to the mailing list to talk about issues or submit changes, but no change will be accepted until someone makes a bugzilla report for it and link back to mailing list and from mailing list to it. Then there can be more automation with phabricator and github notifying bugzilla that it exists/important events happened to the bug. I think if the rules viewed bugzilla centralized to all legs then the need for redundant notification and requests, such as git saying if there is an issue/review in phabricator and an issue report in bugzilla or a pull request automatically created in git when submitted to phabricator, would be avoided. If everything is moved into phabricator, including bugzilla, I think it's worth considering whether existing bugzilla reports, patches, tags, etc can be migrated without losing data. Bugzilla could be in a no new reports mode, but there would still be the problem of reports spread out across different systems. If github is going to be considered for issue tracking I just want to say, after having extensively using it for issue tracking, it tends to be difficult to find an issue if the exact title isn't entered and many duplicate reports are made as a result. Code search sucks and doesnt show you the multiple places in a file where a match was made so a user may be left wondering if code exists or not, but this doesn't seem to be germane given this is about issue tracking. > --000000000000fdfe3705f3820b0b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My two cents...

I think some of the integration issues can be resolved= with some rule changes and showing those relevant rules that people will s= ee every time they make a pull request, report, etc... as I think what will= happen with each item is too uncertain even if there was automation. I thi= nk rules should enshrine a single place that will always get reports and pl= aces to review or pull request and/or discussion requires reports to be mad= e there first. I think that single place should be bugzilla but I'm a b= it biased toward bugzilla as I haven't created an account for freebsd p= habricator.=C2=A0This would mean every review on phabricator or pull reques= t on github would need an associated report on bugzilla as well as link to = that report and link back on bugzilla in the url field (if only one allowed= or easy per report, maybe make dedicated field for other trackers) or firs= t comment or else bugzilla, github, and phabricator posts are closed. The p= roblem of just having someone commenting a link where the pull requestin th= e middle of a long discussion is that it's hard to find.=C2=A0 Perhaps = this part can be automated first as it's draconian if rules/warnings ca= n't be seen before and while editing. People can go to the mailing list= to talk about issues or submit changes, but no change will be accepted unt= il someone makes a bugzilla report for it and link back to mailing list and= from mailing list to it. Then there can be more automation with phabricato= r and github notifying bugzilla that it exists/important events happened to= the bug. I think if the rules viewed bugzilla centralized to all legs then= the need for redundant notification and requests, such as git saying if th= ere is an issue/review in phabricator and an issue report in bugzilla or a = pull request automatically created in git when submitted to phabricator, wo= uld be avoided.

If every= thing is moved into phabricator, including bugzilla, I think it's worth= considering whether existing bugzilla reports, patches, tags, etc can be m= igrated without losing data. Bugzilla could be in a no new reports mode, bu= t there would still be the problem of reports spread out across different s= ystems.

If github is goi= ng to be considered for issue tracking I just want to say, after having ext= ensively using it for issue tracking, it tends to be difficult to find an i= ssue if the exact title isn't entered and many duplicate reports are ma= de as a result. Code search sucks and doesnt show you the multiple places i= n a file where a match was made so a user may be left wondering if code exi= sts or not, but this doesn't seem to be germane given this is about iss= ue tracking.

--000000000000fdfe3705f3820b0b-- From nobody Tue Jan 31 07:52:40 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5ckH6lmTz3bSqM for ; Tue, 31 Jan 2023 07:53:43 +0000 (UTC) (envelope-from parv.0zero9@gmail.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5ckG65hRz40nY for ; Tue, 31 Jan 2023 07:53:42 +0000 (UTC) (envelope-from parv.0zero9@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=FRpCTqqy; spf=pass (mx1.freebsd.org: domain of parv.0zero9@gmail.com designates 2a00:1450:4864:20::632 as permitted sender) smtp.mailfrom=parv.0zero9@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x632.google.com with SMTP id mf7so20363798ejc.6 for ; Mon, 30 Jan 2023 23:53:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=YaSRyZQeB2Q5Nm9dsLUVUd6gjfT2t/mDF/ZcnksyZIk=; b=FRpCTqqywFEOmZUE6I6x2aqfMQkPuhhLQS0Pp909N4ASUGWuQCE4ev3fwM9+wj+HG2 ku7pWgbD365fSLU7vZmIYVVLEBxTzzCPcpF2eSw2RsRzZZELZ4xy+bIszpR+UO+vIX5y 6bk/OA8XK0b9BQD4smfjPQEVeXySbPIfmQ4s3PkVBPXIEQTCJmzzWT1wnJYuaB69g2/k n9vZwp44hpOm3lSpkeUwSKtTI7l6y3sgnw9qHi/q+EMVg4XuCC0tKhgk2sCklQkXP+Bo sNRSR41Kpz3SXtYc3y0+lv2rbcLJpvxJ9HVXEFcVFNU8SC06CnwigCyeMb4A0wuEKVmw UC+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=YaSRyZQeB2Q5Nm9dsLUVUd6gjfT2t/mDF/ZcnksyZIk=; b=CzwlPYJJOXS3eW8U4NNOG6BXI3CX04WECDHgxvRBxtQ5aurjDV2QwW49IuCosU5sG/ X2CRasIghPF/tToEojlm7SOWe+haJe9kHETj9R9vhh7Xn4yLcKWYGo/grvynShjViyek F7WHg5QOMES0rGXjb+V/SoQsMXLqzd+pXMxG/t4/m/VZtqWrdT29SwVA7Et8UCt92Qkl R7zl0JLnWaU2T1j/BNDRtSwwkbfc3vrxJc3I7Vn7GenuyceYhXYr5UjwBlmTELYXsRSj jDBZCogXvioHVp4Z55ljKbM2iK7Oc6F34UJTjFXamjczjXiajnEBF7667ackCMqB9axY cZyg== X-Gm-Message-State: AO0yUKXD8EY2K8LlQpvKiZlZ3KBr5R+1zcxNI66pUw16tP5CCMhyMFes ePaRx6ZH7B/i00R5iRrCzVacEvSFdd8YEAtiEBg3DplJhAw= X-Google-Smtp-Source: AK7set8BHhfXeskjqhqNbvBDB8ETJrjHcgBrumxdlJl0NB83ucUOS+gR0fk9mBy0eCPRMFz8zDF01bABI8nAf/GKND4= X-Received: by 2002:a17:906:6542:b0:88a:47d7:3c3a with SMTP id u2-20020a170906654200b0088a47d73c3amr1451357ejn.182.1675151621099; Mon, 30 Jan 2023 23:53:41 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: "parv/FreeBSD" Date: Mon, 30 Jan 2023 21:52:40 -1000 Message-ID: Subject: Could not change brightness anymore with i915kms & acpi_video modules c 202211 To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000521dde05f38aa1de" X-Spamd-Result: default: False [-3.97 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.97)[-0.968]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::632:from]; ARC_NA(0.00)[]; TAGGED_FROM(0.00)[freebsd]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4P5ckG65hRz40nY X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000521dde05f38aa1de Content-Type: text/plain; charset="UTF-8" Hi there, Since around 2022-11, I am unable to change display brightness of the display of a Framework laptop (Intel i5-1135G7, Iris Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port) & "acpi_video" (FreeBSD) kernel module. Earlier I was able to change brightness via "hw.acpi.video" MIB ... # - Need to have both "i915kms" & "acpi_video" modules already loaded. # # 20221120 - These MIBs do not work anymore as they are missing. hw.acpi.video.lcd0.economy=10 hw.acpi.video.lcd0.fullpower=40 hw.acpi.video.lcd0.brightness=15 ... now the whole of "hw.acpi.video" stub is missing. Nothing has changed in terms of how/when "i915kms" & "acpi_video" are loaded (via "kld_list" variable via "/etc/rc.conf" in that order). What am I missing? - parv ## /etc/rc.conf : clear_tmp_enable="YES" sendmail_enable="NONE" sshd_enable="YES" zfs_enable="YES" dumpdev="AUTO" hostname="luna" devmatch_blacklist="ng_ubt" devmatch_blacklist="$devmatch_blacklist if_iwlwifi" moused_enable="YES" kld_list="filemon" # As of 20220316 on 14-CURRENT order of values assigned to a variable matters # enough that assigning "acpi_video" after "i915kms" is sufficient. # # WARNING - After loading 'acpi_video' module, brightness suddenly increases # blindingly. # # XXX: If i915kms does not load properly on boot, say after world install, will # see a blank screen & Ctrl-Alt-{Delete,Backspace,Escape} do not seem to # work; need a hard reboot. # # 20230120 - Since around 2022-11 or 2022-12, order has no effect on brightness. kld_list="$kld_list i915kms" kld_list="$kld_list acpi_video" # Attemp to maximize battery life. power_profile='economy' economy_cx_lowest='Cmax' performance_cx_lowest='C2' wifibox_enable="YES" defaultrouter="10.0.0.1" defaultroot_delay="10" ifconfig_wifibox0="SYNCDHCP" background_dhclient_wifibox0="YES" ntpd_enable="YES" ntpd_flags="-G" dbus_enable="YES" smartd_enable="YES" ## /etc/sysctl.conf : kern.randompid=1 vfs.usermount=1 kern.vt.kbd_halt=1 kern.vt.kbd_poweroff=1 kern.vt.kbd_reboot=1 kern.vt.kbd_debug=1 kern.vt.kbd_panic=1 vfs.zfs.arc.max=30064771072 dev.hwpstate_intel.0.epp=70 dev.hwpstate_intel.1.epp=70 dev.hwpstate_intel.2.epp=100 dev.hwpstate_intel.3.epp=100 dev.hwpstate_intel.4.epp=100 dev.hwpstate_intel.5.epp=100 dev.hwpstate_intel.6.epp=100 dev.hwpstate_intel.7.epp=100 kern.timecounter.hardware='HPET' hw.acpi.lid_switch_state='S5' hw.acpi.sleep_button_state='S5' # 'acpi_video' module needs to be loaded after 'i915kms' module to have LCD # brightness related MIBs -- hw.acpi.lcd0.* -- to have any effect. This has # been an issue since 2014, see PR 195116, # . # # As of 20220316 on 14-CURRENT order of values assigned to a variable matters # enough that assigning "acpi_video" after "i915kms" to "$kld_list" in # "/etc/rc.conf" is sufficient. # # WARNING - After loading 'acpi_video' module, brightness suddenly increases # blindinly. # # Default of 50 for 'hw.acpi.video.lcd0.brightness' rather too bright; 100 is # blinding. # - Need to have both "i915kms" & "acpi_video" modules already loaded. # # 20221120 - These MIBs do not work anymore as they are missing. #hw.acpi.video.lcd0.economy=10 #hw.acpi.video.lcd0.fullpower=40 #hw.acpi.video.lcd0.brightness=15 # Power management with "i915kms" module from "drm-devel-kmod" (14-CURRENT) # package. # - only in "/boot/loader.conf" ... # # compat.linuxkpi.i915_enable_dc=2 # compat.linuxkpi.i915_disable_power_well=<-1|0|1> # # ... that means need to load i915kms in "/boot/loader.conf" too.? # compat.linuxkpi.i915_fastboot=1 compat.linuxkpi.i915_enable_fbc=1 ## /boot/loader.conf : cryptodev_load="YES" zfs_load="YES" kern.msgbufsize=1146880 ums_load="YES" hms_load="YES" hw.vga.textmode=0 kern.vty=vt # Need to load after i915kms module to have effect; so is loaded via # /etc/rc.conf instead by adding it to $kld_list after "i915kms" as in # 'kld_list="i915kms acpi_video"'. #acpi_video_load="YES" machdep.hwpstate_pkg_ctrl=0 coretemp_load="YES" ## From "/etc/rc.conf" ... # Power management with "i915kms" module from "drm-devel-kmod" (14-CURRENT) # package. # - only in "/boot/loader.conf" ... # # compat.linuxkpi.i915_enable_dc=2 # compat.linuxkpi.i915_disable_power_well=<-1|0|1> # # ... that means need to load i915kms in "/boot/loader.conf" too.? # #compat.linuxkpi.i915_fastboot=1 #compat.linuxkpi.i915_enable_fbc=1 hw.pci.do_power_nodriver=2 --000000000000521dde05f38aa1de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi there,

= Since around 2022-11, I am unable to change display brightness
of the display of a F= ramework laptop (Intel i5-1135G7, Iris
Xe iGPU) with "i915kms" module (fro= m "drm-510-kmod" package/port)
& "acpi_video" (FreeBSD) kern= el module.

Ea= rlier I was able to change brightness via "hw.acpi.video" MIB ...=

# - Need to = have both "i915kms" & "acpi_video" modules already = loaded.
#
# 20221120 - These MIBs do not work anymore as they are mis= sing.
hw.acpi.video.lcd0.economy=3D10
hw.acpi.video.lcd0.fullpower=3D= 40
hw.acpi.video.lcd0.brightness=3D15


... now the whole of "hw.acpi.video" stub= is missing. Nothing has
changed in terms of how/when "i915kms" & &quo= t;acpi_video" are loaded (via
"kld_list" variable via "/etc/rc.= conf" in that order).

What am I missing?


- parv


## /etc/rc.conf :
clear_tmp_enable=3D"YES"
sendm= ail_enable=3D"NONE"
sshd_enable=3D"YES"
zfs_enabl= e=3D"YES"
dumpdev=3D"AUTO"

hostname=3D"l= una"

devmatch_blacklist=3D"ng_ubt"
devmatch_blackl= ist=3D"$devmatch_blacklist if_iwlwifi"

moused_enable=3D&qu= ot;YES"

kld_list=3D"filemon"

# As of 20220316 = on 14-CURRENT order of values assigned to a variable matters
# enough th= at assigning "acpi_video" after "i915kms" is sufficient= .
#
# WARNING - After loading 'acpi_video' module, brightness= suddenly increases
# blindingly.
#
# XXX: If i915kms does not loa= d properly on boot, say after world install, will
# =C2=A0 =C2=A0 =C2=A0= see a blank screen & Ctrl-Alt-{Delete,Backspace,Escape} do not seem to<= br># =C2=A0 =C2=A0 =C2=A0work; need a hard reboot.
#
# 20230120 - Sin= ce around 2022-11 or 2022-12, order has no effect on brightness.
kld_lis= t=3D"$kld_list i915kms"
kld_list=3D"$kld_list acpi_video&= quot;

# Attemp to maximize battery life.
power_profile=3D'eco= nomy'
economy_cx_lowest=3D'Cmax'
performance_cx_lowest=3D= 'C2'

wifibox_enable=3D"YES"
defaultrouter=3D&qu= ot;10.0.0.1"
defaultroot_delay=3D"10"
ifconfig_wifibox= 0=3D"SYNCDHCP"
background_dhclient_wifibox0=3D"YES"<= br>
ntpd_enable=3D"YES"
ntpd_flags=3D"-G"
dbus_enable=3D&q= uot;YES"
smartd_enable=3D"YES"

## /etc/sysctl.conf :
kern.randompid=3D1
vf= s.usermount=3D1

kern.vt.kbd_halt=3D1
kern.vt.kbd_poweroff=3D1
= kern.vt.kbd_reboot=3D1
kern.vt.kbd_debug=3D1
kern.vt.kbd_panic=3D1
vfs.zfs.arc.max=3D30064771072

dev.hwpstate_intel.0.epp=3D70
= dev.hwpstate_intel.1.epp=3D70
dev.hwpstate_intel.2.epp=3D100
dev.hwps= tate_intel.3.epp=3D100
dev.hwpstate_intel.4.epp=3D100
dev.hwpstate_in= tel.5.epp=3D100
dev.hwpstate_intel.6.epp=3D100
dev.hwpstate_intel.7.e= pp=3D100

kern.timecounter.hardware=3D'HPET'

hw.acpi.l= id_switch_state=3D'S5'
hw.acpi.sleep_button_state=3D'S5'=

# 'acpi_video' module needs to be loaded after 'i915kms= ' module to have LCD
# brightness related MIBs -- hw.acpi.lcd0.* -- = to have any effect. This has
# been an issue since 2014, see PR 195116,<= br># <https://bugs.freebsd.org/bugzilla/show_bug_cgi?id=3D195116>.#
# As of 20220316 on 14-CURRENT order of values assigned to a variable= matters
# enough that assigning "acpi_video" after "i915= kms" to "$kld_list" in
# "/etc/rc.conf" is suff= icient.
#
# WARNING - After loading 'acpi_video' module, brig= htness suddenly increases
# blindinly.
#
# Default of 50 for '= hw.acpi.video.lcd0.brightness' rather too bright; 100 is
# blinding.=
# - Need to have both "i915kms" & "acpi_video" = modules already loaded.
#
# 20221120 - These MIBs do not work anymore= as they are missing.
#hw.acpi.video.lcd0.economy=3D10
#hw.acpi.video= .lcd0.fullpower=3D40
#hw.acpi.video.lcd0.brightness=3D15

# Power management with &quo= t;i915kms" module from "drm-devel-kmod" (14-CURRENT)
# pa= ckage.
# - only in "/boot/loader.conf" ...
#
# =C2=A0 = =C2=A0 compat.linuxkpi.i915_enable_dc=3D2
# =C2=A0 =C2=A0 compat.linuxkp= i.i915_disable_power_well=3D<-1|0|1>
#
# =C2=A0... that means n= eed to load i915kms in "/boot/loader.conf" too.?
#
compat.l= inuxkpi.i915_fastboot=3D1
compat.linuxkpi.i915_enable_fbc=3D1

## /boot/loader.conf :<= /div>
cryptodev= _load=3D"YES"
zfs_load=3D"YES"

kern.msgbufsiz= e=3D1146880

ums_load=3D"YES"
hms_load=3D"YES"=

hw.vga.textmode=3D0
kern.vty=3Dvt

# Need to load after i9= 15kms module to have effect; so is loaded via
# /etc/rc.conf instead by = adding it to $kld_list after "i915kms" as in
# 'kld_list= =3D"i915kms acpi_video"'.
#acpi_video_load=3D"YES&quo= t;

machdep.hwpstate_pkg_ctrl=3D0
coretemp_load=3D"YES"<= br>
## From "/etc/rc.conf" ...
# Power management with &quo= t;i915kms" module from "drm-devel-kmod" (14-CURRENT)
# pa= ckage.
# - only in "/boot/loader.conf" ...
#
# =C2=A0 = =C2=A0 compat.linuxkpi.i915_enable_dc=3D2
# =C2=A0 =C2=A0 compat.linuxkp= i.i915_disable_power_well=3D<-1|0|1>
#
# =C2=A0... that means n= eed to load i915kms in "/boot/loader.conf" too.?
#
#compat.= linuxkpi.i915_fastboot=3D1
#compat.linuxkpi.i915_enable_fbc=3D1

h= w.pci.do_power_nodriver=3D2

--000000000000521dde05f38aa1de-- From nobody Tue Jan 31 08:52:16 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5f1t6Vz2z3bsDr for ; Tue, 31 Jan 2023 08:52:18 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ictdccexch001.one.local", Issuer "Stormshield Servers CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5f1t2S2Yz4556 for ; Tue, 31 Jan 2023 08:52:18 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=stormshield.eu header.s=signer header.b=GtCzVfv1; spf=pass (mx1.freebsd.org: domain of Stephane.ROCHOY@stormshield.eu designates 91.212.116.25 as permitted sender) smtp.mailfrom=Stephane.ROCHOY@stormshield.eu; dmarc=pass (policy=quarantine) header.from=stormshield.eu DKIM-Signature: v=1; a=rsa-sha256; d=stormshield.eu; s=signer; c=simple/simple; t=1675155137; h=from:subject:to:date:message-id; bh=QpREWWVdPWpyDMwtDtMZHDFAT8/47D5KmCdbzdReMuk=; b=GtCzVfv1i4RypfaPqsC6SZPcqspOmUSfq+oTXkI1MFs4B18q/eieB7To7zQfiYDX+PUz459Su69 AK4EWyid8ux9Ur0duA0BnzmdOdUMlKW19YJz1zwMVWQ3NQG0x6v2NAcGJEGMpR/Y01yjChNYyh3J9 SthfWAytd+Y/1zou2PxznBAp9wUXTEkyiL7qcWSd7v03hXgiJ5DnezoX0uJWBhoQCEN20TNMisZt/ ZxCgLSjPEVka+ZJ/CjYUoShTfKj0UAMoAJUhiSQXmhMXPx4/80stF1VGAoGnUTtNhyRALYqE9XdDo 5If24J/swYyQGe6pzXTpRf0Hp4tK+NJBblPw== Received: from cthulhu.stephaner.labo.int (10.2.16.1) by ICTDCCEXCH001.one.local (10.180.4.1) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21; Tue, 31 Jan 2023 09:52:17 +0100 Received: by cthulhu.stephaner.labo.int (Postfix, from userid 1001) id BC2461FDC9; Tue, 31 Jan 2023 09:52:16 +0100 (CET) References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <35e07b16-e635-a88c-f10b-cde0df05140b@freebsd.org> User-agent: mu4e 1.2.0; emacs 27.1 From: Stephane Rochoy To: CC: User Ngor , Warner Losh Subject: Re: Tooling Integration and Developer Experience In-Reply-To: <35e07b16-e635-a88c-f10b-cde0df05140b@freebsd.org> Date: Tue, 31 Jan 2023 09:52:16 +0100 Message-ID: <86zg9zw0fz.fsf@cthulhu.stephaner.labo.int> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Originating-IP: [10.2.16.1] X-ClientProxiedBy: ICTDCCEXCH001.one.local (10.180.4.1) To ICTDCCEXCH001.one.local (10.180.4.1) X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.980]; DMARC_POLICY_ALLOW(-0.50)[stormshield.eu,quarantine]; R_DKIM_ALLOW(-0.20)[stormshield.eu:s=signer]; R_SPF_ALLOW(-0.20)[+ip4:91.212.116.25]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[stormshield.eu:+]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; HAS_XOIP(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR] X-Rspamd-Queue-Id: 4P5f1t2S2Yz4556 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Mitchell Horne writes: > [Src] Needs Reviewer > https://reviews.freebsd.org/differential/query/65AoyPFlIhdE/ What is the purpose of the "Contributor Reviews (base)" project/group? Regards, -- St=C3=A9phane Rochoy O: Stormshield From nobody Tue Jan 31 09:23:59 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5fkl6Kcxz3bwtK for ; Tue, 31 Jan 2023 09:24:15 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5fkk34BXz49R3 for ; Tue, 31 Jan 2023 09:24:14 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua; dmarc=none Received: from [188.231.181.61] (helo=[10.2.1.122]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pMms0-000Lcg-R3 for freebsd-current@freebsd.org; Tue, 31 Jan 2023 11:24:04 +0200 Content-Type: multipart/alternative; boundary="------------HMJlOiKBZlKaBknX0M8zKVo1" Message-ID: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> Date: Tue, 31 Jan 2023 11:23:59 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 To: freebsd-current@freebsd.org References: Content-Language: uk-UA From: Oleksandr Kryvulia In-Reply-To: X-Spamd-Result: default: False [-3.28 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.977]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[shurik.kiev.ua]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4P5fkk34BXz49R3 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------HMJlOiKBZlKaBknX0M8zKVo1 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 31.01.23 09:52, parv/FreeBSD пише: > > Since around 2022-11, I am unable to change display brightness > of the display of a Framework laptop (Intel i5-1135G7, Iris > Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port) > & "acpi_video" (FreeBSD) kernel module. > > Earlier I was able to change brightness via "hw.acpi.video" MIB ... > > # - Need to have both "i915kms" & "acpi_video" modules already loaded. > # > # 20221120 - These MIBs do not work anymore as they are missing. > hw.acpi.video.lcd0.economy=10 > hw.acpi.video.lcd0.fullpower=40 > hw.acpi.video.lcd0.brightness=15 > > > ... now the whole of "hw.acpi.video" stub is missing. Nothing has > changed in terms of how/when "i915kms" & "acpi_video" are loaded (via > "kld_list" variable via "/etc/rc.conf" in that order). > > What am I missing? Does backlight(8) works for you? --------------HMJlOiKBZlKaBknX0M8zKVo1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 31.01.23 09:52, parv/FreeBSD пише:

Since around 2022-11, I am unable to change display brightness
of the display of a Framework laptop (Intel i5-1135G7, Iris
Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port)
& "acpi_video" (FreeBSD) kernel module.

Earlier I was able to change brightness via "hw.acpi.video" MIB ...

# - Need to have both "i915kms" & "acpi_video" modules already loaded.
#
# 20221120 - These MIBs do not work anymore as they are missing.
hw.acpi.video.lcd0.economy=10
hw.acpi.video.lcd0.fullpower=40
hw.acpi.video.lcd0.brightness=15


... now the whole of "hw.acpi.video" stub is missing. Nothing has
changed in terms of how/when "i915kms" & "acpi_video" are loaded (via
"kld_list" variable via "/etc/rc.conf" in that order).

What am I missing?

Does backlight(8) works for you?

--------------HMJlOiKBZlKaBknX0M8zKVo1-- From nobody Tue Jan 31 12:33:02 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5kwm5yqXz3cP02 for ; Tue, 31 Jan 2023 12:33:12 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5kwm3LT9z3HHn for ; Tue, 31 Jan 2023 12:33:11 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id E362D8929A; Tue, 31 Jan 2023 12:33:03 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 30VCX3Uk079925 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 31 Jan 2023 12:33:03 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 30VCX2qX079924; Tue, 31 Jan 2023 12:33:02 GMT (envelope-from phk) Message-Id: <202301311233.30VCX2qX079924@critter.freebsd.dk> To: Oleksandr Kryvulia cc: freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 In-reply-to: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> From: "Poul-Henning Kamp" References: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <79922.1675168382.1@critter.freebsd.dk> Date: Tue, 31 Jan 2023 12:33:02 +0000 X-Rspamd-Queue-Id: 4P5kwm3LT9z3HHn X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N -------- Oleksandr Kryvulia writes: > Does backlight(8) works for you? Speaking of backlight(8): On my T14s, I see the following: If I set the light with backlight(8) to something, say 30%, and then change the power-situation, for instance by unplugging the charger, the backlight goes up to 100%. If I then try to set it back to 30% with backlight(8), nothing happens. If I use any other value, for instance 31%, backlight(8) does the job. I guess somewhere some code says "It's always 30%, just return" ? This might be a bit confusing if you have the intensity encoded in some script, which then "sometimes does not work"... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Tue Jan 31 12:52:56 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5lMj53j0z3cQkK for ; Tue, 31 Jan 2023 12:53:05 +0000 (UTC) (envelope-from meka@tilda.center) Received: from c3po.tilda.center (c3po.tilda.center [108.61.164.129]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5lMh4NrCz3Jyg for ; Tue, 31 Jan 2023 12:53:04 +0000 (UTC) (envelope-from meka@tilda.center) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tilda.center header.s=c3po header.b=qZ5kH6Yl; spf=pass (mx1.freebsd.org: domain of meka@tilda.center designates 108.61.164.129 as permitted sender) smtp.mailfrom=meka@tilda.center; dmarc=pass (policy=reject) header.from=tilda.center Received: from [192.168.111.186] (meka.rs [109.93.255.137]) by c3po.tilda.center (Postfix) with ESMTPSA id C9E0F16547 for ; Tue, 31 Jan 2023 13:52:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tilda.center; s=c3po; t=1675169532; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9PVZzSdguV0rpNoHGtmzxggVkZyFWnjcnpBCb8GnNtQ=; b=qZ5kH6YlJgbjK0FlA1YgMfHrplrhAmb5rCTeA8KMWt4F3/vDaAfQYkRIMVKbXWC3MAz3hE MfvD1mN2cU56kJbbcrY/ShbR86q/9nMYssaA098TQIftWiEjsia7THWdf0mogM/VqmwmrL vCASj1GrQaWO9osBp1ornAOcX7DOPsk= Message-ID: Date: Tue, 31 Jan 2023 13:52:56 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 Content-Language: en-US To: freebsd-current@freebsd.org References: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> <202301311233.30VCX2qX079924@critter.freebsd.dk> From: =?UTF-8?Q?Goran_Meki=c4=87?= In-Reply-To: <202301311233.30VCX2qX079924@critter.freebsd.dk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[tilda.center,reject]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[tilda.center:s=c3po]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[tilda.center:+]; ASN(0.00)[asn:20473, ipnet:108.61.164.0/22, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4P5lMh4NrCz3Jyg X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 1/31/23 13:33, Poul-Henning Kamp wrote: > Speaking of backlight(8): On my T14s, I see the following: > > If I set the light with backlight(8) to something, say 30%, and then > change the power-situation, for instance by unplugging the charger, > the backlight goes up to 100%. > > If I then try to set it back to 30% with backlight(8), nothing happens. > > If I use any other value, for instance 31%, backlight(8) does the job. > > I guess somewhere some code says "It's always 30%, just return" ? > > This might be a bit confusing if you have the intensity encoded in > some script, which then "sometimes does not work"... > Actually, I think the problem is a bit deeper, as yet-to-come version of DRM 5.14 suffers from the similar problem: https://github.com/freebsd/drm-kmod/pull/226#issuecomment-1400399357. TL;DR: new DRM code sets brightness to 0% while backlight(8) reports 100%. Regards, meka From nobody Tue Jan 31 12:55:26 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5lQh5GqHz3cRKm for ; Tue, 31 Jan 2023 12:55:40 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5lQh1rChz3KyB for ; Tue, 31 Jan 2023 12:55:40 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1675169731; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=m2RQmFShHwOMF0MNufigIXiW2nnhyDyfEIAxyI4GG3w=; b=TgNudU+9ah3jkpzNsO3wrZA/BGq2Jxi7Pbuq8CbQ04G6TjB4JcysmiIsUiXCcNOu0t1H0V GrBIU7JXXxjsY10qGm64RkMb11U7DAeaI+JW3LCK9YMl3N+ZCRjMGbVDmNsOCFR/v+3bpa RsFUCcZdp8w6kXlhw9h6nGxpGdMiHyQ= Received: from amy.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 24107037 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 31 Jan 2023 12:55:31 +0000 (UTC) Date: Tue, 31 Jan 2023 13:55:26 +0100 From: Emmanuel Vadot To: "Poul-Henning Kamp" Cc: Oleksandr Kryvulia , freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 Message-Id: <20230131135526.a3e96ee0ac8479521a99514b@bidouilliste.com> In-Reply-To: <202301311233.30VCX2qX079924@critter.freebsd.dk> References: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> <202301311233.30VCX2qX079924@critter.freebsd.dk> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4P5lQh1rChz3KyB X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, 31 Jan 2023 12:33:02 +0000 "Poul-Henning Kamp" wrote: > -------- > Oleksandr Kryvulia writes: > > > Does backlight(8) works for you? > > Speaking of backlight(8): On my T14s, I see the following: > > If I set the light with backlight(8) to something, say 30%, and then > change the power-situation, for instance by unplugging the charger, > the backlight goes up to 100%. > > If I then try to set it back to 30% with backlight(8), nothing happens. > > If I use any other value, for instance 31%, backlight(8) does the job. > > I guess somewhere some code says "It's always 30%, just return" ? > > This might be a bit confusing if you have the intensity encoded in > some script, which then "sometimes does not work"... Smells like https://cgit.freebsd.org/src/commit/sys/dev/backlight/backlight.c?id=e26ef41f79902991c772b59927c721aa7fa5fc64 It's not in 13.1 but will be in 13.2 > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Emmanuel Vadot From nobody Tue Jan 31 12:58:25 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5lV40Xgbz3cRp7 for ; Tue, 31 Jan 2023 12:58:36 +0000 (UTC) (envelope-from qroxana@protonmail.com) Received: from mail-40141.protonmail.ch (mail-40141.protonmail.ch [185.70.40.141]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5lV26pVfz3M6D; Tue, 31 Jan 2023 12:58:34 +0000 (UTC) (envelope-from qroxana@protonmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=vLqAv014; spf=pass (mx1.freebsd.org: domain of qroxana@protonmail.com designates 185.70.40.141 as permitted sender) smtp.mailfrom=qroxana@protonmail.com; dmarc=pass (policy=quarantine) header.from=protonmail.com Date: Tue, 31 Jan 2023 12:58:25 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1675169912; x=1675429112; bh=hjXbB4Ds1XzN4hg4PsKQ4JC5W0Sqt724tJnrAoGPR1g=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=vLqAv014hHpc9xRQoXLYLgPjyFth9N5fkhn2fhjeu05Kms0VkNKUgjlf2BtO5zMrc dV3oG7Am3gg+sK8vzFCxl0MBiV3DpNIBXD1+5qi2Z/WzJm6AvuPgHyPTudtLXRCXbt O+ZLfQ8yp1GNSqJ2Nao66RRy9xcpBeQ0HZmy2q5UF1mIkEsk6uq7l6+xdZ1waQWiLW U1pV6VxurrDqs5Db3a5/wEEu1J3Z2CZYsjHA86KyVkTaUHBrEzXl62n1tL33Xj+zfh OYtFK77wiaVv1NB3zWbaRZIUi3A4B4Cqx9T/eZdt/igk0blan53jzZYG0adrdHcsAf qsWUUtraeD12w== To: "freebsd-current@freebsd.org" From: qroxana Cc: Dimitry Andric Subject: Re: buildworld failed after deleting /usr/obj Message-ID: In-Reply-To: <44ybMtpAl4lOcN0PqhC63MaFz0G7l0mD_6RBWLaFNqw7gs2uCbYRhxwcvOv5chBBPH3vSQetkVbwtxWZR14fJyWIMZZet8yU_yiMPa7J_yQ=@protonmail.com> References: <7cKQCx9PEwnnJE5MatS6g5KkKh5prIZTrTlqGL2RfM7Z4TDJGCfEATg9ejghBWDhx7WqDtVpxAA6wEisDAP2Y6c8g-ht2KbUW4YN0eek43g=@protonmail.com> <3CCFF1C8-D618-453F-8412-3D65F551C43C@FreeBSD.org> <44ybMtpAl4lOcN0PqhC63MaFz0G7l0mD_6RBWLaFNqw7gs2uCbYRhxwcvOv5chBBPH3vSQetkVbwtxWZR14fJyWIMZZet8yU_yiMPa7J_yQ=@protonmail.com> Feedback-ID: 29996633:user:proton List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.48 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.96)[-0.959]; NEURAL_HAM_SHORT(-0.52)[-0.521]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail3]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ZERO(0.00)[0]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; DKIM_TRACE(0.00)[protonmail.com:+]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.141:from] X-Rspamd-Queue-Id: 4P5lV26pVfz3M6D X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N ----- Original Message ------- On Sunday, January 29th, 2023 at 3:06 PM, qroxana = wrote: > It appears buildworld doesn't create the obj directory for usr.bin/clang/= llvm-objcopy in stage 2.2 after this commit. >=20 > commit adc3c128c6603054586a993d117e5dd808deac17 > Author: John Baldwin jhb@FreeBSD.org >=20 > AuthorDate: Fri Nov 18 20:12:28 2022 -0800 > Commit: John Baldwin jhb@FreeBSD.org >=20 > CommitDate: Fri Nov 18 20:12:28 2022 -0800 >=20 > src.opts.mk: Require C++20 for C++ support. >=20 > libc++ requires C++20, so mark C++ (MK_CXX) as broken if the compiler > does not support C++20. >=20 > Reviewed by: emaste > Differential Revision: https://reviews.freebsd.org/D36893 >=20 > diff --git a/share/mk/src.opts.mk b/share/mk/src.opts.mk > index f69208f21556..5089a034350d 100644 > --- a/share/mk/src.opts.mk > +++ b/share/mk/src.opts.mk > @@ -348,6 +348,11 @@ __DEFAULT_YES_OPTIONS+=3DOPENMP > __DEFAULT_NO_OPTIONS+=3DOPENMP > .endif >=20 > +# libc++ requires C++20 > +.if !${COMPILER_FEATURES:Mc++20} > +BROKEN_OPTIONS+=3DCXX > +.endif > + > .include >=20 >=20 > # Sorry for the noise, this has been fixed by this commit. commit ac4c695ad61e81d00cff2a03202a4afe94a92513 Author: Ed Maste AuthorDate: Wed Nov 16 09:20:39 2022 -0500 Commit: Ed Maste CommitDate: Thu Jan 26 21:13:16 2023 -0500 Retire WITHOUT_CXX option =20 Several important base system components are written in C++, and the WITHOUT_CXX option produced a system that was not fully functional. Just accept this, and remove the option to build without C++ support. =20 This reverts commit adc3c128c6603054586a993d117e5dd808deac17. =20 Reviewed by: brooks, kevans, jhb (earlier) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D33108 From nobody Tue Jan 31 13:06:47 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5lgh2p3tz3cT04 for ; Tue, 31 Jan 2023 13:06:56 +0000 (UTC) (envelope-from qroxana@protonmail.com) Received: from mail-4318.protonmail.ch (mail-4318.protonmail.ch [185.70.43.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5lgg4KNLz3P0y for ; Tue, 31 Jan 2023 13:06:55 +0000 (UTC) (envelope-from qroxana@protonmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=q3irIR5h; spf=pass (mx1.freebsd.org: domain of qroxana@protonmail.com designates 185.70.43.18 as permitted sender) smtp.mailfrom=qroxana@protonmail.com; dmarc=pass (policy=quarantine) header.from=protonmail.com Date: Tue, 31 Jan 2023 13:06:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1675170413; x=1675429613; bh=GPbfwPmpv3moFJdofDTERq2gnz7fz5p9+hH6YjTdXis=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=q3irIR5hcFq/5zHoh/Sk/SEFuEbp7mroUogHNNA98EHxBOM6YscYBtGAw1uszQ6pl vwBZjiV0Knbp2OvSL94evChYKFYYkBp3HlDAh8Urc3SLPAi+PbiorGg+GNULkF5hlU cDDu07TSsJxw4jMbsAISUFFDKJWisbOxGpK8QPBY+fkKRckzJisfmhGS+P2Ri7g1B7 o5Ew8kaub+KiQpSklig+hVysqUiRSvYzFHhx7yAHsoyzpDEM3jc/LmqRLoZVI1J2zh cHmdJoyhcv6DvAYen7RSIkiTdw30OS9C46tapqpyw9Q0RqP3jmIs12joJGVwHIGc2A bNhldhOup/22Q== To: Rick Macklem From: qroxana Cc: "freebsd-current@freebsd.org" Subject: Re: sbin/mount: failed to mount NFS root Message-ID: In-Reply-To: References: Feedback-ID: 29996633:user:proton List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.995]; NEURAL_HAM_SHORT(-0.51)[-0.506]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24:c]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail3]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[protonmail.com:+]; FROM_HAS_DN(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4P5lgg4KNLz3P0y X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N ------- Original Message ------- On Monday, January 30th, 2023 at 3:08 PM, Rick Macklem wrote: > I think this was fixed by a commit yesterday. >=20 > rick > Thanks Rick. Yes, it has been fixed. commit ad055467bec35885dc3eff2f4dd765f5b2f53259 Author: Kirk McKusick AuthorDate: Sun Jan 29 15:12:48 2023 -0800 Commit: Kirk McKusick CommitDate: Sun Jan 29 15:14:43 2023 -0800 Fix for getmntpoint(3) when checking for NFS mount points. =20 Only attempt to add /dev/ to f_mntfromname names that result in a valid character device. =20 MFC after: 1 week Reported by: Bjoern A. Zeeb Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D37907 From nobody Tue Jan 31 13:09:39 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5lks42xzz3cTHZ for ; Tue, 31 Jan 2023 13:09:41 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5lks2qTqz3Q0y for ; Tue, 31 Jan 2023 13:09:41 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id BACA88929A; Tue, 31 Jan 2023 13:09:39 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 30VD9d4R010473 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 31 Jan 2023 13:09:39 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 30VD9djG010472; Tue, 31 Jan 2023 13:09:39 GMT (envelope-from phk) Message-Id: <202301311309.30VD9djG010472@critter.freebsd.dk> To: Emmanuel Vadot cc: Oleksandr Kryvulia , freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 In-reply-to: <20230131135526.a3e96ee0ac8479521a99514b@bidouilliste.com> From: "Poul-Henning Kamp" References: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> <202301311233.30VCX2qX079924@critter.freebsd.dk> <20230131135526.a3e96ee0ac8479521a99514b@bidouilliste.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10470.1675170579.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Tue, 31 Jan 2023 13:09:39 +0000 X-Rspamd-Queue-Id: 4P5lks2qTqz3Q0y X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N -------- Emmanuel Vadot writes: > > > Does backlight(8) works for you? > > = > > Speaking of backlight(8): On my T14s, I see the following: > > = > > If I set the light with backlight(8) to something, say 30%, and then > > change the power-situation, for instance by unplugging the charger, > > the backlight goes up to 100%. > > = > > If I then try to set it back to 30% with backlight(8), nothing happens= . > > = > > If I use any other value, for instance 31%, backlight(8) does the job. > > = > > I guess somewhere some code says "It's always 30%, just return" ? > > = > > This might be a bit confusing if you have the intensity encoded in > > some script, which then "sometimes does not work"... > > Smells like > https://cgit.freebsd.org/src/commit/sys/dev/backlight/backlight.c?id=3De= 26ef41f79902991c772b59927c721aa7fa5fc64 > It's not in 13.1 but will be in 13.2 I'm running 14.0-CURRENT #0 main-n260119-7f2109f240c2: Mon Jan 16 22:54:18 UTC 2023 -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From nobody Tue Jan 31 13:20:55 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5lzt0vrFz3cVYs for ; Tue, 31 Jan 2023 13:20:58 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5lzs5xhgz3jhN for ; Tue, 31 Jan 2023 13:20:57 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1675171256; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qh5iTwkdoaItg6EbBKCK+7r+csWDEyhOEStguQ82Gpo=; b=DtGcQfQCkQrcp2PB85u2Qont9wWUw6M2nW7KyCo8emEPkZLgR6uNBde8mIqGWDiDA2FOAV oKAljgO0AKLOoTABV9WMtt0LjRPFnAaeomtu/0VKyP7dYP5DnsV1pCKlzcGY2zIyuGdRHD ZoE3IUNp6qZtKfp5r4bLa/PeHuwFW2Y= Received: from amy.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 62673fb9 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 31 Jan 2023 13:20:56 +0000 (UTC) Date: Tue, 31 Jan 2023 14:20:55 +0100 From: Emmanuel Vadot To: "Poul-Henning Kamp" Cc: Oleksandr Kryvulia , freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 Message-Id: <20230131142055.aa32f00d89d286053513348d@bidouilliste.com> In-Reply-To: <202301311309.30VD9djG010472@critter.freebsd.dk> References: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> <202301311233.30VCX2qX079924@critter.freebsd.dk> <20230131135526.a3e96ee0ac8479521a99514b@bidouilliste.com> <202301311309.30VD9djG010472@critter.freebsd.dk> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4P5lzs5xhgz3jhN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, 31 Jan 2023 13:09:39 +0000 "Poul-Henning Kamp" wrote: > -------- > Emmanuel Vadot writes: > > > > > Does backlight(8) works for you? > > > > > > Speaking of backlight(8): On my T14s, I see the following: > > > > > > If I set the light with backlight(8) to something, say 30%, and then > > > change the power-situation, for instance by unplugging the charger, > > > the backlight goes up to 100%. > > > > > > If I then try to set it back to 30% with backlight(8), nothing happens. > > > > > > If I use any other value, for instance 31%, backlight(8) does the job. > > > > > > I guess somewhere some code says "It's always 30%, just return" ? > > > > > > This might be a bit confusing if you have the intensity encoded in > > > some script, which then "sometimes does not work"... > > > > Smells like > > https://cgit.freebsd.org/src/commit/sys/dev/backlight/backlight.c?id=e26ef41f79902991c772b59927c721aa7fa5fc64 > > It's not in 13.1 but will be in 13.2 > > I'm running > > 14.0-CURRENT #0 main-n260119-7f2109f240c2: Mon Jan 16 22:54:18 UTC 2023 What does backlight reports after you've unplugged the AC adaptor ? -- Emmanuel Vadot From nobody Tue Jan 31 13:24:43 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5m4F4Bmwz3cW4n for ; Tue, 31 Jan 2023 13:24:45 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5m4F3DHnz3l48 for ; Tue, 31 Jan 2023 13:24:45 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id C1C448929A; Tue, 31 Jan 2023 13:24:43 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 30VDOhKU024327 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 31 Jan 2023 13:24:43 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 30VDOhS9024326; Tue, 31 Jan 2023 13:24:43 GMT (envelope-from phk) Message-Id: <202301311324.30VDOhS9024326@critter.freebsd.dk> To: Emmanuel Vadot cc: Oleksandr Kryvulia , freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 In-reply-to: <20230131142055.aa32f00d89d286053513348d@bidouilliste.com> From: "Poul-Henning Kamp" References: <6a997703-6f13-716d-d38d-1a2b910d52ec@shurik.kiev.ua> <202301311233.30VCX2qX079924@critter.freebsd.dk> <20230131135526.a3e96ee0ac8479521a99514b@bidouilliste.com> <202301311309.30VD9djG010472@critter.freebsd.dk> <20230131142055.aa32f00d89d286053513348d@bidouilliste.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24324.1675171483.1@critter.freebsd.dk> Date: Tue, 31 Jan 2023 13:24:43 +0000 X-Rspamd-Queue-Id: 4P5m4F3DHnz3l48 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N -------- Emmanuel Vadot writes: > What does backlight reports after you've unplugged the AC adaptor ? I cant make that experiment right now, I also ethernet through that connector, but I'll do it later today. But speaking of what backlight reports: critter phk> backlight brightness: 0 critter phk> backlight 10 critter phk> backlight brightness: 9 critter phk> backlight 20 critter phk> backlight brightness: 19 critter phk> backlight 30 critter phk> backlight brightness: 29 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Tue Jan 31 15:46:27 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5qCq1hDMz3bLZ0 for ; Tue, 31 Jan 2023 15:46:31 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5qCq12sLz3xs7; Tue, 31 Jan 2023 15:46:31 +0000 (UTC) (envelope-from mhorne@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675179991; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=k0mn+AhYrYFvCZPqwgKmCnrF8EVzgaPPef8Pp2j+SLU=; b=Ytd3b5M58L8czCCRQ9GSI2OenwjyJaIU0U0AWMg6WtqwVmnZwLprs1Utwu8/0+nBzWOdRr SKwZ8C1xEinOvUTCBbyR7gWbL0THgNKAEXtu5OttnsCWtafmJylivVwkosgZH1J277zk7f bIHZCoodMxjcLTI2jZNcTu3T4IaRP7cSokq1BcCG+spOgNnr8BfrUjBGSomoShIxuWyvaH Qgp/NvgwTuDxSdGaQWUJZQ7imSTk5n9XUrFhv7aNfhNB1BjOtsj1jgHzS/y36EWR49dR1S b4KR0IbzYXn+OgZQSMmHuow+wxPbWkGcflgS/Fo+5nHTSK8xcwRzwGK4Qlei1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675179991; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=k0mn+AhYrYFvCZPqwgKmCnrF8EVzgaPPef8Pp2j+SLU=; b=m6SmyZcwoEUjN7Fsx8hcc5Lm53sVpoUCMAtG/jRvc05CJ/yn4WxE3ss/YonnAlWyMeC7+z Lnj6pnVv81quycUit7GFQmCed0UH9SI4zYbm+WRE90YAZBCiWvHsIrS+8qnAVmJ8aN0u/1 PNDutf88R51x1mcu8X+wuccCn1F6OnXNJ4Tv2zWsrHoCXz7TPjxpM7rZmsfR4Y+lXpBZY3 vqB/v8RrpanFSvs5gchH25KC0ZgDeTw7eo1ME/+OzYjoWP47dx6PEeHPjb0jkB7kHzSwOZ 9+mhYELrEsw/iGy5E+npdMOLoG2SCSNnCFvMuM6jGNmkDUTzK/PpW8eW9vQELA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675179991; a=rsa-sha256; cv=none; b=F8MQn62tGKLRTQXpooBJPRPRHEgzB3pT0r0ZHAqJJF4d9H8sG0uJMzSp3DMCqbZJ5JGh/G S3Zfu3v0SpEwYlIitpx3dF5Yzod0LBZmAl7/oZlnjfSd6FDfqpqSdm9dGJTDrZZxa3ech6 sdMJqdl6N0FkXfBbeKhMfsXtRqmwdxRKDdoLjs70jUqolurU5y/9a5npiZOMi8tXSL5G9x Bf+A9+bKzSDEVYfiuBGid8pl8FWkVyUrAIFGeC3jPxw8xTQV5Ny2R4ETEtkmsjfSonAsU+ HSkL+3ZtudJF/UJ+LMtBtoBrUcTpbOXzGpCQi9SY3BmU4FBHjfAy9jqLH02LgA== Received: from [192.168.1.151] (host-173-212-76-127.public.eastlink.ca [173.212.76.127]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: mhorne) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P5qCp32zHzcBt; Tue, 31 Jan 2023 15:46:30 +0000 (UTC) (envelope-from mhorne@freebsd.org) Message-ID: Date: Tue, 31 Jan 2023 11:46:27 -0400 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Tooling Integration and Developer Experience Content-Language: en-CA To: Stephane Rochoy , freebsd-current@freebsd.org Cc: User Ngor , Warner Losh References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <35e07b16-e635-a88c-f10b-cde0df05140b@freebsd.org> <86zg9zw0fz.fsf@cthulhu.stephaner.labo.int> From: Mitchell Horne In-Reply-To: <86zg9zw0fz.fsf@cthulhu.stephaner.labo.int> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 1/31/23 04:52, Stephane Rochoy wrote: > > Mitchell Horne writes: > >> [Src] Needs Reviewer >> https://reviews.freebsd.org/differential/query/65AoyPFlIhdE/ > > What is the purpose of the "Contributor Reviews (base)" > project/group? > > Regards, > -- > Stéphane Rochoy > O: Stormshield > It is a group ("Project") that anyone can join to receive notifications whenever the group is tagged. Groups can be added as a reviewer on a revision, for example. There is a Herald rule to automatically add this Contributor Reviews group as a subscriber to any src revisions that have no reviewers specified. This makes it an imperfect search criteria for "reviews which are accepted but not authored by a FreeBSD committer". Mitchell From nobody Tue Jan 31 17:47:33 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5svq4TYcz3brgB for ; Tue, 31 Jan 2023 17:47:51 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5svq418Dz4CWJ for ; Tue, 31 Jan 2023 17:47:51 +0000 (UTC) (envelope-from theraven@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675187271; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GQGcu02RxgGjMFnCrFTtOEMiQGCTBduBu/lCuTNWlo0=; b=hTPmVon0zp4RusBtTE6sGvLpsru0xyTso+l2pc9V+Du8sq1lpP5br2k3Hz2azHypKVqLzJ DbFegWKyjhQHUIMgeq5UKoTRUXkjpxJVylaeqa0u1Ra7dwmt51WwLRs0WWYjd231mCuQ0i UXpj/C1OpF6qIdTvd+640D16aGTY3G6XCRrugPDRnfMclTFgAGSJhegEbrvt5bU/QpAb5e qoNhFcuNtwBasrFmlZI4CqP5ibH8Rd1ynQfKhQmXWq996FmvUFLpVv7/bdq5kHNjVEML+g h/HDzAMarZQy/ST0DN4kZ6LcqDToBUg5Mb2pgxsLSht2SegwenBV7I1imqsh6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675187271; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GQGcu02RxgGjMFnCrFTtOEMiQGCTBduBu/lCuTNWlo0=; b=x2Nkni8g0PmHzpw8WFKs8rNo4AIuvEs0DF6xLKAbN5i2oT/R6RD9zFAazvZ5S2C+l6v/dY fRyHadzVyLa21OJNCu87lk1Pj3eyHsX8/lYMY0Xw1tnpeGCDYGqDBvH5Az/a5up4KM1TXb IDhSeL1qGYMygO6q9Xnpp6n5Sv1m+4S1Ouu6SI35I2AsJgLAS5aX9+NMUoMNiIbHpjc+q1 fPkw7nXRqN+7nrY/Wz8xNZUdsqNx+yKtnlQu2PwwhJKtHpIoxocPYcdtXs7+aD51fDHahQ 6z2bvw13hnDa50wMMubJTWjERDEXjxsIyMqBPKqO/bHHpUJj3Kvr5TMhveej7Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675187271; a=rsa-sha256; cv=none; b=f7z0URrTgNUAAPXMeLkjFCjSwBHYYHsnMnwZJvrMmFf6q+MCRtx+jYtZlRnImMXqfh7xDE Pvu3wAZYlhBdfNGg6ZxlfnZTa4yPBK1wSaQKDlY8aAF1qG3+luANf1rGICl7ZY1Z0k63o6 glY0c7dJdSq92GsYZwmfp9r9zK20D7zBNLD+gTx8tsGDbai01sA7SZcW3b2NubeusjadZ2 uPNYkta3kxFWB73vxGraz3QN6F1lG4ES9l71kBvy77JmEbi7jAVHiErfLksvFe2MtLysKp lDzwv4G7hniSstIQRTJl/wmzkc1qw9unER4c58Qs8PGNVb5wnDrKYcqdC0f/LQ== Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P5svq2wjlzg2g for ; Tue, 31 Jan 2023 17:47:51 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host81-156-200-108.range81-156.btcentralplus.com [81.156.200.108]) by smtp.theravensnest.org (Postfix) with ESMTPSA id 15FBE1A05 for ; Tue, 31 Jan 2023 17:47:35 +0000 (GMT) Message-ID: Date: Tue, 31 Jan 2023 17:47:33 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: GitHub Code Search [Re: Tooling Integration and Developer Experience] Content-Language: en-GB To: freebsd-current@freebsd.org References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> From: David Chisnall In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 30/01/2023 21:39, Yetoo wrote: > > If github is going to be considered for issue tracking I just want to > say, after having extensively using it for issue tracking, it tends to > be difficult to find an issue if the exact title isn't entered and many > duplicate reports are made as a result. Code search sucks and doesnt > show you the multiple places in a file where a match was made so a user > may be left wondering if code exists or not, but this doesn't seem to be > germane given this is about issue tracking. Which search are you using? The old GitHub search is not great, but cs.github.com has replaced local search for me in the FreeBSD tree. It's not *quite* as good as fxr, but it's close. For example, searching for sys_cap_enter: https://cs.github.com/?scopeName=All+repos&scope=&q=sys_cap_enter+repo%3Afreebsd%2Ffreebsd-src+ David From nobody Tue Jan 31 21:43:39 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5z844Nm0z3cNWs for ; Tue, 31 Jan 2023 21:43:48 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5z8363gmz3kyY for ; Tue, 31 Jan 2023 21:43:47 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:14f8:200::1 is neither permitted nor denied by domain of pi@freebsd.org) smtp.mailfrom=pi@freebsd.org; dmarc=none Received: from pi by home.opsec.eu with local (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pMyPj-000HtJ-1r; Tue, 31 Jan 2023 22:43:39 +0100 Date: Tue, 31 Jan 2023 22:43:39 +0100 From: Kurt Jaeger To: User Ngor Cc: freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Message-ID: References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <5207abe0-9c2b-1424-ac58-d52e97ba7413@antonovs.family> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5207abe0-9c2b-1424-ac58-d52e97ba7413@antonovs.family> X-Spamd-Result: default: False [-3.04 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.938]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; DMARC_NA(0.00)[freebsd.org]; ARC_NA(0.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; FREEFALL_USER(0.00)[pi]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4P5z8363gmz3kyY X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hi! > > > This can be as easy as moving everything into Phabricator. > > There's the issue that Phabricator itself is no longer supported > > upstream: [...] > > https://we.phorge.it/ > Should be no harder than regular update. They even have a HOWTO > https://we.phorge.it/w/installation_and_setup/update_from_phabricator/ So, as a step 0 we would need a phorge port... > 1. Upgrade to Phorge > 2. Setup Maniphest for bugs and tasks > 3. Migrate bugs into Maniphest > 4. Enable Harbormaster (Build/CI) - this requires coordination with > whoever is working on pre-commit CI. [...] > Infra operations are hard, and I have experience with it. I'd be happy to > help. Do you think you can provide a phorge port ? -- pi@opsec.eu +49 171 3101372 Now what ? From nobody Tue Jan 31 22:03:28 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P5zZx2BPZz3cR1T for ; Tue, 31 Jan 2023 22:03:37 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.evolve.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5zZw4c2lz3rsq; Tue, 31 Jan 2023 22:03:36 +0000 (UTC) (envelope-from grembo@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 7925f828; Tue, 31 Jan 2023 22:03:28 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id 74fb6f0d (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Tue, 31 Jan 2023 22:03:28 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: Tooling Integration and Developer Experience From: Michael Gmelin In-Reply-To: Date: Tue, 31 Jan 2023 23:03:28 +0100 Cc: User Ngor , freebsd-current@freebsd.org Message-Id: References: To: Kurt Jaeger X-Mailer: iPhone Mail (20B110) X-Rspamd-Queue-Id: 4P5zZw4c2lz3rsq X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On 31. Jan 2023, at 22:44, Kurt Jaeger wrote: >=20 > =EF=BB=BFHi! >=20 >>>> This can be as easy as moving everything into Phabricator. >>> There's the issue that Phabricator itself is no longer supported >>> upstream: > [...] >>> https://we.phorge.it/ >=20 >> Should be no harder than regular update. They even have a HOWTO >> https://we.phorge.it/w/installation_and_setup/update_from_phabricator/ >=20 > So, as a step 0 we would need a phorge port... >> 1. Upgrade to Phorge >> 2. Setup Maniphest for bugs and tasks >> 3. Migrate bugs into Maniphest >> 4. Enable Harbormaster (Build/CI) - this requires coordination with >> whoever is working on pre-commit CI. > [...] >> Infra operations are hard, and I have experience with it. I'd be happy to= >> help. >=20 > Do you think you can provide a phorge port ? >=20 I created the phabricator port in 2014 and have been maintaining it since th= en. I=E2=80=99m also subscribed to phorge, so technically I could also maint= ain a phorge port (I also have many years of experience in maintaining and u= sing phabricator instances, also fixing bugs and adding some local features)= . So far I haven=E2=80=99t created a port for phorge, as progress on it seemed= very slow (and many of the changes were also merged into phab) and therefor= e there was little incentive to migrate any of the instances I maintain. AFAIK FreeBSD=E2=80=99s phabricator instance is not based on the port and us= es custom patches anyway (I can=E2=80=99t remember having a single communica= tion with phabricator-admin regarding the port), therefore having a phorge p= ort most likely isn=E2=80=99t a pre-condition for the project to use it. Best=20 > --=20 > pi@opsec.eu +49 171 3101372 Now what ? >=20 From nobody Wed Feb 1 06:05:30 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P6BHC2j85z3cFSX for ; Wed, 1 Feb 2023 06:05:43 +0000 (UTC) (envelope-from yetoohappy@gmail.com) Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P6BHC0wqRz4cVR; Wed, 1 Feb 2023 06:05:43 +0000 (UTC) (envelope-from yetoohappy@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62a.google.com with SMTP id dr8so26642324ejc.12; Tue, 31 Jan 2023 22:05:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GLSf33TRSxKqdMlYOhwnRa+j6xSiBtOSwH92G7Doro4=; b=QriIVHwc0ZmwfECeO4VNv+Qv+H8K9QQZUKccLzZHghR6mbP8xm9OynjtbKEBTkwKn3 540ySgyQSCSO+FwwYBEbUbsGIBgwSyVY0VDNfY6JljxpPhsOGQ/7VUdW/5C9PgEy3pZB NWqWLb3YuEdKXIFNXdh2ZOPg9DcBG4u/tTyFcREnQlCTv/Ms7dtndHU16RAhrsrih1Js KejkodTQg/YpDbuaFUs95yLuPly7WfRh3Lbxu2wWN7l42I3b6a5CvyyuUfclwHJBX7sR UoiGwlE4+fCjyOmklwBnbFLM4nsJv1N3ACj/NfwOnRU1humWHVXIYMNVt5gDfUNBC6pT oDuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GLSf33TRSxKqdMlYOhwnRa+j6xSiBtOSwH92G7Doro4=; b=oYMEtUQV88rvfIWicyh9AlLCoHHBfAgSTw2UwP3NLrrlpyZkDTda9vMbZUmMceYA4Q zKvJ4RZt8SSc4E2sjluiLEpnsK13jZmbA8fusPfSlK/UxnmumxEAL/j6m8cAcpBU+vIg zMZD1a1FYKTXLWDcVPr27JmrrHbcVwjKJ8lQb68X6E6Vt+FptmyvPq2LpNM4lVrXjju9 umJiRWHms13VCZrgnjknvs612UHq7xPxECQsHTLZJX43wshCRhNDmJJhXrjObqSud3oA i4B71XBY37ywFdJrX3fNgDW+/Muzc/GtrP3oEi+NjL09l4Na81YBgFcThTqYmsdTEGhA /pCw== X-Gm-Message-State: AO0yUKX5qBRgtzuGSOHIU/UqCRYZfz5H8I3dC+Dxl7mqTPMB/sUenmTP AvW36fsXyLWhEPKLgkKVAhcFulWicEnrOmTnNEaoiDmq X-Google-Smtp-Source: AK7set+J7nMe3ucaOighFh/mNLHFAibeMi2y/9IhW0j+5L8rO3z1zaGo4pLTJYAK9r0F5iH2z6GWVMl65VROr5h4m4U= X-Received: by 2002:a17:906:3544:b0:86c:3586:96f1 with SMTP id s4-20020a170906354400b0086c358696f1mr343878eja.137.1675231541338; Tue, 31 Jan 2023 22:05:41 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> In-Reply-To: From: Yetoo Date: Tue, 31 Jan 2023 22:05:30 -0800 Message-ID: Subject: Re: GitHub Code Search [Re: Tooling Integration and Developer Experience] To: David Chisnall Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4P6BHC0wqRz4cVR X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, Jan 31, 2023, 9:47 AM David Chisnall wrote: > > On 30/01/2023 21:39, Yetoo wrote: > > > > If github is going to be considered for issue tracking I just want to > > say, after having extensively using it for issue tracking, it tends to > > be difficult to find an issue if the exact title isn't entered and many > > duplicate reports are made as a result. Code search sucks and doesnt > > show you the multiple places in a file where a match was made so a user > > may be left wondering if code exists or not, but this doesn't seem to be > > germane given this is about issue tracking. > > Which search are you using? The old GitHub search is not great, but > cs.github.com has replaced local search for me in the FreeBSD tree. > It's not *quite* as good as fxr, but it's close. > > For example, searching for sys_cap_enter: > > https://cs.github.com/?scopeName=All+repos&scope=&q=sys_cap_enter+repo%3Afreebsd%2Ffreebsd-src+ > > David Clicking that link greets me with a login screen and a requirement to join a waitlist. Yes, this is beta and may change in the future, but not thrilled that an account is required to use and opt into it. From nobody Wed Feb 1 07:33:35 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P6DDm3drXz3cQvY for ; Wed, 1 Feb 2023 07:33:44 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ictdccexch001.one.local", Issuer "Stormshield Servers CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P6DDm1CRfz3Gxc; Wed, 1 Feb 2023 07:33:44 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; d=stormshield.eu; s=signer; c=simple/simple; t=1675236815; h=from:subject:to:date:message-id; bh=lVvUFKCdCGxwn1PM4zNS+C+qyzXpZiaBc9SzMWXSH34=; b=XjAH4qY0JtTJcoLIhRXR6MGWWfCKZvO0T52iCzLeFfdj9VBH5ja38f6kwLZcPLnwRkRv8ylMLBE VyJX1tkxbLJFYKSFfg4GScdcXmoMo2ZwN9ewxvNak5UZkOnADIAAlA+XT6jNDXf6H15ptVGGiEYPK FvRTeoCAIUQyZYDJScP9Z/Ax3KgZk9H4S58QbjEUO/5Oeec9+yy4Zh0cvSkEKaxppkWKaBZeGR9Tl fXe1vbPkWBdXTRp4LxzvgeyZB2N5hgEMNKInDNb3d6IptlmHZlo07jV7r5oV/9RbEre7ai1CwSX9U 03IXdCPxZtOV9UVwXMRI0fDMRlEymeHFMrSA== Received: from cthulhu.stephaner.labo.int (10.2.16.1) by ICTDCCEXCH001.one.local (10.180.4.1) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21; Wed, 1 Feb 2023 08:33:35 +0100 Received: by cthulhu.stephaner.labo.int (Postfix, from userid 1001) id 4AD231FDC9; Wed, 1 Feb 2023 08:33:35 +0100 (CET) References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <35e07b16-e635-a88c-f10b-cde0df05140b@freebsd.org> <86zg9zw0fz.fsf@cthulhu.stephaner.labo.int> User-agent: mu4e 1.2.0; emacs 27.1 From: Stephane Rochoy To: Mitchell Horne CC: Stephane Rochoy , , User Ngor , Warner Losh Subject: Re: Tooling Integration and Developer Experience In-Reply-To: Date: Wed, 1 Feb 2023 08:33:35 +0100 Message-ID: <86y1phx2k0.fsf@cthulhu.stephaner.labo.int> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Originating-IP: [10.2.16.1] X-ClientProxiedBy: ICTDCCEXCH001.one.local (10.180.4.1) To ICTDCCEXCH001.one.local (10.180.4.1) X-Rspamd-Queue-Id: 4P6DDm1CRfz3Gxc X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Mitchell Horne writes: > On 1/31/23 04:52, Stephane Rochoy wrote: >> Mitchell Horne writes: >> >>> [Src] Needs Reviewer >>> https://reviews.freebsd.org/differential/query/65AoyPFlIhdE/ >> What is the purpose of the "Contributor Reviews (base)" >> project/group? >> Regards, >> -- St=C3=A9phane Rochoy >> O: Stormshield >> > > It is a group ("Project") that anyone can join to receive=20 > notifications whenever > the group is tagged. Groups can be added as a reviewer on a=20 > revision, for > example. > > There is a Herald rule to automatically add this Contributor=20 > Reviews group as a > subscriber to any src revisions that have no reviewers=20 > specified. > > This makes it an imperfect search criteria for "reviews which=20 > are accepted but > not authored by a FreeBSD committer". I guess the committers group was not used to let developers choose to participate or not to the "Needs Reviewer" effort. Correct? As a side note, I was surprised to see we can't query reviews from users not being in a given group, i.e., "Responsible Users" not in "Contributor Reviews (base)" would have been more straightforward. (The Project application allow advanced queries via not() and any() functions). Regards, -- St=C3=A9phane Rochoy O: Stormshield From nobody Wed Feb 1 08:58:33 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P6G6g5Fxbz3bNhp for ; Wed, 1 Feb 2023 08:58:35 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P6G6g4d6tz3QKC for ; Wed, 1 Feb 2023 08:58:35 +0000 (UTC) (envelope-from theraven@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675241915; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yHO4vb+hsWF2B3Y8HJhS94ZrpZV8351E7JPKJALWrWE=; b=j3kdBHpRWVKX7vCwriL8GvjlT4NV8VS/azJUqBCqcPg3S4APY95c4qRimwA0qM/PB7zh3+ craeAGu7QiZR+X3CaZ/F0K3OTEezXacLFjVz0A/B0Ir9a3aMnBa2Ag3ofse0eifO15oPYr H6qB0I0/MYVLLXYlmxsl4lRDmE/VSkLZ6iNo9DhjIXSOtEEv+Gv66qah8EhQGT7x6H2cZq I8QBVo3K58gRW0tzCch78F6GIN0StgbNr2TB+nuwaOo6KIL4i8Av7jR6kKctCVBMLxhlR7 b2gU7tsji+U7ehUWA0DPkQomdE72DjByls1c2jMORL/MaSIpm1sN/vWCtg+uJA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675241915; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yHO4vb+hsWF2B3Y8HJhS94ZrpZV8351E7JPKJALWrWE=; b=THDrTLpljaS88eomgazcoiQvbXVrc4V131llwa5HcSuQGQOZXu302hYzlqi525PQbWiDh0 5kAmScYdRbDR9fylhX/rLe5OjpIBLgoHp/6MxPtpCAIbrvC6uAKwrtXto9M0DbH8/WgyBM M05k9CJR8ikUddDm77O5s8E+XUvju2JdpjPTVnOvhVMiXp3QegniSRMNqxCO8Mqyo1ZnSL JgS1ifs70PNQjtBpBnkNIaO669eIrFx6nLf27d+p1j+udJAu03HY95DQWziB/xfele6bGp tKXSO/lIT40bkS/zplHWe0lcw2HKHDV/z2IPUKKihOfCmGzIFWH+tjXtfEaVOA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675241915; a=rsa-sha256; cv=none; b=Bwsn0sq4YO9cudJxvqNmLqYuuhM1V3XbljtWOx4jLaIBX6rxj2UVGhnyTpw2dgJY40cDfj GEhJItPR5mgr2cmouCxvuXs77KwcUBWN23448Dak2n/wNOGnq3KHJyWzjNRBKBsohQqhR5 V41Z0SDICAsqesJf6qYTs42xfl2b94EZ7HvjO/biSjrVgkpAxfVZILTf8fRniXoLS6KAsJ 7Aw4IDhSxmJbo+u+zWC4sdOBNOAn+UJwXWgzznE5DMD1wqL7rrC3P+JxwD2j0BtZPw7cSb vwTeRU8/kiLvpZHd1feBlilz7fyWPgu2URX79w6LxzQYYcnV61GrZWHUyn3wVw== Received: from smtp.theravensnest.org (smtp.theravensnest.org [45.77.103.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: theraven) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P6G6g3Wwjzx7Z for ; Wed, 1 Feb 2023 08:58:35 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.202] (host81-156-200-108.range81-156.btcentralplus.com [81.156.200.108]) by smtp.theravensnest.org (Postfix) with ESMTPSA id E6A061A29 for ; Wed, 1 Feb 2023 08:58:34 +0000 (GMT) Message-ID: Date: Wed, 1 Feb 2023 08:58:33 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: GitHub Code Search [Re: Tooling Integration and Developer Experience] Content-Language: en-GB To: freebsd-current@freebsd.org References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> From: David Chisnall In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 01/02/2023 06:05, Yetoo wrote: > On Tue, Jan 31, 2023, 9:47 AM David Chisnall wrote: >> On 30/01/2023 21:39, Yetoo wrote: >>> If github is going to be considered for issue tracking I just want to >>> say, after having extensively using it for issue tracking, it tends to >>> be difficult to find an issue if the exact title isn't entered and many >>> duplicate reports are made as a result. Code search sucks and doesnt >>> show you the multiple places in a file where a match was made so a user >>> may be left wondering if code exists or not, but this doesn't seem to be >>> germane given this is about issue tracking. >> Which search are you using? The old GitHub search is not great, but >> cs.github.com has replaced local search for me in the FreeBSD tree. >> It's not*quite* as good as fxr, but it's close. >> >> For example, searching for sys_cap_enter: >> >> https://cs.github.com/?scopeName=All+repos&scope=&q=sys_cap_enter+repo%3Afreebsd%2Ffreebsd-src+ >> >> David > Clicking that link greets me with a login screen and a requirement to > join a waitlist. Yes, this is beta and may change in the future, but > not thrilled that an account is required to use and opt into it. Sorry, I thought it was open to everyone now. If the issue is needing a GitHub account, I don't have a work around - in my experience having one has been unavoidable if you want to contribute to the F/OSS ecosystem for about 10 years now. I used to be a big proponent of projects hosting their own infrastructure on open platforms, but after seeing massive jumps in the number of active contributors for projects that moved to GitHub workflows, I've decided to pick other battles. David From nobody Wed Feb 1 16:35:53 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P6SGL6LZwz3cfQ3 for ; Wed, 1 Feb 2023 16:35:54 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P6SGL5s3Kz3GBw; Wed, 1 Feb 2023 16:35:54 +0000 (UTC) (envelope-from se@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675269354; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LAyjwCf4UPOViLMgFAxA2yZkfrdP/VV1Dj0S1yNnu3c=; b=ezcFid8XmQOpYhnFbRnANxsdOkCKt5lTTMuQ7Y57EOyV2hG86yRn0sqrABEBqMztYlEnaX JQCcUlS/fJhRLhh6eJU7b//pQpU3rryUAzANMjGBzfxkWAd1N2rK9xEILCmDmwLzCXeEnx 4l9IqV1VLJbgmHX6URlAI0lz32446rRVw4SprRQUfrnfee+hnXj5GeS4+OM8oonsbXsQ6O Q48M6giJQHTKCjmGiUzoAqAw26AQ0DDmzmUqYGLgnPX2nvpRkN7oOWsJKIauZFwYkmo2Wd EfXEjFppimd8AEjpf4ICtDGGKRmwGbHStq7KaBvGH9yQxLlgk0eDQuLsGRh9pA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675269354; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LAyjwCf4UPOViLMgFAxA2yZkfrdP/VV1Dj0S1yNnu3c=; b=L7lXs0fYi9vevo8k4rUjJPlFn5yAOhbnN+jXyxKy05DTHGO0LuIHQ+jETOxdyii0tVAIOq iMNtej/nlqgQaUzviflb6H2hK2ckkiw4BLb1VOUsMI+Zlx+JbfPcL72N/QHdu0CDg1HDTD hwoizD11gsmAlacg/xDgc4ShmB5x9CvKu7Dw9MemPSWuRPHwBIXt6WAeRoBdztl4Ho+EnB fEr96Pc+YlCypr83ZYS+JOcHg8zjXDAVkQ9lQ3MLhSCExqnqC3dfevVrs15aeb13sqMBXB eWeoNC9+TdO4CqgWzFcBwUxI7NxsiOUbmmxQAoPNOeWErALvKmwWjviWTIeMwQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675269354; a=rsa-sha256; cv=none; b=dof4iaozD7WkMUx/3N7LDvM2yzrQw2Uzq2EKIPI52CXkVWkfaUJ17+MGVElROQl1FzbcLO +qPzb+Fj7aWscVUUvHAT/YKDXRerN3hCbZuoRsr9Mrjk+SH5G+4ZFIE+h/qaGKq3UoJs52 jtwIFX1kTMvv+quvxM/AlNBHXNFkGRnbELW7JHG4gBzTi0uNQPVLbcczNjBuEfYjE5nmlm O8NJXm6ArbUf+mTMPFtpXaZrKz9kuJ4stF7+hA30wq2FjaVvUPiHsl0ixNu3T5KV2rJgai Sr4+44ApiTuue4993HSZt8xZ/bnpc5hWt7Adm0PKiK02vc1elLewmV52ns2VGg== Received: from [IPV6:2003:cd:5f2a:1000:9173:c1ae:9b8:a4af] (p200300cd5f2a10009173c1ae09b8a4af.dip0.t-ipconnect.de [IPv6:2003:cd:5f2a:1000:9173:c1ae:9b8:a4af]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P6SGL1jlsz16DW; Wed, 1 Feb 2023 16:35:54 +0000 (UTC) (envelope-from se@FreeBSD.org) Message-ID: <60be58f2-c33d-5707-500b-1746c6fc3d67@FreeBSD.org> Date: Wed, 1 Feb 2023 17:35:53 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.7.0 From: Stefan Esser Subject: Re: vt and keyboard accents Content-Language: de-DE, en-US To: Yuri References: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> Cc: FreeBSD CURRENT In-Reply-To: <70f53d17-46eb-c299-1a93-bf28858c1685@aetern.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N Am 29.01.23 um 01:54 schrieb Yuri: > Looking into an issue with accents input for vt and cz (so > /usr/share/vt/keymaps/cz.kbd) keyboard where some of the accents are > working and other result weird unrelated characters output. > > Checking kbdcontrol -d output, there is an obvious difference with > keymap contents -- all mappings are trimmed down to 1 byte after reading: > > kbdcontrol: > dacu 180 ( 180 180 ) ( 'S' 'Z' ) ( 'Z' 'y' ) ( 's' '[' ) > ( 'z' 'z' ) ( 'R' 'T' ) ( 'A' 193 ) ( 'L' '9' ) > ( 'C' 006 ) ( 'E' 201 ) ( 'I' 205 ) ( 'N' 'C' ) > ( 'O' 211 ) ( 'U' 218 ) ( 'Y' 221 ) ( 'r' 'U' ) > ( 'a' 225 ) ( 'l' ':' ) ( 'c' 007 ) ( 'e' 233 ) > ( 'i' 237 ) ( 'n' 'D' ) ( 'o' 243 ) ( 'u' 250 ) > ( 'y' 253 ) > > keymap: > dacu 0xb4 ( 0xb4 0xb4 ) ( 'S' 0x015a ) ( 'Z' 0x0179 ) > ( 's' 0x015b ) > ( 'z' 0x017a ) ( 'R' 0x0154 ) ( 'A' 0xc1 ) > ( 'L' 0x0139 ) > ( 'C' 0x0106 ) ( 'E' 0xc9 ) ( 'I' 0xcd ) > ( 'N' 0x0143 ) > ( 'O' 0xd3 ) ( 'U' 0xda ) ( 'Y' 0xdd ) > ( 'r' 0x0155 ) > ( 'a' 0xe1 ) ( 'l' 0x013a ) ( 'c' 0x0107 ) > ( 'e' 0xe9 ) > ( 'i' 0xed ) ( 'n' 0x0144 ) ( 'o' 0xf3 ) > ( 'u' 0xfa ) > ( 'y' 0xfd ) > > Source of the problem is the following definition in sys/sys/kbio.h: > > struct acc_t { > u_char accchar; > u_char map[NUM_ACCENTCHARS][2]; > }; > > While the keymaps were converted to have the unicode characters for vt > in the commit below, the array to store them (map) was missed, or was > there a reason for this? > > --- > commit 7ba08f814546ece02e0193edc12cf6eb4d5cb8d4 > Author: Stefan Eßer > Date: Sun Aug 17 19:54:21 2014 +0000 > > Attempt at converting the SYSCONS keymaps to Unicode for use with > NEWCONS. > I have spent many hours comparing source and destination formats, > and hope > to have caught the most severe conversion errors. > --- > > I have tried the following patch and it allows me to enter all accents > documented in the keymap, though I must admit I'm not sure it does not > have hidden issues: > > diff --git a/sys/sys/kbio.h b/sys/sys/kbio.h > index 7f17bda76c5..fffeb63e226 100644 > --- a/sys/sys/kbio.h > +++ b/sys/sys/kbio.h > @@ -200,7 +200,7 @@ typedef struct okeymap okeymap_t; > > struct acc_t { > u_char accchar; > - u_char map[NUM_ACCENTCHARS][2]; > + int map[NUM_ACCENTCHARS][2]; > }; > I have extended the range of the map array entries to 16 bits, which is sufficient for all currently defined keymap entries, see commit 1e0853ee8403. Thanks for reporting! Regards, STefan From nobody Thu Feb 2 09:36:51 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P6twg4NqZz3cSnp for ; Thu, 2 Feb 2023 09:37:07 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P6twf5Z54z3rQX for ; Thu, 2 Feb 2023 09:37:06 +0000 (UTC) (envelope-from Alexander@leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=I0TN+cal; spf=pass (mx1.freebsd.org: domain of Alexander@leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@leidinger.net; dmarc=pass (policy=quarantine) header.from=leidinger.net Received: from outgoing.leidinger.net (p5b165a22.dip0.t-ipconnect.de [91.22.90.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "outgoing.leidinger.net", Issuer "R3" (verified OK)) by mailgate.Leidinger.net (Postfix) with ESMTPSA id 8145A6CB for ; Thu, 2 Feb 2023 10:36:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1675330614; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=RPuBJhSJd9HTZm0g13v80fqi6tOZA70UpTHvUqWfI48=; b=I0TN+calhTUi7Mx+cF4V5OrUYkMudFn+IcpugbLAaRbVYgxZWlLwbhWvnmJYm7iQYPa/J3 fBAMkISmXKzBIgZkKLbyvDrl2PUGYUOWQjG7Bavu9AmmXL1eJeuGjR3vBJT288E+DtJzzT qVz20VUImsiMUaINjaWc73T0aY+ltZUGu6nH7x8EiWdoBA5UWFSsXqftEDSU742ig+Vi5d sJgp9QQ6gLMcg7g5OFr3HMaVbulMKSuZdMbJWo9ZSbL+brKHmO2YjAD6M+CXuSh9Loz7c3 5fvjGu1CMUCtL4cIIAzKBLj7tJKsdk6lFHpBb3bjwQHPTaWph7+7gk5ZeBIfwQ== Received: from webmail.leidinger.net (localhost [127.0.0.1]) by outgoing.leidinger.net (Postfix) with ESMTP id 0C6BB2BE for ; Thu, 2 Feb 2023 10:36:52 +0100 (CET) Received: from www (uid 80) (envelope-from Alexander@leidinger.net) id 9ec10 by webmail.leidinger.net (DragonFly Mail Agent v0.13+ on webmail.leidinger.net); Thu, 02 Feb 2023 10:36:51 +0100 Date: Thu, 02 Feb 2023 10:36:51 +0100 Message-ID: <20230202103651.Horde.yAqcbqzfHTSd2KbPO-uxy_y@webmail.leidinger.net> From: Alexander Leidinger To: current@freebsd.org, fs@freebsd.org Subject: py-libzfs build failure on current, zpool_search_import() missing Accept-Language: de,en Content-Type: multipart/signed; boundary="=_C42pVk0VFPj_hlfv-saVsfk"; protocol="application/pgp-signature"; micalg=pgp-sha256 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 X-Spamd-Result: default: False [-6.08 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.979]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; R_SPF_ALLOW(-0.20)[+mx]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[leidinger.net:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4P6twf5Z54z3rQX X-Spamd-Bar: ------ X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format and has been PGP signed. --=_C42pVk0VFPj_hlfv-saVsfk Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, the build of py-libzfs fails on -current due to a missing=20=20 zpool_search_import(),=20and as such iocage can not be build (and the=20=20 old=20iocage segfaults, so the ABI seems to have changed too). The=20=20 symbol=20is available in libzutil, but I can not find=20=20 zpool_search_import()=20in /usr/include. Anyone with an idea if there is something missing (maybe something to=20=20 be=20installed into /usr/include), or what needs to be done to py-libzfs? Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_C42pVk0VFPj_hlfv-saVsfk Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmPbhDMACgkQEg2wmwP4 2IYdRA//Z+1PlqrP/H1t0YhCrfQEBjS5qel6tycKfFg5s9gmD/qHLK7cXfiX7xVw dUBwrL4xZuHMZWh14Q3XPP3P2GQtEuicKZj+M7ggfeNPRoGitYtIfnjruVJJX8UJ WXj11k97z6VKD+TQOiP1jzUQhAUtg99NbKZunxtCZv6zcOU8bxq9dL2I9PRGRB3P lSxXTDYqDm4JRQjYVlRk9acnbebWAayQQVnheaBT2eLPBO17DAXSQjIhJtC325gr bzX7G3ApMCq548gfXwz04xSWYHtEUsngn3zTSQvITL1RHgc7jtEJ0KXCzO3l/rhB 0iAXxWPMpkh/oYU8+/i8o6OnhmarK8PzqUf+vMDsCiSdVTLSC1R232d1EbgsZLo+ xOcBMXzGmsfPs216ZcgAI/mWwct0bYIBzJVG16mr5zm8Sg/7AIm1SpazfEfYnb1P GyPVgl88gdMhLtYnzpMIsvNPOkGakYUomjdUNNfOf//6ERVYZUbLxjqfpdM36Wsh AadMsBRb1w88iPb0AIVX1loQi6kTKtmGLAlNmo9sxhMzdigPRDgmto6jOt3Jrido iRlEZQszXIuUE28lTMxwC8hsQkEKduMtnn9mPwLAweQI6UfkFJZv2bFP7atOJCKs RSg1afFPUxxfwbrdtScWZRmCakyrJw8tP9u1DtMAGuGo6SZSxsg= =RaGN -----END PGP SIGNATURE----- --=_C42pVk0VFPj_hlfv-saVsfk-- From nobody Thu Feb 2 09:36:01 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P6twk4PV7z3cT3X for ; Thu, 2 Feb 2023 09:37:10 +0000 (UTC) (envelope-from parv.0zero9@gmail.com) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P6twj6YRwz3rPk for ; Thu, 2 Feb 2023 09:37:09 +0000 (UTC) (envelope-from parv.0zero9@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b="L8LZjiv/"; spf=pass (mx1.freebsd.org: domain of parv.0zero9@gmail.com designates 2a00:1450:4864:20::636 as permitted sender) smtp.mailfrom=parv.0zero9@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x636.google.com with SMTP id dr8so4146129ejc.12 for ; Thu, 02 Feb 2023 01:37:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=pDJuC+ivA3WcVlGfdFVvwk2ymN+6wMKLeaNoQgz3Dms=; b=L8LZjiv/siRcVUOA+cOgzAALXx41iIowjmfuqN8Aa23VOrGNvHrASgVEAUfX6LhBRy MSswncan1kAWo1OkvtAwGc/ZV2e5YCTdVV51qzZrWuPYS3pz6pHTLcuz7Rsgbg7OSMzW S3GdybDuVYl/zm0Clbo0xHe/tGt96hc+Na0pgU5MdINPE3Qhq04aoL/rS51R1V/FHDGC HIyqEAxN+B8+hgPs0pj3KY8FFWzpvdF8et+TzBaIa/W72TQN610Kk82FPN9ZS9RDk96n //kboEUbci6OKwOVxQ2iBAIOzskKmPzSTQ0UgRnN/ceZ/Zn1FNXtKoI0vqO40TY/XmCr LvVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=pDJuC+ivA3WcVlGfdFVvwk2ymN+6wMKLeaNoQgz3Dms=; b=4yt/vV1BPgmUXHcOTY6Ek7zZhxqKjOo2EIlDkwMKmUa9BnSx+YkQlAqPLvGLrmwluc yZ/gw7WL5FX6n8IlZTFM6nbQ4+pLsJkY3dPCq72CVeno6mU06aQ8L3GzAHMgIdbIVUTX Z7rC3INju/XSRQjUDXRWhkewwsU/NpJqthBr275kmOov0HLRWvOlAjXVlBABn+4afIFG XRN12YlmoWu9wXohEsUkTbp5GNUHkZ4KLFp8Nxgd5mtl8rlk16bMCicTmUeBjBp5cBlG 1WVbdhO+lyyUYvfbAB8A1bAcT7Jplo9gGwt70Vc9DjIwXekGsGKJ6XLB1CiotTBcg8cv RR/A== X-Gm-Message-State: AO0yUKUsyJz4h0xzCNdkIWgQmXiLyi7xD0LkP+TpTakaNnpSQ4of0GnW winRSoh57moxV590KRp6cpkxiNjW4nFgm3oDiBe7h/9Qvyk= X-Google-Smtp-Source: AK7set9ejgtQE+Ax15cRtCwdF6e9vRGrFznJj2f10hls+dHCkkpHnAOdlzqxWqQoAjs+WOSHclT9UWREDg1fT88Al8E= X-Received: by 2002:a17:906:71d3:b0:84d:28da:f3a with SMTP id i19-20020a17090671d300b0084d28da0f3amr1559291ejk.76.1675330628584; Thu, 02 Feb 2023 01:37:08 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: "parv/FreeBSD" Date: Wed, 1 Feb 2023 23:36:01 -1000 Message-ID: Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000ff875805f3b44e8e" X-Spamd-Result: default: False [-3.40 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.40)[-0.404]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::636:from]; ARC_NA(0.00)[]; TAGGED_FROM(0.00)[freebsd]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4P6twj6YRwz3rPk X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000ff875805f3b44e8e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I should have requested in OP to CC to me as I have subscribed to -current@ list without receiving email. So here is my attempt to craft a reponse from the web page ... https://lists.freebsd.org/archives/freebsd-current/2023-January/003142.html > Oleksandr Kryvulia wrote on 20230131-092359 UTC > > 31.01.23 09:52, parv/FreeBSD =D0=BF=D0=B8=D1=88=D0=B5: > > > > Since around 2022-11, I am unable to change display brightness > > of the display of a Framework laptop (Intel i5-1135G7, Iris > > Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port) > > & "acpi_video" (FreeBSD) kernel module. > > > > Earlier I was able to change brightness via "hw.acpi.video" MIB ... > > > > # - Need to have both "i915kms" & "acpi_video" modules already loaded. > > # > > # 20221120 - These MIBs do not work anymore as they are missing. > > hw.acpi.video.lcd0.economy=3D10 > > hw.acpi.video.lcd0.fullpower=3D40 > > hw.acpi.video.lcd0.brightness=3D15 ... > Does backlight(8) works for you? Thanks for the clue. It does! It does ... - I get the same number back via "backlight" without any arguments as what I gave it earlier. There was no reporting of value being subtracted by one; - with 0, everything was near-black, dark enough for not being able to read anything on the console; - with 100, screen was surely damn bright *oh my eyes* - unlike Poul-Hennig K's experience ... https://lists.freebsd.org/archives/freebsd-current/2023-January/003143.html ... when running with & without AC (for short periods) I did not see any change in "backlight" behaviour. The brightness did not change unless I had changed it myself. Thanks again. FreeBSD here is ... FreeBSD luna 14.0-CURRENT FreeBSD 14.0-CURRENT #6 main-n260169-34ac629b40e6: Fri Jan 20 07:05:01 HST 2023 root@luna:/build/world/freebsd/src/amd64.amd64/sys/GENERIC-Light amd64 - parv -- --000000000000ff875805f3b44e8e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I should have requested in OP to CC to me as I have subscribed to
-cu= rrent@ list without receiving email.

So here is my attempt to craft = a reponse from the web page ...

=C2=A0 https://lists.fr= eebsd.org/archives/freebsd-current/2023-January/003142.html


= > Oleksandr Kryvulia wrote on 20230131-092359 UTC
>
> 31.01.= 23 09:52, parv/FreeBSD =D0=BF=D0=B8=D1=88=D0=B5:
> >
> > = Since around 2022-11, I am unable to change display brightness
> >= of the display of a Framework laptop (Intel i5-1135G7, Iris
> > X= e iGPU) with "i915kms" module (from "drm-510-kmod" pack= age/port)
> > & "acpi_video" (FreeBSD) kernel module= .
> >
> > Earlier I was able to change brightness via &qu= ot;hw.acpi.video" MIB ...
> >
> > # - Need to have b= oth "i915kms" & "acpi_video" modules already loaded= .
> > #
> > # 20221120 - These MIBs do not work anymore a= s they are missing.
> > hw.acpi.video.lcd0.economy=3D10
> &g= t; hw.acpi.video.lcd0.fullpower=3D40
> > hw.acpi.video.lcd0.bright= ness=3D15
...
> Does backlight(8) works for you?

Thanks for= the clue. It does! It does ...

- I get the same number back via &qu= ot;backlight" without any arguments as
=C2=A0 what I gave it earlie= r. There was no reporting of value being
=C2=A0 subtracted by one;
- with 0, everything was near-black, dark enough for not being able to=C2=A0 read anything on the console;

- with 100, screen was surely = damn bright *oh my eyes*

- unlike Poul-Hennig K's experience ...=

=C2=A0 =C2=A0 https://lists.freebsd.org/archives/freeb= sd-current/2023-January/003143.html

=C2=A0 ... when running with= & without AC (for short periods) I did not see
=C2=A0 any change in= "backlight" behaviour. The brightness did not change
=C2=A0 u= nless I had changed it myself.

Thanks again.


FreeBSD here= is ...

=C2=A0 FreeBSD luna 14.0-CURRENT FreeBSD 14.0-CURRENT #6
= =C2=A0 main-n260169-34ac629b40e6: Fri Jan 20 07:05:01 HST 2023
=C2=A0 ro= ot@luna:/build/world/freebsd/src/amd64.amd64/sys/GENERIC-Light
=C2=A0 am= d64


- parv

--

--000000000000ff875805f3b44e8e-- From nobody Thu Feb 2 13:58:35 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P70kg1qPMz3dTVN; Thu, 2 Feb 2023 13:58:51 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vk1-f171.google.com (mail-vk1-f171.google.com [209.85.221.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P70kf5shTz4RG4; Thu, 2 Feb 2023 13:58:50 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vk1-f171.google.com with SMTP id q76so910340vkb.4; Thu, 02 Feb 2023 05:58:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=B0g+frbnsz6LsDGeLSBKRg1kyhD4XjRW1fs25rQJt1Q=; b=JcEu+e2zguWFjt9ASLNtyYnVoK7mfywN7XGunM1ab0nit6SnbHtCc0NWXIB0LOBiU1 yUHt/DLnwNHyNmQHTr2d6Cm1bjNlkroXhoWGum6hGFmBE6LfSkNdhj9ccJ8+UXfL5O2w lDeQitfHndwaekGgLxDeRvuCMta9VR0xUXZtPBtO48EIcOVHQrZoQNtz7ZoP4KaVx+qF W8bvcWeJD1I5qKQseQa3QYD6/dPjaz2JCFc0219zW8KaR5DMc2LiwofkRrSGrkGjC/LU YCcmFs75i0RMm6bDw1pNXoMI/FpKKiP/dUzV3A9WQfSNNrGPFie6q5zQcovGXHSaahQO hdTw== X-Gm-Message-State: AO0yUKXaSJtvzIpa03+sLF5lUg/z0T8HbJL5XjrtT8XqM8CMv44iNGjd gY1p3Aeo1R/xX22x9z82/TygZXKMu+R2dCWgNSjrqtxEefY= X-Google-Smtp-Source: AK7set/spJB99AwxkKagKqwga49BVNZK9APLXT7c56mPrkLZcY+W1E6xNkv925t6PRXtC8sfi1SLzYFm7B1v4U6Kkvg= X-Received: by 2002:ac5:c84f:0:b0:3ea:27b8:42c with SMTP id g15-20020ac5c84f000000b003ea27b8042cmr947602vkm.34.1675346328819; Thu, 02 Feb 2023 05:58:48 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20230202103651.Horde.yAqcbqzfHTSd2KbPO-uxy_y@webmail.leidinger.net> In-Reply-To: <20230202103651.Horde.yAqcbqzfHTSd2KbPO-uxy_y@webmail.leidinger.net> From: Alan Somers Date: Thu, 2 Feb 2023 06:58:35 -0700 Message-ID: Subject: Re: py-libzfs build failure on current, zpool_search_import() missing To: Alexander Leidinger Cc: current@freebsd.org, fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4P70kf5shTz4RG4 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Unfortunately libzfs doesn't have a stable API, so this kind of breakage is to be expected. libzfs_core does, but libzfs_core is incomplete. You should report this problem upstream at https://github.com/truenas/py-libzfs . On Thu, Feb 2, 2023 at 2:37 AM Alexander Leidinger wrote: > > Hi, > > the build of py-libzfs fails on -current due to a missing > zpool_search_import(), and as such iocage can not be build (and the > old iocage segfaults, so the ABI seems to have changed too). The > symbol is available in libzutil, but I can not find > zpool_search_import() in /usr/include. > > Anyone with an idea if there is something missing (maybe something to > be installed into /usr/include), or what needs to be done to py-libzfs? > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF From nobody Thu Feb 2 14:14:32 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P715X6kw7z3dfR2 for ; Thu, 2 Feb 2023 14:15:12 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P715X2n3zz4Tf7 for ; Thu, 2 Feb 2023 14:15:12 +0000 (UTC) (envelope-from Alexander@leidinger.net) Authentication-Results: mx1.freebsd.org; none Received: from outgoing.leidinger.net (p5b165a22.dip0.t-ipconnect.de [91.22.90.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "outgoing.leidinger.net", Issuer "R3" (verified OK)) by mailgate.Leidinger.net (Postfix) with ESMTPSA id 749B1AF6 for ; Thu, 2 Feb 2023 15:15:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1675347306; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8Gbg6Z8dachroqA9GfVEqFbDz+NuV21GGLmyr12qz7Y=; b=iPdekXeDD/EU7kKiNSerHSGd+Ihs4Jl/PIp7pq1oe1CP9gDs6X8lTLvjlR1d2Rs0GqgC8F FLSJq0IplyqSFaXSmglhOlpwSthmfB1gKBA4lhlKeu1rezhfzJh69QbLlBpDnpoHanM+Vu 6T55tVjetIGP37ynfMEuQilEXRgfhX77X9EG49KUilhsFq9fJpKm3rjlKeOnKrO5ogssED 7rKj6FXdl35jjX6DuI5qrB03XaklxWAlSEvNhNxm1UFnNPiBbkXK6WEB8Gve5nbr5UkBQL icZ9dWXeQcJXxL1CadEUX8LVLagkt1pqmucrL87YXINnPMk7IH6lt+MO9ZauPQ== Received: from webmail.leidinger.net (localhost [127.0.0.1]) by outgoing.leidinger.net (Postfix) with ESMTP id AE5A94A2 for ; Thu, 2 Feb 2023 15:14:33 +0100 (CET) Received: from www (uid 80) (envelope-from Alexander@leidinger.net) id a0412 by webmail.leidinger.net (DragonFly Mail Agent v0.13+ on webmail.leidinger.net); Thu, 02 Feb 2023 15:14:33 +0100 Date: Thu, 02 Feb 2023 15:14:32 +0100 Message-ID: <20230202151432.Horde.B3fD_ijUP7hDeGcTs2Ymmp1@webmail.leidinger.net> From: Alexander Leidinger To: Alan Somers Cc: current@freebsd.org, fs@freebsd.org Subject: Re: py-libzfs build failure on current, zpool_search_import() missing References: <20230202103651.Horde.yAqcbqzfHTSd2KbPO-uxy_y@webmail.leidinger.net> In-Reply-To: Accept-Language: de,en Content-Type: multipart/signed; boundary="=_MaKj56ndMVWYQg4U9_kepRR"; protocol="application/pgp-signature"; micalg=pgp-sha256 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 X-Rspamd-Queue-Id: 4P715X2n3zz4Tf7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format and has been PGP signed. --=_MaKj56ndMVWYQg4U9_kepRR Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Alan Somers (from Thu, 2 Feb 2023=20=20 06:58:35=20-0700): > Unfortunately libzfs doesn't have a stable API, so this kind of > breakage is to be expected. libzfs_core does, but libzfs_core is > incomplete. You should report this problem upstream at > https://github.com/truenas/py-libzfs . I did already. https://github.com/truenas/py-libzfs/issues/224 There is no libzfs_core.h in /usr/include, can it be that we need to=20=20 install=20this there? Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_MaKj56ndMVWYQg4U9_kepRR Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmPbxUgACgkQEg2wmwP4 2Iar8xAAoZA9ciC3bu+qI4G9gkUY8BjGjrrFqXI5s6N7BVAQyfKo69jmJ+s70Abg lT5wLPZP509IjgXrDUMz0S+HWU0sCHO/CCgQckex6/qx0WGCLaqdSYAWEoiUmdED tajhBLa3nB/cu0n7HmyDtDEY619lDRr91F0/qaJhJ+S+KfXNcKQlS81nTZnuXBii iiKeRCA8XLtExl9Ex5CHJAWZkqD3+pXlAugebiBSeNMp/vMXDwVqkJ3ruunIWRtc B0aUGox9cXowhd02wxtwZEQ7hzLCISh3tmkDGkt96ZtxOyNRRAEju/WqgQI4RWIR 84tbawWtsj0o9usw3jbmeKQ+rvpi511wf6C23CzWvETRf0PUWevRI6PBQty76wpM joDPhV5HpWuYOcsqQgMSoBvrvS3dAv2fmfskSNQ45gHZnVrgvurofcQ96tPwsC/m ZZ1/cAY2y8E29ODmDLpugS2PhWiJ1lk/IgSph2KFuAgr4c2IV98tA/cQo6vsXso5 QpsUxTR9m/hbH9HJWckgA7CM4WZ9TbvWBJ5z0eN/rrARgADjW41rLcJMnyjrGAet +5i3Yd0mOrPOG/zYC6QJOKuLTpCRV9oYmsGVtJsWg+GYMjAek/J842BIVkaZysXJ o0raMo07PmpP+xNjRWH0Y6aBw4gu0x2pn+Y/Sr9NYGypGMkmh4Q= =Mcy7 -----END PGP SIGNATURE----- --=_MaKj56ndMVWYQg4U9_kepRR-- From nobody Thu Feb 2 14:25:10 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P71L60zLSz3dfgq for ; Thu, 2 Feb 2023 14:26:06 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.18.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P71L426HTz4X88 for ; Thu, 2 Feb 2023 14:26:04 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of freebsd-listen@fabiankeil.de has no SPF policy when checking 80.67.18.29) smtp.mailfrom=freebsd-listen@fabiankeil.de; dmarc=none Received: from [91.20.76.172] (helo=fabiankeil.de) by smtprelay06.ispgateway.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pNaXJ-0005AM-0g for freebsd-current@freebsd.org; Thu, 02 Feb 2023 15:26:01 +0100 Date: Thu, 2 Feb 2023 15:25:10 +0100 From: Fabian Keil To: freebsd-current@freebsd.org Subject: Re: 1 year src-patch anniversary! Message-ID: <20230202152510.33a9ab04@fabiankeil.de> In-Reply-To: References: <202301292218.30TMIQmM020883@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/XAKpgO3On+zMuviFzcCQfwe"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Df-Sender: Nzc1MDY3 X-Spamd-Result: default: False [-3.63 / 15.00]; SIGNED_PGP(-2.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.99)[-0.986]; NEURAL_HAM_SHORT(-0.98)[-0.975]; NEURAL_HAM_MEDIUM(-0.47)[-0.467]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; RCVD_COUNT_TWO(0.00)[2]; SUBJECT_ENDS_EXCLAIM(0.00)[]; ASN(0.00)[asn:34011, ipnet:80.67.16.0/20, country:DE]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[80.67.18.29:from]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; R_SPF_NA(0.00)[no SPF record]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[fabiankeil.de]; RWL_MAILSPIKE_POSSIBLE(0.00)[80.67.18.29:from] X-Rspamd-Queue-Id: 4P71L426HTz4X88 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --Sig_/XAKpgO3On+zMuviFzcCQfwe Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Mateusz Guzik wrote on 2023-01-29 at 23:29:48: > On 1/29/23, Jamie Landeg-Jones wrote: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261657 is a trivial= fix > > to an admittedly trivial issue, but it's soon going to hit one year old, > > and has not had any feedback. Not even "this is rubbish. close ticket" > > > > | jamie@catwalk:~ % stat 'so good they named it twice' > > | stat: so good they named it twice: stat: No such file or directory > > > > As such, it's the oldest of my patches to be completely ignored, but th= en, > > most of my fixes I haven't even submitted, because, what's the point? > > I've instead spent time writing something so the patches are automatica= lly > > aplied to my src tree, and distributed to all my servers. > > > > I know it's a volunteer effort, but I've been here 25 years, and whilst > > I could (and should) take on more port-maintainership, any other offers > > of help have fallen on deaf ears. > > >=20 > Well I was not aware of it. >=20 > mail me with git format-patch result and I'll commit. Is this an open invitation? I can easily beat the 1 year anniversary with a couple of ggate-related patches: Teaser: fk@t520 /usr/src $grep "^Reported" ~/web/www.fabiankeil.de/sourcecode/elect= robsd/ElectroBSD-13-f5631983b23-2023.02.02-ggate.diff=20 Reported to security-officer@FreeBSD.org on 2014-12-09. Reported to security-officer@FreeBSD.org on 2014-12-09. Reported to security-officer@FreeBSD.org on 2014-12-09. Reported to security-officer@FreeBSD.org on 2014-12-09. Reported to security-officer@FreeBSD.org on 2014-12-09. Reported to security-officer@FreeBSD.org on 2015-04-05. Reported to security-officer@FreeBSD.org on 2015-04-05. Reported to security-officer@FreeBSD.org on 2015-04-05. The patch set is against stable/13 but I could rebase on HEAD if there's interest and actual merge conflicts. Fabian --Sig_/XAKpgO3On+zMuviFzcCQfwe Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCY9vHxwAKCRAFiohV/3dU nT/4AKDFbK4bGparWV6m4LPySSTY+mPbswCfT+/6GGLSOZ5N8UqlwCswrcqsa2Q= =hb7N -----END PGP SIGNATURE----- --Sig_/XAKpgO3On+zMuviFzcCQfwe-- From nobody Thu Feb 2 16:02:00 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P73T236lmz3fnJk; Thu, 2 Feb 2023 16:02:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-vs1-f48.google.com (mail-vs1-f48.google.com [209.85.217.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P73T2176xz3Pq8; Thu, 2 Feb 2023 16:02:14 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-f48.google.com with SMTP id s24so2292325vsi.12; Thu, 02 Feb 2023 08:02:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xOwQWfA77KlsDcAE77Yz975dy3efLwVE2OWRDjkdfOg=; b=2dpzK1Iah2yZRytDmjPrlqA7y6hqZ6g+KdCubPaEWoEfJ1zRgMwD3PHPqSa7MZdCzm ruSPjOiLTFvvi04gv1rdKy/3hxM0FeRL+gWFpKRfGqRt4vPtj2uWb7I+fAeQwK3ZPXId RHqpRgTXe8HK/LKDV43MEWKFV/aOTpLOnAiN/gWTF8znNAoU6bPVCmEA+13hO1yTURe5 MMkp4jAcp3nsu1ApdglDJFV9gQgPziGJyTaDImaAdPcIobVcaD5EPAziuwyltH/QM8/I pcTcr8B2fjD9fyl02mJNpquh8Fqvlp71cjvWFQgUKx59HN9OQI9BUBiBkWAa2MK/KZ0u MB2Q== X-Gm-Message-State: AO0yUKUEVUK1BdzQfhC3TbnFCRkP0fuqeqdh3Ob9VrHlpzu/FRBH05A3 u0X4Vvk8gSmTXCAQc2wqGo4nNs95Oe9wnvFDNFcWc06j X-Google-Smtp-Source: AK7set/so7QHe/1aHn+oDYtlp7D1POkUfYm6yUj7oe50XoFDeU8ke9b5xEeE4pMLtwCRE4iA9dgdoV9IMtk9mdtAIq4= X-Received: by 2002:a67:ec0f:0:b0:3cb:88c6:293b with SMTP id d15-20020a67ec0f000000b003cb88c6293bmr1182890vso.53.1675353732658; Thu, 02 Feb 2023 08:02:12 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20230202103651.Horde.yAqcbqzfHTSd2KbPO-uxy_y@webmail.leidinger.net> <20230202151432.Horde.B3fD_ijUP7hDeGcTs2Ymmp1@webmail.leidinger.net> In-Reply-To: From: Alan Somers Date: Thu, 2 Feb 2023 09:02:00 -0700 Message-ID: Subject: Re: py-libzfs build failure on current, zpool_search_import() missing To: Ryan Moeller Cc: Alexander Leidinger , current@freebsd.org, fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4P73T2176xz3Pq8 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Thanks! But for the record, what was the actual required change? Could you like to the PR? On Thu, Feb 2, 2023 at 8:44 AM Ryan Moeller wrote: > > I've updated the py-libzfs port to fix the build. > > -- > Ryan Moeller > iXsystems, Inc. > OS Developer > Email: ryan@iXsystems.com From nobody Thu Feb 2 19:16:05 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P77mt5l5vz3kSvv for ; Thu, 2 Feb 2023 19:16:14 +0000 (UTC) (envelope-from SRS0=+va7wo=56=codenetworks.net=sm@eigbox.net) Received: from bosmailout06.eigbox.net (bosmailout06.eigbox.net [66.96.188.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P77ms4wXgz49cT; Thu, 2 Feb 2023 19:16:13 +0000 (UTC) (envelope-from SRS0=+va7wo=56=codenetworks.net=sm@eigbox.net) Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=codenetworks.net header.s=dkim header.b="sBy/6hBQ"; spf=pass (mx1.freebsd.org: domain of "SRS0=+va7wo=56=codenetworks.net=sm@eigbox.net" designates 66.96.188.6 as permitted sender) smtp.mailfrom="SRS0=+va7wo=56=codenetworks.net=sm@eigbox.net"; dmarc=none Received: from [10.20.15.6] (helo=bosmailscan06.eigbox.net) by bosmailout06.eigbox.net with esmtp (Exim) id 1pNf48-0003Lx-II; Thu, 02 Feb 2023 14:16:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=codenetworks.net; s=dkim; h=Sender:Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID:Reply-To: Cc:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=CpDGIZDyOoBfj8tad3KLiUavPbM4oNra8uQIOJkFgP4=; b=sBy/6hBQmtPlOKb99heY881QEM nrE0Ne+MVxHkLgVYvlOPvmq+neKNsG1ONcQF2XKGIkEPHF4vMHH46WI1UcCiORuvpI+dT7yA0FCH3 7tDJ9g8CgS29/JxqaZzbAMHU+X80E0A6X2hesKtaRI+WZVAXWoKZtptXWdS0UEv26redAaveBf8jq fGrXuNqyaLXfliJKmOFPcZwgu6FOBXthlGTJGQqlhrTX9hTxvjlTTuHfAjTAnpt+MNdAuMgRafZoT f4lTWABeA4dPRbY4PWvxiobcaTUwbFOMrtJ3oWfvAA3R15KqUkOmCyzd7dBaJltuP80kD0Mxov9MI zs4Og8wQ==; Received: from [10.115.3.33] (helo=bosimpout13) by bosmailscan06.eigbox.net with esmtp (Exim) id 1pNf48-0002pa-65; Thu, 02 Feb 2023 14:16:12 -0500 Received: from bosauthsmtp03.yourhostingaccount.com ([10.20.18.3]) by bosimpout13 with id GKG92900503yW7601KGCBf; Thu, 02 Feb 2023 14:16:12 -0500 X-Authority-Analysis: v=2.3 cv=H7JAP9Qi c=1 sm=1 tr=0 a=6uKCkKhFq2wXOH2GoQX8aA==:117 a=Ek/qOh1uPkKSHvd30yk7rg==:17 a=IkcTkHD0fZMA:10 a=m04uMKEZRckA:10 a=-Yl_685HdVUA:10 a=6I5d2MoRAAAA:8 a=zor6UEzBprZnuidCUFQA:9 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 Received: from cm-81-9-194-73.telecable.es ([81.9.194.73]:26299 helo=[192.168.3.100]) by bosauthsmtp03.eigbox.net with esmtpa (Exim) id 1pNf44-0001Xx-Nj; Thu, 02 Feb 2023 14:16:08 -0500 Message-ID: <07b88cac-9f46-9405-9a42-970fce1010eb@codenetworks.net> Date: Thu, 2 Feb 2023 20:16:05 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error Content-Language: en-US To: bugzilla-noreply@freebsd.org, freebsd-current References: From: Santiago Martinez In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-EN-UserInfo: d3bdfab0736480cedf04ed92aaea2ef5:931c98230c6409dcc37fa7e93b490c27 X-EN-AuthUser: sm@codenetworks.net X-EN-OrigIP: 81.9.194.73 X-EN-OrigHost: cm-81-9-194-73.telecable.es X-Spamd-Result: default: False [-2.57 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; NEURAL_HAM_LONG(-0.80)[-0.796]; NEURAL_HAM_SHORT(-0.78)[-0.779]; FORGED_SENDER(0.30)[sm@codenetworks.net,SRS0=@eigbox.net]; R_SPF_ALLOW(-0.20)[+ip4:66.96.128.0/18]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_NONE(0.00)[66.96.188.6:from]; R_DKIM_PERMFAIL(0.00)[codenetworks.net:s=dkim]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:29873, ipnet:66.96.128.0/18, country:US]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_VIA_SMTP_AUTH(0.00)[]; TAGGED_FROM(0.00)[va7wo=56=codenetworks.net=sm]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[codenetworks.net:~]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[codenetworks.net: no valid DMARC record]; FROM_NEQ_ENVFROM(0.00)[sm@codenetworks.net,SRS0=@eigbox.net] X-Rspamd-Queue-Id: 4P77ms4wXgz49cT X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N Hi everyone, Seems that commit "2db35273502b3c35aa653effc5c97618567367ab" brakes bnxt driver for BCM57416 based cards. I have tried reverting the commit and the servers are now back online. if anyone has some spare time and energy, can please take a look at the commit, as I´m not sure what part of the commit is braking it. For detail please refer to bugzilla. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269133 Thanks a lot! Santiago From nobody Thu Feb 2 20:58:58 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P7B3d6plqz3kYWr for ; Thu, 2 Feb 2023 20:59:09 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P7B3d0XLjz4Q5y for ; Thu, 2 Feb 2023 20:59:08 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of phk@critter.freebsd.dk designates 130.225.244.222 as permitted sender) smtp.mailfrom=phk@critter.freebsd.dk; dmarc=none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 6A52789295; Thu, 2 Feb 2023 20:58:59 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 312KwwXI003815 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 2 Feb 2023 20:58:59 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 312Kwwj8003814; Thu, 2 Feb 2023 20:58:58 GMT (envelope-from phk) Message-Id: <202302022058.312Kwwj8003814@critter.freebsd.dk> To: "parv/FreeBSD" cc: freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 In-reply-to: From: "Poul-Henning Kamp" References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3812.1675371538.1@critter.freebsd.dk> Date: Thu, 02 Feb 2023 20:58:58 +0000 X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; FREEFALL_USER(0.00)[phk]; ARC_NA(0.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; FROM_HAS_DN(0.00)[]; TAGGED_RCPT(0.00)[freebsd]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.dk]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk] X-Rspamd-Queue-Id: 4P7B3d0XLjz4Q5y X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N -------- parv/FreeBSD writes: > > Does backlight(8) works for you? > > Thanks for the clue. It does! It does ... > > - I get the same number back via "backlight" without any arguments as > what I gave it earlier. There was no reporting of value being > subtracted by one; Sorry for the delay in reporting back. I consistently read one less back, except for 0 and 100. (This could easily be a BIOS bug) It also looks like the "no-op" behaviour I reported previously have gone away with my latest kernel update. But I see a new behaviour, but this may be intentional: When it comes out of screen-blanking, it goes to 100 (and reports 100). Also happens when an external monitor is connected, which is a bit annoying... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Fri Feb 3 07:23:29 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P7Rwk5TQyz2lGJK for ; Fri, 3 Feb 2023 07:24:06 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:313::1:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature ECDSA (P-256)) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P7Rwk3sBFz4QyW for ; Fri, 3 Feb 2023 07:24:06 +0000 (UTC) (envelope-from Alexander@leidinger.net) Authentication-Results: mx1.freebsd.org; none Received: from outgoing.leidinger.net (p5b165a22.dip0.t-ipconnect.de [91.22.90.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) client-signature ECDSA (P-256)) (Client CN "outgoing.leidinger.net", Issuer "R3" (verified OK)) by mailgate.Leidinger.net (Postfix) with ESMTPSA id BAB2E735 for ; Fri, 3 Feb 2023 08:24:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1675409041; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+es+s/Ph52hbd1ygU4MOeRAfXbwkrLEo/5oYz0dKnYA=; b=G5QuOWRwvVmuXA11BxrKfbKJekP3E2ylJ3LDKobcvSSoS3QMTrYIsC/uJG5lwh3NwqZIcJ Ln8EDPmVEg2mVQ3rUfhgA8HOZhta0Ya5wJ+3m2BaaIYwoWun+aUtcPLOhP3BKrCB8AXJDx CAMN8mGucM8qrFH/EZYw6MdZwiPW9q0nW3NZiPswR/CVIwWCz1wc+jsCqsUkOF+ojJyhaq reWOyn4mL+G4rbEj6YEuiJy5LVRy+yitX1e5MbP35s3CTfnGuE75gFbcwiE878uhpvaDe1 31+Jjew7SBHYJlaUYKwloHn49fiR5gIFaUsu0dkiJS622Bxl+qNGjj8/jZI4+Q== Received: from webmail.leidinger.net (localhost [127.0.0.1]) by outgoing.leidinger.net (Postfix) with ESMTP id 5B15E366 for ; Fri, 3 Feb 2023 08:23:29 +0100 (CET) Received: from www (uid 80) (envelope-from Alexander@leidinger.net) id a33b2 by webmail.leidinger.net (DragonFly Mail Agent v0.13+ on webmail.leidinger.net); Fri, 03 Feb 2023 08:23:29 +0100 Date: Fri, 03 Feb 2023 08:23:29 +0100 Message-ID: <20230203082329.Horde.436Pq-oJxzQuK1EXGeqff_1@webmail.leidinger.net> From: Alexander Leidinger To: Ryan Moeller Cc: Alan Somers , current@freebsd.org, fs@freebsd.org Subject: Re: py-libzfs build failure on current, zpool_search_import() missing References: <20230202103651.Horde.yAqcbqzfHTSd2KbPO-uxy_y@webmail.leidinger.net> <20230202151432.Horde.B3fD_ijUP7hDeGcTs2Ymmp1@webmail.leidinger.net> In-Reply-To: Accept-Language: de,en Content-Type: multipart/signed; boundary="=_Xnpm5VJMr7Q7Yqv25Adug6J"; protocol="application/pgp-signature"; micalg=pgp-sha256 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 X-Rspamd-Queue-Id: 4P7Rwk3sBFz4QyW X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:2a00:1828::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format and has been PGP signed. --=_Xnpm5VJMr7Q7Yqv25Adug6J Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Ryan Moeller (from Thu, 2 Feb 2023=20=20 10:43:53=20-0500): > I've updated the py-libzfs port to fix the build. The build still fails on -current as of end of Jan with "too few=20=20 argument=20to function call, expected 4, have 3" for zfs_iter_filesystems. Is a patch for openzfs in -current missing? I haven't seen a commit to=20= =20 -current=20in openzfs in the last 2 days. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_Xnpm5VJMr7Q7Yqv25Adug6J Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmPctnAACgkQEg2wmwP4 2Ib48w//aWGW6DuQBou2TKE0eAKFNyYfrgHDyhJEYjgJ2OrEi+k3x6vaTst0aBhx 72DrtH+dW8TUEk2M02w8XmGQFquE+/xKnkjgoAW6Z2QKi4HFMoaZAxreNzYnNE46 j4rgmIdg66qBerWloKGnTWvF7rPsys5uwNnedVwmP7vn77rTjBGG2jErBGX8azpe 5iBCTtbbljNKNZnX4VcL4IIO48zL+HlFZCSv8vNdKkbCdfruu+ABmU7xznb6PhUS e0vCrVskLL/6TqUjomCmBkHY2Z4612rFs+FrFY365UNKMurcmNSVGAYfMGzhBdm5 1szyTUONC27wxfhNI1W6WAkShjVIOnSJVnx+7OICSQzaKn47LGMyVnqHnKgK2HRV 2aDymUjzYlgH/uhpAClths4URLs1IvEvbAd/PwylKnBowkt81K//dLtPJlAYObQx 1AjfN+NOzX04bNnxPDExTn22bY/HXhO9nlY4Uz6HYm8xuIpUqYEP0MzmWI1FAvrC 7LRPPx1lFYH4h7MqSIZ6c/8+h+ZnQ8Rj1ElRUL31PTgq2DK/fnn2f8Q7RRqSVQu1 8YkhEL4euH55w/hHSktC61Lddvj+mHWeI6vhylyM2ht077AqNN4+YEzmt9WAx84E IhmTtpRVLajaJUElIdWYZEI8BE28V6Rzn+ca60xwLudmYeMy7jg= =Md/u -----END PGP SIGNATURE----- --=_Xnpm5VJMr7Q7Yqv25Adug6J-- From nobody Fri Feb 3 07:40:17 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P7SRC6Lswz2nJ1W for ; Fri, 3 Feb 2023 07:47:03 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P7SRC2dKMz4VTK for ; Fri, 3 Feb 2023 07:47:03 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1675410020; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hG50qnfyhHg7ehDIWTXmiojkvJWtlvgx2btSbH6Hrjo=; b=gVmiRtIDulLPMPvo5BpGKe238VU6J6hxgkh9f0CfNrcT7btg7SiywVUWrEiPjCIoVauvGW MLXRCIOsKTra5NSUUCdEciDEBXjYl6wu2GhO7ebuhnmmKrpkrBCyAjS5hRU6IU4KU08k1M twwP51WeajH3AZ9AESCM5b1bfeqrew0= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id e513296c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 3 Feb 2023 07:40:20 +0000 (UTC) Date: Fri, 3 Feb 2023 08:40:17 +0100 From: Emmanuel Vadot To: "Poul-Henning Kamp" Cc: "parv/FreeBSD" , freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 Message-Id: <20230203084017.b1e8dc1f9116d8a55a1c2cfd@bidouilliste.com> In-Reply-To: <202302022058.312Kwwj8003814@critter.freebsd.dk> References: <202302022058.312Kwwj8003814@critter.freebsd.dk> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4P7SRC2dKMz4VTK X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[freebsd]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, 02 Feb 2023 20:58:58 +0000 "Poul-Henning Kamp" wrote: > -------- > parv/FreeBSD writes: > > > > Does backlight(8) works for you? > > > > Thanks for the clue. It does! It does ... > > > > - I get the same number back via "backlight" without any arguments as > > what I gave it earlier. There was no reporting of value being > > subtracted by one; > > Sorry for the delay in reporting back. > > I consistently read one less back, except for 0 and 100. Even 50 ? > (This could easily be a BIOS bug) At first I though so too but I'll need to check if this isn't a rounding error between backlight(4) and linuxkpi wrappers. I know that some hardware don't have a perfect pwm controller for the backlight and so you have only some steps that it can do (but you don't know them). > It also looks like the "no-op" behaviour I reported previously have > gone away with my latest kernel update. Weird, nothing has changed for a while in this area but happy that it's fixed ;) > But I see a new behaviour, but this may be intentional: When it > comes out of screen-blanking, it goes to 100 (and reports 100). I'm not too surprised about this behavior, there is probably something that we could do about it but this will need more digging in linux framework and the drm drivers. > Also happens when an external monitor is connected, which is a > bit annoying... So if you have, let's say brightness at 50%, and you plug an external monitor, brightness goes up to 100% ? > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Emmanuel Vadot From nobody Fri Feb 3 08:46:28 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P7Tlr006Lz2nMP2 for ; Fri, 3 Feb 2023 08:46:31 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P7Tlq4b10z4cWZ for ; Fri, 3 Feb 2023 08:46:31 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 452A589281; Fri, 3 Feb 2023 08:46:29 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.17.1/8.16.1) with ESMTPS id 3138kSOx006054 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 3 Feb 2023 08:46:28 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.17.1/8.16.1/Submit) id 3138kSMO006053; Fri, 3 Feb 2023 08:46:28 GMT (envelope-from phk) Message-Id: <202302030846.3138kSMO006053@critter.freebsd.dk> To: Emmanuel Vadot cc: "parv/FreeBSD" , freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 In-reply-to: <20230203084017.b1e8dc1f9116d8a55a1c2cfd@bidouilliste.com> From: "Poul-Henning Kamp" References: <202302022058.312Kwwj8003814@critter.freebsd.dk> <20230203084017.b1e8dc1f9116d8a55a1c2cfd@bidouilliste.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6051.1675413988.1@critter.freebsd.dk> Date: Fri, 03 Feb 2023 08:46:28 +0000 X-Rspamd-Queue-Id: 4P7Tlq4b10z4cWZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[freebsd]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N -------- Emmanuel Vadot writes: > On Thu, 02 Feb 2023 20:58:58 +0000 > "Poul-Henning Kamp" wrote: > > > -------- > > parv/FreeBSD writes: > > > > > > Does backlight(8) works for you? > > > > > > Thanks for the clue. It does! It does ... > > > > > > - I get the same number back via "backlight" without any arguments as > > > what I gave it earlier. There was no reporting of value being > > > subtracted by one; > > > > Sorry for the delay in reporting back. > > > > I consistently read one less back, except for 0 and 100. > > Even 50 ? # backlight brightness: 0 # backlight 50 # backlight brightness: 49 # backlight 25 # backlight brightness: 24 # backlight 75 # backlight brightness: 74 yes > So if you have, let's say brightness at 50%, and you plug an external > monitor, brightness goes up to 100% ? No, plugging and unplugging does not change the backlight. But when the screen saver has kicked in, and I wake it up again, it comes back at 100, (and reads back as 100) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Fri Feb 3 15:50:28 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P7g9G0KH6z3kRnx for ; Fri, 3 Feb 2023 15:50:42 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P7g9F0Z5Vz3HqS for ; Fri, 3 Feb 2023 15:50:40 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Authentication-Results: mx1.freebsd.org; none Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 313FoUrf051414; Fri, 3 Feb 2023 07:50:30 -0800 (PST) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 313FoSft051413; Fri, 3 Feb 2023 07:50:28 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202302031550.313FoSft051413@gndrsh.dnsmgr.net> Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 In-Reply-To: <202302030846.3138kSMO006053@critter.freebsd.dk> To: Poul-Henning Kamp Date: Fri, 3 Feb 2023 07:50:28 -0800 (PST) CC: Emmanuel Vadot , "parv/FreeBSD" , freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4P7g9F0Z5Vz3HqS X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[freebsd]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > -------- > Emmanuel Vadot writes: > > On Thu, 02 Feb 2023 20:58:58 +0000 > > "Poul-Henning Kamp" wrote: > > > > > -------- > > > parv/FreeBSD writes: > > > > > > > > Does backlight(8) works for you? > > > > > > > > Thanks for the clue. It does! It does ... > > > > > > > > - I get the same number back via "backlight" without any arguments as > > > > what I gave it earlier. There was no reporting of value being > > > > subtracted by one; > > > > > > Sorry for the delay in reporting back. > > > > > > I consistently read one less back, except for 0 and 100. > > > > Even 50 ? > > # backlight > brightness: 0 > # backlight 50 > # backlight > brightness: 49 > # backlight 25 > # backlight > brightness: 24 > # backlight 75 > # backlight > brightness: 74 > > yes This smells like a zero-bias byte rounding issue... Ie, if the backlight intensity register is 8 bit, having values 0 to 255, and we scale 50% to 256 * 50% == 128 or do we scale to 255 * 50% == 127, and then reverse it as 127/255 == 49. > > > So if you have, let's say brightness at 50%, and you plug an external > > monitor, brightness goes up to 100% ? > > No, plugging and unplugging does not change the backlight. > > But when the screen saver has kicked in, and I wake it up again, it comes > back at 100, (and reads back as 100) > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > -- Rod Grimes rgrimes@freebsd.org From nobody Sat Feb 4 11:38:13 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P89WY2bZyz3n26Q for ; Sat, 4 Feb 2023 11:38:17 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P89WY26mCz3MGM for ; Sat, 4 Feb 2023 11:38:17 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675510697; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=qOwsQJhLuktbaDOu+d8SSWTk9BdE8s7ctOMFJ580w28=; b=CaYMRkFiyxhLpw8MSXIrEw/lhrmB9y7HOQsikdUu61K6MTIfFEbQOdppfWBqRlsjF7ylQn wInIzSaJo76UIxh5CZmoMobwDIy5nNUHYsc3CvH54mclHbm4wzhqWn67UrpckrntLifi2Y tHIa+MCxw4X3yJopel4lwKKrG9fHClks62qHMt1vJguZ0ZxovWtOpteET2hd1lFiQkfCil d9X8aoqPwWgK8wZhV2snVi9gMOFX8nXdXfuyvTjneLQjGoQ1a2Zv/TrtApHt3yJrmeolGM Fivk3WRwPpGLBB8r59CddQBmOaLYIAG+UPWW8vW6Jf9FMtujUTHuYd6S/BEE2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675510697; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=qOwsQJhLuktbaDOu+d8SSWTk9BdE8s7ctOMFJ580w28=; b=Tem37A9A84CHTA8I9N71hQGBDpvzK98UCB0w4r4eHbMK42fUAI55oX+49JACmRa4ryd9mG 0c7atvXkO3uQ/xecLgXcD/5J3elKLDijXyZd8wbmbWjCEO+6U8xcSM2hraGehqkwu3ifB8 NvCA1u4dmbgtQhFr4KooPXFpQ1WryNh6UN12cTWpnNuD5dIWTDvLBmtNZ7drH29sR4g6Uy KXOL2O0gIjSp0uniTrnNgzdZ04zcQet1Zr2T69g44ANvxuwgQqSv+pwaFQLVDiF5qQh64m 3nkjQRVeuWwGldNarcmxN9rY7mV9nhuqXJRwdYfnzC6ZDW6l++4ZzGa73lcHGw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675510697; a=rsa-sha256; cv=none; b=T0oHzC6ReHT6akGMKx7YnPJXJv8jyKx6lvZUN8A4zrCBQbZGAZDNiie3CttyT9mVuFzUXc KPdddDtmWZ8xHjwMCKauAsb2QQ8OePQIiKdsp7QmUiKUbD0HHy+5Oxis5YLtWUal1+jDtE i42XZf6uA4/IFARY0ZYzDNT+CYTOCB6jwhtOsOxTpKdYLQoXfVTIUPZKH+FLqoY0FswFIK 4645paYGXQU35a3t58UVgHQD5qu62T3X9061q2NrZYp1uohNcVCRCB33+Je+C3ymT6XC/O Yz1T8JJRG7zEEo7XF268sMOG/ku0DqmrrNOPUfT0j157nb2Ey4wdrddk4me1kA== Received: from [IPV6:2001:470:1f1c:a0::2] (tunnel642390-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:a0::2]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P89WX6FcPzMZb for ; Sat, 4 Feb 2023 11:38:16 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <9432fe2d-ecc5-bb65-10d2-e5dd98d0fbae@freebsd.org> Date: Sat, 4 Feb 2023 11:38:13 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: GitHub Code Search Content-Language: en-US To: freebsd-current@freebsd.org References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> From: Graham Perrin Organization: FreeBSD In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------LHJUTaw7xYoOt06yxmLYO5VB" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------LHJUTaw7xYoOt06yxmLYO5VB Content-Type: multipart/mixed; boundary="------------4c7zk9DBexl1sOmL0qgTq89a"; protected-headers="v1" From: Graham Perrin To: freebsd-current@freebsd.org Message-ID: <9432fe2d-ecc5-bb65-10d2-e5dd98d0fbae@freebsd.org> Subject: Re: GitHub Code Search References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> In-Reply-To: --------------4c7zk9DBexl1sOmL0qgTq89a Content-Type: multipart/alternative; boundary="------------H2Qi08cfZJEO5Tcf3jkGG05O" --------------H2Qi08cfZJEO5Tcf3jkGG05O Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMzEvMDEvMjAyMyAxNzo0NywgRGF2aWQgQ2hpc25hbGwgd3JvdGU6DQoNCj4g8KOApuKA piBUaGUgb2xkIEdpdEh1YiBzZWFyY2ggaXMgbm90IGdyZWF0LCBidXQgY3MuZ2l0aHViLmNv bSBoYXMgcmVwbGFjZWQgDQo+IGxvY2FsIHNlYXJjaCBmb3IgbWUgaW4gdGhlIEZyZWVCU0Qg dHJlZS4gSXQncyBub3QgKnF1aXRlKiBhcyBnb29kIGFzIA0KPiBmeHIsIGJ1dCBpdCdzIGNs b3NlLg0KPg0KPiBGb3IgZXhhbXBsZSwgc2VhcmNoaW5nIGZvciBzeXNfY2FwX2VudGVyOg0K Pg0KPiBodHRwczovL2NzLmdpdGh1Yi5jb20vP3Njb3BlTmFtZT1BbGwrcmVwb3Mmc2NvcGU9 JnE9c3lzX2NhcF9lbnRlcityZXBvJTNBZnJlZWJzZCUyRmZyZWVic2Qtc3JjKyANCj4NCg0K DQpJIGdldDoNCg0KPiBmYWlsZWQgdG8gZ2V0IG5vbmNlIGZyb20gc2Vzc2lvbg0KDQo= --------------H2Qi08cfZJEO5Tcf3jkGG05O Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 31/01/2023 17:47, David Chisnall wrote:

=F0=A3= =80=A6=E2=80=A6 The old GitHub search is not great, but cs.github.com has replaced local search for me in the FreeBSD tree. It's not *quite<= span class=3D"moz-txt-tag">* as good as fxr, but it's close.

For example, searching for sys_cap_enter:

https://cs.github.com/?scopeName=3DAll+r= epos&scope=3D&q=3Dsys_cap_enter+repo%3Afreebsd%2Ffreebsd-src+=


I get: 

failed to get nonce from session

--------------H2Qi08cfZJEO5Tcf3jkGG05O-- --------------4c7zk9DBexl1sOmL0qgTq89a-- --------------LHJUTaw7xYoOt06yxmLYO5VB Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmPeQ6UFAwAAAAAACgkQt2dIb0oY1AuA KA//eZ3Yn/pUzNtzlw5xSCrCI5MzNc+SXhTcxDah3Z1Y7pEqL/7kYRxEtJKI1+T2rWXaNS8LVHrd k0WIB3lMVIlbyiweawgrHCKUprGKDu5IJWb0BYA9CXmTVv6+v2JwJ4pv89wl+XACNd1CCBaI41JH miDDaP3NVgja9QzfnCy8J25y8wlzyX3Cq08hw+zdtLDBvP1hqFMjEUpIlLXwOt5/6thJp0o/fyLa pSokLDo+YPBaQfrRCcj99dl6wk77xUZeI3P6iDwEkhAI8X7gCwpl84uzhIVDC6T9RmvXtxJ1WDlM DFxdk4IzJOVDNvkF1PCvwZ3W2vtGHo/QCJYqO4R5V460VojmdchmKseUmnPWE8GCtII/4KQvkvkX q0zFQtvnxPM2AtaKYZ1hXQ3S0ADaH7zoum1AskMXEhufzzy1zIFBJNsqKK/GcdiaAckn1yqFvPxO 6LnvvFcciHsnLrhaXNAKBtndXok75HjYEf+75yy2r5+/X/lj2y2SWIhMW3d0obrn3vXYrYbZIHAc 8w9Bec6kxKQkKKr4eQm/HuWTe1UJod+OKy+tSMQQML+yEEx/JuWGVcN/IEVR7NL6PDxxd6I732If pzKYulDtEaVkVfcTfYfl40tO63QBjd5LmKCU7uYQW1UH7VS4xEpKds3x8D1qI75AzBmzf02AQzCE nWA= =NWsP -----END PGP SIGNATURE----- --------------LHJUTaw7xYoOt06yxmLYO5VB-- From nobody Sat Feb 4 11:40:39 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P89ZK2D1Wz3n1wY for ; Sat, 4 Feb 2023 11:40:41 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P89ZK1cgMz3NKW for ; Sat, 4 Feb 2023 11:40:41 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675510841; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=IoQ9XygWBNVNI9TK4qXZmLNXTAfNlc2gMs8JACLHS5Q=; b=ImVhUpQGGR9x52bOUNvM/zAPEx8iMYLj9RY0hKLsCWuk0Ntx1PAiBJVMdztAp2ARcicxLF FdnWvACcpsWFJNY/XuzCtNQuP7xOOTvmojCZaVFfZPVbyS/698Jac8NDcVmclE3oGk6UuC CLFmUe/BAatnOn7xX4xwYMv+mfE5/kPmQAyh9AADc6S/fpsTI3SrAjIPjIup/vhq02iMDC vOK7JACnFrk+o6UibEWnQAD0YUCD5WGkVUEWeXVRlsNHXYt9U4U5weAYvVGihwxbPjZYxR FPthyEdrnb3WEulFarHdSieryS8dNms04yTOWtXWu7qJM5zn/MIHZEZ0GqXi3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1675510841; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=IoQ9XygWBNVNI9TK4qXZmLNXTAfNlc2gMs8JACLHS5Q=; b=xilddQlUEXrVZD2it9l0ZKMKQLThqgVGnOE1X0+GtDHsKV53fHFW8r3GZW73IM+nop2aVm 53vyYTxSutBLA/TnsIgAaAaGtV5si5VW25GkSxTgGxcjg0EXRI9+y/wNWGS1yXMSeVETBl QDq9R1y6RIJo3Ngh3P2jh5lGWOIRyRhjLZ5sQ7Ci6mc2VoKMl3moSFpk0UsF69DxumbNsS YjOliiygS6c3yTZ4A/Dvah5Zf6Gchc/Em4BOilv1G2YkOhYiPsm9777yLHIzuryKficoIA GRMkjCAPejWfZHs2WbvHJS2tHb5PxOp6IjgIwjZYOF6FxVKk5H5RAR8vVmB3WA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1675510841; a=rsa-sha256; cv=none; b=s8hTZUI7nQnk2dswwGf+W7ujT1pBuM6ZFJZMrOWqy5Fzh36h3UyUhlXmAHKbBherUyCn04 7YrLgp+sru/Iy0nMxeCINqn70Aa3j+bgOE1Pp8NxpICxxfa5zHIGkoK+bkeNCprDbKJbuO KhAHesKRgIzx7uJperZaumVCkIEiJq1oIfZtBXxismX1BhVyIL4XM0kcU1Vd6jH7e4yVV2 /ZN0okPxVXD+woviNVNA+PxvZdcEljwJSlBWqQU9SfLuVWdcuGtmGPkaTuvTiGwXoOd/kH sMFofK9bzkN4PcF7c2wq/v/+60RkMmgiuvSA+2Z3ClgAVhpP6+wvl1TmRiWIxg== Received: from [IPV6:2001:470:1f1c:a0::2] (tunnel642390-pt.tunnel.tserv1.lon2.ipv6.he.net [IPv6:2001:470:1f1c:a0::2]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4P89ZJ6QjszN4C for ; Sat, 4 Feb 2023 11:40:40 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <2799847c-3e7f-a82b-75b1-d3b3df685f9a@freebsd.org> Date: Sat, 4 Feb 2023 11:40:39 +0000 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: Tooling Integration and Developer Experience Content-Language: en-US To: freebsd-current@freebsd.org References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <86edrcp13z.fsf@peasant.tower.home> <86zga0nf1q.fsf@peasant.tower.home> <86sffrohfn.fsf@peasant.tower.home> From: Graham Perrin Organization: FreeBSD In-Reply-To: <86sffrohfn.fsf@peasant.tower.home> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------Jht6Ow4IVTBJgEVrZUGHvOEd" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------Jht6Ow4IVTBJgEVrZUGHvOEd Content-Type: multipart/mixed; boundary="------------HTda2de87aE6Xv0rwKdhSq9c"; protected-headers="v1" From: Graham Perrin To: freebsd-current@freebsd.org Message-ID: <2799847c-3e7f-a82b-75b1-d3b3df685f9a@freebsd.org> Subject: Re: Tooling Integration and Developer Experience References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <86edrcp13z.fsf@peasant.tower.home> <86zga0nf1q.fsf@peasant.tower.home> <86sffrohfn.fsf@peasant.tower.home> In-Reply-To: <86sffrohfn.fsf@peasant.tower.home> --------------HTda2de87aE6Xv0rwKdhSq9c Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMzAvMDEvMjAyMyAyMTowOSwgRG1pdHJ5IFNhbHljaGV2IHdyb3RlOg0KPiBNYXliZSwg YnV0IG15IGxhemluZXNzIHdvbid0IGxldCBtZSBrZWVwIGl0IHRoYXQgc2ltcGxlIDopDQo+ IGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9IMTg1IHNob3VsZCBkbyB0aGUgdHJpY2ss IEkgdGhpbmsuDQoNCjQwNCBmb3IgbWUuDQoNCj4gV2FybmVyIExvc2ggPGltcEBic2RpbXAu Y29tPiB3cml0ZXM6DQrigKYNCg== --------------HTda2de87aE6Xv0rwKdhSq9c-- --------------Jht6Ow4IVTBJgEVrZUGHvOEd Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmPeRDcFAwAAAAAACgkQt2dIb0oY1AuM 6A/9EMQ3qZ4rwR1fXrm2bCOeLkAjanm+QKEfaYWSr1K4RgnRDweYPkIKHTBor5dV5fTBjnh4uGuq dC7ylDFlOt4+TyaTdFvsP0AalNcpEJsv99bxRRp2emx7/ii0+ZQNsF7ZcX7HB5nDhcf3Fz76m24G EbjhLbfOi9Mn0dMkjIohocZaeakXqa1CIOccptz0loULeZyyYj5Q9urIzd2N4WdR2bvCC+16Hyek vW92Pos7VpxhEhsa7SJWdMUdPwgcioEPTUwFWRfRODBNluN+n5cJdSG8ur9FsWJ2ngL8QaQzqE4N edtOv9OA5UQTjBRlI6jV7TFAjOcqGRqN1NY93BmLUyXph4rR7YFsiv/MNPCMqIo1Pug3qEJz2TNz Pg/Wd4iKOiQkAQCI3k8n/RiUIgtjrrOZOHOalLz/1fvsszwxrkQNnw0P18Xi8LoFNP73Y2e3LzIN u+nU76edxviTGJY4+9VJ6LkoCRSsL5X+02T6M7eb432T8L/UryK9vwC853EkipojRycUsOeMUtSl JAMHq+zjfE7lfSZ3KNmXqTjoRpCFTjbkIhH6CRh9w5P11DvFypnNVjYKDxwaPWmal0A9h0KRlxTA 6TXvXv6NRlhtK1n/zIrPK4LCA3WZu15XZ0FrpheA1XCqv6MVArzZAmnMapoL8N+OU50VbrhDPJ41 dkY= =f9CA -----END PGP SIGNATURE----- --------------Jht6Ow4IVTBJgEVrZUGHvOEd--