Hi, Le dimanche 13 janvier 2008 à 01:10 +0100, Toni Mueller a écrit : > > > I experience problems with listen 0.4 and tried to migrate to listen > 0.5, but then experienced this bug. So, I went to see what upstream > has > to say about it, and he simply says that he won't fix the problem > (apparently not even documenting it, other than in the tracker). > You are right, I haven't been notified of this change in the upstream BTS (Mehdi: Track ticket #697)
> This kind of problem, and this kind of problem handling, too, makes me > wonder whether listen is actually suitable for the general public. > It is clear that listen is still a young project, but many people seems to use it successfully on a daily basis. > If you can, please prod him to at least document what would need to be > done to keep one's stuff. Thank you! > Keeping the library after upgrading seems not possible. I think the best thing is to warn the user when upgrading the database - as explained, I think the best is that it is done directly in listen, so that the database are backed up and the user can still downgrade to 0.4 if needed. Mehdi, is there anything you can do for users upgrading from 0.4 to 0.5? 0.4 is still in Debian Etch, and many users will experience this problem while upgrading to Lenny. Cheers, Julien
