All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: How do I change the "Architecture" of a package?
Date: Fri, 02 Jan 2015 09:16:27 +0000	[thread overview]
Message-ID: <1420190187.25779.15.camel@linuxfoundation.org> (raw)
In-Reply-To: <54A65B5E.4030504@topic.nl>

On Fri, 2015-01-02 at 09:48 +0100, Mike Looijmans wrote:
> On 12/31/2014 08:13 PM, Mike Looijmans wrote:
> > On 30-12-2014 18:59, Paul Barker wrote:
> >> On Tue, Dec 30, 2014 at 04:24:34PM +0100, Mike Looijmans wrote:
> >>> What if the architecture of a package was accidentally left at its
> >>> default, but it should have been "all" for example?
> >>>
> >>> Just putting "inherit allarch" or simply PACKAGE_ARCH="all" into the
> >>> recipe is not enough. You get stuck with a "more specific" older
> >>> version, so that no device wants to upgrade to the newer version
> >>> that's "all" architecture compatible.
> >>>
> >>
> >> What package manager are you using on the device? If you're using opkg
> >> it should
> >> prioritise by version not arch unless the command line option
> >> '--prefer-arch-to-version' is passed. If you're using opkg and it's
> >> not doing
> >> that, let me know and I'll look into it when I get chance to.
> >
> > It's opkg.
> >
> > But on closer inspection I noticed that the "git" version is also
> > mysteriously reset to 0, so that the package also gets a lower version
> > number instead of a higher one. Seems to be the PR server borking things
> > again or so, I'll have to investigate that next year...
> 
> Weird, something in OE killed "gitpkgv".
> 
> in the recipe, I have this:
> 
> inherit gitpkgv
> PV = "2.0+git${SRCPV}"
> PKGV = "2.0+git${GITPKGV}"
> 
> 
> $ bitbake enigma2-plugin-extensions-autobackup -e | grep PKGV
> 
> delivers correct information:
> 
> PKGV="2.0+git68+2e7a1db"
> GITPKGVTAG="0.0-68-g2e7a1db"
> GITPKGV="68+2e7a1db"
> 
> 
> But after building and deploying the package, the version number will 
> eventually end up being this one:
> 
> 2.0+git5+2e7a1db509-r0.2
> 
> 
> What in OE is replacing a perfectly good PKGV tag with something 
> completely different bearing no relation whatsoever? Even the number of 
> digits in the git tag differs from the one I put in the recipe!
> 
> Even if I put some random text into PKGV, it gets replaced.

Did something come from sstate?

Cheers,

Richard



  reply	other threads:[~2015-01-02  9:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 15:24 How do I change the "Architecture" of a package? Mike Looijmans
2014-12-30 17:59 ` Paul Barker
2014-12-31 19:13   ` Mike Looijmans
2015-01-02  8:48     ` Mike Looijmans
2015-01-02  9:16       ` Richard Purdie [this message]
2015-01-02  9:24         ` Mike Looijmans
2015-01-02  9:28           ` Mike Looijmans
2015-01-04 15:20         ` Bug: PR server changes the PKGV variable too Mike Looijmans
2015-01-05  9:27           ` Richard Purdie
2015-01-05  9:41             ` Mike Looijmans
2015-01-05 10:07               ` Richard Purdie
2015-01-05 10:36                 ` Mike Looijmans
2015-01-05 11:37                   ` Richard Purdie
2015-01-05 12:09                     ` Mike Looijmans
2015-01-05 16:03                       ` Mike Looijmans
2015-01-03 10:52     ` How do I change the "Architecture" of a package? Mike Looijmans

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=1420190187.25779.15.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.