Re: Aw: Re: Re: [gentoo-user] Updating portage, continued

2019-06-12 Thread n952162

On 06/10/19 22:42, Rich Freeman wrote:


On Mon, Jun 10, 2019 at 5:39 PM n952162  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-::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 

Re: [gentoo-user] Emerge wants to downgrade icu

2019-06-12 Thread netfab
Le 12/06/19 à 11:54, Alarig Le Lay a tapoté :
> Hi,
> 
> Since some days emerge asks me to go back to ICU from profile 13.0,
> but I don’t understand why.
> 


Try --autounmask-backtrack=y emerge option.



Re: [gentoo-user] Emerge wants to downgrade icu

2019-06-12 Thread Mickaël Bucas
Le mer. 12 juin 2019 à 11:54, Alarig Le Lay  a écrit :
>
> Hi,
>
> Since some days emerge asks me to go back to ICU from profile 13.0, but
> I don’t understand why.
>
> ~ # emerge --ask --verbose --update --deep --newuse @world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  r  UD#] dev-libs/icu-58.2-r1:0/58.2::gentoo [63.1-r1:0/63.1::gentoo] 
> USE="-debug -doc -examples -static-libs" ABI_X86="32 (64) (-x32)" 22,823 KiB
> [ebuild  rR] dev-util/mdds-1.3.1:1/1.2::gentoo  USE="-valgrind" 0 KiB
> [ebuild   R] media-libs/gd-2.2.5-r2:2/3::gentoo  USE="jpeg png tiff 
> truetype zlib -fontconfig* -static-libs -test -webp -xpm" ABI_X86="32 (64) 
> (-x32)" CPU_FLAGS_X86="sse" 0 KiB
> [ebuild  rR] dev-libs/libixion-0.13.0:0/0.13::gentoo  USE="threads -debug 
> -python -static-libs" PYTHON_SINGLE_TARGET="python3_6 -python3_5" 
> PYTHON_TARGETS="python3_6 -python3_5" 0 KiB
> [ebuild  rR] media-libs/libcdr-0.1.5::gentoo  USE="-doc -static-libs 
> -test" 0 KiB
> [ebuild  rR] dev-tex/bibtexu-3.71_p20170524::gentoo  USE="-doc -source" 0 
> KiB
> [ebuild  rR] app-text/libmspub-0.1.4::gentoo  USE="-doc -static-libs" 0 
> KiB
> [ebuild  rR] app-text/libqxp-0.0.2::gentoo  USE="-debug -doc -test 
> -tools" 0 KiB
> [ebuild  rR] media-libs/libzmf-0.0.2::gentoo  USE="-debug -doc -test 
> -tools" 0 KiB
> [ebuild  rR] dev-lang/spidermonkey-52.9.1_pre1:52::gentoo  
> USE="system-icu -custom-cflags -custom-optimization -debug -minimal -test" 0 
> KiB
> [ebuild  rR] media-libs/libvisio-0.1.6::gentoo  USE="-doc -static-libs 
> -test -tools" 0 KiB
> [ebuild  rR] app-text/libebook-0.1.2-r1::gentoo  USE="-doc -test -tools" 
> 0 KiB
> [ebuild  rR] media-libs/raptor-2.0.15-r2:2::gentoo  USE="curl unicode 
> -debug -json -static-libs" 0 KiB
> [ebuild  rR] dev-libs/libical-3.0.4:0/3::gentoo  USE="berkdb -doc 
> -examples -static-libs -test" 0 KiB
> [ebuild  rR] dev-qt/qtcore-5.12.3:5/5.12::gentoo  USE="icu -debug 
> -systemd -test" 0 KiB
> [ebuild  rR] app-text/libetonyek-0.1.9::gentoo  USE="-doc -static-libs 
> -test" 0 KiB
> [ebuild  rR] media-libs/harfbuzz-2.3.1:0/0.9.18::gentoo  USE="cairo glib 
> graphite icu introspection truetype -debug -static-libs -test" ABI_X86="32 
> (64) (-x32)" 0 KiB
> [ebuild  rR] app-text/texlive-core-2017-r4::gentoo  USE="X luajittex 
> xetex -cjk -doc -source -tk" 0 KiB
> [ebuild  rR] app-office/libreoffice-bin-6.1.5.2::gentoo  USE="-gnome 
> -java -kde" PYTHON_TARGETS="python3_6" 0 KiB
>
> Total: 19 packages (1 downgrade, 18 reinstalls), Size of downloads: 22,823 KiB
>
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> dev-libs/icu:0
>
>   (dev-libs/icu-58.2-r1:0/58.2::gentoo, ebuild scheduled for merge) pulled in 
> by
> (no parents that aren't satisfied by other packages in this slot)
>
>   (dev-libs/icu-63.1-r1:0/63.1::gentoo, installed) pulled in by
> dev-libs/icu:0/63.1 required by 
> (app-office/libreoffice-bin-6.1.5.2:0/0::gentoo, ebuild scheduled for merge)
> ^^^
>
>
> 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 packages are causing rebuilds:
>
>   (dev-libs/icu-58.2-r1:0/58.2::gentoo, ebuild scheduled for merge) causes 
> rebuilds for:
> (dev-qt/qtcore-5.12.3:5/5.12::gentoo, ebuild scheduled for merge)
> (media-libs/libvisio-0.1.6:0/0::gentoo, ebuild scheduled for merge)
> (media-libs/libcdr-0.1.5:0/0::gentoo, ebuild scheduled for merge)
> (app-text/libebook-0.1.2-r1:0/0::gentoo, ebuild scheduled for merge)
> (app-text/libmspub-0.1.4:0/0::gentoo, ebuild scheduled for merge)
> (app-text/texlive-core-2017-r4:0/0::gentoo, ebuild scheduled for merge)
> (media-libs/libzmf-0.0.2:0/0::gentoo, ebuild scheduled for merge)
> (app-office/libreoffice-bin-6.1.5.2:0/0::gentoo, ebuild scheduled for 
> merge)
> (dev-libs/libical-3.0.4:0/3::gentoo, ebuild scheduled for merge)
> (dev-lang/spidermonkey-52.9.1_pre1:52/52::gentoo, ebuild scheduled for 
> merge)
> (media-libs/harfbuzz-2.3.1:0/0.9.18::gentoo, ebuild scheduled for merge)
> (dev-tex/bibtexu-3.71_p20170524:0/0::gentoo, ebuild scheduled for merge)
> (app-text/libqxp-0.0.2:0/0::gentoo, ebuild scheduled for merge)
> (media-libs/raptor-2.0.15-r2:2/2::gentoo, ebuild scheduled for merge)
>
> The following mask changes are necessary to proceed:
>  (see "package.unmask" in the portage(5) man page for 

[gentoo-user] Emerge wants to downgrade icu

2019-06-12 Thread Alarig Le Lay
Hi,

Since some days emerge asks me to go back to ICU from profile 13.0, but
I don’t understand why.

~ # emerge --ask --verbose --update --deep --newuse @world

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

Calculating dependencies... done!
[ebuild  r  UD#] dev-libs/icu-58.2-r1:0/58.2::gentoo [63.1-r1:0/63.1::gentoo] 
USE="-debug -doc -examples -static-libs" ABI_X86="32 (64) (-x32)" 22,823 KiB
[ebuild  rR] dev-util/mdds-1.3.1:1/1.2::gentoo  USE="-valgrind" 0 KiB
[ebuild   R] media-libs/gd-2.2.5-r2:2/3::gentoo  USE="jpeg png tiff 
truetype zlib -fontconfig* -static-libs -test -webp -xpm" ABI_X86="32 (64) 
(-x32)" CPU_FLAGS_X86="sse" 0 KiB
[ebuild  rR] dev-libs/libixion-0.13.0:0/0.13::gentoo  USE="threads -debug 
-python -static-libs" PYTHON_SINGLE_TARGET="python3_6 -python3_5" 
PYTHON_TARGETS="python3_6 -python3_5" 0 KiB
[ebuild  rR] media-libs/libcdr-0.1.5::gentoo  USE="-doc -static-libs -test" 
0 KiB
[ebuild  rR] dev-tex/bibtexu-3.71_p20170524::gentoo  USE="-doc -source" 0 
KiB
[ebuild  rR] app-text/libmspub-0.1.4::gentoo  USE="-doc -static-libs" 0 KiB
[ebuild  rR] app-text/libqxp-0.0.2::gentoo  USE="-debug -doc -test -tools" 
0 KiB
[ebuild  rR] media-libs/libzmf-0.0.2::gentoo  USE="-debug -doc -test 
-tools" 0 KiB
[ebuild  rR] dev-lang/spidermonkey-52.9.1_pre1:52::gentoo  USE="system-icu 
-custom-cflags -custom-optimization -debug -minimal -test" 0 KiB
[ebuild  rR] media-libs/libvisio-0.1.6::gentoo  USE="-doc -static-libs 
-test -tools" 0 KiB
[ebuild  rR] app-text/libebook-0.1.2-r1::gentoo  USE="-doc -test -tools" 0 
KiB
[ebuild  rR] media-libs/raptor-2.0.15-r2:2::gentoo  USE="curl unicode 
-debug -json -static-libs" 0 KiB
[ebuild  rR] dev-libs/libical-3.0.4:0/3::gentoo  USE="berkdb -doc -examples 
-static-libs -test" 0 KiB
[ebuild  rR] dev-qt/qtcore-5.12.3:5/5.12::gentoo  USE="icu -debug -systemd 
-test" 0 KiB
[ebuild  rR] app-text/libetonyek-0.1.9::gentoo  USE="-doc -static-libs 
-test" 0 KiB
[ebuild  rR] media-libs/harfbuzz-2.3.1:0/0.9.18::gentoo  USE="cairo glib 
graphite icu introspection truetype -debug -static-libs -test" ABI_X86="32 (64) 
(-x32)" 0 KiB
[ebuild  rR] app-text/texlive-core-2017-r4::gentoo  USE="X luajittex xetex 
-cjk -doc -source -tk" 0 KiB
[ebuild  rR] app-office/libreoffice-bin-6.1.5.2::gentoo  USE="-gnome -java 
-kde" PYTHON_TARGETS="python3_6" 0 KiB

Total: 19 packages (1 downgrade, 18 reinstalls), Size of downloads: 22,823 KiB

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

dev-libs/icu:0

  (dev-libs/icu-58.2-r1:0/58.2::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)

  (dev-libs/icu-63.1-r1:0/63.1::gentoo, installed) pulled in by
dev-libs/icu:0/63.1 required by 
(app-office/libreoffice-bin-6.1.5.2:0/0::gentoo, ebuild scheduled for merge)
^^^


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 packages are causing rebuilds:

  (dev-libs/icu-58.2-r1:0/58.2::gentoo, ebuild scheduled for merge) causes 
rebuilds for:
(dev-qt/qtcore-5.12.3:5/5.12::gentoo, ebuild scheduled for merge)
(media-libs/libvisio-0.1.6:0/0::gentoo, ebuild scheduled for merge)
(media-libs/libcdr-0.1.5:0/0::gentoo, ebuild scheduled for merge)
(app-text/libebook-0.1.2-r1:0/0::gentoo, ebuild scheduled for merge)
(app-text/libmspub-0.1.4:0/0::gentoo, ebuild scheduled for merge)
(app-text/texlive-core-2017-r4:0/0::gentoo, ebuild scheduled for merge)
(media-libs/libzmf-0.0.2:0/0::gentoo, ebuild scheduled for merge)
(app-office/libreoffice-bin-6.1.5.2:0/0::gentoo, ebuild scheduled for merge)
(dev-libs/libical-3.0.4:0/3::gentoo, ebuild scheduled for merge)
(dev-lang/spidermonkey-52.9.1_pre1:52/52::gentoo, ebuild scheduled for 
merge)
(media-libs/harfbuzz-2.3.1:0/0.9.18::gentoo, ebuild scheduled for merge)
(dev-tex/bibtexu-3.71_p20170524:0/0::gentoo, ebuild scheduled for merge)
(app-text/libqxp-0.0.2:0/0::gentoo, ebuild scheduled for merge)
(media-libs/raptor-2.0.15-r2:2/2::gentoo, ebuild scheduled for merge)

The following mask changes are necessary to proceed:
 (see "package.unmask" in the portage(5) man page for more details)
# required by @__auto_slot_operator_replace_installed__ (argument)
# /usr/portage/profiles/base/package.mask:
# Andreas Sturmlechner  (15 Jul 2018)
# Old ICU is unsupported. ICU 58 only remains for 13.0 based profiles.