![]() JVM: 64-bit Java HotSpot(TM) 64-Bit Server VMĬPU/MEM: 4 Core / 3 GB Max Memory / 22 MB Used Memory JRE: Java(TM) SE Runtime Environment 1.8.0_91 (headless) Sudo dpkg -i /path/to/filebot_4.7.8_bįileBot 4.7.2 (r4178) / Java(TM) SE Runtime Environment 1.8.0_91 (headless)Ĭhromaprint: fpcalc version 1.1.0 (/usr/share/filebot/fpcalc) Sudo aptitude install openjdk-8-jre-headless Please run `filebot -license *.psm` to install your FileBot license. License Error: UNREGISTERED FileBot requires a valid license. Latest Stable Version 4.9.2 (requires licence) 11.2 ERROR: ClassCastException: Cannot cast to.11.1 WARNING: An illegal reflective access operation has occurred.9 FlexGet + Transmission + Filebot Automation.I noticed was listed as a maintainer and i've helped with some dev testing on his plex-media-server ebuild somewhat recently and i'm curious if he might have a suggestion to attempt to nullify that stdout ebuild warning. I'm interesting in submitting a pull request to update filebot to the newer version but the ERROR warning spam would have most people using such an ebuild executing a "doomsday prepping" plan because the error may have done something undesirable to their gentoo install D The dev ebuild i've been working on for filebot 4.8.5 the classpath java dependencies have changed and importing only the filebot jarfile no longer results in filebot being functional.Ī functional substitution to the filebot 4.8.5 ebuild to import/parse all of the new jarfiles results in the ebuild stdout spamming !!! ERROR: Couldn't find a VM dep for 30 or more lines before the ebuild install successfully completes.įor i in jar/* do java-pkg_dojar "$i" done ![]() After i decided to import all of the available jarfiles filebot worked without any complaints regarding missing java classes.Īttempts to install args4j using emerge then have those java classes satisfy the classpath requirements did not correct the filebot classpath runtime error. I attempted to test if filebot 4.8.5 would function without the added jarfiles but that just resulted in a classpath runtime error for args4j and then several other java classes. This error doesn't prevent filebot from functioning but is a larger concern for the filebot 4.8.5 ebuild i've been tinkering with as only one jar file is no longer satisfactory for the java-utlis-2 eclass to build a functional classpath for the end goal of installing a functional filebot ebuild. It's entirely plausible the java-utils-2 eclass has been updated within the past two years and this ebuild error may not have manifested in the past but it appears to be a concern now if filebot ebuilds are to remain functional. ![]() This is not a large concern with only one jarfile to parse or import but i'm not aware of a method to correct this VM dep warning using gentoo's java eclasses and it should be corrected due to changes with the newer version of filebot 4.8.5 i've been testing. Install media-video/filebot-4.7.9-r2 into /var/tmp/portage/media-video/filebot-4.7.9-r2/image/ I've been tinkering a bit with the filebot ebuild attempting to make an updated ebuild as a recent student expressed an interest in using filebot but noticed the java-utils-2 eclass utility was producing an error warning when the filebot jar file was imported or parsed during src_install()
0 Comments
Leave a Reply. |