smart-update lacks the suid bit, which makes it (and ksmarttray) pretty much useless.
ksmarttray uses kdesu, did you really encounter an issue with ksmarttray? I'll fix smart-update suid, I hope I can still do so for FC4.
(In reply to comment #1) > ksmarttray uses kdesu, No it doesn't for running smart-update, only smart --gui. > did you really encounter an issue with ksmarttray? Um, yes. Without being able to run smart-update with root permissions, it fails to check for updates and thus fails to do its primary job.
Unless you strongly object I'll prefer wait on fixing this, as there is still bug #201752, the unghosting of *.pyos and the mass rebuild, all requiring a rebuild of smart of their own probably within the next week.
Waiting for those for devel/FC6 is ok, but I think it wouldn't hurt to build for < FC6 as soon as #201752 is resolved even if that would mean FC6/devel temporarily lagging behind a bit. By the way, there's also some Python 2.5 movement going on, dunno if it's being considered for FC6: http://www.redhat.com/archives/fedora-maintainers/2006-August/msg00074.html BTW, what's the "POST" bug status, and how does one access it? I don't see it in the status drop-down box.
python 2.5 is scheduled a day after FC6t3. Unless one project changes schedule for any reason it looks like FC6 will be 2.4 based. "POST" was the last item on the list. It isn't now available probably because it is selected for this bug, but if you go to any other bug that is ASSIGNED you will have the choice to make it POST. The short description of it is something between ASSIGNED and MODIFIED, my interpretation is "next action is known, but nothing has been changed yet", and I assume POST means "postponed". But I see that MODIFIED is missing, so something is amiss. Either POST is wrongly available, or MODIFIED is wrongly missing, or the description is bogus. Pick one :)