- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 30 2023
On Windows, we had to revert to the old approach which doesn't show progress because KIO::move doesn't work on Windows when crossing partition boundaries. We want to fix this in KIO for a future release. Windows users will have to live without progress for now.
Fixed as suggested by Andre. Additionally, I have added support for hidden files in the old code (which are probably not really a thing on Windows). The downside is that there is no progress on Windows (as before the switch to using KIO::move).
Let's schedule that for 2.6
Possibly, it may consider the case where errno==0 when failure.
Hmm, gcc used to figure out that attr is initialized by npth_mutexattr_init. One of these gcc warning regressions?
May 29 2023
Fix merged to release/23.04 branch.
And thanks gniibe! I have tested 2.4.1 several times in this month (including existing and new keys), the warning was never shown again.
Hi zhangguangzhi, I think that it's version-specific problem.
I traced the chain and this warning message was added in release 2.3.3 T5565.
The problem should be able to reproduce between 2.3.3 and 2.4.0.
Hi,i try to reproduce the problem, my platform is linux and gnupg2-2.2.32-3, but i can't find “gpg: warning: lower 3 bits of the secret key are not cleared". Excuse me, is this a platform-specific or version-specific problem, or is it my operation wrong.
May 28 2023
May 26 2023
Due to back porting another change the fix for 2.2 is now also needed in 2.4.
So the reason this fails is the same as it was back when T3547 was fixed. MoveFile does not work across directories, and even MoveFileEx that supports this for files does not support this for directories.
May 25 2023
FWIW: I have not done any tests but the comment below is about the case I suspected to be the cuase for your problem:
See rG0988e49c45 which implements time and group but not yet the split thing because we are not shure that is good idea to have this w/o any implementation support.
The fix actually does the same as my suggested workaround.
There is an easy workaround: Append an exclamation mark to the adsk key. This way gpg will only search for this subkey.
An example with my test keys:
secring.gpg is only used by unsupported legacy versions of GnuPG. Since 2.1 it is not anymore used.
Since it's ABI change, I created a branch: https://dev.gnupg.org/source/libassuan/history/gniibe%252Ft6487/
May 24 2023
So if I have \MyDirectory\pubring.pgp and MyDirectory\secring.pgp files, how do I use the --homedir option to access those?