![]() ![]() On a side note, please wait a couple of hours (after this blog post) before doing so, as our main repository server is only synced to some mirrors after 4 hours (after 1 hour for most though). if you want to go back to 2.x: then run rpm -e gpodder & zypper install gpodder (as root).if you want to keep using 3.x: then run rpm -e gpodder & zypper install gpodder3 (as root).Now, if, in between those changes, you already did the upgrade, do one of the following: If you want to use gpodder 3.0.0, then just install the package gpodder3 instead: zypper or YaST2 will tell you to remove gpodder in order to do so, as you cannot have both installed at the same time (they have file conflicts). What I have done now is to revert the gpodder package at Packman to the 2.xx branch (and upgrade to 2.20 at the same time). Upstream will still maintain the 2.x branch for quite a while, and gradually port features from 2 to 3 and, hence, it actually makes sense to do it differently. So what happens is that when you just upgrade the gpodder package, you end up with something you don't necessarily want to use. From what I see though the sign in does nothing. It doesn't seem to have all of the features of 2.20 either. I love Clementine, and was thrilled to see podcast support. Now, gpodder 3.0.0 does introduce a lot of changes, notably in the UI but also regarding its database format and requires migrating the database from 2 to 3. It took (relative) ages, but it loaded.The gpodder project introduced its new major release 3.0.0 today and, unfortunately, it seems like I didn't pay attention to the complete change announcement, as I just bumped the gpodder package in Packman to 3.0.0 (from 2.18). if you have a new phone if your phone crashed and had to wipe the data) this is a perfect solution. And if you listened to an episode, refreshed your feeds or did anything else on two or more devices, there is no way to ‘merge’ those changes. ![]() But even then it’s annoying, because you manually need to import every time. So it could work if you have multiple Android devices all with the same AntennaPod version installed. AntennaPod’s database cannot be used by any other programme than AntennaPod. We can’t send just one single row (episode), column (favourited status) or cell (favourite status of a particular episode) of the database to a filesharing service.Īs noted before, sync relies on interoperability. But all of the individual episodes (in AntennaPod) are listed in one single big database. Think of like this: It is possible to share photo’s as individual files - if you take a new one on your phone it gets sent over to Nextcloud and picked up on your computer. I don’t think such synchronisation would be technically possible via a filesharing service (especially with how AntennaPod works). ![]() I’m not a developer, but I think it requires a central service with an API (like ). Synchronisation means this: if I favourite an episode on device A, it’ll be favourited also on device B. You can import your back-up to any other AntennaPod installation. make a back-up each day, like WhatsApp does). You can already export a back-up your AntennaPod database to wherever you want (see menu > Storage > Import/Export > Database export): Dropbox, Nextcloud, OneDrive…Īt the moment this is a manual action, but it could be automated (e.g. In the ebook library tool, calibre, it is easy to place your library on Dropbox, and then you can pick it up on multiple computers, for We need to seperate two things: back-up and synchronisation. Backing up your feeds and listens should be able to go somewhere where else. ![]()
0 Comments
Leave a Reply. |