tde-devels March 2014

devels@trinitydesktop.org

17 participants
58 discussions

by Timothy Pearson

All, I have put a significant amount of work into the QuickBuild system over the past week in an attempt to stabilize it and increase performance. While I am aware that there were some outages in random components (most notably the PPA mirror redirects) while I was doing this, all issues should be resolved at this point. As of this writing four build machines are online, one for each architecture. As we have reached the chiller fund goal (see prior messages) the remaining x86/amd64 build machines will be brought back online over the next couple weeks. Please let me know what you think, and definitely let me know if anything is still malfunctioning! Tim

8 years, 8 months

When TDE crashes...

by Timothy Pearson

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 Cross-post from the users list: When TDE crashes and Dr. Konqi appears... ...please click "Report Crash" instead of "Close". TDE now has a powerful automated crash reporting system that will let you submit a crash report with as little as three mouse clicks--no personal information, logins, or version descriptions are required. Of course we would appreciate a problem description and possibly a contact Email address, but if you don't have time or just don't want to give that information out you can still submit the crash report for analysis and repair. Developers: Automated crash reports are visible at https://crashreport.trinitydesktop.org. Click on the crash ID for a detailed report. Let me know what you think, and if you have any suggestions please let me know! Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iFYEARELAAYFAlM4nhUACgkQLaxZSoRZrGGmpQDfeqFMAKvFQAZ/J1SUDaIyMXHY XjaEWd3CJc6RggDdHGuvUcNQHTtkO9v96najkbqnVmbcJ7Cca8UtXg== =ZkhI -----END PGP SIGNATURE-----

10 years, 1 month

QuickBuild restored

by Timothy Pearson

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 All, I wanted to let you know that the QuickBuild system has been restored to full functionality. All builds are now proceeding normally. Thank you again for your generosity in helping replace the failed chiller; this would not have been possible without your support! Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iFYEARELAAYFAlM4qvUACgkQLaxZSoRZrGG7LQDgg+rOLPLVhGutFDhrpU0daEpd Nx7UEdYoXdLMBQDgyFdCXrqdmSIzG24p0brhccbXkd8AoofjNJyMWw== =yzeo -----END PGP SIGNATURE-----

10 years, 1 month

Re: [trinity-devel] Bugszilla whining poll (i.e. the "your bugszilla bug list needs attention" emails)

by Michele Calgaro

> Considering how long almost all bug reports sit idle, the reminders are little more than spam. That is my opinion too. Perhaps a reminder once a month would be good and would not be considered spam. Cheers Michele

10 years, 1 month

Request of re-packaging 3.5.13.2 for PCLinuxOS - François Andriot

by Alexandre

Hi, I had users (Baron, Tony) of my remaster telling me on the user mailling list that printing is now broken on my remaster. It is mostly due to the fact that since PCLinuxOS is a rolling release, some librairies used are probably newer now than they were when the 3.5.13.2 packages has been built last summer. François Andriot, is it possible for you to rebuild 3.5.13.2 againsts a fully updated PCLinuxOS system please, so that the users will receive it in their updates? I will also re-remaster it with all the updates, and new stuff of course, since R14 release is to be in at least a few weeks or months. Thank you very much! -Alexandre

10 years, 1 month

K->T image rebranding: any volunteer?

by Michele Calgaro

All, in bug 2015 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=2015) Darrell has pointed out several pictures that need rebranding from K to T. Any one volunteering for doing it in his/her spare time? Those rebranding would go into v14.0.0 if we can get the new pictures ready in time. Cheers Michele

10 years, 1 month

Re: [trinity-users] Bugszilla whining poll (i.e. the "your bugszilla bug list needs attention" emails)

by Michele Calgaro

> Does this affect normal trinity users (i.e not developers) who only report bugs? > Janek I assume from your email that you are not receiving whining emails. I think this affects whoever reports a bug in bugszilla and set him/herself as 'bug assignee'. If you are not getting any whining emails, that may be the reason. I am not sure 100% though, it depends on the contents of the whining script that is run daily. Cheers Michele

10 years, 1 month

Bugszilla whining poll (i.e. the "your bugszilla bug list needs attention" emails)

by Michele Calgaro

Dear all, I recently had some discussions with Tim and Slavek about the bugszilla whining functionality, i.e. the "your bugszilla bug list needs attention" emails that are sent out automatically every day. We would like to fine tune that, but first we need to know your opinion about it. Here are some possible options to choose from: 1) the whining emails are reeeeeally useful, please spam my mailbox every 5 minutes so I won't forget what bug I am supposed to be working on instead of spending my time deleting emails. 2) the whining emails are useful and the current setting is ok. 3) the whining emails are useful but the frequency of the remainder is too high (currently daily). It would be better if the emails were sent weekly/bi-weekly/monthly/every 3 months/every 6 months/once a year/once every 5 years.... 4) the whining emails are useless to me but they don't affect me. 5) the whining emails are useless to me and would prefer not to receive them if possible. 6) please stop sending me those useless stuff. Pleeeeeeeease!! Really, please! Looking forward to your opinions, so that we can fine tune the settings in the best way. Cheers Michele

10 years, 1 month

Alternative APT source 'R14 preliminary stable-builds'

by Slávek Banko

Hi all, in light of the recent problems on the build-farm, I used the fact that ever since work on v3.5.13-sru I have the automated preparation of source packages and at the same time I have a private builder where I am doing the test building, and where I have available all supported Debian and Ubuntu distributions (for example, see my test for building on Ubuntu Trusty). I optimize my production line for building packages, so now I have ready alternative APT source containing packages for all supported Debian and Ubuntu distributions. The same packages will be in the future uploaded to my PPA on build-farm, where they will serve as maintanance releases for R14. Similarly, as was my PPA for v3.5.13-sru branch. Therefore, this apt source I call 'R14 preliminary stable-builds'. In order that the packages were readily available, they are synced to my primary mirror. What to do if you want to use it? 1) Add the source to sources.list: deb http://mirror.xcer.cz/trinity-sb *distribution-name* deps-r14 main-r14 2) From some public GPG keyserver download my key and import it into APT: sudo apt-key adv --keyserver pks.gpg.cz --recv-keys ED1F4884 3) Update the packages in such a way as you used to do it :) I hope it will be helpful. -- Slavek

10 years, 1 month

[KDE * Restrictions]

by Darrell

Is there a way to query the full source tree to assemble a list of all possible "kiosk" related restrictions? Or which apps support restrictions? There are two README files in the source tree, but the files seem incomplete: tdelibs/tdecore/README/kiosk tdebase/konsole/README.konsole_kiosk Neither README is installed in the final tdelibs or tdebase packages. The README files indicate there are three major groupings (kdeglobal): [KDE Action Restrictions] [KDE Resource Restrictions] [KDE URL Restrictions] The kiosktool app does not seem to provide a method to assemble a full list of restrictions. I am editing the Admin Guide. An appendix of all possible restrictions would be helpful. Darrell

10 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels March 2014