From nobody Wed Jan 3 22:52:04 2024 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 4T54jS3lyhz56slb for ; Wed, 3 Jan 2024 22:52:12 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4T54jS1G4tz4gd2; Wed, 3 Jan 2024 22:52:11 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 403Mq4pa034511; Wed, 3 Jan 2024 22:52:04 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 403Mq4qV034510; Wed, 3 Jan 2024 22:52:04 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202401032252.403Mq4qV034510@donotpassgo.dyslexicfish.net> Date: Wed, 03 Jan 2024 22:52:04 +0000 Organization: Dyslexic Fish To: jamie@catflap.org, brooks@freebsd.org Cc: dvl@freebsd.org, yuri@freebsd.org, freebsd-current@freebsd.org Subject: Re: git repo port issues? References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> In-Reply-To: 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 [209.250.224.51]); Wed, 03 Jan 2024 22:52:04 +0000 (GMT) X-Rspamd-Queue-Id: 4T54jS1G4tz4gd2 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] Brooks Davis wrote: > Nothing about dates is centralized in git, but some server side checks > could be implemented on CommitDate. IMO we should require that > CommitDate be >= the previous one and less than "now". Ah, I realised Linux doesn't like centralised dates, because of the decentralisation of git, but I thought that as we grabbed from a master repo, those commit dates would be in sync. Anyway, I think some sanity checking would be good. If nothing else, this sort of thing breaks "git log": # git log --since=2023-02-02 --format="%cd %s %cn - %cd" Wed Jan 3 17:08:58 2024 -0500 editors/cudatext: Update to 1.206.5 Jose Alonso Cardenas Marquez - Wed Jan 3 17:08:58 2024 -0500 Thu Jan 4 06:59:31 2024 +0900 net/qrcp: update to 0.11.1 Hiroki Tagato - Thu Jan 4 06:59:31 2024 +0900 Wed Jan 3 16:54:47 2024 -0500 lang/fpc-devel: Update to 3.3.1.20240103 Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:47 2024 -0500 Wed Jan 3 16:54:46 2024 -0500 lang/fpc: fix stage-qa fails Jose Alonso Cardenas Marquez - Wed Jan 3 16:54:46 2024 -0500 Wed Jan 3 16:53:33 2024 -0500 sysutils/acpi_call: Check for errors from copyout() Mark Johnston - Wed Jan 3 16:53:33 2024 -0500 Wed Jan 3 15:37:13 2024 -0600 math/octave-forge-statistics-resampling: Update to 5.5.3. Stephen Montgomery-Smith - Wed Jan 3 15:37:13 2024 -0600 Wed Jan 3 23:00:58 2024 +0300 math/z3: Unbreak on i386 Gleb Popov - Wed Jan 3 23:00:58 2024 +0300 Wed Jan 3 20:52:14 2024 +0100 devel/mongo-c-driver: Use USE_GITHUB helper and always use (lib)utf8proc from ports Daniel Engberg - Wed Jan 3 20:52:14 2024 +0100 Wed Jan 3 22:26:11 2024 +0300 lang/ghc: Unbreak GHC 9.2 on AArch64, refresh bootstraps. Gleb Popov - Wed Jan 3 22:26:11 2024 +0300 Note how I specified February 2023, yet the output stops as soon as it reaches the recent entry with the rogue date. That makes the results corrupt, which may affect other things along the line. I notice the front page of Freshports doesn't even show the offending entries in the list of recent commits, for example, whilst the individual port pages shows the commits in the "wrong" order (i.e. the commits are displayed in the perceived chronalogical order) https://www.freshports.org/misc/py-laspy https://www.freshports.org/graphics/filament