Package Details: sabnzbd 4.2.3-1

Git Clone URL: https://aur.archlinux.org/sabnzbd.git (read-only, click to copy)
Package Base: sabnzbd
Description: A web-interface based binary newsgrabber with NZB file support
Upstream URL: http://www.sabnzbd.org
Keywords: network usenet
Licenses: GPL
Submitter: esh
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 269
Popularity: 0.30
First Submitted: 2007-11-09 16:21 (UTC)
Last Updated: 2024-03-11 16:27 (UTC)

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 64 Next › Last »

Kr1ss commented on 2020-08-04 18:41 (UTC)

Well, at the time of execution of post_upgrade() the files in /opt/sabnzbd/ which belong to the package should already be removed, since the actual upgrade has already been done. I think, therefore only configuration files should be left there.

I did not actually test that though, and I can't do so atm.

fryfrog commented on 2020-08-04 18:35 (UTC)

@mkomko: The old /opt/sabnzbd folder has everything in it, the configs and the installation. It'd be a hot mess to copy everything, I think.

On a default installation of 3.0.0, all the queue and history files are in the admin folder and it defaults to admin folder. Let me go back and install the last version and see how that is.

mkomko commented on 2020-08-04 18:23 (UTC)

@fryfrog: Couldn't you just move "everything"? That's what I would expect.

fryfrog commented on 2020-08-04 17:35 (UTC)

@tixetsal: Can you poke around in your /opt/sabnzbd and see what file you need to move to /var/lib/sabnzbd/ to get your history to come over? It might be history1.db and some *.sab files looking at my install. I'll play around on my test nas and see if I can figure out what I've missed too. Thanks for reporting!

tixetsal commented on 2020-08-04 16:46 (UTC)

I just upgraded from 3.0.0 to 3.0.0-2 and like others, I had to manually fix my config file location when upgrading from 2.x to 3. I also had to manually move Sabnzbd.py in my instance. I lost all my sab history and had to overwrite the keys sab wanted me to use after install.

Is it normal to have to overwrite the key that gets generated? I'm guessing the loss of history was a problem with the upgrade script from 2.x to 3, but I was surprised to lose my history again after the 3.0.0 to 3.0.0-2 upgrade. ?

fryfrog commented on 2020-08-04 15:19 (UTC)

@Kr1ss: Thanks, fixed!

@nottin: @sumebrius: Because of the typo, it seems like your sabnzbd.ini should have been entirely left behind in /opt.

Kr1ss commented on 2020-08-04 14:51 (UTC) (edited on 2020-08-04 15:27 (UTC) by Kr1ss)

That's probably an error in sabnzbd.install :

mv /opt/sabnzbd/sabnzbd/ini /var/lib/sabnzbd/

should be

mv /opt/sabnzbd/sabnzbd.ini /var/lib/sabnzbd/

if I'm correct. @fryfrog ?

EDIT Thank you for the quick update !

kmacleod commented on 2020-08-04 14:44 (UTC)

There's definitely an issue with the migration from /opt/sabnzbd to /var/lib/sabnzbd. It doesn't look like the post_upgrade function gets executed, or if it does, the logic is somehow wrong... not sure how though. The only thing that seemed to get migrated was the 'logs' directory.

As a workaround I manually executed the steps in post_upgrade, although in my case I had to take the config file from /opt/sabnzbd/sabnzbd.ini.pacsave. After a reboot the service comes up- the only thing missing is the history.

sumebrius commented on 2020-08-04 09:23 (UTC)

For me (maybe the same issue for nottin), the config files in /opt/sabnzbd weren't copied over to /var/lib/sabnzbd

But luckily they still exist in the /opt directory (or at least a .bak version does) - this gets me back up and running:

cp /opt/sabnzbd/sabnzbd.ini.bak ./sabnzbd.ini

nottin commented on 2020-08-04 08:39 (UTC)

The update to 3.0.0 removed all my config files, so had to set up everything from scratch. Not sure if that's the intention. In either case, I should have done a backup just in case so I blame myself.

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 64 Next › Last »