[gentoo-user] no ebuilds for telegram

2020-05-14 Thread n952162
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 interes

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Ashley Dixon
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-bi

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Rich Freeman
On Thu, May 14, 2020 at 3:10 PM n952162 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 ba

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread n952162
On 05/14/20 21:28, Rich Freeman wrote: On Thu, May 14, 2020 at 3:10 PM n952162 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 r

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Matt Connell (Gmail)
On 2020-05-14 14:10, n952162 wrote: emerge: there are no ebuilds to satisfy "net-im/telegram-desktop". As others have said, your local repository is out of date. Suggest an emerge-webrsync or emerge --sync and trying again. I'm not interested in the binary version.  There's this: https://

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Jack
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 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

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread n952162
On 05/14/20 21:59, Matt Connell (Gmail) wrote: On 2020-05-14 14:10, n952162 wrote: emerge: there are no ebuilds to satisfy "net-im/telegram-desktop". As others have said, your local repository is out of date. Suggest an emerge-webrsync or emerge --sync and trying again. I'm not interested

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Rich Freeman
On Thu, May 14, 2020 at 4:13 PM n952162 wrote: > > $ lf /var/db/pkg This is NOT your package repository and you should not ever touch anything in there unless you REALLY know what you're doing. You may end up having to reinstall everything on your system at the very least to fix the resulting da

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread n952162
Oops ... $ lf /usr/portage/net-im/telegram-desktop Manifest telegram-desktop-2.1.1.ebuild files/ telegram-desktop-2.1.2.ebuild metadata.xml telegram-desktop-2.1.3.ebuild telegram-desktop-2.0.1-r1.ebuild telegram-desktop-2.1.4.ebuild telegram-desktop-2.1.0.ebuild telegram-desktop-2.1.6.ebuild On

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Rich Freeman
On Thu, May 14, 2020 at 4:13 PM n952162 wrote: > > Action: sync for repo: gentoo, returned code = 0 > > * An update to portage is available. It is _highly_ recommended > * that you update portage now, before any other packages are updated. > > * To update portage, run 'emerge --oneshot porta

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Matt Connell (Gmail)
On 2020-05-14 15:29, n952162 wrote: $ lf /usr/portage/net-im/telegram-desktop Manifest telegram-desktop-2.1.1.ebuild files/ telegram-desktop-2.1.2.ebuild metadata.xml telegram-desktop-2.1.3.ebuild telegram-desktop-2.0.1-r1.ebuild telegram-desktop-2.1.4.ebuild telegram-desktop-2.1.0.ebuild telegra

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Ashley Dixon
On Thu, May 14, 2020 at 04:03:16PM -0500, Matt Connell (Gmail) wrote: > Do you have an alternative PORTDIR defined in /etc/portage/make.conf or > anywhere else? The default is /usr/portage, according to both of my > systems. PORTDIR shouldn't be used; it has been deprecated in favour of the `l

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread n952162
On 05/14/20 23:03, Matt Connell (Gmail) wrote: On 2020-05-14 15:29, n952162 wrote: $ lf /usr/portage/net-im/telegram-desktop Manifest telegram-desktop-2.1.1.ebuild files/ telegram-desktop-2.1.2.ebuild metadata.xml telegram-desktop-2.1.3.ebuild telegram-desktop-2.0.1-r1.ebuild telegram-desktop-

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread n952162
On 05/14/20 22:46, Rich Freeman wrote: On Thu, May 14, 2020 at 4:13 PM n952162 wrote: Action: sync for repo: gentoo, returned code = 0 * An update to portage is available. It is _highly_ recommended * that you update portage now, before any other packages are updated. * To update por

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Matt Connell (Gmail)
On 2020-05-14 16:12, Ashley Dixon wrote: PORTDIR shouldn't be used; it has been deprecated in favour of the `location` attribute in repos.conf. Thanks for the correction. I thought I remembered seeing a comment in make.conf about that, but the stage3 version still had it as of my most rec

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Dale
n952162 wrote: > On 05/14/20 22:46, Rich Freeman wrote: >> On Thu, May 14, 2020 at 4:13 PM n952162 wrote: >>> Action: sync for repo: gentoo, returned code = 0 >>> >>>    * An update to portage is available. It is _highly_ recommended >>>    * that you update portage now, before any other packages

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread Rich Freeman
On Thu, May 14, 2020 at 5:10 PM n952162 wrote: > > On 05/14/20 22:46, Rich Freeman wrote: > > On Thu, May 14, 2020 at 4:13 PM n952162 wrote: > >> Action: sync for repo: gentoo, returned code = 0 > >> > >>* An update to portage is available. It is _highly_ recommended > >>* that you update

