Unmaintained FreeBSD ports which are out of date
Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. Please consider also adopting this port. If any ports have already been updated, you can safely ignore the entry. An e-mail will not be sent again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ cad/ifcopenshell| 0.6.0 | blenderbim-221210 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
How do I depend on a port regardless of its flavor?
I'm working on a port that depends on a port which is flavored. If I do this: RUN_DEPENDS= foo:devel/foo That works because the lack of version spec means the LHS is a file to look for, and /usr/local/bin/foo will be installed regardless of flavor. But I need to also specify a version spec. However, if I do this: RUN_DEPENDS= foo>=1.2:devel/foo That only works if the default flavor is installed. If one of the non-default flavors is installed, the Ports System doesn't find it and tries to build the port. Similarly, pkg thinks I need to install the default flavor. The flavors aren't part of a framework like Python, so I don't have a set of variables I can use to construct a universal pkg name. How do I add a version-limited dependency on a flavored port?
Differing status reports fro the package build cluster
Hi all, I hope that someone can shed light on why I am seeing differing status messages from the package build cluster. If I look at the report on: https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1 the status on 131amd64 default (on beefy16) is: parallel_build, started 10 December. If I look at the same url but with the "latest only" filter, the same jail has a status of stopped:done with a started date of 6 December. I'm assuming that the "all" view is current but does anyone know why they show differently? Thanks for any enlightenment! Simon. smime.p7s Description: S/MIME Cryptographic Signature
RE: Differing status reports fro the package build cluster
Simon Wright wrote on Date: Mon, 12 Dec 2022 00:13:20 UTC : > I hope that someone can shed light on why I am seeing differing status > messages from the package build cluster. > > If I look at the report on: > > https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1 > > the status on 131amd64 default (on beefy16) is: parallel_build, started > 10 December. When I just looked at 86b787b900a8 (a default Ports), it still listed 1126 Remaining: so not done. The prior completed one (0 Remaining) is listed as 908640ce3450 . > If I look at the same url but with the "latest only" filter, the same > jail has a status of stopped:done with a started date of 6 December. https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package shows: 908640ce3450 as well, the same completed one as on the other page. > I'm assuming that the "all" view is current but does anyone know why > they show differently? They agree about what has completed, at least for now. === Mark Millard marklmi at yahoo.com
Re: Differing status reports fro the package build cluster
On 2022-12-12 10:36, Mark Millard wrote: Simon Wright wrote on Date: Mon, 12 Dec 2022 00:13:20 UTC : If I look at the report on: https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1 the status on 131amd64 default (on beefy16) is: parallel_build, started 10 December. When I just looked at 86b787b900a8 (a default Ports), it still listed 1126 Remaining: so not done. The prior completed one (0 Remaining) is listed as 908640ce3450 . If I look at the same url but with the "latest only" filter, the same jail has a status of stopped:done with a started date of 6 December. https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package shows: 908640ce3450 as well, the same completed one as on the other page. I'm assuming that the "all" view is current but does anyone know why they show differently? They agree about what has completed, at least for now. OK, I get it; the report filtered on "View latest only" is only updated when the build for that git hash is complete however the current status of the build boxes - including builds in progress - is shown on the "View All" filter. Thanks for the insight Mark.
Re: Differing status reports fro the package build cluster
On Sun, Dec 11, 2022 at 7:35 PM Simon Wright wrote: > On 2022-12-12 10:36, Mark Millard wrote: > > Simon Wright wrote on > > Date: Mon, 12 Dec 2022 00:13:20 UTC : > > > >> If I look at the report on: > >> > >> > https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1 > >> > >> the status on 131amd64 default (on beefy16) is: parallel_build, started > >> 10 December. > > > > When I just looked at 86b787b900a8 (a default Ports), it still listed > 1126 > > Remaining: so not done. > > > > The prior completed one (0 Remaining) is listed as 908640ce3450 . > > > > > >> If I look at the same url but with the "latest only" filter, the same > >> jail has a status of stopped:done with a started date of 6 December. > > > > https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package > shows: > > > > 908640ce3450 as well, the same completed one as on the other page. > > > >> I'm assuming that the "all" view is current but does anyone know why > >> they show differently? > > > > They agree about what has completed, at least for now. > > OK, I get it; the report filtered on "View latest only" is only updated > when the build for that git hash is complete however the current status > of the build boxes - including builds in progress - is shown on the > "View All" filter. > > Thanks for the insight Mark. > This is close, but you need to realize that the packages will only be available when they have been copied to all global distribution sites, so the fact that the run has been completed does not mean that the packages built on htat run are available. The time to distribute varies with the size of the run and network performance. It has greatly improved during hte past year as mirrors in some places are getting higher speed connections. I should also note that pkg-status data only updates the display on a reload. Updates from the IPv6-onlybuild systems do update every 10 seconds. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Re: Differing status reports fro the package build cluster
On 2022-12-12 14:50, Kevin Oberman wrote: On Sun, Dec 11, 2022 at 7:35 PM Simon Wright wrote: On 2022-12-12 10:36, Mark Millard wrote: Simon Wright wrote on Date: Mon, 12 Dec 2022 00:13:20 UTC : If I look at the report on: https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1 the status on 131amd64 default (on beefy16) is: parallel_build, started 10 December. When I just looked at 86b787b900a8 (a default Ports), it still listed 1126 Remaining: so not done. The prior completed one (0 Remaining) is listed as 908640ce3450 . If I look at the same url but with the "latest only" filter, the same jail has a status of stopped:done with a started date of 6 December. https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package shows: 908640ce3450 as well, the same completed one as on the other page. I'm assuming that the "all" view is current but does anyone know why they show differently? They agree about what has completed, at least for now. OK, I get it; the report filtered on "View latest only" is only updated when the build for that git hash is complete however the current status of the build boxes - including builds in progress - is shown on the "View All" filter. Thanks for the insight Mark. This is close, but you need to realize that the packages will only be available when they have been copied to all global distribution sites, so the fact that the run has been completed does not mean that the packages built on htat run are available. The time to distribute varies with the size of the run and network performance. It has greatly improved during hte past year as mirrors in some places are getting higher speed connections. I should also note that pkg-status data only updates the display on a reload. Updates from the IPv6-onlybuild systems do update every 10 seconds. Noted Kevin, thank you. smime.p7s Description: S/MIME Cryptographic Signature
