[gentoo-user] no ebuilds for telegram

[gentoo-user] no ebuilds for telegram

[n952162]

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

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.

Can I emerge this as source?


[-- Attachment #2: Type: text/html, Size: 1210 bytes --]

Re: [gentoo-user] no ebuilds for telegram

[Ashley Dixon]

[-- 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 --]

Re: [gentoo-user] no ebuilds for telegram

[Rich Freeman]

On Thu, May 14, 2020 at 3:10 PM n952162 <n952162@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?

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?

In theory you can just delete the entire repository directory and run
emerge --sync again to re-create a clean version if in doubt.

Also, do a grep -r telegram in /etc/portage and see if the package is
mentioned in any of your config files.

Oh, and while your email seems to be using standard ASCII, make sure
you're not copy/pasting em-dashes or anything non-ASCII into your
terminal.  I have no idea how portage handles such things but if you
paste a utf8 em-dash into the package name I wouldn't be surprised if
it doesn't find it.

-- 
Rich

Re: [gentoo-user] no ebuilds for telegram

[n952162]

On 05/14/20 21:28, Rich Freeman wrote:

> On Thu, May 14, 2020 at 3:10 PM n952162 <n952162@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.
I'm running profile 17.1, desktop.

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

Re: [gentoo-user] no ebuilds for telegram

[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 <n952162@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?

Re: [gentoo-user] no ebuilds for telegram

[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://packages.gentoo.org/packages/net-im/telegram-desktop

I have this package in my local repositories.  Though, I didn't know it 
existed before today; I've been using the -bin package myself.  I might 
have to make the switch.

Re: [gentoo-user] no ebuilds for telegram

[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 in the binary version. There's this:
>>
>> https://packages.gentoo.org/packages/net-im/telegram-desktop
>
> I have this package in my local repositories.  Though, I didn't know 
> it existed before today; I've been using the -bin package myself.  I 
> might have to make the switch.
>

...
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 portage' now.



$ lf /var/db/pkg
acct-group/         app-text/     mail-mta/ net-nds/       sys-power/
app-accessibility/  app-vim/      media-fonts/ net-print/     sys-process/
app-admin/          dev-db/       media-gfx/ net-wireless/  virtual/
app-arch/           dev-lang/     media-libs/ perl-core/     www-client/
app-cdr/            dev-libs/     media-sound/ sys-apps/      x11-apps/
app-crypt/          dev-perl/     media-video/ sys-auth/      x11-base/
app-dicts/          dev-python/   net-analyzer/ sys-block/     x11-drivers/
app-editors/        dev-qt/       net-dialup/ sys-boot/      x11-libs/
app-emulation/      dev-ruby/     net-dns/ sys-devel/     x11-misc/
app-eselect/        dev-util/     net-firewall/ sys-firmware/  x11-plugins/
app-misc/           dev-vcs/      net-libs/ sys-fs/        x11-terms/
app-portage/        gnome-base/   net-mail/ sys-kernel/    x11-themes/
app-shells/         mail-client/  net-misc/ sys-libs/      x11-wm/

Re: [gentoo-user] no ebuilds for telegram

[Rich Freeman]

On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 damage.

You can find the location of your package repositories by running
emerge --info, and looking for the repositories section.  Each
repository (such as the gentoo repo) will have a location field which
is the path to its location on your disk.

-- 
Rich

Re: [gentoo-user] no ebuilds for telegram

[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 05/14/20 22:19, Rich Freeman wrote:
> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 damage.
>
> You can find the location of your package repositories by running
> emerge --info, and looking for the repositories section.  Each
> repository (such as the gentoo repo) will have a location field which
> is the path to its location on your disk.
>

Re: [gentoo-user] no ebuilds for telegram

[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 telegram-desktop-2.1.6.ebuild

Hmm.  Seems you have the ebuild for the latest (as of today) version, as 
I do, but when you try to use the ebuild, emerge isn't finding it.

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.

Re: [gentoo-user] no ebuilds for telegram

[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-2.1.4.ebuild
>> telegram-desktop-2.1.0.ebuild telegram-desktop-2.1.6.ebuild
>
> Hmm.  Seems you have the ebuild for the latest (as of today) version,
> as I do, but when you try to use the ebuild, emerge isn't finding it.
>
> 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.
>
$ grep PORT /etc/portage/make.conf
PORTDIR="/usr/portage"

Re: [gentoo-user] no ebuilds for telegram

[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 <n952162@web.de> wrote:

> 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-2.1.4.ebuild
> > > telegram-desktop-2.1.0.ebuild telegram-desktop-2.1.6.ebuild
> >
> > Hmm.  Seems you have the ebuild for the latest (as of today) version,
> > as I do, but when you try to use the ebuild, emerge isn't finding it.
> > 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.
>
> $ grep PORT /etc/portage/make.conf
> PORTDIR="/usr/portage"

Re: [gentoo-user] no ebuilds for telegram

[Ashley Dixon]

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

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  `location`
attribute in repos.conf. See bug #546210 and [1]. Anyway, modern systems  should
really migrate to /var/db/repos just for  the  sake  of  uniformity  across  the
Gentoo community.

[1] https://wiki.gentoo.org/wiki//etc/portage/make.conf#PORTDIR

-- 

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 --]

Re: [gentoo-user] no ebuilds for telegram

[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 
recent install, and I try to tread lightly in make.conf so its still there.

The question for n952162 then comes whether the location attribute has 
been changed.

Re: [gentoo-user] no ebuilds for telegram

[Rich Freeman]

On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.

...and?  Did you update portage as it was _highly_ recommended that
you do so first?  What version of portage are you using?  This appears
on the top line of emerge --info.

-- 
Rich

Re: [gentoo-user] no ebuilds for telegram

[n952162]

On 05/14/20 22:46, Rich Freeman wrote:
> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
> ...and?  Did you update portage as it was _highly_ recommended that
> you do so first?  What version of portage are you using?  This appears
> on the top line of emerge --info.
>

$ emerge --info
Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, gcc-7.3.0,
glibc-2.26-r7, 4.14.65-gentoo x86_64)

Re: [gentoo-user] no ebuilds for telegram

[Dale]

n952162 wrote:
> On 05/14/20 22:46, Rich Freeman wrote:
>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>> ...and?  Did you update portage as it was _highly_ recommended that
>> you do so first?  What version of portage are you using?  This appears
>> on the top line of emerge --info.
>>
>
> $ emerge --info
> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, gcc-7.3.0,
> glibc-2.26-r7, 4.14.65-gentoo x86_64)
>
>
>
>

This is what it looks like in my emerge --info.  Mine will be different
from yours since mine is in a different location. 


Repositories:

gentoo
    location: /var/cache/portage/tree
    sync-type: rsync
    sync-uri: rsync://rsync26.us.gentoo.org/gentoo-portage
    priority: -1000
    sync-rsync-verify-max-age: 24
    sync-rsync-extra-opts:
    sync-rsync-verify-jobs: 1
    sync-rsync-verify-metamanifest: no


You are looking for the section called Repositories and then Location. 
If you have any overlays active, those should show below that. 

Dale

:-)  :-) 

Re: [gentoo-user] no ebuilds for telegram

[Rich Freeman]

On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>
> On 05/14/20 22:46, Rich Freeman wrote:
> > On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
> > ...and?  Did you update portage as it was _highly_ recommended that
> > you do so first?  What version of portage are you using?  This appears
> > on the top line of emerge --info.
> >
>
> $ emerge --info
> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, gcc-7.3.0,
> glibc-2.26-r7, 4.14.65-gentoo x86_64)

That version of portage has been removed from the repo for over a year.

I would update your system so that is current and then try again.  I
believe that version of portage should still support EAPI 7 but there
could be some other issue that is giving it problems with more recent
packages in the tree.

-- 
Rich

Re: [gentoo-user] no ebuilds for telegram

[n952162]

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

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, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>> On 05/14/20 22:46, Rich Freeman wrote:
>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>>> ...and?  Did you update portage as it was _highly_ recommended that
>>> you do so first?  What version of portage are you using?  This appears
>>> on the top line of emerge --info.
>>>
>> $ emerge --info
>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, gcc-7.3.0,
>> glibc-2.26-r7, 4.14.65-gentoo x86_64)
> That version of portage has been removed from the repo for over a year.
>
> I would update your system so that is current and then try again.  I
> believe that version of portage should still support EAPI 7 but there
> could be some other issue that is giving it problems with more recent
> packages in the tree.
>


[-- Attachment #2: portage --]
[-- Type: text/plain, Size: 30070 bytes --]


These are the packages that would be merged, in order:

Calculating dependencies  
 * IMPORTANT: 23 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

 * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
 * sections of the emerge man page to learn how to update config files.
.... done!
[ebuild     U  ] dev-lang/python-exec-2.4.6-r1:2::gentoo [2.4.6:2::gentoo] PYTHON_TARGETS="(pypy3) (python2_7) (python3_6) (python3_7*) (python3_8%*) (-jython2_7%*) (-pypy%*) (-python3_4%*) (-python3_5%*)" 86 KiB
[ebuild  N     ] virtual/libcrypt-1-r1:0/1::gentoo  USE="static-libs" 0 KiB
[ebuild  N     ] dev-perl/TimeDate-2.300.0::gentoo  31 KiB
[ebuild  N     ] dev-perl/MailTools-2.190.0::gentoo  USE="-examples -test" 55 KiB
[ebuild  N     ] dev-perl/Error-0.170.250::gentoo  USE="-test" 32 KiB
[ebuild     U  ] dev-lang/perl-5.30.1:0/5.30::gentoo [5.24.3-r1:0/5.24::gentoo] USE="berkdb gdbm -debug -doc -ithreads" 12200 KiB
[ebuild  N     ] virtual/perl-Digest-SHA-6.20.0::gentoo  0 KiB
[ebuild  N     ] dev-perl/Digest-HMAC-1.30.0-r1::gentoo  0 KiB
[ebuild  N     ] dev-perl/Authen-SASL-2.160.0-r1::gentoo  USE="-kerberos" 0 KiB
[ebuild  NS    ] dev-lang/python-3.7.7-r2:3.7/3.7m::gentoo [2.7.15:2.7::gentoo, 3.6.5:3.6/3.6m::gentoo] USE="gdbm ipv6 ncurses readline sqlite ssl xml -bluetooth -build -examples -hardened -libressl -test -tk -wininst" 16879 KiB
[ebuild  N     ] dev-vcs/git-2.26.2::gentoo  USE="blksha1 curl gpg iconv nls pcre pcre-jit perl threads webdav -cgi -cvs -doc -emacs -gnome-keyring -highlight -libressl (-mediawiki) (-mediawiki-experimental) -perforce (-ppcsha1) -subversion -test -tk -xinetd" PYTHON_SINGLE_TARGET="python3_7 -python3_6" 6319 KiB
[ebuild     U  ] dev-python/setuptools-44.1.0::gentoo [36.7.2::gentoo] USE="-test" PYTHON_TARGETS="python2_7 python3_7%* (-pypy3) -python3_6* (-python3_8) (-pypy%) (-python3_4%) (-python3_5%)" 839 KiB
[ebuild     U  ] dev-python/certifi-2019.11.28::gentoo [2018.4.16::gentoo] PYTHON_TARGETS="python2_7 python3_7* (-pypy3) -python3_6* (-python3_8) (-pypy%) (-python3_4%) (-python3_5%)" 153 KiB
[ebuild     U  ] app-portage/gemato-14.3::gentoo [14.0::gentoo] USE="gpg -test -tools (-blake2%*) (-bzip2%*) (-lzma%) (-sha3%)" PYTHON_TARGETS="python3_7* (-pypy3) -python3_6* (-python3_8) (-pypy%) (-python2_7%*) (-python3_4%) (-python3_5%)" 70 KiB
[ebuild     U *] sys-apps/portage-9999::gentoo [2.3.49::gentoo] USE="(ipc) native-extensions rsync-verify xattr -apidoc% -binpkg-zstd% -build -doc -gentoo-dev (-selinux) (-epydoc%)" PYTHON_TARGETS="python3_7* -pypy3% -python3_6* (-python3_8) (-pypy%) (-python2_7%*) (-python3_4%) (-python3_5%)" 0 KiB

Total: 15 packages (6 upgrades, 8 new, 1 in new slot), Size of downloads: 36659 KiB

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

dev-lang/perl:0

  (dev-lang/perl-5.24.3-r1:0/5.24::gentoo, installed) pulled in by
    dev-lang/perl:0/5.24= required by (virtual/perl-Scalar-List-Utils-1.420.200_rc-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                     
    dev-lang/perl:0/5.24=[-build(-)] required by (dev-perl/File-DesktopEntry-0.40.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                      
    dev-lang/perl:0/5.24= required by (virtual/perl-Data-Dumper-2.160.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                          
    dev-lang/perl:0/5.24= required by (virtual/perl-Digest-MD5-2.540.0-r3:0/0::gentoo, installed)
                 ^^^^^^^^                                                                         
    dev-lang/perl:0/5.24= required by (virtual/perl-Time-HiRes-1.974.100-r2:0/0::gentoo, installed)
                 ^^^^^^^^                                                                           
    dev-lang/perl:0/5.24= required by (virtual/perl-IO-Socket-IP-0.370.0-r3:0/0::gentoo, installed)
                 ^^^^^^^^                                                                           
    dev-lang/perl:0/5.24= required by (virtual/perl-ExtUtils-ParseXS-3.310.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                               
    dev-lang/perl:0/5.24= required by (virtual/perl-IO-Compress-2.69.1_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                            
    dev-lang/perl:0/5.24= required by (virtual/perl-parent-0.234.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                     
    dev-lang/perl:0/5.24= required by (virtual/perl-Perl-OSType-1.9.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                        
    dev-lang/perl:0/5.24=[-build(-)] required by (perl-core/File-Temp-0.230.400-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                  
    dev-lang/perl:0/5.24= required by (virtual/perl-Parse-CPAN-Meta-1.441.700.100_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                       
    dev-lang/perl:0/5.24= required by (virtual/perl-podlators-4.70.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                       
    dev-lang/perl:0/5.24= required by (sys-apps/texinfo-6.3:0/0::gentoo, installed)
                 ^^^^^^^^                                                           
    dev-lang/perl:0/5.24= required by (virtual/perl-Storable-2.560.100_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                            
    dev-lang/perl:0/5.24= required by (virtual/perl-Carp-1.400.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                   
    dev-lang/perl:0/5.24= required by (virtual/perl-Getopt-Long-2.480.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                          
    dev-lang/perl:0/5.24= required by (virtual/perl-Compress-Raw-Zlib-2.69.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                               
    dev-lang/perl:0/5.24= required by (virtual/perl-libnet-3.80.100_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                         
    dev-lang/perl:0/5.24= required by (virtual/perl-JSON-PP-2.273.0.100_rc-r6:0/0::gentoo, installed)
                 ^^^^^^^^                                                                             
    dev-lang/perl:0/5.24= required by (dev-perl/IO-Socket-SSL-2.48.0:0/0::gentoo, installed)
                 ^^^^^^^^                                                                    
    dev-lang/perl:0/5.24= required by (virtual/perl-CPAN-Meta-2.150.5-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                        
    dev-lang/perl:0/5.24= required by (virtual/perl-Exporter-5.720.0-r3:0/0::gentoo, installed)
                 ^^^^^^^^                                                                       
    dev-lang/perl:0/5.24= required by (virtual/perl-MIME-Base64-3.150.0-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                          
    dev-lang/perl:0/5.24= required by (dev-perl/Locale-gettext-1.70.0:0/0::gentoo, installed)
                 ^^^^^^^^                                                                     
    dev-lang/perl:0/5.24= required by (virtual/perl-Text-ParseWords-3.300.0-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                              
    dev-lang/perl:0/5.24= required by (virtual/perl-Encode-2.800.100_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                          
    dev-lang/perl:0/5.24= required by (virtual/perl-File-Temp-0.230.400-r5:0/0::gentoo, installed)
                 ^^^^^^^^                                                                          
    dev-lang/perl:0/5.24= required by (virtual/perl-ExtUtils-Manifest-1.700.0-r5:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                
    dev-lang/perl:0/5.24= required by (virtual/perl-IO-1.360.100_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                      
    dev-lang/perl:0/5.24= required by (virtual/perl-ExtUtils-Install-2.40.0-r3:0/0::gentoo, installed)
                 ^^^^^^^^                                                                              
    dev-lang/perl:0/5.24= required by (virtual/perl-Compress-Raw-Bzip2-2.69.0-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                
    dev-lang/perl:0/5.24= required by (virtual/perl-ExtUtils-MakeMaker-7.100.200_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                      
    dev-lang/perl:0/5.24= required by (virtual/perl-Time-Local-1.230.0-r6:0/0::gentoo, installed)
                 ^^^^^^^^                                                                         
    dev-lang/perl:0/5.24= required by (virtual/perl-Test-Harness-3.360.100_rc-r3:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                
    =dev-lang/perl-5.24.3* required by (virtual/perl-Time-HiRes-1.974.100-r2:0/0::gentoo, installed)
    ^              ^^^^^^^                                                                           
    dev-lang/perl:0/5.24= required by (virtual/perl-version-0.991.600-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                        
    dev-lang/perl:0/5.24= required by (virtual/perl-ExtUtils-CBuilder-0.280.225-r2:0/0::gentoo, installed)
                 ^^^^^^^^                                                                                  
    dev-lang/perl:0/5.24= required by (virtual/perl-CPAN-Meta-YAML-0.18.0-r3:0/0::gentoo, installed)
                 ^^^^^^^^                                                                            
    dev-lang/perl:0/5.24= required by (dev-perl/Net-SSLeay-1.820.0:0/0::gentoo, installed)
                 ^^^^^^^^                                                                  
    dev-lang/perl:0/5.24=[-build(-)] required by (dev-perl/TermReadKey-2.330.0:0/0::gentoo, installed)
                 ^^^^^^^^                                                                              
    dev-lang/perl:0/5.24= required by (virtual/perl-File-Path-2.130.0:0/0::gentoo, installed)
                 ^^^^^^^^                                                                     
    dev-lang/perl:0/5.24= required by (virtual/perl-Module-Metadata-1.0.31-r1:0/0::gentoo, installed)
                 ^^^^^^^^                                                                             
    dev-lang/perl:0/5.24= required by (virtual/perl-File-Spec-3.630.100_rc-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                             
    dev-lang/perl:0/5.24= required by (virtual/perl-XSLoader-0.220.0-r4:0/0::gentoo, installed)
                 ^^^^^^^^                                                                       
    (and 72 more with the same problems)

  (dev-lang/perl-5.30.1:0/5.30::gentoo, ebuild scheduled for merge) pulled in by
    =dev-lang/perl-5.30* required by (virtual/perl-Digest-SHA-6.20.0:0/0::gentoo, ebuild scheduled for merge)
    ^              ^^^^^                                                                                      

sys-apps/portage:0

  (sys-apps/portage-9999:0/0::gentoo, ebuild scheduled for merge) pulled in by
    sys-apps/portage (Argument)

  (sys-apps/portage-2.3.49:0/0::gentoo, installed) pulled in by
    sys-apps/portage[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                                

app-portage/gemato:0

  (app-portage/gemato-14.3:0/0::gentoo, ebuild scheduled for merge) pulled in by
    >=app-portage/gemato-14[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-)] required by (sys-apps/portage-9999:0/0::gentoo, ebuild scheduled for merge)
                                                                                                                                                                                                                                                                                                                                                                 

  (app-portage/gemato-14.0:0/0::gentoo, installed) pulled in by
    >=app-portage/gemato-14[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (sys-apps/portage-2.3.49:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                               

dev-python/setuptools:0

  (dev-python/setuptools-44.1.0:0/0::gentoo, ebuild scheduled for merge) pulled in by
    dev-python/setuptools[python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-)] required by (dev-python/certifi-2019.11.28:0/0::gentoo, ebuild scheduled for merge)
                                                                                                                                                                                                                                                                                                                                                                                                                                       
    >=dev-python/setuptools-42.0.2[python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-)] required by (dev-python/certifi-2019.11.28:0/0::gentoo, ebuild scheduled for merge)
    ^^                      ^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                              
    (and 1 more with the same problems)

  (dev-python/setuptools-36.7.2:0/0::gentoo, installed) pulled in by
    dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/certifi-2018.4.16:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                                                                 
    >=dev-python/setuptools-34[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (app-portage/gemato-14.0:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                                  
    dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (app-portage/gemato-14.0:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                             
    dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/pygments-2.2.0:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                                                              
    dev-python/setuptools[python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/pyblake2-1.1.2:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                  
    dev-python/setuptools[python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_python3_6(-),-python_single_target_python3_7(-)] required by (dev-python/pyxattr-0.6.0-r1:0/0::gentoo, installed)
                                                                                                                                                                                                                            

dev-python/certifi:0

  (dev-python/certifi-2019.11.28:0/0::gentoo, ebuild scheduled for merge) pulled in by
    >=dev-python/certifi-2016.9.26[python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-)] required by (dev-python/setuptools-44.1.0:0/0::gentoo, ebuild scheduled for merge)
                                                                                                                                                                                                                                                                                                                                                                                                                                               

  (dev-python/certifi-2018.4.16:0/0::gentoo, installed) pulled in by
    >=dev-python/certifi-2016.9.26[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by (dev-python/setuptools-36.7.2:0/0::gentoo, installed)
                                                                                                                                                                                                                                                                                                                                                                       

NOTE: Use the '--verbose-conflicts' option to display parents omitted above

!!! The slot conflict(s) shown above involve package(s) which may need to
!!! be rebuilt in order to solve the conflict(s). However, the following
!!! package(s) cannot be rebuilt for the reason(s) shown:

  (virtual/perl-MIME-Base64-3.150.0-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Text-ParseWords-3.300.0-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Encode-2.800.100_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-podlators-4.70.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Compress-Raw-Zlib-2.69.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-libnet-3.80.100_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Data-Dumper-2.160.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Digest-MD5-2.540.0-r3:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-CPAN-Meta-2.150.5-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-ExtUtils-Manifest-1.700.0-r5:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Test-Harness-3.360.100_rc-r3:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-File-Path-2.130.0:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Exporter-5.720.0-r3:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Perl-OSType-1.9.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-CPAN-Meta-YAML-0.18.0-r3:0/0::gentoo, installed): ebuild is masked or unavailable
  (dev-perl/File-DesktopEntry-0.40.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-ExtUtils-Install-2.40.0-r3:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-IO-Socket-IP-0.370.0-r3:0/0::gentoo, installed): ebuild is masked or unavailable
  (dev-perl/TermReadKey-2.330.0:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Time-Local-1.230.0-r6:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Parse-CPAN-Meta-1.441.700.100_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (dev-perl/IO-Socket-SSL-2.48.0:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Compress-Raw-Bzip2-2.69.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-IO-Compress-2.69.1_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Storable-2.560.100_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (sys-apps/texinfo-6.3:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Scalar-List-Utils-1.420.200_rc-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-JSON-PP-2.273.0.100_rc-r6:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Module-Metadata-1.0.31-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-parent-0.234.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-File-Spec-3.630.100_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-ExtUtils-MakeMaker-7.100.200_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-ExtUtils-ParseXS-3.310.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (perl-core/File-Temp-0.230.400-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-XSLoader-0.220.0-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-ExtUtils-CBuilder-0.280.225-r2:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-File-Temp-0.230.400-r5:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Time-HiRes-1.974.100-r2:0/0::gentoo, installed): ebuild is masked or unavailable
  (dev-perl/Net-SSLeay-1.820.0:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-IO-1.360.100_rc-r4:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Getopt-Long-2.480.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-version-0.991.600-r1:0/0::gentoo, installed): ebuild is masked or unavailable
  (virtual/perl-Carp-1.400.0-r1:0/0::gentoo, installed): ebuild is masked or unavailable


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


!!! The following installed packages are masked:
- x11-drivers/xf86-input-keyboard-1.9.0::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Piotr Karbowski <slashbeast@gentoo.org> (2020-05-03)
# Obsolete input drivers, use x11-drivers/xf86-input-libinput
# or x11-drivers/xf86-input-evdev instead.
# Removal in 30 days.

- sys-kernel/linux-firmware-20181001::gentoo (masked by: linux-firmware no-source-code freedist license(s))
A copy of the 'linux-firmware' license is located at '/usr/portage/licenses/linux-firmware'.

A copy of the 'no-source-code' license is located at '/usr/portage/licenses/no-source-code'.

A copy of the 'freedist' license is located at '/usr/portage/licenses/freedist'.

- mail-client/thunderbird-52.9.1::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Ian Stakenvicius <axs@gentoo.org> (2018-11-07)
# on behalf of Mozilla Project <mozilla@gentoo.org>
# Mask old/vuln thunderbird for removal by 2019,
# see security bug 670102

- sys-devel/binutils-2.30-r4::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Michał Górny <mgorny@gentoo.org>, Andreas K. Hüttel <dilfridge@gentoo.org>,
# Matthias Maier <tamiko@gentoo.org> (2017-05-21 and later updates)
# These old versions of toolchain packages (binutils, gcc, glibc) are no
# longer officially supported and are not suitable for general use. Using
# these packages can result in build failures (and possible breakage) for
# many packages, and may leave your system vulnerable to known security
# exploits.
# If you still use one of these old toolchain packages, please upgrade (and
# switch the compiler / the binutils) ASAP. If you need them for a specific
# (isolated) use case, feel free to unmask them on your system.

- media-fonts/font-bh-type1-1.0.3-r1::gentoo (masked by: bh-luxi license(s))
A copy of the 'bh-luxi' license is located at '/usr/portage/licenses/bh-luxi'.

- sys-libs/glibc-2.26-r7::gentoo (masked by: package.mask)
- sys-libs/binutils-libs-2.30-r4::gentoo (masked by: package.mask)
- media-fonts/font-bh-ttf-1.0.3-r1::gentoo (masked by: bh-luxi license(s))
- x11-drivers/xf86-input-mouse-1.9.3::gentoo (masked by: package.mask)
- sys-kernel/gentoo-sources-4.14.65::gentoo (masked by: linux-firmware license(s))
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

Re: [gentoo-user] no ebuilds for telegram

[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 is that Gentoo needs to be updated more often 
than yearly.  Others may also comment, but right now, I think a 
reinstall might be easier than working through all the problems, unless 
you are trying to learn more about how things work.

My first question is why you have portage-9999 unmasked?  I suggest 
going for the lowest version currently in the tree.  I'm not sure if 
your first step should really be portage itself, or upgrading packages 
where the installed version is now masked due to security errors or 
being too out of date.

Jack

>
>
> On 05/14/20 23:36, Rich Freeman wrote:
>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>>> On 05/14/20 22:46, Rich Freeman wrote:
>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>>>> ...and?  Did you update portage as it was _highly_ recommended that
>>>> you do so first?  What version of portage are you using? This appears
>>>> on the top line of emerge --info.
>>>>
>>> $ emerge --info
>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, 
>>> gcc-7.3.0,
>>> glibc-2.26-r7, 4.14.65-gentoo x86_64)
>> That version of portage has been removed from the repo for over a year.
>>
>> I would update your system so that is current and then try again.  I
>> believe that version of portage should still support EAPI 7 but there
>> could be some other issue that is giving it problems with more recent
>> packages in the tree.
>>
>

Re: [gentoo-user] no ebuilds for telegram

[n952162]

[-- Attachment #1: Type: text/plain, Size: 2639 bytes --]

e.g.

sudo emerge -av =*sys-apps/portage-2.3.89-r3
<https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.89-r3.ebuild>*

?

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 system.

   (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) pulled in by
     app-portage/gentoolkit required by @selected

On 05/16/20 16:19, Jack wrote:
> 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 is that Gentoo needs to be updated more often
> than yearly.  Others may also comment, but right now, I think a
> reinstall might be easier than working through all the problems,
> unless you are trying to learn more about how things work.
>
> My first question is why you have portage-9999 unmasked?  I suggest
> going for the lowest version currently in the tree.  I'm not sure if
> your first step should really be portage itself, or upgrading packages
> where the installed version is now masked due to security errors or
> being too out of date.
>
> Jack
>
>>
>>
>> On 05/14/20 23:36, Rich Freeman wrote:
>>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>>>> On 05/14/20 22:46, Rich Freeman wrote:
>>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>>>>> ...and?  Did you update portage as it was _highly_ recommended that
>>>>> you do so first?  What version of portage are you using? This appears
>>>>> on the top line of emerge --info.
>>>>>
>>>> $ emerge --info
>>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0,
>>>> gcc-7.3.0,
>>>> glibc-2.26-r7, 4.14.65-gentoo x86_64)
>>> That version of portage has been removed from the repo for over a year.
>>>
>>> I would update your system so that is current and then try again.  I
>>> believe that version of portage should still support EAPI 7 but there
>>> could be some other issue that is giving it problems with more recent
>>> packages in the tree.
>>>
>>
>


[-- Attachment #2: Type: text/html, Size: 4667 bytes --]

Re: [gentoo-user] no ebuilds for telegram

[n952162]

[-- Attachment #1: Type: text/plain, Size: 3572 bytes --]

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/portage[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]
    required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed)

I'm trying to update from 2.3.49 to 2.3.89 and it tells me it has a slot
conflict there.  I can hardly delete portage and then add it ...


On 05/16/20 17:38, n952162 wrote:
>
> e.g.
>
> sudo emerge -av =*sys-apps/portage-2.3.89-r3
> <https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.89-r3.ebuild>*
>
> ?
>
> 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 system.
>
>   (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) pulled in by
>     app-portage/gentoolkit required by @selected
>
> On 05/16/20 16:19, Jack wrote:
>> 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 is that Gentoo needs to be updated more often
>> than yearly.  Others may also comment, but right now, I think a
>> reinstall might be easier than working through all the problems,
>> unless you are trying to learn more about how things work.
>>
>> My first question is why you have portage-9999 unmasked?  I suggest
>> going for the lowest version currently in the tree.  I'm not sure if
>> your first step should really be portage itself, or upgrading
>> packages where the installed version is now masked due to security
>> errors or being too out of date.
>>
>> Jack
>>
>>>
>>>
>>> On 05/14/20 23:36, Rich Freeman wrote:
>>>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>>>>> On 05/14/20 22:46, Rich Freeman wrote:
>>>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>>>>>> ...and?  Did you update portage as it was _highly_ recommended that
>>>>>> you do so first?  What version of portage are you using? This
>>>>>> appears
>>>>>> on the top line of emerge --info.
>>>>>>
>>>>> $ emerge --info
>>>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0,
>>>>> gcc-7.3.0,
>>>>> glibc-2.26-r7, 4.14.65-gentoo x86_64)
>>>> That version of portage has been removed from the repo for over a
>>>> year.
>>>>
>>>> I would update your system so that is current and then try again.  I
>>>> believe that version of portage should still support EAPI 7 but there
>>>> could be some other issue that is giving it problems with more recent
>>>> packages in the tree.
>>>>
>>>
>>
>


[-- Attachment #2: Type: text/html, Size: 5991 bytes --]

Re: [gentoo-user] no ebuilds for telegram

[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, installed) pulled in by
>     
> sys-apps/portage[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]
>    required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo,  
> installed)
> 
> I'm trying to update from 2.3.49 to 2.3.89 and it tells me it has a  
> slot
> conflict there.  I can hardly delete portage and then add it ...
First, if you post a slot conflict, post the whole thing.   (This one  
is OK, but your previous one for gentoolkit only showed one of the two  
entries.  In this case, you probably need to upgrade gentoolkit and  
portage at the same time.

> 
> 
> On 05/16/20 17:38, n952162 wrote:
>> 
>> e.g.
>> 
>> sudo emerge -av =*sys-apps/portage-2.3.89-r3
>> <https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.89-r3.ebuild>*
>> 
>> ?
>> 
>> 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 system.
>> 
>>   (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) pulled in  
>> by
>>     app-portage/gentoolkit required by @selected
>> 
>> On 05/16/20 16:19, Jack wrote:
>>> 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 is that Gentoo needs to be updated more  
>>> often
>>> than yearly.  Others may also comment, but right now, I think a
>>> reinstall might be easier than working through all the problems,
>>> unless you are trying to learn more about how things work.
>>> 
>>> My first question is why you have portage-9999 unmasked?  I suggest
>>> going for the lowest version currently in the tree.  I'm not sure if
>>> your first step should really be portage itself, or upgrading
>>> packages where the installed version is now masked due to security
>>> errors or being too out of date.
>>> 
>>> Jack
>>> 
>>>> 
>>>> 
>>>> On 05/14/20 23:36, Rich Freeman wrote:
>>>>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>>>>>> On 05/14/20 22:46, Rich Freeman wrote:
>>>>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>>>>>>> ...and?  Did you update portage as it was _highly_ recommended  
>>>>>>> that
>>>>>>> you do so first?  What version of portage are you using? This
>>>>>>> appears
>>>>>>> on the top line of emerge --info.
>>>>>>> 
>>>>>> $ emerge --info
>>>>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0,
>>>>>> gcc-7.3.0,
>>>>>> glibc-2.26-r7, 4.14.65-gentoo x86_64)
>>>>> That version of portage has been removed from the repo for over a
>>>>> year.
>>>>> 
>>>>> I would update your system so that is current and then try  
>>>>> again.  I
>>>>> believe that version of portage should still support EAPI 7 but  
>>>>> there
>>>>> could be some other issue that is giving it problems with more  
>>>>> recent
>>>>> packages in the tree.
>>>>> 
>>>> 
>>> 
>> 
> 

Re: [gentoo-user] no ebuilds for telegram

[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/portage-2.3.89-r3
=app-portage/gemato-14.3  =dev-python/setuptools-44.1.0
dev-python/certifi-2019.11.28


On 05/16/20 18:16, Jack wrote:
> 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, installed) pulled in by
>> sys-apps/portage[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]
>>    required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed)
>>
>> I'm trying to update from 2.3.49 to 2.3.89 and it tells me it has a slot
>> conflict there.  I can hardly delete portage and then add it ...
> First, if you post a slot conflict, post the whole thing.   (This one
> is OK, but your previous one for gentoolkit only showed one of the two
> entries.  In this case, you probably need to upgrade gentoolkit and
> portage at the same time.
>
>>
>>
>> On 05/16/20 17:38, n952162 wrote:
>>>
>>> e.g.
>>>
>>> sudo emerge -av =*sys-apps/portage-2.3.89-r3
>>> <https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.89-r3.ebuild>*
>>>
>>>
>>> ?
>>>
>>> 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 system.
>>>
>>>   (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) pulled in by
>>>     app-portage/gentoolkit required by @selected
>>>
>>> On 05/16/20 16:19, Jack wrote:
>>>> 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 is that Gentoo needs to be updated more often
>>>> than yearly.  Others may also comment, but right now, I think a
>>>> reinstall might be easier than working through all the problems,
>>>> unless you are trying to learn more about how things work.
>>>>
>>>> My first question is why you have portage-9999 unmasked?  I suggest
>>>> going for the lowest version currently in the tree.  I'm not sure if
>>>> your first step should really be portage itself, or upgrading
>>>> packages where the installed version is now masked due to security
>>>> errors or being too out of date.
>>>>
>>>> Jack
>>>>
>>>>>
>>>>>
>>>>> On 05/14/20 23:36, Rich Freeman wrote:
>>>>>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>>>>>>> On 05/14/20 22:46, Rich Freeman wrote:
>>>>>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>>>>>>>> ...and?  Did you update portage as it was _highly_ recommended
>>>>>>>> that
>>>>>>>> you do so first?  What version of portage are you using? This
>>>>>>>> appears
>>>>>>>> on the top line of emerge --info.
>>>>>>>>
>>>>>>> $ emerge --info
>>>>>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0,
>>>>>>> gcc-7.3.0,
>>>>>>> glibc-2.26-r7, 4.14.65-gentoo x86_64)
>>>>>> That version of portage has been removed from the repo for over a
>>>>>> year.
>>>>>>
>>>>>> I would update your system so that is current and then try again.  I
>>>>>> believe that version of portage should still support EAPI 7 but
>>>>>> there
>>>>>> could be some other issue that is giving it problems with more
>>>>>> recent
>>>>>> packages in the tree.
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: [gentoo-user] no ebuilds for telegram

[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.g:
>
>     sudo emerge -av =sys-apps/portage-2.3.89-r3
> =app-portage/gemato-14.3  =dev-python/setuptools-44.1.0
> dev-python/certifi-2019.11.28
Maybe.  The issue is to first understand (for each slot conflict) what 
is pulling in each of the conflicting versions.  The newer version is 
probably being pulled in as the default (highest version not flagged or 
masked or ...).  The older version is likely being pulled in by an older 
version of some other package. Rather than specifying specific version, 
just include the other package also.

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. So starting with 
"emerge -1 portage" and seeing the older version of portage is being 
pulled in by gentookit, just "emerge -1 portage gentoolkit". You may 
have to go through many iterations to find a set of packages which will 
cleanly upgrade together.
>
>
> On 05/16/20 18:16, Jack wrote:
>> 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, installed) pulled in by
>>> sys-apps/portage[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] 
>>>
>>>    required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed)
>>>
>>> I'm trying to update from 2.3.49 to 2.3.89 and it tells me it has a 
>>> slot
>>> conflict there.  I can hardly delete portage and then add it ...
>> First, if you post a slot conflict, post the whole thing. (This one
>> is OK, but your previous one for gentoolkit only showed one of the two
>> entries.  In this case, you probably need to upgrade gentoolkit and
>> portage at the same time.
>>
>>>
>>>
>>> On 05/16/20 17:38, n952162 wrote:
>>>>
>>>> e.g.
>>>>
>>>> sudo emerge -av =*sys-apps/portage-2.3.89-r3
>>>> <https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.89-r3.ebuild>* 
>>>>
>>>>
>>>>
>>>> ?
>>>>
>>>> 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 system.
>>>>
>>>>   (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) pulled 
>>>> in by
>>>>     app-portage/gentoolkit required by @selected
>>>>
>>>> On 05/16/20 16:19, Jack wrote:
>>>>> 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 is that Gentoo needs to be updated more often
>>>>> than yearly.  Others may also comment, but right now, I think a
>>>>> reinstall might be easier than working through all the problems,
>>>>> unless you are trying to learn more about how things work.
>>>>>
>>>>> My first question is why you have portage-9999 unmasked? I suggest
>>>>> going for the lowest version currently in the tree.  I'm not sure if
>>>>> your first step should really be portage itself, or upgrading
>>>>> packages where the installed version is now masked due to security
>>>>> errors or being too out of date.
>>>>>
>>>>> Jack
>>>>>
>>>>>>
>>>>>>
>>>>>> On 05/14/20 23:36, Rich Freeman wrote:
>>>>>>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@web.de> wrote:
>>>>>>>> On 05/14/20 22:46, Rich Freeman wrote:
>>>>>>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@web.de> 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 portage' now.
>>>>>>>>> ...and?  Did you update portage as it was _highly_ recommended
>>>>>>>>> that
>>>>>>>>> you do so first?  What version of portage are you using? This
>>>>>>>>> appears
>>>>>>>>> on the top line of emerge --info.
>>>>>>>>>
>>>>>>>> $ emerge --info
>>>>>>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0,
>>>>>>>> gcc-7.3.0,
>>>>>>>> glibc-2.26-r7, 4.14.65-gentoo x86_64)
>>>>>>> That version of portage has been removed from the repo for over a
>>>>>>> year.
>>>>>>>
>>>>>>> I would update your system so that is current and then try 
>>>>>>> again.  I
>>>>>>> believe that version of portage should still support EAPI 7 but
>>>>>>> there
>>>>>>> could be some other issue that is giving it problems with more
>>>>>>> recent
>>>>>>> packages in the tree.
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>

Re: [gentoo-user] no ebuilds for telegram

[Rich Freeman]

On Sat, May 16, 2020 at 1:04 PM Jack <ostroffjh@users.sourceforge.net> 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 update everything:
emerge -auDv --changed-use --keep-going --with-bdeps=y --changed-deps
--backtrack=100 @world

It is quite possible that this will just be a complete mess since such
a long time has passed.

If so I would try to do just those conflicts necessary to get portage
updated to start.  Or maybe try the above command but using @system
instead of @world.

However, nobody should be under the impression that it is normal when
updating to have to routinely update packages one at a time manually
trying to work through conflicts.  As long as all the conflicting
packages are within the scope of an update command, portage should
generally be able to figure out how to handle this.

Often when it can't it is the result of heavy-handed user
configuration (USE=-* and so on).  I'm not saying that users can't do
that if they want, but right now portage doesn't have any concept of
soft use dependencies so anytime you stick something in a config file
portage will treat it as the gospel even if one small change to your
configuration will unblock a large logjam of conflicts.

In an ideal world there would be some kind of prioritization of these
configs so that you could have softer preferences and harder ones, and
portage would just make a best effort to respect soft preferences
without micromanagement.

-- 
Rich

Re: [gentoo-user] no ebuilds for telegram

[Dale]

[-- Attachment #1: Type: text/plain, Size: 3054 bytes --]

Rich Freeman wrote:
> On Sat, May 16, 2020 at 1:04 PM Jack <ostroffjh@users.sourceforge.net> 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 update everything:
> emerge -auDv --changed-use --keep-going --with-bdeps=y --changed-deps
> --backtrack=100 @world
>
> It is quite possible that this will just be a complete mess since such
> a long time has passed.
>
> If so I would try to do just those conflicts necessary to get portage
> updated to start.  Or maybe try the above command but using @system
> instead of @world.
>
> However, nobody should be under the impression that it is normal when
> updating to have to routinely update packages one at a time manually
> trying to work through conflicts.  As long as all the conflicting
> packages are within the scope of an update command, portage should
> generally be able to figure out how to handle this.
>
> Often when it can't it is the result of heavy-handed user
> configuration (USE=-* and so on).  I'm not saying that users can't do
> that if they want, but right now portage doesn't have any concept of
> soft use dependencies so anytime you stick something in a config file
> portage will treat it as the gospel even if one small change to your
> configuration will unblock a large logjam of conflicts.
>
> In an ideal world there would be some kind of prioritization of these
> configs so that you could have softer preferences and harder ones, and
> portage would just make a best effort to respect soft preferences
> without micromanagement.
>


I agree. I'd try to update world as well.  I've had occasion in the past
where doing a emerge -uaDN system would fail with conflicts but emerge
-uaDN world would work, just with a really long list of packages to
update.  It's worth a shot. If nothing else, the error would provide
more info.

To the OP.  Gentoo really needs to be synced and updated at least every
few months.  I do mine once a week.  Some update daily.  The downside of
updating only after long periods of time, running into multiple problem
updates that depend on each other.  It's bad enough with just one of
those to deal with but when you are hit with two, three or more, it
becomes easier to reinstall with a fresh tarball and go from there. 
Updating is doable but it can be very frustrating and result in a loss
of hair.  O_o

Didn't gentoolkit and portage have a circular deps problem several
months back?  I seem to recall it being tricky to get past but it has
been a while back.  This is another problem with updating after long
periods of time.  Old folks with foggy memory can't remember how they
worked around a problem.  If they didn't make notes, most of us forget
to do that, then we don't remember how we got around it to share the
solution, which often requires a decoder ring and a off the charts IQ. 
lol 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 3708 bytes --]