Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Neil Bothwick
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

Re: [gentoo-user] how to update python choice

2018-07-26 Thread allan gottlieb
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 >> >>

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Neil Bothwick
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

Re: [gentoo-user] Re: Setting PYTHON_TARGETS in make.conf is not supported?

2018-07-26 Thread Neil Bothwick
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: > >

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Bill Kenworthy
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

Re: [gentoo-user] how to update python choice

2018-07-26 Thread Neil Bothwick
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

[gentoo-user] CrystalHD decoder in mythfrontend

2018-07-26 Thread sathish holla
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

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Grand Duet
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.

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread 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

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Grand Duet
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

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread 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"? > 2) it may

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Rich Freeman
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

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Grand Duet
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

Re: [gentoo-user] Any real need to switch python targets back and forth every month?

2018-07-26 Thread Grand Duet
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

[gentoo-user] Re: Setting PYTHON_TARGETS in make.conf is not supported?

2018-07-26 Thread Nikos Chantziaras
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

Re: [gentoo-user] Re: scanner problem : latest

2018-07-26 Thread Mick
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,

[gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?

2018-07-26 Thread Grand Duet
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:

Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?

2018-07-26 Thread 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

Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?

2018-07-26 Thread Rich Freeman
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

Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?

2018-07-26 Thread Ralph Seichter
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 (

Re: [gentoo-user] Setting PYTHON_TARGETS in make.conf is not supported?

2018-07-26 Thread gevisz
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