Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 494678 ( - [TRACKER] is gone
Summary: [TRACKER] is gone
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Quality Assurance Team
Keywords: Tracker
: 537662 541806 (view as bug list)
Depends on: 537688 537690 537692 537694 537696 537698 537700 537702 537704 537706 537708 537710 537712 537714 537716 537718 537720 537722 537724 537726 537728 537730 537732 537734 537736 537738 537740 537742 537744 537746 537748 537750 537752 537754 537756 537758 537760 537762 537764 537766 537768 537770 537772 537774 537776 537778 537780 537782 537784 537786 537788 537790 537792 537794 537796 537798 537800 537802 537804 537806 537808 537810 537812 537814 537816 537818 537820 537822 537824 556666
Blocks: thirdpartymirrors-13
  Show dependency tree
Reported: 2013-12-18 20:39 UTC by Ben Kohler
Modified: 2021-03-25 19:24 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---

berlios_mirror_DEAD_ebuild_list (berlios_mirror_DEAD_ebuild_list,10.29 KB, text/plain)
2015-01-25 22:59 UTC, Jeroen Roovers (RETIRED)
berlios_directly_DEAD_ebuild_list (berlios_directly_DEAD_ebuild_list,1.20 KB, text/plain)
2015-01-25 23:01 UTC, Jeroen Roovers (RETIRED)

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Kohler gentoo-dev 2013-12-18 20:39:05 UTC

1 of 2 mirrors in the "berlios" mirror group in profiles/thirdpartymirrors is no longer valid. These were checked as part of an analysis of all third party mirror lists.  


Furthermore, the remaining mirror just redirects to sourceforge, so this berlios mirror group probably does not need to still exist... but approximately 110 ebuilds are still using it.

Comment 1 BT 2014-08-30 03:05:51 UTC
The BerliOS hosting service was shutdown on 30 April 2014. The berlios mirror group should be removed since both mirrors are now dead.

SourceForge has mirrored[1] all BerliOS projects. Any ebuilds using the berlios mirror group can be switched to the sourceforge mirror group.

Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-25 22:38:47 UTC
*** Bug 537662 has been marked as a duplicate of this bug. ***
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-25 22:39:44 UTC
+  25 Jan 2015; Jeroen Roovers <> thirdpartymirrors:
+  Drop mirrors (bug #494678).
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-25 22:44:06 UTC
(In reply to Jeroen Roovers from comment #2)

@Jonas: Did you have a list, say?
Comment 5 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-25 22:46:17 UTC
Should this become a tracker bug with dependent bugs for each package using mirror://berlios or (illegally as per bug #218657) using the domain directly?
Comment 6 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-25 22:59:26 UTC
Comment 7 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-25 22:59:44 UTC
Created attachment 394886 [details]
Comment 8 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-25 23:01:51 UTC
Created attachment 394892 [details]
Comment 9 Jeroen Roovers (RETIRED) gentoo-dev 2015-01-26 00:13:24 UTC
Needless to say, some of these projects might have gone to live elsewhere and should probably not be linked to the berlios -> sourceforge dump.
Comment 10 Jeroen Roovers (RETIRED) gentoo-dev 2015-03-13 12:18:22 UTC
*** Bug 541806 has been marked as a duplicate of this bug. ***
Comment 11 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2015-12-04 21:29:57 UTC
What are we planning to do about this? It's 1.5yr overdue already, and it forces me to ignore invalid mirror:// entries for gentoo-ci.
Comment 12 Jonas Stein gentoo-dev 2016-02-29 17:57:02 UTC
Some packages have a dead upstream for years and no maintainer. At least a (proxy) maintainer would be needed to fix the ebuild. 
I think we can hard mask these with a long delay (90 days?).

For packages with gentoo maintainer (or at least proxy maintainer), I suggest to send a last rite. 

To keep the package just few things are required:
a) find the latest mirror (on sourceforge) 
b) verify, that it is the original source code and not a malicious copy in the name of the old project
c) fix the URL in the ebuild.

This is a little burden, if anybody is interested in keeping these packages and as usual there would be help for new motivated proxy maintainers. 

I suggest to hard mask these and prepare them for deletion with a long delay 
(> 90 days?).
Comment 13 Jeroen Roovers (RETIRED) gentoo-dev 2016-02-29 18:45:19 UTC
(In reply to Jonas Stein from comment #12)
> I suggest to hard mask these and prepare them for deletion

If the missing upstream is the only problem then they should not be removed.
Comment 14 Jonas Stein gentoo-dev 2016-03-13 12:28:09 UTC
> If the missing upstream is the only problem then they should not be removed.

Jeroen, I fully agree, but to my understanding packages need a fix. 
And if nobody volunteers to fix the broken packages after so long timespan we should not leave it in the main tree. 
In most cases the fix will be just time consuming and not difficult like comparing the original source with SF, changing the URL to SF and testing...
Comment 15 Pacho Ramos gentoo-dev 2016-03-13 15:51:27 UTC
Per comment #13, lastritting the packages only for the mirror issue won't probably be really welcomed :|

Well, if QA team want to hardmask them *with the QA hat on*, fine for me... but I won't last rite them from treecleaners, put my mail there and, at the end, me needing to deal with all the angry people (yes, I am used to get really "nice"  private mails because of that) and need to push myself the fixes to the ebuilds that people could rise

Also, cannot we simply rely on our mirrors for them? Looks like in most cases (if not all) they don't have any restriction forcing us to download the sources from iriginal SRC_URI :|
Comment 16 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2016-03-13 16:01:39 UTC
I don't really care who solves this and how. What I'm concerned about, is that a major QA violation (SRC_URI is *invalid*, not just unreachable but *invalid*) is live for 2 years already and nobody bothers fixing it. If people really want to keep their fancy packages, then they need to do this tremendous effort and fix them. I don't have time to fix every QA violation other developers find good to commit and that others love to keep.

That said, since nobody seems to bother, I will try to mask all the involved packages and see if this is enough to silence the QA issues. I doubt this will be enough, so I will probably end up effectively masking them and commenting out SRC_URI.

If someone wants to replace the URIs with spamforge, it's their choice. As far as I'm concerned, this is a move with no benefit and pointless advertisement of company whose behavior towards open source community (see: gimp) is inappropriate, saying lightly. Dead packages are dead, and read-only mirrors of dead homepages don't help much.
Comment 17 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2016-03-13 16:05:00 UTC
Oh wait, I already replaced all those mirror:// entries. So all left is to drop packages that are dead with no upstream.
Comment 18 Pacho Ramos gentoo-dev 2016-03-13 16:32:07 UTC
Then, should we simply close the current opened bug reports? (as they are not relying on anymore?)
Comment 19 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2016-03-13 16:33:36 UTC
I've only wiped out SRC_URIs. Someone should still try to find new home for the packages, or lastrite them.