* From: "David O'Brien" <[EMAIL PROTECTED]>
* Not sure if you saw this message. The more I think about it, I'm not
* sure bumping the shared libc version will accomplish anything other than
* require a compat4x distribution for 4.2-RELEASE. For the 4.0R upgrade
* kit you'd just have to inc
* From: Jordan Hubbard <[EMAIL PROTECTED]>
* Any pending bumps should *definitely* occur before the release goes
* out, so consider me all in favor.
You guys may have missed what I said in the first mail. That implies
rebuilding all packages. I can do that, but I'm afraid it will most
likel
* From: John Polstra <[EMAIL PROTECTED]>
* In article <[EMAIL PROTECTED]>,
* Satoshi Asami <[EMAIL PROTECTED]> wrote:
*
* > It was brought to my attention that recent 40upgrade kills all the
* > networking programs. Looking at the plists, the only thing I can
* > think of is that libc.so
* From: Kris Kennaway <[EMAIL PROTECTED]>
* Having said that, is there any way you could get bento building restricted
* ports, but not publishing the packages? It's quite useful for the kind of
* thing I tried to apply it to (i.e. figuring out whether the port itself is
* broken, or if it's
* From: Kris Kennaway <[EMAIL PROTECTED]>
* Looks like you have either an outdated port, or extra crud in there
* somewhere. The PGP5 port is building fine, according to
* http://bento.freebsd.org
Uh, which part of bento said so? ;)
I believe you are referring to the fact that there is no p
