On 5/14/20 3:57 PM, n952162 wrote:
On 05/14/20 21:28, Rich Freeman wrote:

On Thu, May 14, 2020 at 3:10 PM n952162 <n952...@web.de> wrote:
I tried to emerge net-im/telegram-desktop
but it said:

emerge: there are no ebuilds to satisfy "net-im/telegram-desktop".

Are you sure there is nothing wrong with your local repository? I
assume you're running an amd64 system/profile based on your
accept_keywords change?

Yes.

Nothing particularly exciting is going on with that package as far as
I can tell from the git log.  Have you tried looking at your
repository in the net-im directory to see if it is there?  What
happens if you run an emerge --sync - you don't get any errors?

No, I have no /var/db/pkg/net-im directory, even after running emerge
--sync.
Where is your portage tree?  Do you have anything at all under /var/db/pkg?  What about /usr/portage/...  Have you changed any of the defaults in your make.conf?
I'm running profile 17.1, desktop.

Do I have to do something special to get net-im?

No, it is just another group in the portage tree.  If you are missing it, as others have suggested, you probably have some configuration issue somewhere under /etc/portage.

It does seem odd that portage would offer you net-im/telegram-desktop-bin but not net-im/telegram-desktop.  Have the permissions on the net-im folder or anything under it gotten weird?



Reply via email to