hello duplicity experts,
in a restore from a simple file:/// backend, I get this message:
[...]
Extracting backup chains from list of files:
['duplicity-full.20230408T002440Z.vol1.difftar.gpg',
'duplicity-full.20230408T002440Z.vol2.difftar.gpg',
'duplicity-full.20230408T002440Z.vol3.difftar.gpg',
'duplicity-full.20230408T002440Z.vol4.difftar.gpg',
'duplicity-full.20230408T002440Z.vol5.difftar.gpg',
'duplicity-full.20230408T002440Z.vol6.difftar.gpg',
'duplicity-full-signatures.20230408T002440Z.sigtar.gpg',
'duplicity-full.20230408T002440Z.manifest.gpg']
File duplicity-full.20230408T002440Z.vol1.difftar.gpg is not part of a known
set; creating new set
File duplicity-full.20230408T002440Z.vol2.difftar.gpg is part of known set
File duplicity-full.20230408T002440Z.vol3.difftar.gpg is part of known set
File duplicity-full.20230408T002440Z.vol4.difftar.gpg is part of known set
File duplicity-full.20230408T002440Z.vol5.difftar.gpg is part of known set
File duplicity-full.20230408T002440Z.vol6.difftar.gpg is part of known set
File duplicity-full-signatures.20230408T002440Z.sigtar.gpg is not part of a
known set; creating new set
Ignoring file (rejected by backup set)
'duplicity-full-signatures.20230408T002440Z.sigtar.gpg'
Processing local manifest
b'/repos/.duplicity-cache/ec738e980e6a6d3ec6b3fb3bdd0f6196/duplicity-full.20230408T002440Z.manifest'
(5711)
[...]
Is this a problem? The restore seems to be ok.