Re: [PATCH v3] meta: drop debian stretch support

[Baurzhan Ismagulov <ibr@radix50.net>]

On Mon, Jan 02, 2023 at 02:06:08PM +0100, Jan Kiszka wrote:
> On 02.01.23 13:54, Moessbauer, Felix (T CED INW-CN) wrote:
> > On Mon, 2023-01-02 at 12:51 +0000, Moessbauer, Felix wrote:
> >> On Mon, 2023-01-02 at 12:01 +0100, Jan Kiszka wrote:
> >>> On 27.12.22 07:35, Anton Mikanovich wrote:
> >>>> Debian Stretch state was moved to EOL since July 2020, so drop
> >>>> it.
> >>>
> >>> This cleanup is requiring an entry in RECIPE-API-CHANGELOG.md, see
> >>> https://github.com/siemens/meta-coral/blob/66a85fc4958524526d4a5e2eda0588de2a5f46f9/recipes-devtools/bazel-bootstrap/bazel-bootstrap_4.1.0%2Bds-1.bb#L14
> >>> and https://github.com/siemens/meta-iot2050/pull/396.
> >>
> >> Yes, we definitely need that API changelog entry. We have the
> >> following
> >> pattern in many recipes:
> >>
> >> GBP_EXTRA_OPTIONS = "--git-no-pristine-tar --git-upstream-
> >> branch=master"
> >>
> >> This now has to become:
> >> GBP_EXTRA_OPTIONS = "--no-pristine-tar --upstream-branch=master"
> > 
> > ... and changing this breaks backwards compatibility. This is
> > especially problematic for layers that also have to support older
> > versions of ISAR. At least, there is no release in-between v0.9 and
> > next, so we could argue that breaking things is OK.
> > 
> > An alternative would be to simply replace the --git-<opt> with --<opt>
> > on the fly using bitbake magic.
> 
> We could do that for existing GBP_EXTRA_OPTIONS and introduce a new
> variable that targets the actually used GBP sub-command:
> GBP_EXPORT_ORIG_EXTRA_OPTIONS.

Thanks for the info, we'll check the reported issues.

With kind regards,
Baurzhan