Re: [gentoo-user] no ebuilds for telegram

2020-05-14 Thread madscientistatlarge
Just talked to doc. If you are willing to risk it come on over and lets shop! Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Thursday, May 14, 2020 3:08 PM, n952162 wrote: > On 05/14/20 23:03, Matt Connell (Gmail) wrote: > > > On 2020-05-14 15:29, n952162 wrote: > > >

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread n952162
I did an emerge --sync and then "emerge -v1 portage" and it blew up all over the place.  Log in the attachment. How can I get things reestablished?  Or, does gentoo simply require a smarter user than me, and I should go back to ubuntu? On 05/14/20 23:36, Rich Freeman wrote: On Thu, May 14, 202

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread Jack
On 5/16/20 8:53 AM, n952162 wrote: I did an emerge --sync and then "emerge -v1 portage" and it blew up all over the place.  Log in the attachment. How can I get things reestablished?  Or, does gentoo simply require a smarter user than me, and I should go back to ubuntu? I think the bottom line

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread n952162
e.g. sudo emerge -av =*sys-apps/portage-2.3.89-r3 * ? I got (amongst tons of other stuff):  * Error: The above package list contains packages which cannot be  * installed at the same time on the same syst

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread n952162
Okay, I'm blocked here, at the very beginning: sys-apps/portage:0   (sys-apps/portage-*2.3.89-r3:0*/0::gentoo, ebuild scheduled for merge) pulled in by     =sys-apps/portage-2.3.89-r3 (Argument)   (sys-apps/portage-*2.3.49:0/0*::gentoo, installed) pulled in by sys-apps/por

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread Jack
On 2020.05.16 11:56, n952162 wrote: Okay, I'm blocked here, at the very beginning: sys-apps/portage:0   (sys-apps/portage-*2.3.89-r3:0*/0::gentoo, ebuild scheduled for merge) pulled in by     =sys-apps/portage-2.3.89-r3 (Argument)   (sys-apps/portage-*2.3.49:0/0*::gentoo, ins

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread n952162
Oh oh oh!  Are you saying ... given "..." in this:  Synopsis: emerge [options] [action] [ebuild | tbz2file | file | @set | atom] ... that the solution to my problems is to - for each conflict - to select one of the two and put it on the same command line? e.g:     sudo emerge -av =sys-apps/por

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread Jack
On 5/16/20 12:23 PM, n952162 wrote: Oh oh oh! Are you saying ... given "..." in this:  Synopsis: emerge [options] [action] [ebuild | tbz2file | file | @set | atom] ... that the solution to my problems is to - for each conflict - to select one of the two and put it on the same command line? e

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread Rich Freeman
On Sat, May 16, 2020 at 1:04 PM Jack wrote: > > The basic idea is to upgrade as few packages at a time as possible - but > you can't do just one because of these conflicts. If you get stuck in a really bad dependency mess that is sometimes necessary. However, I'd first suggest just trying to upd

Re: [gentoo-user] no ebuilds for telegram

2020-05-16 Thread Dale
Rich Freeman wrote: > On Sat, May 16, 2020 at 1:04 PM Jack wrote: >> The basic idea is to upgrade as few packages at a time as possible - but >> you can't do just one because of these conflicts. > If you get stuck in a really bad dependency mess that is sometimes necessary. > > However, I'd first