* ERROR: unity-base/compiz-0.9.9_p0_p01-r1 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=unity-base/compiz-0.9.9_p0_p01-r1'`,
* the complete build log and the output of `emerge -pqv '=unity-base/compiz-0.9.9_p0_p01-r1'`.
* This ebuild is from an overlay named 'unity-gentoo': '/var/lib/layman/unity-gentoo/'
* The complete build log is located at '/var/tmp/portage/unity-base/compiz-0.9.9_p0_p01-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/unity-base/compiz-0.9.9_p0_p01-r1/temp/environment'.
* Working directory: '/var/tmp/portage/unity-base/compiz-0.9.9_p0_p01-r1/work/compiz-0.9.9_p0_p01_build'
* S: '/var/tmp/portage/unity-base/compiz-0.9.9_p0_p01-r1/work/compiz-0.9.9~daily13.04.18.1~13.04'

Does not matter it is compilet with -j1 or -j5. The result is the same.

I have tried rebuild boost and every package depends on boost. The result is the same.

The strange thing is that, on my machine I was able to compile this package a few weeks ago.

I appreciate your help!

Ok, I found the solution. It requires 1.52.0-r6 from boost. Thanks for Google for I have found some hints maybe boost the root issue._________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

I would like to ask about network management in unity. I put together a system on my girlfriend's laptop because she is fed up with Ubuntu. But there is no nm-applet available on the tray - vertical menu. If I open the "Network" software then it says that my system is not compatible. If I open the Network Connections then I'm not able to add or change anything because everything is inactive.

My girlfriend is working on her laptop and she is moving everywhere and I really want her to suffer with scripts. I want her to use a good applet which helps her to find a wireless network and connect to it easily.

At the moment, I'm happy with this configuration. But, the eager-beaver question is that it is okay? Should I keep my eyes on it and try the version combination how they re not going to block each other?_________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

I can see that there are new packages in the unity overlay. And at the moment I am a middle of something very strange thing because it looks like I have to manage gnome compile issues, I think, based on version collisions and differences.

I would like to know what is the suggested way to handle the new packages coming from unity overlay? Try to emerge them as soon as possible or wait for a signal from the maintainer?_________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

I can see that there are new packages in the unity overlay. And at the moment I am a middle of something very strange thing because it looks like I have to manage gnome compile issues, I think, based on version collisions and differences.

I would like to know what is the suggested way to handle the new packages coming from unity overlay? Try to emerge them as soon as possible or wait for a signal from the maintainer?

They have unmasked gnome-3.8. This seems to clash with our overlay. All overlay packages masked with ** are for the upcoming Saucy release which is not ready yet. We have to check how we solve that.

I can see that there are new packages in the unity overlay. And at the moment I am a middle of something very strange thing because it looks like I have to manage gnome compile issues, I think, based on version collisions and differences.

I would like to know what is the suggested way to handle the new packages coming from unity overlay? Try to emerge them as soon as possible or wait for a signal from the maintainer?

They have unmasked gnome-3.8. This seems to clash with our overlay. All overlay packages masked with ** are for the upcoming Saucy release which is not ready yet. We have to check how we solve that.

Thanks for the answer! I'm looking forward to the solutions! You guys are doing a great job!_________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

I can see that there are new packages in the unity overlay. And at the moment I am a middle of something very strange thing because it looks like I have to manage gnome compile issues, I think, based on version collisions and differences.

I would like to know what is the suggested way to handle the new packages coming from unity overlay? Try to emerge them as soon as possible or wait for a signal from the maintainer?

They have unmasked gnome-3.8. This seems to clash with our overlay. All overlay packages masked with ** are for the upcoming Saucy release which is not ready yet. We have to check how we solve that.

Ok, the question is that then what is the gnome version which do not clash with unity-overlay, 3.6?_________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

I can see that there are new packages in the unity overlay. And at the moment I am a middle of something very strange thing because it looks like I have to manage gnome compile issues, I think, based on version collisions and differences.

I would like to know what is the suggested way to handle the new packages coming from unity overlay? Try to emerge them as soon as possible or wait for a signal from the maintainer?

They have unmasked gnome-3.8. This seems to clash with our overlay. All overlay packages masked with ** are for the upcoming Saucy release which is not ready yet. We have to check how we solve that.

Ok, the question is that then what is the gnome version which do not clash with unity-overlay, 3.6?

It looks like I could manage it. It required a little action and mask and unmask a few packages, a few hours recompiling and now... possible to compile the unity packages. _________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

Ok, I've changed the unity-portage.p* files so you should stay at gnome-3.6 for unity. I hope I've found all gnome-3.8 packages to mask them.

