[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Intent to backport python-junitxml

On Mon, 4 Feb 2019 11:10:32 -0800
Jonathan Nieder <jrnieder@gmail.com> wrote:

> Hi,
> Neil Williams wrote:
> > An upstream bug report has identified that the version of
> > python3-junitxml in Stretch is lacking functionality which is
> > present in the version included in Buster.
> >
> > https://git.lavasoftware.org/lava/lava/issues/209
> >
> > This is causing the current release of lava-server to raise a HTTP
> > 500 error on certain API calls.  
> That sounds worth fixing in stretch as well.  Is it feasible to do?

Issue #209 relates to functionality which is not present in version
2016.12-3 in Stretch. The code simply doesn't exist in 2016.12 to use
python3-junitxml. So there is no need to change anything in Stretch on
the basis of issue #209 in LAVA.

> Or is the idea that this only affects newer versions of lava than the
> one in stretch?

The first LAVA version to use python3-junitxml is 2019.01, so the
intent is to provide the updated python3-junitxml in stretch-backports
to support a backport of lava-server 2019.01 to stretch-backports.


Neil Williams

Attachment: pgpd1TRfoRdNQ.pgp
Description: OpenPGP digital signature

Reply to: