off64_t mat not the same as int64_t

Breaks them how?

In D600#6438, @werner wrote:

This breaks existing 32 bit systems with the 64 bit types.

This breaks existing 32 bit systems with the 64 bit types. Thus a test for off64_t is required which redefines it to int64_t if it does not exist.

Another remark: It's very easy to change the location of the kleopatragroupsrc because we have full control over its usage and can simply specify an absolute path for the file. If the file isn't found we can simply look in the old location, i.e. migration is also trivial (as long as we can reliably determine the old location).

Fixed and backported for VSD 3.3

Let me remark, that we don't need a general migrator. We only need to make sure that the kleogroups are somehow migrated. Maybe we should do this along with the change of these group files (signing, v5 fingerprints). In any case it is important to get this into vsd33

Alternatively to patching QStandardPaths we could probably patch KConfig (e.g. make KConfigPrivate::changeFileName use a path set by us instead of QStandardPaths::writableLocation(resourceType)). In any case, I see no other solution that patching the base libraries.

What is the status here? Werners opinion is that only the kleopatragroupsrc needs to be migrated.

I think it needs to be made more clear that the proposed options refer to what to do after (!) copying the secret key to the smart card, e.g.

Was mentioned before, but not written here:

We decided to go with Tobias' proposal.