public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/qa-scripts:master commit in: /, htdocs/
Date: Mon, 25 May 2020 12:22:08 +0000 (UTC)	[thread overview]
Message-ID: <1590409289.5a8ae2ba0aa45f033b71638e64105d139f809224.mgorny@gentoo> (raw)

commit:     5a8ae2ba0aa45f033b71638e64105d139f809224
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon May 25 12:21:29 2020 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Mon May 25 12:21:29 2020 +0000
URL:        https://gitweb.gentoo.org/proj/qa-scripts.git/commit/?id=5a8ae2ba

gpyutils: Enable for 38→39, also 37→38 stablereq

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 Makefile.gpyutils | 12 +++++++++++-
 htdocs/index.html |  2 ++
 2 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/Makefile.gpyutils b/Makefile.gpyutils
index 940ad8e..f8fb1b8 100644
--- a/Makefile.gpyutils
+++ b/Makefile.gpyutils
@@ -6,7 +6,7 @@ timestamp = $(PORTDIR)/metadata/timestamp.commit
 outdir = /dev/null
 
 # upgrades for stable impls
-upgr_base = $(outdir)/36-to-37.txt $(outdir)/37-to-38.txt
+upgr_base = $(outdir)/36-to-37.txt $(outdir)/37-to-38.txt $(outdir)/38-to-39.txt
 # related stabilizations
 upgr_streq = $(patsubst %.txt,%-stablereq.txt,$(upgr_base))
 # all upgrade stuff
@@ -59,6 +59,16 @@ $(outdir)/37-to-38-stablereq.txt: $(timestamp)
 	gpy-upgrade-impl -s python3_7 python3_8 > $@.new
 	mv $@.new $@
 
+$(outdir)/38-to-39.txt: $(timestamp)
+	mkdir -p $(outdir)
+	gpy-upgrade-impl python3_8 python3_9 > $@.new
+	mv $@.new $@
+
+$(outdir)/38-to-39-stablereq.txt: $(timestamp)
+	mkdir -p $(outdir)
+	gpy-upgrade-impl -s python3_8 python3_9 > $@.new
+	mv $@.new $@
+
 %.dot: %.txt
 	gpy-depgraph -m python@gentoo.org $< > $@.new
 	mv $@.new $@

diff --git a/htdocs/index.html b/htdocs/index.html
index 2b8399b..3262c67 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -119,6 +119,8 @@
                 <a href="/output/gpyutils/36-to-37.txt" class="list-group-item list-group-item-action">Py3.6 → 3.7 testing</a>
                 <a href="/output/gpyutils/36-to-37-stablereq.txt" class="list-group-item list-group-item-action">Py3.6 → 3.7 stabilizations</a>
                 <a href="/output/gpyutils/37-to-38.txt" class="list-group-item list-group-item-action">Py3.7 → 3.8 testing</a>
+                <a href="/output/gpyutils/37-to-38-stablereq.txt" class="list-group-item list-group-item-action">Py3.7 → 3.8 stabilization</a>
+                <a href="/output/gpyutils/38-to-39.txt" class="list-group-item list-group-item-action">Py3.8 → 3.9 testing</a>
               </div>
             </div>
             <div class="col-lg-4">


             reply	other threads:[~2020-05-25 12:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 12:22 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-19  6:35 [gentoo-commits] proj/qa-scripts:master commit in: /, htdocs/ Michał Górny
2019-08-29  5:51 Michał Górny
2019-08-28  9:19 Michał Górny
2012-11-28 13:54 Jeremy Olexa
2011-06-22 14:25 Jeremy Olexa
2011-06-14 21:09 Jeremy Olexa
2011-05-03 20:22 Jeremy Olexa

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=1590409289.5a8ae2ba0aa45f033b71638e64105d139f809224.mgorny@gentoo \
    --to=mgorny@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox