[gentoo-user] emerge wants to rebuild a lot again

[gentoo-user] emerge wants to rebuild a lot again

[Peter]

Today, I got a lot of rebuild requests from emerge after doing:

emerge -puDvt --newuse world

I spot checked a couple of builds, but nothing has changed! Can you help
decipher the following please:

Using the first application that shows up as an example:

[ebuild   R   ] sys-apps/diffutils-2.8.7-r1  USE="nls -static (-debug%)" 1,037 kB

What does (-debug%) mean? Here is the equery output:

[ Found these USE variables for sys-apps/diffutils-2.8.7-r1 ]
 U I
 - - debug  : Tells configure and the makefiles to build for debugging. Effects vary across packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES=nostrip too
 + + nls    : Adds Native Language Support (using gettext - GNU locale utilities)
 - - static : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically

Ideas? Is it because the -debug variable has been removed from somewhere?

Thx

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge wants to rebuild a lot again

[Boris Fersing]

2006/9/11, Peter <sw98234@hotmail.com>:
> Today, I got a lot of rebuild requests from emerge after doing:
>
> emerge -puDvt --newuse world
>
> I spot checked a couple of builds, but nothing has changed! Can you help
> decipher the following please:
>
> Using the first application that shows up as an example:
>
> [ebuild   R   ] sys-apps/diffutils-2.8.7-r1  USE="nls -static (-debug%)" 1,037 kB
>
> What does (-debug%) mean? Here is the equery output:
>
> [ Found these USE variables for sys-apps/diffutils-2.8.7-r1 ]
>  U I
>  - - debug  : Tells configure and the makefiles to build for debugging. Effects vary across packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES=nostrip too
>  + + nls    : Adds Native Language Support (using gettext - GNU locale utilities)
>  - - static : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically
>
> Ideas? Is it because the -debug variable has been removed from somewhere?

Hi,

did you install portage-2.1.1 ?

Portage has now a new feature, it re-emerges a package when the IUSE
variable has changed :

 * In portage-2.1.1, emerge --newuse is now sensitive to changes in IUSE.
 * Immediately after upgrade from 2.1, users may notice a significantly larger
 * number of packages pulled in by --newuse, but that behavior is normal.
 * For additional information regarding this change, please see bugs #116955,
 * #144333, #144661, and #146060.
>
> Thx
>

HTH.

Boris.
> --
> Peter
> +++++
> Do not reply to this email, it is a spam trap and not monitored.
> I can be reached via this list, or via
> jabber: pete4abw at jabber.org
> ICQ: 73676357
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
Quiconque me parle de Dieu en veut à ma bourse ou à ma liberté.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge wants to rebuild a lot again

[Etaoin Shrdlu]

On Monday 11 September 2006 13:16, Peter wrote:

> Today, I got a lot of rebuild requests from emerge after doing:
>
> emerge -puDvt --newuse world
>
> I spot checked a couple of builds, but nothing has changed!

If you updated portage, maybe the reason is this:

In portage-2.1.1, emerge --newuse is now sensitive to changes in IUSE.
Immediately after upgrade from 2.1, users may notice a significantly 
larger number of packages pulled in by --newuse, but that behavior is 
normal. For additional information regarding this change, please see 
bugs #116955, #144333, #144661, and #146060.

(taken from the output of "emerge portage" when upgrading).
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: emerge wants to rebuild a lot again

[Nico]

[-- Attachment #1: Type: text/plain, Size: 244 bytes --]

>
> yes, that was it. Unfortunately, the messages scroll by quickly and I did
> not have a chance to read it.


Configure the elog system, see /etc/make.conf.example. You'll be able to
read main warnings in the /var/log/portage/elog (default).

[-- Attachment #2: Type: text/html, Size: 400 bytes --]