[m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Jeremy Puhlman]

Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
---
 meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
 1 file changed, 1 deletion(-)
 delete mode 100644 meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend

diff --git a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
deleted file mode 100644
index 7447c56..0000000
--- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-inherit autotools-brokensep
-- 
2.11.1

[m-c-s][PATCH 2/2] libvirt: Update bbappend to match latest version

[Jeremy Puhlman]

Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
---
 .../libvirt/{libvirt_1.%.bbappend => libvirt_4.%.bbappend}                | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename meta-openstack/recipes-extended/libvirt/{libvirt_1.%.bbappend => libvirt_4.%.bbappend} (100%)

diff --git a/meta-openstack/recipes-extended/libvirt/libvirt_1.%.bbappend b/meta-openstack/recipes-extended/libvirt/libvirt_4.%.bbappend
similarity index 100%
rename from meta-openstack/recipes-extended/libvirt/libvirt_1.%.bbappend
rename to meta-openstack/recipes-extended/libvirt/libvirt_4.%.bbappend
-- 
2.11.1

Re: [m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Bruce Ashfield]

Can we log why it is no longer necessary ? i.e. which version of the
package has fixed
the old clean -> rebuild problem.

Bruce

On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com> wrote:
> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
> ---
>  meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
>  1 file changed, 1 deletion(-)
>  delete mode 100644 meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>
> diff --git a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
> deleted file mode 100644
> index 7447c56..0000000
> --- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
> +++ /dev/null
> @@ -1 +0,0 @@
> -inherit autotools-brokensep
> --
> 2.11.1
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Jeremy A. Puhlman]

Going back through the log I didn't see any indication of the problem it 
was trying to solve. I assumed it was
a standard configure doesn't work with a split build. Currently it 
doesn't apply to master at all and I haven't
seen any actual issues. What where the specific steps to reproduce?

On 7/6/2018 7:33 PM, Bruce Ashfield wrote:
> Can we log why it is no longer necessary ? i.e. which version of the
> package has fixed
> the old clean -> rebuild problem.
>
> Bruce
>
> On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com> wrote:
>> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
>> ---
>>   meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
>>   1 file changed, 1 deletion(-)
>>   delete mode 100644 meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>
>> diff --git a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>> deleted file mode 100644
>> index 7447c56..0000000
>> --- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>> +++ /dev/null
>> @@ -1 +0,0 @@
>> -inherit autotools-brokensep
>> --
>> 2.11.1
>>
>> --
>> _______________________________________________
>> meta-virtualization mailing list
>> meta-virtualization@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>

-- 
Jeremy A. Puhlman
jpuhlman@mvista.com

Re: [m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Bruce Ashfield]

On Fri, Jul 6, 2018 at 10:50 PM, Jeremy A. Puhlman <jpuhlman@mvista.com> wrote:
> Going back through the log I didn't see any indication of the problem it was
> trying to solve. I assumed it was
> a standard configure doesn't work with a split build. Currently it doesn't
> apply to master at all and I haven't
> seen any actual issues. What where the specific steps to reproduce?

It would have been added when an incremental build was performed. i.e.
a build, an update and the rebuild triggered the error. They only
appear sporadically, so there's no set of steps to reproduce the issue
consistently.

Unless this is actually breaking something, I tend to just leave them
in place rather than break some nightly build that someone may be
doing ..

Bruce

>
>
> On 7/6/2018 7:33 PM, Bruce Ashfield wrote:
>>
>> Can we log why it is no longer necessary ? i.e. which version of the
>> package has fixed
>> the old clean -> rebuild problem.
>>
>> Bruce
>>
>> On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com>
>> wrote:
>>>
>>> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
>>> ---
>>>   meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
>>>   1 file changed, 1 deletion(-)
>>>   delete mode 100644
>>> meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>
>>> diff --git a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>> b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>> deleted file mode 100644
>>> index 7447c56..0000000
>>> --- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>> +++ /dev/null
>>> @@ -1 +0,0 @@
>>> -inherit autotools-brokensep
>>> --
>>> 2.11.1
>>>
>>> --
>>> _______________________________________________
>>> meta-virtualization mailing list
>>> meta-virtualization@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>>
>>
>>
>
> --
> Jeremy A. Puhlman
> jpuhlman@mvista.com
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Jeremy A. Puhlman]

