Bug 1127

Summary: Improve the error reporting when SkipPackage error is raised
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Scott Garman <scott.a.garman>
Component: meta-yoctoAssignee: Scott Garman <scott.a.garman>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: bluelightning, poky.bs.watcher, poky.watcher, richard.purdie, sgw, song.liu
Version: 1.0   
Target Milestone: 1.2 M3   
Hardware: x86   
OS: Multiple   
Whiteboard: (P1)(Done)
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Bug Depends on:    
Bug Blocks: 1543    

Description Scott Garman 2011-05-31 14:22:31 UTC
Mark Gross reported that trying to build grub on his 64-bit host failed, and the way the error was conveyed was not useful. 

This bug will track how to improve this error reporting situation.
Comment 1 Scott Garman 2011-05-31 15:24:37 UTC
Note: I've currently got an email inquiry in to Mark to get more details about this issue.
Comment 2 Paul Eggleton 2011-06-01 02:06:30 UTC
Scott, as discussed earlier I'm looking into this already; at least at the collection end so that we can get access to the reason for the package being skipped. I'm happy to leave the reporting end for you to work on if you'd prefer.
Comment 3 Scott Garman 2011-06-06 11:14:25 UTC
I confirmed with Mark that he would like to see what recipes get skipped due to SkipPackage exceptions:

"I blew a bunch of time trying to build qemu64 minimal target before I
found that you need the meta-intel layer such that grub 2 would be
provided.  Recipes-bsp has grub 0.97 but, it raises a SkipPackage
exception if the target is not 32 bit."

"bitbake -DDD grub would report NoProvider: grub  Yet show the
grub_0.97.bb was indeed getting processed."
Comment 4 Scott Garman 2011-06-09 07:53:50 UTC
Moving this to M3 because I see little chance of me fixing this *and* bug #542 in this milestone. Richard agreed that bug #542 was the more important one to fix for now.
Comment 5 Paul Eggleton 2011-07-28 08:31:24 UTC
So we now print out the reason a package has been skipped if a NoProvider error occurs. Is this enough to mark this as fixed?
Comment 6 Richard Purdie 2012-01-15 02:01:35 UTC
I think the various changes mean this one is resolved now.