tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

bugattach.pearsoncomputing.net uses an invalid security certificate
by deloptes 07 Jul '16

07 Jul '16

1 0

My_Documents mangled UTF8
by deloptes 05 Jul '16

05 Jul '16

Hi, in the course of vcard and the encoding issue I ask herewith for help to solve another annoying utf8 encoding issue. Problem: Attached images show that My_Documents when language set to bg gets mangled. Unfortunately looking into this I found out it is mangled in /opt/trinity/share/apps/kdesktop/Desktop/My_Documents I tested in fresh install of TDE, but after first logout/login it changed I workaround it by fixing the file and removing the write permissions. I don't know where to look for the system:/ entry. regards

3 12

SyncEvolution again trying to finalize the work
by deloptes 03 Jul '16

03 Jul '16

Hi, after few months of testing, I do not see any issues in the TDE backends/plugins. I want to finalize this work and upload the code in some way. I asked SyncEvolution about it [1,2] while trying to build 1.5.1 against synthesis. This required version which is provided in debian sid. Unfortunately I hit a bug [3] and I think I'll try against syncevolution from git as the patch for [3] is still to be uploaded for 1.5.1. What I want to discuss with you based on [1] is if you think it is wise to provide syncevolution-whatever-trinity package(s), which for the moment I think is the best and fast (but not optimal) solution. I will call this short term solution - STS. I think it would be more complex to push each distro to include support for tdepim in syncevolution, but in long term it is the best solution. I will call this long term solution - LTS. However I think there are still few places to improve in the code (the calendar part mostly) and there are some issues in the underlaying libkcal or whatever handles the todo's subject/description when utf-8 and/or quoted content. In fact I dropped support for cal v1 in the plugins as it looks broken and I did not have time to deal with it. SyncEvolution does convert internally a v1 cal into v2 just excellent. So the plan for the STS would be to modify the vendors build scripts (I know only debian ... so debian/*) to produce the syncevolution packages with trinity extention, which will be build with the tdepim/wallet support on top of the vendors configure options. Those packages should replace the vendors own packages and thus provide the tdepim support. The LTS would easy the way that we'll have tdepim/wallet in the mainline, but perhaps we should still provide packages to overwrite the distros shipped package. Based on this what are you thinking? Thanks in advance [1] http://comments.gmane.org/gmane.comp.mobile.syncevolution/5396 [2] http://comments.gmane.org/gmane.comp.mobile.syncevolution/5393 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824426

1 1

dbus vs gdbus in TDE
by deloptes 28 Jun '16

28 Jun '16

Hi another question that popped up when working on syncevolution plugins was the future of dbus. https://www.mail-archive.com/syncevolution%40syncevolution.org/msg05071.html It looks like it is getting replaced by gdbus and I found that libraries are linked to dbus-1 for some reason I do not understand. Example ldd /opt/trinity/lib/libkaddressbook.so | grep dbus libdbus-1-tqt.so.0 => /usr/lib/libdbus-1-tqt.so.0 (0x00007fb69ebb2000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007fb69d452000) ldd /opt/trinity/lib/trinity/libkaddressbookpart.so | grep dbus libdbus-1-tqt.so.0 => /usr/lib/libdbus-1-tqt.so.0 (0x00007f61da129000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f61d89c9000) What are the plans and what can we do in future? thanks and regards

1 0

test target and code
by deloptes 26 Jun '16

26 Jun '16

Hi again, I'm sorry to bother you again with this, but I asked once how I can add a testing target. I started then working on this tdepim libkcal testing stuff again. I still have some issues when my "SUMMARY" or "DESCRIPTION" of event or todo are in cyrillic. Unfortunately I was/am busy at work and I lost all threads .... perhaps you know this feeling ... getting older. I also found the key to building testing targets DEB_MAKE_CHECK_TARGET=testing fakeroot debian/rules build so I think the next exercise (may be long term one) would be to revive the check/testing code laying around. I think I have a good plan 1. fix the libkcal issue "SUMMARY" - "DESCRIPTION" 2. build syncevolution deb packages for TDE 3. fix the libkcal test cases (now a lot of them fail on some date issue - perhaps because originally there was a local zoneinfo data included in the code and now it is not there) 4. start migrating testing to CMake (first in the packages I already have worked with) what do you think? regards

2 6

Repeatable proxy 502 errors
by Mike Bird 23 Jun '16

23 Jun '16

Repeatable proxy 502 errors during apt-get update, e.g.: W: Failed to fetch http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-r14.0.0/ubuntu/d… 502 Proxy Error Appears to be due to no DNS A record for: ppa2.quickbuild.raptorengineering.com FWIW there is an A record for the above if "2" omitted. --Mike

2 1

Trinity on FreeBSD
by Mark Moellering 03 Jun '16

03 Jun '16

Hi, I would like to see Trinity on FreeBSD, so I subscribed to see what I can do. Please let me know how I can help. I run FreeBSD and can code, although I don't have a lot of experience with kernel level programming. Thanks Mark Moellering

2 1

Testing target in cmake
by deloptes 22 May '16

22 May '16

Hi, I was wondering how one can add a testing target in cmake just as it is done in the Makfeile.am in tedelibs and tedepim. There you have check-local: ....... but I don't know how to do it in cmake, so that it compiles but does not run tests except you say make check-local. I think general rule is required and probably added to the tde cmake. I or we could then re-add the tests that were skipped when moving to cmake.

1 0

TDEPIM cmake question
by deloptes 19 May '16

19 May '16

Hi, can someone help quickly please. I am facing an issue with vCal format conversion "quoted printable" and charset: UTF-8. I git cloned the tdepim package and following previous instructions I updated submodule for cmake. I do mkdir testbuild ; cd testbuild; cmake ..; make but nothing happens. What am I doing wrong? This same procedure worked for tdelibs and some other packages. I wanted to debug having the know how to add test capabilities - I wanted to add testing for libkcal and wanted to compile but in vain. Thanks in advance PS: the problem is that fromString is not working (fails) for TODO.

5 13

Re: [trinity-devel] suse 42.1 - crucial(?) trinity package(s) require an unavailable package
by François Andriot 15 May '16

15 May '16

Le 14/05/2016 11:58, Felix Miata a écrit : > > > The "trinity-libarts-akode" package requires the library > > "libakode.so.2", which is supposed to be provided by "trinity-akode" > > package. > > In your case, zypper found that it was provided by "libakode". > > > Notice that the Trinity's package for Akode is split in several smaller > > package, e.g. "trinity-akode" and several "libakode_xxx". > > > I do not even have any 'libakode' package available in my 42.1 > > installation, > > I didn't expect anyone would, since there is no such package in 42.1 > repos for zypper to find. > > > so where does it come from ? > > Maybe it is inherited from a previous opensuse release that you have > > upgraded , or it comes from another 3rd party repository... > > 42.1 in this case is an upgrade (zypper dup) from _Factory_ (before > the name change to Tumbleweed, from an installation last upgraded as > Factory in December 2014). What I don't understand is how to get rid > of the libakode package when the package manager claims other packages > depend on it. Will rpm -e --nodeps not break the TDE packages that > zypper claims depend on it? Why doesn't zypper recognize the trinity* > package(s) you mention as providing the required libs? Are the Trinity > packages broken WRT dependencies? Yes, you can forcibly remove the libakode package (rpm -e --nodeps) and then install trinity-akode , it won't break your system;. It is likely that 'libakode' was installed before Trinity on your computer, and the 'trinity-akode' does not obsolete 'libakode', so it was kept intact. François

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels