tde-devels August 2017

devels@trinitydesktop.org

3 participants
3 discussions

pinentry-tqt
by deloptes 22 Aug '17

22 Aug '17

Hi I am not sure if someone is interested but I played with pinentry recently and produced a working executable from pinentry-0.8.3 (qt3 code ported to tqt) and a base of pinentry-0.9.7. I just can't do the packaging myself so that I may replace the existing pinentry-* with the one I modified, so that it satisfies all dependencies. I can provide the binary if someone wants to use it for now, but the question here is wouldn't it be better to get the code into the official pinentry project? and why is kleopatra-trinity* kmail-trinity* kmailcvt-trinity* kontact-trinity* tde-trinity* tdepim-trinity* dependant on pinentry-qt/qt4 ? Is it because pinentry-qt was previously qt3, but now qt5? It pulls in qt5 libraries which I want to avoid. regards

2 3

kgpg and key dates
by deloptes 06 Aug '17

06 Aug '17

I upgraded to stretch and testing 14.1 (DEV) Unfortunately when trying to send a gpg signed message today I realized that gpg is not working properly. I started from command line and saw message gpg2 migration successfull. I also see a file .gpg-v21-migrated When I start kgpg from command line it shows many line with invalid date. Gpg however lists all keys with properly displayed date. Kgpg does not display date or name assigned to key. I managed to find out that the date in the key is a unix timestamp, but in kgpg we have TQDate fromString with QT:ISODate, which forces fromString to split the string instead using it as unix time stamp. I did following to fix it if (ret.gpgkeyexpiration.isEmpty()) ret.gpgkeyexpiration=i18n("Unlimited"); else { TQDate date = TQDate::fromString(ret.gpgkeyexpiration, Qt::ISODate); if (!date.isValid()) { TQDateTime timestamp; timestamp.setTime_t(ret.gpgkeycreation.toInt()); date = timestamp.date(); } However I need to look into why the names are not shown properly. Perhaps we'll get a patch Can you confirm this? I created a Bug 2791 regards

1 4

trinitydesktop.org bugs.pearsoncomputing.net
by deloptes 02 Aug '17

02 Aug '17

Hi all, both domains are unreachable at the moment. Is it a local issue here or something gone wrong at the other end? PS: I wanted to upload improved patch to kgpg, but failed to get there. regards

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels August 2017