[gentoo-user] nx / nxclient - replacement

[thelma]

Are there any good replacement for "nx / nxclient" in Linux?
NX is long time gone from portage.  I hope, I can still install them
from atic.
This was another reason I wasn't upgrading for a long time as I need
them to access remote boxes in GUI.

-- 
Thelma

Re: [gentoo-user] Re: Copying USB->USB: sync after every file

[Mick]

Ha!  I just upgraded to 4.9.6-r1 gentoo kernel sources and I can no longer
mount USB sticks!  I can still mount them using pmount on the CLI, but the
desktop click-to-mount function does not work in Plasma, KDE applications
or enlightenment.

On 5 February 2017 at 17:04, Frank Steinmetzger  wrote:

> On Sun, Feb 05, 2017 at 12:20:25PM +0100, Frank Steinmetzger wrote:
>
> > Having no time over the week, I finally got the new install running. But
> > before I was set back by not being able to log in to Plasma with lightdm.
> > Only sddm works.
>
> I really need to lower my sentences’ complexity. That should be “But --
> just like
> before -- I was set back by not being able to log in to Plasma with
> lightdm.”
>
> --
> Gruß | Greetings | Qapla’
> Please do not share anything from, with or about me with any social
> network.
>
> No, you *can’t call 999 now.  I’m downloading my mail.
>



-- 
Regards,
Mick

Re: [gentoo-user] rdate -s timeout for 129.6.15.28

[thelma]

On 02/05/2017 11:37 PM, the...@sys-concept.com wrote:
> I installed "rdate" and trying to sync time on my new box but I'm getting:
> 
> /usr/bin/rdate -s 129.6.15.28
> rdate: timeout for 129.6.15.28
> 
> Time setting works on my other boxes but new the new one :-/

It worked with "-u" switch and is working now with "-s"

[gentoo-user] rdate -s timeout for 129.6.15.28

[thelma]

I installed "rdate" and trying to sync time on my new box but I'm getting:

/usr/bin/rdate -s 129.6.15.28
rdate: timeout for 129.6.15.28

Time setting works on my other boxes but new the new one :-/

-- 
Thelma

Re: [gentoo-user] Re: Gentoo on a Surface Pro 3?

[Alex Thorne]

A wiki article would be great. I'd be happy to contribute my experiences
with my Surface Pro 4 if I eventually get round to installing Gentoo on it.

On Sat, 4 Feb 2017 at 22:30 Daniel Frey  wrote:

> On 02/01/2017 01:34 PM, Alex Thorne wrote:
> > While I haven't tried this I would be very interested to hear how it
> > goes, what hardware you can get working etc. Do keep us updated.
> >
>
> An update...
>
> After a lot of experimenting, rebuilding kernels, figuring out what's
> needed and not... this took a few days, I have it working somewhat.
>
> I am using gentoo-sources-4.9.6-r1 for this test. I did a lot of
> experimenting to see what's needed for the tablet only (not the dock,
> for example.) I've managed to trim the kernel down a fair bit removing
> drivers that are not needed.
>
> This is what I have working so far without tweaks on plasma and systemd
> (only installing userland packages and configuring the kernel. After two
> days I found a starter .config with could've made things SO MUCH EASIER.
> Oh well.):
>
> -standard AHCI controller
> -Displayport port on tablet
> -Sound
>   -Speakers work fine
>   -Headphones work (speakers on tablet automute)
>   -Microphone works (used audacity to record my voice)
> -MicroSD slot (I didn't even know it HAD one until I read the specs!
>   (it's well hidden under the kickstand)
> -Power button (pops up plasma's logout/shutdown/restart dialog)
> -Windows button on the front of the tablet (opens K menu)
> -Volume buttons on the side of the tablet
> -Both front and rear webcams (tested using Kamoso)
> -USB3 port (a given, really...)
> -Wifi (using mwifiex_pcie)
> -Bluetooth
> -Touch screen
>   -Finger touch works, no multitouch though
>   -Pen works on display, and taps will do a left-click
>   -Buttons on pen do not seem to work. It will pair with Bluetooth
>but x11 doesn't seem to register an input device.
> -Screen brightness is directly supported (intel_backlight), can change
>  the display by using /sys/class/backlight/intel_backlight/brightness or
>  by using KDE's brightness slider in the Power applet in the tray
> -Battery is detected and showing power levels
> -Type cover (this worked with no patches in 4.9.6-r1)
>   -Keyboard section works normally
>   -Trackpad works, but doesn't seem to recognize multitouch
> -Closing the lid appears to put plasma to sleep. Opening the lid wakes
>  the tablet and asks for password
>
> Some things to maybe figure out:
>
> -Type cover touchpad multitouch
> -Touch screen multitouch
> -Pen bluetooth pairing for the buttons
> -Proper HiDPI detection (used /etc/sddm.conf but when using an external
>  display it was all messed up. However, my monitor is very old and
>  doesn't support EDID properly which may be the problem.) On occasion,
>  when the lock screen comes on, it doesn't detect the display correctly
>  when woken up and scales it incorrectly.
>
> I must say, out of the box it actually works reasonably well. I skipped
> the distcc setup - I knew that the i7 has overheat problems in these
> tablets but I have the i5 version and it has been working fine with no
> overheating problems.
>
> I also borrowed a dock from work so I plan to tweak the kernel some more
> to see if I can get the USB3 and USB2 ports working, as well as the
> displayport and headphone jack.
>
> Other things of note: I found out through the Mint kernel that it can
> register the sensors in the device, under Industrial IO setup. However,
> there doesn't seem to be anything in userland that can use this sensor
> to automatically rotate the display.
>
> I have taken tons of notes through this process. Maybe I should start a
> wiki article...
>
> Dan
>
>
>

Re: [gentoo-user] upgrading 1-year old system

[Neil Bothwick]

On Sun, 5 Feb 2017 13:02:01 -0700, the...@sys-concept.com wrote:

> > >=sys-fs/eudev-1.3 required by (virtual/udev-215:0/0::gentoo,
> > >installed)  
> > 
> >   (sys-fs/udev-225-r1:0/0::gentoo, ebuild scheduled for merge) pulled
> > in by 
> >> =sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
> > (>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by  
> > (virtual/libudev-215-r1:0/1::gentoo, ebuild scheduled for merge)
> > 
> > sys-fs/udev is not installed

You probably have different USE flags for virtual/libudev and eudev, so
the virtual tries to pull in udev instead. As it so often the case, the
full output from emerge will help, particularly if you add the -t switch.

Or you could simply use udev instead of eudev.


-- 
Neil Bothwick

The voices in my head may not be real, but they have some good ideas!


pgpb3i1HaEfBP.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] New Installation

[Floyd Anderson]

Hi Dale,

lets have a break. I lose the thread and driving nearer the ditch than 
the track. I think the main things were said. All following would only 
drift away.


Sorry for the noise.

--
floyd

Re: [gentoo-user] New Installation

[Dale]

Rich Freeman wrote:
> On Sun, Feb 5, 2017 at 11:16 AM, Floyd Anderson  wrote:
>> That’s why Gentoo is often regarded as the freedom of choice.
> This includes the freedom to shoot yourself in the foot.
>
> I suggest that new users consider going with the defaults except when
> they have a reason not to.
>
> Sure, we can all pass around our make.conf files, and people can just
> blindly copy what we're using.  In a sense this is also stick with the
> "defaults" - just somebody else's choice of defaults.
>
> The difference is that if you don't do this then you're getting the
> defaults the maintainer thought best, and the settings that get the
> widest extent of testing.  If you run into a problem, you're probably
> close to the upstream configuration, which means both upstream and the
> maintainer are probably going to be willing to lend you a hand.
> You're also closer to the settings used by other distros, which means
> their own documentation will help you.
>
> Stick with the profile defaults to start.  By all means tweak
> something if you have a reason to, but make these conscious informed
> decisions.  Keep things simple.
>
> When you start out with a very complex USE configuration on a distro
> you're new to, then you're going to struggle a lot to deal with the
> resulting issues.
>
> In terms of profiles themselves, hardened isn't the friendliest place
> to start.  It tends to get used in server environments, and I suspect
> very few run a desktop environment in a hardened environment.  I'd
> suggest chatting with others who run hardened to understand its
> limitations.  I've been running Gentoo for a very long time now and I
> wouldn't expect to do a hardened desktop install and get through it
> without a bit of troubleshooting.
>

Shooting oneself in the foot could be that USE="-* 
option.  Talk about being brave.  lol 

As a somewhat seasoned Gentoo user, when I built this new rig, I had to
add USE flags slowly.  As a test, I tried copying my USE flags over from
the old install.  When I did a emerge -uvaDN system, it puked all over
my keyboard.  I recall having blockers that emerge couldn't resolve. 
There were some other issues as well.  I went back to defaults and added
them slowly.  That worked well. 

I've read about hardened.  I've always wanted to play with it but I'd
want a separate puter to play with that on.  I've also wondered if it
would even benefit me at all.

Dale

:-)  :-) 

Re: [gentoo-user] New Installation

[Dale]

Floyd Anderson wrote:
> On Sun, 05 Feb 05:05:56 -0600
> Dale  wrote:
>> The point of my post was not for a specific flag.  I just picked a
>> flag that has been around for a long time and pretty much everyone
>> recognizes what it is for.
>>
>> […]
>>
>> I might add, there are flags that we can't change.  Those are set by
>> upstream or the devs.  My post wasn't about that either.  It was all
>> about managing options that we can change..
>
> I think there is an unfortunate misunderstanding and I may have to be
> more clear. I also just picked the threads-flag example as what it is,
> an example — not as a specific advise. My intention was to demonstrate
> my thoughts when I read the post from the dev list.
>
> Basically I handle my USE flags similar as you do and had described in
> your former post. What I always want goes to make.conf (trying to keep
> it according to less is more) and specific flags lives in package.use.
>
> When I read the post from Rich, I remember that I have the mentioned
> ‘threads’ flag globally set. Some time ago I put it in, it works and
> nearly no thoughts were wasted since then. I didn’t care about:
>  • pulling in heavyweight dependencies
>  • package maintainers set a flag off by default for stability
>  • ...
>
> in that moment. That was what I mean with rethinking might be worth
> before *I* set a flag globally. Hope it’s clearer now ;-)
>

I read your post a couple times, I could see two different ways to read
it.  I sort of addressed them both.  One way of me seeing it was based
on some other replies.  I see the way you meant it now tho.  That's the
thing about text, it's hard to put emotion etc into it.  ;-)  Unless it
is like Duncan's.  His posts are long but there isn't much room for
reading something the wrong way either.  lol 

When I did my last install for this new puter, I did mine this way.  I
do the base install and rebooted.  I poked around to make sure things
were working right and stable, network for sure.  Then I synced and
looked at the output, I always use the -a option.  What I looked for,
USE flags and what was on, what was off and what would be changing. 
Some USE flags are obvious but some require one to do a euse -i  to see what it does and sometimes a google search.  If I see
something that is not what I want, I then decide if it should be global
or for a specific set of packages and put it where it makes sense.  I
might add, that is how I do with my updates from then on.  I sync,
emerge -uvaDN world and look at what is changing and such.  If I don't
like a setting, or something is new, go set it like I want it.  How one
does that is debatable for sire.  Different tools, methods and thought
processes lead to different ways. 


>> You have choices on how to do things, pick the one that works and
>> does what you need.  It's a strong point for Gentoo.  I think USE
>> flags are one of the biggest features of Gentoo. It's not like we
>> have a fancy installer that can read our minds.  ROFL
>>
>> It is interesting to see and read how others do this tho.  It's amazing
>> sometimes how many different ways the same thing can be managed and
>> still work.  I'm not sure any other distro can do that, not that I used
>> others in a long time.
>
> That’s why Gentoo is often regarded as the freedom of choice. I love
> it to think for myself and not only consume what other OSes provides
> or not provides. Therefore (besides the USE flag feature) and because
> almost everything we feed our machines with, is plain text, we have
> the ability for creating ebuilds, overlays, patches. That’s so
> exciting even it may be hard sometimes, to learn all those stuff and
> stay up to date with it.
>


I admit, I leave most of it to the devs.  I'm not a coder or even a
script kid.  Heck, setting up a cron job requires google and some
reading.  I started using Gentoo back in 2003 and the old 1.4 days.  It
was interesting back then for sure.  Heck, portage and friends has come
a very long ways since then.  Blockers and such handle what used to be
huge problems when upgrading.  Add in that age is making other things I
have to do take longer, not to mention health issues, I just don't have
time to dig to deep. 

Gentoo certainly has choice.  If one really wants to control every
single thing there is, USE="-* " will get a person
there in a hurry.  If one doesn't want control, just something that
works, pick a good profile and go for it.  For some, that is all that is
needed. 

Gentoo has hiccups at times and some things worry me but generally, good
options are available. 

Dale

:-)  :-) 

Re: [gentoo-user] upgrading 1-year old system

[thelma]