On 7/6/2018 8:20 PM, Bruce Ashfield wrote:
> On Fri, Jul 6, 2018 at 10:50 PM, Jeremy A. Puhlman <jpuhlman@mvista.com> wrote:
>> Going back through the log I didn't see any indication of the problem it was
>> trying to solve. I assumed it was
>> a standard configure doesn't work with a split build. Currently it doesn't
>> apply to master at all and I haven't
>> seen any actual issues. What where the specific steps to reproduce?
> It would have been added when an incremental build was performed. i.e.
> a build, an update and the rebuild triggered the error. They only
> appear sporadically, so there's no set of steps to reproduce the issue
> consistently.
>
> Unless this is actually breaking something, I tend to just leave them
> in place rather than break some nightly build that someone may be
> doing ..

Fair enough. Then the append needs to be updated for the master version. 
You want me to send you a update to do that, or would
you like to handle it?


>
> Bruce
>
>>
>> On 7/6/2018 7:33 PM, Bruce Ashfield wrote:
>>> Can we log why it is no longer necessary ? i.e. which version of the
>>> package has fixed
>>> the old clean -> rebuild problem.
>>>
>>> Bruce
>>>
>>> On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com>
>>> wrote:
>>>> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
>>>> ---
>>>>    meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
>>>>    1 file changed, 1 deletion(-)
>>>>    delete mode 100644
>>>> meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>
>>>> diff --git a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>> b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>> deleted file mode 100644
>>>> index 7447c56..0000000
>>>> --- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>> +++ /dev/null
>>>> @@ -1 +0,0 @@
>>>> -inherit autotools-brokensep
>>>> --
>>>> 2.11.1
>>>>
>>>> --
>>>> _______________________________________________
>>>> meta-virtualization mailing list
>>>> meta-virtualization@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>>>
>>>
>> --
>> Jeremy A. Puhlman
>> jpuhlman@mvista.com
>>
>
>

-- 
Jeremy A. Puhlman
jpuhlman@mvista.com

Re: [m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Bruce Ashfield]

On Fri, Jul 6, 2018 at 11:31 PM, Jeremy A. Puhlman <jpuhlman@mvista.com> wrote:
>
>
> On 7/6/2018 8:20 PM, Bruce Ashfield wrote:
>>
>> On Fri, Jul 6, 2018 at 10:50 PM, Jeremy A. Puhlman <jpuhlman@mvista.com>
>> wrote:
>>>
>>> Going back through the log I didn't see any indication of the problem it
>>> was
>>> trying to solve. I assumed it was
>>> a standard configure doesn't work with a split build. Currently it
>>> doesn't
>>> apply to master at all and I haven't
>>> seen any actual issues. What where the specific steps to reproduce?
>>
>> It would have been added when an incremental build was performed. i.e.
>> a build, an update and the rebuild triggered the error. They only
>> appear sporadically, so there's no set of steps to reproduce the issue
>> consistently.
>>
>> Unless this is actually breaking something, I tend to just leave them
>> in place rather than break some nightly build that someone may be
>> doing ..
>
>
> Fair enough. Then the append needs to be updated for the master version. You
> want me to send you a update to do that, or would
> you like to handle it?

Either works. Probably easier if I just do it, so I'll add your
reported-by tag to the update of the bbappend.

Bruce

