That is because you guys are the only ones building trinity nightly on a daily basis :-) I am steadily working through different bug reports at a crawling pace, and expect many of them to be pushed by R14. I have not even looked at any build problems as bug reports. I consider build bugs problems for packagers ( you ) and I let you resolve them because at this point you have a very good idea of how it works. I see there are a few marked as PATCHAVAIL. why not push those patches now that you have write access? Don't forget they have been using kde3.5 for quite some time I suspect, and are currently using Trinity 3.5.12. While R14 may have bugs we _are_ getting through many of them. I concur with the sentiment, only to then say "Yes, such is the plight of finite time and energy"

The funny thing is that the HAL dependency bug is among the oldest open bug reports on the tracker, dating back almost to the fork of KDE3.5. It is also one of the first things other desktops environments throw at us to claim that TDE is obsolete. This is high priority for me to fix, it has been over 3 years and in all that time no one has had the requisite expertise to repair it.

Could you focus on interfacing upower with kpowersave instead? udisks is a dead end from what I have been reading, and I already have a very large chunk of the needed generic udev interface, along with disk handling, completed as of yesterday night.

On Fri, Mar 30, 2012 at 14:38, Serghei Amelian <serghei(a)thel.ro> wrote: At the moment you can run udisks in parallel with udisks2; the plan for suse is unknown as there is a great "debate" going on right now.

The funny thing is that the HAL dependency bug is among the oldest open bug reports on the tracker, dating back almost to the fork of KDE3.5. It is also one of the first things other desktops environments throw at us to claim that TDE is obsolete. This is high priority for me to fix, it has been over 3 years and in all that time no one has had the requisite expertise to repair it. I would love to fix the bugs myself, however there is the issue of money and time on my end. Simply put I can't dedicate weeks of unpaid time to TDE each month; bills have to be paid and other tasks need to be finished. Then there is the issue of varying platforms and distributions; I use Debian and Ubuntu and see no build problems whatsoever. Linux can be somewhat infuriating for software developers for this reason; what works perfectly on one distribution fails on another. I don't have the time or resources to install and learn every distribution that TDE runs on, so I rely on others to handle the repair of bugs that only show up on their distribution or setup. HAL is slowly breaking down as the kernel changes, and there will eventually come a time when it just doesn't work any more, making the initial development of an alternative imperative. The R14.0 release can be pushed back if needed, especially since Slavek Banko has been fixing critical bugs in the Debian/Ubuntu packages for 3.5.13. I know it is frustrating, but please remember that we are all volunteers working on this project because in many cases the alternatives are even worse than a buggy release of TDE. Just to be clear, I am not receiving payment for my work on TDE either; the money collected via the Donations page barely covers annual operating expenses, and many times falls short. If those involved in LiMux or any other major TDE deployment would provide coders willing to help squash bugs, or even sponsor the project, then we could make faster progress. I have yet to see this happen. For now I continue to fix bugs that are most irritating to me, as I have time, in the finest FOSS tradition. :-) As others here do the same the bug list will slowly be whittled down, even if it takes longer than we would like.