If you see any 'Multiple package instances within a single package slot', check for a line as like as (x11-libs/gtk+-3.8.2_p3_p02::unity-gentoo, ebuild scheduled for merge) pulled in by. You should see the gnome-3.8 package which is still unmasked.

For instance:

Code:

(x11-libs/gtk+-3.8.2_p3_p02::unity-gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/gtk+-3.7.10:3[introspection?] required by (media-video/totem-3.8.2-r1::gentoo, ebuild scheduled for merge)

Check your own files in /etc/portage if you have unmasked by your own. If not, let me know so I can mask it over unity-portage.pkeywords

Ok, I've changed the unity-portage.p* files so you should stay at gnome-3.6 for unity. I hope I've found all gnome-3.8 packages to mask them.

If you see any 'Multiple package instances within a single package slot', check for a line as like as (x11-libs/gtk+-3.8.2_p3_p02::unity-gentoo, ebuild scheduled for merge) pulled in by. You should see the gnome-3.8 package which is still unmasked.

For instance:

Code:

(x11-libs/gtk+-3.8.2_p3_p02::unity-gentoo, ebuild scheduled for merge) pulled in by
>=x11-libs/gtk+-3.7.10:3[introspection?] required by (media-video/totem-3.8.2-r1::gentoo, ebuild scheduled for merge)

Check your own files in /etc/portage if you have unmasked by your own. If not, let me know so I can mask it over unity-portage.pkeywords

Many thanks!

What I did: I cleaned up my mask and unmask files to see the behavior of your update. You can find below the list I had to add to have Unity working.

On the other hand, what about systemd? In the portage tree systemd and consolekit are conflicting. However, consolekit are not maintained anymore.

As far as I know and I experienced in the last two days Gnome-3.8 forcing systemd. According to a few information I got on the gentoo mailing list Unity does not use systemd, they use upstart or something like this._________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

>>> Installing (2 of 2) gnome-base/gnome-session-3.6.2_p0_p05-r1
* Removing /usr/share/info
* Removing /usr/share/doc
* checking 35 files for package collisions
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at http://bugs.gentoo.org unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/share/xsessions/gnome-fallback-compiz.desktop
* /usr/share/xsessions/gnome-fallback.desktop
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* gnome-base/gnome-panel-3.6.2_p0_p11:0::unity-gentoo
* /usr/share/xsessions/gnome-fallback-compiz.desktop
* /usr/share/xsessions/gnome-fallback.desktop
*
* Package 'gnome-base/gnome-session-3.6.2_p0_p05-r1' NOT merged due to
* file collisions. If necessary, refer to your elog messages for the
* whole content of the above message

On the other hand, what about systemd? In the portage tree systemd and consolekit are conflicting. However, consolekit are not maintained anymore.

As far as I know and I experienced in the last two days Gnome-3.8 forcing systemd. According to a few information I got on the gentoo mailing list Unity does not use systemd, they use upstart or something like this.

shiznix is experimenting with systemd and (saucy) Unity. I don't know about the outcome.

The current (raring) Unity relates on gnome-3.6. So I've no idea if it will work fine with gnome-3.8

>>> Installing (2 of 2) gnome-base/gnome-session-3.6.2_p0_p05-r1
* Removing /usr/share/info
* Removing /usr/share/doc
* checking 35 files for package collisions
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at http://bugs.gentoo.org unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/share/xsessions/gnome-fallback-compiz.desktop
* /usr/share/xsessions/gnome-fallback.desktop
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* gnome-base/gnome-panel-3.6.2_p0_p11:0::unity-gentoo
* /usr/share/xsessions/gnome-fallback-compiz.desktop
* /usr/share/xsessions/gnome-fallback.desktop
*
* Package 'gnome-base/gnome-session-3.6.2_p0_p05-r1' NOT merged due to
* file collisions. If necessary, refer to your elog messages for the
* whole content of the above message

What to do?

'gnome-base/gnome-panel' and 'gnome-base/gnome-session' installing the same files. That's strange, I've never seen it on my systems

>>> Installing (2 of 2) gnome-base/gnome-session-3.6.2_p0_p05-r1
* Removing /usr/share/info
* Removing /usr/share/doc
* checking 35 files for package collisions
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at http://bugs.gentoo.org unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/share/xsessions/gnome-fallback-compiz.desktop
* /usr/share/xsessions/gnome-fallback.desktop
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* gnome-base/gnome-panel-3.6.2_p0_p11:0::unity-gentoo
* /usr/share/xsessions/gnome-fallback-compiz.desktop
* /usr/share/xsessions/gnome-fallback.desktop
*
* Package 'gnome-base/gnome-session-3.6.2_p0_p05-r1' NOT merged due to
* file collisions. If necessary, refer to your elog messages for the
* whole content of the above message

What to do?

'gnome-base/gnome-panel' and 'gnome-base/gnome-session' installing the same files. That's strange, I've never seen it on my systems

Yes, they wants to install the same files. Once I met issue like this. It was reported in the BGO and later it was fixed. Since this overlay is not part of the official tree only this place is where I can report this issue. On the other hand, the result of this is that either package will not be installed. I'm afraid if I install a very close version from the portage tree then I will not have the Unity patches and it may result a compiling issue or something will not work._________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

Yes, they wants to install the same files. Once I met issue like this. It was reported in the BGO and later it was fixed. Since this overlay is not part of the official tree only this place is where I can report this issue. On the other hand, the result of this is that either package will not be installed. I'm afraid if I install a very close version from the portage tree then I will not have the Unity patches and it may result a compiling issue or something will not work.

You can report it here or even as issue in the repository at github.
But I didn't see ever a problem with both packages.
The overlay masked all ::gentoo packages which are patched for Unity. In normal cases you should not be able to install them.

Yes, they wants to install the same files. Once I met issue like this. It was reported in the BGO and later it was fixed. Since this overlay is not part of the official tree only this place is where I can report this issue. On the other hand, the result of this is that either package will not be installed. I'm afraid if I install a very close version from the portage tree then I will not have the Unity patches and it may result a compiling issue or something will not work.

You can report it here or even as issue in the repository at github.
But I didn't see ever a problem with both packages.
The overlay masked all ::gentoo packages which are patched for Unity. In normal cases you should not be able to install them.

Can you please unmerge both packages and remerge them again?

The result is the same. Does not matter the package order during re-emerge. Either one collide with the other. _________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

I decided to clean up my system from Gnome and Unity stuff to have a clean base. Jesus, what a mess!

I have been promised to myself I never ever in my life not going to touch gnome stuff, and I need a few day to rest not to promise it again._________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

1) you have to mask 'net-libs/webkit-gtk-2.0.4'. It's needed for gnome-3.8. It seems you have unmasked it by yourself.
2) The same with 'gnome-base/gnome-panel-3.6.2_p0_p11'. That's the 'saucy' version which should not be used atm. Please use 'gnome-base/gnome-panel-3.6.2-r1' from gentoo for the current Unity.

