germinate (maybe?) fails to detect a closed loop on a package currently being processed

[Adam Conrad]

06:00 <cjwatson> http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.utopic/rdepends/ALL/indicator-applet
06:01 <cjwatson> Heh, that's amusing
06:01 <cjwatson> unity Recommends: indicator-appmenu Recommends: indicator-applet | indicator-renderer
06:01 <infinity> And unity provides indicator-renderer, so that should be a closed loop.
06:01 <cjwatson> Possibly this is a germinate bug; it could be that it's failing to notice that the virtual package is satisfied by something it's currently processing
06:01 <cjwatson> Can you file a germinate bug for that?

So, our assumption here is that the seeds shouldn't lead to indicator-applet being pulled into main, since unity is what's pulling in indicator-datetime (etc), and it also provides indicator-renderer.

[Colin Watson (cjwatson)]

16:39 <cjwatson> indicator-applet: so, this actually comes from the supported-hardware-desktop seed, where unity isn't a thing, via a chain of Recommends
16:39 <cjwatson> What do you think of this approach? http://paste.ubuntu.com/8310362/
16:40 <cjwatson> The net change to all.sources would demote these sources to universe (or stop asking for them to be promoted): alacarte cpufrequtils gnome-applets gnome-media gnome-panel indicator-applet libgnome-media-profiles
21:36 <infinity> So, the outcome of that seems fine, but what if the nvidia-* stuff starts recommending things that aren't already in main?
21:36 <infinity> We'd get behaviour we don't want at that point.
21:38 <cjwatson> Mm. Might sleep on it.

... and apparently sleep didn't produce an answer, but hopefully that's enough for somebody else to pick this up and run with it.