Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 165836
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: PPC Porters <ppc@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Denis Dupeyron <calchan@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 165836 depends on: Show dependency tree
Bug 165836 blocks: 157892
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-02-07 21:30 0000
Stabilization of a recent version of kino is required for bug #157892. The
version that would naturally be stabilized is 0.9.2. However, a few things play
in favor of stabilizing 0.9.5 instead:

- 0.9.5 is a bugfix release in the 0.9.X branch, like 0.9.2 was, and as were
0.9.4 and 0.9.3 before that (both did not make it into Portage because of me
being on hiatus). All these versions add nothing new, they only fix bugs in the
code, so it wouldn't make much sense to stabilize 0.9.2 when we know it's
buggy.

- 0.9.5 has been in portage for 17 days only, so it's less that the usual 30,
but still decent. Plus, kino isn't that much of a critical package.

- knowing how much most arch teams are short on staff, asking for a
stabilization of 0.9.2 now and 0.9.5 in less than 2 weeks sounds like a waste
of their time.

The ppc64 arch will probably be an exception for this stabilization, as kino
was only keyworded ~ppc64 recently and for the first time. I'll let you judge,
though, which is why I have put ppc64 in CC. Remove yourself if you want it
too.

So please, arch teams, stabilize kino-0.9.5, or state why you'd rather
stabilize 0.9.2 instead (and go ahead and do so while you're at it).

Thanks in advance.
Denis.

------- Comment #1 From Simon Stelling (RETIRED) 2007-02-07 22:15:48 0000 -------
[ebuild   R   ] media-video/kino-0.9.5  USE="alsa dvdr quicktime vorbis -ffmpeg
-sox" 0 kB 

This works fine if you have ffmpeg installed on your system (note the
-ffmpeg!). However, if you don't have it, it all goes boom:

checking for LIBQUICKTIME... yes
checking for SWSCALE... no
checking for AVCODEC... no
checking libavcodec version (build >4644)... configure: error: FFMPEG is the
new, preferred DV codec. If you must only
                        support libdv, then you must explicitly specify it
using --with-libdv-only.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/media-video/kino-0.9.5/work/kino-0.9.5/config.log

!!! ERROR: media-video/kino-0.9.5 failed.
Call stack:
  ebuild.sh, line 1611:   Called dyn_compile
  ebuild.sh, line 968:   Called qa_call 'src_compile'
  environment, line 1279:   Called src_compile
  kino-0.9.5.ebuild, line 50:   Called econf '--disable-dependency-tracking'
'--disable-debug' '--enable-quicktime' '--without-avcodec' '--without-dv1394'
  ebuild.sh, line 574:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if
relevant.
!!! A complete build log is located at
'/var/tmp/portage/media-video/kino-0.9.5/temp/build.log'.

Also, if you have ffmpeg installed but merge kino with USE=-ffmpeg, it still
uses ffmpeg to convert movies you load that are not DV, so you might want to
just make the dep unconditional.

Since 0.9.2 works in this case, I marked that one stable on amd64 for now.

------- Comment #2 From Denis Dupeyron 2007-02-07 22:56:29 0000 -------
(In reply to comment #1)
> Also, if you have ffmpeg installed but merge kino with USE=-ffmpeg, it still
> uses ffmpeg to convert movies you load that are not DV, so you might want to
> just make the dep unconditional.

Good idea, I fixed it. Thanks.

Denis.

------- Comment #3 From Gustavo Zacarias (RETIRED) 2007-02-08 14:08:25 0000 -------
sparc stable.

------- Comment #4 From Christian Faulhammer 2007-02-08 17:39:40 0000 -------
x86 stable

------- Comment #5 From Markus Rothe 2007-02-13 10:56:23 0000 -------
ppc64 stable

------- Comment #6 From Simon Stelling (RETIRED) 2007-02-13 19:47:48 0000 -------
re-adding amd64 since according to Denis the problem mentioned in comment #1 is
fixed now.

------- Comment #7 From Simon Stelling (RETIRED) 2007-02-18 15:59:11 0000 -------
0.9.5 marked stable on amd64

------- Comment #8 From Alessandro Arrichiello 2007-03-13 23:08:20 0000 -------
I think there is a bug in ppc
Hi this is my emerge --info

whiterabbit  # emerge --info
Portage 2.1.2-r9 (default-linux/ppc/ppc32/2006.1, gcc-4.1.1, 
glibc-2.4-r3, 2.6.19-gentoo-r5 ppc)
=================================================================
System uname: 2.6.19-gentoo-r5 ppc 750CXe
Gentoo Base System version 1.12.1
Timestamp of tree: Wed, 07 Mar 2007 20:00:01 +0000
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 
1.10
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r4
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CBUILD="powerpc-unknown-linux-gnu"
CFLAGS="-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config 
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo 
/etc/texmf/web2c"
CXXFLAGS="-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ 
http://gd.tuwien.ac.at/opsys/linux/gentoo/ http://gentoo.tiscali.nl/ "
LINGUAS="en it"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times 
--compress --force --whole-file --delete --delete-after --stats 
--timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa apache2 arts berkdb bitmap-fonts bonobo cdr cli cracklib 
crypt cups dri dvd eds emboss encode esd firefox fortran gdbm gif gnome 
gpm gstreamer gtk gtkhtml iconv ipv6 isdnlog jpeg kde ldap libg++ libwww 
mad midi mikmod mozilla mp3 mpeg ncurses nls nptl nptlonly ogg opengl 
pam pcre pdf perl png ppc pppd python qt3 qt4 quicktime readline 
reflection ruby sdl session spell spl ssl tcpd truetype truetype-fonts 
type1-fonts unicode vorbis xml xorg xv zlib" ALSA_CARDS="aoa 
aoa-fabric-layout aoa-onyx aoa-soundbus aoa-soundbus-i2s aoa-tas 
aoa-toonie powermac usb-audio via82xx" ALSA_PCM_PLUGINS="adpcm alaw asym 
copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa 
lfloat linear meter mulaw multi null plug rate route share shm softvol" 
ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux" 
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb 
ncurses text" LINGUAS="en it" USERLAND="GNU" VIDEO_CARDS="rage128"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, 
LDFLAGS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

I have this error when try to execute KINO:
whiterabbit  # kino
> help language code en

Kino experienced a segmentation fault.
Dumping stack from the offending thread

Obtained 10 stack frames.
kino [0x1002bfd4]
[0x100374]
[(nil)]
/usr/lib/libgthread-1.2.so.0 [0xfec6fec]
/usr/lib/libglib-2.0.so.0(g_slice_alloc+0x428) [0xf317efc]
/usr/lib/libglib-2.0.so.0(g_hash_table_new_full+0x4c) [0xf2ed7b4]
/usr/lib/libglib-2.0.so.0(g_intern_static_string+0x18c) [0xf2e5ef8]
/usr/lib/libgobject-2.0.so.0(g_type_init_with_debug_flags+0x174) 
[0xf3db624]
/usr/lib/libgdk-x11-2.0.so.0(gdk_pre_parse_libgtk_only+0x5c) [0xf8b9b84]
/usr/lib/libgtk-x11-2.0.so.0 [0xfac47a0]

Done dumping - exiting.


Let me know..

------- Comment #9 From Denis Dupeyron 2007-03-25 10:03:08 0000 -------
(In reply to comment #8)
> I think there is a bug in ppc
> Hi this is my emerge --info
[...]
> Let me know..

I have just committed a fix that looks like it would solve this issue. Please
try it, and tell us.

Denis.

------- Comment #10 From Tobias Scherbaum 2007-03-25 10:48:14 0000 -------
ppc stable

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug