Error: Deluge had a failure Exception: RuntimeError Message: pkg error: - py39-libtorrent-rasterbar : Refusing to fetch artifact and run post_install.sh! Partial plugin destroyed
# Connect to the jail
iocage console Deluge
# Install all needed packages
pkg update
pkg install ca_root_nss
pkg install python39
pkg install py39-pip
pkg install py39-pillow
pkg install libtorrent-rasterbar
pkg install rust
# Prepare the system
pw useradd -n deluge -u 8675309 -m -c "Deluge BitTorrent Client" -s /usr/sbin/nologin -w no
mkdir -p /home/deluge/.config/deluge
chown -R deluge:deluge /home/deluge/
mkdir /Downloads
chown deluge:deluge /Downloads
# Install the packages
pip install --upgrade pip
pip install deluge
# Configure the services
sysrc -f /etc/rc.conf deluged_enable="YES"
sysrc -f /etc/rc.conf deluged_user="deluge"
sysrc -f /etc/rc.conf deluge_web_enable="YES"
sysrc -f /etc/rc.conf deluge_web_user="deluge"
#create service executables
cd /usr/local/etc/
mkdir rc.d
ee deluged
<paste the script from ressource (3) section DELUGED>, save and exit
ee deluge_web
<paste the script from ressource (3) section WEB UI>, save and exit
[COLOR=rgb(20, 20, 20)]chmod +x deluged
chmod +x deluge_web[/COLOR]
# Start the services
service deluged start
service deluge_web start
www.truenas.com
This particular one doesn't really have anything to do with CORE plugins. It's just a plain FreeBSD issue. It's broken on my laptop also running vanilla FreeBSD.Plugins on CORE are a dead feature walking. They've never really been robust, and iX has now thrown in the towel on them:
iXsystems, when are you going to stop pretending that CORE has (usable) plugins?
Plugins are broken. We all know it, and you have no intention of fixing them. Most notably, @Kris Moore has said not to use them, and that they're "more or less deprecated": using plugins on CORE is a path to sadness. The plugin system is more or less deprecated and as you can tell, somewhat...
# Connect to the jail iocage console Deluge # Install all needed packages pkg update pkg install ca_root_nss python39 py39-boost-libs py39-chardet py39-distro py39-mako py39-pillow py39-pip py39-twisted py39-rencode py39-setproctitle py39-xdg b2 libtorrent-rasterbar portdowngrade rust subversion # Prepare the system pw useradd -n deluge -u 8675309 -m -c "Deluge BitTorrent Client" -s /usr/sbin/nologin -w no mkdir -p /home/deluge/.config/deluge chown -R deluge:deluge /home/deluge/ mkdir /Downloads chown deluge:deluge /Downloads # Install the packages pip install --upgrade pip pip install deluge # install working py-libtorrent-rasterbar from ports portsnap fetch update portdowngrade net-p2p/py-libtorrent-rasterbar r569235 cd ./py-libtorrent-rasterbar make install clean # Configure the services sysrc -f /etc/rc.conf deluged_enable="YES" sysrc -f /etc/rc.conf deluged_user="deluge" sysrc -f /etc/rc.conf deluge_web_enable="YES" sysrc -f /etc/rc.conf deluge_web_user="deluge" #create service executables cd /usr/local/etc/ mkdir rc.d ee deluged <paste the script from ressource (3) section DELUGED>, save and exit ee deluge_web <paste the script from ressource (3) section WEB UI>, save and exit chmod +x deluged chmod +x deluge_web # Start the services service deluged start service deluge_web start
portdowngrade net-p2p/py-libtorrent-rasterbar r569235 make: "/usr/share/mk/bsd.port.mk" line 32: Cannot open /usr/ports/Mk/bsd.port.mk make: Fatal errors encountered -- cannot continue[: make:: unexpected operator Usage: /usr/local/sbin/portdowngrade [-r] port-directory|port [revision/date] When called without a revision to restore, svn log is called on the port's directory so that relevant revisions can be identified. Look for lines containing "Update to X.X". You may wish to filter it through less. When called with a port name instead of directory/origin, INDEX is grepped for the correct origins and a list is presented. When called with -r, make describe is called in the restored port and all of the ports that the restored port depended on are also checked out at the same date. This software requires that a ports tree has been fetched and is present in make: stopped in /root.
Yeah, those would be the prepackaged apps. What parallel do you see between plugins on CORE and "basically all of Docker"?
I think that anything that comes pre-packaged is something recommended by iXsystems, you know? Like how it had "Community" and "iX" on CORE. How will iX make recommendations of community-approved Docker packages? If there's a topic about this, I'd like to go there. I can only imagine there are some packages iX won't approve of combining together.
Worked perfectly ! thank you for this solution
