Warnings from building at HEAD

Warnings from building at HEAD

[Patrick Venture]

I'm seeing these warnings, is anybody else?  (Building quanta-q71l as
of a few minutes ago).

WARNING: libgpg-error-native-1.27-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to
incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
patching file src/Makefile.am
Hunk #1 succeeded at 61 with fuzz 2 (offset -3 lines).
patching file src/syscfg/lock-obj-pub.ppc64le-unknown-linux-gnu.h

Now at patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
WARNING: phosphor-ipmi-host-1.0-r1 do_unpack: noskeleton in
MACHINE_FEATURES. Remove mapper-wait on host settings.
WARNING: libgpg-error-1.27-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to
incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
patching file src/Makefile.am
Hunk #1 succeeded at 61 with fuzz 2 (offset -3 lines).
patching file src/syscfg/lock-obj-pub.ppc64le-unknown-linux-gnu.h

Now at patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
Using an insecure image signing key!
WARNING: python-pygobject-2.28.7-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to
incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch obsolete_automake_macros.patch
patching file configure.ac
Hunk #2 succeeded at 82 with fuzz 1.

Now at patch obsolete_automake_macros.patch

Re: Warnings from building at HEAD

[Brad Bishop]

> On Aug 23, 2018, at 5:19 PM, Patrick Venture <venture@google.com> wrote:
> 
> I'm seeing these warnings, is anybody else?  (Building quanta-q71l as
> of a few minutes ago).
> 
> WARNING: libgpg-error-native-1.27-r0 do_patch:
> Some of the context lines in patches were ignored. This can lead to
> incorrectly applied patches.
> The context lines in the patches can be updated with devtool:
> 
>    devtool modify <recipe>
>    devtool finish --force-patch-refresh <recipe> <layer_path>
> 
> Then the updated patches and the source tree (in devtool's workspace)
> should be reviewed to make sure the patches apply in the correct place
> and don't introduce duplicate lines (which can, and does happen
> when some of the context is ignored). Further information:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
> Details:
> Applying patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> patching file src/Makefile.am
> Hunk #1 succeeded at 61 with fuzz 2 (offset -3 lines).
> patching file src/syscfg/lock-obj-pub.ppc64le-unknown-linux-gnu.h
> 
> Now at patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> WARNING: phosphor-ipmi-host-1.0-r1 do_unpack: noskeleton in
> MACHINE_FEATURES. Remove mapper-wait on host settings.
> WARNING: libgpg-error-1.27-r0 do_patch:
> Some of the context lines in patches were ignored. This can lead to
> incorrectly applied patches.
> The context lines in the patches can be updated with devtool:
> 
>    devtool modify <recipe>
>    devtool finish --force-patch-refresh <recipe> <layer_path>
> 
> Then the updated patches and the source tree (in devtool's workspace)
> should be reviewed to make sure the patches apply in the correct place
> and don't introduce duplicate lines (which can, and does happen
> when some of the context is ignored). Further information:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
> Details:
> Applying patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> patching file src/Makefile.am
> Hunk #1 succeeded at 61 with fuzz 2 (offset -3 lines).
> patching file src/syscfg/lock-obj-pub.ppc64le-unknown-linux-gnu.h
> 
> Now at patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> Using an insecure image signing key!
> WARNING: python-pygobject-2.28.7-r0 do_patch:
> Some of the context lines in patches were ignored. This can lead to
> incorrectly applied patches.
> The context lines in the patches can be updated with devtool:
> 
>    devtool modify <recipe>
>    devtool finish --force-patch-refresh <recipe> <layer_path>
> 
> Then the updated patches and the source tree (in devtool's workspace)
> should be reviewed to make sure the patches apply in the correct place
> and don't introduce duplicate lines (which can, and does happen
> when some of the context is ignored). Further information:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
> Details:
> Applying patch obsolete_automake_macros.patch
> patching file configure.ac
> Hunk #2 succeeded at 82 with fuzz 1.
> 
> Now at patch obsolete_automake_macros.patch

