[Bug]: sabnzbd=4.3.1-2
fails to install due to python-sabyenc3=8.2.0
and cffi
Android NDK incompatibility
#20243
Labels
bug report
Something is not working properly.
Problem description
sorry for yet another issue regarding
sabnzbd=4.3.1-2
it seems someone has angered some sort of dependency god somewhere...sabnzd=4.3.1-2
does not install nor run due to some more dependency problemscffi
requires a newer ndk or temporary fix from: [Python py project unable to build wheel]: #20039 to be able to be built.Additionally
sabnzbd=4.3.1-2
does not work even after applying that temporary fix aspython-sabyenc3
was already updated to8.2
in d3893d8 butsabnzbd=4.3.1-2
still expects8.1
. The current RC bumped it's requirement ofsabctools
(python-sabyenc3
) to8.2
: sabnzbd/sabnzbd@989e215As upstream probably still won't always bump those versions at the same time maybe it would be a good idea to exclude both
sabnzbd
as well aspython-sabyenc3
from auto-updates and make sure to not update one of them without the other?I did have some time to read the build environment documentation and was able to do some testing of my own this time and build
sabnzbd=4.3.2RC1
after changing theTERMUX_PKG_VERSION
andTERMUX_PKG_SHA256
:I'm not sure if this is expected behaviour but i also had to bootstrap
glib
according to #20070 (comment) and building some additional packages first as it did not pick them up correctly as dependencies or was not able to build the wheels for themHere are the steps I had to run in a clean docker build environment:
gobject-introspection
fromglib
'sbuild.sh
and disable it through the flag:glib
:gobject-introspection
:glib
file to force rebuilding:glib
:python-pip
:python-cryptography
:sabnzbd
:I would have assumed that everything except maybe
glib
, due to the bootstrapping stuff, should have been picked up automatically and no additional build steps would be required. But then again maybe I did something wrong. After reading the Order of build steps my first guess would be that the problem is the-s
for the installation/build of the dependencies?which then would prevent the installation of the dependencies of all packages on which sabnzbd depends?
Anyways: This
4.3.2RC1
package then installs and runs without a problem with my termux installation, where I had already applied the temporary fix from: #20039 to be able to installsabnzbd=4.3.1-2
while pinningpython-sabyenc3
to8.1
4.3.2
probably will be released soon and we probably can't really fix the NDK problem until there is a new release for it as well, so there are probably two options:sabnzbd
andpython-sabyenc3
to the latest working versions with the old ndk and without the temporary fix.sabnzbd
and a new Android NDK and leavesabnzdb
broken for now.What steps will reproduce the bug?
Installing
sabnzbd
with the newest package baseWhat is the expected behavior?
sabnzbd
should be installed and run without problemsSystem information
The text was updated successfully, but these errors were encountered: