Re: debuild finds no secret key after dist-upgrade (original) (raw)
[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]
- To: debian-mentors@lists.debian.org
- Subject: Re: debuild finds no secret key after dist-upgrade
- From: Andrey Rahmatullin <wrar@debian.org>
- Date: Fri, 15 Sep 2017 23:03:30 +0500
- Message-id: <[🔎] 20170915180330.idhigeddwyfzjhyl@belkar.wrar.name>
- In-reply-to: <[🔎] 25048756627690738769@scdbackup.webframe.org>
- References: <[🔎] 24650756628002111141@scdbackup.webframe.org> <[🔎] 25048756627690738769@scdbackup.webframe.org>
On Fri, Sep 15, 2017 at 07:54:30PM +0200, Thomas Schmitt wrote:
I forgot to use ls option -a when looking. There is a .gpg-v21-migrated. With an astounding ctime/mtime date:
-rw-r--r-- 1 thomas thomas 0 Aug 21 2015 .gpg-v21-migrated
So this seems already to have happened 2 years ago, when i set up that system and gave it the key from my workstation. So I suppose the gpg2 migration ran before you added the key to gpg1?
Now i have no idea at all why my secret key is suddenly gone. WHy are you saying they are gone if secring.gpg still exists? gpg2 just doesn't use it and you already know that. I guess you'll need to do the migration again (try deleting .gpg-v21-migrated?).
-- WBR, wRAR
Attachment:signature.asc
Description: PGP signature
Reply to:
- Follow-Ups:
- Re: debuild finds no secret key after dist-upgrade
* From: "Thomas Schmitt" scdbackup@gmx.net
- Re: debuild finds no secret key after dist-upgrade
- References:
- Re: debuild finds no secret key after dist-upgrade
* From: "Thomas Schmitt" scdbackup@gmx.net - Re: debuild finds no secret key after dist-upgrade
* From: "Thomas Schmitt" scdbackup@gmx.net
- Re: debuild finds no secret key after dist-upgrade
- Prev by Date:Re: debuild finds no secret key after dist-upgrade
- Next by Date:Re: debuild finds no secret key after dist-upgrade
- Previous by thread:Re: debuild finds no secret key after dist-upgrade
- Next by thread:Re: debuild finds no secret key after dist-upgrade
- Index(es):