tde-devels

devels@trinitydesktop.org

3803 discussions

ktorrent 14.1.4 FTBFS
by Darrell Anderson 10 May '25

10 May '25

I am compiling 14.1.4 packages for Slackware 15.0. ktorrent fails to build with the following fatal error: ktorrent-trinity-14.1.4/src/libktorrent/torrent/cachefile.cpp:44:10: fatal error: settings.h: No such file or directory I'm using cmake. Appreciate some help. Thanks.

3 3

TDE Packaging System
by Darrell Anderson 10 May '25

10 May '25

What are the requirements to submit a collection of distro build scripts to the TDE packaging system? Once the scripts are part of the packaging system, will prebuilt packages then be available to anybody for downloading and installing? Thanks.

2 2

Fwd: Re: KDE3 vs. TDE in openSUSE
by J Leslie Turriff 10 May '25

10 May '25

After reading this, I wonder if it is actually why TDE is not available in openSUSE's mainline repositories, or some other reason? Leslie ---------- Forwarded Message ---------- Subject: Re: KDE3 vs. TDE in openSUSE Date: 2025-05-09, 19:22:21 From: Felix Miata <mrmazda(a)earthlink.net> To: kde3(a)lists.opensuse.org Gianluca Interlandi composed on 2025-05-09 16:29 (UTC-0700): >> What justifies KDE3 keep-alive as mature as TDE has become, now 14.1.4, >> 15 years later? > KDE3 is still part of the official openSUSE repositories. Yes, but not really. KDE3 got its own repo too long ago to remember, so yes, available from openSUSE, but requires special effort to install differing little from installing TDE. > Do you think > there is or there will be a way to make TDE part of the openSUSE > repositories? In this way, TDE can be selected during an openSUSE > installation instead as doing it after everything is setup. I know that > the Trinity website recommends installing packages from packman and > switching vendor before installing TDE. Maybe this can be done also after > TDE is installed? I've been disabling Packman in recent months. With so few remaining patents applicable, I haven't had any need for it in some time. >> With Leap 16 abandoning the hardware that makes the two shine, is 15.6 >> support cessation time to retire the old codepath and name? > Can you please elaborate what you mean by this? Are you saying that TDE > will not "shine" in Leap 16? What I meant with "shine" was KDE3/TDE notable liveliness on old hardware compared to contemporary DEs like Gnome, XFCE and Plasma. KDE3 was fast on 32bit when 64bit was a new thing most had yet to acquire. Gianluca Interlandi composed on 2025-05-09 16:43 (UTC-0700): > Now I see what you mean. Leap 16 will require x86_64-v2. How do you check > for this? For example, on Intel Core 2 Duo I have the following flags: Core2Duo/Quad is v1, dead for 16.0, as are some early Core i3/i5/i7 varieties IIRC. The deal breaking marker flag is sse4_2 that is missing[1]. If the CPU is in a 775 or older motherboard socket, AFAICT it's v1. [1] https://en.opensuse.org/X86-64_microarchitecture_levels -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.4 tde-config: 1.0

1 0

Installing packages to /usr
by Darrell Anderson 07 May '25

07 May '25

I notice in my Devuan VM that several TDE packages are installed to /usr rather than /opt/trinity, such as dependency prerequisites and bindings. What criteria is used to decide when to install to /usr? Thanks. :)

2 1

Kerberos support
by Darrell Anderson 06 May '25

06 May '25

* Are the TDE packages providing kerberos support only based on heimdal or is krb5 supported too.? * Is there a list of which TDE packages support kerberos? Thanks. :)

1 0

Building tdepim
by Darrell Anderson 06 May '25

06 May '25

For the various groupware functions, does any respective software need to be installed before compiling? Such as kolab, scalix, exchange, wizards, etc? Should the build fail if any underlying software is not installed and those features are enabled? I looked in the wiki and did not find anything related to tdepim requirements, but perhaps I missed the page. Thanks. :)

2 1

