I had a similar problem some months ago. I can't remember all the details, but i think it had to do something with avi. I changed the useflags of transcode until the emerge of the latest version finished without any error. Try to unmask the latest version of transcode and emerge it.
Good luck. /Uwe Harry Putnam wrote: > I'm trying to install k3b. One of its dependancies is transcode. The > emerge stopped at transcode with specific errors, When checking > bugzilla I see this is a known problem. > > I'm not sure how to proceed from here. For example: If I have emerge > install a version that doesn't appear in the bug reports (several > versions back) how would that effect the install of k3b. Wouldn't it > still want to install the problem version? > > Can I do something in /etc/portage/package.provided that will allow > the old build to stand? I'm familiar with how it works on backages > that are a version or two ahead. But somewhere, when I read up on > package.provided it said this would work as long as the package listed > there was a newer version. > > I currently have: > cat /etc/portage/package.provided > rsnapshot-1.2.2 > bacula-1.48.5 > > In both cases those are newer than anything in portage (even masked). > > I'd rather not build transcode by hand because the emerge of k3b > showed a complicated string of deps and it seems like I could get in a > pretty good mess going outside of portage for some pieces of it. > > Can someone outline a proceedure for a case like this? >
begin:vcard fn:Uwe Klosa n:Klosa;Uwe org:Uppsala University;Electronic Publishing Centre adr:;;;Uppsala;;75120;Sweden email;internet:[EMAIL PROTECTED] tel;work:+46 (0)18 471 7658 url:http://publications.uu.se/epcentre version:2.1 end:vcard
