----- KRYPTIVA PACKAGED MESSAGE ----- PACKAGING TYPE: SIGNED Bernhard R. Link wrote:
Okay, I expected that... I just did a dist-upgrade and everything is suddenly back in working order. I correctly got asked the passphrase to the GPG key then the process completed successfully. I have no idea what was wrong last week. > Looking at this versions, that seems to be a stable libgpgme and an > testing/unstable libgpg-error and unstable libdb4.3. I had downgraded libgpgme11 to the 'testing' version. I wanted to see if the problem was caused by an upgrade to libgpgme11. The same problem happened with libgpgme11 1.1.5 in unstable. > it always check before writing, I guess the libgpgme code causes > this. Looks like I'll have to add something to ignore that signal, > then. :-( It's more than likely that libgpgme was/is the source of the problem. I just can't confirm it well enough to post a bug there. ----- KRYPTIVA SIGNED MESSAGE ----- This email claims to have been packaged by Kryptiva. To process this email and authenticate its origin, get the free plugin from: http://www.kryptiva.com/downloads ----- KRYPTIVA SIGNATURE START ----- AvWVqAAAAAIAAAABAAAAAAAATiACAQAAAAC3AQAIAAAAAwAAAAECABS3FuvxegTt63v7UWCF iSdtKgVqvAMAFNtYnPf/czq1EyEfvnKRBT4kXaMpBAAUwE9zWB8V95nnwDISPpTDaMZtlIkF ABTaOaPuXmtLDTJVv++VYBiQr9gHCQYAFDuNARRvjNC64Ot9WqpwR2+z0V3UBwAUe4bu019N 2Nwgdg07693LziAURncRABgAAAAAAABOIEbAS1wAA16LAAAAAAAAFKkTAAQAAAAAAAAAggP9 H6ngz1VatsudKIGurNtrozwc/5Cy5foQLNHRqa01tobHidoLexY6O0WwKQiJuwdYbXZWMXpQ KiwE0ngwndK+/FbgRWjhXyhGWZnMZqruRwiESNCDWlvW6nqfTqwkbmKwn1tTDfxaznAgte3L QfxnG73fIF1pI2GNfIxTYh3/2z8= ----- KRYPTIVA SIGNATURE END ----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
