>You just want "KDevelop" -> "TDevelop" and "KDE Development" ->
>"TDE Development" ?
>I can give them a shot tomorrow if no one else gets there first.
Sounds great!
Darrell
Artists,
I filed bug report 1607 against the TDevelop splash image branding.
If you feel up to the task please help with updating the images.
http://bugs.trinitydesktop.org/show_bug.cgi?id=1607
There are three images located in git: main/tdevelop/pics/misc.
kdevassistant-splash.png
kdevdesigner-splash.png
tdevelop-splash.png
Thanks :-)
Darrell
Hi there,
after several months, I have started to rebuild TDE from the current GIT
sources on Debian/Testing, but I have soon noticed that the "tde-packaging"
repository is not up to date with the "tde" repository.
Namely, when trying to build "tdelibs" I run into a broken dependency for
"libart-2.0-dev" version >=14.0.0. The current files in the "tde-packaging"
repository for "libart" builds to a version which is 2.3.22.
I double-checked the nightly builds on the web site, and I saw that the
correct package (version 14.0.0) is created.
So my questions are:
1) is there a date already scheduled for an update of the "tde-packaging"
repository, and if so when
2) otherwise, is there any other place where I can find the updated
packaging files (other than download the .dsc and .tar.xz file for each
package from the nightly build website and then extract the packaging
scripts)?
Thanks
Michele
>So, if I think they should be applied, am I supposed to add them
>to some
>list or as a depend for some bug or mark up them somehow?
I updated the etherpad.
Please remember the etherpad list is not all-inclusive of every
unresolved bug report. The etherpad is a list of selected bug
reports from the various categories that we believe must be fixed
for the official R14 release.
Feel free to voice opinions about the contents of the list. Just
please remember that everybody involved has bug reports that are
not in the etherpad list. The goal is to release R14 and not to
resolve all outstanding bug reports in the next couple of weeks.
That would be impossible. The remaining unresolved bug reports
number far too many to add to this list. The etherpad list is a
triage of sorts. There will be plenty of opportunity to resolve
remaining open bug reports with each subsequent minor point release
(R14.0.1, R14.0.2, etc.) and this is exactly how we will resolve
them all. :-) All bug reports cause some pain to one degree or
another. The etherpad list contains those reports we believe cause
the most pain. :-)
Alexander, I saw your additions to the etherpad. I moved them to
different categories but all of the items are still there. :-)
Darrell
All,
TDE R14.0.0 will be entering a hard freeze 00:00GMT 07/23/2013. A hard
freeze means that only patches which resolve bug reports will be accepted.
For additional details on our R14 release schedule and critical bugs that
need to be resolved, please visit the TDE R14 release Etherpad at
http://trinity.etherpad.trinitydesktop.org/39
If you can help out with the open bugs listed at that Etherpad, please do
so. R14.0.0 cannot be delayed much further due to HAL and NetworkManager
changes, and if necessary any remaining open bugs listed as of R14.0.0
release will need to be addressed in an R14.0.1 SRU.
Thanks!
Timothy Pearson
Trinity Desktop Project
Hello,
I'm building R14 for CentOS 6. This distribution is using NetworkManager
0.8 .
Is the Knetworkmanager8 package still relevant for this distribution ?
Because I've got FTBFS with it (see bottom of this mail).
But I've built by error tdenetworkmanager (aka knetworkmanager9), and it
built correctly, but it also looks like it works correctly (not really
tested but it shows my wireless network).
Is "tdenetworkmanager" supposed to replace both versions of
knetworkmanager ?
Thanks
François
FTBFS in knetworkmanager8:
[ 20%] Building CXX object
knetworkmanager-0.8/src/CMakeFiles/tdeinit_knetworkmanager-shared.dir/knetworkmanager-connection.cpp.o
cd
"/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/build/knetworkmanager-0.8/src"
&& /usr/lib64/ccache/c++ -DHAVE_CONFIG_H
-Dtdeinit_knetworkmanager_shared_EXPORTS -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/usr/include/tqt3
-I/usr/include/tqt -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL
-DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-include tqt.h -fPIC
-I"/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/build/knetworkmanager-0.8/src"
-I"/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/build"
-I/opt/trinity/include/tde -I/usr/include/tqt3 -I/usr/include/tqt
-I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include
-I/usr/include/NetworkManager -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -UQT_NO_ASCII_CAST -o
CMakeFiles/tdeinit_knetworkmanager-shared.dir/knetworkmanager-connection.cpp.o
-c
"/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/knetworkmanager-0.8/src/knetworkmanager-connection.cpp"
/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/knetworkmanager-0.8/src/knetworkmanager-connection.cpp:
In constructor
'ConnectionSettings::ConnectionPrivate::ConnectionPrivate(ConnectionSettings::Connection*)':
/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/knetworkmanager-0.8/src/knetworkmanager-connection.cpp:64:
error: cannot allocate an object of abstract type
'ConnectionSettings::ConnectionSecretsDBus'
/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/knetworkmanager-0.8/src/knetworkmanager-connection_secrets_dbus.h:51:
note: because the following virtual functions are pure within
'ConnectionSettings::ConnectionSecretsDBus':
/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/build/knetworkmanager-0.8/src/dbus/connection.h:94:
note: virtual bool DBus::Secrets::GetSecrets(const TQString&, const
TQStringList&, bool, TQT_DBusDataMap<TQString>&, TQT_DBusError&)
make[2]: ***
[knetworkmanager-0.8/src/CMakeFiles/tdeinit_knetworkmanager-shared.dir/knetworkmanager-connection.cpp.o]
Error 1
make[2]: Leaving directory
`/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/build'
make[1]: ***
[knetworkmanager-0.8/src/CMakeFiles/tdeinit_knetworkmanager-shared.dir/all]
Error 2
make[1]: Leaving directory
`/dev/shm/BUILD.el6.x86_64/trinity-knetworkmanager8-14.0.0~pre106+401c11db/build'
make: *** [all] Error 2
>+ kdepasswd => tdepasswd
>+ libsmokekde => libsmoketde
>
>It also offers yet another renaming:
>
>+ libsmokeqt => libsmoketqt
>
>What is your opinion?
Slavek,
As I updated my local source tree I vaguely noticed some kdepasswd -
> tdepasswd changes in the script output. Are all proposed changes
completed?
Darrell
On Sun, 21 Jul 2013 21:19:54 -0500 "Timothy Pearson"
<kb9vqf(a)pearsoncomputing.net> wrote:
>For those who are not signed up for the TDE Announcements mailing
>list,
>TDE v3.5.13.2 was released today! The release announcement can be
>viewed
>at http://trinity-announce.pearsoncomputing.net/?0::28 or on the
>TDE
>website at http://www.trinitydesktop.org
Good job everybody!
Darrell
>Thanks Darrell, seems like I missed than section in between the
>load of NOTEs :p
>
>BTW, I had to add this include at the top of src/kernel/qpngio.cpp
>to
>fix the compilation issue I was asking about, which I got it tqt3
>as
>well:
>#include <x86_64-linux-gnu/zconf.h>
>
>I had to put this in the include search path too:
>export C[XX / PP / PLUS]_INCLUDE_PATH=/usr/include/freetype2/
>
>I don't know if that might break something in the future, but at
>least it built :)
Tim is the subject matter expert with qt3/tqt3. Best to holler at
him.
Regarding CPLUS_INCLUDE_PATH, we had a discussion about that
variable a very long time ago. Search the mail archives. We
discovered that variable caused problems. Now, that was a very long
time ago and Trinity has evolved in many ways since then, but I
still unset the variable when I run my build scripts.
BTW, the build notes wiki hasn't been reviewed by a newcomer in a
long time. Please offer improvements and critiques. :-)
Darrell