Sorry to be a pest. At the bottom of closed PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183791
There is a working fix that hasn't been committed yet. A target needs to be
added to audio/liba52/Makefile I recommend changing it a little bit though from
the one in the PR, to this:
pre-in
I submitted a working port for namecoin-qt and namecoind. Please try it and
share any feedback/improvements you have. Let me know how you use it and with
what options, please. More info is in the PR and the .shar attached there
contains namecoin and namecoin-daemon.
http://www.freebsd.org/cgi/q
On Sat, Jan 04, 2014 at 03:56:26PM + I heard the voice of
Mathieu Arnold, and lo! it spake thus:
>
> Log:
> Revert lang/openjdk7 to 7u25.
This has had build problems for me on 2 different systems that had _45
installed. It blows up after using the installed openjdk7 partway
through with an
On Sun, Jan 05, 2014 at 12:24:17AM +0100, Michael Gmelin wrote:
> It's a trivial patch to a trivial problem I posted 19 months ago.
>
> Please resolve as fixed or wontfix or whatever you like. Leaving it
> open without any response is pointless.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=port
It's a trivial patch to a trivial problem I posted 19 months ago.
Please resolve as fixed or wontfix or whatever you like. Leaving it
open without any response is pointless.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168479
--
Michael Gmelin
___
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 2014-Jan-03 17:53:02 +0100, Torbjorn Granlund wrote:
>We have been forced to add three FreeBSD-related items to the releases
>notes:
Your use of "work" in the following notes is ambiguous. Are you referring
to building gmp, another program linking against gmp or executing a program
that links
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, 2013-12-28 at 14:36:41 +1100, Kubilay Kocak wrote:
> ...
> Attached is a patch (to lang/postfix) which restores the default warning
> flags while continuing to respect user-supplied flags. This can likely
> be applied to all postfix ports. Maintainer is CC'd.
>
> I've tested it quickly her
Hi,there
Do you guys have some time to update these two? Many thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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
Hello world :-)
There still is a conflict of binutils and arm-eabi-binutils in binary
packages / ports - they install locale files into same destination.
This blocks ARM development and/or other tools that depends on
binutils. Please note that binutils are also dependency of various
other packages
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
22 matches
Mail list logo
