Re: git: 8ecb1f814114 - main - Revert "lang/rust: Update to 1.63.0"

From: Baptiste Daroussin <bapt_at_FreeBSD.org>
Date: Thu, 25 Aug 2022 13:56:01 UTC
On Thu, Aug 25, 2022 at 03:42:09PM +0200, Piotr Kubaj wrote:
> On 22-08-25 15:24:12, Baptiste Daroussin wrote:
> > On Thu, Aug 25, 2022 at 02:21:28PM +0200, Piotr Kubaj wrote:
> > > On 22-08-25 14:08:26, Baptiste Daroussin wrote:
> > > > On Thu, Aug 25, 2022 at 10:50:30AM +0000, Piotr Kubaj wrote:
> > > > > The branch main has been updated by pkubaj:
> > > > > 
> > > > > URL: https://cgit.FreeBSD.org/ports/commit/?id=8ecb1f8141144c1603eb4026122d2e60eeaccd64
> > > > > 
> > > > > commit 8ecb1f8141144c1603eb4026122d2e60eeaccd64
> > > > > Author:     Piotr Kubaj <pkubaj@FreeBSD.org>
> > > > > AuthorDate: 2022-08-25 10:29:24 +0000
> > > > > Commit:     Piotr Kubaj <pkubaj@FreeBSD.org>
> > > > > CommitDate: 2022-08-25 10:49:36 +0000
> > > > > 
> > > > >     Revert "lang/rust: Update to 1.63.0"
> > > > >     
> > > > >     This reverts commit f36cc819accadae1fefc14c203e5fbe9c74e1492.
> > > > >     
> > > > >     I asked for an exp-run for powerpc and powerpc64 on a recently provided
> > > > >     cluster machine but got no reply.
> > > > >     
> > > > >     PR:     265915
> > > > 
> > > > You cannot take the decision to revert on your own for many reasons:
> > > > 
> > > > 1. etiquete: we ask people to actually revert if needed and escalate if they
> > > > don't, we never revert directly ourself! the only one allowed to do "rude" revert
> > > > are people taking care of the package building when something break the delivery
> > > > of packages for Tier 1
> > > I did it myself so that users don't upgrade in the meantime, since that
> > > would create further confusion. If I let it wait, then PORTEPOCH should
> > > have been bumped for all the affected ports, which I think we all agree
> > > would be troublesome.
> > 
> > No what will happen is given it works on Tier1, the Tier2 will fix one by one
> > the issues that raised if any without reverting, meaning no PORTEPOCH would be
> > needed.
> 
> Isn't it better to fix issues BEFORE committing?


Yes if possible in a timely manner, but again this is the life of Tier 2 to be best
effort support.

And again the problem here is the behaviour, the driven by revert by a committer
of the work of another committer, this is not acceptable and have never been
accepted in the project.

Best regards,
Bapt