You are not logged in.
Pages: 1
Recently there were a few threads about corrupted image alerts for libgpod being kicked out by packman during an -Syu. At the same time, I read a bug and a post that indicated that perhaps 0.4.0 was meant for testing, not extra. At this point, as far as I can tell, the libgpod in extra is 0.4.0 - even the PKGBUILD I get when refreshing ABS is for 0.4.0. 0.4.0 causes massive corruption of my iPod database, essentially rendering it useless. 0.3.2, which I recently downgraded to, does not. My question, which I realise has been asked in sort of a roundabout way is this: which version of libgpod should be in extra? I can NoUpgrade libgpod for a while if we actually have moved to 0.4.0, but I have to admit to being confused. I didn't really want to file a bug just to ask a (stupid?) question.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
Yes, libgpod 0.4.0 going to extra was my mistake. I had downgraded it and put 0.4.0 in testing as it should have been. It now appears that 0.4.0 has been tagged 'CURRENT' and 0.4.0 has been moved to extra. cvs, or course, doesn't keep track of who did that, but I'd ask Blaasvis about it.
I had only upgraded libgpod because gtkpod needed it, and he was away at the time.
Offline
Thanks for the reply - I meant to post this a while ago. With amarok 1.4.4 the new libgpod 0.4.0 works very well. Again, thanks for the reply, and thanks for all your hard work on Arch!
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
Pages: 1