Package Details: acestream-engine 3.1.49-1

Git Clone URL: https://aur.archlinux.org/acestream-engine.git (read-only)
Package Base: acestream-engine
Description: ACE Stream engine
Upstream URL: http://acestream.org
Keywords: acestream engine
Licenses: unknown
Submitter: Scimmia
Maintainer: jonian
Last Packager: jonian
Votes: 121
Popularity: 0.89
First Submitted: 2013-04-11 21:20
Last Updated: 2019-07-28 17:01

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

koskal commented on 2017-05-22 16:48

I thought there was problem with python2-2.7.13-2 and python2-m2crypto 0.24.0-3,so I downgraded the packages and and worked again. Today I decided to update again and still working with no errors. The only change I've made was that I change the owner of the acestream folder in opt from root to my user, otherwise the gtk version cant start. So no problem here!! Thanks

positron commented on 2017-05-20 08:18

Here's working, what kind of recent updates you're talking about?

EDIT: Since libopenssl-1.0-compat has been orphaned I tried to do the trick using openssl-1.0 and it worked. Here's an updated PKGBUILD:

https://pastebin.com/EUMGMtgm

EDIT2: Works only with python2-m2crypto from testing.

koskal commented on 2017-05-15 16:06

After recent updates doesn't work:

2017-05-15 19:05:39,035|MainThread|acestream|error during startup
Traceback (most recent call last):
File "core.c", line 1590, in
File "core.c", line 144, in
File "core.c", line 86, in
File "/usr/lib/python2.7/site-packages/M2Crypto/__init__.py", line 26, in <module>
from M2Crypto import (ASN1, AuthCookie, BIO, BN, DH, DSA, EVP, Engine, Err,
File "/usr/lib/python2.7/site-packages/M2Crypto/ASN1.py", line 14, in <module>
from M2Crypto import BIO, m2
File "/usr/lib/python2.7/site-packages/M2Crypto/BIO.py", line 7, in <module>
from M2Crypto import m2
File "/usr/lib/python2.7/site-packages/M2Crypto/m2.py", line 30, in <module>
from M2Crypto._m2crypto import *
File "/usr/lib/python2.7/site-packages/M2Crypto/_m2crypto.py", line 17, in <module>
__m2crypto = swig_import_helper()
File "/usr/lib/python2.7/site-packages/M2Crypto/_m2crypto.py", line 16, in swig_import_helper
return importlib.import_module('__m2crypto')
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
ImportError: No module named __m2crypto

positron commented on 2017-05-01 20:54

Here's a PKGBUILD with the modifications mentioned by dieghen89:

https://pastebin.com/2XRMZD6W

dieghen89 commented on 2017-05-01 10:51

Why not making libopenssl-1.0-compat a dependency and adding the symlink inside the package? Having symlinks in the / that are untracked by the package manager is not a great idea.

milomilo commented on 2017-04-29 18:26

comment from cirrus is correct.
path "/opt/acestream/lib/" worked for me!

cirrus commented on 2017-04-28 12:45

mpuzirew: workaround #2 worked but i had to extact both .so files to /opt/acestream/lib/
thanks for the tip.

mpuzirew commented on 2017-04-25 10:43

Recent openssl-1.0 update to 1.0.2.k-3 version broke acestreamengine (error "version 1.0.0 not found" or smth. when trying to start engine). There are two possible workarounds:
1) Downgrade openssl-1.0 to 1.0.2.k-2 version and lock package update (put to ignore).
2) Other way, download openssl-1.0 1.0.2.k-2 package http://ala.seblu.net/packages/o/openssl-1.0/openssl-1.0-1.0.2.k-2-x86_64.pkg.tar.xz and manually unpack libcrypto.so.1.0.0 and libssl.so.1.0.0 files trom the package to /opt/acestream/lib/acestreamengine/, then acestreamengine will use these older libraries instead of system ones.

Best commented on 2017-04-14 19:59

The 2 versions installs differently too, so it was extra complexity with I did not want for something I was not going to use. Now you have the i686 aur package so hope everyone is happy now:)

thepasto commented on 2017-04-14 10:25

@an7oine Thanks!

I think the big difference between those two packages is not the architecture.
The version is different, x86_64 will be updated, unmantained 3.0.2 version for x86, is working now, but nobody can say how long it will and it won't be update anymore.
If we are going to use the same aur package for both version you'll see 3.1.16 version when you've 3.0.2 version, instead. You'll get upgrade notifications, when you've anything to update because your version will be always the same.

Just my opinion, as you can see i'm not the package mantainer! If you decide to merge the packages, it's not a real problem!