Why recent k3b package require so old transcode package. Generaly there is much more recent version in portage. I was able to find a informations about problems with 0.6.12 but what about latest version (0.6.14) ? Reproducible: Always Steps to Reproduce: 1. 2. 3.
I think there is a realy good idea to add a local flag for k3b to do not require so old transcode. I personaly use transcode package not in k3b and I realy need recent version. But now every emerge --update try to install older version of transcode without any good reason. This is realy frustrating.
I have set -encode in my portage.use for k3b to solve the issue temporarly, but indeed this should be fixed. Quite annoying. Luckily I don't use the encoding part of k3b.
not portage.use , but package.use of course as in /etc/portage/package.use
I don't know, why it was masked to a special version. I tried it with any version of transcode. So I removed the version-string.
Lars: I don't know why the bug was assigned to youz, but you can read in Bug 54159 about it. Please revert.
Probably it has been assigned to me, as I take care for the cd-recording tools. So, it's not only an amd64-issue. ppc also relies on ggc-3.4 as the default compiler. Seems we have to include more arches to the transcode list.
Lars, regarding maintenance have a look at metadata.xml. You're expected not to touch other herds/developers ebuilds or to ask before, if you think you need to. amd64 is excluded, because the relevant transcode version is not keyworded for this arch.
Well, I know metadata.xml. And I'm the last who will herd a bug. You can revert the changes, but expect a bug from ppc about this transcode-foo.
>You can revert the changes Eh, you break stuff and I'm good enough to fix it!?!
*** This bug has been marked as a duplicate of 54159 ***
