Date: Thu, 27 Jun 2002 20:18:49 +0200 From: Henk Wevers <henk@wevers.org> To: security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv Message-ID: <3D1B5709.8010902@wevers.org> References: <Pine.NEB.3.96L.1020627130314.6971H-100000@fledge.watson.org> <3D1B4E24.1F91E51D@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Is it possible that all the port mantainers bump the portversion one number higher, so that upgrading is more easy to update an package like apache? I allready updated apache for an example, only not after the new make world again. If i do this i will need to deinstall and reinstall the port. My EUR 0.02 cents Henk Eric Anderson wrote: > I mentioned this a while back, and I still think it's a good idea (once once > OpenSSH is ready). Like we were saying with the Apache bug - those who don't > read the lists, are typically RELEASE hungry, and will jump all over a 4.6.1 > without really caring that it's mostly security fixes - and those that do follow > the lists, will have their stuff patched and ready before the 4.6.1 rolled out, > so we get best of both worlds. > > That's just my $0.02 - not meaning much without an @freebsd.org at the end of my > email. :) > > Eric > > p.s. - should this move to -chat? > > > Robert Watson wrote: > >>On Thu, 27 Jun 2002, Matthew Dillon wrote: >> >> >>> I'm beginning to think that once all this settles down a 4.6.1 release >>> may be a good idea. Apache, ssh, now the resolver... nasty. >> >>I've been wondering about that also. However, the release engineering >>process is fairly heavy-weight, and the last time we did a light-weight >>x.x.1 release, people leapt on that opportunity to over-load it with lots >>of minor fixes that ended up making it a fairly broken release (since >>inevitably they weren't minor, but we weren't willing to do a full >>heavy-weight release). Regardless, we'd want to wait to spin a .x.x.1 >>release until the new OpenSSH was merged back, I think, so it will be a >>bit yet before we can really make a decision on this. The best strategy >>would be to literally slap down another tag on RELENG_4_6 and call it >>RELENG_4_6_1 point-release. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D1B5709.8010902>