From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp09.online.nl (smtp09.online.nl [194.134.42.54]) by mail.openembedded.org (Postfix) with ESMTP id 5EE2C7277A for ; Fri, 2 Jan 2015 08:48:31 +0000 (UTC) Received: from smtp09.online.nl (localhost [127.0.0.1]) by smtp09.online.nl (Postfix) with ESMTP id 9462E1E1C0 for ; Fri, 2 Jan 2015 09:48:30 +0100 (CET) Received: from [192.168.1.4] (s55969068.adsl.online.nl [85.150.144.104]) by smtp09.online.nl (Postfix) with ESMTP for ; Fri, 2 Jan 2015 09:48:30 +0100 (CET) Message-ID: <54A65B5E.4030504@topic.nl> Date: Fri, 02 Jan 2015 09:48:30 +0100 From: Mike Looijmans Organization: Topic User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: openembedded-core@lists.openembedded.org References: <54A2C3B2.9010006@topic.nl> <20141230175915.GB18678@crash.betafive.co.uk> <54A44ADC.3010000@topic.nl> In-Reply-To: <54A44ADC.3010000@topic.nl> X-Online-Scanned: by Cloudmark authority (on smtp09.online.nl) 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 08:48:34 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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. -- Mike Looijmans