The port databases/mantis is wildly out of date. While the bug reporting guidlines state not to raise bug reports for this I feel it is warranted as for some reason portscout is not picking up on the new versions. https://portscout.freebsd.org/ports@freebsd.org.html Doesn't list the port as out of date and the port revision is 1.2.19. However visiting www.mantisbt.org shows the current version as 2.5.1. I think the fact that portscout hasn't picked up the version update also means that the port vulnerability checker isn't picking up the fact that the current port revision has many uncorrected security defects. 5 were fixed in 1.2.20 and there have been may more raised against the 1.3.x and 2.x.x releases which could easily also apply to 1.2.19.
I no longer use mantis. I am happy to give up maintainership and/or commit PRs submitted to update the port. As usual, it's a matter of time resources.
That's cool. I'll see if I can find some time to submit an updated package for a more up to date version as we do use it here. Is it still worth working out why the portcout tool isn't picking up the version announcements?
I would wait until after the port is updated.
Created attachment 184703 [details] update to 2.5.1 + plugins Need q-a and feedback.
(In reply to Dan Langille from comment #1) What bug tracker do you use?
I have several databases that are currently running 1.2.19 from the port so once I work out which plugins we need I can test this on our test deployment jail. It might take a while as although I'm the system admin I'm not the mantis db admin so I might need a little time with them to understand what bits of mantis we do actually use so I can configure the port appropriately.
(In reply to rozhuk.im from comment #5) I'm not using a bug tracker at home now.
Created attachment 184719 [details] update to 2.5.1 + plugins add missing libs, remove unneeded files
Created attachment 184727 [details] update to 2.5.1 + plugins Remove all plugns than compatible only with 1.x. If some one want to use 1.x then easy way to start - modify prev attachment to use 1.x core and remove from there 2.x only plugins.
I tried the attached patch. It fails. Details at https://services.unixathome.org/poudriere/data/110amd64-working/2017-08-06_21h41m41s/logs/errors/mantis-2.5.1.log summary: ====> You must check at least one option in the PLUGINS multi I'm out of time. If you can fix it, I'll try again.
Created attachment 185616 [details] fix options selection
Thank you. Are you sure that databases/mantis/files/patch-api_rest_swagger_index.php is required? That patch does not apply cleanly, and looking at the vendor code, it seems fine.
Created attachment 185639 [details] applies cleanly and builds - based on previous patch applies cleanly and builds
If you like the most recently submitted patch, I'll commit it.
(In reply to Dan Langille from comment #12) Yes, it required. Without it some script will be loaded from external source. I install matis in few different places with my patch, can you provide more information about failures?
Created attachment 185654 [details] includes patch dropped in previous attempt (In reply to rozhuk.im from comment #15) I have no idea why I thought that. Here is a new patch from my working directory. It is also vastly different from what I had before. I have no explanation.
(In reply to Dan Langille from comment #16) Looks ok, but in my patch I remove tests and some crap by hands to not install it.
(In reply to rozhuk.im from comment #17) Would you like to become the maintainer for this port?
(In reply to Dan Langille from comment #18) No, thanks.
A commit references this bug: Author: dvl Date: Tue Aug 22 14:55:13 UTC 2017 New revision: 448537 URL: https://svnweb.freebsd.org/changeset/ports/448537 Log: Upgrade to 2.5.1 give up MAINTAINER PR: 220689 Changes: head/databases/mantis/Makefile head/databases/mantis/distinfo head/databases/mantis/files/patch-api_rest_swagger_index.php head/databases/mantis/files/patch-config__defaults__inc.php head/databases/mantis/pkg-plist
Thank you all.