public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Ausmus" <james.ausmus@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Please explain why this new 'emerge @preserved-rebuild' is good?
Date: Thu, 8 Jan 2009 11:23:24 -0800	[thread overview]
Message-ID: <b79f23070901081123u33b6a551jffb918a62e1e4ce@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0901081055y18f26d7fy38c28a86de7184c3@mail.gmail.com>

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

On Thu, Jan 8, 2009 at 10:55 AM, Mark Knecht <markknecht@gmail.com> wrote:

> On Thu, Jan 8, 2009 at 10:24 AM, Mark Knecht <markknecht@gmail.com> wrote:
> > On Thu, Jan 8, 2009 at 10:07 AM, James Ausmus <james.ausmus@gmail.com>
> wrote:
> > <SNIP>
> >>>
> >>> Right now I'm seeing that @preserved-rebuild and revdep-rebuild want
> >>> to do different things. revdep-rebuild is rebuilding nss which may or
> >>> may not fail. @preserved-rebuild wanted to rebuild eveolution which
> >>> did fail.
> >>
> >> I would suggest performing the revdep-rebuild first, then doing the
> >> @preserved-rebuild - if revdep-rebuild is coming up with broken
> packages,
> >> those broken packages can actually prevent other packages (such as
> >> evolution) from building properly.
> >> -James
> >>
> >
> > We'll see how it works out. I've done the revdep-rebuild.
> > @preserved-rebuild failed last night but is running again. If it
> > continues to fail I'll file a bug report.
> >
> > I don't use evolution. It's just caught up in the emerge gnome stuff
> > and the gnome-light construct stopped working a while back so
> > evolution has been there not causing trouble (other than build
> > time/disk space) until now.
> >
> > - Mark
> >
> And the emerge of evolution failed as it did last night so in this
> case the revdep-rebuild didn't matter.
>
> Interesting that the evolution build fails for the package name (nss)
> that revdep-rebuild just rebuilt:
>
>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:
> warning: libsoftokn3.so.11, needed by /usr/lib64/nss/libnss3.so.11,
> not found (try using -rpath or -rpath-link)
> /usr/lib64/nss/libnss3.so.11: undefined reference to
> `FC_GetFunctionList@NSS_3.4'
> /usr/lib64/nss/libnss3.so.11: undefined reference to
> `NSC_ModuleDBFunc@NSS_3.4'
> /usr/lib64/nss/libnss3.so.11: undefined reference to
> `NSC_GetFunctionList@NSS_3.4'
> collect2: ld returned 1 exit status
> make[4]: *** [contact-print-test] Error 1
> make[4]: *** Waiting for unfinished jobs....
>

Hmm, and the mystery deepens... It looks like the source of the issue is the
"warning: libsoftokn3.so.11, needed by /usr/lib64/nss/libnss3.so.11, not
found" message - libsoftokn3.so has the ModuleDBFunc symbol in it, and it is
owned by the nss package, so I'm not sure what is going on there. What does
a "ls /usr/lib/nss/libsoft*" return?

-James




>
> and previously completed:
>
> emerge --oneshot dev-libs/nss:0
>
> Would there be any requirements to exit the terminal and log in again
> (or source something) after the revdep-rebuild and before the emerge
> @preserved-rebuild step?
>
> I'm bothered that it seems to be asking for NSS_3.4 when all I see in
> portage are 3.1/3.2 versions...
>
> lightning ~ # eix -I dev-libs/nss
> [I] dev-libs/nss
>     Available versions:  3.11.9-r1 3.12.2_rc1 {utils}
>     Installed versions:  3.12.2_rc1(10:00:56 AM 01/08/2009)(-utils)
>     Homepage:            http://www.mozilla.org/projects/security/pki/nss/
>     Description:         Mozilla's Network Security Services library
> that implements PKI support
>
> lightning ~ #
> lightning ~ # emerge -pv evolution
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R   ] mail-client/evolution-2.22.3.1  USE="crypt dbus hal
> ipv6 ldap spell ssl -debug -kerberos -krb4 -mono -networkmanager -nntp
> -pda -profile" 0 kB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 kB
> lightning ~ #
>
> Thanks,
> Mark
>
>

[-- Attachment #2: Type: text/html, Size: 4709 bytes --]

  reply	other threads:[~2009-01-08 19:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 17:20 [gentoo-user] Please explain why this new 'emerge @preserved-rebuild' is good? Mark Knecht
2009-01-08 17:42 ` Graham Murray
2009-01-08 17:51   ` Mark Knecht
2009-01-08 17:58     ` Neil Bothwick
2009-01-08 18:03       ` Mark Knecht
2009-01-08 18:07         ` James Ausmus
2009-01-08 18:24           ` Mark Knecht
2009-01-08 18:55             ` Mark Knecht
2009-01-08 19:23               ` James Ausmus [this message]
2009-01-08 19:29                 ` Mark Knecht
2009-01-08 19:36                   ` James Ausmus
2009-01-08 19:39                     ` Mark Knecht
2009-01-08 19:45                       ` James Ausmus
2009-01-08 19:49                         ` Mark Knecht
2009-01-08 20:02                           ` James Ausmus
2009-01-08 22:35                             ` Mark Knecht
2009-01-08 23:21                               ` James Ausmus
2009-01-08 23:56                                 ` Mark Knecht
2009-01-09  1:38                                   ` Mark Knecht
2009-01-08 17:47 ` Neil Bothwick
2009-01-08 17:52   ` Volker Armin Hemmann
2009-01-08 17:53   ` Mark Knecht
2009-01-08 18:00     ` Neil Bothwick
2009-01-08 18:05       ` Mark Knecht
2009-01-08 21:59   ` Momesso Andrea

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=b79f23070901081123u33b6a551jffb918a62e1e4ce@mail.gmail.com \
    --to=james.ausmus@gmail.com \
    --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