All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Orling <ticotimo@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [layerindex-web][PATCH 0/6] Recipe Reporting System fixes
Date: Mon, 15 Jan 2024 10:03:11 -0800	[thread overview]
Message-ID: <cover.1705341467.git.tim.orling@konsulko.com> (raw)

This series fixes some syntax changes and other issues which have made
the Recipe Reporting System non-functional synce May 2020.

For now, the rrs/tools/rrs_distros.py script is commented out of the
rrs/tools/daily_run.sh since it requires changes in oe-core that may need
some discussion.

The other scripts which are part of rrs/tools/rrs_distros.py are now all
functional and have been live tested on layers.openembedded.org:
* rrs_maintainer_history.py
* rrs_upgrade_history.py
* rrs_upstream_history.py

The results can now be seen at https://layers.openembedded.org/rrs/

This series is applied on top of the previous "docker-fixes" series.

The following changes since commit 662ca9a4be52a21ed03e7421b51e5c1e1ef9afb1:

  docker-compose.yml: drop version '3' (2024-01-12 14:16:22 -0800)

are available in the Git repository at:

  https://github.com/moto-timo/layerindex-web rrs-fixes
  https://github.com/moto-timo/layerindex-web/tree/rrs-fixes

Tim Orling (6):
  rrs_maintainer_history: new override syntax
  rrs_maintainer_history: fix syntax
  rrs_upgrade_history: remap new srcrev fetcher API
  rrs_upstream_history: allow skip update_data
  rrs_upstream_history: fix get_recipe_pv_without_srcpv
  rrs_upstream_history: fix get_upstream_info

 rrs/tools/rrs_maintainer_history.py |  6 +++---
 rrs/tools/rrs_upgrade_history.py    |  1 +
 rrs/tools/rrs_upstream_history.py   | 30 ++++++++++++++++++++---------
 3 files changed, 25 insertions(+), 12 deletions(-)

-- 
2.34.1



             reply	other threads:[~2024-01-15 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 18:03 Tim Orling [this message]
2024-01-15 18:03 ` [layerindex-web][PATCH 1/6] rrs_maintainer_history: new override syntax Tim Orling
2024-01-15 18:03 ` [layerindex-web][PATCH 2/6] rrs_maintainer_history: fix syntax Tim Orling
2024-01-15 18:03 ` [layerindex-web][PATCH 3/6] rrs_upgrade_history: remap new srcrev fetcher API Tim Orling
2024-01-15 18:03 ` [layerindex-web][PATCH 4/6] rrs_upstream_history: allow skip update_data Tim Orling
2024-01-15 18:03 ` [layerindex-web][PATCH 5/6] rrs_upstream_history: fix get_recipe_pv_without_srcpv Tim Orling
2024-01-15 18:03 ` [layerindex-web][PATCH 6/6] rrs_upstream_history: fix get_upstream_info Tim Orling

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=cover.1705341467.git.tim.orling@konsulko.com \
    --to=ticotimo@gmail.com \
    --cc=yocto@lists.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.