mauricev

I didn't get those warnings because when I built the digest I gave it the full path and when I attempted to emerge autossh, I just told it emerge -v autossh. I never referenced "cat" itself.

Ah, the word cat was not meant to be taken literally, but it refers to the category of the package, which, in this case, is net-misc. That fixed it. And, no, there were no warnings from emerge. Thanks!

/var/git/overlay └── local-overlay ├── COPYRIGHT.txt ├── LICENSE.txt ├── README.rst ├── cat │ └── autossh │ ├── Manifest │ ├── autossh-1.4f.ebuild │ └── metadata.xml ├── metadata │ └── layout.conf └── profiles └── repo_name

sudo: tree: command not found

That was a mistake, not the mistake. It still doesn't work.

Yes, I did that. But one thing that wasn't not stated in the docs is that path where the packages must reside. I would have never guessed it.

I want to use the latest version of autossh, which isn't yet in the portage tree. I followed the instructions at https://www.funtoo.org/Local_Overlay, but what are the next steps? Do I recreate the kits directory hierarchy in /var/git/overlay/local-overlay. ( I tried that and it had no effect.) My updated autossh ebuild is not being seen.

4.15.17-1 https://pastebin.com/zK629ztL

On a system I built with KDE-plasma, I notice that login to the KDE console (using SDDM) may take up to more than a minute to login. I also noticed once that parts of the GUI (the "start" menu) became nonresponsive for about 30 seconds. I am noticing this in the log [console-kit-daemon] CRITICAL: polkit_authority_check_authorization: assertion 'POLKIT_IS_AUTHORITY (authority)' failed_ This seems like a hint.

I put RUBY_TARGETS="ruby23 ruby24" in make.conf and now everything is emerging. If I comment the line, I get this emerge: there are no ebuilds built with USE flags to satisfy "virtual/rubygems[ruby_targets_ruby22]". !!! One of the following packages is required to complete your request: - virtual/rubygems-13::ruby-kit (Missing IUSE: ruby_targets_ruby22) - virtual/rubygems-12::ruby-kit (Missing IUSE: ruby_targets_ruby22) - virtual/rubygems-11::ruby-kit (Missing IUSE: ruby_targets_ruby22) (dependency required by "dev-ruby/minitest-5.10.3::ruby-kit[-test,ruby_targets_ruby22]" [ebuild]) (dependency required by "dev-lang/ruby-2.4.3::ruby-kit" [installed]) (dependency required by "dev-ruby/test-unit-3.2.6::ruby-kit[ruby_targets_ruby24]" [ebuild]) (dependency required by "dev-lang/ruby-2.3.6::ruby-kit" [installed]) (dependency required by "dev-ruby/net-telnet-0.1.1-r1::ruby-kit[ruby_targets_ruby23]" [ebuild])

https://pastebin.com/D8knQCXg

https://pastebin.com/4JGNYdbx

When trying to emerge, I get the following WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: virtual/rubygems:0 virtual/rubygems-13:0/0::ruby-kit, ebuild scheduled for merge conflicts with virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/net-telnet-0.1.1-r1:1/1::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/json-2.1.0:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/rake-12.1.0:0/0::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/net-telnet-0.1.1-r1:1/1::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/json-2.1.0:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/rake-12.1.0:0/0::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/minitest-5.10.3:5/5::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-lang/ruby-2.2.9:2.2/2.2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/power_assert-1.1.0:0/0::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/test-unit-3.2.6:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/test-unit-3.2.6:2/2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-lang/ruby-2.2.9:2.2/2.2::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ virtual/rubygems[ruby_targets_ruby22] required by dev-ruby/minitest-5.10.3:5/5::ruby-kit, ebuild scheduled for merge ^^^^^^^^^^^^^^^^^^^ =virtual/rubygems-13[ruby_targets_ruby22] required by dev-ruby/power_assert-1.1.0:0/0::ruby-kit, ebuild scheduled for merge

I set -rdoc in USE and that seems to have worked around it.

In trying to emerge kde-plasma, I am getting this Oops! Conflicts have been encountered: >>> dev-lang/ruby-2.4.3:2.4/2.4::ruby-kit, ebuild scheduled for merge, wants >=dev-ruby/rdoc-5.1.0[ruby_targets_ruby24] >>> dev-lang/ruby-2.2.9:2.2/2.2::ruby-kit, ebuild scheduled for merge, wants >=dev-ruby/rdoc-4.0.1[ruby_targets_ruby22] My candidates are: >>> dev-ruby/rdoc-5.1.0:0/0::ruby-kit, ebuild scheduled for merge has SLOT 0/0 but not IUSE ruby_targets_ruby22 >>> dev-ruby/rdoc-4.3.0:0/0::ruby-kit, ebuild scheduled for merge has SLOT 0/0 and IUSE ruby_targets_ruby22