Permission denied error message when trying to install YaCy
Following this guide http://wiki.yacy.net/index.php/En:DebianInstall
when I am at the very first step:
echo 'deb http://debian.yacy.net ./' > /etc/apt/sources.list.d/yacy.list
I get permission denied, even when trying to add a "sudo". Anyone in the know?
You can use 'tee':
$ echo 'deb http://debian.yacy.net ./' | sudo tee /etc/apt/sources.list.d/yacy.list
Thanks, but when I do the next step I get some wierd error messages there as well :/
When I try to do wget http://debian.yacy.net/yacy_orbiter_key.asc -O- | apt-key add - I get "Resolving debian.yacy.net (debian.yacy.net)... ERROR: This command can only be used by root.
188.40.30.87
Connecting to debian.yacy.net (debian.yacy.net)|188.40.30.87|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 958 [text/plain]
Saving to: ‘STDOUT’
- 0%[ ] 0 --.-KB/s in 0s
Cannot write to ‘-’ (Broken pipe)."
And if I do apt-key advanced --keyserver pgp.net.nz --recv-keys 03D886E7 I get "gpg: requesting key 03D886E7 from hkp server pgp.net.nz
gpg: key 03D886E7: public key "Michael Peter Christen <name at domain>" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
gpg: no writable keyring found: eof
gpg: error reading `[stdin]': general error
gpg: import from `[stdin]' failed: general error
gpg: Total number processed: 0
"
Which seems wrong to me.
Indeed because when I do sudo apt update I get:
"W: GPG error: http://debian.yacy.net ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1F968B3903D886E7
E: The repository 'http://debian.yacy.net ./ Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details."
I do the next step I get some wierd error messages there as well :/
They are not weird. They all say that you must have administrative privileges to do what you want to do. You can get those prefixing the commands with "sudo " or you can open a shell with administrative privileges and then copy-paste the http://wiki.yacy.net/index.php/En:DebianInstall 's commands, unmodified:
$ sudo -i
To then exit the shell with administrative privileges:
# exit
> Following this guide http://wiki.yacy.net/index.php/En:DebianInstall
>
> when I am at the very first step:
>
> echo 'deb http://debian.yacy.net ./' > /etc/apt/sources.list.d/yacy.list
>
> I get permission denied, even when trying to add a "sudo". Anyone in the
> know?
https://trisquel.info/en/forum/comparison-search-engines#comment-140202
Thank you. That may or may not be working, but I find value in trying the "official" method of installment so as to "test" whether something is wrong in the guide and then they can potentially change what is wrong. If I have some trouble installing something through the "official" guide I find that is a *big* issue with the program as a whole. It shouldn't be necessary to go to a third party forum to get an alternative method in my opinion. Yet here we are though...
PS. You never my answered my questions there :p
Besides thinking that this should go to trisquel-users mailing list (or "Trisquel users" forum), what worries me the most is that they are telling you to add a third-party repository rather than to use the one of the system distribution you're using. Of course sometimes the package might not be available in this, but in such cases it's safer to just take main YaCy .DEB file rather (for example, by manually visiting https://debian.yacy.net/ and looking there) than blindly trusting some third party that has no commitment to follow the GNU Free System Distribution Guidelines (GNU FSDG or simply FSDG). And allowing the blind trust is what you would be doing by adding that line to either "sources.list" or its directory counterpart. Some say that they would take care as to not install "new" packages that come from these repositories, but they forget that these repositories can also modify existing packages.
Em 7 de julho de 2019 23:50:15 BRT, name at domain escreveu:
>Following this guide http://wiki.yacy.net/index.php/En:DebianInstall
>
>when I am at the very first step:
>
>echo 'deb http://debian.yacy.net ./' >
>/etc/apt/sources.list.d/yacy.list
>
>I get permission denied, even when trying to add a "sudo". Anyone in
>the
>know?
--
- Página com formas de contato:
https://libreplanet.org/wiki/User:Adfeno#vCard
- Ativista do software livre (não confundir com o gratuito). Avaliador
da liberdade de software e de sites.
- Página com lista de contribuições:
https://libreplanet.org/wiki/User:Adfeno#Contribs
- Para uso em escritórios e trabalhos, favor enviar arquivos do padrão
internacional OpenDocument/ODF 1.2 (ISO/IEC 26300-1:2015 e
correlatos). São os .odt/.ods/.odp/odg. O LibreOffice é a suíte de
escritório recomendada para editar tais arquivos.
- Para outros formatos de arquivos, veja:
https://libreplanet.org/wiki/User:Adfeno#Arquivos
- Gosta do meu trabalho? Contrate-me ou doe algo para mim!
https://libreplanet.org/wiki/User:Adfeno#Suporte
- Use comunicações sociais federadas padronizadas, onde o "social"
permanece independente do fornecedor. #DeleteWhatsApp. Use #XMPP
(https://libreplanet.org/wiki/XMPP.pt), #DeleteFacebook
#DeleteInstagram #DeleteTwitter #DeleteYouTube. Use #ActivityPub via
#Mastodon (https://joinmastodon.org/).
- #DeleteNetflix #CancelNetflix. Evite #DRM:
https://www.defectivebydesign.org/
Indeed. Perhaps it would be beneficial to have stricter rules on who is allowed to write in the "documentation" section on this site so as to avoid confusion for new users and/or non-technical persons like me.
How do I summon David? Isn't David the boss here?
You tell his name three times in a row and he just appears (but he's not the boss at all, just a humble servant).
Regarding your suggestion, we don't usually have this problem in the wiki, although as you mention, we're by definition a bit weak against this kind of (malicious or not) temporal introduction of poor advice on the documentation. We may be adding some new controls in this regards in the new site.
In any case, if I'm not mistaken, in this case the information about the relatively risky installation steps of Yacy didn't really come from our project's documentation pages but from their own, right? I don't think the dark fire will avail us there :)
> if I'm not mistaken, in this case the information about the relatively risky installation steps of Yacy didn't really come from our project's documentation pages but from their own, right?
Well... yeah, but does that make any difference? :p I mean... the link to the installation steps are in Trisquel's documentations, so indirectly the installation steps are in Trisquel's documentation.