| 1 |
On 5/14/20 3:57 PM, n952162 wrote: |
| 2 |
> On 05/14/20 21:28, Rich Freeman wrote: |
| 3 |
> |
| 4 |
>> On Thu, May 14, 2020 at 3:10 PM n952162 <n952162@×××.de> wrote: |
| 5 |
>>> I tried to emerge net-im/telegram-desktop |
| 6 |
>>> but it said: |
| 7 |
>>> |
| 8 |
>>> emerge: there are no ebuilds to satisfy "net-im/telegram-desktop". |
| 9 |
>>> |
| 10 |
>> Are you sure there is nothing wrong with your local repository? I |
| 11 |
>> assume you're running an amd64 system/profile based on your |
| 12 |
>> accept_keywords change? |
| 13 |
> |
| 14 |
> Yes. |
| 15 |
> |
| 16 |
>> Nothing particularly exciting is going on with that package as far as |
| 17 |
>> I can tell from the git log. Have you tried looking at your |
| 18 |
>> repository in the net-im directory to see if it is there? What |
| 19 |
>> happens if you run an emerge --sync - you don't get any errors? |
| 20 |
> |
| 21 |
> No, I have no /var/db/pkg/net-im directory, even after running emerge |
| 22 |
> --sync. |
| 23 |
Where is your portage tree? Do you have anything at all under |
| 24 |
/var/db/pkg? What about /usr/portage/... Have you changed any of the |
| 25 |
defaults in your make.conf? |
| 26 |
> I'm running profile 17.1, desktop. |
| 27 |
> |
| 28 |
> Do I have to do something special to get net-im? |
| 29 |
|
| 30 |
No, it is just another group in the portage tree. If you are missing |
| 31 |
it, as others have suggested, you probably have some configuration issue |
| 32 |
somewhere under /etc/portage. |
| 33 |
|
| 34 |
It does seem odd that portage would offer you |
| 35 |
net-im/telegram-desktop-bin but not net-im/telegram-desktop. Have the |
| 36 |
permissions on the net-im folder or anything under it gotten weird? |
Archives