CMake conversions
by Darrell Anderson 05 May '25

05 May '25

When attempting to build 14.1.4 packages, are the cmake conversions listed in the wiki now required to build or can the packages still use automake? https://wiki.trinitydesktop.org/Release_Notes_For_R14.1.4#CMake_conversions Thanks. :)

2 2

Testing back traces
by Darrell Anderson 05 May '25

05 May '25

I am creating a Slackware build environment. I want to test back traces (not tripping out symbols). I seem to recall there was a way to test this in TDE but I don't remember. How to test back traces and symbols? Thanks. :)

3 4

Beware the ides of openssh 10 version detection on konqueror/kate/kwrite sftp://
by David C Rankin 05 May '25

05 May '25

Devs, openSUSE Tumbleweed just had an issue with the sftp kio not detecting the ssh version with openssh-10 breaking sftp:// in konqueror/kate/kwrite etc. Yasuhiko has a fix. (I don't have a link yet). It apparently has to do with how a regex was written, likely the 2-digit '10' was too much for the old one. Just a heads up. I'll see if I can get a link from him. -- David C. Rankin, J.D.,P.E.

1 1

PyTQt: ModuleNotFoundError: No module named 'sip_tqt_config'
by Darrell Anderson 04 May '25

04 May '25

I'm trying to build TDE bindings packages for Slackware. I'm not a Python wiz kid and don't play one on TV. I understand what is happening in the failure but don't know how to fix. My pytqt build script fails with: ModuleNotFoundError: No module named 'sip_tqt_config' Caused by the configure.py command: import sip_tqt_config I presume the sip4-tqt package built okay because such a file does exist: /usr/lib64/python3.9/site-packages/sip4-tqt/sip_tqt_config.py Running the following command exits with a zero exit code: python3 /usr/lib64/python3.9/site-packages/sip4-tqt/sip_tqt_config.py Running a python shell: import sys print(sys.path) ['', '/usr/lib64/python39.zip', '/usr/lib64/python3.9', '/usr/lib64/python3.9/lib-dynload', '/usr/lib64/python3.9/site-packages'] Here is how I compiled sip4-tqt: PYTHON_SITE_PACKAGES=$(python3 -c "import site; print(site.getsitepackages())" | cut -d ',' -f1 | tr -d "'" | tr -d "\[") FLAGS="$CPUOPT -I${INSTALL_DIR}/include/tqt -I/${INSTALL_DIR}/include -I/usr/include" python3 configure.py \ -b "${INSTALL_DIR}/bin" \ -d "${PYTHON_SITE_PACKAGES}/${PRGNAM}" \ -e "${INSTALL_DIR}/include/" \ -u CFLAGS="$FLAGS" CXXFLAGS="$FLAGS" Where $INSTALL_DIR=/opt/trinity. Here is how I am trying to compile pytqt based on my poor understanding of the Debian rules script: PYTHON_VERSION="$(python3 -V | cut -f 2 -d' ' | cut -f 1-2 -d.)" PYTHON_SITE_PACKAGES="$(python3 -c "import site; print(site.getsitepackages())" | cut -d ',' -f1 | tr -d "'" | tr -d "\[")" FLAGS="$CPUOPT -I${INSTALL_DIR}/include/tqt -I/${INSTALL_DIR}/include -I/usr/include" python3 configure.py \ -b "${INSTALL_DIR}/bin" \ -d "${PYTHON_SITE_PACKAGES}/${PRGNAM}" \ -e "${INSTALL_DIR}/include/" \ -l /usr/include/python${PYTHON_VERSION} \ -v ${PYTHON_SITE_PACKAGES}/sip4-tqt/ \ -m /usr/lib${LIBDIRSUFFIX}/python${PYTHON_VERSION}/config-3.9-x86_64-linux-gnu \ -z CFLAGS="$FLAGS" CXXFLAGS="$FLAGS" Where $INSTALL_DIR=/opt/trinity. Fish out of water.... Thanks. :)

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels