Re: git: 56b5ec772f67 - main - all: Bump PORTREVISION after lang/go{119,120} update

From: Michael Gmelin <grembo_at_freebsd.org>
Date: Wed, 08 Mar 2023 14:20:43 UTC

On Wed, 15 Feb 2023 14:33:43 -0500
Dmitri Goutnik <dmgk@FreeBSD.org> wrote:

> On 15/02/2023 14:07, Dmitri Goutnik wrote:
> > The branch main has been updated by dmgk:
> > 
> > URL:
> > https://cgit.FreeBSD.org/ports/commit/?id=56b5ec772f679a600dabe41622c1350594628286
> > 
> > commit 56b5ec772f679a600dabe41622c1350594628286
> > Author:     Dmitri Goutnik <dmgk@FreeBSD.org>
> > AuthorDate: 2023-02-15 11:36:35 +0000
> > Commit:     Dmitri Goutnik <dmgk@FreeBSD.org>
> > CommitDate: 2023-02-15 19:06:01 +0000
> > 
> >      all: Bump PORTREVISION after lang/go{119,120} update  
> 
> So just to answer the obvious question - no, I'm not planning to
> rebase and merge this monstrosity to quarterly.
> 
> If there are no objections from ports-secteam@, I can bump
> PORTREVISIONs in 2023Q1 by a direct commit.
> 

Hi,

I just stumbled over an unintended side-effect of this: I had a problem
with node-exporter that had been fixed in main in version 1.5.0_1:

https://cgit.freebsd.org/ports/commit/?id=ede3d9baa55c5670f9243191e390f1a8bfddcd4c

Meanwhile, node-exporter on 2023Q1 was bumped to the same revision:

https://cgit.freebsd.org/ports/commit/sysutils/node_exporter?h=2023Q1&id=9ff952570bc5120a01d31a8406f17ad49ddfb2e9

So it took me a while to realize that "my" version 1.5.0_1 of
node-exporter didn't contain the fix and the bug already had already
been fixed in main.

Not a huge deal, but slightly confusing.

Best
Michael

-- 
Michael Gmelin