>You can probably start your builds again, though a few of the
>larger/more
>obscure packages such as tdebindings will likely fail to build at
>this time.
And just as importantly, the commits web page is again updating so
I know what happened and where to debug should problems arise. :)
Darrell
>Should be nearly stable again at this point; I successfully ran a
>combined
>TDE/KDE4 program for the first time tonight but there is at least
>one
>minor crash I need to correct/test.
>
>You can probably start your builds again, though a few of the
>larger/more
>obscure packages such as tdebindings will likely fail to build at
>this time.
I'll update my GIT repo and start running build sets when we are
informed all packages build without error. Please let us know when
all packages build. :)
Darrell
Is anybody able to use krfb/krdc from GIT?
I receive a "The connection to the host has been interrupted"
kdialog. I can see the icon try to attach to the system tray but is
gone almost too fast to see.
Darrell
How can I find out when the nightly builds are ready for use ?
I am testing these on Wheezy, not usable as of today, we were warned
(thanks), just want to get back to testing when appropriate.
Thank You
--
Peace,
Greg
On Tue, 29 Jan 2013 11:21:19 -0600 "Slávek Banko"
<slavek.banko(a)axis.cz> wrote:
>On Tuesday 29 of January 2013 18:04:12 Darrell Anderson wrote:
>> The commits web page has not updated in many days.
>>
>> Yet again.
>>
>> Darrell
>>
>
>And tbottu is not active on IRC :)
What is the status of the recent ABI/API breakage? Is everything
again stable to allow build runs?
Darrell
Hello all,
I would like to install TDE on Debian Squeeze but i want only the minimal
not games , educations , videos .
Thanks for your help.
Sincerely,
Jean
--
MILOT Jean
Tél. : 0659514624
milot.jean(a)gmail.com
Hi all,
I have a problem to discuss:
Before long time I prepared a patch, which is included in the commit 9e3f8a7f.
It was based on a completely broken patch for KDE4 - commit c24ea2b4. Our
patch works correctly, but contains one potential risk - is dependent on DNS
=> on the network delays.
First question is, how big is this risk, because we have a patch incorporated
nearly a year ago and no problems observed. The fact is that if the user will
have a problem with the network, probably will not even be able to open a
remote window. However, this risk actually exists.
In my proposal for the integration of our patch into KDE4 was a risk discussed
by KDE4 team and Martin prepared a solution where the DNS queries is executed
in a separate thread - commit cbb7f575. In comparison with our patch it is
quite big patch. Backport of Martin's patch is hampered by the fact that he
was used QtConcurrent which is included in QT4.7 and higher.
Therefore, I have a question: What next? Martin designed a simple revert our
patch seems to me inappropriate. The second option is to leave our patch
unchanged and also a risk. Third, that someone remakes patch to not use
QtConcurrent (it is beyond my abilities).
Your suggestions?
Thanks for your comments and help
Mentioned commits:
http://quickgit.kde.org/?p=kde-workspace.git&a=commit&h=c24ea2b4aac214ce29a…http://git.trinitydesktop.org/cgit/tdebase/commit/?id=9e3f8a7f0c9f2ed1125c7…http://quickgit.kde.org/?p=kde-workspace.git&a=commit&h=cbb7f5750fe2a3b4916…
Slavek
--