On Tue, Jun 12, 2007 at 11:23:34AM +0100, Alex Zbyslaw wrote:
> It doesn't look like what I was suggesting is the issue so it's all
> moot, but the example I can see:
>
>sudo portupgrade -fo devel/bison2 bison
>
> is different from what I was suggesting:
>
>sudo portupgrade -f -o devel/
Josh Tolbert wrote:
On Fri, Jun 08, 2007 at 12:04:38PM +0100, Alex Zbyslaw wrote:
Josh Tolbert wrote:
(15:38:21 <[EMAIL PROTECTED]:~>) $ pkg_info | grep bison
bison-1.75_2,1 A parser generator from FSF, (mostly) compatible with
Yacc
(15:38:30 <[EMAIL PROTECTED]:~>) $ sudo portu
On Fri, Jun 08, 2007 at 12:04:38PM +0100, Alex Zbyslaw wrote:
> Josh Tolbert wrote:
>
> >(15:38:21 <[EMAIL PROTECTED]:~>) $ pkg_info | grep bison
> >bison-1.75_2,1 A parser generator from FSF, (mostly) compatible with
> >Yacc
> >(15:38:30 <[EMAIL PROTECTED]:~>) $ sudo portupgrade -o devel/bi
Hello,
Having successfully completed my update from Xorg 6.9 to Xorg 7.2, I decided
to install a few things, one of which required devel/bison2 instead of bison.
Usually, portupgrade -o would handle this for me, but lately it seems like
portupgrade -o doesn't want to replace ports. Has anyone else
