Bug 260152 - Listings via pkg-status.freebsd.org appear outdated for main-amd64, main-arm64 (FreeBSD:14:aarch64) …
Summary: Listings via pkg-status.freebsd.org appear outdated for main-amd64, main-arm6...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Package Infrastructure (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Port Management Team
URL: https://pkg-status.freebsd.org/builds...
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2021-11-30 23:53 UTC by Graham Perrin
Modified: 2023-10-06 06:55 UTC (History)
3 users (show)

See Also:


Attachments
Screenshot: ports-mgmt/pkg at beefy18 and in FreshPorts (222.00 KB, image/png)
2021-12-01 01:26 UTC, Graham Perrin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin freebsd_committer freebsd_triage 2021-11-30 23:53:20 UTC
For example, at <https://pkg-status.freebsd.org/builds?type=package> seeking: 

main

– finds nothing more recent than 2021-09-08 (September). 

For main-amd64 the run reportedly began in June. 

Underlying: clicking through to <http://beefy18.nyi.freebsd.org/jail.html?mastername=main-amd64-default>, the latest build does have logs from June. 

That can't be true, can it? (We're nearly in December.)
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2021-11-30 23:57:52 UTC
Sorry, is this a duplicate of bug 253130?
Comment 2 Steve Wills freebsd_committer freebsd_triage 2021-12-01 00:11:36 UTC
(In reply to Graham Perrin from comment #0)
Searching main, I see:

default	default	main-armv7	pfda1da2d7917_s9939af1a16	31668	15034  (+332)	620  (+528)	15559  (+9350)	455  (+31)	0	stopped:crashed:	Wed, 08 Sep 2021 12:37:55 GMT	98:50:08	beefy12

but I'm not sure why you're searching main. Clear search and sort by latest and at this very moment, this is the latest:

default	default	130amd64	401d71441a09	1109	604  (+116)	28  (+1)	56	421	0	stopped:done:	Tue, 30 Nov 2021 01:03:39 GMT	07:48:34	beefy16

which links to:

https://pkg-status.freebsd.org/builds/default:default:130amd64:401d71441a09:beefy16

which links to:

https://pkg-status.freebsd.org/builds/default:default:130amd64:401d71441a09:beefy16

which all seems fine to me, but maybe I'm missing something.

(In reply to Graham Perrin from comment #1)
That looks to be a separate issue.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2021-12-01 00:33:42 UTC
^Triage: Correct Assignee
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2021-12-01 00:57:31 UTC
(In reply to Steve Wills from comment #2)

> … why you're searching main. …

I use FreeBSD-CURRENT
Comment 5 Graham Perrin freebsd_committer freebsd_triage 2021-12-01 01:26:52 UTC
Created attachment 229823 [details]
Screenshot: ports-mgmt/pkg at beefy18 and in FreshPorts

(In reply to Graham Perrin from comment #0)

> … <http://beefy18.nyi.freebsd.org/jail.html?mastername=main-amd64-default>, the latest build …

beefy18, to the left (main-amd64-default) shows the latest build of ports-mgmt/pkg as: 

    pkg-1.16.3

FreshPorts, to the right shows: 

    1.17.5 

– for FreeBSD:14:amd64, with a repo build date of 2021-11-26.
Comment 6 Steve Wills freebsd_committer freebsd_triage 2021-12-01 02:55:32 UTC
(In reply to Graham Perrin from comment #4)

I see! :)

(In reply to Graham Perrin from comment #5)

Hmm, there do seem to be newer builds:

http://beefy18.nyi.freebsd.org/build.html?mastername=main-amd64-default&build=pd99f40d544e4_sc3134a6af0

But they're hard to find, not linked from the "Latest build" and pkg-status isn't getting the info. Will have to look into it more.
Comment 8 Graham Perrin freebsd_committer freebsd_triage 2022-03-31 20:01:27 UTC
Gentle bump
Comment 9 Graham Perrin freebsd_committer freebsd_triage 2022-05-30 04:52:30 UTC
Example workaround (thanks to marklmi#1172 in Discord): 

1. <https://pkg-status.freebsd.org/?type=package&all=1> (view all)
2. search (filter for) main-amd64
3. use the 'Started (UTC)' column to sort, if required.
Comment 10 Graham Perrin 2023-10-06 00:19:53 UTC
Since pkgmgr@ was created, should the assignee change for this report?
Comment 11 Antoine Brodin freebsd_committer freebsd_triage 2023-10-06 06:55:37 UTC
No, I don't manage pkg-status