On Mon, Sep 6, 2021 at 11:41 PM Yu, Mingli <[email protected]> wrote:
>
>
>
> On 9/7/21 11:05 AM, Bruce Ashfield wrote:
> > [Please note: This e-mail is from an EXTERNAL e-mail address]
> >
> > On Mon, Sep 6, 2021 at 10:35 PM Yu, Mingli <[email protected]> wrote:
> >>
> >>
> >>
> >> On 9/6/21 10:08 PM, Bruce Ashfield wrote:
> >>> [Please note: This e-mail is from an EXTERNAL e-mail address]
> >>>
> >>> On Mon, Sep 6, 2021 at 9:46 AM Bruce Ashfield <[email protected]> 
> >>> wrote:
> >>>>
> >>>> I also already have this version bump queued locally.
> >>>
> >>> Actually cancel that. I have more -dev versions under test (I got my
> >>> uprev's confused for a moment).
> >>>
> >>> But we don't want this SRCREV change. I put it to the tip of the
> >>> release branch on purpose, this rewinds the SRCREV, and it isn't
> >>> something I'd merge.
> >>>
> >>> But the packageconfig change can be valid, and is something I'd take.
> >>
> >> Okay, I will send the packageconfig part then. BTW, why is there dev
> >> version, I think the latest release version should satisfy most of our
> >> needs.
> >
> > In this case, it is just a commit that bumps the version in
> > preparation for more changes (for 3.3.2), if you look at the
> > historical SRCREV bumps, I always take those changes.  There's no
> > reason to exclude them, since they are part of the release development
> > cycle. 3.3.2 will be out before the next release, and by taking those
> > commits, it shows the intention to track the tip for anything we may
> > need.
>
> If so, could we put two recipes here? one is for dev version such as
> podman-dev.bb and one such as podman_git.bb to track the latest release?
>

There's no value in doing that. There aren't specific "more stable" or
"development" releases. That simply doubles maintenance and splits our
testing.

By the time meta-virt 'releases' against honister, we'll be at the
next dot release.

Bruce

> Thanks,
>
> >
> > Bruce
> >
> >>
> >> Thanks,
> >>
> >>>
> >>> Bruce
> >>>
> >>>>
> >>>>
> >>>> On Mon, Sep 6, 2021 at 4:09 AM Yu, Mingli <[email protected]> 
> >>>> wrote:
> >>>>>
> >>>>> From: Mingli Yu <[email protected]>
> >>>>>
> >>>>> Remove the unvalid keys to silence the below warning:
> >>>>>    # podman --version
> >>>>>    WARN[0000] Failed to decode the keys 
> >>>>> ["storage.options.override_kernel_check" 
> >>>>> "storage.options.overlay.ostree_repo"] from 
> >>>>> "/etc/containers/storage.conf"
> >>>>>    podman version 3.3.1
> >>>>>
> >>>>> Signed-off-by: Mingli Yu <[email protected]>
> >>>>> ---
> >>>>>    recipes-containers/skopeo/files/storage.conf | 6 +++---
> >>>>>    recipes-containers/skopeo/skopeo_git.bb      | 2 +-
> >>>>>    2 files changed, 4 insertions(+), 4 deletions(-)
> >>>>>
> >>>>> diff --git a/recipes-containers/skopeo/files/storage.conf 
> >>>>> b/recipes-containers/skopeo/files/storage.conf
> >>>>> index 818cfe8..c0d512f 100644
> >>>>> --- a/recipes-containers/skopeo/files/storage.conf
> >>>>> +++ b/recipes-containers/skopeo/files/storage.conf
> >>>>> @@ -30,7 +30,7 @@ size = ""
> >>>>>    #mount_program = "/usr/bin/fuse-overlayfs"
> >>>>>
> >>>>>    # OverrideKernelCheck tells the driver to ignore kernel checks based 
> >>>>> on kernel version
> >>>>> -override_kernel_check = "true"
> >>>>> +#override_kernel_check = "true"
> >>>>
> >>>> But there's no reason to drop this.
> >>>>
> >>>>>
> >>>>>    # mountopt specifies comma separated list of extra mount options
> >>>>>    mountopt = "nodev"
> >>>>> @@ -126,8 +126,8 @@ mountopt = "nodev"
> >>>>>    # xfs_nospace_max_retries = "0"
> >>>>>
> >>>>>    # If specified, use OSTree to deduplicate files with the overlay 
> >>>>> backend
> >>>>> -ostree_repo = ""
> >>>>> +#ostree_repo = ""
> >>>>>
> >>>>>    # Set to skip a PRIVATE bind mount on the storage home directory.  
> >>>>> Only supported by
> >>>>>    # certain container storage drivers
> >>>>> -skip_mount_home = "false"
> >>>>> +#skip_mount_home = "false"
> >>>>
> >>>> or any of these .. the skopeo configuration serves many different use
> >>>> cases, if these are causing warnings in your setup, you need to carry
> >>>> your own storage.conf
> >>>>
> >>>> Bruce
> >>>>
> >>>>> diff --git a/recipes-containers/skopeo/skopeo_git.bb 
> >>>>> b/recipes-containers/skopeo/skopeo_git.bb
> >>>>> index 39ee8ca..adb7de1 100644
> >>>>> --- a/recipes-containers/skopeo/skopeo_git.bb
> >>>>> +++ b/recipes-containers/skopeo/skopeo_git.bb
> >>>>> @@ -27,7 +27,7 @@ SRC_URI = " \
> >>>>>        file://registries.conf \
> >>>>>    "
> >>>>>
> >>>>> -SRCREV = "01e51ce610e3cfe1230a10af982e962c4ad1c990"
> >>>>> +SRCREV = "130f32f047b7bf9b1fb4f95c4c5b1da6255e4829"
> >>>>>    PV = "v1.4.1+git${SRCPV}"
> >>>>>    GO_IMPORT = "import"
> >>>>>
> >>>>> --
> >>>>> 2.17.1
> >>>>>
> >>>>>
> >>>>> 
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> - Thou shalt not follow the NULL pointer, for chaos and madness await
> >>>> thee at its end
> >>>> - "Use the force Harry" - Gandalf, Star Trek II
> >>>
> >>>
> >>>
> >>> --
> >>> - Thou shalt not follow the NULL pointer, for chaos and madness await
> >>> thee at its end
> >>> - "Use the force Harry" - Gandalf, Star Trek II
> >>>
> >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6753): 
https://lists.yoctoproject.org/g/meta-virtualization/message/6753
Mute This Topic: https://lists.yoctoproject.org/mt/85407706/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to