Package Details: plex-media-server 1.41.0.8994-1

Git Clone URL: https://aur.archlinux.org/plex-media-server.git (read-only, click to copy)
Package Base: plex-media-server
Description: The back-end media server component of Plex.
Upstream URL: https://plex.tv/
Keywords: DLNA
Licenses: custom
Conflicts: plex-media-server-plexpass
Submitter: alucryd
Maintainer: fryfrog (tixetsal)
Last Packager: fryfrog
Votes: 348
Popularity: 0.029861
First Submitted: 2014-10-14 22:11 (UTC)
Last Updated: 2024-09-26 17:02 (UTC)

Latest Comments

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 107 Next › Last »

tmoore commented on 2016-02-12 15:51 (UTC)

Please don't flag out of date. 0.9.15.3-1674 is for plexpass members only. See https://aur.archlinux.org/packages/plex-media-server-plexpass/ instead

zer0t3ch commented on 2016-02-11 03:13 (UTC)

@techwiz Thanks for the fast response, but I figured it out. Turns out, when you log into a server remotely (over WAN) without first setting it up from localhost, it shows you your other servers, but refuses to make that fact obvious. TL;DR: I'm retarded, I was looking at server 1 through server 2.

techwiz commented on 2016-02-11 01:52 (UTC)

@tmoore client should be like v2.5.4 @zer0t3ch did you reload the plex app after restarting the plex service? That is, navigate to the plex app again, not refresh the page.

tmoore commented on 2016-02-11 01:50 (UTC) (edited on 2016-02-11 01:52 (UTC) by tmoore)

You sure you aren't seeing the *client* version in your browser? i.e. the player? what does "pacman -Q | grep plex" say? Also, shift-refresh your browser, you could have a cache issue.

zer0t3ch commented on 2016-02-11 01:46 (UTC)

So I'm having a bit of an odd problem. After stopping the service, wiping all traces of plex from my computer, and then installing from this package, the Plex web interface is showing as running Version 0.9.12.13. Just to be sure, I made 100% certain that no instance was running and manually ran the binary installed from this package, and it still shows up as the wrong version, despite the correct version's RPM being downloaded by makepkg. Any ideas? I'm at a complete loss.

justin8 commented on 2016-02-03 01:18 (UTC) (edited on 2016-02-03 01:18 (UTC) by justin8)

Yep! Keep up the good work

tmoore commented on 2016-02-03 00:46 (UTC)

Just so I'm clear, is everyone happy with the current state of the PKGBUILD? :)

justin8 commented on 2016-02-03 00:12 (UTC)

Yeah, there is no point depending on current packages being installed changing the package creation, that is just a recipe for disaster. @jquagga you don't need to delete them at all, it works on grsec/selinux and vanilla kernels just fine with it there. It just increases compatibility.

alucryd commented on 2016-02-02 18:45 (UTC)

That would only work if you build on the same machine, or one that has SELinux/Grsec. People with modest servers/NASes probably build their packages on much more powerful computers.

jquagga commented on 2016-02-02 18:38 (UTC)

Rather than the different makedepends per arch, I think it would be simpler to test for the presence of selinux or grsecurity and then add the makedepends and the execstack command. That would leave most of us not running selinux/grsec (including all the the ARM folks) without having to delete those lines.

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 107 Next › Last »