Bug 3213 - If my bblayers.conf file gets out of sync, it should be updated without popping alerts or relaunching Hob
Summary: If my bblayers.conf file gets out of sync, it should be updated without poppi...
Status: VERIFIED FIXED
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.4 M4
Assignee: Cristiana Voicu
QA Contact:
URL:
Whiteboard:
Depends on: 2934
Blocks:
  Show dependency tree
 
Reported: 2012-10-03 14:03 UTC by Belen Barros Pena
Modified: 2013-02-22 13:47 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
bblayers-lconfversion-3.png (233.60 KB, image/png)
2013-02-19 15:02 UTC, Belen Barros Pena 		no flags Details
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 Belen Barros Pena 2012-10-03 14:03:04 UTC 
For some history on this issue, see 3082 and 3176
Comment 1 Cristiana Voicu 2013-01-31 13:08:03 UTC 
Now bblayers.conf is synchronized with Hob. So bblayers.conf file do not gets out of sync. See more in #2934.
Comment 2 Belen Barros Pena 2013-02-01 10:56:22 UTC 
Hi Cristiana,

This is still popping up an error message. Looking at the previous bugs, the idea of this one was to get Hob to update the bblayers.conf file transparently (no error messages shown, no need to restart Hob). 

Let me know if you have any questions.

Belen
Comment 4 Belen Barros Pena 2013-02-19 15:02:11 UTC 
Created attachment 1076 [details]
bblayers-lconfversion-3.png

I tested this on master (c7b23ab68aafc04d9830ef318015912e5d4f0672), and it works beautifully if you change the LCONF_VERSION value to '5' or '4'. But when you change it to 3 or below, you get an error message (see attached file bblayers-lconfversion-3.png).

Is this intended?
Comment 5 Cristiana Voicu 2013-02-22 13:00:45 UTC 
Hi Belen,

When bug #3082 was implemented, they have decided to implement it only for version 4 and 5. Version 3 is very old, so this case is almost impossible. So this is intended.
Cristiana

(In reply to comment #4)
> Created attachment 1076 [details]
> bblayers-lconfversion-3.png
> 
> I tested this on master (c7b23ab68aafc04d9830ef318015912e5d4f0672), and it
> works beautifully if you change the LCONF_VERSION value to '5' or '4'. But
> when you change it to 3 or below, you get an error message (see attached
> file bblayers-lconfversion-3.png).
> 
> Is this intended?
Comment 6 Belen Barros Pena 2013-02-22 13:47:26 UTC 
In that case, verified fixed on c7b23ab68aafc04d9830ef318015912e5d4f0672

(In reply to comment #5)
> Hi Belen,
> 
> When bug #3082 was implemented, they have decided to implement it only for
> version 4 and 5. Version 3 is very old, so this case is almost impossible.
> So this is intended.
> Cristiana
> 
> (In reply to comment #4)
> > Created attachment 1076 [details]
> > bblayers-lconfversion-3.png
> > 
> > I tested this on master (c7b23ab68aafc04d9830ef318015912e5d4f0672), and it
> > works beautifully if you change the LCONF_VERSION value to '5' or '4'. But
> > when you change it to 3 or below, you get an error message (see attached
> > file bblayers-lconfversion-3.png).
> > 
> > Is this intended?