tde-devels

devels@trinitydesktop.org

7 participants
3785 discussions

pytdeextensions FTBFS on debian/testing and patch
by Michele Calgaro 02 Sep '13

02 Sep '13

Hi there, today I run into a FTBFS when building libraries/pytdeextensions on debian/testing (jessie). The package actually compiles, but the building process actually fails after that when invoking "dh_python". dh_python -ppytdeextensions-trinity make: dh_python: Command not found I tracked down the problem to be in the file "debian/python-distutils-jaunty.mk", where "dh_python2" needs to be invoked instead of "dh_python" and prepared a patch for it. While looking at the problem I also spotted that the patch "11_fix_get_libdir_name.diff" was out-of-sync with the code by 63 lines, so I updated the patch to point to the correct line. With both patches, the package builds correctly. I don't know if you are having the same problem I had. The nightly built package is not ready at the time of writing (it is schedule for building in a few hours), so I can't compare. I don't know whether the patch for "dh_python" breaks the building for debian/wheezy, since last year I didn't have any problem compiling in such environment. If so, a separate entry needs to be created in the tde-packaging for debian/jessie (instead of pointing to wheezy) and the patch added to the "libraries/pytdeextensions" files. Cheers Michele

2 1

Re: [trinity-devel] X-KDE -> X-TDE
by Darrell Anderson 01 Sep '13

01 Sep '13

>Not for R14.0.0, but we can look into it for R14.1.0. We will >need some >degree of upstream cooperation in various projects so as not to >break >things like automatic tdesudo prompts for administrative programs. In hindsight, there might not be many changes. I grepped the sources and there are not many || tests. As you just mentioned, Slavek also previously explained to me that some of the || tests are necessary to support non-TDE su/sudo apps. Darrell

1 0

X-KDE -> X-TDE
by Darrell Anderson 01 Sep '13

01 Sep '13

While reviewing the upcoming patch set for LIB_K* -> LIB_TDE* I noticed some things. There are a handful of spots in the sources where readEntry looks for X-TDE-* || X-KDE-*. We can't blindly change all such occurrences because many are legitimate, such as the tdebase/applnk files that support KDE4 menus and some occasional spots where code is supporting both TDE and KDE4 (such as su). Yet I think in many of those || tests we can eliminate the test for readEntry X-KDE-*. I don't see this as an urgent issue and I'll open a bug report if asked. We can resolve those || tests in R14.0.1 or R14.1.0. Comments? Thoughts? Darrell

2 1

Re: [trinity-devel] LIB_KUTILS->LIB_TDEUTILS
by Darrell Anderson 01 Sep '13

01 Sep '13

>> When do you think this update will be completed? > >I'm working hard on it. Because by using >convert_existing_kde3_app_to_tde were >found some hidden and omissed mistakes, patches are larger => >require more >effort to verify. Completed it should be on a Sunday evening. I'm helping Slavek review the patch set. Hopefully later today we both start full build sets to check for both compiling and usability issues. A full build set at my end takes about 9.5 hours. Darrell

1 0

Re: [trinity-devel] LIB_KUTILS->LIB_TDEUTILS
by Darrell Anderson 01 Sep '13

01 Sep '13

