> Yeah, sorry, there should be --export.
>
Great!
gpg --no-default-keyring --export --keyring /etc/apt/trusted.gpg >
/etc/apt/trusted.gpg.new
fixed the problem. I now need to decide whether I should nuke and pave.
The only question that remains is: how did this happen? There must be an
issue
> That's your problem. Run
>
> gpg --no-default-keyring --keyring /etc/apt/trusted.gpg >
> /etc/apt/trusted.gpg.new
> mv /etc/apt/trusted.gpg.new /etc/apt/trusted.gpg
>
> To convert the keybox file back to a key ring.
>
>
The gpg command hangs. If I issue it without the pipe I get:
gpg: Go
> ... In the gmail web UI,
> you click on the three dots and then move your cursor to the position
> where you want to start writing (I actually forgot to add this to the
> previous email...).
>
OK. I'm not a fan of a UI where the same element does very different
things. In the past there was a
:01.468603835 +1000
Modify: 2017-05-29 17:45:53.533125958 +1000
Change: 2017-05-29 17:45:53.533125958 +1000
Birth: -
So, it doesn't look like the issue?
Thanks, Pete
On 26 May 2017 at 19:51, Julian Andres Klode <j...@debian.org> wrote:
> On Fri, May 26, 2017 at 06:21:23PM +1000, Pet
using Testing, but there
must be a way out of here.
Regards, Pete Miller
On 25 May 2017 at 21:33, Julian Andres Klode <j...@debian.org> wrote:
> On Thu, May 25, 2017 at 08:23:34PM +1000, Peter Miller wrote:
> > Julian,
> >
> > There is no such thing as perfect security. I
property ownership, so I
appreciate matching effort to risk.
Thanks, Pete
On 25 May 2017 at 19:00, Julian Andres Klode <j...@debian.org> wrote:
> On Thu, May 25, 2017 at 06:49:31PM +1000, Peter Miller wrote:
> > David,
> >
> > Thanks for your time on this. I am surprised that
David,
Thanks for your time on this. I am surprised that the answer to this issue
is a re-install: it's only the keys that are corrupt somehow, and I am
surprised there is not a simple way to fix this. I have an unusual setup
with a mirrored ZFS pool as my home directory, so I'm a little
Julian,
I thought doing one update might fix the issue, since nothing else was
working, hence --allow-unauthenticated.
I did not install or update anything in /etc/apt/trusted.gpg.d, or anywhere
else similar, so how did it get corrupted? Is there a source issue? Are
there automated checks after
adding code to the scripts that involve EACCES or EPERM, so
that they pass by default if they are run by root.
starting at a
---
starting at /tmp/libexplain-10570/a
This has a different cause. The chroot probably doesn't have /proc
mounted. I will add a check for this in the test.
--
Peter
On Sat, 2012-03-03 at 13:17 +, Neil Williams wrote:
Having a test suite which is dependent on the architecture-dependent
configuration of the running kernel is going to be permanently
problematic in a Debian buildd infrastructure...
As I learn of these issues I fix them, to the extent
fixed in version 0.24
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
table,
or not.
How exactly do you manage to build this on your own but make it fail
on most other machines?
Because each Linux architecture, as seen from the perspective of this
library, is actually different. I am not intentionally making it
fail.
--
Peter Miller pmil...@opensource.org.au
On Wed, 2009-06-10 at 08:27 +1000, Peter Miller wrote:
On Tue, 2009-06-09 at 14:24 +0200, Christoph Berg wrote:
This is not your key.
On further checking, I'm not sure what you are telling me.
That key is what gpg --armor --export D0EDB64D reports,
and D0EDB64D is most definitely my key.
I
Package: debian-maintainers
Version: 1.54ubuntu1
Severity: normal
new DM application for Peter Miller
-- System Information:
Debian Release: 5.0
APT prefers jaunty-updates
APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500,
'jaunty-backports'), (500, 'jaunty')
Architecture
--
Regards
Peter Miller pmil...@opensource.org.au
/\/\*http://miller.emu.id.au/pmiller/
PGP public key ID: 1024D/D0EDB64D
fingerprint = AD0A C5DF C426 4F03 5D53 2BDB 18D8 A4E2 D0ED B64D
See http://www.keyserver.net or any PGP keyserver for public key.
Comment: Add Peter Miller pmil
attached the output of
gpg --armor --export D0EDB64D D0EDB64D.pub
That is definitely my public key.
--
Regards
Peter Miller pmil...@opensource.org.au
/\/\*http://miller.emu.id.au/pmiller/
PGP public key ID: 1024D/D0EDB64D
fingerprint = AD0A C5DF C426 4F03 5D53 2BDB 18D8 A4E2 D0ED
likely alternatives in error messages. Fuzzy
comparisons for byte arrays, wide character strings, and
multi-byte character strings are also available. In addition,
there are integer alternatives for systems with slow floating
point emulation.
--
Regards
Peter Miller
Miller [EMAIL PROTECTED]
License: LGPL
Packages built on Ubuntu Intrepid: http://libexplain.sourceforge.net/
Regards
Peter Miller [EMAIL PROTECTED]
/\/\*http://miller.emu.id.au/pmiller/
PGP public key ID: 1024D/D0EDB64D
fingerprint = AD0A C5DF C426 4F03 5D53 2BDB 18D8 A4E2 D0ED B64D
See
, or packages being build outside Aegis' control? Either way, what
files are involved?
A patch is below.
Thanks. It will be in the 4.22 release.
--
Regards
Peter Miller [EMAIL PROTECTED]
/\/\*http://www.canb.auug.org.au/~millerp/
PGP public key ID: 1024D/D0EDB64D
fingerprint = AD0A C5DF
19 matches
Mail list logo
