Date: Tue, 21 Nov 2023 09:08:08 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 274418] news/nzbhydra2: Update to 5.1.11 Message-ID: <bug-274418-7788-zgMsbsAIPh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274418-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-274418-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274418 kreeblah@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #245572|0 |1 is obsolete| | Attachment #246457| |maintainer-approval?(marcel Flags| |@herrbischoff.com) --- Comment #4 from kreeblah@gmail.com --- Created attachment 246457 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D246457&action= =3Dedit Update news/nzbhydra2 to 5.3.3 and ensure lib/ only contains the current .j= ar file 5.3.3 was just released, and the new wrapper file in it contains a fix for = what was probably causing the issues with not being able to find java. There wa= s a bug in the old version which was causing it to overwrite the java parameter. So, this updates to 5.3.3. I also added a line to the startup script to cl= ean out the lib/ directory and remove any file which doesn't match the current = .jar file, since that should be the only file in there. This should ensure that= , no matter what, there aren't any issues with upgrades. >From talking with folks, apparently some of the code paths that pkg takes f= or local packages can leave old files around, which is likely how that was happening with files in the lib/ directory, but this would compensate for t= hat. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274418-7788-zgMsbsAIPh>