Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 May 2013 12:00:20 -0400
From:      "Steve Wills" <swills@FreeBSD.org>
To:        "Marco Beishuizen" <mbeis@xs4all.nl>
Cc:        freebsd-ports@FreeBSD.org, Bryan Drewery <bdrewery@FreeBSD.org>
Subject:   Re: portupgrade broken after ruby upgrade
Message-ID:  <9a179859cc10c87f2595dbed116e2310.squirrel@mouf.net>
In-Reply-To: <alpine.BSF.2.00.1305281434550.18445@localhost>
References:  <alpine.BSF.2.00.1305281104060.18445@localhost> <51A49743.2000900@FreeBSD.org> <alpine.BSF.2.00.1305281434550.18445@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, 28 May 2013, the wise Bryan Drewery wrote:
>
>>> root@yokozuna:/usr/ports# portupgrade -a
>>> invalid byte sequence in UTF-8
>>> Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFOQ
>>
>> Portupgrade does not handle major ruby upgrades well.
>>
>> I recommend rebuilding portupgrade and its databases:
>>
>> # make -C /usr/ports/ports-mgmt/portupgrade build deinstall install
>> clean
>> # rm -f /var/db/pkg/pkgdb.db
>> # rm -f /usr/ports/*.db
>> # pkgdb -fu
>> # portsdb -fu

Not sure this will help in your current stat, but for others who haven't
upgraded yet, the notes in UPDATING were incorrect and have been updated,
and after some testing I believe they should work better now. My apologies
for the mistake.

Steve





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9a179859cc10c87f2595dbed116e2310.squirrel>