>
>
>
>>
>> Bruce
>>
>>>
>>> On 7/6/2018 7:33 PM, Bruce Ashfield wrote:
>>>>
>>>> Can we log why it is no longer necessary ? i.e. which version of the
>>>> package has fixed
>>>> the old clean -> rebuild problem.
>>>>
>>>> Bruce
>>>>
>>>> On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com>
>>>> wrote:
>>>>>
>>>>> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
>>>>> ---
>>>>>    meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
>>>>>    1 file changed, 1 deletion(-)
>>>>>    delete mode 100644
>>>>> meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>
>>>>> diff --git
>>>>> a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>> b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>> deleted file mode 100644
>>>>> index 7447c56..0000000
>>>>> --- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>> +++ /dev/null
>>>>> @@ -1 +0,0 @@
>>>>> -inherit autotools-brokensep
>>>>> --
>>>>> 2.11.1
>>>>>
>>>>> --
>>>>> _______________________________________________
>>>>> meta-virtualization mailing list
>>>>> meta-virtualization@yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>>>>
>>>>
>>>>
>>> --
>>> Jeremy A. Puhlman
>>> jpuhlman@mvista.com
>>>
>>
>>
>
> --
> Jeremy A. Puhlman
> jpuhlman@mvista.com
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Mark Asselstine]

On Sat, Jul 7, 2018 at 12:31 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Fri, Jul 6, 2018 at 11:31 PM, Jeremy A. Puhlman <jpuhlman@mvista.com> wrote:
>>
>>
>> On 7/6/2018 8:20 PM, Bruce Ashfield wrote:
>>>
>>> On Fri, Jul 6, 2018 at 10:50 PM, Jeremy A. Puhlman <jpuhlman@mvista.com>
>>> wrote:
>>>>
>>>> Going back through the log I didn't see any indication of the problem it
>>>> was
>>>> trying to solve. I assumed it was
>>>> a standard configure doesn't work with a split build. Currently it
>>>> doesn't
>>>> apply to master at all and I haven't
>>>> seen any actual issues. What where the specific steps to reproduce?
>>>
>>> It would have been added when an incremental build was performed. i.e.
>>> a build, an update and the rebuild triggered the error. They only
>>> appear sporadically, so there's no set of steps to reproduce the issue
>>> consistently.
>>>
>>> Unless this is actually breaking something, I tend to just leave them
>>> in place rather than break some nightly build that someone may be
>>> doing ..
>>
>>
>> Fair enough. Then the append needs to be updated for the master version. You
>> want me to send you a update to do that, or would
>> you like to handle it?
>
> Either works. Probably easier if I just do it, so I'll add your
> reported-by tag to the update of the bbappend.
>
> Bruce

This dates back to the src/build split
http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/commit/?id=b288eb5c2e5961caf57645b246143d3e2e596c55

No clues in the project's commits to indicate an explicit fix being
applied. I am 1/2 tempted to revert back to 0.6.0 and see what the
error was to be able to properly drop this.

Mark

>
>>
>>
>>
>>>
>>> Bruce
>>>
>>>>
>>>> On 7/6/2018 7:33 PM, Bruce Ashfield wrote:
>>>>>
>>>>> Can we log why it is no longer necessary ? i.e. which version of the
>>>>> package has fixed
>>>>> the old clean -> rebuild problem.
>>>>>
>>>>> Bruce
>>>>>
>>>>> On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com>
>>>>> wrote:
>>>>>>
>>>>>> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
>>>>>> ---
>>>>>>    meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
>>>>>>    1 file changed, 1 deletion(-)
>>>>>>    delete mode 100644
>>>>>> meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>>
>>>>>> diff --git
>>>>>> a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>> b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>> deleted file mode 100644
>>>>>> index 7447c56..0000000
>>>>>> --- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>> +++ /dev/null
>>>>>> @@ -1 +0,0 @@
>>>>>> -inherit autotools-brokensep
>>>>>> --
>>>>>> 2.11.1
>>>>>>
>>>>>> --
>>>>>> _______________________________________________
>>>>>> meta-virtualization mailing list
>>>>>> meta-virtualization@yoctoproject.org
>>>>>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Jeremy A. Puhlman
>>>> jpuhlman@mvista.com
>>>>
>>>
>>>
>>
>> --
>> Jeremy A. Puhlman
>> jpuhlman@mvista.com
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization

Re: [m-c-s][PATCH 2/2] libvirt: Update bbappend to match latest version

