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).
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 doesn't seem to have all of the features of 2.20 either. So what happens is that when you just upgrade the
gpodder package, you end up with something you don't necessarily want to use. At least as of now.
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. 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).
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).
Now, if, in between those changes, you already did the upgrade, do one of the following:
- if you want to keep using 3.x: then run
rpm -e gpodder && zypper install gpodder3(as root)
- if you want to go back to 2.x: then run
rpm -e gpodder && zypper install gpodder(as root)
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).
Sorry for the inconvenience.