On 02/05/2017 12:52 PM, the...@sys-concept.com wrote:
> 
> On 02/04/2017 03:20 AM, Neil Bothwick wrote:
>> On Sat, 4 Feb 2017 00:47:24 -0700, the...@sys-concept.com wrote:
>>
>>> !!! existing preserved libs:
>> package: sys-libs/ncurses-5.9-r5  
>>>  *  - /usr/lib64/libpanelw.so.5
>>>  *  - /usr/lib64/libpanelw.so.5.9
>>>  *  used
>>> by 
>>> /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/_curses_panel.so
>>> (app-office/openoffice-bin-4.1.2)
>>>  *  - /lib64/libncursesw.so.5
>>>  *  - /lib64/libncursesw.so.5.9
>>>  *  used
>>> by 
>>> /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/_curses.so
>>> (app-office/openoffice-bin-4.1.2)
>>>  *  used
>>> by 
>>> /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/_curses_panel.so
>>> (app-office/openoffice-bin-4.1.2)
>>>  *  used
>>> by 
>>> /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/readline.so
>>> (app-office/openoffice-bin-4.1.2) Use emerge @preserved-rebuild to
>>> rebuild packages using these libraries
>>>
>>> Every time I run: "emerge @preserved-rebuild" it keeps rebuilding
>>> OpenOffice and displays that message. I don't have any more on my
>>> system "sys-libs/ncurses-5.9-r5"
>>
>> It's not rebuilding anything, you're using a -bin package, it's simply
>> unpacking and installing the same files each time.
>>
>>> system is only showing: sys-libs/ncurses-6.0-r1
>>
>> Yes, but the files you have installed were built against an older
>> ncurses. Libreoffice-bin is more up to date, so try either that or
>> openoffice.
>>
>>
> The above mostly like is nothing to worry about, it must have something
> to do with openoffice-bin.
> 
> But I have three blockers and don't know how to handle it on my other
> old working system:
> 
> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking sys-fs/eudev-3.1.5)
> [blocks B ] media-libs/jpeg:0 ("media-libs/jpeg:0" is blocking
> media-libs/libjpeg-turbo-1.5.0)
> [blocks B ] media-libs/libjpeg-turbo:0 ("media-libs/libjpeg-turbo:0"
> is blocking media-libs/jpeg-8d-r1)
> 
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
> 
>   (media-libs/jpeg-8d-r1:0/0::gentoo, installed) pulled in by
> 
>> =media-libs/jpeg-8d-r1:0[static-libs?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
> (>=media-libs/jpeg-8d-r1:0[abi_x86_32(-),abi_x86_64(-)]) required by
> (virtual/jpeg-0-r2:0/0::gentoo, ebuild scheduled for merge)
> 
>   (media-libs/libjpeg-turbo-1.5.0:0/0::gentoo, ebuild scheduled for
> merge) pulled in by
> 
>> =media-libs/libjpeg-turbo-1.3.0-r3:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
> (>=media-libs/libjpeg-turbo-1.3.0-r3:0[abi_x86_64(-)]) required by
> (virtual/jpeg-62:62/62::gentoo, ebuild scheduled for merge)
> media-libs/libjpeg-turbo required by
> (net-misc/nxclient-3.5.0.7:0/0::nxclient, installed)
> 
>   (sys-fs/eudev-3.1.5:0/0::gentoo, installed) pulled in by
> sys-fs/eudev required by @selected
> >=sys-fs/eudev-1.3 required by (virtual/udev-215:0/0::gentoo, installed)
> 
>   (sys-fs/udev-225-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by
> 
>> =sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
> (>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
> (virtual/libudev-215-r1:0/1::gentoo, ebuild scheduled for merge)
> 
> sys-fs/udev is not installed
> 
> I only have sys-fs/udev-init-scripts
> 
> sys-fs/eudev-3.1.5 is installed
> 
> So why system is complaining?
> I remove "udev" from make.conf as well
> 
> USE="gnome -qt4 -hal -arts -berkdb X qtk -qt3 -kde dvd alsa cdr cups
> apache2 ssl foomaticdb ppds mysql -acl \
> java tiff png usb scanner gimp gimpprint cgi fam nptl truetype kpathsea
> type1 opengl tetex spell consolekit dbus policykit -systemd"
> 
> Same thing with jpeg, I have: media-libs/jpeg-8d-r1 installed
> So why is it complaining?

I think the solution is to unmerge:
sys-fs/eudev-3.1.5
media-libs/jpeg-8d-r1

and let the system do the magic :-/

--
Thelma

Re: [gentoo-user] New Installation

[Floyd Anderson]

On Sun, 05 Feb 12:00:15 -0500
Rich Freeman  wrote:

On Sun, Feb 5, 2017 at 11:16 AM, Floyd Anderson  wrote:


That’s why Gentoo is often regarded as the freedom of choice.


This includes the freedom to shoot yourself in the foot.


He, nice allegory. Oh, and yes that’s what I like — you can but it 
doesn’t have to be inevitable done. Sometimes it’s necessary to 
hopefully learn something. Kids may believing you only *after* they 
touched the hot plate. Long ago, I couldn’t believe a Linux is able to 
destroy itself — until a mentor shows me.



I suggest that new users consider going with the defaults except when
they have a reason not to.

Sure, we can all pass around our make.conf files, and people can just
blindly copy what we're using.  In a sense this is also stick with the
"defaults" - just somebody else's choice of defaults.


That remember me when I start using SciTE with Lua, Vim and Mutt. I saw 
myself in front of tons of documentations and user experiences and I was 
unable to wait for results. Copying just any stuff from a public .config 
file repo without any clue what those things really do isn’t meaningful. 
Someone would still stay at the point as before and when things gets 
broken, frustration arise.



The difference is that if you don't do this then you're getting the
defaults the maintainer thought best, and the settings that get the
widest extent of testing.  If you run into a problem, you're probably
close to the upstream configuration, which means both upstream and the
maintainer are probably going to be willing to lend you a hand.
You're also closer to the settings used by other distros, which means
their own documentation will help you.

Stick with the profile defaults to start.  By all means tweak
something if you have a reason to, but make these conscious informed
decisions.  Keep things simple.


This was my intention (as the result of earlier experiences) when Gentoo 
comes into my life over two years ago. The only thing that bothers me 
down to the present day, I cannot get hardware acceleration to work with 
my GPU (Radeon HD 7870 XT). I’ve tested a lot USE flags, switched from 
stable to bleeding edge and back. Now run on testing (mixed with a 
stable toolchain and able to get free from a broken system by an 
intermediate chroot) and hoping mesa from Git, Open Source AMDGPU and 
kernel >=4.9 have pity with me someday.



When you start out with a very complex USE configuration on a distro
you're new to, then you're going to struggle a lot to deal with the
resulting issues.

In terms of profiles themselves, hardened isn't the friendliest place
to start.  It tends to get used in server environments, and I suspect
very few run a desktop environment in a hardened environment.  I'd
suggest chatting with others who run hardened to understand its
limitations.  I've been running Gentoo for a very long time now and I
wouldn't expect to do a hardened desktop install and get through it
without a bit of troubleshooting.


Well, this hardened stuff looks interesting to me — at least when I 
protect my browser profile — but I can wait opening those magic box.



Thank you for your suggestions and the kindly response. It should not be 
locked up in a subthread. ;-)


--
Best regards,
Floyd Anderson

Re: [gentoo-user] upgrading 1-year old system

[thelma]

On 02/04/2017 03:20 AM, Neil Bothwick wrote:
> On Sat, 4 Feb 2017 00:47:24 -0700, the...@sys-concept.com wrote:
> 
>> !!! existing preserved libs:
> package: sys-libs/ncurses-5.9-r5  
>>  *  - /usr/lib64/libpanelw.so.5
>>  *  - /usr/lib64/libpanelw.so.5.9
>>  *  used
>> by 
>> /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/_curses_panel.so
>> (app-office/openoffice-bin-4.1.2)
>>  *  - /lib64/libncursesw.so.5
>>  *  - /lib64/libncursesw.so.5.9
>>  *  used
>> by /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/_curses.so
>> (app-office/openoffice-bin-4.1.2)
>>  *  used
>> by 
>> /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/_curses_panel.so
>> (app-office/openoffice-bin-4.1.2)
>>  *  used
>> by 
>> /usr/lib64/openoffice/program/python-core-2.7.6/lib/lib-dynload/readline.so
>> (app-office/openoffice-bin-4.1.2) Use emerge @preserved-rebuild to
>> rebuild packages using these libraries
>>
>> Every time I run: "emerge @preserved-rebuild" it keeps rebuilding
>> OpenOffice and displays that message. I don't have any more on my
>> system "sys-libs/ncurses-5.9-r5"
> 
> It's not rebuilding anything, you're using a -bin package, it's simply
> unpacking and installing the same files each time.
> 
>> system is only showing: sys-libs/ncurses-6.0-r1
> 
> Yes, but the files you have installed were built against an older
> ncurses. Libreoffice-bin is more up to date, so try either that or
> openoffice.
> 
> 
The above mostly like is nothing to worry about, it must have something
to do with openoffice-bin.

But I have three blockers and don't know how to handle it on my other
old working system:

[blocks B ] sys-fs/udev ("sys-fs/udev" is blocking sys-fs/eudev-3.1.5)
[blocks B ] media-libs/jpeg:0 ("media-libs/jpeg:0" is blocking
media-libs/libjpeg-turbo-1.5.0)
[blocks B ] media-libs/libjpeg-turbo:0 ("media-libs/libjpeg-turbo:0"
is blocking media-libs/jpeg-8d-r1)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (media-libs/jpeg-8d-r1:0/0::gentoo, installed) pulled in by

>=media-libs/jpeg-8d-r1:0[static-libs?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
(>=media-libs/jpeg-8d-r1:0[abi_x86_32(-),abi_x86_64(-)]) required by
(virtual/jpeg-0-r2:0/0::gentoo, ebuild scheduled for merge)

  (media-libs/libjpeg-turbo-1.5.0:0/0::gentoo, ebuild scheduled for
merge) pulled in by

>=media-libs/libjpeg-turbo-1.3.0-r3:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
(>=media-libs/libjpeg-turbo-1.3.0-r3:0[abi_x86_64(-)]) required by
(virtual/jpeg-62:62/62::gentoo, ebuild scheduled for merge)
media-libs/libjpeg-turbo required by
(net-misc/nxclient-3.5.0.7:0/0::nxclient, installed)

  (sys-fs/eudev-3.1.5:0/0::gentoo, installed) pulled in by
sys-fs/eudev required by @selected
>=sys-fs/eudev-1.3 required by (virtual/udev-215:0/0::gentoo, installed)

  (sys-fs/udev-225-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by

>=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
(>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
(virtual/libudev-215-r1:0/1::gentoo, ebuild scheduled for merge)

sys-fs/udev is not installed

I only have sys-fs/udev-init-scripts

sys-fs/eudev-3.1.5 is installed

So why system is complaining?
I remove "udev" from make.conf as well

USE="gnome -qt4 -hal -arts -berkdb X qtk -qt3 -kde dvd alsa cdr cups
apache2 ssl foomaticdb ppds mysql -acl \
java tiff png usb scanner gimp gimpprint cgi fam nptl truetype kpathsea
type1 opengl tetex spell consolekit dbus policykit -systemd"

Same thing with jpeg, I have: media-libs/jpeg-8d-r1 installed
So why is it complaining?

--
Thelma

[gentoo-user] Missing python binding?

[Daniel Frey]

I am trying magick-rotation to see if it will work on my Surface Pro 3
(they tested in on a Surface Pro 2 and it was working, unsure if the
hardware is different.)

However: I get this:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python2.7/magick-rotation", line 20, in

from gui_gtk import *
ImportError: No module named gui_gtk


>From searching this points to pygtk, which is installed:

$ equery list pygtk
 * Searching for pygtk ...
[IP-] [  ] dev-python/pygtk-2.24.0-r4:2

I've also tried rebuilding it, still no worky.

Anyone know how to solve this?

Dan

Re: [gentoo-user] New Installation

[Neil Bothwick]

On Sun, 5 Feb 2017 12:07:10 -0500, Rich Freeman wrote:

> I'll be honest and admit that I probably should give my own USE flags
> another look.  Most of them probably pre-date the existance of USE
> defaults when a lot more tweaking tended to be needed to get things
> working right.

I recently transferred my hard drives to a new box but added an NVMe
drive for the OS. I tried leaving out most of my previous USE flags, nly
adding them when I saw the need. I surprised by how many of them I didn't
need or want any more


-- 
Neil Bothwick

Celery is not food. It is a member of the plywood family.


pgpkiG5m3DRbB.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] New Installation

[Neil Bothwick]

On Sun, 5 Feb 2017 09:53:42 -0700, the...@sys-concept.com wrote:

> Thank you all, yes good advice. I have removed most of the entries from
> the "USE=" what is left (and I'm not even sure I need them).
> 
> USE="-qt4 -kde -gnome -arts -berkdb -acl X gtk alsa cups apache2 ssl
> udev tiff png usb scanner cgi nptl type1 -systemd"

kde qt? and gnome are unset in the default and desktop profiles. arts
hasn't been around for many years, it was part of KDE3.

> I'll let the portage handle it, I use XFCE for desktop.

Then set the standard desktop profile.


-- 
Neil Bothwick

Two rights don't make a wrong, they make an airplane.


pgpUufOmhMRT3.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Bad luck with new installation: Compilation issues (eudev)

[Meino . Cramer]

Hi Alexander,

thanks for the link!

Had found the culprit myself and fixed it with
a user patch...

Cheers
Meino



Alexander Openkowski  [17-02-05 18:28]:
> Have you seen this thread in the forums? It looks like your problem:
> 
> https://forums.gentoo.org/viewtopic-t-1057500-view-previous.html?sid=9c8b57325eef824a0748ec4ca94ac8b1
> 
> Found via a quick google search. Keywords: "eudev 3.2.1 error gentoo".
> No offense, really. But you do not need to wait for an answer if you
> search for yourself. :-)
> 
> On 02/05/2017 03:08 PM, meino.cra...@gmx.de wrote:
> > Hi,
> >
> > I am still compiling my new root...
> >
> > After some of the rebuild/sinc/revdep/ cycles I got this while trying
> > to update sys-fs/eudev
> >
> > (ACCEPT_KEYWORDS is set to ~amd64 globally right before any
> > compilations)
> >
> > /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev/udev-builtin-keyboard.c:31:26:
> >  note: previous declaration of 'keyboard_lookup_key' was here
> >  static const struct key *keyboard_lookup_key(const char *str, unsigned 
> > len);
> >   ^
> > x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. 
> > -I/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev -I../..  
> > -include ../../config.h -DROOTPREFIX=\"\" 
> > -DUDEV_HWDB_DIR=\"/etc/udev/hwdb.d\" -DUDEV_HWDB_BIN=\"/etc/udev/hwdb.bin\" 
> > -DUDEV_CONF_DIR=\"/etc/udev\" -DUDEV_ROOT_RUN=\"/run\" 
> > -DUDEV_RULES_DIR=\"/lib/udev/rules.d\" -DUDEV_LIBEXEC_DIR=\"/lib/udev\" 
> > -DUDEV_VERSION=\"220\" -I 
> > /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/shared -I 
> > /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/libudev -I 
> > ../../src/udev   -march=native -msse -msse2 -msse3 -O2 -pipe -c -o 
> > udevadm-monitor.o 
> > /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev/udevadm-monitor.c
> > make[4]: *** [Makefile:813: libudev_core_la-udev-builtin-keyboard.lo] Error 
> > 1
> > make[4]: *** Waiting for unfinished jobs
> > make[4]: Leaving directory 
> > '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src/udev'
> > make[3]: *** [Makefile:500: all] Error 2
> > make[3]: Leaving directory 
> > '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src/udev'
> > make[2]: *** [Makefile:394: all-recursive] Error 1
> > make[2]: Leaving directory 
> > '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src'
> > make[1]: *** [Makefile:446: all-recursive] Error 1
> > make[1]: Leaving directory 
> > '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64'
> > make: *** [Makefile:378: all] Error 2
> >  * ERROR: sys-fs/eudev-3.2.1::gentoo failed (compile phase):
> >  *   emake failed
> >  * 
> >  * If you need support, post the output of `emerge --info 
> > '=sys-fs/eudev-3.2.1::gentoo'`,
> >  * the complete build log and the output of `emerge -pqv 
> > '=sys-fs/eudev-3.2.1::gentoo'`.
> >  * The complete build log is located at 
> > '/var/tmp/portage/sys-fs/eudev-3.2.1/temp/build.log'.
> >  * The ebuild environment file is located at 
> > '/var/tmp/portage/sys-fs/eudev-3.2.1/temp/environment'.
> >  * Working directory: 
> > '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64'
> >  * S: '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1'
> >
>  Failed to emerge sys-fs/eudev-3.2.1, Log file:
> >
> > eix eudev shows:
> > solfire ~ # eix sys-fs/eudev
> > [U] sys-fs/eudev
> >  Available versions:  1.9-r2 1.10-r2 3.1.2 3.1.5 (~)3.2 (~)3.2.1 
> > **4. ** {+blkid doc efi gudev +hwdb introspection +keymap +kmod 
> > +modutils +openrc (+)rule-generator selinux smack static-libs test 
> > ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"}
> >  Installed versions:  3.1.5(05:33:42 02/02/17)(hwdb kmod -introspection 
> > -rule-generator -selinux -static-libs -test ABI_MIPS="-n32 -n64 -o32" 
> > ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32")
> >  Homepage:https://github.com/gentoo/eudev
> >  Description: Linux dynamic and persistent device naming 
> > support (aka userspace devfs)
> >
> >
> > I dont want to poison the mailing list with long logs in case of
> > someone knows what's going on here...but if wanted, I will post them
> > of course... :)
> >
> > Cheers
> > Meino
> >
> >
> >
> >
> >
> 
> 

Re: [gentoo-user] Bad luck with new installation: Compilation issues (eudev)

[Alexander Openkowski]

Have you seen this thread in the forums? It looks like your problem:

https://forums.gentoo.org/viewtopic-t-1057500-view-previous.html?sid=9c8b57325eef824a0748ec4ca94ac8b1

Found via a quick google search. Keywords: "eudev 3.2.1 error gentoo".
No offense, really. But you do not need to wait for an answer if you
search for yourself. :-)

On 02/05/2017 03:08 PM, meino.cra...@gmx.de wrote:
> Hi,
>
> I am still compiling my new root...
>
> After some of the rebuild/sinc/revdep/ cycles I got this while trying
> to update sys-fs/eudev
>
> (ACCEPT_KEYWORDS is set to ~amd64 globally right before any
> compilations)
>
> /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev/udev-builtin-keyboard.c:31:26:
>  note: previous declaration of 'keyboard_lookup_key' was here
>  static const struct key *keyboard_lookup_key(const char *str, unsigned len);
>   ^
> x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. 
> -I/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev -I../..  
> -include ../../config.h -DROOTPREFIX=\"\" 
> -DUDEV_HWDB_DIR=\"/etc/udev/hwdb.d\" -DUDEV_HWDB_BIN=\"/etc/udev/hwdb.bin\" 
> -DUDEV_CONF_DIR=\"/etc/udev\" -DUDEV_ROOT_RUN=\"/run\" 
> -DUDEV_RULES_DIR=\"/lib/udev/rules.d\" -DUDEV_LIBEXEC_DIR=\"/lib/udev\" 
> -DUDEV_VERSION=\"220\" -I 
> /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/shared -I 
> /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/libudev -I 
> ../../src/udev   -march=native -msse -msse2 -msse3 -O2 -pipe -c -o 
> udevadm-monitor.o 
> /var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev/udevadm-monitor.c
> make[4]: *** [Makefile:813: libudev_core_la-udev-builtin-keyboard.lo] Error 1
> make[4]: *** Waiting for unfinished jobs
> make[4]: Leaving directory 
> '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src/udev'
> make[3]: *** [Makefile:500: all] Error 2
> make[3]: Leaving directory 
> '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src/udev'
> make[2]: *** [Makefile:394: all-recursive] Error 1
> make[2]: Leaving directory 
> '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src'
> make[1]: *** [Makefile:446: all-recursive] Error 1
> make[1]: Leaving directory 
> '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64'
> make: *** [Makefile:378: all] Error 2
>  * ERROR: sys-fs/eudev-3.2.1::gentoo failed (compile phase):
>  *   emake failed
>  * 
>  * If you need support, post the output of `emerge --info 
> '=sys-fs/eudev-3.2.1::gentoo'`,
>  * the complete build log and the output of `emerge -pqv 
> '=sys-fs/eudev-3.2.1::gentoo'`.
>  * The complete build log is located at 
> '/var/tmp/portage/sys-fs/eudev-3.2.1/temp/build.log'.
>  * The ebuild environment file is located at 
> '/var/tmp/portage/sys-fs/eudev-3.2.1/temp/environment'.
>  * Working directory: 
> '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64'
>  * S: '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1'
>
 Failed to emerge sys-fs/eudev-3.2.1, Log file:
>
> eix eudev shows:
> solfire ~ # eix sys-fs/eudev
> [U] sys-fs/eudev
>  Available versions:  1.9-r2 1.10-r2 3.1.2 3.1.5 (~)3.2 (~)3.2.1 **4. 
> ** {+blkid doc efi gudev +hwdb introspection +keymap +kmod +modutils 
> +openrc (+)rule-generator selinux smack static-libs test ABI_MIPS="n32 n64 
> o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"}
>  Installed versions:  3.1.5(05:33:42 02/02/17)(hwdb kmod -introspection 
> -rule-generator -selinux -static-libs -test ABI_MIPS="-n32 -n64 -o32" 
> ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32")
>  Homepage:https://github.com/gentoo/eudev
>  Description: Linux dynamic and persistent device naming support 
> (aka userspace devfs)
>
>
> I dont want to poison the mailing list with long logs in case of
> someone knows what's going on here...but if wanted, I will post them
> of course... :)
>
> Cheers
> Meino
>
>
>
>
>

Re: [gentoo-user] New Installation

[Rich Freeman]

On Sun, Feb 5, 2017 at 11:53 AM,   wrote:
>
> Thank you all, yes good advice. I have removed most of the entries from
> the "USE=" what is left (and I'm not even sure I need them).

This is a good way to get started.  Get your system working, then
start playing with it.  At least you can browse the web while things
build then.  :)

>
> USE="... -berkdb

I'd question this at a global level.  I'm not saying it will
definitely cause issues, but the selection of a storage backend seems
like the sort of thing you'd want to make per-package and not
globally, unless you have a specific aversion to berkdb.  If you turn
this off on some packages they might fail to run until you set up a
mysql database or something for them, and that is probably overkill in
some cases.  The maintainer's default choice may be more appropriate,
again unless you have a specific concern with it.

This is the sort of setting that can make perfect sense in package.use.

I'll be honest and admit that I probably should give my own USE flags
another look.  Most of them probably pre-date the existance of USE
defaults when a lot more tweaking tended to be needed to get things
working right.

Believe it or not, this is probably the easiest it has ever been for
somebody new to Gentoo.  :)  Back when I installed we were still
recommending doing stage1 installs, and that was on far inferior
hardward.  Just imagine sitting in a chroot for a day or two before
you can even get your box to boot.  Oh, and no livecds either, if you
didn't have another computer handy (which was more likely to be the
case back then - no smartphones/etc), you made do with links.  I think
we at least made its home page the handbook.

-- 
Rich

Re: [gentoo-user] Re: Copying USB->USB: sync after every file

[Frank Steinmetzger]

On Sun, Feb 05, 2017 at 12:20:25PM +0100, Frank Steinmetzger wrote:

> Having no time over the week, I finally got the new install running. But
> before I was set back by not being able to log in to Plasma with lightdm.
> Only sddm works.

I really need to lower my sentences’ complexity. That should be “But -- just 
like
before -- I was set back by not being able to log in to Plasma with lightdm.”

-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any social network.

No, you *can’t call 999 now.  I’m downloading my mail.


signature.asc
Description: Digital signature

Re: [gentoo-user] New Installation

[Rich Freeman]

On Sun, Feb 5, 2017 at 11:16 AM, Floyd Anderson  wrote:
>
> That’s why Gentoo is often regarded as the freedom of choice.

This includes the freedom to shoot yourself in the foot.

I suggest that new users consider going with the defaults except when
they have a reason not to.

Sure, we can all pass around our make.conf files, and people can just
blindly copy what we're using.  In a sense this is also stick with the
"defaults" - just somebody else's choice of defaults.

The difference is that if you don't do this then you're getting the
defaults the maintainer thought best, and the settings that get the
widest extent of testing.  If you run into a problem, you're probably
close to the upstream configuration, which means both upstream and the
maintainer are probably going to be willing to lend you a hand.
You're also closer to the settings used by other distros, which means
their own documentation will help you.

Stick with the profile defaults to start.  By all means tweak
something if you have a reason to, but make these conscious informed
decisions.  Keep things simple.

When you start out with a very complex USE configuration on a distro
you're new to, then you're going to struggle a lot to deal with the
resulting issues.

In terms of profiles themselves, hardened isn't the friendliest place
to start.  It tends to get used in server environments, and I suspect
very few run a desktop environment in a hardened environment.  I'd
suggest chatting with others who run hardened to understand its
limitations.  I've been running Gentoo for a very long time now and I
wouldn't expect to do a hardened desktop install and get through it
without a bit of troubleshooting.

-- 
Rich

Re: [gentoo-user] New Installation

[thelma]

On 02/05/2017 02:23 AM, J. Roeleveld wrote:
> On Saturday, February 4, 2017 11:36:56 PM CET the...@sys-concept.com wrote:
> 
> (longer reply)
> 
>>
>> I change in make.conf to:
>> USE="bindist"
>>
>> and I was able to install basic system correctly, network is working and I
>> can proceed with castomazation but my next question: What is the correct
>> way to configure "USE=" in make.conf?
>>
>> When I use a below: (copied from my other systems):
>>
>> USE="-qt4 -kde -gnome -arts -berkdb -acl X gtk alsa cups apache2 ssl
>> foomaticdb truetype kpathsea ppds mysql udev tiff png usb scanner gimp
>> gimpprint cgi fam nptl type1 opengl tetexspell consolkit dbus pam policykit
>> jpeg lock session startup-notification thunar cleartype corefonts -systemd
>> -DOPENSSL_NO_HEARTBEATS abi_x86_32"
>>
>> PS. I think "dbus" is no longer used, isn't it?
> 
> I have dbus installed, so the package still exists. If it is a valid 
> USE-flag, 
> I don't know.
> 
> In your list, I see a few I have never used. Most of them, I would personally 
> only set for those packages where I want them to apply, but that is a 
> personal 
> decision.
> 
> My main concerns with your list are:
> # -DOPENSSL_NO_HEARTBEATS
> This seems more like something that should be added as a compiler-flag for 1 
> package or something in an apache config file.
> 
> # abi_x86_32
> I am assuming you want packages to also be build for 32-bit.
> If that is the case, I would set the following in your make.conf file:
> # ABI_X86="64 32"
> and remove this entry from your USE-list.
> 
> # consolkit
> I think this should be "consolekit" as that one does exist.
> 
>> I get a log of blockers and my file "package.use" starting to look like
>> trash can with entries like:
>>
>> # required by x11-libs/libxcb-1.12::gentoo
>> # required by x11-apps/xwininfo-1.1.3::gentoo
>> # required by x11-misc/xscreensaver-5.36::gentoo
>> # required by xfce-base/xfce4-session-4.12.1-r1::gentoo[xscreensaver]
>> # required by xfce-base/xfce4-meta-4.12::gentoo
>> # required by xfce-base/xfce4-meta (argument)
>>
>>> =x11-libs/libXau-1.0.8 abi_x86_32
> 
> This is related to the above comment about your abi... useflag.
> 
>> # required by x11-libs/libxcb-1.12::gentoo
>> # required by x11-apps/xwininfo-1.1.3::gentoo
>> # required by x11-misc/xscreensaver-5.36::gentoo
>> # required by xfce-base/xfce4-session-4.12.1-r1::gentoo[xscreensaver]
>> # required by xfce-base/xfce4-meta-4.12::gentoo
>> # required by xfce-base/xfce4-meta (argument)
>>
>>> =dev-libs/libpthread-stubs-0.3-r1 abi_x86_32
> 
> Same
> 
>> If I try to use my USE="-qt4 ... etc" and try to emerge:
>> emerge --ask xfce-base/xfce4-meta
>>
>> I get tones of blockers and problem solving eg.:
>>
>> [blocks B  ] dev-util/pkgconf[pkg-config]
>> ("dev-util/pkgconf[pkg-config]" is blocking dev-util/pkgconfig-0.28-r2)
>> [blocks B  ] media-libs/libjpeg-turbo:0 ("media-libs/libjpeg-turbo:0"
>> is blocking media-libs/jpeg-8d-r1) [blocks B  ] media-libs/jpeg:0
>> ("media-libs/jpeg:0" is blocking media-libs/libjpeg-turbo-1.5.0) [blocks B 
>> ] sys-fs/udev ("sys-fs/udev" is blocking sys-fs/eudev-3.1.5) [blocks B 
>> ] dev-util/pkgconfig ("dev-util/pkgconfig" is blocking
>> dev-util/pkgconf-0.9.12)
>>
>>  * Error: The above package list contains packages which cannot be
>>  * installed at the same time on the same system.
>>
>>   (dev-util/pkgconf-0.9.12:0/0::gentoo, ebuild scheduled for merge) pulled
>> in by
>> >=dev-util/pkgconf-0.9.3-r1[pkg-config,abi_x86_32(-)?,abi_x86_64(-)?,abi
>> >_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc
>> >_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>> >(>=dev-util/pkgconf-0.9.3-r1[pkg-config,abi_x86_32(-),abi_x86_64(-)])
>> >required by (virtual/pkgconfig-0-r1:0/0::gentoo, ebuild scheduled for
>> >merge)
>>   (sys-fs/eudev-3.1.5:0/0::gentoo, ebuild scheduled for merge) pulled in by
>>
>> >=sys-fs/eudev-1.3 required by (virtual/udev-215:0/0::gentoo, installed)
>> >=sys-fs/eudev-1.3:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi
>> >_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_
>> >64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
>> >(>=sys-fs/eudev-1.3:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
>> >(virtual/libudev-215-r1:0/1::gentoo, ebuild scheduled for merge)
>>   (sys-fs/udev-225-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by
>>
>> >=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,a
>> >bi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_pp
>> >c_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
>> >(>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
>> >(virtual/libudev-215-r1:0/1::gentoo, ebuild scheduled for merge)
>> >=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo,
>> >installed)
>>   (dev-util/pkgconfig-0.28-r2:0/0::gentoo, ebuild scheduled for merge)
>>

Re: [gentoo-user] New Installation

[Floyd Anderson]

On Sun, 05 Feb 05:05:56 -0600
Dale  wrote:
The point of my post was not for a specific flag.  I just picked a flag 
that has been around for a long time and pretty much everyone 
recognizes what it is for.


[…]

I might add, there are flags that we can't change.  Those are set by
upstream or the devs.  My post wasn't about that either.  It was all
about managing options that we can change..


I think there is an unfortunate misunderstanding and I may have to be 
more clear. I also just picked the threads-flag example as what it is, 
an example — not as a specific advise. My intention was to demonstrate 
my thoughts when I read the post from the dev list.


Basically I handle my USE flags similar as you do and had described in 
your former post. What I always want goes to make.conf (trying to keep 
it according to less is more) and specific flags lives in package.use.


When I read the post from Rich, I remember that I have the mentioned 
‘threads’ flag globally set. Some time ago I put it in, it works and 
nearly no thoughts were wasted since then. I didn’t care about:

 • pulling in heavyweight dependencies
 • package maintainers set a flag off by default for stability
 • ...

in that moment. That was what I mean with rethinking might be worth 
before *I* set a flag globally. Hope it’s clearer now ;-)


You have choices on how to do things, pick the one that works and does 
what you need.  It's a strong point for Gentoo.  I think USE flags are 
one of the biggest features of Gentoo. It's not like we have a fancy 
installer that can read our minds.  ROFL


It is interesting to see and read how others do this tho.  It's amazing
sometimes how many different ways the same thing can be managed and
still work.  I'm not sure any other distro can do that, not that I used
others in a long time.


That’s why Gentoo is often regarded as the freedom of choice. I love it 
to think for myself and not only consume what other OSes provides or not 
provides. Therefore (besides the USE flag feature) and because almost 
everything we feed our machines with, is plain text, we have the ability 
for creating ebuilds, overlays, patches. That’s so exciting even it may 
be hard sometimes, to learn all those stuff and stay up to date with it.


--
Best regards,
Floyd Anderson

Re: [gentoo-user] Can't get X running in Kernel 4.4.26. [Solved]

[Mick]

On Sunday 05 Feb 2017 13:08:18 Alan Mackenzie wrote:
> On Thu, Dec 29, 2016 at 14:52:08 +, J. Roeleveld wrote:
> > On December 29, 2016 3:24:27 PM GMT+01:00, Alan Mackenzie  
wrote:
> > >Hi, Gentoo.
> > >
> > >I'm having trouble with my kernel 4.4.26.  It will do everything
> > >expected of it except for running X Windows.
> > >
> > >I've checked I've got the kernel configuration set up as described in
> > >the gentoo wiki documents, unless I've overlooked something.
> > >
> > >What happens is that I run "startx", and a little while later, the X
> > >server reports that no screens are found.
> > >
> > >More precisely, the following appears in Xorg.0.log:
> > >KAVERI, KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
> > >HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
> > >
> > >[47.952] (II) modesetting: Driver for Modesetting Kernel Drivers:
> > >kms
> > >[47.952] (--) using VT number 7
> > >
> > >[47.963] (II) [KMS] Kernel modesetting enabled.
> > >[47.963] (WW) Falling back to old probe method for modesetting
> > >[47.963] (EE) No devices detected.
> > >[47.963] (EE)
> > >Fatal server error:
> > >[47.963] (EE) no screens found(EE)
> > >[47.963] (EE)
> > >Please consult the The X.Org Foundation support
> > >
> > > at http://wiki.x.org
> > > 
> > > for help.
> > >
> > >[47.963] (EE) Please also check the log file at
> > >"/var/log/Xorg.0.log" for additional information.
> > >[47.963] (EE)
> > >
> > >Note the "No devices detected".
> > >
> > >
> > >The corresponding piece of the working Xorg.0.log in my older kernel
> > >
> > >is:
> > >KAVERI, KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
> > >HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
> > >
> > >[   188.705] (II) modesetting: Driver for Modesetting Kernel Drivers:
> > >kms
> > >[   188.705] (--) using VT number 7
> > >
> > >[   188.713] (II) [KMS] Kernel modesetting enabled.
> > >[   188.713] (WW) Falling back to old probe method for modesetting
> > >[   188.713] (WW) VGA arbiter: cannot open kernel arbiter, no
> > >multi-card support
> > >[   188.713] (II) RADEON(0): Creating default Display subsection in
> > >Screen section
> > >
> > >"Default Screen Section" for depth/fbbpp 24/32
> > >
> > >[   188.713] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
> > >[   188.713] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes
> > >(32 bpp pixmaps)
> > >[   188.713] (==) RADEON(0): Default visual is TrueColor
> > >[   188.713] (==) RADEON(0): RGB weight 888
> > >[   188.713] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
> > >[   188.713] (--) RADEON(0): Chipset: "ATI Radeon HD 4550" (ChipID =
> > >0x9540)
> > >
> > >
> > >Needless to say, the kernel version is the sole difference between the
> > >non-working 4.4.26 and the working 4.0.5.
> > >
> > >Would somebody please help me track down this problem.  Thanks!
> > 
> > I ended up skipping 4.4 kernels as I had problems as well.
> > Not with X, but hibernate wasn't working.
> > 4.6 and 4.8 kernels do seem to work better.
> > 
> > You could try a more recent one as well.
> 
> I found the problem whilst debugging the same symptoms in kernel 4.9.6.
> I'd disabled "Enable PCI quirk workarounds" in General Setup.  After
> reenabling it, my X functions again.  Don't ask me what brought me to
> suspect this setting.
> 
> I mean, my PC is "relatively recent" (2009).  PCI, even PCIe, is as old
> as the hills.  Surely they got the quirks out of the chipsets by 2009?
> Apparently not!
> 
> > --
> > Joost

Thanks for letting us know.  I would have *never* thought of this setting 
causing a problem with X ...  O_O

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Bad luck with new installation: Compilation issues (eudev)

[Meino . Cramer]

Hi,

I am still compiling my new root...

After some of the rebuild/sinc/revdep/ cycles I got this while trying
to update sys-fs/eudev

(ACCEPT_KEYWORDS is set to ~amd64 globally right before any
compilations)

/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev/udev-builtin-keyboard.c:31:26:
 note: previous declaration of 'keyboard_lookup_key' was here
 static const struct key *keyboard_lookup_key(const char *str, unsigned len);
  ^
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. 
-I/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev -I../..  
-include ../../config.h -DROOTPREFIX=\"\" -DUDEV_HWDB_DIR=\"/etc/udev/hwdb.d\" 
-DUDEV_HWDB_BIN=\"/etc/udev/hwdb.bin\" -DUDEV_CONF_DIR=\"/etc/udev\" 
-DUDEV_ROOT_RUN=\"/run\" -DUDEV_RULES_DIR=\"/lib/udev/rules.d\" 
-DUDEV_LIBEXEC_DIR=\"/lib/udev\" -DUDEV_VERSION=\"220\" -I 
/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/shared -I 
/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/libudev -I 
../../src/udev   -march=native -msse -msse2 -msse3 -O2 -pipe -c -o 
udevadm-monitor.o 
/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1/src/udev/udevadm-monitor.c
make[4]: *** [Makefile:813: libudev_core_la-udev-builtin-keyboard.lo] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory 
'/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src/udev'
make[3]: *** [Makefile:500: all] Error 2
make[3]: Leaving directory 
'/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src/udev'
make[2]: *** [Makefile:394: all-recursive] Error 1
make[2]: Leaving directory 
'/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64/src'
make[1]: *** [Makefile:446: all-recursive] Error 1
make[1]: Leaving directory 
'/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64'
make: *** [Makefile:378: all] Error 2
 * ERROR: sys-fs/eudev-3.2.1::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info 
'=sys-fs/eudev-3.2.1::gentoo'`,
 * the complete build log and the output of `emerge -pqv 
'=sys-fs/eudev-3.2.1::gentoo'`.
 * The complete build log is located at 
'/var/tmp/portage/sys-fs/eudev-3.2.1/temp/build.log'.
 * The ebuild environment file is located at 
'/var/tmp/portage/sys-fs/eudev-3.2.1/temp/environment'.
 * Working directory: 
'/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1-abi_x86_64.amd64'
 * S: '/var/tmp/portage/sys-fs/eudev-3.2.1/work/eudev-3.2.1'

>>> Failed to emerge sys-fs/eudev-3.2.1, Log file:


eix eudev shows:
solfire ~ # eix sys-fs/eudev
[U] sys-fs/eudev
 Available versions:  1.9-r2 1.10-r2 3.1.2 3.1.5 (~)3.2 (~)3.2.1 **4. 
** {+blkid doc efi gudev +hwdb introspection +keymap +kmod +modutils 
+openrc (+)rule-generator selinux smack static-libs test ABI_MIPS="n32 n64 o32" 
ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"}
 Installed versions:  3.1.5(05:33:42 02/02/17)(hwdb kmod -introspection 
-rule-generator -selinux -static-libs -test ABI_MIPS="-n32 -n64 -o32" 
ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32")
 Homepage:https://github.com/gentoo/eudev
 Description: Linux dynamic and persistent device naming support 
(aka userspace devfs)


I dont want to poison the mailing list with long logs in case of
someone knows what's going on here...but if wanted, I will post them
of course... :)

Cheers
Meino

Re: [gentoo-user] Can't get X running in Kernel 4.4.26. [Solved]

[Alan Mackenzie]

On Thu, Dec 29, 2016 at 14:52:08 +, J. Roeleveld wrote:
> On December 29, 2016 3:24:27 PM GMT+01:00, Alan Mackenzie  wrote:
> >Hi, Gentoo.

> >I'm having trouble with my kernel 4.4.26.  It will do everything
> >expected of it except for running X Windows.

> >I've checked I've got the kernel configuration set up as described in
> >the gentoo wiki documents, unless I've overlooked something.

> >What happens is that I run "startx", and a little while later, the X
> >server reports that no screens are found.

> >More precisely, the following appears in Xorg.0.log:

> >KAVERI, KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
> >HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
> >[47.952] (II) modesetting: Driver for Modesetting Kernel Drivers:
> >kms
> >[47.952] (--) using VT number 7

> >[47.963] (II) [KMS] Kernel modesetting enabled.
> >[47.963] (WW) Falling back to old probe method for modesetting
> >[47.963] (EE) No devices detected.
> >[47.963] (EE)
> >Fatal server error:
> >[47.963] (EE) no screens found(EE)
> >[47.963] (EE)
> >Please consult the The X.Org Foundation support
> > at http://wiki.x.org
> > for help.
> >[47.963] (EE) Please also check the log file at
> >"/var/log/Xorg.0.log" for additional information.
> >[47.963] (EE)

> >Note the "No devices detected".


> >The corresponding piece of the working Xorg.0.log in my older kernel
> >is:

> >KAVERI, KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
> >HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
> >[   188.705] (II) modesetting: Driver for Modesetting Kernel Drivers:
> >kms
> >[   188.705] (--) using VT number 7

> >[   188.713] (II) [KMS] Kernel modesetting enabled.
> >[   188.713] (WW) Falling back to old probe method for modesetting
> >[   188.713] (WW) VGA arbiter: cannot open kernel arbiter, no
> >multi-card support
> >[   188.713] (II) RADEON(0): Creating default Display subsection in
> >Screen section
> >"Default Screen Section" for depth/fbbpp 24/32
> >[   188.713] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
> >[   188.713] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes
> >(32 bpp pixmaps)
> >[   188.713] (==) RADEON(0): Default visual is TrueColor
> >[   188.713] (==) RADEON(0): RGB weight 888
> >[   188.713] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
> >[   188.713] (--) RADEON(0): Chipset: "ATI Radeon HD 4550" (ChipID =
> >0x9540)


> >Needless to say, the kernel version is the sole difference between the
> >non-working 4.4.26 and the working 4.0.5.

> >Would somebody please help me track down this problem.  Thanks!

> I ended up skipping 4.4 kernels as I had problems as well.
> Not with X, but hibernate wasn't working.
> 4.6 and 4.8 kernels do seem to work better.

> You could try a more recent one as well.

I found the problem whilst debugging the same symptoms in kernel 4.9.6.
I'd disabled "Enable PCI quirk workarounds" in General Setup.  After
reenabling it, my X functions again.  Don't ask me what brought me to
suspect this setting.

I mean, my PC is "relatively recent" (2009).  PCI, even PCIe, is as old
as the hills.  Surely they got the quirks out of the chipsets by 2009?
Apparently not!

> --
> Joost

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Re: Copying USB->USB: sync after every file

[Frank Steinmetzger]

On Mon, Jan 30, 2017 at 12:54:44AM +0100, Frank Steinmetzger wrote:
> On Sun, Jan 29, 2017 at 11:12:43PM +, Mick wrote:
> > On Sunday 29 Jan 2017 02:14:27 Frank Steinmetzger wrote:
> > > On Sat, Jan 28, 2017 at 11:56:03PM +, Mick wrote:
> > > > On Saturday 28 Jan 2017 23:55:05 Frank Steinmetzger wrote:
> > > > > Well, I created a test user, which is only member of the audio and 
> > > > > video
> > > > > groups. With that, I do get the arrow button which is also able to 
> > > > > mount
> > > > > the media. But it also gets “Access denied” when I click on the 
> > > > > Dolphin
> > > > > item. So it’s not a permission thing per se. More like a settings
> > > > > problem with my KDE (funnily enough on both my machines). *sigh*
> > > > 
> > > > Add your user to group plugdev, reboot and try again.
> > > 
> > > Adding myself to that group is one of the first things I learned and
> > > remembered from when I dived into the Gentoo world. ;-)
> > 
> > I can't recall if you confirmed you are also a member of the usb group?  If 
> > yes, then I'm running out of ideas ...
> 
> I am not part of that group (never have, methinks). So on the laptop I added
> my user to the usb group, logged out and back in, but the behaviour remained
> unchanged.
> 
> I set up a new Gentoo system on a spare HDD in a chroot. It is still
> building (thouh plasma is already done). I’ll boot it tomorrow and see what
> it does. This is my first system with KDE5 from scratch without having seen
> KDE4 (except for the PIM suite).

Having no time over the week, I finally got the new install running. But
before I was set back by not being able to log in to Plasma with lightdm.
Only sddm works.
Anyhoo, the newly installed system also has my storage media permission
problem. S it’s back to square one. :(

-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

Sorry, this signature is not available in your country.


signature.asc
Description: Digital signature

Re: [gentoo-user] nm-applet shows "?" in Gnome tool tray

[Frank Steinmetzger]

On Sun, Feb 05, 2017 at 10:42:12AM +, Mick wrote:

> Hi All,
> […]
> In addition, there is a question mark "?" displayed by the nm-applet in the
> tool tray when I have a wireless connection.  On wired connections I get the
> question mark superimposed on the wired network tool tray symbol.

I too noticed this question mark, for me it started when I upgraded NM from
1.0 to 1.4. Since that time, Network Manager doesn't autoconnect for me
anymore. I always have to select my WiFi manually after every suspend.

IIRC there was something or other about missing dbus calls in the log. I did a
downgrade right away to fix it for me. But now that I am on KDE5, 1.4 is
required. So when I wake up from suspend, I do have a question mark, then I
select my network, it connects and the question mark disappears.

frank@tp ~ LC_ALL=en eix -I networkmanager
[I] kde-frameworks/networkmanager-qt
 Available versions:  (5) 5.29.0(5/5.29) ~5.30.0(5/5.30)
   {debug teamd test}
 Installed versions:  5.29.0(5)(17:42:55 01/23/17)(-debug -teamd -test)

[I] net-misc/networkmanager
 Available versions:  [m]1.4.0-r1 (~)1.4.4 (~)1.4.4-r1 {audit bluetooth 
connection-sharing consolekit +dhclient gnutls +introspection json 
+modemmanager ncurses +nss ofono +ppp resolvconf selinux systemd teamd test 
vala +wext +wifi ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" 
ABI_X86="32 64 x32" KERNEL="linux"}
 Installed versions:  1.4.4-r1(17:39:22 01/23/17)(bluetooth consolekit 
dhclient introspection modemmanager ncurses nss ppp wext wifi -audit 
-connection-sharing -gnutls -json -ofono -resolvconf -selinux -systemd -teamd 
-test -vala ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" 
ABI_X86="64 -32 -x32" KERNEL="linux")


-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

Signatures are being revised, we apologise for any inconvenience.


signature.asc
Description: Digital signature

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Neil Bothwick]

On Sun, 05 Feb 2017 09:26:27 +, Mick wrote:

> Regarding booting off a directory, have a look at booting ISO images
> with GRUB.  I would think a similar approach should allow you to boot
> from a directory instead of an ISO image.

That's only possible because the ISO images have support for it in their
init scripts, so you're back to needing an initramfs to do it.


-- 
Neil Bothwick

Hard work has a future payoff. Laziness pays off now.


pgpQ2kLJDBBal.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] New Installation

[Dale]

Floyd Anderson wrote:
> On Sun, 05 Feb 01:44:30 -0600
> Dale  wrote:
>> the...@sys-concept.com wrote:
>>>
>>> I change in make.conf to:
>>> USE="bindist"
>>>
>>> and I was able to install basic system correctly, network is working
>>> and I can proceed with castomazation but
>>> my next question: What is the correct way to configure "USE=" in
>>> make.conf?
>>>
>>> When I use a below: (copied from my other systems):
>>>
>>> USE="-qt4 -kde -gnome -arts -berkdb -acl X gtk alsa cups apache2 ssl
>>> foomaticdb truetype kpathsea ppds mysql udev tiff png usb scanner
>>> gimp gimpprint cgi fam nptl type1 opengl tetexspell consolkit dbus
>>> pam policykit jpeg lock session startup-notification thunar
>>> cleartype corefonts -systemd -DOPENSSL_NO_HEARTBEATS abi_x86_32"
>>>
>>> PS. I think "dbus" is no longer used, isn't it?
>>>  <<< SNIP >>>
>>> -- 
>>> Thelma
>>>
>>>
>>
>>
>> Ask anyone, I'm different on the way I do USE flags, or I feel that
>> way.  If I have a flag that I want enabled/disabled on basically
>> everything that uses that flag, it goes in make.conf.  If I have a USE
>> flag that I may need for just a few packages, or a single package, I put
>> it in package.use.  As a example.  The kde USE flag.  Since I run mostly
>> KDE and want any packages I build to work with KDE, it goes in
>> make.conf.  To go with the other direction on this.  qt4 and qt5.  Some
>> packages work or look better with one or the other.  For those
>> exceptions, I use package.use to set those.  Since emerge reads
>> package.use last, those setting apply.
>>
>> Basically, make.conf is the rule for USE flags.  Package.use is for
>> exceptions to that rule.
>>
>> As usual, do what makes the most sense to you.  I post this just in case
>> this way may make sense, not that much of anything I do makes sense to
>> anyone else.  ;-)
>>
>> Dale
>>
>> :-)  :-)
>>
>
> Recently I read an interesting post [1] (especially the middle
> paragraph about the USE-flag ‘threads’ example). It let me rethink how
> I handle USE (which is even similar your way) and it might be worth to
> consider why a package maintainer defaults a flag on/off.
> [1] 
> 
>
>


I'm subscribed there and recall reading that.  The point of my post was
not for a specific flag.  I just picked a flag that has been around for
a long time and pretty much everyone recognizes what it is for.  As I
mentioned in another post, I could have picked many other flags.  X,
gnome, cups, or any number of others.  The biggest point, there are many
ways to handle USE flags.  Pick what works for you and more importantly,
makes sense to you.  Anytime us Gentoo users are
installing/upgrading/adding packages, we have to watch for changes or
even new flags that may not be set the way we want.  It's up to us on
how to manage it.  I posted my way, others can post their way.  The OP
can pick whichever makes the most sense to them. 

I might add, there are flags that we can't change.  Those are set by
upstream or the devs.  My post wasn't about that either.  It was all
about managing options that we can change.. 

Rich has some good points at times.  I try to read his posts unless it
is something that doesn't interest me.  I think he also supports the
point I was making in my post.  You have choices on how to do things,
pick the one that works and does what you need.  It's a strong point for
Gentoo.  I think USE flags are one of the biggest features of Gentoo. 
It's not like we have a fancy installer that can read our minds.  ROFL 

It is interesting to see and read how others do this tho.  It's amazing
sometimes how many different ways the same thing can be managed and
still work.  I'm not sure any other distro can do that, not that I used
others in a long time. 

Dale

:-)  :-)

Re: [gentoo-user] New Installation

[Neil Bothwick]

On Sat, 4 Feb 2017 23:36:56 -0700, the...@sys-concept.com wrote:

> my next question: What is the correct way to configure "USE=" in
> make.conf?
> 
> When I use a below: (copied from my other systems):
> 
> USE="-qt4 -kde -gnome -arts -berkdb -acl X gtk alsa cups apache2 ssl
> foomaticdb truetype kpathsea ppds mysql udev tiff png usb scanner gimp
> gimpprint cgi fam nptl type1 opengl tetexspell consolkit dbus pam
> policykit jpeg lock session startup-notification thunar cleartype
> corefonts -systemd -DOPENSSL_NO_HEARTBEATS abi_x86_32"

Copying an old USE setting is not the best idea. USE flags, profiles and
your needs change over time and /etc/portage gathers a lot of cruft. Now
you have the system working with the base profile, switch to a profile
that suits your needs and let portage rebuild @world. Then make small
changes to USE flags as needed.

I recently ported a system to new hardware and did the base install this
way. I found that I ended up with a system that worked just the same but
with far less in make.conf and package.use.

With USE flags, small changes are always best. A mass import of a USE
line like that above is likely to cause circular dependencies and other
problems.

How you manage the split between make.conf and package.use is up to you.
If I want a flag to apply globally, I put it in mzke.conf, otherwise it
goes in package.use, in a file names after the software requiring it
(which is not the same as the package name). If I find I have set the
same flag several times in package.use, I consider moving it to make.conf.


-- 
Neil Bothwick

A friend of mine sent me a postcard with a satellite photo of the
entire planet on it, and on the back he wrote, "Wish you were here."


pgpN6N_JnxMiI.pgp
Description: OpenPGP digital signature

[gentoo-user] nm-applet shows "?" in Gnome tool tray

[Mick]

Hi All,

In /etc/NetworkManager/NetworkManager.conf I have set up:

[connectivity]
uri=https://www.google.com

Since then I have noticed when the system comes up and a wired or wireless 
connection is established, a page opens up which displays a web page from the 
Gnome project, rather than google.com.

In addition, there is a question mark "?" displayed by the nm-applet in the 
tool tray when I have a wireless connection.  On wired connections I get the 
question mark superimposed on the wired network tool tray symbol.

Is there some explanation for either of these two phenomena?
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] New Installation

[Floyd Anderson]

On Sun, 05 Feb 01:44:30 -0600
Dale  wrote:

the...@sys-concept.com wrote:


I change in make.conf to:
USE="bindist"

and I was able to install basic system correctly, network is working and I can 
proceed with castomazation but
my next question: What is the correct way to configure "USE=" in make.conf?

When I use a below: (copied from my other systems):

USE="-qt4 -kde -gnome -arts -berkdb -acl X gtk alsa cups apache2 ssl foomaticdb 
truetype kpathsea ppds mysql udev tiff png usb scanner gimp gimpprint cgi fam nptl type1 
opengl tetexspell consolkit dbus pam policykit jpeg lock session startup-notification 
thunar cleartype corefonts -systemd -DOPENSSL_NO_HEARTBEATS abi_x86_32"

PS. I think "dbus" is no longer used, isn't it?
 <<< SNIP >>>
--
Thelma





Ask anyone, I'm different on the way I do USE flags, or I feel that
way.  If I have a flag that I want enabled/disabled on basically
everything that uses that flag, it goes in make.conf.  If I have a USE
flag that I may need for just a few packages, or a single package, I put
it in package.use.  As a example.  The kde USE flag.  Since I run mostly
KDE and want any packages I build to work with KDE, it goes in
make.conf.  To go with the other direction on this.  qt4 and qt5.  Some
packages work or look better with one or the other.  For those
exceptions, I use package.use to set those.  Since emerge reads
package.use last, those setting apply.

Basically, make.conf is the rule for USE flags.  Package.use is for
exceptions to that rule.

As usual, do what makes the most sense to you.  I post this just in case
this way may make sense, not that much of anything I do makes sense to
anyone else.  ;-)

Dale

:-)  :-)



Recently I read an interesting post [1] (especially the middle paragraph 
about the USE-flag ‘threads’ example). It let me rethink how I handle 
USE (which is even similar your way) and it might be worth to consider 
why a package maintainer defaults a flag on/off. 


[1] 


--
Best regards,
Floyd Anderson

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Meino . Cramer]

J. Roeleveld  [17-02-05 11:28]:
> On Sunday, February 5, 2017 10:43:21 AM CET meino.cra...@gmx.de wrote:
> > Mick  [17-02-05 10:36]:
> > > On Sunday 05 Feb 2017 10:13:09 meino.cra...@gmx.de wrote:
> 
> > The last time I used star it kills my filesystem. It mau be the most
> > POSIX compliant thing of the universe...but...
> > Its long ago...I never have touched this again...
> > 
> > I will check the grub thingy...good idea! :)
> 
> If you figure that one out, please share.
> I would love to know how to do that.
> 
> > Currentlu I am totally blocked from build a new system, since
> > gcc has stopped working globally.
> 
> I have this occasionally. Run:
> # gcc-config -l
> 
> Usually the first on in that list is the one you want. Which would be set 
> with:
> # gcc-config 1
> 
> And then correct your profile:
> # source /etc/profile
> 
> And try emerge again :)
> 
> --
> Joost
> 
> 
> 

Hi Joost,

the problem was a superflous "," in the make.conf-file which screwed
up some later stages of the whole process.

I am still setting up the system...you...compiling the world is the
gentooist daily bussiness ;)

So it may take some time till I try the grub thing.
If I find a way (or a valid info that it will definetly NOT work) 
I will post it here (this thread or a separate one).

Cheers
Meino

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[J. Roeleveld]

On Sunday, February 5, 2017 10:43:21 AM CET meino.cra...@gmx.de wrote:
> Mick  [17-02-05 10:36]:
> > On Sunday 05 Feb 2017 10:13:09 meino.cra...@gmx.de wrote:

> The last time I used star it kills my filesystem. It mau be the most
> POSIX compliant thing of the universe...but...
> Its long ago...I never have touched this again...
> 
> I will check the grub thingy...good idea! :)

If you figure that one out, please share.
I would love to know how to do that.

> Currentlu I am totally blocked from build a new system, since
> gcc has stopped working globally.

I have this occasionally. Run:
# gcc-config -l

Usually the first on in that list is the one you want. Which would be set with:
# gcc-config 1

And then correct your profile:
# source /etc/profile

And try emerge again :)

--
Joost

Re: [gentoo-user] Suddenly gcc fails to compile anything...

[Meino . Cramer]

meino.cra...@gmx.de  [17-02-05 09:54]:
> Hi,
> 
> after installing / updateing 122 package (first sync/update of the new
> gentoo installation), gcc is no longer able to compile stuff
> (according to configure) -- problem is always the same:
> 
> Thread model: posix
> gcc version 5.4.0 (Gentoo 5.4.0-r3 p1.3, pie-0.6.5) 
> configure:3882: $? = 0
> configure:3871: x86_64-pc-linux-gnu-gcc -V >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-V'
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> configure:3882: $? = 1
> configure:3871: x86_64-pc-linux-gnu-gcc -qversion >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-qversion'
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> 
> 
> I have no idea, where this "-V' and '-qversion' results from...my
> make.conf looks like this:
> # These are the USE and USE_EXPAND flags that were used for
> # buidling in addition to what is provided by the profile.
> USE="bindist"
> CPU_FLAGS_X86="mmx mmxext sse3"
> PORTDIR="/usr/portage"
> DISTDIR="${PORTDIR}/distfiles"
> PKGDIR="${PORTDIR}/packages"
> 
> # mcc added initially 
> ACCEPT_KEYWORDS="~amd64"
> MAKEOPT="-j7"
> VIDEO_CARDS="nvidia"
> NOCOLOR=true
> INPUT_DEVICE=evdev
> PORTAGE_ELOG_SYSTEM="save"
> PORTAGE_ELOG_CLASSES="warn error info log qa"
> FEATURES=splitdebug
> PORTAGE_BZIP2_COMMAND="bzip2"
> 
> Cheers
> Meino
> 

Found it myself:
It was a superflous "," in make.conf which creates the chaos.
In the future I will strictly avoid ","s... ;)

Cheers
Meino

Re: [gentoo-user] New Installation

[Dale]

Peter Humphrey wrote:
> On Sunday 05 Feb 2017 01:44:30 Dale wrote:
>
>> Ask anyone, I'm different on the way I do USE flags, or I feel that
>> way.  If I have a flag that I want enabled/disabled on basically
>> everything that uses that flag, it goes in make.conf.  If I have a USE
>> flag that I may need for just a few packages, or a single package, I put
>> it in package.use.
> The devs have already made that choice, though of course you don't have to 
> follow them.
>

Other than the profile, I set the USE line in make.conf, or
package.use.  I'm not trying to post details on a specific USE flag,
just picking a common one that makes the point of how it can be handled. 


>> Basically, make.conf is the rule for USE flags.  Package.use is for
>> exceptions to that rule.
> Or, if the USE flag is documented in /usr/portage/profiles/use.desc it's for 
> general application and you put it in make.conf, and if it's in 
> /usr/portage/profiles/use.local.desc it applies to one or a few specific 
> packages and you put it in package.use.
>
> Then you just have to decide how to arrange you package.use directory. This 
> is mine, in case it helps anyone:
>
> # ls /etc/portage/package.use
> boinc  firefox  firmware  iputils  qtwebengine  runtime-meta  xorg
>
> # cat /etc/portage/package.use/xorg
> media-libs/mesa -vaapi
> sys-devel/llvm  clang video_cards_radeon
> x11-libs/libdrm video_cards_radeon
>
> # cat /etc/portage/package.use/boinc
> app-emulation/virtualboxadditions extensions java python
> x11-libs/wxGTK  webkit
>
> You can see I have all the USE flags affecting the xorg-x11 system in one 
> file, 
> all those needed by boinc in another, and so on. In my usual top-down 
> approach I name each file by what it's for, not what's in it.
>
>> As usual, do what makes the most sense to you.  I post this just in case
>> this way may make sense, not that much of anything I do makes sense to
>> anyone else.  ;-)
> You're too modest...  :)
>

I have one file.  I tried having more than one file and I did not like
that one bit.  Sometimes the same line can fit in a different package
depending on what pulls in a package and needs a certain USE flag
setting.  If I need to know if a package is listed in package.use, I
have one file to look at.  I don't have to spend a lot of time looking
in the file I think it should be in only to find it in another file for
some other reason than the current one.  Yep, I tried that road.  It's
not for me.  If it works for you tho, do it that way.  Everyone has a
way/method that works for them. 

Dale

:-)  :-) 

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Meino . Cramer]

Mick  [17-02-05 10:36]:
> On Sunday 05 Feb 2017 10:13:09 meino.cra...@gmx.de wrote:
> > J. Roeleveld  [17-02-05 10:04]:
> > > On Sunday, February 5, 2017 9:46:53 AM CET meino.cra...@gmx.de wrote:
> > > > J. Roeleveld  [17-02-05 08:44]:
> > > > > On February 5, 2017 6:26:27 AM GMT+01:00, meino.cra...@gmx.de wrote:
> > > > > >Hi,
> > > > > >
> > > > > >since my old Gentoo installation seems to be screwed up (regarding
> > > > > >the update process) beyond repair I decided to install a new one
> > > > > >instead of waiting for help.
> > > > > >
> > > > > >I already made space at a certain of my harddisk and installed the
> > > > > >stage3 there.
> > > > > >Chrooting is one of the first steps to check, whether what I have
> > > > > >done so is valid.
> > > > > >
> > > > > >But before deleting the old root and install the new one at its
> > > > > >place I would like to do a atmost identical boot into the new
> > > > > >root.
> > > > > >
> > > > > >As far as I know the kernel only allows to boot into a partition
> > > > > >(instead of a directory on a partition containing the root
> > > > > >installation) and I am still using devices to boot from instead
> > > > > >of GPT.
> > > > > >
> > > > > >Is there any neat trick to do a real boot into the new root via
> > > > > >the normal boot process (grub2) nevertheless ?
> > > > > >
> > > > > >Cheers
> > > > > >Meino
> > > > > 
> > > > > If I understand correctly. The answer is no. (Unless you write some
> > > > > clever
> > > > > initramfs)
> > > > > 
> > > > > Afaik, the kernel takes the entire partition and mounts it at '/'. If
> > > > > you
> > > > > want it to use a directory (which would then be at '/newinstall') you
> > > > > need to get the kernel to chroot into that directory and run init in
> > > > > there.
> > > > > 
> > > > > Only option I see is to use an extra disk. Maybe a USB drive and use
> > > > > that.
> > > > > 
> > > > > --
> > > > > Joost
> > > > 
> > > > Hi Joost,
> > > > 
> > > > thanks fpr your posting! :)
> > > > 
> > > > Ok...another USB drive mau lay around here...will see...
> > > > Just two quick questions:
> > > > 
> > > > Is this ok, to preserve as much as possible of the
> > > > settings/attributes/whatever of the files or do you anything better
> > > > and quickier than this:
> > > > (cd /. ; tar cf - . ) | ( cd /. ; tar xvpsf - )
> > > > ?
> > > 
> > > Don't forget to add the permissions on the source side:
> > > 
> > > tar --xattrs -cvpf .
> > > And maybe also add "--xattrs" on the target side.
> > > 
> > > Other options:
> > > # rsync (not fully certain about options)
> > > # cd  ; cp -a  .
> > > 
> > > I never did any timing, but logic tells me using the "cp" option is
> > > quicker
> > > (as it is all on the same system)
> > > 
> > > --
> > > Joost
> > 
> > THANKS! for the correction of the commandline, Joost!!!
> > 
> > While copying I am always on the same system ... it is just another
> > subdirectory from the copuing process's perspective (or I miss
> > the point here totally...still doing below my normal coffee level
> > currentlu ;)
> > 
> > I think rsync becomes speedy for updates...only...?
> > 
> > Cheers
> > Meino
> 
> Also have a look at app-arch/star.
> 
> Regarding booting off a directory, have a look at booting ISO images with 
> GRUB.  I would think a similar approach should allow you to boot from a 
> directory instead of an ISO image.
> -- 
> Regards,
> Mick

Thanks for the infos, Mick! 

The last time I used star it kills my filesystem. It mau be the most
POSIX compliant thing of the universe...but...
Its long ago...I never have touched this again...

I will check the grub thingy...good idea! :)

Currentlu I am totally blocked from build a new system, since
gcc has stopped working globally.

Will see...

Cheers
Meino

Re: [gentoo-user] Suddenly gcc fails to compile anything...

[Meino . Cramer]

Dale  [17-02-05 10:28]:
> meino.cra...@gmx.de wrote:
> > Hi,
> >
> > after installing / updateing 122 package (first sync/update of the new
> > gentoo installation), gcc is no longer able to compile stuff
> > (according to configure) -- problem is always the same:
> >
> > Thread model: posix
> > gcc version 5.4.0 (Gentoo 5.4.0-r3 p1.3, pie-0.6.5) 
> > configure:3882: $? = 0
> > configure:3871: x86_64-pc-linux-gnu-gcc -V >&5
> > x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-V'
> > x86_64-pc-linux-gnu-gcc: fatal error: no input files
> > compilation terminated.
> > configure:3882: $? = 1
> > configure:3871: x86_64-pc-linux-gnu-gcc -qversion >&5
> > x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-qversion'
> > x86_64-pc-linux-gnu-gcc: fatal error: no input files
> > compilation terminated.
> >
> >
> > I have no idea, where this "-V' and '-qversion' results from...my
> > make.conf looks like this:
> > # These are the USE and USE_EXPAND flags that were used for
> > # buidling in addition to what is provided by the profile.
> > USE="bindist"
> > CPU_FLAGS_X86="mmx mmxext sse3"
> > PORTDIR="/usr/portage"
> > DISTDIR="${PORTDIR}/distfiles"
> > PKGDIR="${PORTDIR}/packages"
> >
> > # mcc added initially 
> > ACCEPT_KEYWORDS="~amd64"
> > MAKEOPT="-j7"
> > VIDEO_CARDS="nvidia"
> > NOCOLOR=true
> > INPUT_DEVICE=evdev
> > PORTAGE_ELOG_SYSTEM="save"
> > PORTAGE_ELOG_CLASSES="warn error info log qa"
> > FEATURES=splitdebug
> > PORTAGE_BZIP2_COMMAND="bzip2"
> >
> > Cheers
> > Meino
> >
> 
> The first thing I would check, gcc-config -l and see what it says.  It's
> been a good long while but I've had it update and for some reason not
> switch properly.  Sometimes, I set it even if it shows it is correct and
> then it works.  It has been a while since it did that but it is quick
> and easy to test.  If it doesn't work, maybe someone else will have a
> better idea.
> 
> Dale
> 
> :-)  :-) 
> 
Hi Dale,

thanks for the hint...but unfortunately it does not change anuthing...

Any other idea?


Cheers
Meino

Re: [gentoo-user] New Installation

[Dale]

Mick wrote:
> On Sunday 05 Feb 2017 01:44:30 Dale wrote:
>> the...@sys-concept.com wrote:
>>> I change in make.conf to:
>>> USE="bindist"
>>>
>>> and I was able to install basic system correctly, network is working and I
>>> can proceed with castomazation but my next question: What is the correct
>>> way to configure "USE=" in make.conf?
> [snip...]
>
>> If I have a flag that I want enabled/disabled on basically
>> everything that uses that flag, it goes in make.conf.  If I have a USE
>> flag that I may need for just a few packages, or a single package, I put
>> it in package.use.
> Yes, this is pretty much the case.  System wide USE flags go in make.conf.  
> Package specific USE flags *which do not apply system wide* go in package.use.
>
>
>> As a example.  The kde USE flag.  Since I run mostly
>> KDE and want any packages I build to work with KDE, it goes in
>> make.conf.
> Errm ... not exactly.
>
> If one uses KDE (it's called Plasma these days) then the way to set up system 
> wide KDE USE flags is to select the corresponding profile.  This will set up 
> the correct USE flags and help install all necessary dependencies (e.g. Qt, 
> dbus, polkit, etc.).  The way to do this is to use 'eselect profile list' and 
> set the desired profile from those listed.  This will set a symlink from your 
> make.profile to the required /usr/portage/profiles/default/ selection of USE 
> flags.
>
> Afterwards, have a look in the USE flags shown when you run 'emerge --info' 
> to 
> find out what your OS is using in an emerge.  If you want something set up 
> globally to cater e.g. for your hardware, which is not shown in 'emerge --
> info', you can set it in make.conf.  This will avoid polluting your make.conf 
> with duplicate USE flags which are already set by your make.profile.
>
> While talking about hardware, you may want to consider installing and running:
>
>  app-portage/cpuid2cpuflags
>
> It will give a list specific to the instruction set of your CPU which you 
> should add in CPU_FLAGS_X86=  in your make.conf
>
> Finally, have a quick read here where it explains how to interpret the output 
> of emerge messages regarding USE flags and how to differentiate between 
> local, 
> global and conflicting USE flags:
>
>  https://devmanual.gentoo.org/general-concepts/use-flags/index.html
>
> HTH


I was just using the kde flag as a example.  Although, the kde USE flag
is still in use by several packages. 

kde - Add support for KDE (K Desktop Environment)

I could have also used X or several others as a example. 

Dale

:-)  :-) 

Re: [gentoo-user] New Installation

[J. Roeleveld]

On Saturday, February 4, 2017 11:28:37 PM CET Alan McKinnon wrote:
> On 04/02/2017 17:56, Peter Humphrey wrote:
> > On Saturday 04 Feb 2017 17:32:53 Alan McKinnon wrote:
> >> Modern kernels DO get nervous if they have no swap at all - it's used
> >> internally. So make a small amount of swap to make the kernel happy, say
> >> 64M or so. Yes, megs.
> >> 
> >> And if your machine sleeps to disk you will need swap large enough to
> >> store the memory image - it has to go somewhere and that is swap.
> >> 
> >> That's my advice. Now let the nay-sayers begin the argument
> > 
> > No argument from me, Alan. It isn't just the kernel that gets nervous - I
> > do too if I don't have any swap available. I have 32 GB and an 8 GB swap,
> > which I'm thinking of reducing (the swap, that is). My SSD is only 256 GB
> > and my boinc partition has filled up today, so I need to recover some
> > unused space.
> I'd be much more nervous about swap on SSD tbh.
> 
> I can't imagine that working well, by it's nature swap is write-heavy

I don't see much issue with swap on SSD as long as it isn't used too much.
My laptop only has SSD, my desktop also has a spinning-rust disk for scratch-
heavy (many, many writes) activities.

My swap is on SSD, it's not used often, I guess I would wear out that SSD 
sooner with the activities of my home-dir and akonadi. :)

I don't see anything bad happening yet using smartctl and this machine is 
running a lot lately with, for my desktop, quite high uptimes.

--
Joost

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Mick]

On Sunday 05 Feb 2017 10:13:09 meino.cra...@gmx.de wrote:
> J. Roeleveld  [17-02-05 10:04]:
> > On Sunday, February 5, 2017 9:46:53 AM CET meino.cra...@gmx.de wrote:
> > > J. Roeleveld  [17-02-05 08:44]:
> > > > On February 5, 2017 6:26:27 AM GMT+01:00, meino.cra...@gmx.de wrote:
> > > > >Hi,
> > > > >
> > > > >since my old Gentoo installation seems to be screwed up (regarding
> > > > >the update process) beyond repair I decided to install a new one
> > > > >instead of waiting for help.
> > > > >
> > > > >I already made space at a certain of my harddisk and installed the
> > > > >stage3 there.
> > > > >Chrooting is one of the first steps to check, whether what I have
> > > > >done so is valid.
> > > > >
> > > > >But before deleting the old root and install the new one at its
> > > > >place I would like to do a atmost identical boot into the new
> > > > >root.
> > > > >
> > > > >As far as I know the kernel only allows to boot into a partition
> > > > >(instead of a directory on a partition containing the root
> > > > >installation) and I am still using devices to boot from instead
> > > > >of GPT.
> > > > >
> > > > >Is there any neat trick to do a real boot into the new root via
> > > > >the normal boot process (grub2) nevertheless ?
> > > > >
> > > > >Cheers
> > > > >Meino
> > > > 
> > > > If I understand correctly. The answer is no. (Unless you write some
> > > > clever
> > > > initramfs)
> > > > 
> > > > Afaik, the kernel takes the entire partition and mounts it at '/'. If
> > > > you
> > > > want it to use a directory (which would then be at '/newinstall') you
> > > > need to get the kernel to chroot into that directory and run init in
> > > > there.
> > > > 
> > > > Only option I see is to use an extra disk. Maybe a USB drive and use
> > > > that.
> > > > 
> > > > --
> > > > Joost
> > > 
> > > Hi Joost,
> > > 
> > > thanks fpr your posting! :)
> > > 
> > > Ok...another USB drive mau lay around here...will see...
> > > Just two quick questions:
> > > 
> > > Is this ok, to preserve as much as possible of the
> > > settings/attributes/whatever of the files or do you anything better
> > > and quickier than this:
> > > (cd /. ; tar cf - . ) | ( cd /. ; tar xvpsf - )
> > > ?
> > 
> > Don't forget to add the permissions on the source side:
> > 
> > tar --xattrs -cvpf .
> > And maybe also add "--xattrs" on the target side.
> > 
> > Other options:
> > # rsync (not fully certain about options)
> > # cd  ; cp -a  .
> > 
> > I never did any timing, but logic tells me using the "cp" option is
> > quicker
> > (as it is all on the same system)
> > 
> > --
> > Joost
> 
> THANKS! for the correction of the commandline, Joost!!!
> 
> While copying I am always on the same system ... it is just another
> subdirectory from the copuing process's perspective (or I miss
> the point here totally...still doing below my normal coffee level
> currentlu ;)
> 
> I think rsync becomes speedy for updates...only...?
> 
> Cheers
> Meino

Also have a look at app-arch/star.

Regarding booting off a directory, have a look at booting ISO images with 
GRUB.  I would think a similar approach should allow you to boot from a 
directory instead of an ISO image.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] New Installation

[J. Roeleveld]

On Saturday, February 4, 2017 11:36:56 PM CET the...@sys-concept.com wrote:

(longer reply)

> 
> I change in make.conf to:
> USE="bindist"
> 
> and I was able to install basic system correctly, network is working and I
> can proceed with castomazation but my next question: What is the correct
> way to configure "USE=" in make.conf?
> 
> When I use a below: (copied from my other systems):
> 
> USE="-qt4 -kde -gnome -arts -berkdb -acl X gtk alsa cups apache2 ssl
> foomaticdb truetype kpathsea ppds mysql udev tiff png usb scanner gimp
> gimpprint cgi fam nptl type1 opengl tetexspell consolkit dbus pam policykit
> jpeg lock session startup-notification thunar cleartype corefonts -systemd
> -DOPENSSL_NO_HEARTBEATS abi_x86_32"
> 
> PS. I think "dbus" is no longer used, isn't it?

I have dbus installed, so the package still exists. If it is a valid USE-flag, 
I don't know.

In your list, I see a few I have never used. Most of them, I would personally 
only set for those packages where I want them to apply, but that is a personal 
decision.

My main concerns with your list are:
# -DOPENSSL_NO_HEARTBEATS
This seems more like something that should be added as a compiler-flag for 1 
package or something in an apache config file.

# abi_x86_32
I am assuming you want packages to also be build for 32-bit.
If that is the case, I would set the following in your make.conf file:
# ABI_X86="64 32"
and remove this entry from your USE-list.

# consolkit
I think this should be "consolekit" as that one does exist.

> I get a log of blockers and my file "package.use" starting to look like
> trash can with entries like:
> 
> # required by x11-libs/libxcb-1.12::gentoo
> # required by x11-apps/xwininfo-1.1.3::gentoo
> # required by x11-misc/xscreensaver-5.36::gentoo
> # required by xfce-base/xfce4-session-4.12.1-r1::gentoo[xscreensaver]
> # required by xfce-base/xfce4-meta-4.12::gentoo
> # required by xfce-base/xfce4-meta (argument)
> 
> >=x11-libs/libXau-1.0.8 abi_x86_32

This is related to the above comment about your abi... useflag.

> # required by x11-libs/libxcb-1.12::gentoo
> # required by x11-apps/xwininfo-1.1.3::gentoo
> # required by x11-misc/xscreensaver-5.36::gentoo
> # required by xfce-base/xfce4-session-4.12.1-r1::gentoo[xscreensaver]
> # required by xfce-base/xfce4-meta-4.12::gentoo
> # required by xfce-base/xfce4-meta (argument)
> 
> >=dev-libs/libpthread-stubs-0.3-r1 abi_x86_32

Same

> If I try to use my USE="-qt4 ... etc" and try to emerge:
> emerge --ask xfce-base/xfce4-meta
> 
> I get tones of blockers and problem solving eg.:
> 
> [blocks B  ] dev-util/pkgconf[pkg-config]
> ("dev-util/pkgconf[pkg-config]" is blocking dev-util/pkgconfig-0.28-r2)
> [blocks B  ] media-libs/libjpeg-turbo:0 ("media-libs/libjpeg-turbo:0"
> is blocking media-libs/jpeg-8d-r1) [blocks B  ] media-libs/jpeg:0
> ("media-libs/jpeg:0" is blocking media-libs/libjpeg-turbo-1.5.0) [blocks B 
> ] sys-fs/udev ("sys-fs/udev" is blocking sys-fs/eudev-3.1.5) [blocks B 
> ] dev-util/pkgconfig ("dev-util/pkgconfig" is blocking
> dev-util/pkgconf-0.9.12)
> 
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
> 
>   (dev-util/pkgconf-0.9.12:0/0::gentoo, ebuild scheduled for merge) pulled
> in by
> >=dev-util/pkgconf-0.9.3-r1[pkg-config,abi_x86_32(-)?,abi_x86_64(-)?,abi
> >_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc
> >_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
> >(>=dev-util/pkgconf-0.9.3-r1[pkg-config,abi_x86_32(-),abi_x86_64(-)])
> >required by (virtual/pkgconfig-0-r1:0/0::gentoo, ebuild scheduled for
> >merge)
>   (sys-fs/eudev-3.1.5:0/0::gentoo, ebuild scheduled for merge) pulled in by
> 
> >=sys-fs/eudev-1.3 required by (virtual/udev-215:0/0::gentoo, installed)
> >=sys-fs/eudev-1.3:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi
> >_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_
> >64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
> >(>=sys-fs/eudev-1.3:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
> >(virtual/libudev-215-r1:0/1::gentoo, ebuild scheduled for merge)
>   (sys-fs/udev-225-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by
> 
> >=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,a
> >bi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_pp
> >c_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
> >(>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by
> >(virtual/libudev-215-r1:0/1::gentoo, ebuild scheduled for merge)
> >=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo,
> >installed)
>   (dev-util/pkgconfig-0.28-r2:0/0::gentoo, ebuild scheduled for merge)
> pulled in by
> >=dev-util/pkgconfig-0.28-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-
> >)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,ab
> >i

Re: [gentoo-user] Suddenly gcc fails to compile anything...

[Dale]

meino.cra...@gmx.de wrote:
> Hi,
>
> after installing / updateing 122 package (first sync/update of the new
> gentoo installation), gcc is no longer able to compile stuff
> (according to configure) -- problem is always the same:
>
> Thread model: posix
> gcc version 5.4.0 (Gentoo 5.4.0-r3 p1.3, pie-0.6.5) 
> configure:3882: $? = 0
> configure:3871: x86_64-pc-linux-gnu-gcc -V >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-V'
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
> configure:3882: $? = 1
> configure:3871: x86_64-pc-linux-gnu-gcc -qversion >&5
> x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-qversion'
> x86_64-pc-linux-gnu-gcc: fatal error: no input files
> compilation terminated.
>
>
> I have no idea, where this "-V' and '-qversion' results from...my
> make.conf looks like this:
> # These are the USE and USE_EXPAND flags that were used for
> # buidling in addition to what is provided by the profile.
> USE="bindist"
> CPU_FLAGS_X86="mmx mmxext sse3"
> PORTDIR="/usr/portage"
> DISTDIR="${PORTDIR}/distfiles"
> PKGDIR="${PORTDIR}/packages"
>
> # mcc added initially 
> ACCEPT_KEYWORDS="~amd64"
> MAKEOPT="-j7"
> VIDEO_CARDS="nvidia"
> NOCOLOR=true
> INPUT_DEVICE=evdev
> PORTAGE_ELOG_SYSTEM="save"
> PORTAGE_ELOG_CLASSES="warn error info log qa"
> FEATURES=splitdebug
> PORTAGE_BZIP2_COMMAND="bzip2"
>
> Cheers
> Meino
>

The first thing I would check, gcc-config -l and see what it says.  It's
been a good long while but I've had it update and for some reason not
switch properly.  Sometimes, I set it even if it shows it is correct and
then it works.  It has been a while since it did that but it is quick
and easy to test.  If it doesn't work, maybe someone else will have a
better idea.

Dale

:-)  :-) 

Re: [gentoo-user] New Installation

[Peter Humphrey]

On Sunday 05 Feb 2017 01:44:30 Dale wrote:

> Ask anyone, I'm different on the way I do USE flags, or I feel that
> way.  If I have a flag that I want enabled/disabled on basically
> everything that uses that flag, it goes in make.conf.  If I have a USE
> flag that I may need for just a few packages, or a single package, I put
> it in package.use.

The devs have already made that choice, though of course you don't have to 
follow them.

> Basically, make.conf is the rule for USE flags.  Package.use is for
> exceptions to that rule.

Or, if the USE flag is documented in /usr/portage/profiles/use.desc it's for 
general application and you put it in make.conf, and if it's in 
/usr/portage/profiles/use.local.desc it applies to one or a few specific 
packages and you put it in package.use.

Then you just have to decide how to arrange you package.use directory. This 
is mine, in case it helps anyone:

# ls /etc/portage/package.use
boinc  firefox  firmware  iputils  qtwebengine  runtime-meta  xorg

# cat /etc/portage/package.use/xorg
media-libs/mesa -vaapi
sys-devel/llvm  clang video_cards_radeon
x11-libs/libdrm video_cards_radeon

# cat /etc/portage/package.use/boinc
app-emulation/virtualboxadditions extensions java python
x11-libs/wxGTK  webkit

You can see I have all the USE flags affecting the xorg-x11 system in one file, 
all those needed by boinc in another, and so on. In my usual top-down 
approach I name each file by what it's for, not what's in it.

> As usual, do what makes the most sense to you.  I post this just in case
> this way may make sense, not that much of anything I do makes sense to
> anyone else.  ;-)

You're too modest...  :)

-- 
Regards
Peter

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Dale]

J. Roeleveld wrote:
> On Sunday, February 5, 2017 9:46:53 AM CET meino.cra...@gmx.de wrote:
>> J. Roeleveld  [17-02-05 08:44]:
>>> On February 5, 2017 6:26:27 AM GMT+01:00, meino.cra...@gmx.de wrote:
 Hi,

 since my old Gentoo installation seems to be screwed up (regarding
 the update process) beyond repair I decided to install a new one
 instead of waiting for help.

 I already made space at a certain of my harddisk and installed the
 stage3 there.
 Chrooting is one of the first steps to check, whether what I have
 done so is valid.

 But before deleting the old root and install the new one at its
 place I would like to do a atmost identical boot into the new
 root.

 As far as I know the kernel only allows to boot into a partition
 (instead of a directory on a partition containing the root
 installation) and I am still using devices to boot from instead
 of GPT.

 Is there any neat trick to do a real boot into the new root via
 the normal boot process (grub2) nevertheless ?

 Cheers
 Meino
>>> If I understand correctly. The answer is no. (Unless you write some clever
>>> initramfs)
>>>
>>> Afaik, the kernel takes the entire partition and mounts it at '/'. If you
>>> want it to use a directory (which would then be at '/newinstall') you
>>> need to get the kernel to chroot into that directory and run init in
>>> there.
>>>
>>> Only option I see is to use an extra disk. Maybe a USB drive and use that.
>>>
>>> --
>>> Joost
>> Hi Joost,
>>
>> thanks fpr your posting! :)
>>
>> Ok...another USB drive mau lay around here...will see...
>> Just two quick questions:
>>
>> Is this ok, to preserve as much as possible of the
>> settings/attributes/whatever of the files or do you anything better
>> and quickier than this:
>> (cd /. ; tar cf - . ) | ( cd /. ; tar xvpsf - )
>> ?
> Don't forget to add the permissions on the source side:
>
> tar --xattrs -cvpf . 
> And maybe also add "--xattrs" on the target side.
>
> Other options:
> # rsync (not fully certain about options)
> # cd  ; cp -a  .
>
> I never did any timing, but logic tells me using the "cp" option is quicker 
> (as it is all on the same system)
>
> --
> Joost
>

I've moved my OS from one drive to another a few times.  I use cp -av
and let her rip.  It takes a while but I tried the tar way and guess
what, it took a while too.  It just seems to add one more step. 

Good advice. 

Dale

:-)  :-) 

Re: [gentoo-user] New Installation

[Mick]

On Sunday 05 Feb 2017 01:44:30 Dale wrote:
> the...@sys-concept.com wrote:
> > I change in make.conf to:
> > USE="bindist"
> > 
> > and I was able to install basic system correctly, network is working and I
> > can proceed with castomazation but my next question: What is the correct
> > way to configure "USE=" in make.conf?
[snip...]

> If I have a flag that I want enabled/disabled on basically
> everything that uses that flag, it goes in make.conf.  If I have a USE
> flag that I may need for just a few packages, or a single package, I put
> it in package.use.

Yes, this is pretty much the case.  System wide USE flags go in make.conf.  
Package specific USE flags *which do not apply system wide* go in package.use.


> As a example.  The kde USE flag.  Since I run mostly
> KDE and want any packages I build to work with KDE, it goes in
> make.conf.

Errm ... not exactly.

If one uses KDE (it's called Plasma these days) then the way to set up system 
wide KDE USE flags is to select the corresponding profile.  This will set up 
the correct USE flags and help install all necessary dependencies (e.g. Qt, 
dbus, polkit, etc.).  The way to do this is to use 'eselect profile list' and 
set the desired profile from those listed.  This will set a symlink from your 
make.profile to the required /usr/portage/profiles/default/ selection of USE 
flags.

Afterwards, have a look in the USE flags shown when you run 'emerge --info' to 
find out what your OS is using in an emerge.  If you want something set up 
globally to cater e.g. for your hardware, which is not shown in 'emerge --
info', you can set it in make.conf.  This will avoid polluting your make.conf 
with duplicate USE flags which are already set by your make.profile.

While talking about hardware, you may want to consider installing and running:

 app-portage/cpuid2cpuflags

It will give a list specific to the instruction set of your CPU which you 
should add in CPU_FLAGS_X86=  in your make.conf

Finally, have a quick read here where it explains how to interpret the output 
of emerge messages regarding USE flags and how to differentiate between local, 
global and conflicting USE flags:

 https://devmanual.gentoo.org/general-concepts/use-flags/index.html

HTH
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Meino . Cramer]

J. Roeleveld  [17-02-05 10:04]:
> On Sunday, February 5, 2017 9:46:53 AM CET meino.cra...@gmx.de wrote:
> > J. Roeleveld  [17-02-05 08:44]:
> > > On February 5, 2017 6:26:27 AM GMT+01:00, meino.cra...@gmx.de wrote:
> > > >Hi,
> > > >
> > > >since my old Gentoo installation seems to be screwed up (regarding
> > > >the update process) beyond repair I decided to install a new one
> > > >instead of waiting for help.
> > > >
> > > >I already made space at a certain of my harddisk and installed the
> > > >stage3 there.
> > > >Chrooting is one of the first steps to check, whether what I have
> > > >done so is valid.
> > > >
> > > >But before deleting the old root and install the new one at its
> > > >place I would like to do a atmost identical boot into the new
> > > >root.
> > > >
> > > >As far as I know the kernel only allows to boot into a partition
> > > >(instead of a directory on a partition containing the root
> > > >installation) and I am still using devices to boot from instead
> > > >of GPT.
> > > >
> > > >Is there any neat trick to do a real boot into the new root via
> > > >the normal boot process (grub2) nevertheless ?
> > > >
> > > >Cheers
> > > >Meino
> > > 
> > > If I understand correctly. The answer is no. (Unless you write some clever
> > > initramfs)
> > > 
> > > Afaik, the kernel takes the entire partition and mounts it at '/'. If you
> > > want it to use a directory (which would then be at '/newinstall') you
> > > need to get the kernel to chroot into that directory and run init in
> > > there.
> > > 
> > > Only option I see is to use an extra disk. Maybe a USB drive and use that.
> > > 
> > > --
> > > Joost
> > 
> > Hi Joost,
> > 
> > thanks fpr your posting! :)
> > 
> > Ok...another USB drive mau lay around here...will see...
> > Just two quick questions:
> > 
> > Is this ok, to preserve as much as possible of the
> > settings/attributes/whatever of the files or do you anything better
> > and quickier than this:
> > (cd /. ; tar cf - . ) | ( cd /. ; tar xvpsf - )
> > ?
> 
> Don't forget to add the permissions on the source side:
> 
> tar --xattrs -cvpf . 
> And maybe also add "--xattrs" on the target side.
> 
> Other options:
> # rsync (not fully certain about options)
> # cd  ; cp -a  .
> 
> I never did any timing, but logic tells me using the "cp" option is quicker 
> (as it is all on the same system)
> 
> --
> Joost
> 
> 

THANKS! for the correction of the commandline, Joost!!!

While copying I am always on the same system ... it is just another
subdirectory from the copuing process's perspective (or I miss
the point here totally...still doing below my normal coffee level
currentlu ;)

I think rsync becomes speedy for updates...only...?

Cheers
Meino

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[J. Roeleveld]

On Sunday, February 5, 2017 9:46:53 AM CET meino.cra...@gmx.de wrote:
> J. Roeleveld  [17-02-05 08:44]:
> > On February 5, 2017 6:26:27 AM GMT+01:00, meino.cra...@gmx.de wrote:
> > >Hi,
> > >
> > >since my old Gentoo installation seems to be screwed up (regarding
> > >the update process) beyond repair I decided to install a new one
> > >instead of waiting for help.
> > >
> > >I already made space at a certain of my harddisk and installed the
> > >stage3 there.
> > >Chrooting is one of the first steps to check, whether what I have
> > >done so is valid.
> > >
> > >But before deleting the old root and install the new one at its
> > >place I would like to do a atmost identical boot into the new
> > >root.
> > >
> > >As far as I know the kernel only allows to boot into a partition
> > >(instead of a directory on a partition containing the root
> > >installation) and I am still using devices to boot from instead
> > >of GPT.
> > >
> > >Is there any neat trick to do a real boot into the new root via
> > >the normal boot process (grub2) nevertheless ?
> > >
> > >Cheers
> > >Meino
> > 
> > If I understand correctly. The answer is no. (Unless you write some clever
> > initramfs)
> > 
> > Afaik, the kernel takes the entire partition and mounts it at '/'. If you
> > want it to use a directory (which would then be at '/newinstall') you
> > need to get the kernel to chroot into that directory and run init in
> > there.
> > 
> > Only option I see is to use an extra disk. Maybe a USB drive and use that.
> > 
> > --
> > Joost
> 
> Hi Joost,
> 
> thanks fpr your posting! :)
> 
> Ok...another USB drive mau lay around here...will see...
> Just two quick questions:
> 
> Is this ok, to preserve as much as possible of the
> settings/attributes/whatever of the files or do you anything better
> and quickier than this:
> (cd /. ; tar cf - . ) | ( cd /. ; tar xvpsf - )
> ?

Don't forget to add the permissions on the source side:

tar --xattrs -cvpf . 
And maybe also add "--xattrs" on the target side.

Other options:
# rsync (not fully certain about options)
# cd  ; cp -a  .

I never did any timing, but logic tells me using the "cp" option is quicker 
(as it is all on the same system)

--
Joost

[gentoo-user] Suddenly gcc fails to compile anything...

[Meino . Cramer]

Hi,

after installing / updateing 122 package (first sync/update of the new
gentoo installation), gcc is no longer able to compile stuff
(according to configure) -- problem is always the same:

Thread model: posix
gcc version 5.4.0 (Gentoo 5.4.0-r3 p1.3, pie-0.6.5) 
configure:3882: $? = 0
configure:3871: x86_64-pc-linux-gnu-gcc -V >&5
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-V'
x86_64-pc-linux-gnu-gcc: fatal error: no input files
compilation terminated.
configure:3882: $? = 1
configure:3871: x86_64-pc-linux-gnu-gcc -qversion >&5
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option '-qversion'
x86_64-pc-linux-gnu-gcc: fatal error: no input files
compilation terminated.


I have no idea, where this "-V' and '-qversion' results from...my
make.conf looks like this:
# These are the USE and USE_EXPAND flags that were used for
# buidling in addition to what is provided by the profile.
USE="bindist"
CPU_FLAGS_X86="mmx mmxext sse3"
PORTDIR="/usr/portage"
DISTDIR="${PORTDIR}/distfiles"
PKGDIR="${PORTDIR}/packages"

# mcc added initially 
ACCEPT_KEYWORDS="~amd64"
MAKEOPT="-j7"
VIDEO_CARDS="nvidia"
NOCOLOR=true
INPUT_DEVICE=evdev
PORTAGE_ELOG_SYSTEM="save"
PORTAGE_ELOG_CLASSES="warn error info log qa"
FEATURES=splitdebug
PORTAGE_BZIP2_COMMAND="bzip2"

Cheers
Meino

Re: [gentoo-user] A new gentoo ... how to check before delete the old one?

[Meino . Cramer]

J. Roeleveld  [17-02-05 08:44]:
> On February 5, 2017 6:26:27 AM GMT+01:00, meino.cra...@gmx.de wrote:
> >Hi,
> >
> >since my old Gentoo installation seems to be screwed up (regarding
> >the update process) beyond repair I decided to install a new one
> >instead of waiting for help.
> >
> >I already made space at a certain of my harddisk and installed the
> >stage3 there.
> >Chrooting is one of the first steps to check, whether what I have
> >done so is valid.
> >
> >But before deleting the old root and install the new one at its
> >place I would like to do a atmost identical boot into the new
> >root.
> >
> >As far as I know the kernel only allows to boot into a partition
> >(instead of a directory on a partition containing the root
> >installation) and I am still using devices to boot from instead
> >of GPT.
> >
> >Is there any neat trick to do a real boot into the new root via
> >the normal boot process (grub2) nevertheless ?
> >
> >Cheers
> >Meino
> 
> If I understand correctly. The answer is no. (Unless you write some clever 
> initramfs)
> 
> Afaik, the kernel takes the entire partition and mounts it at '/'. If you 
> want it to use a directory (which would then be at '/newinstall') you need to 
> get the kernel to chroot into that directory and run init in there.
> 
> Only option I see is to use an extra disk. Maybe a USB drive and use that.
> 
> --
> Joost
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> 

Hi Joost,

thanks fpr your posting! :)

Ok...another USB drive mau lay around here...will see...
Just two quick questions:

Is this ok, to preserve as much as possible of the
settings/attributes/whatever of the files or do you anything better
and quickier than this:
(cd /. ; tar cf - . ) | ( cd /. ; tar xvpsf - )
?

Cheers
Meino