From nobody Fri Oct 10 20:51:41 2025 X-Original-To: freebsd-pkg@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 4cjzSZ4k7Mz6Bxr7 for ; Fri, 10 Oct 2025 20:51:58 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-22.consmr.mail.gq1.yahoo.com (sonic301-22.consmr.mail.gq1.yahoo.com [98.137.64.148]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4cjzSZ2Bf6z49l5 for ; Fri, 10 Oct 2025 20:51:58 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1760129515; bh=AIIWK07oQAAGeYpyo6wtRqpbhJDYWJPqxqWtKDYu5Mo=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=BuxkG5KAP9aZW8ramVW7WNCPfZxEeqn73Z89ozy8jq37wCgzlqvn0/gc5lpVIp+Ux8y5VJqH2AKogmbEUEvSeJjnONudNme1F5T8Q0I8G7/nmIFeuL/AjejAPUl31nO3e0kQIDPotnTYrX/QYh8sx3YwCmM+wPR5/kAQaKJpIxICTCPqmZFzxnoqdDye3QYlxtfjuoy79FhGy98Zay3QNTCJeECut0Qedyl54tDGVPnPnIgqEa2CFFH23DSPkVqrLgX6v++PF/54/Ueon1h/Lb8lIJ4EiVtNaIickwUdcRsIo56wSHlxqJo7PEmA3ftE/66ZytK2QMcrFo/ezfAuUw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1760129515; bh=y/mx8KC5b0Q7UsiwZmV8KoQYQkNs2saouhza7Y3N+jl=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=TPfLuPPHmhtwRDC8pUMnOZlXLQWQEniSf5QeSFHzYB3knYkmkdWLbhuaTb+PKmhFDnDbKJ9Yw/vHYuYJUaixIrgc/xL+a/X1VHTDh9fLv2mLx8bBSF+QshmqDtqz0C0ohoaJ8ASRBaqszxLt8BbaaL0NZKqvuS89nNn4TzLHv+NW9+Y/M/TEVTNYCz6E+1OLOBKKd+VHUh757LDIB0n4mkPncpcAMbjXf4bBDzqM3tFiOwyvFepZ4QPQn0/jIScKVAMrSEKja8Z6fWAIm2R8Ex0rcPsx2NqjOUXddX/WNfUwwnV3kTNAz6i7oYPrzwohgRJsqT/t8ynYp1g7+d6V0Q== X-YMail-OSG: 9NImv4oVM1l_tR3Lyu_Vbn_K7h23BzCrJOrosfRRqFgpVkYKFuD5F1ujl4uj0dl rcK.zWUCLwUib.Zeh1ebGuHPTj2yO_j2ttkIlh3Z5.7nDoflX_vL6Pseirp8uYFMckb7gfcsiFWP H1fthdJ9_P_2uZ24qbWwkEiD_lrnDRbXyNdj73hy7XLs1NK3_vcwsezmd2d9v7F_f9_EV6RMwYyK vSBt_piaZUndRunVvCSppS5bjmqgNdyTXECLgf8npIJ.CUDS28a2ZDDNCiw2xgOlp7QqKkgK0lzC c4vBMSVg8qzuXXaQhVfpADXJgRCj1V0C3FI.v8vNVDxegVyUAnMkubvud6Sg09pVUs7mfYi__PUn 3dzfClCbGxIru3zCzHHO_QWG4v8qTeLUN3FDsrFHfTw2eaUUtaaauLPiBFygFriQ9fKbZG52zi2M FQmdHvai_1EN6ciMPdp8w.3jSEYDHJFnRemFrK4tSCIF04L9mCqcpASJKswkGi1mIrWE4a84g64i wunQvgy1ArN_p5RsJLHCFj7uqKGdQ6XA.UwGk.veFlB_n1jxX_R3qQFKkrh9785Xnik0U.J1OEwb O11lQIoXJwZWeFdJ0PFTJJszNH32o57JHvt20uolzQ6g34xicaWnEG64iz9vi_V3PqEFN4S9Eacb zh_9185Y0PeSpvrka64Ds021w3crl84EQvqjnbfOV4J6jes8Fm_B7kuA4GY5bca_zni4Igh5Egd3 JsnIjQaZHOdUw7ktLJcTciaHMNJFu2vz75hSe2eTTbuj.YyhBJ.XBMIuAC62ECzEdqwzdM5SLIUg j_vTpZfRBOwebbUUkK1JwAX50ZA_Ucg9ugHWEtNepj1N4dOb7uohjyfiB1uFJtNe.xJhoqaeoPa9 Ar2z6W.YJY1iKQ68pfF2NZR_lHXckVfx42VOF11uTned5dtiUemVQbd5vMRJPnESdshpuV5WoX9p VmmVax.UTHT8Y9hHwMol154Fcs_3oSgRZiMcBpLvYKVha.1reSxJoeLC5lZ.ClaBt.tVkt5Fm8aw 6GGs_Hd_saR7q1M3wR9R8vQF1eNhisuvksNP_KKhUiW1lTyyu9hyZ87o2uEaZd7Z5R97NmquNMsa Ur3tzhEKf7WcOmd17YGVVfXAcMxzPjF1q_xtV8Q9bgT7Qhw7yrWhBC2Zzaho770Yj7iRo8SXtj40 pZO9tjSmKWhhWuxFNDViVExnhWoXTsVcpIpiQXiIbY2rjsVJMwEloSJiBfA2BMW6hPVO.LdDeK5e Wu8CglHt0wPy4j77JB.Bt9Fsa8G.PV6MNrPXN0A5gTmUHgwshnQGtDIHjUwYolsQZD6eSXm_3oXn Vu5AsZiT.WEyxFDSeAKV4FV4WLuE7diMLRT_kpMJr6WRKH7YvFphP5ihoQSmWRLRuuWhy607sK7h o7R56K8C7yzMBjbHuXrPPOU0WFLPruBpsNnrNnCJedF41FyAYiPIDiNz9ftv8ybySf_Buba1bQlR s5qUYcf7HntuWtujO5lymMyPNyVdXv9cLFBQ_4oICrGwWg7LutdyHwcrvUfk70BoI.Ayf0vuN6IJ jJKvFB0NtWNtFeCNjxfJV9N8Ixr52V6y6j9oVfJAXvt9Y6EUiyvw8RzFd8fuA_KEEGCrFtoVuA_i TtVhUvRNeH9UA7MfM79iyi70567ZcSkSr_hvYZ4h36mxntuQUh_wt86cHs3C9r2lTq5KXh9yOjJo ftuplvbFnQli9lUA8Sau1TGyVBREfnAOlYcSWIvpDtTrdJezALOqUBzhfgQ9zfe1ByEVTK147azh SMbo3OMZutA3iqetMKcD2d15B1FSEPxzS0GsTSkiep3WEkOVOJACi_6UIR7zD84yRWsE1am9lIuI 9VQbkxCPAWIda4ztcGyAoEO2RF6VVJnlJ9x31pRsLs6ymFsx1lq5uA1seqfQRDMALacal_0XMKn8 PKseBQTk5qIpKFIeFNBzKhD.C1a5QyCA8LhyVlkCSd0aC_o5ozeB6az7fr7a1as3qKSAuUlet7LZ aigbVAStAAAmDg2IT_dPfRU8eEsA7PbjTb5Osr9my5JhLak2z_LeuJtMvJXFzu3FBg9XE5UXOLVW QCoeWyt9jUV55pUZtmM6aSSZSzUdsyzay0FXP3hdrVZ3SKiD7ynn4wW0DkuRZ6cApcR1LDLxZED7 WIfGqAqSE0uDXTdSC3AgRvmyWPkJB37C85cq1TXLPVq98rwrE.mq3q2_v372n8S_M.nDnl1utM7j PqH5bjWVocULoj1RLxv4ByyITeQCTJWQnEubvvyVLeP5hsh6NJlBOcbEucDC_ukTAw8keCLRuQ36 IPFliwQ-- X-Sonic-MF: X-Sonic-ID: 1b84ad4f-2c0d-42b8-b8e9-4c1db6fb9936 Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.gq1.yahoo.com with HTTP; Fri, 10 Oct 2025 20:51:55 +0000 Received: by hermes--production-gq1-66b66ffd5-kfn4g (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID c4a89ab8220c3ae15750e71b82de3983; Fri, 10 Oct 2025 20:51:52 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Binary package management and package tools discussion List-Archive: https://lists.freebsd.org/archives/freebsd-pkg List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkg@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\)) Subject: Re: FYI: 15stable-amd64-quarterly has had 2 successful builds, despite not being distributed yet From: Mark Millard In-Reply-To: <2468720.gG0HsuGxDd@ravel> Date: Fri, 10 Oct 2025 13:51:41 -0700 Cc: freebsd-pkg@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <6109335.Zv9zXsTiuT@ravel> <2468720.gG0HsuGxDd@ravel> To: Olivier Certner X-Mailer: Apple Mail (2.3826.700.81) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cjzSZ2Bf6z49l5 On Oct 10, 2025, at 06:55, Olivier Certner wrote: >> I like "Total" for the above. >=20 > Great. >=20 >> Are you suggesting to change the content of the that list >> and the whole page to make no reference to the "scope >> of the build" information (no count, no list for such)? >=20 > We should probably keep it, as it has (like all the other lists on the = page) a search box that can be used to determine quickly if a package = was supposed to be addressed. >=20 > Adding a status column to that list would be useful. It would say = either: > - "Up-to-date" in case of an incremental build and the package already = exists. > - Any of the already existing statuses ("Built", "Failed", "Skipped", = "Ignored", "Fetched", "Remaining"). > With this, users can jump to the relevant status-specific table and = consult the additional columns there (such as Log) for a specific port. = This makes it easier to find the fate of a specific package by not = having to search in all tables. We can then imagine refinements (a link = automatically filling the search box of the right table and jumping to = it), but already just having the status info seems valuable. Official builds are probably almost always "bulk -a" or "bulk -ca" instead of a more specific list, leading to the Queued Ports "Reason" column then saying "listed" for everything and all port-packages to be considered for further classification. In other cases, the Queued Ports list could be smaller. And that makes another reason for use of "All . . ." naming to be inappropriate. Your idea above does involve updating rows of a frequently large table on the fly instead of adding new rows as builds complete. An alternative would be to just have something like "already built at start" and "not yet built at start". That would be more of an up-front, one-time large-table build. That could make an implementation more likely to happen --or happen sooner than the above, possibly forming a separate step in a sequence of updates. The first submittal is: https://github.com/freebsd/poudriere/issues/1264 and sticks to the simpler, more-static extra column --and only as an optional thing going with the rename to "Build scope" (instead of "Queued Ports"). It may be a bit before I submit anything for the dynamic table update idea that would have more detailed information. >> Are you suggesting that the list should only list the >> port-packages that are in the "Total" and, so, that >> the "entries" figure would have the same value as >> "Total"? >=20 > No. And, if we add the status column as evoked above, I don't think = there is a need to even add this list of non-up-to-date packages as a = separate section. Okay. >> (Calling the items ports when a port can define multiple packages >> and pacakges are what is built is odd these >> days --and has been for a long time.) >=20 > If you view a port as an origin + a flavor, there's still a 1:1 = correspondence, but that doesn't seem to be the common acceptation for a = "port" and could be considered a stretch of the mind. That's why using = "packages" seems preferable to using "ports". Not too sure if saying = "port-packages" is better, as it might cause more confusion. I listed "port-packages" because there are now also "base-packages" and pkg has established a repeatedly-used context where just "packages" (a mix of both types) are handled without distinctions when pkgbase is also in use --and this has lead to some confusions of its own that I've observed. So I'm personally biased to be explicit whenever only one of the 2 types is involved/relevant. (Not the same as everything needing to follow my convention for dealing with the issues.) >> So if the "scope of the build" information is >> kept, I expect that its terminology should be >> changed to avoid ambiguity. >>=20 >> I could imagine having lists and figures for >> both: >>=20 >> ) "Total's port-packages" >> and: >> ) "All port-packages" >=20 > I really think these two terminologies are too close and thus = confusing (why would the "Total" and "All" numbers differ? that's really = unintuitive). "Build scope" seems much better (further improvements = welcome). See earlier above about my own reason for "All port-packages" to be inappropriate. Okay. "Build scope" is what I referenced in: https://github.com/freebsd/poudriere/issues/1264 >> Note: >> If I understand right, such may well be changes to >> how poudriere works for providing html pages. I looked around and found that the build-details page is from poudriere output during the build (poudriere-devel context example): # grep -r "card-body" = /usr/local/poudriere/data/logs/bulk/.html/build.html=20 /usr/local/poudriere/data/logs/bulk/.html/build.html: =
Build
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Jobs
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Built Ports
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Skipped Ports
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Inspected Ports
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Ignored Ports
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Fetched Ports
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Queued Ports
/usr/local/poudriere/data/logs/bulk/.html/build.html: =
Remaining Ports
(While I do personal poudriere-devel builds, I do not use the web page interface for my own builds, just for monitoring the official FreeBSD build activity. So this was not familiar.) > All these changes are cosmetic except the new status column in the = "Build scope" (or whatever) list. That specific change is anyway a = nice-to-have and could be done separately in a second step once the = existing names are fixed, which really is the priority. >=20 Sounds like separate submittals against poudriere on FreeBSD's github. I've started with the first submittal being: https://github.com/freebsd/poudriere/issues/1264 =3D=3D=3D Mark Millard marklmi at yahoo.com