Hi, using snapshot.debian.net I did some tests. These are _my_ resultes; they may need further confirmation!
libsqlite3-0_3.2.1-1_i386.deb: works libsqlite3-0_3.3.8-1.1_i386.deb: works libsqlite3-0_3.4.2-2_i386.deb: works (38 minutes for 100% of 25000 songs, CPU load 40-50%) libsqlite3-0_3.5.6-1_i386.deb: doesn't work (>1 hour for 22%, CPU load 100%) libsqlite3-0_3.5.6-2_i386.deb: doesn't work libsqlite3-0_3.5.6-3_i386.deb: doesn't work libsqlite3-0_3.5.7-2_i386.deb: doesn't work (>4 hours for 37%, CPU load 100%) libsqlite3-0_3.5.8-1_i386.deb: doesn't work I know that libsqlite3-0 3.5.x entered unstable earlier than 2008-03-20, but I _guess_ that I noticed this bug just that day, because this was the first time to completely rescan my collection; until that day I had just refreshed it, so don't take this specific date too serious! I _suggest_: reassign 479068 libsqlite3-0 3.5.6-1 and severity 479068 serious since rookies will simply chuck away Amarok after waiting for hours for their collection to be scanned. @Robert Jacobs: How big is your collection? How long did it take to completely rescan it? Alexander Kurtz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
