| 1 |
On 2016-11-05 08:47, Michał Górny wrote: |
| 2 |
> Thou shalt not rely on the mirrors! Though mirrors as a temporary |
| 3 |
> solution are acceptable. As long as you don't turn it into 'wrong |
| 4 |
> SRC_URI is fine, the file is on the mirrors'. |
| 5 |
|
| 6 |
> Also, it would be nice not to have the berlios -> sourceforge crap |
| 7 |
> repeated. If software is dead-dead, we should lastrite it or revive it, |
| 8 |
> not point to some dead copy by malware hosting provider. |
| 9 |
|
| 10 |
The shutdown is in two weeks. |
| 11 |
One can see clearly a drop of broken ebuilds after the first mail on the |
| 12 |
mailinglist and after the personal mail on 2016-11-24. [1] Thank you all |
| 13 |
for fixing so many ebuilds already. |
| 14 |
But still 400 ebuilds use googlecode. |
| 15 |
|
| 16 |
56 of these do not have a maintainer. |
| 17 |
|
| 18 |
How should we proceed now? |
| 19 |
|
| 20 |
Should we lastrite all unmaintained packages and generate bugtickets for |
| 21 |
the maintained ebuilds? |
| 22 |
|
| 23 |
Who has experience with automatic generation of bugtickets and could |
| 24 |
write a script for this? The tickets should block the main ticket [2]. |
| 25 |
|
| 26 |
|
| 27 |
[1] http://www.akhuettel.de/~huettel/plots/googlecode.php |
| 28 |
[2] https://bugs.gentoo.org/show_bug.cgi?id=544092 |
| 29 |
|
| 30 |
-- |
| 31 |
Best, |
| 32 |
Jonas |
Archives