[OE-core] [PATCH 04/15] file: replace obsolete automake macros with working ones

[Marko Lindqvist]

On 4 January 2013 20:23, Marko Lindqvist <cazfi74 at gmail.com> wrote:
> On 4 January 2013 20:08, Saul Wold <sgw at linux.intel.com> wrote:
>> On 01/03/2013 12:36 PM, Marko Lindqvist wrote:
>>>
>>> Add obsolete-automake-macros.patch that replaces automake macros
>>> no longer supported by automake-1.13 with modern constructs.
>>>
>>> Signed-off-by: Marko Lindqvist <cazfi74 at gmail.com>
>>> ---
>>>   .../file/file/obsolete_automake_macros.patch            |   15
>>> +++++++++++++++
>>>   meta/recipes-devtools/file/file_5.11.bb                 |    3 ++-
>>>   2 files changed, 17 insertions(+), 1 deletion(-)
>>>   create mode 100644
>>> meta/recipes-devtools/file/file/obsolete_automake_macros.patch
>>>
>>> diff --git
>>> a/meta/recipes-devtools/file/file/obsolete_automake_macros.patch
>>> b/meta/recipes-devtools/file/file/obsolete_automake_macros.patch
>>> new file mode 100644
>>> index 0000000..61ee062
>>> --- /dev/null
>>> +++ b/meta/recipes-devtools/file/file/obsolete_automake_macros.patch
>>> @@ -0,0 +1,15 @@
>>> +Upstream-status: Not sent
>>> +
>>
>> What does "Not sent" mean here?  Is it Pending? You plan to submit it?
>
>  It meant that I'm about to send it. I sent all the other such patches
> to upstreams (and updated Upstream-Statuses) as a last thing before I
> sent patch series to oe. But with "file" I noticed that they had
> released new version just while I were working. So I left it to wait
> for me to check if patch is still needed upstream. It isn't - simply
> updating to new upstream version could be solution for oe. I'm only a
> bit worried about release announcement wording that release with such
> big internal changes is for the adventurous - others should stick to
> previous release.

 Checking "file" mailing list now a couple of days after the release
it seems the warning was in order - many reggressions reported. So I
guess we stick to patching old 5.11 version.


 - ML