[Bruce Ashfield]

merged

Bruce

On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com> wrote:
> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
> ---
>  .../libvirt/{libvirt_1.%.bbappend => libvirt_4.%.bbappend}                | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  rename meta-openstack/recipes-extended/libvirt/{libvirt_1.%.bbappend => libvirt_4.%.bbappend} (100%)
>
> diff --git a/meta-openstack/recipes-extended/libvirt/libvirt_1.%.bbappend b/meta-openstack/recipes-extended/libvirt/libvirt_4.%.bbappend
> similarity index 100%
> rename from meta-openstack/recipes-extended/libvirt/libvirt_1.%.bbappend
> rename to meta-openstack/recipes-extended/libvirt/libvirt_4.%.bbappend
> --
> 2.11.1
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: [m-c-s][PATCH 1/2] libbsd: Remove dangling append that no longer is needed

[Bruce Ashfield]

I went ahead and did the rename of the bbappend. At some distant point
in the future
we can determine if it really was necessary :D

Bruce

On Sat, Jul 7, 2018 at 12:31 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Fri, Jul 6, 2018 at 11:31 PM, Jeremy A. Puhlman <jpuhlman@mvista.com> wrote:
>>
>>
>> On 7/6/2018 8:20 PM, Bruce Ashfield wrote:
>>>
>>> On Fri, Jul 6, 2018 at 10:50 PM, Jeremy A. Puhlman <jpuhlman@mvista.com>
>>> wrote:
>>>>
>>>> Going back through the log I didn't see any indication of the problem it
>>>> was
>>>> trying to solve. I assumed it was
>>>> a standard configure doesn't work with a split build. Currently it
>>>> doesn't
>>>> apply to master at all and I haven't
>>>> seen any actual issues. What where the specific steps to reproduce?
>>>
>>> It would have been added when an incremental build was performed. i.e.
>>> a build, an update and the rebuild triggered the error. They only
>>> appear sporadically, so there's no set of steps to reproduce the issue
>>> consistently.
>>>
>>> Unless this is actually breaking something, I tend to just leave them
>>> in place rather than break some nightly build that someone may be
>>> doing ..
>>
>>
>> Fair enough. Then the append needs to be updated for the master version. You
>> want me to send you a update to do that, or would
>> you like to handle it?
>
> Either works. Probably easier if I just do it, so I'll add your
> reported-by tag to the update of the bbappend.
>
> Bruce
>
>>
>>
>>
>>>
>>> Bruce
>>>
>>>>
>>>> On 7/6/2018 7:33 PM, Bruce Ashfield wrote:
>>>>>
>>>>> Can we log why it is no longer necessary ? i.e. which version of the
>>>>> package has fixed
>>>>> the old clean -> rebuild problem.
>>>>>
>>>>> Bruce
>>>>>
>>>>> On Fri, Jul 6, 2018 at 5:23 PM, Jeremy Puhlman <jpuhlman@mvista.com>
>>>>> wrote:
>>>>>>
>>>>>> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
>>>>>> ---
>>>>>>    meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend | 1 -
>>>>>>    1 file changed, 1 deletion(-)
>>>>>>    delete mode 100644
>>>>>> meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>>
>>>>>> diff --git
>>>>>> a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>> b/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>> deleted file mode 100644
>>>>>> index 7447c56..0000000
>>>>>> --- a/meta-openstack/recipes-support/libbsd/libbsd_0.8.%.bbappend
>>>>>> +++ /dev/null
>>>>>> @@ -1 +0,0 @@
>>>>>> -inherit autotools-brokensep
>>>>>> --
>>>>>> 2.11.1
>>>>>>
>>>>>> --
>>>>>> _______________________________________________
>>>>>> meta-virtualization mailing list
>>>>>> meta-virtualization@yoctoproject.org
>>>>>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Jeremy A. Puhlman
>>>> jpuhlman@mvista.com
>>>>
>>>
>>>
>>
>> --
>> Jeremy A. Puhlman
>> jpuhlman@mvista.com
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"