On 06/14/10 04:48, Matthew Seaman wrote:
Even having replaced libassuan with libassuan-1, there still seems to be
a problem for some ports:
Yes, I fixed that shortly after the first update, thanks to QAT. :)
I had tested picking up the new dependency for building the port, but
didn't test fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/06/2010 12:23:52, Doug Barton wrote:
> On 06/14/10 02:30, Paul Macdonald wrote:
>>
>> Hi
>>
>> Is anyone else seeing problems with
>>
>> Upgrading 'gnupg-2.0.14_2' to 'gnupg-2.0.14_3'
>
> Please read /usr/ports/UPDATING.
Even having replaced li
On 06/14/10 02:30, Paul Macdonald wrote:
Hi
Is anyone else seeing problems with
Upgrading 'gnupg-2.0.14_2' to 'gnupg-2.0.14_3'
Please read /usr/ports/UPDATING.
hth,
Doug
--
... and that's just a little bit of history repeating.
-- Propellerheads
