1 |
On Thu, May 14, 2020 at 3:10 PM n952162 <n952162@×××.de> wrote: |
2 |
> |
3 |
> I tried to emerge net-im/telegram-desktop |
4 |
> but it said: |
5 |
> |
6 |
> emerge: there are no ebuilds to satisfy "net-im/telegram-desktop". |
7 |
> |
8 |
|
9 |
Are you sure there is nothing wrong with your local repository? I |
10 |
assume you're running an amd64 system/profile based on your |
11 |
accept_keywords change? |
12 |
|
13 |
Nothing particularly exciting is going on with that package as far as |
14 |
I can tell from the git log. Have you tried looking at your |
15 |
repository in the net-im directory to see if it is there? What |
16 |
happens if you run an emerge --sync - you don't get any errors? |
17 |
|
18 |
In theory you can just delete the entire repository directory and run |
19 |
emerge --sync again to re-create a clean version if in doubt. |
20 |
|
21 |
Also, do a grep -r telegram in /etc/portage and see if the package is |
22 |
mentioned in any of your config files. |
23 |
|
24 |
Oh, and while your email seems to be using standard ASCII, make sure |
25 |
you're not copy/pasting em-dashes or anything non-ASCII into your |
26 |
terminal. I have no idea how portage handles such things but if you |
27 |
paste a utf8 em-dash into the package name I wouldn't be surprised if |
28 |
it doesn't find it. |
29 |
|
30 |
-- |
31 |
Rich |