Bug 10700 - buildtools + deb packaging: Package nativesdk-buildtools-perl-dummy not found
Summary: buildtools + deb packaging: Package nativesdk-buildtools-perl-dummy not found
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.2
Hardware: x86 x86_64
: Medium+ normal
Target Milestone: 2.3 M3
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-11-22 09:38 UTC by Michel D'HOOGE
Modified: 2017-02-02 12:33 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
git diff meta/classes/package_deb.bbclass (909 bytes, patch)
2016-11-22 09:38 UTC, Michel D'HOOGE 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michel D'HOOGE 2016-11-22 09:38:58 UTC 
Created attachment 3543 [details]
git diff meta/classes/package_deb.bbclass

This bug report follows a discussion with Paul Eggleton on the Yocto mailing list.
https://lists.yoctoproject.org/pipermail/yocto/2016-November/033065.html

The problem is that the ARCH value of nativesdk-buildtools-perl-dummy is "allarch" (both in the name of the produced .deb files and in the Packages corresponding summary file). This should be only "all".

The patch in attachment corrects the problem on my side.

Note that Paul was concerned that maybe the dummy package would be discarded in favor of "real" perl packages.
From what I see in x86_64-buildtools-nativesdk-standalone-2.2.host.manifest, this isn't the case. Only the following packages have perl in their names.
  nativesdk-buildtools-perl-dummy buildtools-dummy-nativesdk 1.0-r2
  nativesdk-git-perltools x86-64-nativesdk 2.9.3-r0
Comment 1 Ross Burton 2017-01-26 12:44:25 UTC 
That solution isn't very general and will break if another package tries the same trick.  Patch on the list for a different fix.
Comment 2 Ross Burton 2017-02-02 12:33:30 UTC 
Fixed in oe-core 58a5771f20f7851816b5f39df0ada8f16438065c.