>I'll do it. > >Because the change must be reflected also in >convert_existing_kde3_app_to_tde, >I can use this script to update all modules. > >The change relates to: >+ LIB_KDNSSD >+ LIB_KIMPROXY >+ LIB_KIO >+ LIB_KPARTS >+ LIB_KSPELL >+ LIB_KSYCOCA >+ LIB_KUNITTEST >+ LIB_KUTILS > >If I missed some, please let me know. Looks like common/admin/acinclude.m4.in might help, starting at line 2315: AC_SUBST(LIB_KDED, $lib_kded) AC_SUBST(LIB_TDECORE, "-ltdecore") AC_SUBST(LIB_TDEUI, "-ltdeui") AC_SUBST(LIB_KIO, "-ltdeio") AC_SUBST(LIB_KJS, "-lkjs") AC_SUBST(LIB_SMB, "-lsmb") AC_SUBST(LIB_KAB, "-lkab") AC_SUBST(LIB_TDEABC, "-ltdeabc") AC_SUBST(LIB_TDEHTML, "-ltdehtml") AC_SUBST(LIB_KSPELL, "-ltdespell") AC_SUBST(LIB_KPARTS, "-ltdeparts") AC_SUBST(LIB_TDEPRINT, "-ltdeprint") AC_SUBST(LIB_KUTILS, "-ltdeutils") AC_SUBST(LIB_TDEPIM, "-ltdepim") AC_SUBST(LIB_KIMPROXY, "-ltdeimproxy") AC_SUBST(LIB_KNEWSTUFF, "-lknewstuff") AC_SUBST(LIB_KDNSSD, "-ltdednssd") AC_SUBST(LIB_KUNITTEST, "-ltdeunittest") # these are for backward compatibility AC_SUBST(LIB_KSYCOCA, "-ltdeio") AC_SUBST(LIB_TDEFILE, "-ltdeio") From that list we can find the following: LIB_KIO LIB_KSPELL LIB_KPARTS LIB_KUTILS LIB_KIMPROXY LIB_KDNSSD LIB_KUNITTEST LIB_KSYCOCA That list matches your list. Do you need help with the patching? Darrell

4 6

Re: [trinity-devel] LIB_KUTILS->LIB_TDEUTILS
by Darrell Anderson 31 Aug '13

31 Aug '13

>Yes, we have drawn from the same source :) > >To avoid inconsistent state modules × admin module, I am preparing >to integrate all as bulk. That's fine. >Processing on my machine is still running. Then I'll check the >patches, before >I start to commit. So the question is, if you want help with >control patches >before commit? Patches are a little bigger (and not yet all >ready). It is not >a good idea to send them to mailing list. Provide me a link if you want me to help test the patches. :-) Darrell

1 0

LIB_KUTILS->LIB_TDEUTILS
by Darrell Anderson 31 Aug '13

31 Aug '13

All of the Makefiles include references to LIB_KUTILS, but the libraries were renamed to tdeutils*. As long as we are moving quickly with various renames at the moment, should we rename LIB_KUTILS -> LIB_TDEUTILS? I know this requires changes to all admin directories and complete rebuilds for everybody, but seems like the correct thing to do. Darrell

3 4

Re: [trinity-devel] LIB_KUTILS->LIB_TDEUTILS
by Darrell Anderson 30 Aug '13

30 Aug '13

>> All of the Makefiles include references to LIB_KUTILS, but the >> libraries were renamed to tdeutils*. As long as we are moving >> quickly with various renames at the moment, should we rename >> LIB_KUTILS -> LIB_TDEUTILS? I know this requires changes to all >> admin directories and complete rebuilds for everybody, but seems >> like the correct thing to do. >> >Go ahead, but quickly please. :-) What is the proper way to push the change to common/admin/acinclude.m4.in? (I don't recall ever pushing a patch to admin files.) That is the sole file in common that needs updating (although many modules need touching). Darrell

2 1

tdebindings FTBFS in parallel-tests (with automake 0.13.3)
by Slávek Banko 30 Aug '13

30 Aug '13

Hello, during build tdebindings on Debian Jessie (automake 0.13.3) occurs FTBFS in parallel-tests due to missing admin/test-driver. Because it concerns to the common admin module, the proposed fix will be reflected in all modules. Please, you can test it before I push the patch? Thanks Slavek

3 6

*.kdevelop/*.tdevelop files
by Darrell Anderson 27 Aug '13

27 Aug '13

There remain a handful of *.kdevelop files, which for consistency with other modules, should be renamed to *.tdevelop: applications/kasablanca/kasablanca.kdevelop applications/kbibtex/kbibtex.kdevelop applications/kkbswitch/kkbswitch.kdevelop applications/klcddimmer/klcddimmer.kdevelop applications/ksensors/ksensors.kdevelop applications/kshutdown/kshutdown.kdevelop applications/kvpnc/kvpnc.kdevelop applications/mplayerthumbs/mplayerthumbs.kdevelop applications/tork/tork.kdevelop Regardless, do these *.kdevelop/*.tdevelop files serve any meaningful purpose? If not should we purge them from the sources? Darrell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels