On 04/10/2012 12:35 PM, Darrell Anderson wrote: That's great news! I have 86 TDE build scripts of which 68 are building after the gcc47 update (10 have never built) -- so that only leaves 49 to go :) gcc47 current failures of those that were building prior to gcc47 (unknown number undiscovered in 39 untried packages) tde-kipi-plugins mutiple declarations of 'TQListViewItemIterator it(d->listView)' in kipi-plugins/flickrexport/imageslist.cpp tde-tdeedu tde-tdegraphics tde-tdepim tde-rosegarden tde-basket (gcc47 - fixed: patch tde-basket-gcc47.diff) tde-k3b tde-kima tde-krusader -- David C. Rankin, J.D.,P.E.

No I don't know that. Please provide the specifics! Even after the admin and cmake directories replicate (how do they do that --- in your nightlies or during any local build?), that will not catch everything. So I probably still need to make another pass to create module specific packages, which, if I understand you correctly, means only a handful of patches rather than 117. Darrell

Do you mean I can't push changes to admin/cmake in each individual module because the next time I resync they all will be overwritten? That any changes I always want to make to admin/cmake must be to the common ones and they must be pushed immediately? How do I test here before pushing to the master server? If the replication occurs only at the main GIT server, then those replications do not occur locally to all of the modules in my local tree. Seems the only way to make this change is to patch my common admin/cmake and push immediately. But then I hold my breath that I did not break anything major. Seems as though there is a point of uncertainty whne pushing changes to the common admin/cmake. I can't simulate the replication of the main GIT server. Perhaps I am misunderstanding the whole thing. I also need to concurrently push the changes to tdelibs because of kstandarddirs.cpp. Darrell

I think. Maybe. When I build locally, does each module pull from my local common admin/cmake? I remain unclear about that. Do I have permissions to push to the common admin/cmake? I tried pushing some nominal typo corrections for qt3 and tqt3 and was rejected. Darrell

Ok. I don't need to do that. I'll push the common directory changes to GIT and wait until the next day to resync here. By then the main repo will have replicated those changes to all other modules. I just now created the patches for common. Only three files involved and only a one-liner in each. With those changes I'll push the tdelibs patch then too because kstandarddir.h/cpp need to be updated concurrently. That still leaves individual module changes wioth various oddball changes, such as docbook files, but I can regenerate those patches after the master server has done the basics. Ok. Darrell