Hi arches, I added new tracker a few days ago to the tree and re-added tracker support to nautilus-2.28.2. As a consequence, your keywords were dropped from nautilus and will be dropped from gnome meta by the time it is added to the tree. Please consider keywording tracker and nautilus back. Thanks.
(In reply to comment #0) > I added new tracker a few days ago to the tree and re-added tracker support to > nautilus-2.28.2. Weird you're asking for bsd keywording while the tracker ebuild has a mandatory dep on util-*linux*.... > As a consequence, your keywords were dropped from nautilus and > will be dropped from gnome meta by the time it is added to the tree. Please > consider keywording tracker and nautilus back. Why? We've had a p.use.mask on nautilus[tracker] for ages on bsd... and it seems to be the case for other arches too.
(In reply to comment #1) > (In reply to comment #0) > > I added new tracker a few days ago to the tree and re-added tracker support to > > nautilus-2.28.2. > > Weird you're asking for bsd keywording while the tracker ebuild has a mandatory > dep on util-*linux*.... hum right, I had forgotten that one. I guess there is upstream work to do here. > > As a consequence, your keywords were dropped from nautilus and > > will be dropped from gnome meta by the time it is added to the tree. Please > > consider keywording tracker and nautilus back. > > Why? We've had a p.use.mask on nautilus[tracker] for ages on bsd... and it > seems to be the case for other arches too. I didn't check individual arch package.mask, I added a global mask a few weeks ago for tracker 0.6 elimination purpose but it's now restricted so it can be used in nautilus-2.28.2 with tracker-0.7.
ok I re-added arm, hppa and sh and bsd keyword on nautilus after checking they had the USE masked in profile. Keeping everyone CCed so we can get a word on if you guys would like to support tracker or not. If not, please add a use.mask entry in your profile.
~alpha/~ia64/~sparc done and arm/sh are happy with the mask
All arches done, closing.
(In reply to comment #5) > All arches done, closing. > ~ppc/~ppc64/~hppa still missing, tracker needed by gnome-base/nautilus ...
ppc64 done btw, alternative would be to use.mask "tracker" on profiles, in case hppa doesn't want tracker...
Keywording of gnome-base/nautilus removed for HPPA.
Marked ~ppc.
@bsd, any comment about tracker support ?
alpha, ia64, ppc, ppc64 and sparc, I'm sorry guys, but I must re-add you here due to the fix of bug #325435, I had to drop your keyword again. Please either keyword app-text/odt2txt or mask the gsf use flag altogether. @bsd, I'm still waiting for a word from you guys. Thanks in advance.
~alpha/~ia64/~sparc done
~ppc64 done
This looks very broken: tracker-0.10.0.ebuild:KEYWORDS="~alpha ~amd64 ~x86" tracker-0.10.4.ebuild:KEYWORDS="~alpha ~amd64 ~x86" tracker-0.8.17.ebuild:KEYWORDS="~alpha ~amd64 ~ia64 ~ppc64 ~sparc ~x86" tracker-0.9.38.ebuild:KEYWORDS="~alpha ~amd64 ~x86" As current version for ia64/ppc64/sparc will fail to compile, for instance, with current stable sys-power/upower. So rekeyword latest asap, or drop keywords so we can get rid of the will-not-compile-for-sure versions.
the only installable tracker is 0.8 and should work with latest upower as I backported appropriate patches iirc. I'll unmask 0.10 asap though given last talk I had with upstream about depending on too recent libs.
So what we have to do, then?
(In reply to comment #11) > @bsd, I'm still waiting for a word from you guys. we're fine with the mask, esp. since the util-linux dep is still there, 2.5 years later :)
Looks like tracker is now amd64/x86 only (for all versions)