On February 28, 2017 6:46:36 AM EST, Oliver Welter <[email protected]> wrote:
>Hi Fabian,
>
>I just tested with our vagrant machine:
>
>root@oxi-test-jessie:/etc/apt/sources.list.d# cat openxpki.list
>deb http://packages.openxpki.org/debian/ jessie release
>
>aptitude show libopenxpki-perl
>Package: libopenxpki-perl
>State: installed
>Automatically installed: no
>Version: 1.16.5-1
>Priority: optional
>Section: perl
>Maintainer: OpenXPKI Foundation <[email protected]>
>Architecture: amd64
>Uncompressed Size: 5,842 k
>Depends: perl (>= 5.20.2-3+deb8u6), perlapi-5.20.2, libc6 (>= 2.2.5),
>
>So its very likely that your setup is broken in someway.
>
>Oliver
>
>
>Am 28.02.2017 um 11:14 schrieb Fabian A. Santiago:
>> On February 28, 2017 4:08:35 AM EST, Oliver Welter <[email protected]>
>wrote:
>>> Hi Fabian,
>>>
>>> this looks like you added the Ubuntu repository instead of the
>debian
>>> one. Check the contents of the sources file.
>>>
>>> Oliver
>>>
>>> Am 27.02.2017 um 21:59 schrieb Fabian Santiago:
>>>> On Mon, Feb 27, 2017 at 2:39 PM, Fabian Santiago
>>>> <[email protected]> wrote:
>>>>> Hello,
>>>>>
>>>>> i've just deployed a new server with debian 8 jessie on it and
>when
>>>>> reaching the install step:
>>>>>
>>>>> "aptitude install libopenxpki-perl openxpki-i18n"
>>>>>
>>>>> it complains that i do not have perlapi:
>>>>>
>>>>> Depends: perlapi-5.18.2 which is a virtual package.
>>>>>
>>>>> i have installed:
>>>>>
>>>>> dpkg-query -l 'perlapi*'
>>>>> Desired=Unknown/Install/Remove/Purge/Hold
>>>>> |
>>>
>Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>>>>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>>>>> ||/ Name                              Version
>>>>> Architecture          Description
>>>>>
>>>
>+++-=================================-=====================-=====================-=======================================================================
>>>>> un  perlapi-5.20.0                    <none>                <none>
>>>>>            (no description available)
>>>>> un  perlapi-5.20.1                    <none>                <none>
>>>>>            (no description available)
>>>>> un  perlapi-5.20.2                    <none>                <none>
>>>>>            (no description available)
>>>>>
>>>>> how can i get around this issue? Thanks.
>>>>>
>>>>> - Fabian S.
>>>>
>>>>
>>>
>------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> OpenXPKI-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/openxpki-users
>>>>
>>
>> Thanks Oliver,
>>
>> I followed the quickstart guide and I've also double checked at you
>request; definitely debian.
>>
>> I fixed my issue by using perlbrew to install and switch to Perl
>5.18.x. this got me up and running. My default os load appeared to
>simply have too new a Perl version for openxpki.
>>
>> Any other thoughts?
>>
>>
>>
>>
>------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> OpenXPKI-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/openxpki-users
>>

Interesting,

I'm testing on a brand new linode VMS deployed with debian 8. Run updates first 
as well. Could it be something in the base image used by linode?

-- 
Thanks.
Fabian S.

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users

Reply via email to