why aren't you using eix-sync?

2016-04-29 8:43 GMT+02:00 Daiajo Tibdixious <dai...@gmail.com>:

> Yeah eventually found that out.
> I have emerge --sync and eix-update in a cron job, which hasn't been
> running
> (for unknown reasons, vixie cron is in startup and is running).
>
> On Fri, Apr 29, 2016 at 9:01 AM, Jonathan Callen <jcal...@gentoo.org>
> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> > On 04/26/2016 10:43 PM, Daiajo Tibdixious wrote:
> >> Some products show [I] dev-libs/libdbus-qt while many others show
> >> [?] dev-qt/qt-dbus
> >>
> >> I expect the [I] status for installed products, what does the ?
> >> mean? I tried rebuilding the ones with ? which didn't change it and
> >> revdep-rebuild didn't find anything.
> >>
> >> This seemed to start after the kde/plasma upgrade. Since then sddm
> >> won't start, KDE won't start, and I'm worried the ? is a clue.
> >>
> >>
> >
> > A question mark usually means that the eix database is out of date (or
> > doesn't match the current repos).  The simplest fix for that is
> > probably to run eix-update to get the database back up-to-date.
> >
> > - --
> > Jonathan Callen
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2
> >
> > iQIcBAEBCgAGBQJXIpY3AAoJEEIQbvYRB3mgZikQAMNbrWiKWrg0dTqhKzQ/Xlpy
> > O3pdRVA/lyyXvMseTuKB4oG5USAtBhukcdQkrdzO75doTg1itCdfv/LDw3OzfaF7
> > 898LV3U5x49ZiWa8tn7lzPkPQBQ/eH1RgJ4rFXlZNYNXXUp5SMM16Lfs8iTAqNS8
> > PXaqmTntOKXY2YUy5gZvUuZd4Y9CwDkq7X9tA11b2MHwYSQSYoVn2XlozVUdNVFO
> > KmRS1blQL9+w8o2/jqmz+xK0EAGwNKnsoPFJMpt9a49oGUwqZP0k/x6BTFVJFw8u
> > ACVuQBk5thySE4AoSJEBtrg+dn0Z0ufYHAZoKvE52i1Lc1wdeXlG/mocL6+4/xWa
> > 0tLb1+kany9u27IUO3GPQflm7xGbmNPaDE0e/dSnVkYs1KJa1ACzphmEk17Jl4dP
> > 3hD6gCzJPMsd2exP5Oj0fwXwU9tMoiQBMXZFp08j/vuwLNZCLSLcbkTlDuuud2EB
> > QKQX75+yJAmCNHhTVVWrFEuDDcm6yzEraifVxPZu2HmWBrH2O2QRtWD89fHbEc+u
> > YIihSTwj8B4pfmcIIzyzZNM6YKWMkpxwIEEoKT3ZIbK142BUok1sGHQQ1OVQpm5S
> > DQbxcGSoLg9glxPxZKgZ92D7n7roieGsBJlPzbV4wV4EqrJ9wfV7kbG4pyZ/WlDA
> > hCbqrbOOQsjySHXusW/E
> > =TJNc
> > -----END PGP SIGNATURE-----
> >
>
>

Reply via email to