[gentoo-user] issue on binary merge

[gentoo-user] issue on binary merge

[Sascha Lucas]

Hi List,

can some explain this? Machine A+B have identical make.conf (expect in 3 
USE-falgs), /etc/portage/*, /usr/portage, profile.

Machine A:
  - FEATURES="buildpkg"
  - added USE-flag "samba"
  - emerge -uD --newuse world
    * builds new samba package
    * rebuilds some packages (kdebase, cups, mplayer etc.)

Machine B:
  - mount PGKDIR of machine A via nfs to PGKDIR on machine B
  - added USE-flag "samba"
  - emerge -uD --newuse --usepkg world
    * merges binary samba
    * does not merge anything else (no binary, no ebuild )

It would be nice if I understand why emerge won't remerge binary packages 
with changed use-flags.

THX,

Sascha.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Nick Rout]

On Wed, 2005-09-07 at 18:33 +0200, Sascha Lucas wrote:
> Hi List,
> 
> can some explain this? Machine A+B have identical make.conf (expect in 3 
> USE-falgs), /etc/portage/*, /usr/portage, profile.
> 
> Machine A:
>   - FEATURES="buildpkg"
>   - added USE-flag "samba"
>   - emerge -uD --newuse world
>     * builds new samba package
>     * rebuilds some packages (kdebase, cups, mplayer etc.)
> 
> Machine B:
>   - mount PGKDIR of machine A via nfs to PGKDIR on machine B
>   - added USE-flag "samba"
>   - emerge -uD --newuse --usepkg world
>     * merges binary samba
>     * does not merge anything else (no binary, no ebuild )
> 
> It would be nice if I understand why emerge won't remerge binary packages 
> with changed use-flags.

It doesn't know that kdebase, cups etc need rebuilding unless you use
the --newuse option


> 
> THX,
> 
> Sascha.
> 
-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Sascha Lucas]

>> Machine B:
>>   - mount PGKDIR of machine A via nfs to PGKDIR on machine B
>>   - added USE-flag "samba"
>>   - emerge -uD --newuse --usepkg world
>>     * merges binary samba
>>     * does not merge anything else (no binary, no ebuild )
>>
>> It would be nice if I understand why emerge won't remerge binary packages
>> with changed use-flags.
>
> It doesn't know that kdebase, cups etc need rebuilding unless you use
> the --newuse option

well on Machine B I did emerge -uD --newuse --usepkg world. Isn't it what 
you ment?

Sascha.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Ian Clowes]

Sascha Lucas wrote:
> 
> Hi List,
> 
> Machine B:
>   - mount PGKDIR of machine A via nfs to PGKDIR on machine B
>   - added USE-flag "samba"
>   - emerge -uD --newuse --usepkg world
>     * merges binary samba
>     * does not merge anything else (no binary, no ebuild )
> 
> It would be nice if I understand why emerge won't remerge binary packages
> with changed use-flags.

Hi Sascha

If you do --pretend --verbose, does it show the changed USE flags for
the packages?  Not sure if 'world' does this, but you could try the
individual packages that you expect to be rebuilt.  IIRC, it appears in
green (on a colour screen...) with a + and * next to the USE flag.

If the flags aren't shown as 'new' then its not strictly a problem with
the merge, but one with the way the flag changes are being enumerated.

If they are shown as changed then at least Portage is working out that
it would like to have new builds of the packages, and any failure is
presumably due to the way this cascades down to the binary merge
mechanism, such as the ability of a binary package to declare what USE
flags it was built with.

Not a solution, but hopefully it'll add insight.

IanC
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Sascha Lucas]

> If you do --pretend --verbose, does it show the changed USE flags for
> the packages?  Not sure if 'world' does this, but you could try the
> individual packages that you expect to be rebuilt.  IIRC, it appears in
> green (on a colour screen...) with a + and * next to the USE flag.

emerge -uD --pretend --verbose --usepkg --newuse world does not show the 
change in USE-Flags. However it installes some software cased by the new 
USE-Flag (in my example samba). I run "equery hasuse my_new_flag" and the 
merged this pkgs with:

emerge -1 --usepkg --pretend --verbose pkg_spec_from_equery

then the change in USE-Flags are showen and my _correct_ binarys are used.

> Not a solution, but hopefully it'll add insight.

it seems we are actually 2 who worked at the same time with binarys :-)

Sascha.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Ian Clowes]

Sascha Lucas wrote:
> 
> emerge -1 --usepkg --pretend --verbose pkg_spec_from_equery
> 
> then the change in USE-Flags are showen and my _correct_ binarys are used.
> 

There's probably a good reason for it being the way it is, but it
doesn't sound as transparent as we might like.

A further interesting scenario might be to have a binary package
available built with different USE flags to those on the target machine,
and seeing if it gets installed or not.  I guess it shouldn't.  But then
there's the CFLAGS issue as well, and I'm even more unsure how that's
supposed to be handled.

I'm still pretty new to Gentoo, but is this perhaps related to the
feature I've read about (and maybe misremembered) regarding only
packages that you explicity emerge going into world (dependencies
don't)?  I wonder if you'd see different results if you explicitly
emerged cups rather than it having been implicity emerged due to a
dependency.  By doing the emerge you described you've 'promoted' those
packages from implicit to explicit emerge.

IanC
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Sascha Lucas]

>> emerge -1 --usepkg --pretend --verbose pkg_spec_from_equery
>>
>> then the change in USE-Flags are showen and my _correct_ binarys are used.
>>
>
> There's probably a good reason for it being the way it is, but it
> doesn't sound as transparent as we might like.

yes may be... if so, I would like to know the reason :-)


> A further interesting scenario might be to have a binary package
> available built with different USE flags to those on the target machine,
> and seeing if it gets installed or not.  I guess it shouldn't.  But then
> there's the CFLAGS issue as well, and I'm even more unsure how that's
> supposed to be handled.

If you build a binary with different USE flags then on the target it 
would be merged as ebuild and not as binary. But this seems only to work 
with --usepkg not with --getbinpkg. ?? CFLAGS handling is done in the same 
way like USE flags. You can use the tbz2tool to split your binary into 
data (tar) and info (text). In this info-text is every thing stored like 
USe, CFALGS, ....

> I'm still pretty new to Gentoo, but is this perhaps related to the
> feature I've read about (and maybe misremembered) regarding only
> packages that you explicity emerge going into world (dependencies
> don't)?  I wonder if you'd see different results if you explicitly
> emerged cups rather than it having been implicity emerged due to a
> dependency.  By doing the emerge you described you've 'promoted' those
> packages from implicit to explicit emerge.

Hm... yes every time you type emege .... it will be recorded in the 
world-file, expect emerge --oneshot (-1)... so my explicit merge will not 
be recorded in world it stays what it was before (world or dependency).

So I understand --usepkg in this way to use binary if all USE/C flags etc 
match. If not fallback to ebuilds. So I know I have the right binary pkgs, 
why does:

emerge -uDpv --newuse world

and

emerge -uDpv --newuse --usepkg world

show different results?

Sascha.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Nick Rout]

There is no meta-info AFAIK in a binary .tar.gz, so portage does NOT
know what CFLAGS, or USE flags it is built with.

Go ahead, use quickpkg to make a binary tarball of any package on your
system, then look tat the tarball. There is nothing to indicate USE or
CFLAGS.

If you want to install binaries you have to know yourself what options
were used in the compile.


On Wed, 07 Sep 2005 22:08:13 +0100
Ian Clowes wrote:

> A further interesting scenario might be to have a binary package
> available built with different USE flags to those on the target machine,
> and seeing if it gets installed or not.  I guess it shouldn't.  But then
> there's the CFLAGS issue as well, and I'm even more unsure how that's
> supposed to be handled.

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Zac Medico]

Nick Rout wrote:
> There is no meta-info AFAIK in a binary .tar.gz, so portage does NOT
> know what CFLAGS, or USE flags it is built with.
> 
> Go ahead, use quickpkg to make a binary tarball of any package on your
> system, then look tat the tarball. There is nothing to indicate USE or
> CFLAGS.
> 
> If you want to install binaries you have to know yourself what options
> were used in the compile.
> 

The metadata is appended to the end of the tbz2 file.  I guess you didn't see my email earlier today which included a script that extracts the use flags.

http://marc.10east.com/?l=gentoo-user&m=112613409500463&w=2

Zac
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Nick Rout]

On Wed, 07 Sep 2005 18:02:49 -0700
Zac Medico wrote:


> The metadata is appended to the end of the tbz2 file.  I guess you didn't see my email earlier today which included a script that extracts the use flags.
> 
> http://marc.10east.com/?l=gentoo-user&m=112613409500463&w=2
> 
> Zac

err yes, see my more recent post, thanks for correcting my
misapprehension.

Its not easy to spot the metainfo.

> -- 
> gentoo-user@gentoo.org mailing list

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] issue on binary merge

[Nick Rout]

Bugger, after reading Sacha's last post and trying tbz2tool -split
package.tbz2 I realise that the meta info is there, quite a lot of it!

You certainly don't get to see it parsing the file with mc

I was wrong, my apologies.

A tool to better parse that metainfo out of binary packages would be
good.


On Thu, 08 Sep 2005 12:17:46 +1200
Nick Rout wrote:

> There is no meta-info AFAIK in a binary .tar.gz, so portage does NOT
> know what CFLAGS, or USE flags it is built with.
> 
> Go ahead, use quickpkg to make a binary tarball of any package on your
> system, then look tat the tarball. There is nothing to indicate USE or
> CFLAGS.
> 
> If you want to install binaries you have to know yourself what options
> were used in the compile.
> 
> 
> On Wed, 07 Sep 2005 22:08:13 +0100
> Ian Clowes wrote:
> 
> > A further interesting scenario might be to have a binary package
> > available built with different USE flags to those on the target machine,
> > and seeing if it gets installed or not.  I guess it shouldn't.  But then
> > there's the CFLAGS issue as well, and I'm even more unsure how that's
> > supposed to be handled.
> 
> -- 
> Nick Rout <nick@rout.co.nz>

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list