cpoppema
commented
4 years ago Thanks for reporting in such detail @13k. I will confirm @aauren's PR as soon as I can and push new images.
libtorrent-rasterbar wasn't always installed by default, it used to be installed only for TORRENT_PLUGIN="deluge". Later I learned some other FlexGet plugins also rely on libtorrent and I moved some installation instructions around. Dependency management for deluge/libtorrent-rasterbar has always been poor for alpine. I was very happy to see a python-only client for deluge, but we were still stuck with libtorrent-rasterbar. Since this is only available in @edge, whenever there's an update it almost immediately complains about not having the right python bindings for it when a different python version was installed (other than from @edge). That is why I am looking forward to aauren's solution since it builds our own python bindings instead of relying on what is available in @edge :smile:.
Is there a reason for packages like boost-python3@edge to be in the auto-update workflow? This potentially changes the python minor version (from 3.7 to 3.8, in this case) and breaks everything.
boost-python3 is a dependency for libtorrent-rasterbar (a dependency for some plugins used by FlexGet). Since we're auto-updating FlexGet (and it's plugin) I figured it to only make sense to update each other dependencies as well, thinking every latest version is compatible with each other - or if not: dependency management will sort that out. About the part where it potentially breaks for every update, yes that is totally the case right now, though it doesn't happen too often and is usually a pretty easy fix. Nonetheless, I'm looking forward to merge a long term solution like building libtorrent-rasterbar in the image and removing the auto-update (see #56).
13k
Oshayr
The auto-update scripts are installing alpine packages that depend on python. If the python version in the image (currently 3.7) is different than the actual current python version in alpine (
python@edge= 3.8.0-r0), it will break everything that was installed in the image with the older python version, including pip.Is there a reason for packages like
boost-python3@edgeto be in the auto-update workflow? This potentially changes the python minor version (from 3.7 to 3.8, in this case) and breaks everything. I see it is already installed in the image.I guess updating the image with the latest python and pushing to the registry should fix it, but whenever a new minor version is released, this will always happen.
Container logs: