From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 63BC47213F for ; Fri, 2 Jan 2015 09:16:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t029G2io013042; Fri, 2 Jan 2015 09:16:02 GMT Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id bqgbNqiCLjYg; Fri, 2 Jan 2015 09:16:02 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t029Fo41013029 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 2 Jan 2015 09:16:02 GMT Message-ID: <1420190187.25779.15.camel@linuxfoundation.org> From: Richard Purdie To: Mike Looijmans Date: Fri, 02 Jan 2015 09:16:27 +0000 In-Reply-To: <54A65B5E.4030504@topic.nl> References: <54A2C3B2.9010006@topic.nl> <20141230175915.GB18678@crash.betafive.co.uk> <54A44ADC.3010000@topic.nl> <54A65B5E.4030504@topic.nl> X-Mailer: Evolution 3.12.7-0ubuntu1 Mime-Version: 1.0 Cc: openembedded-core@lists.openembedded.org Subject: Re: How do I change the "Architecture" of a package? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2015 09:16:44 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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