-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Torfinn Ingolfsen wrote:
> Hi,
>
> 2009/4/13 Bernhard Fröhlich :
>> Looks like another missing patch. Now i've double checked with your list
>> and this is the last missing one. (also taken from mythtv-frontend)
>>
>> http://home.bluelife.at/ports/myt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernhard Fröhlich wrote:
> On Mon, April 13, 2009 8:34 pm, Torfinn Ingolfsen wrote:
>> Hello,
>>
>> 2009/4/13 Bernhard Fröhlich :
>>> Here are the patches that i've needed to get both ports working again.
>>>
>>>
>>> multimedia/mythtv:
>>>
>>> http://h
On Thursday 16 April 2009 19:52:38 Chris Rees wrote:
> 2009/4/16 Oleg Ginzburg :
> > Hello maillist!
> >
> > I have two examples of ports with which arises some complexities by
> > operation with pkg_add and argument "-r".
> >
> > One of ports is "security/keepassx". His name is registered in lower
editors/vim
mail/procmail
net-mgmt/net-snmp
net-mgmt/nagios
--
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354
Consultant - P6M7G8 Inc.
Hello maillist!
I have two examples of ports with which arises some complexities by operation
with pkg_add and argument "-r".
One of ports is "security/keepassx". His name is registered in lowercase,
however at installation in/var/db/pkg is registered as KeepAssX. If to try to
install port wi
On Thu, Apr 16, 2009 at 08:19, Joseph King wrote:
> After trying for about 12 hours straight I gave up trying to get this client
> working on the amd64 arch. As far as I can tell it is only for i386.
>
> I downgraded from amd64 to i386 because of this.
>
> Figured you might want to remove the amd6
SAITOU Toshihide wrote:
In message: <49e687c1.70...@seliverstoff.fr>
michel writes:
SAITOU Toshihide wrote:
In message: <49c65f17.9020...@seliverstoff.fr>
michel writes:
--- (the lines is omitted) ---
I encountered a same problem and solved by delet
After trying for about 12 hours straight I gave up trying to get this client
working on the amd64 arch. As far as I can tell it is only for i386.
I downgraded from amd64 to i386 because of this.
Figured you might want to remove the amd64 from the ONLY_FOR_ARCHS=
This might also be the case with
In message: <49e687c1.70...@seliverstoff.fr>
michel writes:
> SAITOU Toshihide wrote:
> > In message: <49c65f17.9020...@seliverstoff.fr>
> > michel writes:
--- (the lines is omitted) ---
> > I encountered a same problem and solved by deleting some
> > obsolete(?) m4 files
