On 03/06/2014 01:05 AM, Michele Calgaro wrote:
> 
>> Kerry/Beagle -> the only good Beagle is a dead Beagle (software wise), leave it
>> dead, ashes-to-ashes dust-to-dust and all that jazz.
>> [FAILED]  [00/00:00:34.221]  "applications/kerry"
> Now builds OK! The report was slightly rearranged to mirror the new build order, but in reality libbeagle was not part of the full rebuild (I had forgotten to include it in the build list). After I saw that, I built libbeagle and after your email I rebuilt kerry. Now no problem :)
> [  OK  ]  [00/00:05:32.386]  "applications/kerry"

Take care if you actually launch it, it can bring your desktop to it's knees
while it tries to 'index' your entire computer. Since SuSE 11.0, 1st order of
business has always been to shoot the dog in the head....

>> ksquirrel and libksquirrell are a few that would normally build. I believe they
>> provide additional graphics libs and extensions to some packages. I build
>> libksquirrel but not ksquirrel itself.
>> [FAILED]  [00/00:00:36.914]  "libraries/libksquirrel"
>> [FAILED]  [00/00:00:36.301]  "applications/ksquirrel"
> libksquirrel fails for a missing dependency and ksquirrel requires libksquirrel. I will have to check this as well.

Important! Here are the dependencies:

depends=('djvulibre'
	'ghostscript'
	'giflib'
	'libmng'
	'librsvg'
	'libxft'
	'libxml2'
	'netpbm'
	'potrace'
	'tde-tdebase'
	'transfig'
	'xfig'
	'xmedcon'
	'xorg-xwd')

If you don't have xmedcon, I have a build script for it. It add really neat
capabilities to view/manage medical imaging (CT-Scans, MRI's X-rays, etc. in the
native medical image formats)

> 
>> What does smartcardauth do? I haven't built it before
>> [FAILED]  [00/00:00:53.049]  "applications/smartcardauth"
> As for Kerry, the problem was a missing dependency not previously built (pcsc-lite-nodbus).
> After recompiling, no problem!
> [  OK  ]  [00/00:03:54.424]  "applications/smartcardauth"
> 
> According to debian control file description:
> "This utility will allow you to set up your computer to accept a SmartCard as an authentication source for:
>  - Your encrypted LUKS partition
>  - TDE3.x, including automatic login, lock, and unlock features
>  It is designed to work with any ISO 7816-1,2,3,4 compliant smartcard
>  Examples of such cards are:
>  - The Schlumberger MultiFlex
>  - The ACS ACOS5 / ACOS6 series of cryptographic ISO 7816 cards
>  If a card is chosen that has PKSC support, such as the ACOS cards, this utility can run
>  simultaneously with the certificate reading program(s) to provide single sign on
>  in addition to the PKCS certificate functionality"

Thank you for the explanation.


-- 
David C. Rankin, J.D.,P.E.