Hi Patrick

Yep, I’ve seen these.  In fact, it is my patch it is complaining about - it started
with the bump to Yocto 2.5.  I haven’t had a chance to fix it up.

-brad

Re: Warnings from building at HEAD

[Lei YU]

This warning message comes from `meta/lib/oe/patch.py`:

    def runcmd(args, dir = None):
        ...
        if " fuzz " in output:
            bb.warn("""...

It checks "fuzz" in the patch output, which means the patch is applied but
the context is different.
I would think it is OK, it is just a warning to tell that the patch is
out-of-date.

To fix this, we need to update each patch that triggers the warning, and the
patch itself may be out of openbmc's scope.

On Fri, Aug 24, 2018 at 10:02 AM Brad Bishop
<bradleyb@fuzziesquirrel.com> wrote:
>
>
> > On Aug 23, 2018, at 5:19 PM, Patrick Venture <venture@google.com> wrote:
> >
> > I'm seeing these warnings, is anybody else?  (Building quanta-q71l as
> > of a few minutes ago).
> >
> > WARNING: libgpg-error-native-1.27-r0 do_patch:
> > Some of the context lines in patches were ignored. This can lead to
> > incorrectly applied patches.
> > The context lines in the patches can be updated with devtool:
> >
> >    devtool modify <recipe>
> >    devtool finish --force-patch-refresh <recipe> <layer_path>
> >
> > Then the updated patches and the source tree (in devtool's workspace)
> > should be reviewed to make sure the patches apply in the correct place
> > and don't introduce duplicate lines (which can, and does happen
> > when some of the context is ignored). Further information:
> > http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
> > Details:
> > Applying patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> > patching file src/Makefile.am
> > Hunk #1 succeeded at 61 with fuzz 2 (offset -3 lines).
> > patching file src/syscfg/lock-obj-pub.ppc64le-unknown-linux-gnu.h
> >
> > Now at patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> > WARNING: phosphor-ipmi-host-1.0-r1 do_unpack: noskeleton in
> > MACHINE_FEATURES. Remove mapper-wait on host settings.
> > WARNING: libgpg-error-1.27-r0 do_patch:
> > Some of the context lines in patches were ignored. This can lead to
> > incorrectly applied patches.
> > The context lines in the patches can be updated with devtool:
> >
> >    devtool modify <recipe>
> >    devtool finish --force-patch-refresh <recipe> <layer_path>
> >
> > Then the updated patches and the source tree (in devtool's workspace)
> > should be reviewed to make sure the patches apply in the correct place
> > and don't introduce duplicate lines (which can, and does happen
> > when some of the context is ignored). Further information:
> > http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
> > Details:
> > Applying patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> > patching file src/Makefile.am
> > Hunk #1 succeeded at 61 with fuzz 2 (offset -3 lines).
> > patching file src/syscfg/lock-obj-pub.ppc64le-unknown-linux-gnu.h
> >
> > Now at patch 0001-syscfg-Add-ppc64le-cross-build-support.patch
> > Using an insecure image signing key!
> > WARNING: python-pygobject-2.28.7-r0 do_patch:
> > Some of the context lines in patches were ignored. This can lead to
> > incorrectly applied patches.
> > The context lines in the patches can be updated with devtool:
> >
> >    devtool modify <recipe>
> >    devtool finish --force-patch-refresh <recipe> <layer_path>
> >
> > Then the updated patches and the source tree (in devtool's workspace)
> > should be reviewed to make sure the patches apply in the correct place
> > and don't introduce duplicate lines (which can, and does happen
> > when some of the context is ignored). Further information:
> > http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
> > Details:
> > Applying patch obsolete_automake_macros.patch
> > patching file configure.ac
> > Hunk #2 succeeded at 82 with fuzz 1.
> >
> > Now at patch obsolete_automake_macros.patch
>
> Hi Patrick
>
> Yep, I’ve seen these.  In fact, it is my patch it is complaining about - it started
> with the bump to Yocto 2.5.  I haven’t had a chance to fix it up.
>
> -brad