All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Milan Shah <mshah@mvista.com>, yocto@yoctoproject.org
Cc: Paul Barker <pbarker@konsulko.com>, Armin Kuster <akuster@mvista.com>
Subject: Re: [error-report-web][PATCH] report-error.bbclass: Add layer and bitbake version info to error report
Date: Fri, 26 Mar 2021 10:51:41 +0000	[thread overview]
Message-ID: <7b5173bb8a6359a3c7597341c60ec2726d8f6108.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+=qD9NoNqBWv+ATf_tw-cc+Vz0xaDO6biCMFmx_M2Xq0LpA2A@mail.gmail.com>

On Fri, 2021-03-26 at 16:04 +0530, Milan Shah wrote:
> It seems like patches sent for error-report-web are not much important to the community as this patch has
> not been reviewed/commented on by anyone since 6th January 2021 (more than 2.5 months).
> 
> Still, I'm sending a reminder one last time for [YOCTO #9700].
> https://lists.yoctoproject.org/g/yocto/message/51891
> 
> Please review/comment on it so that things can move further.

Sorry, that isn't true, they are important and appreciated. We're 
just struggling to handle everything.

The challenge/problem has been that there are much older patches which
were half merged and broke things. People have rightly been complaining
about those issues and Khem for example has been carrying a patch for 3
years to work arond that problem. I did figure out a fix for that which
has now been merged.

We also needed to migrate the service from py2 to py3 and deal with a
set of patches that had been applied locally that we had been unaware of
until very recently but which complicate things. The people who wrote 
them are no longer around to help with that.

The original authors of this code are no longer around, the people who
stepped up to try and help also haven't had time so the support/review
has struggled. The service is in daily use however so it is important
and that is why I'm now trying to unravel and fix things.

I do want to get to your patch but you can appreciate that adding it 
directly on top of an already failing set of changes wouldn't be good
for anyone.

We are making progress in resolving the issues so I hope to get some
kind of better answer to you soon.

Cheers,

Richard



  reply	other threads:[~2021-03-26 10:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 13:38 [error-report-web][PATCH] report-error.bbclass: Add layer and bitbake version info to error report Milan Shah
2021-01-11 13:15 ` Milan Shah
2021-02-01  4:36   ` Milan Shah
2021-02-23  9:51     ` Milan Shah
2021-03-15 11:06       ` Milan Shah
2021-03-26 10:34         ` Milan Shah
2021-03-26 10:51           ` Richard Purdie [this message]
2021-03-26 11:45             ` Milan Shah
     [not found]             ` <166FE1E7B1DE5E9C.21604@lists.yoctoproject.org>
2021-07-09  5:21               ` [yocto] " Milan Shah
2021-07-09  8:33                 ` Richard Purdie
2021-07-09  8:37                   ` Milan Shah
2021-07-09  8:53                     ` Richard Purdie
2021-07-09  8:56                       ` Milan Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7b5173bb8a6359a3c7597341c60ec2726d8f6108.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster@mvista.com \
    --cc=mshah@mvista.com \
    --cc=pbarker@konsulko.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.