Date: Sat, 03 Feb 2018 07:25:46 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: Mark Linimon <linimon@lonesome.com>, MANTANI Nobutaka <nobutaka@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r460814 - head/www/w3m Message-ID: <201802031525.w13FPkPG004608@slippy.cwsent.com> In-Reply-To: Message from Alexey Dokuchaev <danfe@FreeBSD.org> of "Sat, 03 Feb 2018 14:40:01 %2B0000." <20180203144001.GB10426@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20180203144001.GB10426@FreeBSD.org>, Alexey Dokuchaev writes: > On Sat, Feb 03, 2018 at 08:33:28AM -0600, Mark Linimon wrote: > > On Sat, Feb 03, 2018 at 02:12:57PM +0000, MANTANI Nobutaka wrote: > > > Remove PORTREVISION that should be removed in the previous update. > > > > Well, once it is in, it must stay in, if I understand things correctly. > > It was fixed pretty fast, so it's probably OK (typically I'd agree, hence > I've said "FYI"). I've been in that situation, when an upline vendor sends patches, forgets to remove PORTREVSION and I don't catch it. It sucks but it is what it is. Due to timing of mirror updates and people running svnup someone may have a port with PORTREVISION and when PORTREVISION is bumped to 1 again said persons will not receive an update. It's not OK. Either revert the change or increase PORTEPOCH. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201802031525.w13FPkPG004608>