Gryd T L wrote (from
https://www.mail-archive.com/freebsd-ports@freebsd.org/msg54593.html)
...
> The following helped me identity the ports with bad files:
>
> find /var/db/pkg -type f -exec iconv -t US-ASCII {} > /dev/null \;
>
> Reinstalling the indicated ports solved it for me. I'm currently
>
On Sun, 5 Jan 2014, the wise Gyrd Thane Lange wrote:
Hi!
I had a similar problem some time ago. Some intermediate combination of
pkg-tools/ruby/portupgrade installed bad metadata. The following
helped me identity the ports with bad files:
find /var/db/pkg -type f -exec iconv -t US-ASCII {} > /
On Sat, 4 Jan 2014, the wise Steve Wills wrote:
I'm not sure this is the right solution. Most of those types of problems
have disappeared now that rdoc isn't a dependency. If you remove
rubygem-rdoc, does the problem go away?
Rubygem-rdoc wasn't installed at all, so this isn't it either I'm a
On Sat, 04 Jan 2014 15:41:31 +0100
Mathieu Arnold wrote:
> +--On 4 janvier 2014 15:21:07 +0100 Marco Beishuizen
> wrote:
> | Hi,
> |
> | Since portupgrade doesn't work with the default ruby19 ("invalid
> | byte sequence" errors) I want to reinstall ruby18 instead. But
> | ruby18 has been remove
On Sat, Jan 04, 2014 at 03:45:12PM +0100, John Marino wrote:
> On 1/4/2014 15:38, Marco Beishuizen wrote:
> > On Sat, 4 Jan 2014, the wise John Marino wrote:
> >
> > Portupgrade builds fine, but I have my locale set to UTF-8 and in that
> > case the pkgdb breaks and portupgrade no longer works:
>
On Sat, 4 Jan 2014, the wise Mathieu Arnold wrote:
Hum, pkgtools.something, in /usr/local/etc/. Maybe you need to remove
/var/db/pkg/pkgdb.db and let pkgdb rebuild it.
/usr/local/etc/pkgtools.conf is the default and rebuilding the pkgdb.db
has no effect either.
Regards,
Marco
--
The sendm
+--On 4 janvier 2014 17:04:49 +0100 Marco Beishuizen
wrote:
| On Sat, 4 Jan 2014, the wise Mathieu Arnold wrote:
|
|> That error may come from a non us-ascii character in portupgrade's
|> configuration files.
|
| Which configuration files are you referring to?
Hum, pkgtools.something, in /usr/
On Sat, 4 Jan 2014, the wise Mathieu Arnold wrote:
That error may come from a non us-ascii character in portupgrade's
configuration files.
Which configuration files are you referring to?
Thanks,
Regards,
Marco
--
1 bulls, 3 cows.
___
freebsd-ports@
On 1/4/2014 16:33, Marco Beishuizen wrote:
> On Sat, 4 Jan 2014, the wise John Marino wrote:
>
>> Ruby18 is gone forever, and unsupported, so that's not the best option.
>> DragonFly had these same type errors with ruby19, until we redefined
>> GEM_ENV in bsd.ruby.mk
>>
>> -GEM_ENV?=
On Sat, 4 Jan 2014, the wise John Marino wrote:
Ruby18 is gone forever, and unsupported, so that's not the best option.
DragonFly had these same type errors with ruby19, until we redefined
GEM_ENV in bsd.ruby.mk
-GEM_ENV?=LC_CTYPE=UTF-8
+GEM_ENV+=LC_ALL=en_US.UTF
On 1/4/2014 15:38, Marco Beishuizen wrote:
> On Sat, 4 Jan 2014, the wise John Marino wrote:
>
> Portupgrade builds fine, but I have my locale set to UTF-8 and in that
> case the pkgdb breaks and portupgrade no longer works:
>
> ...
> root@yokozuna:/home/marco# pkgdb -FfO
> ---> Checking the pac
+--On 4 janvier 2014 15:21:07 +0100 Marco Beishuizen
wrote:
| Hi,
|
| Since portupgrade doesn't work with the default ruby19 ("invalid byte
| sequence" errors) I want to reinstall ruby18 instead. But ruby18 has been
| removed from the ports, so how can I install ruby18 again?
That error may come
On Sat, 4 Jan 2014, the wise John Marino wrote:
Are you sure about your statement, "portupgrade doesn't work with
default ruby19"?
It seems to build fine for us:
http://pkgbox64.dragonflybsd.org/bulk/bleeding-edge-default/latest-per-pkg/portupgrade-2.4.12%2c2.log
It also builds fine on FreeBS
On 1/4/2014 15:21, Marco Beishuizen wrote:
> Since portupgrade doesn't work with the default ruby19 ("invalid byte
> sequence" errors) I want to reinstall ruby18 instead. But ruby18 has
> been removed from the ports, so how can I install ruby18 again?
Are you sure about your statement, "portupgrad
Hi,
Since portupgrade doesn't work with the default ruby19 ("invalid byte
sequence" errors) I want to reinstall ruby18 instead. But ruby18 has been
removed from the ports, so how can I install ruby18 again?
Regards,
Marco
--
Illinois isn't exactly the land that God forgot:
it's more like the
15 matches
Mail list logo
