From: Ashley Dixon <ash@suugaku.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] no ebuilds for telegram
Date: Thu, 14 May 2020 20:23:54 +0100 [thread overview]
Message-ID: <20200514192354.ir442u4xsboz5sfp@ad-gentoo-main.Home> (raw)
In-Reply-To: <30425f04-1d8d-f436-fed7-001d9bacd434@web.de>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Thu, May 14, 2020 at 09:10:56PM +0200, n952162 wrote:
> I tried to emerge net-im/telegram-desktop
> but it said:
>
> emerge: there are no ebuilds to satisfy "net-im/telegram-desktop".
>
> emerge: searching for similar names...
> emerge: Maybe you meant any of these: net-im/telegram-desktop-bin,
> net-misc/grdesktop, net-im/mattermost-desktop-bin?
>
> I'm not interested in the binary version. There's this:
>
> https://packages.gentoo.org/packages/net-im/telegram-desktop
>
> I tried adding this to /etc/portage/package.accept_keywords because the
> newest versions are shown in yellow:
>
> net-im/telegram-desktop ~amd64
>
> but it didn't help.
The error message you received doesn't indicate a masked package, so adding to
package.accept_keywords will not help. "There are no ebuilds to satisfy..."
indicates that it cannot find the package---masked or otherwise---in the local
Portage tree.
Do you have the directory `/var/db/repos/gentoo/net-im/telegram-desktop` ? If
not, try an emerge-webrsync.
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-14 19:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 19:10 [gentoo-user] no ebuilds for telegram n952162
2020-05-14 19:23 ` Ashley Dixon [this message]
2020-05-14 19:28 ` Rich Freeman
2020-05-14 19:57 ` n952162
2020-05-14 20:08 ` Jack
2020-05-14 19:59 ` Matt Connell (Gmail)
2020-05-14 20:13 ` n952162
2020-05-14 20:19 ` Rich Freeman
2020-05-14 20:29 ` n952162
2020-05-14 21:03 ` Matt Connell (Gmail)
2020-05-14 21:08 ` n952162
2020-05-14 21:51 ` madscientistatlarge
2020-05-14 21:12 ` Ashley Dixon
2020-05-14 21:17 ` Matt Connell (Gmail)
2020-05-14 20:46 ` Rich Freeman
2020-05-14 21:10 ` n952162
2020-05-14 21:23 ` Dale
2020-05-14 21:36 ` Rich Freeman
2020-05-16 12:53 ` n952162
2020-05-16 14:19 ` Jack
2020-05-16 15:38 ` n952162
2020-05-16 15:56 ` n952162
2020-05-16 16:16 ` Jack
2020-05-16 16:23 ` n952162
2020-05-16 17:04 ` Jack
2020-05-16 17:32 ` Rich Freeman
2020-05-16 22:29 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200514192354.ir442u4xsboz5sfp@ad-gentoo-main.Home \
--to=ash@suugaku.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox