- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 7 2024
Mar 6 2024
See also rG40b85d8e8cecadf35e51e84b30de4fac820d714b for gnupg 2.4.
Sorry, for not following up earlier. Can you please do me a favor and run the last tests again, this time adding -v and --debug 1 to the invocation? Feel free to forward the output to my private address is that is easier (wk at gnupg.org).
Mar 5 2024
We migrated to another box and it might be the case that we planned to also support https. I need to see whetehr I can find notes in the etckeeper.
Mar 4 2024
How to test:
Mar 1 2024
In 2.4 we have rG1383aa475 which does
Feb 29 2024
Feb 28 2024
Although I don't think this is the case here one should be aware that tests mail fail due to global configuration of GnuPG (/etc/gnupg/*.conf). There is no easy way so solve this except for running a per-test local installation of GnuPG using the gpgconf.ctl feature.
Feb 27 2024
Arghh, a GPGME_DEBUG=3 which shows basic I/O preparation does not exhibit the bug.
Fixing gpg is easy but there is some bug lingering in gpgme which might be a recent regression. An strace shows
Those options where originally intended for debugging but your suggestion makes sense. I also add this to most other tools.
Feb 26 2024
At the failed attempt I notice a DEVINFO_STATUS removal soon after the SWITCHCARD. This is related to the reader status file and triggered by ccid_slot_status. --debug ipc.app,reader might be a better selection of debug flags here.
Feb 23 2024
I think we should close this bug or re-purpose it to silence those warnings in common cases.
That could be fixed in src/argparse.c:set_opt_arg by adding and endptr to the strtol calls and check that only white space follows. However, there is some risk of regression with this approach. Maybe just display a warning?
Removing gpgrt because we meanwhile have full utf-8 support there.