Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: filebot 4.7.7-5

Git Clone URL: (read-only)
Package Base: filebot
Description: The ultimate tool to rename TV/anime shows, download subtitles, and validate checksums.
Upstream URL:
Keywords: mass rename subtitle
Licenses: GPL
Submitter: ndowens
Maintainer: max.bra
Last Packager: max.bra
Votes: 117
Popularity: 3.672395
First Submitted: 2009-06-21 07:41
Last Updated: 2017-01-17 16:45

Pinned Comments

apodim commented on 2016-12-24 19:42

Just a note to those that don't want to use java-p7zip-binding, or can't because their platform is not supported (arm).

You can also use "Apache Common VFS", which is actually the default extractor of filebot portable, or "p7zip".

Latest Comments

1 2 3 4 5 6 ... Next › Last »

max.bra commented on 2017-01-17 16:54

Thanks for the clarification. Not being a JNA specialist and not reading the internal manifest files, i was not aware of these differences about internal versions.

Episode 3
Non hacky way but greater donwload size. Native code is now from official JNA release.
Ready for the upcoming versions FB 4.7.8 - JNA 4.3.0.

rednoah commented on 2017-01-17 10:26

FileBot bundles the JNA class files, but not the JNA native code.

FileBot 4.7.7 bundles JNA 4.2.2 which uses jnidispatch 4.0.1
FileBot 4.7.8 (alpha) bundles JNA 4.3.0 which uses jnidispatch 5.1.0

I've only tested this on my Mac, so it might actually be different from the less common / less maintained architectures.

All the native libraries that are usually in the jna.jar are also in the git repo:

You will find older versions of all the libraries in the git history:

apodim commented on 2017-01-13 23:33


Just tested latest build.

Sysinfo appears fine:
FileBot 4.7.7 (r4678)
JNA Native: 4.0.1

A run also completes successfully, same as with earlier versions.

Again thanks for your efforts!

max.bra commented on 2017-01-13 15:23

taken your word for it. included more arm archs with from last filebot official package that include them (4.7.5).

JNA restored, episode 2
yes, this is a bit hacky but this is the only way i have seen for include all archs other than x86 and x86_64 since 4.7.7 code does not work with latest jna release.

filebot JNA state:
jna 4.2.2 (latest) : filebot does not work
jna 4.0.1 (4.7.5) : filebot works (of course), arm* archs included. i'm not able to find linkable release on jna git repo
jna 4.0.0 (jna git): the only 4.0.x rel. on github, not working (apodim report)

this package, right now, restore native libs from phisical 4.7.5 filebot official package

edit: typo

apodim commented on 2017-01-12 20:59


Regarding dropping other architectures. I can attest that filebot works perfectly, albeit changing environment values for java to use more memory might be needed, with armv6.

Now about the default excractor, initially I used the one provided by "Apache Common VFS", just enabled rar and zip support from php.ini, but at some point I switched to p7zip because I had trouble with ISO files. So far works absolutely fine.

EDIT: Perhaps I got a little ahead of myself, just saw the changes in the build file relating to extractor and assumed it was something related to that, and the actual problem has something to do with this
"JNA Native: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/linux-arm/ not found in resource path ([file:/usr/share/java/filebot/filebot.jar])
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load arm (32-bit) native library Could not initialize class com.sun.jna.Native "

Again let me know if I can help.

max.bra commented on 2017-01-12 13:09

restored jna access retrieving an old jna version from official git
arch is now limited to i686, x86_64 and armv7h.

armv7h package is to be entirely tested. feedbacks appreciated.

your code does not work with latest jna version 4.2.2

rednoah commented on 2017-01-10 15:53

I dislike the idea of shipping native code for 10+ architectures hidden in a jar. It also lead to FileBot kinda/partially/mostly (but not fully) working by accident when FileBot and Java was installed for the wrong architecture.

All FileBot packages should include the required native libraries, and this change makes sure that they are included and loaded from the proper location (and not some random temporary folder).

Also, on some systems, the OS might block libraries loaded from non-secure locations. Due to JNA only including one "arm" binary, it may or may not work (and crash the process) on incompatible arm platforms.

max.bra commented on 2017-01-10 07:46

is there a compelling reason to have eliminated all native libs from 4.7.7 jar tree?

rednoah commented on 2017-01-09 19:57

FileBot extract module can be set without modifying the via the ENV:

export JAVA_OPTS="-Dnet.filebot.Archive.extractor=ApacheVFS"

rednoah commented on 2017-01-09 19:53

Newer versions of filebot portable expect all native libraries (including in the system library path.

Portable has been updated with the following options:

-Djna.nosys=false -Djna.nounpack=true