On 06/10/19 22:42, Rich Freeman wrote:
On Mon, Jun 10, 2019 at 5:39 PM n952162<n952...@web.de> wrote:
On 06/06/19 06:00,n952...@web.de wrote:
In trying to update portage (before I update my system), I have this:
!!! All ebuilds that could satisfy
">=dev-python/setuptools-34[python_targets_pypy(-)?,pn_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-pyth-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]"
have been mas
!!! One of the following masked packages is required to complete your request:
- dev-python/setuptools-9999::gentoo (masked by: EAPI 7)
- dev-python/setuptools-41.0.1::gentoo (masked by: EAPI 7)
- dev-python/setuptools-41.0.0::gentoo (masked by: EAPI 7)
- dev-python/setuptools-40.9.0::gentoo (masked by: EAPI 7)
- dev-python/setuptools-40.8.0::gentoo (masked by: EAPI 7)
- dev-python/setuptools-40.7.3::gentoo (masked by: EAPI 7)
- dev-python/setuptools-40.6.3::gentoo (masked by: backtracking: slot conflict)
- dev-python/setuptools-36.7.2::gentoo (masked by: backtracking: slot conflict)
Looking athttps://packages.gentoo.org/packages/dev-python/setuptools shows
that the only two versions stable for am64 are 40.6.3 and 36.7.2.
What is backtracking and how can I have a slot conflict if it's the developers
who determine what version sits in a slot?
Backtracking refers to how the dependency resolver works - it couldn't
figure out a way to satisfy your requirements. You have a slot
conflict because two different packages that you asked for require two
different versions of setuptools to be installed at the same time in
the same slot, or at least that is what portage interprets what it is
finding.
The verbose output (attached) says that the package with /"new SLOT
installation (side-by-side versions)" /is:
dev-lang/python-3.6.5:3.6/3.6m
The version in /var/db/pkg/dev-lang/python-* is:
/var/db/pkg/dev-lang/python-3.5.4-r1/python-3.5.4-r1.ebuild:SLOT="3.5/3.5m"
That doesn't look like the same slot...
How can there be a slot collision? If the developers say, slot 3 is for
a particular version, why should anybody want to push anything else into
slot 3?
I'd need to see more of the output to get a sense of what is
actually going on - posting 10 lines out of what was probably 1000+
lines of output honestly doesn't help anybody to assist you. Yes, the
whole output is tedious but probably contains clues.
Gladly! I've attached the output of this command:
sudo emerge --verbose y --verbose-conflicts
--verbose-slot-rebuilds --oneshot portage 2>&1 | tee
emerge-portage-2.txt
I presume that the flags in front of the dependency list are those given
in the --pretend option of emerge(1) ...
One might say, I have a package already dependent on setuptools and it's not
the right one, but how can it be that two different versions want to go into
the same slot?
There are many ways this can happen. Maybe package A wants setuptools
40.7.3 or greater, and package B wants setuptools 40.6.3 or lesser,
and you asked for both.
But isn't that exactly what slots are supposed to address? How can
there be a conflict? A limited number of slots?
Often though it is an issue with not
backtracking enough - if you're doing a huge update often you need to
add --backtrack=100 or rarely even a larger value in order for portage
to find a way to meet the requirements.
Can I follow the backtracking in this attached output somehow, to see
what how backtracking works?
Sometimes you need to include
--with-bdeps=y because something portage isn't considering in-scope is
pulling in something that conflicts, and it could be resolved by
letting portage update more packages.
Backtracking is something to do with dependency checking. I haven't seen any
explanation of what goes on in dependency checking and why backtracking is
necessary. Can someone point to an explanation?
Basically your config files, like the world file, and the profile
system set, contain a list of stuff you want. Portage wants to give
you want you want. Maybe these files specify 200 packages you're
interested in directly. Each of these might ask for 5 more, and each
of those 5 more, and so on. Portage works backwards through the
dependency tree to generate a list of every requirement of every
package. These can form circular loops, and the tree can get quite
large very quickly. As an optimization I believe portage avoids
traversing the entire thing and only goes back so far - usually it can
find a solution to your requirements without traversing the entire
tree.
I'm trying to understand that ...
A -> +
|
+ -> B ->+
| |
| + -> C[0]
| + -> D
|
+ -> C[1]
Okay, so backtracking is ... when I'm at C[1] and see there's already a C[0] ...
Then I go back to B to see if it might be happy with C[1]?
!!! Your current profile is deprecated and not supported anymore.
!!! Use eselect profile to update your profile.
!!! Please upgrade to the following profile if possible:
default/linux/amd64/17.0/desktop
You may use the following command to upgrade:
eselect profile set default/linux/amd64/17.0/desktop
These are the packages that would be merged, in order:
Calculating dependencies ..... . . ... done!
[ebuild N ] app-crypt/openpgp-keys-gentoo-release-20190427::gentoo
USE="{-test}" 59 KiB
[ebuild N ] dev-python/bz2file-0.98::gentoo PYTHON_TARGETS="python2_7
(-pypy)" 12 KiB
[ebuild U ] dev-libs/libgpg-error-1.29::gentoo [1.27-r1::gentoo] USE="nls
static-libs -common-lisp" ABI_X86="(64) -32 (-x32)" 874 KiB
[ebuild NS ] dev-lang/python-3.6.5:3.6/3.6m::gentoo [2.7.14-r1:2.7::gentoo,
3.5.4-r1:3.5/3.5m::gentoo] USE="gdbm ipv6 ncurses readline ssl (threads) xml
-build -examples -hardened -libressl -sqlite {-test} -tk -wininst" 16663 KiB
[ebuild U ] dev-python/setuptools-40.6.3::gentoo [36.7.2::gentoo]
USE="{-test}" PYTHON_TARGETS="python2_7 python3_6* (-pypy) (-pypy3) -python3_5*
(-python3_7) (-python3_4%)" 820 KiB
[ebuild U ] dev-python/certifi-2018.4.16::gentoo [2017.4.17::gentoo]
PYTHON_TARGETS="python2_7 python3_6* (-pypy) (-pypy3) -python3_5* (-python3_7)
(-python3_4%)" 147 KiB
[ebuild U ] app-crypt/gnupg-2.2.10::gentoo [2.2.4::gentoo] USE="bzip2 ldap
nls readline smartcard ssl%* usb -doc (-selinux) -tofu -tools -wks-server
(-gnutls%*)" 6504 KiB
[ebuild N ] app-portage/gemato-14.1::gentoo USE="blake2 bzip2 gpg -lzma
-sha3 {-test} -tools" PYTHON_TARGETS="python2_7 python3_6 (-pypy) -python3_5
(-python3_7)" 70 KiB
[ebuild U ~] sys-apps/portage-2.3.67::gentoo [2.3.13-r1::gentoo] USE="(ipc)
native-extensions rsync-verify%* xattr -build -doc -epydoc -gentoo-dev%
(-selinux)" PYTHON_TARGETS="python2_7 python3_6* -pypy -python3_5* -python3_7%
(-python3_4%)" 1002 KiB
Total: 9 packages (5 upgrades, 3 new, 1 in new slot), Size of downloads: 26147
KiB
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
sys-apps/portage:0
(sys-apps/portage-2.3.67:0/0::gentoo, ebuild scheduled for merge) pulled in by
sys-apps/portage (Argument)
(sys-apps/portage-2.3.13-r1:0/0::gentoo, installed) pulled in by
sys-apps/portage[python_targets_python2_7(-),python_targets_python3_5(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]
required by (app-portage/gentoolkit-0.4.0:0/0::gentoo, installed)
dev-python/setuptools:0
(dev-python/setuptools-40.6.3:0/0::gentoo, ebuild scheduled for merge) pulled
in by
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-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, ebuild scheduled for
merge)
>=dev-python/setuptools-34[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]
required by (app-portage/gemato-14.1:0/0::gentoo, ebuild scheduled for merge)
dev-python/setuptools[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]
required by (app-portage/gemato-14.1:0/0::gentoo, ebuild scheduled for merge)
(dev-python/setuptools-36.7.2:0/0::gentoo, installed) pulled in by
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_5(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]
required by (dev-python/pyxattr-0.5.5:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_5(-),-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/certifi-2017.4.17:0/0::gentoo, installed)
dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-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/certifi:0
(dev-python/certifi-2018.4.16:0/0::gentoo, ebuild scheduled for merge) pulled
in by
>=dev-python/certifi-2016.9.26[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]
required by (dev-python/setuptools-40.6.3:0/0::gentoo, ebuild scheduled for
merge)
(dev-python/certifi-2017.4.17:0/0::gentoo, installed) pulled in by
>=dev-python/certifi-2016.9.26[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]
required by (dev-python/setuptools-36.7.2:0/0::gentoo, installed)
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.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by sys-devel/crossdev-20171230::gentoo
# required by @selected
# required by @world (argument)
=sys-apps/portage-2.3.67 ~amd64
Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.
* In order to avoid wasting time, backtracking has terminated early
* due to the above autounmask change(s). The --autounmask-backtrack=y
* option can be used to force further backtracking, but there is no
* guarantee that it will produce a solution.
!!! The following installed packages are masked:
- virtual/perl-Carp-1.400.0-r1::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Andreas K. Hüttel <dilfri...@gentoo.org> (11 May 2019)
# Perl 5.24 will be removed soon. Please upgrade.
- mail-client/thunderbird-52.5.2::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Ian Stakenvicius <a...@gentoo.org> (07 Nov 2018)
# on behalf of Mozilla Project <mozi...@gentoo.org>
# Mask old/vuln thunderbird for removal by 2019,
# see security bug 670102
- www-client/firefox-52.5.2::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Thomas Deutschmann <whi...@gentoo.org> (12 Oct 2018)
# EOL and has known vulnerabilities. Please move to
# Firefox 60 or newer if you can.
- sys-kernel/gentoo-sources-4.9.76-r1::gentoo (masked by: linux-firmware
license(s))
A copy of the 'linux-firmware' license is located at
'/usr/portage/licenses/linux-firmware'.
- virtual/perl-CPAN-Meta-2.150.5-r1::gentoo (masked by: package.mask)
- virtual/perl-Scalar-List-Utils-1.420.200_rc-r1::gentoo (masked by:
package.mask)
- virtual/perl-Getopt-Long-2.480.0-r1::gentoo (masked by: package.mask)
- sys-libs/binutils-libs-2.29.1-r1::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Michał Górny <mgo...@gentoo.org>, Andreas K. Hüttel <dilfri...@gentoo.org>,
# Matthias Maier <tam...@gentoo.org> (21 May 2017 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-ttf-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'.
- virtual/perl-Perl-OSType-1.9.0-r1::gentoo (masked by: package.mask)
- media-fonts/font-bh-type1-1.0.3-r1::gentoo (masked by: bh-luxi license(s))
- virtual/perl-Compress-Raw-Bzip2-2.69.0-r1::gentoo (masked by: package.mask)
- virtual/perl-Module-Metadata-1.0.31-r1::gentoo (masked by: package.mask)
- net-libs/libnsl-0::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Andreas K. Hüttel <dilfri...@gentoo.org> (11 Sep 2018)
# Mask transition ebuilds that were needed only for <glibc-2.26
# We will keep them in the tree as long as we have masked
# <glibc-2.26.
- virtual/perl-version-0.991.600-r1::gentoo (masked by: package.mask)
- virtual/perl-Data-Dumper-2.160.0-r1::gentoo (masked by: package.mask)
- virtual/perl-Compress-Raw-Zlib-2.69.0-r1::gentoo (masked by: package.mask)
- virtual/perl-ExtUtils-ParseXS-3.310.0-r1::gentoo (masked by: package.mask)
- dev-lang/perl-5.24.3::gentoo (masked by: package.mask)
- sys-libs/glibc-2.25-r9::gentoo (masked by: package.mask)
- virtual/perl-parent-0.234.0-r1::gentoo (masked by: package.mask)
- media-fonts/corefonts-1-r7::gentoo (masked by: MSttfEULA license(s))
A copy of the 'MSttfEULA' license is located at
'/usr/portage/licenses/MSttfEULA'.
- sys-devel/binutils-2.29.1-r1::gentoo (masked by: package.mask)
- virtual/perl-Digest-MD5-2.540.0-r3::gentoo (masked by: package.mask)
- sys-kernel/linux-firmware-20180103-r1::gentoo (masked by: linux-firmware
no-source-code freedist license(s))
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'.
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
