> 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 a
On 5/28/2013 7:37 AM, Marco Beishuizen wrote:
> 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 w
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:
# m
On 5/28/2013 4:12 AM, Marco Beishuizen wrote:
> Hi,
>
> Seems that portupgrade is broken after the upgrade from ruby18 to ruby19:
> ...
> root@yokozuna:/usr/ports# portupgrade -a
> invalid byte sequence in UTF-8
> Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFOQ
> ...
>
> I've rebuilt th
On Tue, 28 May 2013, the wise Jerry wrote:
Did you update the ports as specified in the UPDATING file?
Yes, but that didn't do anything.
what is the output of: "pkg_info -R ruby-1.9\* and "pkg_info -R
ruby-1.8\*" if you still have it installed?
...
root@yokozuna:/usr/ports# pkg_info -R ruby
On Tue, 28 May 2013 11:12:18 +0200 (CEST)
Marco Beishuizen articulated:
> Seems that portupgrade is broken after the upgrade from ruby18 to
> ruby19: ...
> root@yokozuna:/usr/ports# portupgrade -a
> invalid byte sequence in UTF-8
> Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFOQ
> ...
>
Hi,
Seems that portupgrade is broken after the upgrade from ruby18 to ruby19:
...
root@yokozuna:/usr/ports# portupgrade -a
invalid byte sequence in UTF-8
Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFOQ
...
I've rebuilt the pkgdb and reinstalled portupgrade but that didn't help.
Regard
On Tue, 23 Aug 2011, Andrea Venturoli wrote:
On 08/23/11 14:59, Frank_s wrote:
Following the directions in UPDATING and using portupgrade:
...
Did I break it? Do I own both pieces? How can I fix this?
Please see my two other threads.
You probably don't have the latest portupgrade (2.4.9.2_2,
On 08/23/11 14:59, Frank_s wrote:
Following the directions in UPDATING and using portupgrade:
> ...
Did I break it? Do I own both pieces? How can I fix this?
Please see my two other threads.
You probably don't have the latest portupgrade (2.4.9.2_2,2), which
fixes what you posted.
However,
Following the directions in UPDATING and using portupgrade:
20110822:
AFFECTS: users of lang/ruby
AUTHOR: s...@freebsd.org
The default ruby version has been updated to 1.9. Please rebuild all
ports that
depends on it.
If you use portmaster:
# portmaster -r ruby18
If you use por
10 matches
Mail list logo