Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Gnupg recipe fixes
Date: Mon, 25 Mar 2013 13:39:56 +0000	[thread overview]
Message-ID: <1364218796.3097.49.camel@ted> (raw)
In-Reply-To: <20130325133252.0000678c@unknown>

On Mon, 2013-03-25 at 13:32 +0000, Paul Barker wrote:
> On Mon, 25 Mar 2013 13:25:57 +0000
> Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> > On Mon, 2013-03-25 at 12:57 +0000, Paul Barker wrote:
> > > On Mon, 25 Mar 2013 00:55:05 +0000
> > > Paul Barker <paul@paulbarker.me.uk> wrote:
> > > 
> > > > I'm setting up a signed apt repository of .deb packages built
> > > > using OpenEmbedded and I've ran into an issue with apt-get on the
> > > > target board not being able to find 'gpgv' to verify the
> > > > signatures. This is installed as 'gpgv2' in the gnupg recipe.
> > > > Therefore I've used update-alternatives to create the appropriate
> > > > link.
> > > > 
> > > 
> > > I've re-thought this already. Is update-alternatives the right
> > > thing to use here? Maybe not as there isn't anything else that
> > > provides gpgv and gnupg_1.* and gnupg_2.* probably can't co-exist
> > > on the same install. I could just add a line to do_install_append()
> > > to create the gpgv link manually, similar to how the link for gpg
> > > is already created. Please let me know which is the better solution
> > > here.
> > > 
> > > I also noticed that gnupg_1.4.7.bb splits gpgv into a separate
> > > package but gnupg_2.0.19 doesn't. I could write a patch to modify
> > > one of these to match the other if desired?
> > 
> > I glanced at this earlier and wondered what the alternative provider
> > was. If we have no alternative, a symlink is fine.
> > 
> > I'm open to separate packaging of the utilities if its useful and they
> > can use used one without the other. If we'd generally need both, they
> > can exist in the same package fine.
> > 
> > Cheers,
> > 
> > Richard
> > 
> 
> I'll put a new patch together to add the symlink. Does this warrant
> incrementing PR?

In the old scheme of things this was needed but is no longer required
since we have the PR server and checksums for the tasks which change
when details like this change.

Cheers,

Richard




      reply	other threads:[~2013-03-25 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  0:55 Gnupg recipe fixes Paul Barker
2013-03-25  0:55 ` [PATCH 1/2] gnupg: Replace manual link with update-alternatives Paul Barker
2013-03-25  0:55 ` [PATCH 2/2] gnupg: Added update-alternatives entry for gpgv Paul Barker
2013-03-25 12:57 ` Gnupg recipe fixes Paul Barker
2013-03-25 13:25   ` Richard Purdie
2013-03-25 13:32     ` Paul Barker
2013-03-25 13:39       ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1364218796.3097.49.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@paulbarker.me.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox