Hi.
I've noticed few things about i2p port:
- i2p package doesn't have openjdk as dependency but it needs openjdk to run;
- there is unsubstituted strings in i2prouter, runplain.sh and eepget after
install (/usr/local/etc/rc.d/i2p install): %INSTALL_PATH and
%SYSTEM_java_io_tmpdir. This string
On Fri, 14 Jun 2013 09:45:44 -0400
Robert Huff wrote:
>
> One of my machines crashed this morning, and
> lost /usr/ports/db
> - the directory and everything in it.
> Portmaster refuses to run.
> How do I re-create that information?
>
IIRC there's a backup under /var/backups mad
Where would -Wall -msse3 be included? /etc/make.conf or within /usr/portsMk?
___
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"
As I had no answer on this problem, I ask again for this.
It seems to me that the port needs to be fixed.
# uname -a
FreeBSD atom0 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4
06:55:39 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
The problem with devel/gobje
This PR was submitted to allow portconf to handle dash symbols (as well as plus
symbols), which is highly important because of the new OPTIONS framework. It was
submitted in Oct 2012 but has been untouched since then. I have been using the
patch myself and it works fine, without it, I would be u
--On June 14, 2013 11:13:25 AM -0500 Paul Schmehl
wrote:
I'm updating machines, and the updates all work fine except a machine
running 9.1 Release. On that machine, portmaster hangs.
This is what I see:
===> Building for xorg-macros-1.17
===>>> Creating a backup package for old version xo
I'm updating machines, and the updates all work fine except a machine
running 9.1 Release. On that machine, portmaster hangs.
This is what I see:
===> Building for xorg-macros-1.17
===>>> Creating a backup package for old version xorg-macros-1.16.1
I tried using -B to eliminate the backups,
On Fri, Jun 14, 2013 at 2:36 PM, Michael Gmelin wrote:
> On Thu, 13 Jun 2013 08:24:18 +0200
> Matthias Apitz wrote:
>
>> El día Thursday, June 13, 2013 a las 08:07:14AM +0200, Eitan Adler
>> escribió:
>>
>> > On Thu, Jun 13, 2013 at 3:15 AM, Michael Gmelin
>> > wrote:
>> > > So my question is: A
One of my machines crashed this morning, and lost /usr/ports/db
- the directory and everything in it.
Portmaster refuses to run.
How do I re-create that information?
Respectfully,
Robert Huff
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
Hi all,
When building a port for the first time a dialog may appear to configure
options for that port. This configuration is saved such that later
builds no longer show the dialog. This behaviour has now been extended
to include options set in /etc/make.conf. It allows you to configure
options
On Thu, 13 Jun 2013 08:24:18 +0200
Matthias Apitz wrote:
> El día Thursday, June 13, 2013 a las 08:07:14AM +0200, Eitan Adler
> escribió:
>
> > On Thu, Jun 13, 2013 at 3:15 AM, Michael Gmelin
> > wrote:
> > > So my question is: Are we port maintainers now really supposed to
> > > make ports wor
On Fri, Jun 14, 2013 at 06:40:03AM -0400, Jerry wrote:
> On Fri, 14 Jun 2013 12:10:17 +0200 Baptiste Daroussin articulated:
> >
> > This is not a FreeBSD "specific" problem given that Marc Espie is
> > from OpenBSD and so was speaking of problems found on OpenBSD. using
> > google I found the said
On 6/14/2013 13:21, John Marino wrote:
I despise languages that aren't backwards compatible, so if 5.18
actually broke compatibility intentionally then I for one would vote for
staying on 5.16 for a long, long time. I am reserving judgement for the
full story.
I just realize that Perl default
2013-06-13 22:15, Koichiro IWAO skrev:
Everyone missing remmina,
I manage to finish updating remmina on this weekend.
Sorry for the long wait.
We appreciate you work. Thank you :-)
どうもありがとうございました
/Leslie
___
freebsd-ports@freebsd.org mailing lis
On 6/14/2013 12:40, Jerry wrote:
Just so I am understanding this correctly, the problem is not with
Perl-5.18, but rather applications that were written for earlier
versions that may not have in fact been written in tight compliance
with the specifications of the earlier versions and those proble
On Fri, 14 Jun 2013 04:52:08 -0500
Matthew D. Fuller articulated:
> On Fri, Jun 14, 2013 at 01:12:09AM -0700 I heard the voice of
> Thomas Mueller, and lo! it spake thus:
> >
> > In that case, why didn't they go to perl 5.18?
>
> I should hope that lang/perl5.16 _NEVER_ goes to 5.18 8-}
The p
On Fri, 14 Jun 2013 12:10:17 +0200
Baptiste Daroussin articulated:
> On Fri, Jun 14, 2013 at 05:49:41AM -0400, Jerry wrote:
> > On Fri, 14 Jun 2013 10:18:31 +0200
> > John Marino articulated:
> >
> > > According to OpenBSD's Marc Espie on a pkgsrc list, a lot of
> > > established scripts will bre
Le 14/06/2013 10:12, Thomas Mueller a écrit :
> I see in the $PORTSDIR/UPDATING file that perl has been updated.
>
> perl5.16 has been updated from 5.16.2 to 5.16.3 .
>
> Since this is only (?) a minor-version update, why should it be necessary to
> upgrade all ports that depend on perl?
>
> po
from my priginal post:
I see in the $PORTSDIR/UPDATING file that perl has been updated.
perl5.16 has been updated from 5.16.2 to 5.16.3 .
Since this is only (?) a minor-version update, why should it be necessary to
upgrade all ports that depend on perl?
portmaster -r perl
In that case, why di
On Fri, Jun 14, 2013 at 05:49:41AM -0400, Jerry wrote:
> On Fri, 14 Jun 2013 10:18:31 +0200
> John Marino articulated:
>
> > According to OpenBSD's Marc Espie on a pkgsrc list, a lot of
> > established scripts will break on perl 5.18. Apparently it is not
> > highly backwards compatible.
> >
> >
On Fri, Jun 14, 2013 at 01:12:09AM -0700 I heard the voice of
Thomas Mueller, and lo! it spake thus:
>
> In that case, why didn't they go to perl 5.18?
I should hope that lang/perl5.16 _NEVER_ goes to 5.18 8-}
--
Matthew Fuller (MF4839) | fulle...@over-yonder.net
Systems/Network Admin
On Fri, 14 Jun 2013 10:18:31 +0200
John Marino articulated:
> According to OpenBSD's Marc Espie on a pkgsrc list, a lot of
> established scripts will break on perl 5.18. Apparently it is not
> highly backwards compatible.
>
> A large % of the perl packages would cease to build if they just
> mov
On 13/06/2013 15:24, Miguel Clara wrote:
> Than I tried to rebuild just "libdrm" and not xorg, with portmaster
> -f, pkg was mentioned again but this time the update worked and I'm
> now with pkg-1.0.13
>
> pkg info | grep pkg
> pkg-1.0.13 New generation package manager
>
> I'
On 6/14/2013 10:12, Thomas Mueller wrote:
Since this is only (?) a minor-version update, why should it be necessary to
upgrade all ports that depend on perl?
In that case, why didn't they go to perl 5.18?
According to OpenBSD's Marc Espie on a pkgsrc list, a lot of established
scripts will br
I see in the $PORTSDIR/UPDATING file that perl has been updated.
perl5.16 has been updated from 5.16.2 to 5.16.3 .
Since this is only (?) a minor-version update, why should it be necessary to
upgrade all ports that depend on perl?
portmaster -r perl
In that case, why didn't they go to perl 5.1
Am 2013-06-14 06:19, schrieb RyōTa SimaMoto:
Hi,
portaudit rejects the latest version (1.6.12) of devel/dbus
because acceptable version is set too higher (1.16.12) than it.
http://portaudit.FreeBSD.org/4e9e410b-d462-11e2-8d57-080027019be0.html
___
fre
27 matches
Mail list logo
