Move sab/sick from Windows to Linux

[jwhitener]

I've been having issues with Sab not being able to write long file names to Windows 10. I tried changing the special settings in Sab to limit folder path length to 40, 65, etc.. but it isn't helping. See http://wiki.sabnzbd.org/known-issues#toc3

I have a new computer coming from system76 that is Ubuntu. If I want to migrate the Sab settings and download show history from Windows to Linux, I assume I'll copy the C:\Users\me\AppData\Local\sabnzbd\sabnzbd.ini to /home/me/.sab.../sabnzbd.ini. Is it also easy to copy whatever contains the downloaded show history? Where is that stored? If it is at all difficult/buggy, I'll probably be fine just copying the ini over.

Also, I assume this community has equal experience with Sickbeard. http://sickbeard.com/forums/viewtopic.php?f=3&t=1147

update tv_shows set location = replace(location, 'old path', 'new path');

Do I need to install some variant of sqllite to run sql commands against the sickeard db file? Is there any easier way to migrate from one path/os to another with sickbeard?

[shypike]

Long names on Windows: please try release 0.8.0Beta1 (see Announcements).

Just copy the c:\Users\USER\AppData\local\sabnzbd\admin content to the equivalent place in Linux (~/.sabnzbd/admin).

[jwhitener]

Thank you for the info about another area to download sab.

Would you mind linking the newer releases to the main site at http://sabnzbd.org/ ? (with a short description of the fixes so google can index the content of the page) As a casual user, I wasn't aware that any newer versions where available. It certainly is hard to google answers when the only notice about a fix is in a sub section of a forum, Google can't index that very well.

I know (as a dev in another related field) that pushing new info to users about enhancements is tough/tricky, but I find that I spend a lot of time trying to debug sab/sick/rage/sonarr issues. It seems like there should be a cleaner method of finding/receiving answers about global issues than forum searches.

[shypike]

We keep the Alpha and Beta releases low profile, because we know they still contain issues.
(Probably just minor ones in the case of Beta1)
It is possible to be automatically notified of test releases, if you set that option in Config->Switches.

[jwhitener]

We keep the Alpha and Beta releases low profile, because we know they still contain issues.
(Probably just minor ones in the case of Beta1)
It is possible to be automatically notified of test releases, if you set that option in Config->Switches.

Thank you.