Bug 244697 - net-p2p/jackett: needs updated to 0.13.x
Summary: net-p2p/jackett: needs updated to 0.13.x
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-09 18:16 UTC by Phillip R. Jaenke
Modified: 2020-06-21 16:27 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (michiel)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Phillip R. Jaenke 2020-03-09 18:16:01 UTC
Primarily for awareness pending Mono updates.
Discovered as part of lang/mono 6.8.0.105 update testing; net-p2p/jackett is unable to correctly bind to the network port due to a .NET change, and will not function. This was resolved by upstream somewhere in 0.13.x and confirmed working with 0.13.560. 
However, 0.13.560 will not work with mono 5.10! So the update to 0.13.x can't be done until the lang/mono 6.8.0.105 commit is done (D23300 on phab).
Comment 1 Michiel van Baak Jansen 2020-03-09 19:15:54 UTC
(In reply to Phillip R. Jaenke from comment #0)

Thanks for the report.
I am aware of this issue, and basically postponed all updates until the mono issues are resolved.
Jackett will not run on FreeBSD 12, because the kqueue interfaces have changed and the mono port lacks support for this.

I'm sorry for the current situation, but I dont have the time nor experience to actually help and fix the mono port, so I'm basically waiting for the mono team to get that resolved before I will invest time in the jackett port again.
Comment 2 Michiel van Baak Jansen 2020-06-21 16:07:55 UTC
(In reply to Phillip R. Jaenke from comment #0)

See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247460
Comment 3 Lewis Cook freebsd_committer freebsd_triage 2020-06-21 16:27:06 UTC
^Triage: Closed as requested from maintainer

If there any relevant information, please feel free to re-open for further discussion. Until then refer to bug#247460.