On 2022/10/10 21:57, Caspar Schutijser wrote: > Hi, > > On Mon, Oct 10, 2022 at 09:01:46AM +0200, Matthieu Herrb wrote: > > On Wed, Oct 05, 2022 at 06:23:03PM +0200, Caspar Schutijser wrote: > > > Hi all, > > > > > > Below is a diff that updates net/snowflake_proxy to 2.3.1. Tested on > > > amd64, seems to work fine here. > > > > > > This is the first time I'm touching a Go port, I think. So please have > > > a careful look to see whether I screwed something up (I don't think so > > > though). > > > > > > Comments or OKs? > > > > > > > Hi, > > > > It would be nice to provide an upgrade for 7.2-stable too. Apparently > > the 2.1 version has stopped accepting to relay trafic a few days ago, > > altough I didn't see a formal annoucement of this on their website. > > That's a good point, I agree. I saw the same problem but I had other > problems as well so I wasn't sure if running the old version was causing > the lack of traffic. But together with your observation, that seems > likely. > > I don't have a 7.2-stable ports tree set up yet but I can take care of > that soonish. Any OKs for this? Diff will be the exact same as the one > that I committed to -current.
OK for that. > If I commit it to -stable, should I bump net/snowflake_proxy's > REVISION in -current? I've seen such commits before, > "bump to be ahead of -stable", but just checking to see if I understand > the rules. That's needed when the port in -current is different to what's in -stable, for example if there are differences in WANTLIB/LIB_DEPENDS due to other changes in the tree.
