From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-bumpchecker:master commit in: modules/
Date: Fri, 3 Mar 2017 23:50:54 +0000 (UTC) [thread overview]
Message-ID: <1488576921.5a0aef2c23dd3bbf66cc530f3daef3f2e84cce9c.leio@gentoo> (raw)
commit: 5a0aef2c23dd3bbf66cc530f3daef3f2e84cce9c
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 3 21:34:08 2017 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Fri Mar 3 21:35:21 2017 +0000
URL: https://gitweb.gentoo.org/proj/gentoo-bumpchecker.git/commit/?id=5a0aef2c
gnome: Remove the old latest_versions_* vars that won't work
This also removes a GNOME class extra init in gnome_output for retrieving
the broken link, which won't be nice for future plans of requests usage
in terms of HTTP session
modules/gnome_module.py | 2 --
modules/gnome_output.py | 2 --
2 files changed, 4 deletions(-)
diff --git a/modules/gnome_module.py b/modules/gnome_module.py
index ba1f29f..205d96e 100644
--- a/modules/gnome_module.py
+++ b/modules/gnome_module.py
@@ -34,8 +34,6 @@ class GNOME:
self.gnome_release = ".".join(gnome_release_list[:2])
self.ftpserver = "download.gnome.org"
- self.latest_versions_file_path = 'http://www.gnome.org/~vuntz/tmp/versions/'
- self.latest_versions_url = self.latest_versions_file_path + 'versions-' + self.gnome_release
self.release_versions_file_path = 'https://download.gnome.org/teams/releng/'
def generate_data_from_versions_markup(self, url):
diff --git a/modules/gnome_output.py b/modules/gnome_output.py
index 9859a6f..f1fcfdf 100644
--- a/modules/gnome_output.py
+++ b/modules/gnome_output.py
@@ -61,8 +61,6 @@ class Output:
lines.append("<h2>Gnome " + clioptions_module.Options().get_arguments().release_number + " Progress</h2>")
lines.append("contact " + os.environ["USER"] + "@gentoo.org if anything is not correct<br>")
lines.append("Generated date: " + current_time + "<br>")
- lines.append("<a href=\"" + gnome_module.GNOME().latest_versions_url \
- + "\">Upstream versions list</a> <br>")
# stats
lines.append("<br>")
next reply other threads:[~2017-03-03 23:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 23:50 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-16 20:16 [gentoo-commits] proj/gentoo-bumpchecker:master commit in: modules/ Mart Raudsepp
2022-03-27 4:48 Matt Turner
2021-12-11 22:11 Mart Raudsepp
2021-04-14 22:57 Matt Turner
2021-04-14 22:57 Matt Turner
2019-08-24 16:38 Mart Raudsepp
2019-03-26 13:33 Mart Raudsepp
2019-01-16 0:27 Mart Raudsepp
2017-10-31 23:12 Mart Raudsepp
2017-03-21 2:57 Mart Raudsepp
2017-03-21 2:29 Mart Raudsepp
2017-03-21 2:29 Mart Raudsepp
2017-03-21 2:29 Mart Raudsepp
2017-03-21 1:59 Mart Raudsepp
2017-03-21 1:59 Mart Raudsepp
2017-03-20 23:12 Mart Raudsepp
2017-03-11 14:09 Mart Raudsepp
2017-03-03 23:50 Mart Raudsepp
2017-03-03 23:50 Mart Raudsepp
2017-03-03 23:50 Mart Raudsepp
2017-03-03 23:50 Mart Raudsepp
2017-03-03 23:50 Mart Raudsepp
2017-03-03 23:50 Mart Raudsepp
2017-03-03 23:50 Mart Raudsepp
2012-11-21 23:42 Gilles Dartiguelongue
2011-09-04 19:27 Mart Raudsepp
2011-06-07 16:36 Nirbheek Chauhan
2011-03-26 2:59 Nirbheek Chauhan
2011-03-15 13:19 Tomas Chvatal
2011-02-20 21:03 Nirbheek Chauhan
2011-02-20 13:56 Tomas Chvatal
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=1488576921.5a0aef2c23dd3bbf66cc530f3daef3f2e84cce9c.leio@gentoo \
--to=leio@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