[gentoo-dev] emerge world --emptytree problems

[gentoo-dev] emerge world --emptytree problems

[Andreas Kotowicz]

Hi,

I just did a "emerge --update world --emptytree" and due to a time sync
it stopped after about 90% of all packages (and 1 day of compiling). If
I now rerun "emerge --update world --emptytree" it wants to recompile
the whole thing again. why doesn't it write down to some file which
packages have been finished so the remaining ones can be done? or is
this maybe a bug - or even wanted?

andreas

[gentoo-dev] webmin testing

[Ken Nowack]

Hey all,

Been testing webmin, just wanted to let whoever the
package maintainer is that Net-SSLeay should be
installed by default if it is not already installed on
the host system. Otherwise you get a base install with
no SSL support. Can 'ya add that to the ebuild please.

Apart from that, the package appears to be working
very well. I haven't had any issues with it at all.

Thanks,

Ken

__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com

Re: [gentoo-dev] emerge world --emptytree problems

[Paul de Vrieze]

On Wednesday 10 July 2002 21:24, Andreas Kotowicz wrote:
> Hi,
>
> I just did a "emerge --update world --emptytree" and due to a time sync
> it stopped after about 90% of all packages (and 1 day of compiling). If
> I now rerun "emerge --update world --emptytree" it wants to recompile
> the whole thing again. why doesn't it write down to some file which
> packages have been finished so the remaining ones can be done? or is
> this maybe a bug - or even wanted?
>

It is "predictable" behaviour and such not a bug. What you could do is get a 
list of everything to be included in the compile, and put it in a file (after 
removing the colors)
Then you could make some smart grep on the emerge log (you did log, didn't you 
;-) ) to check everything that has allready been compiled. Subtract those 
files (remove every compiled package from the world file) and supposed the 
filename is TOBUILD you do a
emerge `cat TOBUILD`

Paul

ps. I thought renaming the /var/db/pkg directory and doing an emerge -u world 
should also work, but for me (the pretend) it only wants to emerge system.
Could that be a bug?


-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

Re: [gentoo-dev] emerge world --emptytree problems

[Chad Huneycutt]

Paul de Vrieze wrote:
> On Wednesday 10 July 2002 21:24, Andreas Kotowicz wrote:
>>I just did a "emerge --update world --emptytree" and due to a time sync
>>it stopped after about 90% of all packages (and 1 day of compiling). If
>>I now rerun "emerge --update world --emptytree" it wants to recompile
>>the whole thing again. why doesn't it write down to some file which
>>packages have been finished so the remaining ones can be done? or is
>>this maybe a bug - or even wanted?
> 
> It is "predictable" behaviour and such not a bug. What you could do is get a 
> list of everything to be included in the compile, and put it in a file (after 
> removing the colors)
> Then you could make some smart grep on the emerge log (you did log, didn't you 
> ;-) ) to check everything that has allready been compiled. Subtract those 
> files (remove every compiled package from the world file) and supposed the 
> filename is TOBUILD you do a
> emerge `cat TOBUILD`

If you don't have a log, you can probably figure out which packages to 
exclude by doing an mtime-based find on /var/db/pkg.  Then you should be 
able to see the 10% that need to be rebuilt.

-- 
Chad Huneycutt