public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Ruskin <aoyu93@dsl.pipex.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why does emerge give up too easily?
Date: Sun, 1 Dec 2002 18:19:21 +0000	[thread overview]
Message-ID: <200212011819.21739.aoyu93@dsl.pipex.com> (raw)
In-Reply-To: <3DEA1974.4060800@foser.warande.net>

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


  reply	other threads:[~2002-12-01 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-01 12:28 [gentoo-dev] Why does emerge give up too easily? Peter Ruskin
2002-12-01 14:15 ` foser
2002-12-01 18:19   ` Peter Ruskin [this message]
2002-12-01 18:18     ` foser
     [not found]       ` <200212020913.42688.tharkun@upb.de>
2002-12-02 12:54         ` foser
2002-12-02 18:14       ` Alexander Gretencord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200212011819.21739.aoyu93@dsl.pipex.com \
    --to=aoyu93@dsl.pipex.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox