Re: [gentoo-user] Recent change in python - some packages are not happy
On Sunday, 24 June 2018 10:35:37 BST Marc Joliet wrote:
> Am Sonntag, 24. Juni 2018, 11:10:48 CEST schrieb Mick:
> [snip]
>
> > Is the default python target determined by the profile and does this
> > override choices through eselect?
> >
> > Should 'eselect python update' set 3.6 as the default when emerge seems to
> > be determined to use 3.5?
> >
> > # eselect python list
> >
> > Available Python interpreters, in order of preference:
> > [1] python3.6
> > [2] python3.5
> > [3] python3.4 (uninstalled)
> > [4] python2.7 (fallback)
> >
> > While from emerge --info I get:
> >
> > PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5"
>
> The two are orthogonal: one determines for which versions of Python a
> package is installed, the other manages the python{,2,3} symlinks.
>
> > I don't fancy rebuilding libreoffice + 67 more packages on 3 PCs just for
> > grins.
>
> See bug #656406. If you don't care for going back (like me), you can do the
> following (make.conf isn't enough because apparently that overrides, e.g.,
> asciidoc being forced to PYTHON_SINGLE_TARGET="python2_7"):
>
> % cat /etc/portage/profile/make.defaults
> PYTHON_TARGETS="python2_7 -python3_5 python3_6"
> PYTHON_SINGLE_TARGET="-python3_5 python3_6"
Thank you Mark, I guessed the version update had been reversed, but hadn't
seen the bug.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Recent change in python - some packages are not happy
Am Sonntag, 24. Juni 2018, 11:10:48 CEST schrieb Mick:
[snip]
> Is the default python target determined by the profile and does this
> override choices through eselect?
>
> Should 'eselect python update' set 3.6 as the default when emerge seems to
> be determined to use 3.5?
>
> # eselect python list
> Available Python interpreters, in order of preference:
> [1] python3.6
> [2] python3.5
> [3] python3.4 (uninstalled)
> [4] python2.7 (fallback)
>
>
> While from emerge --info I get:
>
> PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5"
The two are orthogonal: one determines for which versions of Python a package
is installed, the other manages the python{,2,3} symlinks.
> I don't fancy rebuilding libreoffice + 67 more packages on 3 PCs just for
> grins.
See bug #656406. If you don't care for going back (like me), you can do the
following (make.conf isn't enough because apparently that overrides, e.g.,
asciidoc being forced to PYTHON_SINGLE_TARGET="python2_7"):
% cat /etc/portage/profile/make.defaults
PYTHON_TARGETS="python2_7 -python3_5 python3_6"
PYTHON_SINGLE_TARGET="-python3_5 python3_6"
HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Recent change in python - some packages are not happy
On Saturday, 23 June 2018 12:35:32 BST you wrote: > On Saturday, 23 June 2018 11:09:10 BST Alec Ten Harmsel wrote: > > On Sat, Jun 23, 2018 at 10:38:35AM +0100, Mick wrote: > > > On Saturday, 23 June 2018 10:30:09 BST Neil Bothwick wrote: > > > > On 23 June 2018 10:14:31 BST, Mick wrote: > > > > >I came up to this today following a portage sync: > > > > > > > > > ># emerge -uaNDv world > > > > > > > > > > > > > > >These are the packages that would be merged, in order: > > > > > > > > > >Calculating dependencies / > > > > > > > > > >!!! Problem resolving dependencies for sys-devel/gdb from @selected > > > > >.. done! > > > > > > > > > > > > > > >!!! The ebuild selected to satisfy "sys-devel/gdb" has unmet > > > > >requirements. > > > > >- sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml > > > > >-lzma > > > > >- > > > > >multitarget -test -vanilla" ABI_X86="(64)" > > > > >PYTHON_SINGLE_TARGET="-python2_7 - > > > > >python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 > > > > >-python3_5" > > > > > > > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > > > >python? ( exactly-one-of ( python_single_target_python2_7 > > > > > > > > > >python_single_target_python3_4 python_single_target_python3_5 ) ) > > > > > > > > > > ... > > > > > > > > Start with "grep - ir python /etc/portage". That found the source of > > > > the > > > > problem on one of my systems, I was setting PYTHON_SINGLE_TARGET for > > > > one > > > > package. > > > > > > Thanks Neil, I already had a look just in case I had set something up > > > and > > > forgot about it. This is all it showed: > > > > > > # grep -ir python /etc/portage > > > /etc/portage/package.use/package.use:=media-libs/lcms-1.19-r1 python > > > > How about `emerge --info | grep PYTHON_SINGLE_TARGET'? The problem looks > > > > to be: > > > PYTHON_SINGLE_TARGET="-python2_7 -python3_4 -python3_5" > > > > At least one PYTHON_SINGLE_TARGET needs to be set. I'd guess that > > PYTHON_SINGLE_TARGET got updated to 3.6, leaving GDB in its dust. > > > > Alec > > Thanks Alec, yes python-3.6 was moved to the stable tree. This is what I > have: > > PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" Errm ... no I don't! This morning after an update the targets have moved back to ... python3_5, despite having set up with eselect python3_6. Is the default python target determined by the profile and does this override choices through eselect? Should 'eselect python update' set 3.6 as the default when emerge seems to be determined to use 3.5? # eselect python list Available Python interpreters, in order of preference: [1] python3.6 [2] python3.5 [3] python3.4 (uninstalled) [4] python2.7 (fallback) While from emerge --info I get: PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" I don't fancy rebuilding libreoffice + 67 more packages on 3 PCs just for grins. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Recent change in python - some packages are not happy
On Sat, Jun 23, 2018 at 12:35:32PM +0100, Mick wrote:
> On Saturday, 23 June 2018 11:09:10 BST Alec Ten Harmsel wrote:
> >
> > How about `emerge --info | grep PYTHON_SINGLE_TARGET'? The problem looks
> >
> > to be:
> > > PYTHON_SINGLE_TARGET="-python2_7 -python3_4 -python3_5"
> >
> > At least one PYTHON_SINGLE_TARGET needs to be set. I'd guess that
> > PYTHON_SINGLE_TARGET got updated to 3.6, leaving GDB in its dust.
> >
> > Alec
>
> Thanks Alec, yes python-3.6 was moved to the stable tree. This is what I
> have:
>
> PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6"
>
> --
> Regards,
> Mick
I see this at the top of gdb-7.12.1.build:
PYTHON_COMPAT=( python{2_7,3_4,3_5} )
For the mean time, you can either accept the breakage, set
PYTHON_SINGLE_TARGET="python3_5" in /etc/portage/make.conf for now, or run an
unstable gdb.
Alec
Re: [gentoo-user] Recent change in python - some packages are not happy
On Saturday, 23 June 2018 11:09:10 BST Alec Ten Harmsel wrote: > On Sat, Jun 23, 2018 at 10:38:35AM +0100, Mick wrote: > > On Saturday, 23 June 2018 10:30:09 BST Neil Bothwick wrote: > > > On 23 June 2018 10:14:31 BST, Mick wrote: > > > >I came up to this today following a portage sync: > > > > > > > ># emerge -uaNDv world > > > > > > > > > > > >These are the packages that would be merged, in order: > > > > > > > >Calculating dependencies / > > > > > > > >!!! Problem resolving dependencies for sys-devel/gdb from @selected > > > >.. done! > > > > > > > > > > > >!!! The ebuild selected to satisfy "sys-devel/gdb" has unmet > > > >requirements. > > > >- sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml -lzma > > > >- > > > >multitarget -test -vanilla" ABI_X86="(64)" > > > >PYTHON_SINGLE_TARGET="-python2_7 - > > > >python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 -python3_5" > > > > > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > > >python? ( exactly-one-of ( python_single_target_python2_7 > > > > > > > >python_single_target_python3_4 python_single_target_python3_5 ) ) > > > > > > > > ... > > > > > > Start with "grep - ir python /etc/portage". That found the source of the > > > problem on one of my systems, I was setting PYTHON_SINGLE_TARGET for one > > > package. > > > > Thanks Neil, I already had a look just in case I had set something up and > > forgot about it. This is all it showed: > > > > # grep -ir python /etc/portage > > /etc/portage/package.use/package.use:=media-libs/lcms-1.19-r1 python > > How about `emerge --info | grep PYTHON_SINGLE_TARGET'? The problem looks > > to be: > > PYTHON_SINGLE_TARGET="-python2_7 -python3_4 -python3_5" > > At least one PYTHON_SINGLE_TARGET needs to be set. I'd guess that > PYTHON_SINGLE_TARGET got updated to 3.6, leaving GDB in its dust. > > Alec Thanks Alec, yes python-3.6 was moved to the stable tree. This is what I have: PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Recent change in python - some packages are not happy
On Sat, Jun 23, 2018 at 10:38:35AM +0100, Mick wrote: > On Saturday, 23 June 2018 10:30:09 BST Neil Bothwick wrote: > > On 23 June 2018 10:14:31 BST, Mick wrote: > > >I came up to this today following a portage sync: > > > > > ># emerge -uaNDv world > > > > > > > > >These are the packages that would be merged, in order: > > > > > >Calculating dependencies / > > > > > >!!! Problem resolving dependencies for sys-devel/gdb from @selected > > >.. done! > > > > > > > > >!!! The ebuild selected to satisfy "sys-devel/gdb" has unmet > > >requirements. > > >- sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml -lzma > > >- > > >multitarget -test -vanilla" ABI_X86="(64)" > > >PYTHON_SINGLE_TARGET="-python2_7 - > > >python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 -python3_5" > > > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > >python? ( exactly-one-of ( python_single_target_python2_7 > > > > > >python_single_target_python3_4 python_single_target_python3_5 ) ) > > > > > > ... > > > > Start with "grep - ir python /etc/portage". That found the source of the > > problem on one of my systems, I was setting PYTHON_SINGLE_TARGET for one > > package. > > Thanks Neil, I already had a look just in case I had set something up and > forgot about it. This is all it showed: > > # grep -ir python /etc/portage > /etc/portage/package.use/package.use:=media-libs/lcms-1.19-r1 python > How about `emerge --info | grep PYTHON_SINGLE_TARGET'? The problem looks to be: > PYTHON_SINGLE_TARGET="-python2_7 -python3_4 -python3_5" At least one PYTHON_SINGLE_TARGET needs to be set. I'd guess that PYTHON_SINGLE_TARGET got updated to 3.6, leaving GDB in its dust. Alec
Re: [gentoo-user] Recent change in python - some packages are not happy
On Saturday, 23 June 2018 10:30:09 BST Neil Bothwick wrote: > On 23 June 2018 10:14:31 BST, Mick wrote: > >I came up to this today following a portage sync: > > > ># emerge -uaNDv world > > > > > >These are the packages that would be merged, in order: > > > >Calculating dependencies / > > > >!!! Problem resolving dependencies for sys-devel/gdb from @selected > >.. done! > > > > > >!!! The ebuild selected to satisfy "sys-devel/gdb" has unmet > >requirements. > >- sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml -lzma > >- > >multitarget -test -vanilla" ABI_X86="(64)" > >PYTHON_SINGLE_TARGET="-python2_7 - > >python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 -python3_5" > > > > The following REQUIRED_USE flag constraints are unsatisfied: > >python? ( exactly-one-of ( python_single_target_python2_7 > > > >python_single_target_python3_4 python_single_target_python3_5 ) ) > > > >The above constraints are a subset of the following complete > > > >expression: > >python? ( exactly-one-of ( python_single_target_python2_7 > > > >python_single_target_python3_4 python_single_target_python3_5 ) > >python_single_target_python2_7? ( python_targets_python2_7 ) > >python_single_target_python3_4? ( python_targets_python3_4 ) > >python_single_target_python3_5? ( python_targets_python3_5 ) ) any-of ( > >client > >server ) > > > >(dependency required by "@selected" [set]) > >(dependency required by "@world" [argument]) > > > > > >The system is currently using python 3.5: > > > ># eselect python update > > > >Switching to python3.5 > > > >Asus ~ # eselect python list > > > >Available Python interpreters, in order of preference: > > > >[1] python3.5 > > > >[2] python2.7 > > > > [3] python3.4 (uninstalled) > > > >Then noticed python-3.6.5 has been moved to stable, but the above won't > >allow > >me to proceed without --exclude gdb. Other systems are similarly > >refusing to > >run their weekly update, but due to other packages, e.g. > >libreoffice-bin. Is > >it a matter of waiting and resync'ing again later? > > Start with "grep - ir python /etc/portage". That found the source of the > problem on one of my systems, I was setting PYTHON_SINGLE_TARGET for one > package. Thanks Neil, I already had a look just in case I had set something up and forgot about it. This is all it showed: # grep -ir python /etc/portage /etc/portage/package.use/package.use:=media-libs/lcms-1.19-r1 python -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Recent change in python - some packages are not happy
On 23 June 2018 10:14:31 BST, Mick wrote: >I came up to this today following a portage sync: > ># emerge -uaNDv world > > >These are the packages that would be merged, in order: > >Calculating dependencies / > >!!! Problem resolving dependencies for sys-devel/gdb from @selected >.. done! > > >!!! The ebuild selected to satisfy "sys-devel/gdb" has unmet >requirements. >- sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml -lzma >- >multitarget -test -vanilla" ABI_X86="(64)" >PYTHON_SINGLE_TARGET="-python2_7 - >python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 -python3_5" > > The following REQUIRED_USE flag constraints are unsatisfied: >python? ( exactly-one-of ( python_single_target_python2_7 >python_single_target_python3_4 python_single_target_python3_5 ) ) > >The above constraints are a subset of the following complete >expression: >python? ( exactly-one-of ( python_single_target_python2_7 >python_single_target_python3_4 python_single_target_python3_5 ) >python_single_target_python2_7? ( python_targets_python2_7 ) >python_single_target_python3_4? ( python_targets_python3_4 ) >python_single_target_python3_5? ( python_targets_python3_5 ) ) any-of ( >client >server ) > >(dependency required by "@selected" [set]) >(dependency required by "@world" [argument]) > > >The system is currently using python 3.5: > ># eselect python update > >Switching to python3.5 > >Asus ~ # eselect python list > >Available Python interpreters, in order of preference: > >[1] python3.5 > >[2] python2.7 > > [3] python3.4 (uninstalled) > > >Then noticed python-3.6.5 has been moved to stable, but the above won't >allow >me to proceed without --exclude gdb. Other systems are similarly >refusing to >run their weekly update, but due to other packages, e.g. >libreoffice-bin. Is >it a matter of waiting and resync'ing again later? Start with "grep - ir python /etc/portage". That found the source of the problem on one of my systems, I was setting PYTHON_SINGLE_TARGET for one package. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
[gentoo-user] Recent change in python - some packages are not happy
I came up to this today following a portage sync: # emerge -uaNDv world These are the packages that would be merged, in order: Calculating dependencies / !!! Problem resolving dependencies for sys-devel/gdb from @selected .. done! !!! The ebuild selected to satisfy "sys-devel/gdb" has unmet requirements. - sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml -lzma - multitarget -test -vanilla" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-python2_7 - python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 -python3_5" The following REQUIRED_USE flag constraints are unsatisfied: python? ( exactly-one-of ( python_single_target_python2_7 python_single_target_python3_4 python_single_target_python3_5 ) ) The above constraints are a subset of the following complete expression: python? ( exactly-one-of ( python_single_target_python2_7 python_single_target_python3_4 python_single_target_python3_5 ) python_single_target_python2_7? ( python_targets_python2_7 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python3_5? ( python_targets_python3_5 ) ) any-of ( client server ) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) The system is currently using python 3.5: # eselect python update Switching to python3.5 Asus ~ # eselect python list Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 [3] python3.4 (uninstalled) Then noticed python-3.6.5 has been moved to stable, but the above won't allow me to proceed without --exclude gdb. Other systems are similarly refusing to run their weekly update, but due to other packages, e.g. libreoffice-bin. Is it a matter of waiting and resync'ing again later? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
