Bug 240592 - broken URL in abuse package description
Summary: broken URL in abuse package description
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: abuse
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL: http://www.labyrinth.net.au/~trandor/...
Whiteboard:
Depends On:
Blocks: 237018
TreeView+ depends on / blocked
 
Reported: 2007-05-18 16:57 UTC by petrosyan
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-05-20 08:45:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description petrosyan 2007-05-18 16:57:48 UTC
Description of problem:
broken URL in abuse package description
URL         : http://www.labyrinth.net.au/~trandor/abuse/

Version-Release number of selected component (if applicable):
abuse-0.7.0-3.fc6

How reproducible:
Always

Steps to Reproduce:
rpm -qi abuse

Comment 1 Hans de Goede 2007-05-18 17:27:00 UTC
I've know this for a while, the problem is that upstream's site (which used to
be there) has disappeared, and there is no new site.

So any suggestions?


Comment 2 petrosyan 2007-05-18 17:58:41 UTC
Here is google cache of his page:
http://72.14.205.104/search?q=cache:C2U2kZiBcDEJ:www.labyrinth.net.au/~trandor/+%22Anthony+Kruize%22+abuse&hl=en&ct=clnk&cd=1&gl=us

Here is the sourceforge project he is referring to:
http://sourceforge.net/projects/abuse2

If the project simply disapperead maybe remove the URL field form the package
description?

Here is abuse's author's new homepage:
http://www.geocities.com/trandorous/

His email address is: (trandorous AT yahoo.com.au) maybe you could contact him
and ask him about the status of the project. It seems to me he has abandoned it.

Comment 3 Hans de Goede 2007-05-20 08:45:09 UTC
I've just build abuse-0.7.0-4 for devel, fixing the URL.

Once rawhide becomes rawhide again (once F7 is released), this version will show
up in rawhide.



Note You need to log in before you can comment on or make changes to this bug.