Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65468 - [flyspray] bug tracker search function fails for some package name

Attached to Project: Arch Linux
Opened by Dennis Busch (Dennis) - Wednesday, 12 February 2020, 12:58 GMT
Last edited by Jelle van der Waa (jelly) - Wednesday, 16 September 2020, 19:04 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Jelle van der Waa (jelly)
Sven-Hendrik Haase (Svenstaro)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Steps to reproduce:
1.) go to: https://www.archlinux.org/packages/extr … emtest86+/
2.) click "Bug Reports"
3.) see that results are empty
4.) remove the "+" from the end in the search field and search again
5.) see the bugs for that package
This task depends upon

Comment by Dennis Busch (Dennis) - Wednesday, 12 February 2020, 13:00 GMT
correct link for step 1.) https://www.archlinux.org/packages/extra/any/memtest86+/
Comment by Dennis Busch (Dennis) - Wednesday, 12 February 2020, 13:30 GMT
Sorry, forgot this bug tracker is only for packaging issues. I reported it upstream here: https://bugs.flyspray.org/index.php?do=details&task_id=2591
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 12 February 2020, 13:36 GMT
I'll check, but this might be due to the regexes we use on flyspray's nginx configuration. I'm not sure this worked before either, because I don't even have the previous nginx config file anymore.
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 12 February 2020, 17:50 GMT
Well, given that upstream has fixed the issue, it's a downstream issue, because we use our own "customized" version of flyspray.
Comment by Dennis Busch (Dennis) - Saturday, 15 February 2020, 09:30 GMT
It has been confirmed as a bug upstream (and they fixed it in their github master branch): https://bugs.flyspray.org/index.php?do=details&task_id=2591
Comment by Giancarlo Razzolini (grazzolini) - Monday, 17 February 2020, 18:20 GMT
@Dennis

I understand that, but I need to pick up those upstream changes and merge into our downstream version of flyspray. I plan on doing this during this next week.
Comment by Dennis Busch (Dennis) - Monday, 17 February 2020, 18:22 GMT
Aye, did not intend to pressure, just thought I'd report the update from upstream for completeness sake.

Loading...