Bug 197874

Summary: freshports: Bug-Links wrong
Product: Services Reporter: Kalten <kalten>
Component: Bug TrackerAssignee: Dan Langille <dvl>
Status: Closed FIXED    
Severity: Affects Many People CC: dan, koobs
Priority: ---    
Version: unspecified   
Hardware: Any   
OS: Any   

Description Kalten 2015-02-21 06:16:20 UTC
The problem occurs if one browses through a port description on
http://www.freshports.org/ e.g. http://www.freshports.org/www/firefox/
or in a search result list
e.g. http://www.freshports.org/search.php?query=firefox

If one clicks on the red “Find issues related to this port” bug (without
‘+’-sign) it results in a link e.g.
---8<---
https://bugs.freebsd.org/bugzilla/buglist.cgi?component=Individual%20Port%28s%29&list_id=28394&product=Ports%20Tree&query_format=advanced&resolution=---&short_desc=www%2Ffirefox&short_desc_type=allwordssubstr
--->8---
but it ought to be
---8<---
https://bugs.freebsd.org/bugzilla/buglist.cgi?component=Individual%20Port%28s%29&list_id=28394&product=Ports%20%26%20Packages&query_format=advanced&resolution=---&short_desc=www%2Ffirefox&short_desc_type=allwordssubstr
--->8---
i.e. changing
“product=Ports%20Tree” to
“product=Ports%20%26%20Packages”
Or one will not find any reports.

Similar:
If one clicks on the red “Report an issue related to this port” bug (with
‘+’-sign) it results in a link e.g.
---8<---
https://bugs.freebsd.org/bugzilla/enter_bug.cgi?component=Individual%20Port%28s%29&product=Ports%20Tree&short_desc=www%2Ffirefox
--->8---
but it ought to be
---8<---
https://bugs.freebsd.org/bugzilla/enter_bug.cgi?component=Individual%20Port%28s%29&product=Ports%20%26%20Packages&short_desc=www%2Ffirefox
--->8---
again i.e. changing
“product=Ports%20Tree” to
“product=Ports%20%26%20Packages”
Or a red field with the text
> Sorry, either the product Ports Tree does not exist or you aren't
> authorized to enter a bug into it. 
will appear.

Regards,
 Kalten
Comment 1 Marcus von Appen freebsd_committer freebsd_triage 2015-02-21 07:47:26 UTC
This is out of Bugmeister's access, since freshports.org is not maintained by Bugmeister.

I added the website maintainer to this bug, so he can have a look.
Comment 2 Dan Langille freebsd_committer freebsd_triage 2015-02-21 14:56:15 UTC
Thank you for this.

Fixed.  Please confirm, then I'll close this.
Comment 3 Kalten 2015-02-22 02:06:54 UTC
(In reply to Marcus von Appen from comment #1)
>> This is out of Bugmeister's access, since freshports.org is not
>> maintained by Bugmeister. 
I think you had been assigned to it automatically—I am not sure.

>> I added the website maintainer to this bug, so he can have a look.
Thank you!
Did I select the wrong possibilities?
 Product: Services
 Component: Bug Tracker
Which one would have been correct?

(In reply to Dan Langille from comment #2)
> Thank you for this.
I am the one to say thank you to you and all the others for all that
work! :-)

> Fixed.  Please confirm, then I'll close this.
Yes: Searching as well as reporting bugs related to the ports there
works in search result lists and description pages of ports now.
Everything is fine now.

One more thing: you could add a link on http://www.freshports.org/ on
the right inside the “This site”-box allowing to report bugs on
FreshPorts it self—let us say “Report Bug on the FreshPorts website” or
something similar so that from now on people will not have to wonder
which “Product:”, “Component” and “Summary”-prefix to use.

Regards,
 Kalten
Comment 4 Dan Langille freebsd_committer freebsd_triage 2015-10-31 15:00:55 UTC
Have a look at http://beta.freshports.org/issues.php
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-02 05:03:00 UTC
@Dan Has this been resolved? If so please close with correct/appropriate resolution type
Comment 6 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-02 05:04:15 UTC
We should probably have a FreshPorts Component under the Services Product given it is such a prominent/important service.
Comment 7 Dan Langille freebsd_committer freebsd_triage 2015-11-02 11:58:39 UTC
(In reply to Kubilay Kocak from comment #5)
I'm waiting for feedback from the OP before closing, but yes, I've done the work.