Thanks. For the record, done at https://lists.gnupg.org/pipermail/gnupg-users/2023-August/066692.html.

What I would like to be able to do would be:

Why do you need an integer - for real random this must be larger than 64 bits and then you have problems to to find a suitable type for a variable.

This is now mostly done. These 3 patches make it work:

https://invent.kde.org/pim/eventviews/-/merge_requests/90

For reference this is the code used to fill the pubkey table:

static gpg_error_t
store_into_pubkey (enum kbxd_store_modes mode,
                   enum pubkey_types pktype, const unsigned char *ubid,
                   const void *blob, size_t bloblen)
{
  gpg_error_t err;
  const char *sqlstr;
  sqlite3_stmt *stmt = NULL;

You are right - issuing an SQL statement returns the rrror. Hwoever, the selfcheck from sqlitebrowser does not show any errors.

I guess we should follow the GNU standards and provide only info files ;-)

Firstly, I clean up the code with each individual thread for monitoring something; That's T6692 and T6693.
Then, I pushed rG76a2f180286e: agent: Better interaction between main loop and cache expiration. and rG92de0387f04b: agent: Introduce management of timer to expire cache entries.
No more use of tick, but timers.

Other problems of yat2m transformation:
https://bugs.debian.org/1050886

Nothing to test (except that the tool tips are now shown for the widgets).

In T6679#174951, @werner wrote:

The copy of the database we received for this case is not damaged. A possible problem might be insufficient rights to read the database. For example created with an Admin account and then later used by a different user.

The copy of the database we received for this case is not damaged. A possible problem might be insufficient rights to read the database. For example created with an Admin account and then later used by a different user.

It's pushed by rG716e59b0b628: agent: Add agent_kick_the_loop function.

Pushed the change by rG7025375e8bec: agent: Have a thread monitoring parent PID and homedir.
It depends on T6682 to wake up the loop.

Push the code by rG95186ae92f92: agent: Use a thread to monitor socket takeover.

Thank you for the response, @werner! (original reporter here)

BTW. you should use gpg --quick-set-expire FINGERPRINT 5y this is easier for scripting. Using
--export-options no-export-clean should keep the old signatures.

gpg only uses the latest self-signatures and ignores old one. Thus I do not understand your problem.