On 05/09/2013 06:42 AM, ael wrote:
> I too have the same problem after upgrading from 2.201-1 to 3.5.1-1:
> just a dist-upgrade on testing, so much changed at the smae time.
> 
> I found that all my subscriptions had gone, found the note about
> gpodder-migrate2tres in /usr/share/doc/gpodder/ and tried it.
> 
> On the first attempt:
>  "Existing gPodder 3 user data found.
>     To continue, please remove:
> 
>        /ael_elf1/ael/gPodder/Database
>        /ael_elf1/ael/gPodder/Downloads"
> 
> In fact only ~/gPodder/Database existed: I renamed it as Database_bak,
> and ran gpodder-migrate2tres again:
>  " Would carry out the following actions:
> 
>       Move downloads from /ael_elf1/ael/podcasts
>                        to /ael_elf1/ael/gPodder/Downloads
> 
>       Convert database from /ael_elf1/ael/.config/gpodder/database.sqlite
>                          to /ael_elf1/ael/gPodder/Database
> 
> 
> Continue? (Y/n) y
> Done. Have fun with gPodder 3!
> "
> However, gpodder is still reporting no subscriptions. So this seems to 
> fail for me. What had I done wrong or is this a bug?

Hi,

thank you for the bug report - I'm not sure about the database migration
issue, yet.

However, I was curious about whether you saw the NEWS.Debian entry
during the upgrade - that is, you shouldn't have to find the fine in
/usr/share/doc/gpodder on your own.  Is it correct to say that you
didn't see this note during upgrade process?

Thank you,
tony


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to