public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Immensely disappointed in emerge -DuN world these days
Date: Thu, 13 Sep 2007 11:40:13 +0200	[thread overview]
Message-ID: <200709131140.14465.bo.andresen@zlin.dk> (raw)
In-Reply-To: <5bdc1c8b0709122041i66988d75y2ac4fcc7ecf5565e@mail.gmail.com>

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

On Thursday 13 September 2007 05:41:59 Mark Knecht wrote:
> > This latest emerge pass seems to be working better. I did have to skip
> > a couple of packages though. I'll go back and see if I can catch them
> > with revdep-rebuild when it hopefully finishes up in the next hour.
[...]
> db2omf: Could not construct the OMF maintainer element.
>   Add an author, corpauthor, editor, othercredit, or publisher
>   element with the role attribute set to "maintainer" to epiphany.xml.
> make[2]: *** [epiphany-C.omf] Error 10
> make[2]: Leaving directory
> `/var/tmp/portage/www-client/epiphany-2.16.3/work/epiphany-2.16.3/help'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/www-client/epiphany-2.16.3/work/epiphany-2.16.3'
> make: *** [all] Error 2
>
> !!! ERROR: www-client/epiphany-2.16.3 failed.

I think you either need a later version of epiphany (2.18.x) or an earlier 
version of gnome-doc-utils (0.8.x). Since epiphany-2.18.2 is latest stable 
this is probably one of those cases where the -X for revdep-rebuild would 
make the whole difference...

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-09-13  9:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 23:36 [gentoo-user] Immensely disappointed in emerge -DuN world these days Mark Knecht
2007-09-12 23:45 ` Dan Farrell
2007-09-12 23:53   ` Danilo Marcelo
2007-09-13  1:06   ` Mark Knecht
2007-09-13  1:24     ` Dan Farrell
2007-09-13  2:03       ` Mark Knecht
2007-09-13  4:02         ` Dan Farrell
2007-09-13  6:10         ` [gentoo-user] " Alexander Skwar
2007-09-13  2:54     ` [gentoo-user] " Mark Knecht
2007-09-13  3:09       ` Bo Ørsted Andresen
2007-09-13  3:23         ` Mark Knecht
2007-09-13  3:33           ` Bo Ørsted Andresen
2007-09-13  3:58         ` Dan Farrell
2007-09-13  9:32           ` Bo Ørsted Andresen
2007-09-13 15:28             ` Dan Farrell
2007-09-13  3:22     ` Iain Buchanan
2007-09-13  3:32       ` Mark Knecht
2007-09-13  3:48         ` Bo Ørsted Andresen
2007-09-13  6:13         ` [gentoo-user] " Alexander Skwar
2007-09-13  3:41     ` [gentoo-user] " Mark Knecht
2007-09-13  9:40       ` Bo Ørsted Andresen [this message]
2007-09-13  6:09     ` [gentoo-user] " Alexander Skwar
2007-09-13  0:04 ` [gentoo-user] " Bo Ørsted Andresen
2007-09-13  7:57 ` Daevid Vincent
2007-09-13  8:59   ` Neil Bothwick
2007-09-13  9:46     ` Volker Armin Hemmann
2007-09-13 15:02       ` Neil Bothwick
2007-09-13 16:05     ` Marzan, Richard non Unisys
2007-09-13 16:29       ` Neil Bothwick
2007-09-13 20:14         ` Marzan, Richard non Unisys
2007-09-14 16:50           ` Mark Knecht
2007-09-13  9:55   ` Benno Schulenberg

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=200709131140.14465.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --cc=gentoo-user@lists.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