On Thu, Sep 27, 2012 at 8:39 PM, Eitan Adler wrote:
> On 27 September 2012 22:52, Kevin Oberman wrote:
>> In any case, if you don't have the ispell wrapper selected, than there
>> should be no conflict. It looks like that was intended since there are
>> two CONFLICTS statements. the first is unco
On 27 September 2012 22:52, Kevin Oberman wrote:
> In any case, if you don't have the ispell wrapper selected, than there
> should be no conflict. It looks like that was intended since there are
> two CONFLICTS statements. the first is unconditional and I suspect
> should have been removed. The se
On Thu, Sep 27, 2012 at 6:17 PM, Tsurutani Naoki
wrote:
> I think aspell does not conflict with ispell; they have no common files.
> Is it any problem with ispell when running or building aspell ?
>
> BTW, textproc/ispell does not have "CONFLICTS" entry... it is confusing.
I suspect it is bogus u
I think aspell does not conflict with ispell; they have no common files.
Is it any problem with ispell when running or building aspell ?
BTW, textproc/ispell does not have "CONFLICTS" entry... it is confusing.
---
Tsurutani Naoki
turut...@scphys.kyoto-u.ac.jp
___
On Do., 27. Sep. 2012 13:55:51 CEST, Anton Shterenlikht
wrote:
> redports.org is good, thank you to whoever worked on it.
You're welcome.
> One question: the upstream for my port is non-existent,
> so rather then patch it, I'm updating the code itself.
> I then create a new tarball. It seems r
On Thu, Sep 27, 2012 at 12:55:51PM +0100, Anton Shterenlikht wrote:
> redports.org is good, thank you to whoever worked on it.
>
> One question: the upstream for my port is non-existent,
> so rather then patch it, I'm updating the code itself.
> I then create a new tarball. It seems redports doesn
On 27 September 2012 13:21, Florent Peterschmitt wrote:
> Le 26/09/2012 14:10, Olivier Duchateau a écrit :
>
>> 2012/9/26 Florent Peterschmitt:
>>>
>>> Le 26/09/2012 12:26, Sergey V. Dyatko a écrit :
>>>
On Wed, 26 Sep 2012 14:17:57 +
Florent Peterschmitt wrote:
> Hello,
>
- Original Message -
> 2012/9/26 Lawrence K. Chen, P.Eng. :
> > So, now that its in the wild...I upgraded...and it broke my dual
> > monitor desktop (at work). Seems like gdm/gnome can't see the
> > other monitor. Tried rebuilding a bunch of other things, but
> > didn't help. Reverting t
On Thu, 27 Sep 2012 17:21:30 +
Florent Peterschmitt wrote:
> Le 26/09/2012 14:10, Olivier Duchateau a écrit :
> > 2012/9/26 Florent Peterschmitt:
> >> Le 26/09/2012 12:26, Sergey V. Dyatko a écrit :
> >>
> >>> On Wed, 26 Sep 2012 14:17:57 +
> >>> Florent Peterschmitt wrote:
> >>>
>
On Thu, Sep 27, 2012 at 12:07 AM, Ruslan Mahmatkhanov wrote:
> First thank you for working on this. According to squid web-page, 3.2 is
> the only stable version ("Current versions suitable for production use."),
> that is actively maintained. 3.1 and less are listed in "Old versions -
> Provided
On Wed, Sep 26, 2012 at 5:42 PM, Joseph Mingrone wrote:
> Hello;
>
> I have been using encfs successfully for many months.
>
> % encfs ~/.crypt ~/files/crypt
>
> Today, I tried to mount the same way as usual. My password was
> accepted, but the directory ~/files/crypt disappeared after the mount.
On 27 Sep 2012 16:29, "Anton Shterenlikht" wrote:
>
> What is the meaning of USA_RESIDENT=YES in redports build logs?
>
The US government considers cryptography a weapon, so exporting it is
technically an offence. Therefore, a declaration that you're a US resident
is required for strong cryptogr
What is the meaning of USA_RESIDENT=YES in redports build logs?
Anton
___
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"
From: Dimitry Andric
On 2012-09-27 14:16, Anton Shterenlikht wrote:
> Building my port with clang I get this warning
> (gcc doesn't pick this up):
>
> x11.c:1543:5: warning: add explicit braces to avoid dangling else
[-Wdangling-else]
>
Le 26/09/2012 14:10, Olivier Duchateau a écrit :
2012/9/26 Florent Peterschmitt:
Le 26/09/2012 12:26, Sergey V. Dyatko a écrit :
On Wed, 26 Sep 2012 14:17:57 +
Florent Peterschmitt wrote:
Hello,
Why the terminal emulator from XFCE4 is called Terminal instead of
xfce4-terminal ?
http:
2012/9/26 Lawrence K. Chen, P.Eng. :
> So, now that its in the wild...I upgraded...and it broke my dual monitor
> desktop (at work). Seems like gdm/gnome can't see the other monitor. Tried
> rebuilding a bunch of other things, but didn't help. Reverting to previous
> (295.71) has things worki
On 2012-09-27 14:16, Anton Shterenlikht wrote:
Building my port with clang I get this warning
(gcc doesn't pick this up):
x11.c:1543:5: warning: add explicit braces to avoid dangling else
[-Wdangling-else]
else if (actual_type != None)
^
1 warning generated.
If the warning isn't fat
On Wed, Sep 26, 2012 at 02:05:57PM -0700, David Wolfskill wrote:
> On Wed, Sep 26, 2012 at 04:59:28PM -0400, Wesley Shields wrote:
> > On Wed, Sep 26, 2012 at 04:43:57AM -0700, David Wolfskill wrote:
> > > This is a FreeBSD/i386 stable/9 system:
> > >
> > > FreeBSD freebeast.catwhisker.org 9.1-PRE
On Wed, Sep 26, 2012 at 03:12:39PM +0100, Anton Shterenlikht wrote:
> From m.sea...@infracaninophile.co.uk Wed Sep 26 14:21:51 2012
>
> On 26/09/2012 13:06, Anton Shterenlikht wrote:
> > I was updating my port until I got to
> >
> > make: don't know how to make insta
I'm not great with C.
Building my port with clang I get this warning
(gcc doesn't pick this up):
x11.c:1543:5: warning: add explicit braces to avoid dangling else
[-Wdangling-else]
else if (actual_type != None)
^
1 warning generated.
I think I understand what's going on,
but wanted someb
redports.org is good, thank you to whoever worked on it.
One question: the upstream for my port is non-existent,
so rather then patch it, I'm updating the code itself.
I then create a new tarball. It seems redports doesn't
update the tarball every time I request a build.
So it seems I have to upda
Hello!
Are you planning to update coovachilli port to version 1.2.9?
Thank you,
Egor
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.o
On 2012-09-26 01:41, Jan Beich wrote:
> Oliver Pinter writes:
I just committed a fix for this, based on Jan's patch in ports/172100.
Regards!
--
Niclas
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
T
Hi,
Can this be some kind of library version mismatch? Both PHP and
Mapserver use GD for working with graphics. But PHP uses its internal GD
while Mapserver uses the FreeBSD version. Both differ in version;
FreeBSD GD is gd-2.0.35_8,1, PHP uses [GD Version] => bundled (2.0.34
compatible). So,
Sorry for spamming. I did a `make` in /usr/ports/lang/php5 and checked,
if there's a Zend directory in work/php-5.4.6/, but there's no Zend
directory in work. Should one be there? Can someone please verify, if
there's usually a Zend directory at
/usr/ports/lang/php5/work/php-5.4.6/? That would
On 27 Sep 2012, at 05:02 AM, Егор Потёмкин wrote:
> Hello!
>
> Are you planning to update coovachilli port to version 1.2.9?
>
> Thank you,
> Egor
No, waiting for 1.3.0 to release.___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.or
Hi Thomas,
Thomas-Martin Seck wrote on 27.09.2012 09:22:
Hi,
this is just a short update on the status of Squid 3 ports. As you may
have noticed I am a bit behind with regards to Squid 3.2. Sorry for that
-- I could not spend much time for ports development in the last few
months. To add insult
Btw., I wonder why
/usr/ports/lang/php5/work/php-5.4.6/Zend/zend_object_handlers.c appears
in the core dump. Shouldn't that have been moved to an appropriate
directory somewhere and the link be updated?
Frank
Am 2012-09-26 16:17, schrieb Frank Broniewski:
Hi,
I have a problem with PHP Maps
28 matches
Mail list logo