[gentoo-dev] Why does emerge give up too easily?

[gentoo-dev] Why does emerge give up too easily?

[Peter Ruskin]

# emerge -pu world

These are the packages that I would merge, in order.

Calculating world dependencies /

emerge: all ebuilds that could satisfy ">=x11-libs/gtk+-2.1.2" (from 
ebuild / net-www/mozilla-1.2 merge) have been masked.

...but there *are* other packages that could be emerged :-(

Peter
-- 
Gentoo Linux 1.4 (Portage 2.0.44 (default-x86-1.4, gcc-3.2.1, 
glibc-2.3.1-r2)).  KDE: 3.0.99 (KDE 3.1 RC3)  Qt: 3.1.0
AMD Athlon(tm) XP 1900+ 512MB.	Kernel: 2.4.20-win4lin.	GCC 3.2.1
Linux user #275590 (http://counter.li.org/).  up 1:10.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Why does emerge give up too easily?

[foser]

Peter Ruskin wrote:
> # emerge -pu world
> 
> These are the packages that I would merge, in order.
> 
> Calculating world dependencies /
> 
> emerge: all ebuilds that could satisfy ">=x11-libs/gtk+-2.1.2" (from 
> ebuild / net-www/mozilla-1.2 merge) have been masked.
> 
> ...but there *are* other packages that could be emerged :-(
> 

USE=-gtk2 emerge mozilla

The gtk2 port needs some unstable stuff, which i wouldn't recommend 
right now.


And emerge giving up: what is the use of installing other stuff when you 
don't have one dep.

- foser


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Why does emerge give up too easily?

[foser]

Peter Ruskin wrote:

> My point is that I will probably be able to emerge, for example, 
> sane-backends separately, but if the first package in "These are the 
> packages that I would merge, in order" fails, the `emerge -u world` 
> command is thereafter useless.  Why won't it skip failures?
> 

Because the other packages may still depend on it (eg. Galeon-1.2.7 
depends on mozilla-1.2).

If you choose to use unstable stuff atm you have to stop using -u world, 
because it most likely will downgrade stuff.

- foser


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Why does emerge give up too easily?

[Peter Ruskin]

On Sunday 01 Dec 2002 14:15, foser wrote:
> Peter Ruskin wrote:
> > # emerge -pu world
> >
> > These are the packages that I would merge, in order.
> >
> > Calculating world dependencies /
> >
> > emerge: all ebuilds that could satisfy ">=x11-libs/gtk+-2.1.2" (from
> > ebuild / net-www/mozilla-1.2 merge) have been masked.
> >
> > ...but there *are* other packages that could be emerged :-(
>
> USE=-gtk2 emerge mozilla

Thanks ... but see below
>
> The gtk2 port needs some unstable stuff, which i wouldn't recommend
> right now.
>
>
> And emerge giving up: what is the use of installing other stuff when
> you don't have one dep.
>
# emerge -pu world

These are the packages that I would merge, in order.

Calculating world dependencies ...done!
[ebuild    U ] net-www/mozilla-1.2
[ebuild    U ] gnome-base/gconf-1.0.8-r4
[ebuild    U ] net-www/galeon-1.2.7
[ebuild    U ] gnome-base/libgnomeui-2.0.6-r1
[ebuild    U ] gnome-base/gdm-2.4.0.12-r1
[ebuild    U ] dev-util/kdevelop-3.0_alpha2
[ebuild    U ] app-editors/nano-1.0.9-r2
[ebuild    U ] dev-perl/XML-RegExp-0.03-r1
[ebuild    U ] sys-libs/libieee1284-0.2.1
[ebuild    U ] media-gfx/sane-backends-1.0.9
[ebuild    U ] media-gfx/sane-frontends-1.0.9

# emerge -u world
Calculating world dependencies ...done!
>>> emerge (1 of 11) net-www/mozilla-1.2 to /
>>> md5 ;-) mozilla-source-1.2.tar.bz2
>>> md5 ;-) fcpackage.2_0.tar.gz
>>> Unpacking source...
>>> Unpacking mozilla-source-1.2.tar.bz2
>>> Unpacking fcpackage.2_0.tar.gz
 * Applying mozilla-1.2-branch-update.patch.bz2...

 * Failed Patch: mozilla-1.2-branch-update.patch.bz2!
 *
 * Include in your bugreport the contents of:
 *
 *   
/var/tmp/portage/mozilla-1.2/temp/mozilla-1.2-branch-update.patch.bz2-30030.out


!!! ERROR: net-www/mozilla-1.2 failed.
!!! Function epatch, Line 300, Exitcode 0
!!! Failed Patch: mozilla-1.2-branch-update.patch.bz2!

My point is that I will probably be able to emerge, for example, 
sane-backends separately, but if the first package in "These are the 
packages that I would merge, in order" fails, the `emerge -u world` 
command is thereafter useless.  Why won't it skip failures?

Peter
-- 
Gentoo Linux 1.4 (Portage 2.0.44 (default-x86-1.4, gcc-3.2.1, 
glibc-2.3.1-r2)).  KDE: 3.0.99 (KDE 3.1 RC3)  Qt: 3.1.0
AMD Athlon(tm) XP 1900+ 512MB.	Kernel: 2.4.20-win4lin.	GCC 3.2.1
Linux user #275590 (http://counter.li.org/).  up 6:55.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Why does emerge give up too easily?

[foser]

Alexander Gretencord wrote:
> You are right, _may_, so portage should check _if_ the failed ebuild is a dep 
> for a package down in the chain and if not continue with it.

Maybe, from a portage pov i don't think that's easy to implement. Maybe 
in an ideal situation, but then you should also know what packages 
failed and why and which packages are affected.

 > This has nothing
> to do with unstable, as gentoo is bleeding edge this can even and has 
> happened to "stable" packages...

Bleeding edge is no excuse for failing packages, fyi mozilla-1.2 is 
masked and so is galeon-1.2.7 .

- foser



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Why does emerge give up too easily?

[Alexander Gretencord]

On Sunday 01 December 2002 19:18, foser wrote:
> Peter Ruskin wrote:
> > My point is that I will probably be able to emerge, for example,
> > sane-backends separately, but if the first package in "These are the
> > packages that I would merge, in order" fails, the `emerge -u world`
> > command is thereafter useless.  Why won't it skip failures?
>
> Because the other packages may still depend on it (eg. Galeon-1.2.7
> depends on mozilla-1.2).

But then portage should be able to check if an ebuild in the chain has the 
failed package as a dep and only leave those deps and that ebuild alone and 
merge the rest which does not have a failed package as a dep (or a package 
that will fail because of the failed dep)


Alex

-- 
"They that can give up essential liberty to obtain a little temporary safety 
deserve neither liberty nor safety."
Benjamin Franklin


--
gentoo-dev@gentoo.org mailing list