Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 178073 - kde-misc/kio-locate wrong HOMEPAGE on packages.g.o.
Summary: kde-misc/kio-locate wrong HOMEPAGE on packages.g.o.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: [OLD] gpackages (show other bugs)
Hardware: All All
: High minor (vote)
Assignee: Albert Hopkins (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-11 16:37 UTC by Markus
Modified: 2011-11-11 15:59 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus 2007-05-11 16:37:45 UTC
+++ This bug was initially created as a clone of Bug #175076 +++

As of the currently visible ebuild in the database (0.4.5), this issue is not fixed. 
It still points to arminstraub.de (see below for original bug report). Additionally, the HOMEPAGE link now opens several ad popups and tries to initiate the download of file called "new.exe" in the background (the hazardous part), which might contain potentially dangerous software. (I couldn't check what this exe-file does though, but I think it's at least suspicious)

Therefore I request to change the HOMEPAGE link to http://www.arminstraub.com/browse.php?page=programs_kiolocate (It's arminstraub.de now)

---cut---orinial bug---

Wrong HOMEPAGE in kio_locate ebuilds, as arminstraub.de is abandoned and Armin Straub uses arminstraub.com now as homepage.

Reproducible: Always

Steps to Reproduce:
1. grep HOMEPAGE /usr/portage/kde-misc/kio-locate/*.ebuild
2. browse arminstraub.de , see it abandoned


Expected Results:  
HOMEPAGE should be 
http://arminstraub.com/browse.php?page=programs_kiolocate
in kio_locate's ebuilds.

Armin Straub seems to have arminstraub.com now as a new homepage (he's living in USA now)

I'll notify the previous maintainer of kio_locate (Michael Schürig, until v0.1), as he too points to arminstraub.de.
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2007-05-11 17:17:52 UTC
No idea, where you're looking it up, but the ebuild definitely has been fixed on April the 18th.
Comment 2 Markus 2007-05-11 18:30:05 UTC
I'm looking it up here:
http://packages.gentoo.org/search/?sstring=kio-locate
and here:
http://packages.gentoo.org/ebuilds/?kio-locate-0.4.5

Klick on the HOMEPAGE link on either page and it will lead to:
http://arminstraub.de/browse.php?page=programs_kiolocate
which, as I said, opens several poups and attempt to download some shady executable.
Ok, update: I just tried it again 1 min ago. The exe download seems to be gone but it still leads into pop-up hell.
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2007-05-11 18:36:05 UTC
$ grep HOMEPAGE /usr/portage/kde-misc/kio-locate/*.ebuild
HOMEPAGE="http://arminstraub.com/browse.php?page=programs_kiolocate"

Has nothing to do w/ the ebuild. No idea why packages.g.o. doesn't get updated over and over again.
Comment 4 Markus 2007-05-11 19:34:15 UTC
(In reply to comment #3)
> $ grep HOMEPAGE /usr/portage/kde-misc/kio-locate/*.ebuild
> HOMEPAGE="http://arminstraub.com/browse.php?page=programs_kiolocate"
> 
> Has nothing to do w/ the ebuild. No idea why packages.g.o. doesn't get updated
> over and over again.
> 

Well, I'm sorry if it doesn't have anything to do with the ebuild, but I don't know where I should file the bug instead. I tried emailing the mail adress that was listed in the bottom line of packages.gentoo.org. I got a reply from there to come here and file a bug, which I did. This is my second try to bring this to anybodys attention within 24 hours, and I'm giving up now. If anybody knows who is responsible or in charge, please notify them, I'm tired of being told "It has nothing to do with me, go tell someone else".
Comment 5 Albert Hopkins (RETIRED) gentoo-dev 2007-05-11 22:06:46 UTC
I've made a "small" change to the homepage_update routine that really shouldn't have made any difference.  There have been a lot of timeouts lately connecting to the DB server so that may have been the problem.  Nevertheless it seems to be fixed now.