2.2 -> 2.2.1 causes track loss in local collection

[Colin Kern]

I experienced this same problem when I built Amarok from Git about a
week before 2.2.1 was released.  I went back to using 2.2 and restored
my database from a backup I made.  Now that my distro has updated its
package to 2.2.1, I haven't rescanned my collection yet.  After the
upgrade, though, most of my songs show 0:00 as the length, and other's
incorrectly show lengths between 15 and 17 minutes.  A rescan would
probably fix this, but I don't want to to lose tracks.

Colin

On Mon, Dec 7, 2009 at 12:58 PM, Christian Kreibich <christian at whoop.org> wrote:
> On Mon, 2009-11-30 at 13:05 -0800, Christian Kreibich wrote:
>> Would an error in this query explain a failing
>> collection re-scan?
>
> I take it the answer is no.
>
> --
> Cheers,
> Christian
>
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>