Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
+-- [ http://bugs.openembedded.net/show_bug.cgi?id=5133#c4 ]
|
| I think the proper fix for this will be for bitbake to error out.
| --force-defaults will just mask the problem. We need to be made aware of the
| underlying problem in the recipes and fix them.
|
+--
I guess what we need from opkg is a non-interactive mode. If turned on, opkg
should
fail rather than ask questions in those cases. This would make do_rootfs in OE
fail
as well instead of hanging forever (consuming 100% CPU, btw).
Original comment by rolf.leg...@gmail.com
on 23 Jun 2009 at 7:28
Trunk now installs new conflicting config files with a -opkg postfix and
informs the user of this action.
This prevents hanging at a prompt, but doesn't provide bitbake/oe users with
any easy mechanism to determine that recipes
need to be fixed. Perhaps a new option e.g. --maintainer-checks should error
out in cases like these?
Original comment by graham.g...@gmail.com
on 21 Dec 2009 at 12:38
I'm going to close this bug. The initial hanging problem has been resolved and
OpenEmbedded can use its log_check facility to find conflicting conf files by
looking for the following pattern:
Collected errors:
* resolve_conffiles: Existing conffile /etc/foo is different from the conffile in the new package. The new conffile will be placed at /etc/foo-opkg
Original comment by graham.g...@gmail.com
on 8 Jun 2010 at 1:55
Original issue reported on code.google.com by
angus.ai...@gmail.com
on 31 Mar 2009 at 5:47