From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sys-fs/-MERGING-static-dev installed but unable to find it
Date: Tue, 15 Sep 2015 13:29:47 +0100 [thread overview]
Message-ID: <1493091.AYR2Czp2am@wstn> (raw)
In-Reply-To: <55F7DF4C.5010707@gmail.com>
On Tuesday 15 September 2015 04:05:16 Dale wrote:
> Peter Humphrey wrote:
> > On Monday 14 September 2015 11:28:36 Marc Joliet wrote:
> >> Just for the record, but I think emaint (part of portage) should be
> >> capable
> >> of fixing this automatically (specifically, it's "merges" command). It
> >> can
> >> do a couple more things, so check it out anyway. (Also, per the news
> >> item
> >> "New portage plug-in sync system" from 2015-02-02, "emaint sync" is going
> >> to become the preferred way of syncing the portage tree and overlays.)
> >
> > Thanks for the reminder, Marc. I'd forgotten about that news item.
> >
> > When I ran "emaint all" just now I got "has outdated metadata" against
> > five KDE packages. Does anyone here know what that implies? Google didn't
> > help.
> I got one of those too.
>
> root@fireball / # emaint all
--->8
> Emaint: check movebin 100%
> [============================================>]
>
> 'kde-base/kdelibs-4.14.11' has outdated metadata
>
> Emaint: check moveinst 100%
> [============================================>]
>
> 'kde-base/kdelibs-4.14.11' has outdated metadata
>
> [============================================>]
Yes, that's one of the five I got. I can't tell you the other four now because
they've scrolled off.
> Still not quite sure exactly what this does tho. :/
Nor I. Still, it doesn't seem to be anything to worry about.
--
Rgds
Peter
prev parent reply other threads:[~2015-09-15 12:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 3:46 [gentoo-user] sys-fs/-MERGING-static-dev installed but unable to find it Dale
2015-09-14 4:36 ` wabenbau
2015-09-14 5:00 ` wabenbau
2015-09-14 5:21 ` Dale
2015-09-14 5:14 ` Dale
2015-09-14 7:41 ` Neil Bothwick
2015-09-14 5:07 ` wraeth
2015-09-14 5:14 ` wabenbau
2015-09-14 5:34 ` [SOLVED] " Dale
2015-09-14 5:50 ` wraeth
2015-09-14 8:37 ` Peter Humphrey
2015-09-14 8:45 ` Dale
2015-09-14 9:09 ` wraeth
2015-09-14 9:16 ` Dale
2015-09-14 5:28 ` Dale
2015-09-14 9:28 ` Marc Joliet
2015-09-14 11:24 ` Dale
2015-09-14 14:56 ` Peter Humphrey
2015-09-14 15:38 ` [gentoo-user] " james
2015-09-14 20:41 ` [gentoo-user] " Neil Bothwick
2015-09-15 8:50 ` Peter Humphrey
2015-09-15 9:07 ` wraeth
2015-09-15 9:30 ` Neil Bothwick
2015-09-15 12:30 ` Peter Humphrey
2015-09-15 9:05 ` Dale
2015-09-15 12:29 ` Peter Humphrey [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=1493091.AYR2Czp2am@wstn \
--to=peter@prh.myzen.co.uk \
--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