Date: Tue, 3 Jul 2001 10:56:41 -0300 From: "Mario Sergio Fujikawa Ferreira" <lioux@uol.com.br> To: Alexander Langer <alex@big.endian.de> Cc: sobomax@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG, jedgar@FreeBSD.ORG Subject: Re: ports/27839: Update mail/qpopper to version 4.0.3 Message-ID: <20010703105641.A753@Fedaykin.here> In-Reply-To: <20010603135017.A2289@kawoserv.kawo2.rwth-aachen.de>; from alex@big.endian.de on Sun, Jun 03, 2001 at 01:49:55PM %2B0200 References: <200106021857.f52IvHs09944@freefall.freebsd.org> <200106021950.f52Jowo52032@mail.uic-in.net> <20010603135017.A2289@kawoserv.kawo2.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 03, 2001 at 01:49:55PM +0200, Alexander Langer wrote: > Thus spake Maxim Sobolev (sobomax@mail-in.net): > > > > Assign to jedgar, a member of the Security-Officer Team. > > Why? Maintainer of the port is committer, so IMO he could take > > actions necessary. I wonder why member of the Security-Officer > > Team could do this job better. > > I first wanted to assign it to both, lioux and a security-officer team > member (but that's not possible). Then I decided that assigning it to > the security officer is more important, because it's a security risk > and one has to write an advisory anyways. Yet another reason for us to consider a gnats replacing in the future. (fearing another bikeshed) > But, to be honest, I was quite unsure with doing that and admit that > it could have been wrong :-) Well, I do not resent this being assigned to a security-officer team member. :) At least, the problem was taken care of. However, I am not sure what could have been done that I couldn't have done myself. The fix was known and indeed pretty simple, updating the distfile version. I am not territorial with my ports, a fix should be committed if it is REALLY necessary. sobomax, will and others have committed to ports under maintainer and I've thanked them for doing so. In fact, I appreciate the commit giving quick response to the problem. Nevertheless, we should assign at least a 1 day time out to the maintainer before action is taken unless the update can't wait (this is one of those gray bikeshed shade areas). At least, a BROKEN flag state should be committed in between. Given some complex ports (such as qmail master port), sometimes the maintainer is the most appropriate person to handle an update since it may break lots of slave ports. Just a thought for future actions. My 2 cents, -- Mario S F Ferreira - UnB - Brazil - "I guess this is a signature." lioux at ( freebsd dot org | linf dot unb dot br ) flames to beloved devnull@someotherworldbeloworabove.org feature, n: a documented bug | bug, n: an undocumented feature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010703105641.A753>