No idea why 0.6.12-r1 is unusable but i'm sure i'll hear why. Anyway, as gcc-3.4 won't compile any of the older trancode versions.. we need 0.6.12 or better. For Proof there is bug #54046. http://bugs.gentoo.org/show_bug.cgi?id=54046
!amd64? ( <media-video/transcode-0.6.12 )
remove the < and its fine
Steps to Reproduce:
2.watch it emerge its dependencies (transcode namely)
old transcode failed compiling as expected.
I expected 0.6.12 to be an alright version to merge, but the ebuild requires any
older version but 0.6.12. The old version fails as in bug #54046
Portage 2.0.51_pre10 (2004.0, gcc-3.4.0, glibc-22.214.171.12440605-r1, 2.6.7-rc3-love2)
System uname: 2.6.7-rc3-love2 i686 Intel(R) Pentium(R) 4 CPU 1.70GHz
Gentoo Base System version 1.4.16
CFLAGS="-O2 -march=pentium4 -ftracer -mfpmath=sse -ffast-math
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3.3/share/config /usr/kde/3/share/config
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -ftracer -mfpmath=sse -ffast-math
FEATURES="autoaddcvs ccache sandbox"
USE="X acpi alsa apache2 apm arts avi berkdb cdr crypt cups encode esd fbcon
flac foomaticdb gdbm gif gimpprint gpm gtk gtk2 imlib java jpeg kde libg++
libwww mad mikmod mmx motif moznocompose moznoirc mpeg mysql ncurses nls nptl
oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl
slang spell sse ssl svga tcpd tiff truetype x86 xml2 xmms xv zlib"
K3b 0.11.11 released
And the fixes keep on coming...
* Some compile fixes for older systems.
* Some little improvements.
* Honor the manual writing app selection for automatic CDRW erasing.
* Properly eject the written media between multiple cd (clone) copies.
* Fixed toc reading for old CD drives which report raw toc data in bcd.
* K3b now refuses to use transcode >= 0.6.12 for dvd ripping. The next major version will be able to use new transcode versions.
amd64 team, do you want to keyword transcode-0.6.11? Otherwise close this bug as invalid, please.
Knew it, this is closed as of now. For gcc-3.4 users just change, this of course will make dvd ripping not work right.. but at least k3b will compile.
!amd64? ( <media-video/transcode-0.6.12 )
!amd64? ( >=media-video/transcode-0.6.12 )
*** Bug 54710 has been marked as a duplicate of this bug. ***
I am on a centrino laptop. I get something similar. It will emerge both with no errors but will keep switching when ever I do emerge -UD world. If 0.6.11 is on it will upgrade to 0.6.12-r1 if 0.6.12-r1 is on it will downgrade to 0.6.11. It gets really annoying. Any reason k3b would be doing this?
same here (centrino laptop also)
*** Bug 56400 has been marked as a duplicate of this bug. ***
So is it the case the k3b can't use transcode 0.6.12? Or just that it can't use 0.6.12 on amd64?
Don: k3b can't use 0.6.12 and <0.6.12 isn't keyworded amd64
Alrighty now I understand. I had misinterpreted the RDEPEND myself. A thousand apologies.
So k3b will support newer transcode in 0.12.x?
>The next major version will be able to use new transcode versions.
Let's hope 0.12 is supposed to be a major version... ;)
*** Bug 56522 has been marked as a duplicate of this bug. ***
k3b works fine with newer version of k3b I would strongly suggest changing it in the ebuild. There is no reason for k3b to depend on an older version of transcode.
I'm closing this bug. Its dead, been dead for awile, and I just forgot about it.
If its dead why hasnt the ebuild been changed yet?
Lee Trager: can you provide a link were the author says that k3b now works also with newer versions of transcode? I don't have much time to search for it. Thanks.
On k3b.org it says a dep is transcode only saying the lowest version you can have is 0.6.0pre5. If you really want me to ill e-mail the author and ask him if k3b works with newer versions but I see no reason to.
k3b.org, news 15.06.2004: K3b now refuses to use transcode >= 0.6.12 for dvd ripping. The next major version will be able to use new transcode versions.
Email the author, if you like to.
I did not look in the news section and it seems you are correct. Sorry.
*** Bug 72301 has been marked as a duplicate of this bug. ***
*** Bug 75252 has been marked as a duplicate of this bug. ***
This bug was closed as fixed for the k3b team:
It's fixed for k3b-0.12, but the fix was not backported to 0.11.x