| Summary: | bitbake -u depexp gives warnings | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Stoicescu Cornel <corneliux.stoicescu> | ||||
| Component: | bitbake | Assignee: | Ross Burton <ross.burton> | ||||
| Status: | VERIFIED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | gary, poky.bs.watcher, poky.watcher, sgw | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Stoicescu Cornel
2013-05-09 14:19:18 UTC
This is an error in your host (native) pygobject library and does not happen on all development hosts. What is your development host? The problem does not appear on Fedora (13,16) nor Ubuntu (12.04, 12.10) Here is my environment: [cornel@NODE3 build]$ uname -a Linux NODE3 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7 17:29:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Ross, I'm assuming this is the host pygobject and there is nothing we can do about this? If so, its probably a CANTFIX (WONTFIX) ? Yes, this is host pygobject (the gio bit) so there's nothing we can do. If you know where to push the changes, I have a patch that fixes this (attached) Created attachment 1224 [details]
Patch to clean up GTK registration errors
You were beat to it last year: https://git.gnome.org/browse/pygobject/commit/gio/gio-types.defs?h=pygobject-2-28&id=42d01f060c5d764baa881d13c103d68897163a49 Sadly still not in a tarball release yet, someone should prod them to make a finaly 2.28.x release with these fixes in. Latest Fedora version (Fedora 19) has "gnome-session 3.8.4" that does not reproduce this bug. |