BOINC on ARM

jarek jada4p at gmail.com
Thu Jan 11 18:22:58 UTC 2018


Thanks again.

With help of your PPA URL I tried to install boinc from your PPA.

Unfortunately Ubuntu in container is restricted, i.e. it is not full
distribution, thus some commands are missing.

When trying to use

add-apt-repository ppa:costamagnagianfranco/boinc

I got error

bash: add-apt-repository: command not found

Thus I added following line to /etc/apt/sources.list

deb http://ppa.launchpad.net/costamagnagianfranco/boinc/ubuntu xenial main

hoping it'll do. Then I purged BOINC from Ubuntu container (removing
/var/lib/boinc-client directory and issuing apt-get autoremove &
autoclean as well). But, when I issued command apt-get update, there
were error messages

W: GPG error: http://ppa.launchpad.net/costamagnagianfranco/boinc/ubuntu
xenial InRelease: The following signatures couldn't be verified
because the public key is not available: NO_PUBKEY 1BCB19E03C2A1859
W: The repository
'http://ppa.launchpad.net/costamagnagianfranco/boinc/ubuntu xenial
InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user
configuration details.

Unfortunately, apt-secure command is missing as well.

Is there any way around?

TIA & best regards, jp

On Thu, Jan 11, 2018 at 5:00 PM, Gianfranco Costamagna
<locutusofborg at debian.org> wrote:
> Hello,
>
>>Unfortunately I'm neither developer nor geek, thus I need more
>
>>detailed instructions :-( I don't know where to find bionic (Github?!?
>
> sorry!
> Ubuntu Bionic is the currently development version of Ubuntu, it will be called
> 18.04LTS once it is out (april).
>
>>later I found https://github.com/BOINC/boinc but for moment being I'm
>>unable to make sense from it) or your ppa :-( Could you please give me
>>URL of your ppa?
>
>
> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc
>
> this is the ppa I'm talking about.
>
>
> unfortunately the build will take hours/days because of spectre/meltdown kernel patches
> being deployed right now on ubuntu builders
> https://mobile.twitter.com/launchpadstatus
> (amd64 and i386 are currently back, but armhf/arm64 will take some more time to update
> and catch up with the building queue)
>
> G.
>
>
> On Thu, Jan 11, 2018 at 2:28 PM, Gianfranco Costamagna
> <locutusofborg at debian.org> wrote:
>> Hello,
>>
>>>sorry troubling you; I found this address in /etc/init.d/boinc-client.
>>
>>
>> ack
>>>I installed Ubuntu Xenial in container and BOINC there. SFSG.
>>>Because I encountered repeated errors "Authorization failure: -155"
>>>issuing many boinccmd commands, I removed BOINC installation from the
>>>container and reinstalled it. But this error persisted even after
>>>purging and reinstalling BOINC.
>>>In next attempt (after purging BOINC from container and even removing
>>>/var/lib/boinc-client directory, doing apt-get autoremove, apt-get
>>>autoclean and reinstalling BOINC in Ubuntu container) first boinccmd
>>>was OK:
>>>boinccmd --lookup_account https://lhcathome.cern.ch/lhcathome/ `mail` `password`
>>>
>>>but next commands ended again with the same error:
>>>boinccmd --project_attach https://lhcathome.cern.ch/lhcathome/ `account`
>>>Authorization failure: -155
>>>boinccmd --get_state
>>>Authorization failure: -155
>>>
>>>Moreover, in /var/log/boincerr.log there are, after 1st line:
>>>
>>>dir_open: Could not open directory ‘slots’ from ‘/var/lib/boinc-client’.
>>>repeated (ad libitum) following lines:
>>>dir_open: Could not open directory ‘/dev/input’ from ‘/var/lib/boinc-client’.
>>>dir_open: Could not open directory ‘/dev/input/mice’ from
>>>‘/var/lib/boinc-client’.
>>>
>>>Could anybody please advice?
>>
>> lease try boinc from bionic (18.04 devel), or from my ppa:
>> I'm uploading 7.8.4 in some minutes
>>
>> also, please provide output of
>> systemctl status boinc-client
>>
>> G.



More information about the pkg-boinc-devel mailing list