1) you have to mask 'net-libs/webkit-gtk-2.0.4'. It's needed for gnome-3.8. It seems you have unmasked it by yourself.
2) The same with 'gnome-base/gnome-panel-3.6.2_p0_p11'. That's the 'saucy' version which should not be used atm. Please use 'gnome-base/gnome-panel-3.6.2-r1' from gentoo for the current Unity.

(x11-libs/gtk+-3.8.2::gentoo, installed) pulled in by
>=x11-libs/gtk+-3.8.0:3[cups?] required by (gnome-base/gnome-core-libs-3.8.0::gentoo, ebuild scheduled for merge)
(and 2 more with the same problem)

According to my previous experience with Unity install and Gnome-3.8 upgrade-downgrade hell I think I have to mask packages until there is no gnome-3.8 and/or gtk-3.8 related stuff, am I right?
On the other hand, Gnome/Unity stuff compared to KDE install is a hell because there are no clear and straightforward package versions which can provide you clear information about the set or version where it is belongs to._________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell

Sorry you and others had to bear the brunt of gnome-3.8's introduction into the main tree and the havoc it has temporarily caused the overlay.

Not the fault of the Gnome team, but totally down to me not keyword unmasking gnome-3.6 by version but blindly relying on it's keyword state instead.
So instead of for example having 'gnome-base/gnome-core-libs' in the unity-portage.pkeywords file, I should have had '=gnome-base/gnome-core-libs-3.6*'.
In this way, gnome-3.8 would have been released but caused zero effect on the stability of the Raring stream of packages.

Please sync up the overlay as the latest commit should complete this process.
Thanks for using unity-gentoo

Sorry you and others had to bear the brunt of gnome-3.8's introduction into the main tree and the havoc it has temporarily caused the overlay.

Not the fault of the Gnome team, but totally down to me not keyword unmasking gnome-3.6 by version but blindly relying on it's keyword state instead.
So instead of for example having 'gnome-base/gnome-core-libs' in the unity-portage.pkeywords file, I should have had '=gnome-base/gnome-core-libs-3.6*'.
In this way, gnome-3.8 would have been released but caused zero effect on the stability of the Raring stream of packages.

Please sync up the overlay as the latest commit should complete this process.
Thanks for using unity-gentoo

Thank you very much! I'm happy to use unity-gentoo overlay, because this stuff, I mean Unity, is very usable. On the other hand, you do a great job!
I do my best not to drive you crazy. _________________- -
-- Csanyi Andras/Sayusi Ando --
-- "Trust in God and keep the gunpowder dry!!" - Cromwell