[gentoo-user] CrystalHD decoder in mythfrontend
I had posted about this in the mythtv mailing list earlier, here I want to draw the attention of video experts in the group. I am trying to use the CrystalHD BCM70015 card in an Intel Atom box and seeing the following video glitch https://cdn.pbrd.co/images/Hw60GWc.jpg There are two issues here, one is the overlapped images and the second one is on the right side there is a mostly green flashing vertical band. Appreciate any inputs to understand the root cause of this problem. holla -- http://lists.mythtv.org/pipermail/mythtv-users/2018-July/396812.html
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
2018-07-25 18:20 GMT+03:00 Mike Gilbert : > On Wed, Jul 25, 2018 at 7:58 AM Grand Duet wrote: >> >> After today's emerge-webrsync, I have found that python_targets >> and python_single_targets use flags have been changed again >> from python3_5 to python3_6, which leads to a lot of recompilation. >> >> It already happened last month and a week later the both use flags >> was changed back, again with a lot of recompilations. >> >> And it was not the first time! >> >> Is any real need to switch python_targets and python_single_target >> back and forth every month? >> > > It's very simple: > > 1. The default was switched to python3.6. This was probably a bit premature. > 2. People complained that this broke their systems, so we reverted the > default back to python3.5. > 3. The problems were fixed, so we switched the default back to python3.6. > > Sorry to have wasted your precious computing time, but hey, people > make mistakes sometimes. Before switching python_targets for the first time, you could use your news system to inform Gentoo users that 1) you are switching python_targets 2) it may be "a bit premature", and so, those who really want to have a stable Gentoo system should 1) do such and such changes to their config files and 2) wait about 3 months untill all the dust will settle. By the way, last time I have tried to set PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" in my /etc/portage/make.conf and I got a vary strange errors from emerge afterwards: every time the # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world command was run, a *new* package complained about something and system update aborted. I guess from that that the syntax of setting python_targets has been changed lately (may be, it should now be set only in package.use) but nobody informed Gentoo users about it. P.S. The said above together with the recent Gentoo signing key issue and sometimes "corrupted" daily portage snapshots that I download by emerge-webrsync make me think that even so called "stable" Gentoo lacks quality control and cannot be considered as stable and suted for those that really need a stable system.
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
On Thu, Jul 26, 2018 at 6:44 AM Grand Duet wrote: > > Before switching python_targets for the first time, you could use your > news system to inform Gentoo users that > 1) you are switching python_targets > 2) it may be "a bit premature", If anybody thought that it was a bit premature it wouldn't have been done at all. > and so, those who really want to have a stable Gentoo system should > 1) do such and such changes to their config files and > 2) wait about 3 months untill all the dust will settle. Did this even impact the stable branch? I thought this was only deployed to ~arch. If you want stable Gentoo, you probably shouldn't have edited make.conf to set your keywords to ~arch. > P.S. The said above together with the recent Gentoo signing key issue > and sometimes "corrupted" daily portage snapshots that I download by > emerge-webrsync make me think that even so called "stable" Gentoo > lacks quality control and cannot be considered as stable and suted for > those that really need a stable system. Well, most people stick with RHEL/CentOS or Debian Stable for that kind of experience, where changes only happen on releases with significant QA, and backporting of fixes. That simply isn't the kind of experience Gentoo aims to deliver. -- Rich
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
2018-07-26 15:01 GMT+03:00 Rich Freeman : > On Thu, Jul 26, 2018 at 6:44 AM Grand Duet wrote: >> >> Before switching python_targets for the first time, you could use your >> news system to inform Gentoo users that >> 1) you are switching python_targets >> 2) it may be "a bit premature", > > If anybody thought that it was a bit premature it wouldn't have been > done at all. It is exactly what is bad: nobody expects any troubles where they definitely should be! Anyway, it is a good idea to write a news on changing python_targets and major version of gcc, even if no developper expects any troubles, because we already know their predictive (dis)ability. :) >> and so, those who really want to have a stable Gentoo system should >> 1) do such and such changes to their config files and >> 2) wait about 3 months untill all the dust will settle. > > Did this even impact the stable branch? Yes. > If you want stable Gentoo, you probably shouldn't have edited make.conf > to set your keywords to ~arch. I did not. Moreover, currently I have no single unstable package installed on my system. >> P.S. The said above together with the recent Gentoo signing key issue >> and sometimes "corrupted" daily portage snapshots that I download by >> emerge-webrsync make me think that even so called "stable" Gentoo >> lacks quality control and cannot be considered as stable and suted for >> those that really need a stable system. > > Well, most people stick with RHEL/CentOS or Debian Stable for that > kind of experience, where changes only happen on releases with > significant QA, and backporting of fixes. That simply isn't the kind > of experience Gentoo aims to deliver. It is sad to hear. Actually, I don't want to change the Linux distro. A bit more "due diligence" from Gentoo devs will be enough. :) May be, adding some additional "almost stable" level between "stable" and "unstable" one to make "stable" stable indeed? In any case, if I will leave Gentoo, it will be in favour of some BSD, not a Linux disro.
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
On Thu, 26 Jul 2018 13:44:28 +0300, Grand Duet wrote: > Before switching python_targets for the first time, you could use your > news system to inform Gentoo users that > 1) you are switching python_targets Like the one on May 22nd titled "Python 3.6 to become the default target"? > 2) it may be "a bit premature", That sort of information is only known with hindsight or a time machine. > and so, those who really want to have a stable Gentoo system should > 1) do such and such changes to their config files and Like in the aforementioned news item? FWIW I had no problem with the profile change and locked my system at 3.6 to save switching back when the profile did so. -- Neil Bothwick Anything worth fighting for is worth fighting dirty for. pgpnnOkD4mJ2G.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
On Thu, Jul 26, 2018 at 8:45 AM Grand Duet wrote: > > Anyway, it is a good idea to write a news on changing python_targets > and major version of gcc, even if no developper expects any troubles, > because we already know their predictive (dis)ability. :) > You won't get any argument from me there - more news is usually better. If nothing else people want to know they don't have to do something when they see 200 packages being upgraded. > > Did this even impact the stable branch? > > Yes. Hmm, I suspect I didn't sync before it was reverted. Either that or I noticed the noise on the lists and waited a day. This is one issue with our news - it isn't really realtime. If we want people to hold the presses and re-sync they don't get that notice until they've already re-synced. > May be, adding some additional "almost stable" level between > "stable" and "unstable" one to make "stable" stable indeed? If anything it seems like the proposal to drop stable comes along every few years. I don't see anybody being eager to add another level of QA. A big practical issue would be that unless people are actually using the two lower levels significantly then nothing is actually getting checked before going to stable. There is really no reason you couldn't have a release-based Gentoo derivative. Everything is in git. All "somebody" needs to do is start a repo with a release-driven workflow that treats Gentoo as the upstream master branch, targeting changes for release branches and then doing release candidates and QA/etc. Then those release-based users would sync from there instead of the upstream Gentoo repo. Ideally somebody would bundle it with a reference binary repo that people could optionally sync from to speed installs for packages where they're not changing USE flags. The problem is that this all takes quite a bit of work, and I'm skeptical that it would ever happen. However, for larger Gentoo deployments in production environments I suspect most are doing things more-or-less in this fashion, but just with the packages they care about. If somebody has 100 production servers running Gentoo I doubt they are set to just sync from us. Rather they would set up their own mirror and carefully test portage snapshots before they go rolling them out. -- Rich
Re: [gentoo-user] Re: scanner problem : latest
On Tuesday, 24 July 2018 15:38:35 BST Mick wrote: > On Tuesday, 24 July 2018 15:14:32 BST Philip Webb wrote: > > 180723 Neil Bothwick wrote: > > > On Fri, 20 Jul 2018 09:04:26 -0400, Philip Webb wrote: > > >> Linux Mint 19 leads you along to a point where you've told it > > >> where to install, you click 'proceed' & it chugs along nicely, > > >> then it says it's trying to install a bootloader > > >> without asking whether you want it to or where to do it. > > > > > > For future reference, start the Mint installer with "ubiquity -b", > > > then it doesn't install a boot loader at all > > > and you can add it to your Gentoo bootloader after rebooting. > > > > I started the Mint installer by clicking on its desktop button. > > What is 'ubiquity' & how would I use it ? > > > > > WinErr 018: Unrecoverable error - System has been destroyed. > > > Buy a new one. Old Windows licence is not valid anymore. > > > > That's how I felt for 30 min after Mint played its dirty trick above > > (grin). > > See attached screenshot. > > Meanwhile I'm still at a loss why on a BIOS with GPT system GRUB installed > fine without any mishaps, but upon a GRUB update some days later it refused > to install without me creating a new protective MBR partition marked as > ef02. > :-/ I just noticed when I start the VM using the aqemu GUI, the system identifies its virtual hard drives as /dev/sda, while when I start it with qemu-system- x86_64 on the CLI it identifies the hard drives as /dev/vda. This is the reason of GRUB refusing to update itself ... I installed with aqemu, then some days later I tried to update GRUB running the VM via the CLI. So much for thinking aqemu is a just a simple GUI for running qemu VMs. It evidently does its own tha'ng. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
2018-07-26 16:01 GMT+03:00 Neil Bothwick : > On Thu, 26 Jul 2018 13:44:28 +0300, Grand Duet wrote: > >> Before switching python_targets for the first time, you could use your >> news system to inform Gentoo users that >> 1) you are switching python_targets > > Like the one on May 22nd titled "Python 3.6 to become the default target"? > >> and so, those who really want to have a stable Gentoo system should >> 1) do such and such changes to their config files and > > Like in the aforementioned news item? > > FWIW I had no problem with the profile change and locked my system at 3.6 > to save switching back when the profile did so. Ok. There was such a news. However, I have actually followed the following recommendation in it, before the last python_target switch from 3.5 to 3.6: If you would like to postpone the switch to Python 3.6, you can copy the current value of PYTHON_TARGETS and/or PYTHON_SINGLE_TARGET to /etc/portage/make.conf or its equivalent: PYTHON_TARGETS="python2_7 python3_5" PYTHON_SINGLE_TARGET="python3_5" but the emerge gave strange errors mentioned above and aborted.
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
2018-07-26 16:04 GMT+03:00 Rich Freeman : > On Thu, Jul 26, 2018 at 8:45 AM Grand Duet wrote: >> > Did this even impact the stable branch? >> >> Yes. > > Hmm, I suspect I didn't sync before it was reverted. Either that or I > noticed the noise on the lists and waited a day. > > This is one issue with our news - it isn't really realtime. If we > want people to hold the presses and re-sync they don't get that notice > until they've already re-synced. > >> May be, adding some additional "almost stable" level between >> "stable" and "unstable" one to make "stable" stable indeed? > > If anything it seems like the proposal to drop stable comes along > every few years. I don't see anybody being eager to add another level > of QA. A big practical issue would be that unless people are actually > using the two lower levels significantly then nothing is actually > getting checked before going to stable. > > There is really no reason you couldn't have a release-based Gentoo > derivative. Everything is in git. All "somebody" needs to do is > start a repo with a release-driven workflow that treats Gentoo as the > upstream master branch, targeting changes for release branches and > then doing release candidates and QA/etc. Then those release-based > users would sync from there instead of the upstream Gentoo repo. > Ideally somebody would bundle it with a reference binary repo that > people could optionally sync from to speed installs for packages where > they're not changing USE flags. > > The problem is that this all takes quite a bit of work, and I'm > skeptical that it would ever happen. However, for larger Gentoo > deployments in production environments I suspect most are doing things > more-or-less in this fashion, but just with the packages they care > about. If somebody has 100 production servers running Gentoo I doubt > they are set to just sync from us. Rather they would set up their own > mirror and carefully test portage snapshots before they go rolling > them out. Ok. Thank you for your reply.
[gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?
Just now I have tried to manually set PYTHON_TARGETS="python2_7 python3_6" PYTHON_SINGLE_TARGET="python3_6" in /etc/portage/make.conf and got the following error: # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world These are the packages that would be merged, in order: Calculating dependencies... done! !!! The ebuild selected to satisfy "app-text/asciidoc" has unmet requirements. - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="(-pypy) -python2_7" PYTHON_TARGETS="python2_7 (-pypy)" The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( python_single_target_pypy python_single_target_python2_7 ) The above constraints are a subset of the following complete expression: exactly-one-of ( python_single_target_pypy python_single_target_python2_7 ) python_single_target_pypy? ( python_targets_pypy ) python_single_target_python2_7? ( python_targets_python2_7 ) (dependency required by "app-text/dvisvgm-2.1.3::gentoo" [installed]) (dependency required by "app-text/texlive-2017::gentoo[extra]" [installed]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) which is similar to those errors I got while trying to set PYTHON_TARGETS="python2_7 python3_5" PYTHON_SINGLE_TARGET="python3_5" before switching yesterday from python-3.5 to python-3.6 target. Does it mean that setting python targets in /etc/portage/make.conf is not supported any more? P.S. Currently my system is up-to-date and already switched to python-3.6 targets.
Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?
On Thu, Jul 26, 2018 at 10:57 AM Grand Duet wrote: > > Just now I have tried to manually set > > PYTHON_TARGETS="python2_7 python3_6" > PYTHON_SINGLE_TARGET="python3_6" > > in /etc/portage/make.conf and got the following error: > > # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > > !!! The ebuild selected to satisfy "app-text/asciidoc" has unmet requirements. > - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight > -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="(-pypy) -python2_7" > PYTHON_TARGETS="python2_7 (-pypy)" > > The following REQUIRED_USE flag constraints are unsatisfied: > exactly-one-of ( python_single_target_pypy python_single_target_python2_7 > ) > > The above constraints are a subset of the following complete expression: > exactly-one-of ( python_single_target_pypy > python_single_target_python2_7 ) python_single_target_pypy? ( > python_targets_pypy ) python_single_target_python2_7? ( > python_targets_python2_7 ) > > (dependency required by "app-text/dvisvgm-2.1.3::gentoo" [installed]) > (dependency required by "app-text/texlive-2017::gentoo[extra]" [installed]) > (dependency required by "@selected" [set]) > (dependency required by "@world" [argument]) > > which is similar to those errors I got while trying to set > > PYTHON_TARGETS="python2_7 python3_5" > PYTHON_SINGLE_TARGET="python3_5" > > before switching yesterday from python-3.5 to python-3.6 target. > > Does it mean that setting python targets in /etc/portage/make.conf is > not supported any more? No, setting PYTHON_TARGETS in make.conf should still work. It looks like asciidoc only supports python2, and for some reason portage is trying to disable python2_7. I'm not sure why that might be; we enable python2_7 for asciidoc via profiles/base/package.use. Have you made some odd change to your profile, or overridden something in /etc/portage/package.use?
Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?
On Thu, Jul 26, 2018 at 10:57 AM Grand Duet wrote: > > Just now I have tried to manually set > > PYTHON_TARGETS="python2_7 python3_6" > PYTHON_SINGLE_TARGET="python3_6" > > !!! The ebuild selected to satisfy "app-text/asciidoc" has unmet requirements. > - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight > -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="(-pypy) -python2_7" > PYTHON_TARGETS="python2_7 (-pypy)" > > The following REQUIRED_USE flag constraints are unsatisfied: > exactly-one-of ( python_single_target_pypy python_single_target_python2_7 > ) > > Does it mean that setting python targets in /etc/portage/make.conf is > not supported any more? No, it means that this setting doesn't work with asciidoc specifically. I believe you'd need to override the setting for that one particular package in package.env. Unfortunately that is a fairly significant dependency that just about everybody doing this runs into. Anytime you set a setting globally in make.conf there is the possibility of needing to override it per-package if it causes compatibility issues. Personally I'd suggest just letting the profiles control everything unless you really care what is going on with python. If you do care a lot about what is going on with python, then you're probably are in a better position to deal with errors like this. -- Rich
Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?
On 26.07.2018 16:57, Grand Duet wrote: > PYTHON_TARGETS="python2_7 python3_6" > PYTHON_SINGLE_TARGET="python3_6" > [...] > The ebuild selected to satisfy "app-text/asciidoc" has unmet requirements. > The following REQUIRED_USE flag constraints are unsatisfied: > exactly-one-of ( python_single_target_pypy python_single_target_python2_7 ) > [...] > Does it mean that setting python targets in /etc/portage/make.conf is > not supported any more? No. It means what the message says says. app-text/asciidoc requires its PYTHON_SINGLE_TARGET to be either PyPy exclusive or Python 2.7. You cannot force an application to use Python 3.x if the maintainer flagged the ebuild as incompatible with Python 3.x. -Ralph
[gentoo-user] Re: Setting PYTHON_TARGETS in make.conf is not supported?
On 26/07/18 17:57, Grand Duet wrote: Just now I have tried to manually set PYTHON_TARGETS="python2_7 python3_6" PYTHON_SINGLE_TARGET="python3_6" in /etc/portage/make.conf and got the following error: # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world These are the packages that would be merged, in order: Calculating dependencies... done! !!! The ebuild selected to satisfy "app-text/asciidoc" has unmet requirements. - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="(-pypy) -python2_7" PYTHON_TARGETS="python2_7 (-pypy)" When setting PYTHON_SINGLE_TARGET in make.conf, some packages might result in that error. That just means that for those packages, you need to set the correct python USE flag. For asciidoc, I believe you need this: app-text/asciidoc python_single_target_python2_7
Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?
2018-07-26 18:09 GMT+03:00 Mike Gilbert : > On Thu, Jul 26, 2018 at 10:57 AM Grand Duet wrote: >> >> Just now I have tried to manually set >> >> PYTHON_TARGETS="python2_7 python3_6" >> PYTHON_SINGLE_TARGET="python3_6" >> >> in /etc/portage/make.conf and got the following error: >> >> # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world >> >> These are the packages that would be merged, in order: >> >> Calculating dependencies... done! >> >> !!! The ebuild selected to satisfy "app-text/asciidoc" has unmet >> requirements. >> - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight >> -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="(-pypy) -python2_7" >> PYTHON_TARGETS="python2_7 (-pypy)" >> >> The following REQUIRED_USE flag constraints are unsatisfied: >> exactly-one-of ( python_single_target_pypy >> python_single_target_python2_7 ) >> >> The above constraints are a subset of the following complete expression: >> exactly-one-of ( python_single_target_pypy >> python_single_target_python2_7 ) python_single_target_pypy? ( >> python_targets_pypy ) python_single_target_python2_7? ( >> python_targets_python2_7 ) >> >> (dependency required by "app-text/dvisvgm-2.1.3::gentoo" [installed]) >> (dependency required by "app-text/texlive-2017::gentoo[extra]" [installed]) >> (dependency required by "@selected" [set]) >> (dependency required by "@world" [argument]) >> >> which is similar to those errors I got while trying to set >> >> PYTHON_TARGETS="python2_7 python3_5" >> PYTHON_SINGLE_TARGET="python3_5" >> >> before switching yesterday from python-3.5 to python-3.6 target. >> >> Does it mean that setting python targets in /etc/portage/make.conf is >> not supported any more? > > No, setting PYTHON_TARGETS in make.conf should still work. > > It looks like asciidoc only supports python2, and for some reason > portage is trying to disable python2_7. I'm not sure why that might > be; we enable python2_7 for asciidoc via profiles/base/package.use. > > Have you made some odd change to your profile, or overridden something > in /etc/portage/package.use? No, I have not make any changes in my profile or packege.use. I have only added PYTHON_TARGETS="python2_7 python3_6" PYTHON_SINGLE_TARGET="python3_6" lines to /etc/portage/make.conf And when I comment these two lines in /etc/portage/make.conf, the error mentioned above disappears. Without those two lines in make.conf, I have the following: $ equery uses asciidoc * Found these USE flags for app-text/asciidoc-8.6.10: U I - - examples : Install examples, usually source code - - graphviz : Add support for the Graphviz library - - highlight : Enable source code highlighting + + python_single_target_python2_7 : Build for Python 2.7 only + + python_targets_python2_7 : Build with Python 2.7 With those two lines in make.conf, I have the following: $ equery uses asciidoc * Found these USE flags for app-text/asciidoc-8.6.10: U I - - examples : Install examples, usually source code - - graphviz : Add support for the Graphviz library - - highlight : Enable source code highlighting - + python_single_target_python2_7 : Build for Python 2.7 only + + python_targets_python2_7 : Build with Python 2.7 Ok, got it: the mentioned above settings in /etc/portage/make.conf overrides those of asciidoc. So, the recomendations made in the news "Python 3.6 to become the default target" (mentioned in the thread "Any real need to switch python targets back and forth every month?") on how to set python targets in /etc/portage/make.conf was actually useless. Thank you for all who replied to this thread.
Re: [gentoo-user] how to update python choice
On Thu, Jul 26 2018, Neil Bothwick wrote: > On Wed, 25 Jul 2018 23:23:18 -0400, allan gottlieb wrote: > >> On Thu, Jul 26 2018, Bill Kenworthy wrote: >> >> > On 26/07/18 09:10, allan gottlieb wrote: >> >> I am still using python 3.4, i.e. >> >> >> >> sh-4.4# eselect python show >> >> python3.4 >> >> sh-4.4# >> >> >> >> sh-4.4# eselect python list >> >> Available Python interpreters, in order of preference: >> >> [1] python3.4 >> >> [2] python3.6 (fallback) >> >> [3] python3.5 (fallback) >> >> [4] python2.7 (fallback) >> >> sh-4.4# >> >> >> >> I realize I should have updated previously. >> >> >> >> Is a python update as simple as >> >> emerge --update --changed-use --with-bdeps=n @world >> >> eselect python set python3.6 >> >> emerge --update --changed-use --with-bdeps=n @world >> >> >> >> I have no custom python scripts on either of my systems. >> >> >> >> thanks in advance, >> >> allan >> >> >> > >> > >> > Hi, no problems doing it except because of the large number of >> > packages look forward to hours of compiling (24hrs on my surface >> > pro4). Got a few other systems to do which is going to take awhile. >> > >> > BillK >> >> Thank you, that is just what I needed to know. > > If the packages were already built with python_3.6 in PYTHON_TARGETS, > there should be no rebuilding. It is the change on PYTHON_TARGETS that > triggers the rebuild, eselect just chooses from one of the available > targets AIUI. Thanks for the clarification. allan
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
On Thu, 26 Jul 2018 09:04:13 -0400, Rich Freeman wrote: > This is one issue with our news - it isn't really realtime. If we > want people to hold the presses and re-sync they don't get that notice > until they've already re-synced. We could do with an option to sync only the news rather than the whole tree, then we can read new news items before syncing fully. -- Neil Bothwick "Apple I" (c) Copyright 1767, Sir Isaac Newton. pgpr3QPyyIfat.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
On Thu, 26 Jul 2018 17:34:25 +0300, Grand Duet wrote: > > FWIW I had no problem with the profile change and locked my system at > > 3.6 to save switching back when the profile did so. > > Ok. There was such a news. However, I have actually followed the > following recommendation in it, before the last python_target switch > from 3.5 to 3.6: > >If you would like to postpone the switch to Python 3.6, you can copy >the current value of PYTHON_TARGETS and/or PYTHON_SINGLE_TARGET >to /etc/portage/make.conf or its equivalent: > > PYTHON_TARGETS="python2_7 python3_5" > PYTHON_SINGLE_TARGET="python3_5" > > but the emerge gave strange errors mentioned above and aborted. I got some message about USE flags when keeping it at 3.6 in the same way. So I did it in what seemed like the more elegant way of overriding a profile change, in /etc/portage/profile/make.defaults. PYTHON_TARGETS="python2_7 python3_5 -python3_6" PYTHON_SINGLE_TARGET="python3_5 -python3_6" -- Neil Bothwick Last words of a Windows user: = Where do I have to click now? - There? pgpRfsaAtQmlL.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: Setting PYTHON_TARGETS in make.conf is not supported?
On Thu, 26 Jul 2018 18:12:21 +0300, Nikos Chantziaras wrote: > When setting PYTHON_SINGLE_TARGET in make.conf, some packages might > result in that error. That just means that for those packages, you need > to set the correct python USE flag. For asciidoc, I believe you need > this: > >app-text/asciidoc python_single_target_python2_7 Or set your profile override in /etc/portage/profile as per my reply in the other python thread. -- Neil Bothwick "Logic will get you from A to B. Imagination will take you everywhere." (Albert Einstein) pgpwabvC83ozF.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Any real need to switch python targets back and forth every month?
On 26/07/18 21:01, Neil Bothwick wrote: > On Thu, 26 Jul 2018 13:44:28 +0300, Grand Duet wrote: > >> Before switching python_targets for the first time, you could use your >> news system to inform Gentoo users that >> 1) you are switching python_targets > Like the one on May 22nd titled "Python 3.6 to become the default target"? > >> 2) it may be "a bit premature", > That sort of information is only known with hindsight or a time machine. > >> and so, those who really want to have a stable Gentoo system should >> 1) do such and such changes to their config files and > Like in the aforementioned news item? > > FWIW I had no problem with the profile change and locked my system at 3.6 > to save switching back when the profile did so. > > Yes there was the original news item - but nothing about the problems this caused, and the back and forwarding which is causing me grief. It is only switching targets, but when you have problems and decide to remove 3.6 and recompile, then having to go through it all again without proper information it has impact. A news item is supposed to give information ... I am not criticising the changes itself (sh.. happens), but being left in the dark about it. BillK
