l10n daemon script <scripty@kde.org> committed
rKLEOPATRAe2a770f1874b: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
Problem with SHA-256 on x86-64 is that it took long time for Intel to introduce SHA acceleration (SHA1 & SHA256) to their main CPU products.
po: Fix small typos in German translation
Add tomorrow as release date for gpg4win-4.2.0
Fix name in okular hack patch
Add patch to customize okular bugurl
Noticed in gpg4win 4.2.0-beta373:
😂 I literally laughed when I saw this. You are taking this so much further and faster then I expected. Great job!
Current progress, the viewer now support viewing embedded calendar events, embedded emails and embedded calendar events in an embedded email
Add page for 4.2.0 version info
sm: Fix open_es_fread and open_es_fwrite for gnupg_fd_t.
sm: Use open_stream_nc for do_listkeys.
sm: Use gnupg_fd_t and open_stream_nc for assuan_get_input_fd.
sm: Use open_stream_nc for HANDLE by assuan_get_output_fd.
l10n daemon script <scripty@kde.org> committed
rKLEOPATRA1ab793f97abb: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
l10n daemon script <scripty@kde.org> committed
rKLEOPATRA25036df92f34: GIT_SILENT made messages (after extraction) (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT made messages (after extraction)
Normal priority to get the _1_ removed when no folder with the same name already exists in that location.
Strip archive extension for CMS folder, too
• aheinecke moved
T6531: Gpgtar behavioral change when extracting archives from
Restricted Project Column to
Restricted Project Column on the
Restricted Project board.
Strangely enough this does not happen on linux. Maybe related to the KMime changes we have there?
Remove KTextWidgets from optional Okular deps
Revert "Remove KF5TextWidgets from non required deps"
Switch poppler to current master snapshot
Remove KF5TextWidgets from non required deps
For S/MIME archives the output for e.g. testfolder.tar.gz.p7m is now named "testfolder.tar.gz_1_/testfolder" with the "_1_" even added if there is no "archive.tar.gz"
gpg: Add support for Subkey-Expire-Date.
Merge remote-tracking branch 'origin' into kf6
gpg: Fix expiration time when Creation-Date is specified.
Fixed in master.
Will backport into 2.4, after testing.
Use unsigned int for a bit field.
l10n daemon script <scripty@kde.org> committed
rKLEOPATRA2b991692f88f: GIT_SILENT made messages (after extraction) (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT made messages (after extraction)
Appimage: Remove NSS devel from packages
Fix uninstallation of xmlgui subdirs for okular
Appimage: Add Qt5Qml to disabled package list
Current progress left being the qml version for Kalendar and right the QtWidget version for Kleopatra. This still require some work in the QtWidget viewer to display that the message is signed and encrypted
gpg: Move the check by is_secured_file earlier.
common: Change iobuf_fdopen argument type to gnupg_fd_t.
common: Add gnupg_check_special_filename.
common,gpg,kbx: Factor out open_stream_nc.
l10n daemon script <scripty@kde.org> committed
rKLEOPATRA2dc41ad6b63b: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
So some more data from 2.4.3. Once unpatched and once with your patch.
NEWS, doc: Remove mention of brainpool transfer
Switch Kleopatra and libkleo to gpg4win/23.07 branch
Require 23.04 version of kpimtextedit
Require 23.04 version of kmime, don't require optional dependencies
One complication comes from the fact that gpgmepp and qgpgme include the global that is generated by configure. This needs to be replaced. I'll attach two files where I grepped for usage of the 's s (generated on Linux) in and . The files probably contain false positives.
I was able to find the Craft blueprint with the CMake build system in my Win VM and pushed it to invent: , feel free to use it for inspiration or base for future work, or ignore it completely :). It's probably far from a production-ready CMake script, some years ago I just really really *really* wanted to build KMail on Windows (don't ask why) so I did some unspeakable evils to make it happen. This is one of the better things that came out of it...
Add upstreamed patch for Okular
With the added MIME types Kleopatra now suggests as new file name, at least on Linux. Needs to be checked on Windows.
Add MIME types for signed and encrypted archives
common:w32: Fix gnupg_w32_set_errno.
common:w32: Fix gnupg_w32_set_errno.
l10n daemon script <scripty@kde.org> committed
rKLEOPATRA9454960c6d9c: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
Merge remote-tracking branch 'origin' into kf6
qt: Fix DLL version in cmake config files
qt: Ensure that we check the correct paths
qt: Fix check for required files
Merged into master: and should be available in Release 23.08.
I had to fix it anyway in order to be able to provide screenshot for the latest blog post about encrypting invitations :)
l10n daemon script <scripty@kde.org> committed
rKLEOPATRA2be91e19595f: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
l10n daemon script <scripty@kde.org> committed
rKLEOPATRA659c5424163f: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
Readd missing cmake requirement patch for Okular
Update okular config call
blog: Add an upstream version note
NEWS: Update spelling and language corrections
Update KDE Applications to latest
Update make-msi.guids from releasehost
swdb: release GpgOL 2.5.8
See T6585 for the 1.21.0 release
• werner updated the task description for
T6463: Release GPGME 1.20.0.
Post release version bump
Update NEWS for todays release
Am I correct that the reason for the speed up is that it can use a second CPU's engine. If there is a real performance improvement here, we should add this for example using a --compatibility-flag. This way we can gather experience and eventually make it the default. The compatibility flags won't introduce an API incompatibility.