From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016
Date: Tue, 20 Dec 2016 23:57:10 +0100 [thread overview]
Message-ID: <1748fb90-d51f-49b1-33df-f1d7a8508866@gentoo.org> (raw)
In-Reply-To: <20161105084708.712a975d.mgorny@gentoo.org>
On 2016-11-05 08:47, Michał Górny wrote:
> Thou shalt not rely on the mirrors! Though mirrors as a temporary
> solution are acceptable. As long as you don't turn it into 'wrong
> SRC_URI is fine, the file is on the mirrors'.
> Also, it would be nice not to have the berlios -> sourceforge crap
> repeated. If software is dead-dead, we should lastrite it or revive it,
> not point to some dead copy by malware hosting provider.
The shutdown is in two weeks.
One can see clearly a drop of broken ebuilds after the first mail on the
mailinglist and after the personal mail on 2016-11-24. [1] Thank you all
for fixing so many ebuilds already.
But still 400 ebuilds use googlecode.
56 of these do not have a maintainer.
How should we proceed now?
Should we lastrite all unmaintained packages and generate bugtickets for
the maintained ebuilds?
Who has experience with automatic generation of bugtickets and could
write a script for this? The tickets should block the main ticket [2].
[1] http://www.akhuettel.de/~huettel/plots/googlecode.php
[2] https://bugs.gentoo.org/show_bug.cgi?id=544092
--
Best,
Jonas
next prev parent reply other threads:[~2016-12-20 22:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 23:54 [gentoo-dev] Google Code shutdown requires 524 ebuilds to be fixed before end of 2016 Jonas Stein
2016-11-05 0:20 ` Rich Freeman
2016-11-05 0:23 ` M. J. Everitt
2016-11-05 0:30 ` M. J. Everitt
2016-11-05 1:20 ` Rich Freeman
2016-11-05 1:29 ` M. J. Everitt
2016-11-05 1:21 ` Jonas Stein
2016-11-05 1:36 ` Jonas Stein
2016-11-05 3:09 ` Mike Gilbert
2016-11-05 4:45 ` Kent Fredric
2016-11-05 4:51 ` M. J. Everitt
2016-11-06 0:16 ` Robin H. Johnson
2016-12-25 1:13 ` Gokturk Yuksek
2016-12-25 5:54 ` Daniel Campbell
2016-11-05 7:38 ` Paweł Hajdan, Jr.
2016-11-05 7:47 ` Michał Górny
2016-12-20 22:57 ` Jonas Stein [this message]
2016-12-21 8:42 ` Gokturk Yuksek
2016-12-21 12:41 ` Kent Fredric
2016-12-21 20:54 ` Andreas K. Huettel
2016-12-24 10:29 ` Raymond Jennings
2016-12-24 14:38 ` Mart Raudsepp
2016-11-05 11:05 ` Sergei Trofimovich
2016-12-20 22:35 ` Jonas Stein
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=1748fb90-d51f-49b1-33df-f1d7a8508866@gentoo.org \
--to=jstein@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