public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --depclean and virtual/glibc problems
Date: Tue, 20 Feb 2007 20:01:50 -0800	[thread overview]
Message-ID: <5bdc1c8b0702202001i429ab392rdcbc49201b176b7d@mail.gmail.com> (raw)
In-Reply-To: <200702210427.58796.bo.andresen@zlin.dk>

On 2/20/07, Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
> On Wednesday 21 February 2007 03:47:05 Mark Knecht wrote:
> > Thanks for responding. I didn't know about that option or the
> > difference between how it's used for --depclean. Thanks.
> >
> > I solved the lm_sensors one before your response came back.
> > Unfortunately --with-bdeps=y doesn't seem to identify anything new to
> > emerge. I don't see how it could if I don't see virtual/glibc in
> > portage:
> >
> > gandalf ~ # emerge --with-bdeps=y -pvDNu world
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating world dependencies... done!
> >
> > Total: 0 packages, Size of downloads: 0 kB
> > gandalf ~ # eix =virtual/glibc
> > No matches found.
> > gandalf ~ #
> >
> > I must be doing something wrong here. Is the need for this virtual
> > package caused by some USE option on something else like glibc itself?
>
> Was just a guess, heh.
>
> virtual/glibc was changed to virtual/libc 2½ years ago. Since
> sys-libs/db-3.2.9-r2 and media-libs/xvid-0.9.1 are no longer in the tree
> portage are using their ancient/obsolete deps on virtual/glibc which it
> cannot satisfy. Had they been in the tree portage would use their updated
> deps from the tree.
>
> I'm guessing nothing in world depends on them (or in the case of db on that
> slot) so they probably can just be unmerged (and would be if --depclean
> wasn't taking so many precautions)... Otherwise I reckon at least xvid should
> be updated to a newer version. The safe route, however, would probably be:
> `emerge --oneshot sys-libs/db:3 media-libs/xvid`.
>
> --
> Bo Andresen

OK, thanks again. I see a big part of my problem, being a user type,
is that I really don't understand slots at all, other than letting the
system somehow have multiple versions of the same package for whatever
reason. (Which is far beyond me!)

Anyway, I did emerge -C on the offending packages and then emerge
-pvDuN world and revdep-rebuild again to make sure everything was
correct. All seems good. Now --depclean is working and I can clean up
at the next level.

The problems of administering a machine 350 miles away. It only
happens once or twice a year and there's often a lot to learn and a
lot to do.

thanks again,
Mark
--
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2007-02-21  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5bdc1c8b0702201704n7d3e0c9euda062cea9a070da6@mail.gmail.com>
     [not found] ` <200702210258.39129.bo.andresen@zlin.dk>
2007-02-21  2:47   ` [gentoo-user] --depclean and virtual/glibc problems Mark Knecht
     [not found]     ` <200702210427.58796.bo.andresen@zlin.dk>
2007-02-21  4:01       ` Mark Knecht [this message]

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=5bdc1c8b0702202001i429ab392rdcbc49201b176b7d@mail.gmail.com \
    --to=markknecht@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