Re: Listing packages built for a random release/architecture
- In reply to: Kevin Oberman : "Re: Listing packages built for a random release/architecture"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 10 Sep 2024 05:05:20 UTC
El mar, 10 sept 2024, 0:49, Kevin Oberman <rkoberman@gmail.com> escribió: > > > On Mon, Sep 9, 2024 at 2:10 PM Fernando Apesteguía < > fernando.apesteguia@gmail.com> wrote: > >> >> >> On Mon, Sep 9, 2024 at 8:58 PM Kevin Oberman <rkoberman@gmail.com> wrote: >> >>> >>> For amd64 V14.?, you can go to >>> https://pkg-status.freebsd.org/beefy22/jail.html?mastername=140amd64-defaultThis >>> is a list of all builds for 14. (Packages are always built for the oldest >>> supported minor release of each major version. Minor updates must not break >>> the system ABI, so 14.0 builds should work for all V14 systems. The >>> exception is kernel modules which get messy, but not binutils. >>> >>> Unfortunately, builds on hte new Chicago build systems are no linger >>> ordered by time, but by hash. The last build is highlighted yellow, but it >>> will likely not include all packages, so you have to find the last few >>> builds and walk back over them to find binutils. Fortunately, binutils >>> was updated in the latest build completed yesterday. For cases where you >>> need ot go back, here is a list of the most recent builds for 140amd64: >>> f550157a18a4 >>> 46b3743b8460 >>> 50625859d806 35743 >>> 60a177caf143 5734 >>> ff9b1b7bdb15 750 >>> ac90984a4ba1 1649 >>> 1963f6d23107 9924 >>> 3efa6621722c 14528 >>> b3cf46924d98 10287 >>> a760f6876277 1307 >>> 935c61ac4bff 3346 >>> 15d22e1c70da 9178 >>> 1b6eada811a7 3353 >>> 59e63aec278e 11646 >>> 94b089c7ad30 5477 >>> b9994ae18767 35841 >>> 13f486017d78 19763 >>> >>> Newest at the bottom. the second column is the number of packages built >>> in the build. >>> >>> I really hope that this is improved! >>> >> >> Thanks! >> This is what I was looking for. >> >> Now, how do you exactly go from https://pkg-status.freebsd.org/ to >> https://pkg-status.freebsd.org/beefy22/jail.html?mastername=140amd64-default >> ?? >> Because in the main page, if I filter in "Package Builds" using the text >> box at the right, and type "140", I get 15 entries, and none of them has >> the 13f486017d78 >> <https://pkg-status.freebsd.org/beefy22/build.html?mastername=140amd64-default&build=13f486017d78> >> hash for the build. >> In addition if I click on >> <http://gohan02.nyi.freebsd.org/build.html?mastername=14stable-amd64-quarterly-baseline&build=59d8804dcdd7> >> 59d8804dcdd7 >> <https://pkg-status.freebsd.org/builds/baseline:quarterly:14stable-amd64:59d8804dcdd7:gohan02> >> and try to go to the poudriere build, my system can not reach >> http://gohan02.nyi.freebsd.org/build.html?mastername=14stable-amd64-quarterly-baseline&build=59d8804dcdd7 >> >> Cheers. >> > > Since the new builders are in Chicago, it's not surprising > gohan02.nyi.freebsd.org > <http://gohan02.nyi.freebsd.org/build.html?mastername=14stable-amd64-quarterly-baseline&build=59d8804dcdd7> > does not get you there. ATM, this is a bit of a mess. I hope it will be > fixed, the pkg-status does not yet talk to the new Chicago systems, so the > last build in New York will be the last that shows up directly on > pkg-status. As far as I can tell, only 140amd64 is no a new builder. I do > see one build of 140i386-default on beefy21. Looks like 14amd64-monthly > might be headed for beefy20, but it doesn't seem to be loading now, so it > might not be production, yet. > > Wish I could be more helpful, but I just poke around and see what I can > find. > You were very helpful. Thanks for the information -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >