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