Bug#754435: libavcodec55: vlc segfaults with error 4 in libavcodec.so
Am 11.07.2014, 04:12 Uhr, schrieb Reinhard Tartler siret...@gmail.com: (...) We need more information to find out the source of this problem. Please provide a full backtrace as described at https://wiki.debian.org/HowToGetABacktrace Please see attached backtraces. Please replace this package with the package found in debian. It may or may not be the source of this problem. Oops, last leftover of my deb-multimedia adventures. aptitude log: [DOWNGRADE] libmp3lame0:amd64 1:3.99.5-dmo2 - 3.99.5+repack1-3 [INSTALLIEREN] libav-dbg:amd64 [INSTALLIEREN] vlc-dbg:amd64 Regards, Tim(gdb) bt #0 ff_emu_edge_vfix3_mmx.body_loop () at /build/libav-KCSjC9/libav-10.2/libavcodec/x86/videodsp.asm:333 #1 0x7fffd147cee8 in emulated_edge_mc (h_extend_var=optimized out, hfix_tbl=optimized out, v_extend_var=optimized out, vfix_tbl=optimized out, h=optimized out, w=32128, src_y=optimized out, src_x=optimized out, block_h=optimized out, block_w=optimized out, src_stride=optimized out, dst_stride=optimized out, src=0x7fffc29d5ffd \200\200\200, dst=optimized out) at /build/libav-KCSjC9/libav-10.2/libavcodec/x86/videodsp_init.c:172 #2 emulated_edge_mc_sse2 (buf=0x7fffbc0689b0 \200\200\200\200\200\177\177\200\200, src=0x7fffc29d5ffd \200\200\200, buf_stride=304, src_stride=304, block_w=0, block_h=1, src_x=304, src_y=32128, w=304, h=128) at /build/libav-KCSjC9/libav-10.2/libavcodec/x86/videodsp_init.c:234 #3 0x7fffd12e3967 in mpeg_motion_internal (mb_y=15, is_mpeg12=0, h=16, motion_y=4, motion_x=22, pix_op=0x7fffcd50dc40, ref_picture=optimized out, field_select=0, bottom_field=0, field_based=0, dest_cr=0x7fffbc072320 \200\201\201\200\200\177\177\200, dest_cb=0x7fffbc06fd20 \200\200\177\177\177\177\177~, dest_y=0x7fffbc06d720 BA?;41,'\\036\032\030\026\027\026, s=0x7fffcd50b8e0) at /build/libav-KCSjC9/libav-10.2/libavcodec/mpegvideo_motion.c:332 #4 mpeg_motion (s=0x7fffcd50b8e0, dest_y=0x7fffbc06d720 BA?;41,'\\036\032\030\026\027\026, dest_cb=0x7fffbc06fd20 \200\200\177\177\177\177\177~, dest_cr=0x7fffbc072320 \200\201\201\200\200\177\177\200, field_select=0, ref_picture=optimized out, pix_op=0x7fffcd50dc40, motion_x=22, motion_y=4, h=16, mb_y=15) at /build/libav-KCSjC9/libav-10.2/libavcodec/mpegvideo_motion.c:383 #5 0x7fffd12e5386 in MPV_motion_internal (is_mpeg12=optimized out, qpix_op=optimized out, pix_op=optimized out, ref_picture=optimized out, dir=optimized out, dest_cr=optimized out, dest_cb=optimized out, dest_y=optimized out, s=optimized out) at /build/libav-KCSjC9/libav-10.2/libavcodec/mpegvideo_motion.c:905 #6 ff_MPV_motion (s=0x7fffcd50b8e0, dest_y=0x7fffbc06d720 BA?;41,'\\036\032\030\026\027\026, dest_cb=0x7fffbc06fd20 \200\200\177\177\177\177\177~, dest_cr=0x7fffbc072320 \200\201\201\200\200\177\177\200, dir=optimized out, ref_picture=optimized out, pix_op=0x7fffcd50dc40, qpix_op=0x7fffcd50d7a8) at /build/libav-KCSjC9/libav-10.2/libavcodec/mpegvideo_motion.c:976 #7 0x7fffd12d3091 in MPV_decode_mb_internal (is_mpeg12=optimized out, block=optimized out, s=optimized out) at /build/libav-KCSjC9/libav-10.2/libavcodec/mpegvideo.c:2181 #8 ff_MPV_decode_mb (s=0x7fffcd50b8e0, block=0x7fffbc019d20) at /build/libav-KCSjC9/libav-10.2/libavcodec/mpegvideo.c:2310 #9 0x7fffd1153af5 in decode_slice (s=s@entry=0x7fffcd50b8e0) at /build/libav-KCSjC9/libav-10.2/libavcodec/h263dec.c:238 #10 0x7fffd11543b2 in ff_h263_decode_frame (avctx=0x7fffcd50afe0, data=0x7fffcd50b460, got_frame=0x7fffcb951d2c, avpkt=optimized out) at /build/libav-KCSjC9/libav-10.2/libavcodec/h263dec.c:568 #11 0x7fffd137b1cb in avcodec_decode_video2 (avctx=avctx@entry=0x7fffcd50afe0, picture=0x7fffcd50b460, got_picture_ptr=got_picture_ptr@entry=0x7fffcb951d2c, avpkt=avpkt@entry=0x7fffcb951d30) at /build/libav-KCSjC9/libav-10.2/libavcodec/utils.c:1480 #12 0x7fffd1ea6d9b in DecodeVideo (p_dec=optimized out, pp_block=optimized out) at avcodec/video.c:610 #13 0x77148c00 in DecoderDecodeVideo (p_dec=p_dec@entry=0x7fffcd4f9a88, p_block=p_block@entry=0x7fffcd5125c0) at input/decoder.c:1479 #14 0x7714a141 in DecoderProcessVideo (b_flush=false, p_block=0x7fffcd5125c0, p_dec=optimized out) at input/decoder.c:1841 #15 DecoderProcess (p_block=optimized out, p_dec=optimized out) at input/decoder.c:2014 #16 DecoderThread (p_data=0x7fffcd4f9a88) at input/decoder.c:936 #17 0x779ac0ca in start_thread (arg=0x7fffcb952700) at pthread_create.c:309 #18 0x774dd06d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 (gdb) bt full #0 ff_emu_edge_vfix3_mmx.body_loop () at /build/libav-KCSjC9/libav-10.2/libavcodec/x86/videodsp.asm:333 No locals. #1 0x7fffd147cee8 in emulated_edge_mc (h_extend_var=optimized out, hfix_tbl=optimized out, v_extend_var=optimized out, vfix_tbl=optimized out, h=optimized out, w=32128, src_y=optimized out, src_x=optimized out, block_h=optimized out, block_w=optimized out, src_stride=optimized out, dst_stride=optimized out,
Bug#754459: ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22)
Package: xbmc Version: 2:13.1~rc1+dfsg1-1 Severity: normal Dear Maintainer, see the log: 14:43:24 T:140551195269440 NOTICE: DVDPlayer: Opening: http://109.87.115.25:/udp/238.0.0.64:1234 14:43:24 T:140551195269440 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED 14:43:24 T:140548719478528 NOTICE: Thread DVDPlayer start, auto delete: false 14:43:24 T:140548719478528 NOTICE: Creating InputStream 14:43:24 T:140548719478528 ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22) 14:43:24 T:140548719478528 NOTICE: CCurlFile::FillBuffer - Reconnect, (re)try 1 14:43:24 T:140548719478528 ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22) 14:43:24 T:140548719478528 ERROR: CCurlFile::CReadState::Connect, didn't get any data from stream. 14:43:24 T:140548719478528 ERROR: Open - failed to open source http://109.87.115.25:/udp/238.0.0.64:1234 14:43:24 T:140548719478528 ERROR: CDVDPlayer::OpenInputStream - error opening [http://109.87.115.25:/udp/238.0.0.64:1234] This is very strange, because the same URL can play vlc. And this is common problem. There are many other URL like this (http://IP:PORT/udp/IP:PORT) that vlc can play, but xbmc can't. Not all of them, but too many. And this is not stable situation: it is changing in the time. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xbmc depends on: ii fonts-dejavu-core 2.34-1 ii fonts-roboto 1:4.3-3 ii libjs-iscroll 5.1.1+dfsg1-2 ii libjs-jquery 1.7.2+dfsg-3 ii mesa-utils 8.2.0-1 ii python-imaging 2.4.0-2 pn python:any none ii ttf-dejavu-core2.34-1 ii x11-utils 7.7+1 ii xbmc-bin 2:13.1~rc1+dfsg1-1 xbmc recommends no packages. xbmc suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#754096: xbmc: Working ...
On Wed, Jul 09, 2014 at 12:58:41PM +0200, Bálint Réczey wrote: The hangs were solved by installing xbmc-pvr-iptvsimple on my system. Could you please give it a try? This debian package was not installed, but this add-on was enabled. So I've deinstalled it, and then have installed debian package, but nothing changes. Note please, that this depend on time. If You wait few seconds while it Working ..., and then hit x it may not hang. To get it hang You should wait long enough. * ### Vladimir Stavrinov ### vstavri...@gmail.com * ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#754435: libavcodec55: vlc segfaults with error 4 in libavcodec.so
Control: tag -1 -moreinfo +upstream Control: severity -1 normal Control: retitle -1 libavcodec55.so crashes vlc while decoding unspecified mpeg media On Fri, Jul 11, 2014 at 6:37 AM, Tim Wiederhake tw...@gmx.net wrote: Am 11.07.2014, 04:12 Uhr, schrieb Reinhard Tartler siret...@gmail.com: (...) We need more information to find out the source of this problem. Please provide a full backtrace as described at https://wiki.debian.org/HowToGetABacktrace Please see attached backtraces. Thanks. The trace indeed looks like a genuine crash during mpeg decoding. This bug needs to be reported upstream. Would you mind to follow the bug crash reporting guidelines as https://libav.org/bugreports.html, and report back the bugzilla number here? Cheers, -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Re: Bug#754435: libavcodec55: vlc segfaults with error 4 in libavcodec.so
Processing control commands: tag -1 -moreinfo +upstream Bug #754435 [libavcodec55] libavcodec55: vlc segfaults with error 4 in libavcodec.so Removed tag(s) moreinfo. Bug #754435 [libavcodec55] libavcodec55: vlc segfaults with error 4 in libavcodec.so Added tag(s) upstream. severity -1 normal Bug #754435 [libavcodec55] libavcodec55: vlc segfaults with error 4 in libavcodec.so Severity set to 'normal' from 'important' retitle -1 libavcodec55.so crashes vlc while decoding Bug #754435 [libavcodec55] libavcodec55: vlc segfaults with error 4 in libavcodec.so Changed Bug title to 'libavcodec55.so crashes vlc while decoding' from 'libavcodec55: vlc segfaults with error 4 in libavcodec.so' -- 754435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#752168: marked as done (x264: FTBFS on arm*)
Your message dated Fri, 11 Jul 2014 12:36:34 + with message-id e1x5a42-0002ly...@franck.debian.org and subject line Bug#752168: fixed in x264 2:0.142.2431+gita5831aa-1 has caused the Debian Bug report #752168, regarding x264: FTBFS on arm* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: x264 Version: 2:0.142.2412+gitd7e6896-1 Severity: serious Justification: fails to build from source (but built successfully in the past) x264 failed to build on armel and armhf: | gcc -Wshadow -O3 -fno-fast-math -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -I. -I. -fno-aggressive-loop-optimizations -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -fPIC -fomit-frame-pointer -fno-tree-vectorize -D_FORTIFY_SOURCE=2 -c -o common/arm/predict-c.o common/arm/predict-c.c | common/arm/predict-c.c:36:6: error: conflicting types for 'x264_predict_8x8c_dc_neon' | void x264_predict_8x8c_dc_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:32:6: note: previous declaration of 'x264_predict_8x8c_dc_neon' was here | void x264_predict_8x8c_dc_neon( pixel *src ); | ^ | common/arm/predict-c.c:39:6: error: conflicting types for 'x264_predict_8x8c_h_neon' | void x264_predict_8x8c_h_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:33:6: note: previous declaration of 'x264_predict_8x8c_h_neon' was here | void x264_predict_8x8c_h_neon( pixel *src ); | ^ | common/arm/predict-c.c:40:6: error: conflicting types for 'x264_predict_8x8c_v_neon' | void x264_predict_8x8c_v_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:34:6: note: previous declaration of 'x264_predict_8x8c_v_neon' was here | void x264_predict_8x8c_v_neon( pixel *src ); | ^ | common/arm/predict-c.c:43:6: error: conflicting types for 'x264_predict_8x8_dc_neon' | void x264_predict_8x8_dc_neon( uint8_t *src, uint8_t edge[36] ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:31:6: note: previous declaration of 'x264_predict_8x8_dc_neon' was here | void x264_predict_8x8_dc_neon( pixel *src, pixel edge[36] ); | ^ | common/arm/predict-c.c:48:6: error: conflicting types for 'x264_predict_8x8_v_neon' | void x264_predict_8x8_v_neon( uint8_t *src, uint8_t edge[36] ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:29:6: note: previous declaration of 'x264_predict_8x8_v_neon' was here | void x264_predict_8x8_v_neon( pixel *src, pixel edge[36] ); | ^ | common/arm/predict-c.c:49:6: error: conflicting types for 'x264_predict_8x8_h_neon' | void x264_predict_8x8_h_neon( uint8_t *src, uint8_t edge[36] ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:30:6: note: previous declaration of 'x264_predict_8x8_h_neon' was here | void x264_predict_8x8_h_neon( pixel *src, pixel edge[36] ); | ^ | common/arm/predict-c.c:53:6: error: conflicting types for 'x264_predict_16x16_dc_neon' | void x264_predict_16x16_dc_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:37:6: note: previous declaration of 'x264_predict_16x16_dc_neon' was here | void x264_predict_16x16_dc_neon( pixel *src ); | ^ | common/arm/predict-c.c:56:6: error: conflicting types for 'x264_predict_16x16_h_neon' | void x264_predict_16x16_h_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:36:6: note: previous declaration of 'x264_predict_16x16_h_neon' was here | void x264_predict_16x16_h_neon( pixel *src ); | ^ | common/arm/predict-c.c:57:6: error: conflicting types for 'x264_predict_16x16_v_neon' | void x264_predict_16x16_v_neon( uint8_t *src ); | ^ | In file included from common/arm/predict-c.c:27:0: | common/arm/predict.h:35:6: note: previous declaration of 'x264_predict_16x16_v_neon' was here | void x264_predict_16x16_v_neon( pixel *src ); | ^ | make[2]: *** [common/arm/predict-c.o] Error 1 For the full log see https://buildd.debian.org/status/fetch.php?pkg=x264arch=armelver=2:0.142.2412+gitd7e6896-1stamp=1402770990 Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: x264 Source-Version:
Bug#754469: xbmc: play next
Package: xbmc Version: 2:13.1~rc1+dfsg1-1 Severity: normal Dear Maintainer, The problem exists when some items in the playlist don't works. When play next feature is enabled, it really try to play next if current item fail, but first it stops there and don't continues next, and second it don't moves cursor, so You don't know what item on the list it try or plays. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xbmc depends on: ii fonts-dejavu-core 2.34-1 ii fonts-roboto 1:4.3-3 ii libjs-iscroll 5.1.1+dfsg1-2 ii libjs-jquery 1.7.2+dfsg-3 ii mesa-utils 8.2.0-1 ii python-imaging 2.4.0-2 pn python:any none ii ttf-dejavu-core2.34-1 ii x11-utils 7.7+1 ii xbmc-bin 2:13.1~rc1+dfsg1-1 xbmc recommends no packages. xbmc suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 architecture list
On Fri, Jul 11, 2014 at 3:06 AM, Jonas Smedegaard d...@jones.dk wrote: [resent - to list this time, as intended] Quoting Felipe Sateler (2014-07-10 17:12:34) Ardour3 takes a long time to build. The mips and mipsel buildds killed the build after 150 and 300 minutes of inactivity. I managed to build ardour3 in the mipsel porterbox, so I don't think ardour has any real problem on mipsel. I was wondering if maybe we should restrict ardour to the architectures it is likely to be used. Otherwise we might need to ask that ardour be retried until it manages to print output fast enough to avoid getting killed. What do you think? I think we should not decide based on where it is likely to be used, but here is is possible to use. In an ideal world, I would agree. But manpower is very short in the team, so prioritizing is of the essence. Spending time on ensuring builds on an architecture (close to) nobody uses is not a very good use of it. But, if you have a suggestion to ensure the build doesn't time out, I'm all ears :) -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 715590
Processing commands for cont...@bugs.debian.org: tags 715590 + pending Bug #715590 [m2vrequantiser] [Mayhem] Bug report on m2vrequantiser: M2VRequantiser crashes with exit status 139 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 715590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 715590
Processing commands for cont...@bugs.debian.org: tags 715590 + pending Bug #715590 [m2vrequantiser] [Mayhem] Bug report on m2vrequantiser: M2VRequantiser crashes with exit status 139 Ignoring request to alter tags of bug #715590 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 715590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 architecture list
Quoting Felipe Sateler (2014-07-11 15:55:34) On Fri, Jul 11, 2014 at 3:06 AM, Jonas Smedegaard d...@jones.dk wrote: Quoting Felipe Sateler (2014-07-10 17:12:34) Ardour3 takes a long time to build. The mips and mipsel buildds killed the build after 150 and 300 minutes of inactivity. I managed to build ardour3 in the mipsel porterbox, so I don't think ardour has any real problem on mipsel. I was wondering if maybe we should restrict ardour to the architectures it is likely to be used. Otherwise we might need to ask that ardour be retried until it manages to print output fast enough to avoid getting killed. What do you think? I think we should not decide based on where it is likely to be used, but here is is possible to use. In an ideal world, I would agree. But manpower is very short in the team, so prioritizing is of the essence. Spending time on ensuring builds on an architecture (close to) nobody uses is not a very good use of it. But, if you have a suggestion to ensure the build doesn't time out, I'm all ears :) Maybe I failed to understand, but seems to me that asking th ardour build to be retired until not myeriously hanging on porter boxes is not burdening man power (of the Multimedia team) but instead putting the burden on the porting team where it belongs. I find it wrong of us to try second-guess interests of Debian users. Particularly, looking at popularity contest is wrong here, IMO, as that a) is generally inaccurate (contributions to it is voluntary and only reflects internet-connected hosts) and b) tells only about past usage patterns, not interests-if-available for next release of Debian and the hardware that will then be supported. ...but to address your concrete question: I do not have ideas how to reliably avoid builds hanging, but if not already tried I do have a suggestion for that: Ask the porters, as it seems you have narrowed the issue to be architecture-dependent (if not, then so much more reason against treating it as such!). - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processing of m2vrequantiser_1.1-2_amd64.changes
m2vrequantiser_1.1-2_amd64.changes uploaded successfully to localhost along with the files: m2vrequantiser_1.1-2_amd64.deb m2vrequantiser_1.1-2.dsc m2vrequantiser_1.1-2.debian.tar.gz Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: notfound 662857 in phasex/0.12.0+m1-6
Processing commands for cont...@bugs.debian.org: notfound 662857 phasex/0.12.0+m1-6 Bug #662857 [phasex] phasex does not start, complaining about kernel modules No longer marked as found in versions phasex/0.12.0+m1-6. thanks Stopping processing here. Please contact me if you need assistance. -- 662857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#662857: marked as done (phasex does not start, complaining about kernel modules)
Your message dated Fri, 11 Jul 2014 16:00:47 +0100 with message-id camhuwowzo+p6j52ffe8arxcbb6-qdwrfii+k1qodesya729...@mail.gmail.com and subject line Closing #662857 has caused the Debian Bug report #662857, regarding phasex does not start, complaining about kernel modules to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 662857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: phasex Version: 0.12.0+m1-6 Severity: normal Dear Maintainer, When I start phasex: phasex Using client name phasex Unhandled ALSA MIDI error. Please make sure that the 'snd_seq_midi' and 'snd_seq_midi_event' kernel modules are loaded and functioning properly. PHASEX Exiting... I tried to load the modules using modprobe, but no improvements -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages phasex depends on: ii libasound21.0.25-2 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-26 ii libcairo2 1.10.2-6.2 ii libfontconfig12.8.0-3.1 ii libfreetype6 2.4.8-1 ii libgdk-pixbuf2.0-02.24.1-1 ii libglib2.0-0 2.30.2-6 ii libgtk2.0-0 2.24.10-1 ii libjack0 [libjack-0.116] 1:0.121.3+20120222git81e8f031-1 ii libpango1.0-0 1.29.4-2 ii libsamplerate00.1.8-3 ii libx11-6 2:1.4.4-4 Versions of packages phasex recommends: ii jackd 5 Versions of packages phasex suggests: ii jack-keyboard 2.6-2 ii vkeybd 1:0.1.18d-2 -- no debconf information ---End Message--- ---BeginMessage--- Version: 0.12.0+m1-6 As said by the submitter, this is not a bug of phasex. Closing. -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A---End Message--- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: notfound 662857 in 0.12.0~pre1-3
Processing commands for cont...@bugs.debian.org:
notfound 662857 0.12.0~pre1-3
Bug #662857 {Done: Alessio Treglia ales...@debian.org} [phasex] phasex does
not start, complaining about kernel modules
Ignoring request to alter found versions of bug #662857 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
662857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 730233
Processing commands for cont...@bugs.debian.org: tags 730233 + upstream Bug #730233 [smtube] smtube: Please honor the $http_proxy environment variable Ignoring request to alter tags of bug #730233 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 730233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 architecture list
On Fri, Jul 11, 2014 at 10:40 AM, Jonas Smedegaard d...@jones.dk wrote: Quoting Felipe Sateler (2014-07-11 15:55:34) On Fri, Jul 11, 2014 at 3:06 AM, Jonas Smedegaard d...@jones.dk wrote: Quoting Felipe Sateler (2014-07-10 17:12:34) Ardour3 takes a long time to build. The mips and mipsel buildds killed the build after 150 and 300 minutes of inactivity. I managed to build ardour3 in the mipsel porterbox, so I don't think ardour has any real problem on mipsel. I was wondering if maybe we should restrict ardour to the architectures it is likely to be used. Otherwise we might need to ask that ardour be retried until it manages to print output fast enough to avoid getting killed. What do you think? I think we should not decide based on where it is likely to be used, but here is is possible to use. In an ideal world, I would agree. But manpower is very short in the team, so prioritizing is of the essence. Spending time on ensuring builds on an architecture (close to) nobody uses is not a very good use of it. But, if you have a suggestion to ensure the build doesn't time out, I'm all ears :) Maybe I failed to understand, but seems to me that asking th ardour build to be retired until not myeriously hanging on porter boxes is not burdening man power (of the Multimedia team) but instead putting the burden on the porting team where it belongs. The burden is on us due to having to track down a missing build. But most importantly it is a burden on our users because until the mipsel build is up again, ardour3 cannot migrate to testing. I find it wrong of us to try second-guess interests of Debian users. Particularly, looking at popularity contest is wrong here, IMO, as that a) is generally inaccurate (contributions to it is voluntary and only reflects internet-connected hosts) and b) tells only about past usage patterns, not interests-if-available for next release of Debian and the hardware that will then be supported. In general, I agree. I would love to be able to provide all packages in all archs. But it may not be feasible due to time constraints. ...but to address your concrete question: I do not have ideas how to reliably avoid builds hanging, but if not already tried I do have a suggestion for that: Ask the porters, as it seems you have narrowed the issue to be architecture-dependent (if not, then so much more reason against treating it as such!). The problem, as far as I can see, is that the build takes too long. I built ardour3 in eder (a mipsel porterbox) successfully, and it took over 12 hours! If you look at the log I linked to, the build daemon killed the build after some time without activity. -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processing of smtube_2.1-2_amd64.changes
smtube_2.1-2_amd64.changes uploaded successfully to localhost along with the files: smtube_2.1-2_amd64.deb smtube_2.1-2.dsc smtube_2.1-2.debian.tar.gz Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 architecture list
On Fri, Jul 11, 2014 at 11:19 AM, Felipe Sateler fsate...@debian.org wrote: On Fri, Jul 11, 2014 at 10:40 AM, Jonas Smedegaard d...@jones.dk wrote: Quoting Felipe Sateler (2014-07-11 15:55:34) On Fri, Jul 11, 2014 at 3:06 AM, Jonas Smedegaard d...@jones.dk wrote: Quoting Felipe Sateler (2014-07-10 17:12:34) Ardour3 takes a long time to build. The mips and mipsel buildds killed the build after 150 and 300 minutes of inactivity. I managed to build ardour3 in the mipsel porterbox, so I don't think ardour has any real problem on mipsel. I was wondering if maybe we should restrict ardour to the architectures it is likely to be used. Otherwise we might need to ask that ardour be retried until it manages to print output fast enough to avoid getting killed. What do you think? I think we should not decide based on where it is likely to be used, but here is is possible to use. In an ideal world, I would agree. But manpower is very short in the team, so prioritizing is of the essence. Spending time on ensuring builds on an architecture (close to) nobody uses is not a very good use of it. But, if you have a suggestion to ensure the build doesn't time out, I'm all ears :) Maybe I failed to understand, but seems to me that asking th ardour build to be retired until not myeriously hanging on porter boxes is not burdening man power (of the Multimedia team) but instead putting the burden on the porting team where it belongs. The burden is on us due to having to track down a missing build. But most importantly it is a burden on our users because until the mipsel build is up again, ardour3 cannot migrate to testing. I find it wrong of us to try second-guess interests of Debian users. Particularly, looking at popularity contest is wrong here, IMO, as that a) is generally inaccurate (contributions to it is voluntary and only reflects internet-connected hosts) and b) tells only about past usage patterns, not interests-if-available for next release of Debian and the hardware that will then be supported. In general, I agree. I would love to be able to provide all packages in all archs. But it may not be feasible due to time constraints. ...but to address your concrete question: I do not have ideas how to reliably avoid builds hanging, but if not already tried I do have a suggestion for that: Ask the porters, as it seems you have narrowed the issue to be architecture-dependent (if not, then so much more reason against treating it as such!). The problem, as far as I can see, is that the build takes too long. I built ardour3 in eder (a mipsel porterbox) successfully, and it took over 12 hours! If you look at the log I linked to, the build daemon killed the build after some time without activity. I just realized I didn't post the link before. Sorry! Here it is: https://buildd.debian.org/status/logs.php?pkg=ardour3ver=3.5.380~dfsg-2suite=sid -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
m2vrequantiser_1.1-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Jul 2014 15:35:43 +0100 Source: m2vrequantiser Binary: m2vrequantiser Architecture: source amd64 Version: 1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintainers@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: m2vrequantiser - MPEG-2 streams requantization Closes: 715590 Changes: m2vrequantiser (1.1-2) unstable; urgency=medium . * Avoid sscanf() access to argv's 3rd argument when only one is given. (Closes: #715590) * debian/patches/1001-makefile.patch: - Don't append -g -02 to CFLAGS by default, let the build takes it on its own. - Process CPPFLAGS when compiling for hardening. * Set up debhelper 9. * Bump Standards. Checksums-Sha1: 085da2817e882e9f8a77dfbe21a02100018f9080 1982 m2vrequantiser_1.1-2.dsc 7b8429d7f2c00fbfebdf88727cb5605022be226e 2724 m2vrequantiser_1.1-2.debian.tar.gz e1eb9a7011d7bc7e75acb31b616eee66ded123a1 43636 m2vrequantiser_1.1-2_amd64.deb Checksums-Sha256: cbb29c94d263472a68e95c92f64627103ec4d448a5b12a8594879cbe5f03a3dd 1982 m2vrequantiser_1.1-2.dsc 1bba8d6a60ee161e8655891b8b74e2f40c4a323c699285b6f46397b0345980be 2724 m2vrequantiser_1.1-2.debian.tar.gz 95523c722ff2ad08c080f9dbe314d4ad8c661b5eb58f7c7152ee4fc016c3aa90 43636 m2vrequantiser_1.1-2_amd64.deb Files: f2bb9bb1fcef49cc96fb81d8f4100b9a 43636 video optional m2vrequantiser_1.1-2_amd64.deb b45ba03eb9d74044cd2df772972e0257 1982 video optional m2vrequantiser_1.1-2.dsc c31fac83ab945f67dfba3acf750c13e3 2724 video optional m2vrequantiser_1.1-2.debian.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTv/nwAAoJEOikiuUxHXZaM+gP/3wsucoEqtp8vKswDAAyzOy/ LRNmUR6poHNy8Kx2SWcR/9G/KJIVoKlb3wQInkTfl2fXkynSlISzhEe/+qMPr6xg mGF9GBdWTjF9uAAv/DYHJegh78XSllwUpP/bME1f2iz91ZUdlaRdWOQylMEJ6gWp oeTV2xeDih99R4coQiy0sxG6UT4uN1OiCmI0AbU/Hg0Z5qNXqPXo8IDO++EKx8lU 2YzZqsIXfsxJOzX86K1QmQV4mOnFQAkKioNtwHgjV3XsgUH/hEh+t92oY1FZNhtk qFTZvAB2K0Ieg4VdvV0bNdDA3yjuPXWEzeUZGaOKPnxq/ElEOqkVVpj0LHB69czw KR3hkAtKU+8XvjKioWBFycN1KnjsMKg8TxGm8M/ERs4NVgJsYx9PGZnvP67b2F2y hgY8lpnrJG2ce0tHXdIaG81DzHZiMtJryg9uMB1WfEICOfcT3fTew+zb1vtikWA2 DPvUF6fMMcM/RMRpmrXkPM50MP9W3rZV6/0g2rGenXYxv5zAAhhYGJ9rdCkAwIXm e+D83oNMTN6O1oakPsJTWhPdTUd041iG6aor0NboJS9eave3SeAXVQyjl1TIkGBH Na1OmumhX6ns3yw+GeRB2mZ2HWbL7kjXRO5pByrIzaIAzRbd5JEv17DC3uYQJoDe be5T8R6t98hP5oUnNSex =UWS6 -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
smtube_2.1-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Jul 2014 16:13:26 +0100 Source: smtube Binary: smtube Architecture: source amd64 Version: 2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintainers@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: smtube - YouTube videos browser Closes: 752590 Changes: smtube (2.1-2) unstable; urgency=medium . * Add mpv as optional dependency. (Closes: #752590) Checksums-Sha1: 6f4ac5a1fcd2f6afac98ebb7b1a6e0d86973ce62 1939 smtube_2.1-2.dsc 200d0ef21765a37f00c1b7f8c9183518523cb501 2923 smtube_2.1-2.debian.tar.gz 555ba0dd4793875d6d2ba3e865859ef987013669 418700 smtube_2.1-2_amd64.deb Checksums-Sha256: 666f6cdcb91bc19da7a5f146c41ab5ec2eb6f9836b266ba358c783f7eef1b8f8 1939 smtube_2.1-2.dsc 52760e71a42a2ba450a7976363b3e0351595285b410934c4fc5bcd7b2968ba80 2923 smtube_2.1-2.debian.tar.gz 29be3867e2144f66952d7586cb54a5446efeac7fd04661303978d5ef33d7a390 418700 smtube_2.1-2_amd64.deb Files: a91d39d3b8d9d008f23cd8fc97ebbfee 418700 video optional smtube_2.1-2_amd64.deb 91abb80ca48d56c5200f8bf8e8e07c2d 1939 video optional smtube_2.1-2.dsc a7c425932a3a260f17d64011fd1a84f5 2923 video optional smtube_2.1-2.debian.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTv//eAAoJEOikiuUxHXZaaKQP/15GCgjhEoEheLNBVHGao7oj FBAIE24K//GpWTbeGrO6Cj7/EzaFCDIaIdr/u01GGGnE6U/i9i0xdpGJYE63rSjk iEj2hy5DG2wvk7SNwrdsHmxmxSR/UBSLM7j38wf91VHx8cwBHJKY6hCa2OZzn27U dqJIzXFR7ofcU1D3CM9RacsTU+pL63slri2kfrRi2MWZEvTZ75maUfryMYqAMMoi zOTdH7tii9+39Prs1123Bi0e5Dxkz//4iEuNUngdoXzr1r0TSkunXBhcGG1cOMIn jqfptVt6d/rkVwNLwo+UJjJY/lGJ80/87NdZYiWYrQlDORLCsj5IWAJ0BNoY4GV9 XbjGYoMHlaVUNc7M0TCIwPfzpeNj7td0152EvRSSnDNg8JGdjOg6uusxABBFqP5k wDc50jBW1B7AWdpG92sLWDxBD8akKx7yD5h2iaGJVOzyKepBTEtOiosc8YXHNSrD DMESU0LYG6ixYoAZRW7Httyk1GZ4Qh2jAltN6DUdWGr+FMdmUiH8ujTa+2obdWw1 VKZ4qMn1aTio6iQBzFe+uf9/tDbIOLQtidRyORXbRyFZXDLbWCy7ylgIEROP5UHY ilWhY6DOQ6KqSmYUD16QpEmTvxyfI87sczGNNP2i7s20OWVicBcqnv4PSDa42fY3 2IcSr6TrP2/LovSd0mOT =IJYW -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#752590: marked as done (smtube: SMTube should include MPV as optional dependency)
Your message dated Fri, 11 Jul 2014 15:40:51 + with message-id e1x5cwn-vs...@franck.debian.org and subject line Bug#752590: fixed in smtube 2.1-2 has caused the Debian Bug report #752590, regarding smtube: SMTube should include MPV as optional dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: smtube Version: 2.1-1 Severity: normal * What led up to the situation? Trying to uninstall VLC while having SMTube installed * What exactly did you do (or not do) that was effective (or ineffective)? sudo apt-get remove vlc * What was the outcome of this action? While the command did want to uninstall VLC, it also wanted to install smplayer and viceversa. * What outcome did you expect instead? VLC to be removed and smplayer/mplayer/mplayer2 not to be installed as well. I think MPV should be included as a dependency for SMtube (same way totem/mplayer/vlc are). SMtube uses MPV as well so there should be no problem there. If you want to use SMTube and you only use mpv you would have to install an additional video player as well which seems rather unnecesary. Thanks! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smtube depends on: ii libc6 2.19-3 ii libgcc1 1:4.9.0-7 ii libqt4-network 4:4.8.6+dfsg-2 ii libqt4-script 4:4.8.6+dfsg-2 ii libqt4-xml 4:4.8.6+dfsg-2 ii libqtcore4 4:4.8.6+dfsg-2 ii libqtgui4 4:4.8.6+dfsg-2 ii libstdc++6 4.9.0-7 ii mplayer2 [mplayer] 2.0-728-g2c378c7-2 ii smplayer14.3.0-1 smtube recommends no packages. smtube suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: smtube Source-Version: 2.1-2 We believe that the bug you reported is fixed in the latest version of smtube, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia ales...@debian.org (supplier of updated smtube package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Jul 2014 16:13:26 +0100 Source: smtube Binary: smtube Architecture: source amd64 Version: 2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintainers@lists.alioth.debian.org Changed-By: Alessio Treglia ales...@debian.org Description: smtube - YouTube videos browser Closes: 752590 Changes: smtube (2.1-2) unstable; urgency=medium . * Add mpv as optional dependency. (Closes: #752590) Checksums-Sha1: 6f4ac5a1fcd2f6afac98ebb7b1a6e0d86973ce62 1939 smtube_2.1-2.dsc 200d0ef21765a37f00c1b7f8c9183518523cb501 2923 smtube_2.1-2.debian.tar.gz 555ba0dd4793875d6d2ba3e865859ef987013669 418700 smtube_2.1-2_amd64.deb Checksums-Sha256: 666f6cdcb91bc19da7a5f146c41ab5ec2eb6f9836b266ba358c783f7eef1b8f8 1939 smtube_2.1-2.dsc 52760e71a42a2ba450a7976363b3e0351595285b410934c4fc5bcd7b2968ba80 2923 smtube_2.1-2.debian.tar.gz 29be3867e2144f66952d7586cb54a5446efeac7fd04661303978d5ef33d7a390 418700 smtube_2.1-2_amd64.deb Files: a91d39d3b8d9d008f23cd8fc97ebbfee 418700 video optional smtube_2.1-2_amd64.deb 91abb80ca48d56c5200f8bf8e8e07c2d 1939 video optional smtube_2.1-2.dsc a7c425932a3a260f17d64011fd1a84f5 2923 video optional smtube_2.1-2.debian.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTv//eAAoJEOikiuUxHXZaaKQP/15GCgjhEoEheLNBVHGao7oj FBAIE24K//GpWTbeGrO6Cj7/EzaFCDIaIdr/u01GGGnE6U/i9i0xdpGJYE63rSjk iEj2hy5DG2wvk7SNwrdsHmxmxSR/UBSLM7j38wf91VHx8cwBHJKY6hCa2OZzn27U dqJIzXFR7ofcU1D3CM9RacsTU+pL63slri2kfrRi2MWZEvTZ75maUfryMYqAMMoi zOTdH7tii9+39Prs1123Bi0e5Dxkz//4iEuNUngdoXzr1r0TSkunXBhcGG1cOMIn jqfptVt6d/rkVwNLwo+UJjJY/lGJ80/87NdZYiWYrQlDORLCsj5IWAJ0BNoY4GV9
Processing of mpv_0.4.1-1_amd64.changes
mpv_0.4.1-1_amd64.changes uploaded successfully to localhost along with the files: mpv_0.4.1-1_amd64.deb mpv-dbg_0.4.1-1_amd64.deb libmpv1_0.4.1-1_amd64.deb libmpv-dev_0.4.1-1_amd64.deb libmpv-dbg_0.4.1-1_amd64.deb mpv_0.4.1-1.dsc mpv_0.4.1.orig.tar.gz mpv_0.4.1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
mpv_0.4.1-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Jul 2014 18:11:27 +0200 Source: mpv Binary: mpv mpv-dbg libmpv1 libmpv-dev libmpv-dbg Architecture: source amd64 Version: 0.4.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintainers@lists.alioth.debian.org Changed-By: Alessandro Ghedini gh...@debian.org Description: libmpv-dbg - video player based on MPlayer/mplayer2 (client library debug) libmpv-dev - video player based on MPlayer/mplayer2 (client library dev files) libmpv1- video player based on MPlayer/mplayer2 (client library) mpv- video player based on MPlayer/mplayer2 mpv-dbg- video player based on MPlayer/mplayer2 (debug) Changes: mpv (0.4.1-1) unstable; urgency=medium . * New upstream release Checksums-Sha1: 6db29ad24f5ad7a90f85638e28439a60c8ccee81 2827 mpv_0.4.1-1.dsc e31a3f2714ad99181b3a9e849b2a5a4a40e955a2 2562004 mpv_0.4.1.orig.tar.gz 281d5c2719a1082a56556714a41e217f50a0a98d 91796 mpv_0.4.1-1.debian.tar.xz f5a127ba96ed3bf6a6068f9ce0a36e52fa30d669 719828 mpv_0.4.1-1_amd64.deb 129dc2118341e878d1f7e01b2e5fb4e687c50958 1892754 mpv-dbg_0.4.1-1_amd64.deb b2e020dc253c3d508a893cd65cf3c912407036d7 567292 libmpv1_0.4.1-1_amd64.deb 68b05b0de9f27a324cff1657f9ca996a39aa1c9e 22292 libmpv-dev_0.4.1-1_amd64.deb 12187fefa1e6ec1bc7818a83b9590bc9e7518595 1880474 libmpv-dbg_0.4.1-1_amd64.deb Checksums-Sha256: 8eb914914d62c133311b396cee361ec3814f20d51a20299e87b560556bc152e6 2827 mpv_0.4.1-1.dsc 969511267ad443235ac60a947fc40b5fb93fbd97670e23e42705cd39f8f71273 2562004 mpv_0.4.1.orig.tar.gz d8566053c954d73991da7cc59579dd5325b8f88f941885721f75229c82547924 91796 mpv_0.4.1-1.debian.tar.xz 8d7f1eff89d59b7f1acdefdcb5dc451653bc01593ad195961713f8bab9d92729 719828 mpv_0.4.1-1_amd64.deb f54663586af4e462a8cf11fb29805126eb985419fe373876cd5880c7d8a159fa 1892754 mpv-dbg_0.4.1-1_amd64.deb b16d9496d1c9860d7746d48eaa71cc924f6e785fbb9f415a66a48e5758beabdd 567292 libmpv1_0.4.1-1_amd64.deb 0db6735970b400527cb5272a27632ecace697076653bf7bf076c84671f6a8092 22292 libmpv-dev_0.4.1-1_amd64.deb b5bf57d254c94229f6ff46fee198dd278a25ac8aa3a818f16c4f35f88badd4af 1880474 libmpv-dbg_0.4.1-1_amd64.deb Files: 61792ef1adfac9a12cfc20bb37f995ca 719828 video optional mpv_0.4.1-1_amd64.deb 9d935c02bf00d26e0d8977f4f6cf05b5 1892754 debug extra mpv-dbg_0.4.1-1_amd64.deb 4fe64f51d854e2e4e0dfe044e81b6f91 567292 libs optional libmpv1_0.4.1-1_amd64.deb 739220a06149f840ef783e6ac3c1edcf 22292 libdevel optional libmpv-dev_0.4.1-1_amd64.deb f43bdc4595247677784d8353f736effc 1880474 debug extra libmpv-dbg_0.4.1-1_amd64.deb 70262c879d4fc50c648c8b8dc0f9c7f2 2827 video optional mpv_0.4.1-1.dsc 24dcff8c676388227b280a463f9a05d0 2562004 video optional mpv_0.4.1.orig.tar.gz 4361a12f2c4fcc65c2596358de9c5a04 91796 video optional mpv_0.4.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTwA1XAAoJEK+lG9bN5XPLrlgP/ioM1Pgwz8fgqR90zD3CYf8V CB84N7tg6bfsshU5M8wmQcE9oFk0COiJQBF2ZJ5ay3BQdDn1eHuzAqxmWQdZUKMR RWqqYtIVYZ35IHfUX6uwAHxQ3cZcs5hQ+T2f6aoS8AONMaR52xhTVJyaz9sr41/R FwzE16LjGBMQNDIrHQmdncOZeIm77KE7PROsN11GfOr2Nbg7NfFDzUpzqv/8a22P 74/DnbP9KgplOx3peYaXEz2DlpFfA44rwHfIJLQoY9hYk9ZS+PRyXS2D99/c60rB ckeNAxaDSeXVx57tcQf2MkIQif9XW1SXutss+8tfXuNleqs8UDz2LJdX6RKVDh+B vdowRVRpEo1ojx/qklRn6A7dn9QLbq4AHoV3koIgKNjoBkmxuKXoS14ZBZeZF+/8 /zTqbq2SvuzAfAEc97HttCohHMCOV9GP3o6Ca6D84gaFUFlzA0giVN0eyirvnBb+ GFSiDsDPtvmRHXb7FLQu4pkUuajyOh7Lt2IV+DtSH4U8wNsaN16BVqvl67EenqKb Od8pDYuMNcLIL8ayt/1nKIg8N52SlsYKm28KFEay7O+MN5cZX0ZC27ZsntYl1Sv7 3ct/uhg1MR8bVxld/XJViLF/b/+mKtghsyFSYosz/tHGfdI4/mcnEcXjdSGXs2kG g8A9hv0DpXFPDhasIxOv =8eMR -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 architecture list
On Fri, Jul 11, 2014 at 11:19 AM, Felipe Sateler fsate...@debian.org wrote: On Fri, Jul 11, 2014 at 10:40 AM, Jonas Smedegaard d...@jones.dk wrote: Quoting Felipe Sateler (2014-07-11 15:55:34) On Fri, Jul 11, 2014 at 3:06 AM, Jonas Smedegaard d...@jones.dk wrote: Quoting Felipe Sateler (2014-07-10 17:12:34) Ardour3 takes a long time to build. The mips and mipsel buildds killed the build after 150 and 300 minutes of inactivity. I managed to build ardour3 in the mipsel porterbox, so I don't think ardour has any real problem on mipsel. I was wondering if maybe we should restrict ardour to the architectures it is likely to be used. Otherwise we might need to ask that ardour be retried until it manages to print output fast enough to avoid getting killed. What do you think? I think we should not decide based on where it is likely to be used, but here is is possible to use. In an ideal world, I would agree. But manpower is very short in the team, so prioritizing is of the essence. Spending time on ensuring builds on an architecture (close to) nobody uses is not a very good use of it. But, if you have a suggestion to ensure the build doesn't time out, I'm all ears :) Maybe I failed to understand, but seems to me that asking th ardour build to be retired until not myeriously hanging on porter boxes is not burdening man power (of the Multimedia team) but instead putting the burden on the porting team where it belongs. The burden is on us due to having to track down a missing build. But most importantly it is a burden on our users because until the mipsel build is up again, ardour3 cannot migrate to testing. I find it wrong of us to try second-guess interests of Debian users. Particularly, looking at popularity contest is wrong here, IMO, as that a) is generally inaccurate (contributions to it is voluntary and only reflects internet-connected hosts) and b) tells only about past usage patterns, not interests-if-available for next release of Debian and the hardware that will then be supported. In general, I agree. I would love to be able to provide all packages in all archs. But it may not be feasible due to time constraints. ...but to address your concrete question: I do not have ideas how to reliably avoid builds hanging, but if not already tried I do have a suggestion for that: Ask the porters, as it seems you have narrowed the issue to be architecture-dependent (if not, then so much more reason against treating it as such!). The problem, as far as I can see, is that the build takes too long. I built ardour3 in eder (a mipsel porterbox) successfully, and it took over 12 hours! If you look at the log I linked to, the build daemon killed the build after some time without activity. It turns out that waf prints its diagnostics on stderr instead of stdout. For some reason, the buildd does not monitor stderr, so it thought that the build had not printed anything for 5 hours! I think I have this fixed by a patch, so lets see how this goes. I;m building now -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processing of ardour3_3.5.380~dfsg-3_amd64.changes
ardour3_3.5.380~dfsg-3_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: ardour3_3.5.380~dfsg-3_amd64.deb ardour3_3.5.380~dfsg-3.dsc ardour3_3.5.380~dfsg-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host ravel.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processing of ardour3_3.5.380~dfsg-3_amd64.changes
ardour3_3.5.380~dfsg-3_amd64.changes uploaded successfully to localhost along with the files: ardour3_3.5.380~dfsg-3_amd64.deb ardour3_3.5.380~dfsg-3.dsc ardour3_3.5.380~dfsg-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
ardour3_3.5.380~dfsg-3_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 11 Jul 2014 12:46:37 -0400 Source: ardour3 Binary: ardour3 Architecture: source amd64 Version: 3.5.380~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintainers@lists.alioth.debian.org Changed-By: Felipe Sateler fsate...@debian.org Description: ardour3- digital audio workstation (graphical gtk2 interface) Changes: ardour3 (3.5.380~dfsg-3) unstable; urgency=medium . * Prevent build failures in slower architectures by forcing waf logging to stdout instead of stderr. Checksums-Sha1: 8d6253b75f5f1df1b016f33a64fc5068fc532857 2949 ardour3_3.5.380~dfsg-3.dsc e07f8d50e4a8a99fe6ceb61d1d9eecbc507a8e20 105080 ardour3_3.5.380~dfsg-3.debian.tar.xz 1cd75ae40e88817789303630e5e3d878af642402 7107156 ardour3_3.5.380~dfsg-3_amd64.deb Checksums-Sha256: 540f503cbaacfffe1dc9cefa5e53a88bfefe2d9db09a67f87e66e19c269f8111 2949 ardour3_3.5.380~dfsg-3.dsc ec9eb67fa4dc7b124ef91ab818fb0b4f425d023bebe94f21d77dfd20ca9e9802 105080 ardour3_3.5.380~dfsg-3.debian.tar.xz a51be3f5b4daa60cbd05405760545f6a9d663ea7562fa84b34485aff983b8d06 7107156 ardour3_3.5.380~dfsg-3_amd64.deb Files: d6ce412cf0c05594a27a6a3955fb91d7 7107156 sound optional ardour3_3.5.380~dfsg-3_amd64.deb c98157ed793b57a59599449d4d52d98f 2949 sound optional ardour3_3.5.380~dfsg-3.dsc c28978aecd39422df9949f5fb6320fc4 105080 sound optional ardour3_3.5.380~dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTwBxTAAoJEKO6uuJAjdbPKLEP/i6YkO82T+zrjBsBZu5ikEBK kWtot/XPET5JVolpsg+P4LqYdO6TnsvFNlGKxN+2nyXQ+7eh3gtFTJlQ+ASqlu8a BQeaplh+bF/SIBU0o3Lx3t1W3l/j7ozR8dmvaix3LN2Nvu1HVnmI35E0vmyEae0n 0PdE9zVdpi/FStUxvpocZoevC/NdYr9s6KL5Pmv/zPncGqDirr10GKc3N8ECNBMS kBKXXHlAZ0+DVtYq5G1+gv4w1g4a78vBqXIGe3eL3YTKVkv83i9ZniZc4H41a/Dq KMdbUuGHrCfGpv0FCqWmro7gHuyKOHq9+n+AKuHmCaZvpA7WrFZRDHTTvUv7Hm/q EGYS9Pf+7i8MMQ++XUvuQ+SB8PV9+Tk6Kih2lZqZiszRab3I8+/1nVhrdJVFkfUC opJoD+qg6wzctKhsM706PeQ9A4o6AuHT9tgBngM23xYnDQdjVE+U++JJmMMtwbom TNcJBwPw3sx6qBX2P67mjsmSH5mZIntOvXpZPoZWnKQq8CJX4ZK8Vm5q4BOtyTiU /RymxUJ02vPEsxIW1+ovPq9LMEJNvKUuYyxMoPnyqvZ8zIYiCcVIkRKas0yzPaAx pm8lUudXMxQO68zqYgoerDPR6sPi6mHXkGGoEhl6V2e05na2lV/rWdpEAAE/h575 DhzIUWtI6lFIiKrJw9Fl =3WHp -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#754435: libavcodec55: vlc segfaults with error 4 in libavcodec.so
*sigh* and another place to register and eventually forget the password... I opened up libavcodec bug #716 which you can find here: http://bugzilla.libav.org/show_bug.cgi?id=716 Regards, Tim ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#754510: mpv: segfaults on too short tracks
Package: mpv Version: 1:0.4.1-dmo1 Severity: normal Dear Maintainer, lsdvd dvdimage Title: 01, Length: 00:22:04.000 Chapters: 01, Cells: 01, Audio streams: 06, Subpictures: 12 Title: 02, Length: 00:21:54.400 Chapters: 01, Cells: 01, Audio streams: 06, Subpictures: 12 Title: 03, Length: 00:21:52.000 Chapters: 01, Cells: 01, Audio streams: 06, Subpictures: 12 Title: 04, Length: 00:00:00.480 Chapters: 01, Cells: 01, Audio streams: 06, Subpictures: 12 Title: 05, Length: 00:00:12.800 Chapters: 01, Cells: 01, Audio streams: 06, Subpictures: 12 Title: 06, Length: 00:00:00.480 Chapters: 01, Cells: 01, Audio streams: 06, Subpictures: 12 Title: 07, Length: 00:03:14.000 Chapters: 01, Cells: 01, Audio streams: 06, Subpictures: 12 Longest track: 01 playing mpv -dvd-image dvdimage dvd://3 causes mpv to segfault (since mpv starts with 0 whereas lsdvd starts at 1, track 3 for mpv is track 4 of lsdvd output) let me know what i can do to provide more info. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mpv depends on: ii libasound2 1.0.28-1 ii libass5 0.10.2-3 ii libavcodec5510:2.2.4-dmo3 ii libavdevice55 10:2.2.4-dmo3 ii libavfilter410:2.2.4-dmo3 ii libavformat55 10:2.2.4-dmo3 ii libavresample1 10:2.2.4-dmo3 ii libavutil52 10:2.2.4-dmo3 ii libbluray1 2:0.6.0-dmo2 ii libbs2b03.1.0+dfsg-2 ii libc6 2.19-5 ii libcaca00.99.beta19-2 ii libcdio-cdda1 0.83-4.1 ii libcdio-paranoia1 0.83-4.1 ii libcdio13 0.83-4.1 ii libdvdnav4 4.2.1-3 ii libdvdread4 4.2.1-2 ii libegl1-mesa [libegl1-x11] 10.2.3-1 ii libenca01.15-2 ii libgl1-mesa-glx [libgl1]10.2.3-1 ii libguess1 1.2-dmo2 ii libjack-jackd2-0 [libjack-0.116]1.9.10+20140610git97e0e80b~dfsg-1 ii libjpeg88d1-1 ii liblcms2-2 2.6-3 ii liblircclient0 0.9.0~pre1-1 ii liblua5.2-0 5.2.3-1 ii libmpg123-0 1.20.0-1 ii libncurses5 5.9+20140118-1 ii libopenal1 1:1.14-4 ii libpostproc52 10:2.2.4-dmo3 ii libpulse0 5.0-2 ii libquvi70.4.1-2.1 ii libsmbclient2:4.1.9+dfsg-1 ii libswscale2 10:2.2.4-dmo3 ii libtinfo5 5.9+20140118-1 ii libv4l-01.2.1-2 ii libva-glx1 1.3.1-3 ii libva-x11-1 1.3.1-3 ii libva1 1.3.1-3 ii libvdpau1 0.7-2 ii libwayland-client0 1.5.0-1 ii libwayland-cursor0 1.5.0-1 ii libwayland-egl1-mesa [libwayland-egl1] 10.2.3-1 ii libx11-62:1.6.2-2 ii libxext62:1.3.2-1 ii libxinerama12:1.1.3-1 ii libxkbcommon0 0.4.0-1 ii libxss1 1:1.2.2-1 ii libxv1 2:1.0.10-1 ii libxxf86vm1 1:1.1.3-1 ii zlib1g 1:1.2.8.dfsg-1 mpv recommends no packages. mpv suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#754511: mpv: after each track it either displays dvd menu or copyright blurb
Package: mpv Version: 1:0.4.1-dmo1 Severity: normal Dear Maintainer, having a dvd image with 3 tracks, i play it via mpv -dvd-image dvdimage dvd://0-2 but instead of siwtching seamlessly to the next track, after track 0 and 1 i get the dvd menu and after track 2 it plays the copyright blurb. while after the blurb at leats it finishes, it stays at the menu unless i intervene. i'd expect it to behave like mplayer does: play all tracks after each automatically other without -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mpv depends on: ii libasound2 1.0.28-1 ii libass5 0.10.2-3 ii libavcodec5510:2.2.4-dmo3 ii libavdevice55 10:2.2.4-dmo3 ii libavfilter410:2.2.4-dmo3 ii libavformat55 10:2.2.4-dmo3 ii libavresample1 10:2.2.4-dmo3 ii libavutil52 10:2.2.4-dmo3 ii libbluray1 2:0.6.0-dmo2 ii libbs2b03.1.0+dfsg-2 ii libc6 2.19-5 ii libcaca00.99.beta19-2 ii libcdio-cdda1 0.83-4.1 ii libcdio-paranoia1 0.83-4.1 ii libcdio13 0.83-4.1 ii libdvdnav4 4.2.1-3 ii libdvdread4 4.2.1-2 ii libegl1-mesa [libegl1-x11] 10.2.3-1 ii libenca01.15-2 ii libgl1-mesa-glx [libgl1]10.2.3-1 ii libguess1 1.2-dmo2 ii libjack-jackd2-0 [libjack-0.116]1.9.10+20140610git97e0e80b~dfsg-1 ii libjpeg88d1-1 ii liblcms2-2 2.6-3 ii liblircclient0 0.9.0~pre1-1 ii liblua5.2-0 5.2.3-1 ii libmpg123-0 1.20.0-1 ii libncurses5 5.9+20140118-1 ii libopenal1 1:1.14-4 ii libpostproc52 10:2.2.4-dmo3 ii libpulse0 5.0-2 ii libquvi70.4.1-2.1 ii libsmbclient2:4.1.9+dfsg-1 ii libswscale2 10:2.2.4-dmo3 ii libtinfo5 5.9+20140118-1 ii libv4l-01.2.1-2 ii libva-glx1 1.3.1-3 ii libva-x11-1 1.3.1-3 ii libva1 1.3.1-3 ii libvdpau1 0.7-2 ii libwayland-client0 1.5.0-1 ii libwayland-cursor0 1.5.0-1 ii libwayland-egl1-mesa [libwayland-egl1] 10.2.3-1 ii libx11-62:1.6.2-2 ii libxext62:1.3.2-1 ii libxinerama12:1.1.3-1 ii libxkbcommon0 0.4.0-1 ii libxss1 1:1.2.2-1 ii libxv1 2:1.0.10-1 ii libxxf86vm1 1:1.1.3-1 ii zlib1g 1:1.2.8.dfsg-1 mpv recommends no packages. mpv suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#754512: mpv: dvd:// plays second track
Package: mpv Version: 1:0.4.1-dmo1 Severity: normal Dear Maintainer, playing a dvd image with 7 tracks (0-3 are episodes, 4-6 are just the usual fillers) via mpv -dvd-image dvdimage dvd:// plays the second track, not the first. i am not quite sure what exactly to expect (just playing or presenting the dvd menu or something entirely different), but i think it shouldn't skip the first track. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mpv depends on: ii libasound2 1.0.28-1 ii libass5 0.10.2-3 ii libavcodec5510:2.2.4-dmo3 ii libavdevice55 10:2.2.4-dmo3 ii libavfilter410:2.2.4-dmo3 ii libavformat55 10:2.2.4-dmo3 ii libavresample1 10:2.2.4-dmo3 ii libavutil52 10:2.2.4-dmo3 ii libbluray1 2:0.6.0-dmo2 ii libbs2b03.1.0+dfsg-2 ii libc6 2.19-5 ii libcaca00.99.beta19-2 ii libcdio-cdda1 0.83-4.1 ii libcdio-paranoia1 0.83-4.1 ii libcdio13 0.83-4.1 ii libdvdnav4 4.2.1-3 ii libdvdread4 4.2.1-2 ii libegl1-mesa [libegl1-x11] 10.2.3-1 ii libenca01.15-2 ii libgl1-mesa-glx [libgl1]10.2.3-1 ii libguess1 1.2-dmo2 ii libjack-jackd2-0 [libjack-0.116]1.9.10+20140610git97e0e80b~dfsg-1 ii libjpeg88d1-1 ii liblcms2-2 2.6-3 ii liblircclient0 0.9.0~pre1-1 ii liblua5.2-0 5.2.3-1 ii libmpg123-0 1.20.0-1 ii libncurses5 5.9+20140118-1 ii libopenal1 1:1.14-4 ii libpostproc52 10:2.2.4-dmo3 ii libpulse0 5.0-2 ii libquvi70.4.1-2.1 ii libsmbclient2:4.1.9+dfsg-1 ii libswscale2 10:2.2.4-dmo3 ii libtinfo5 5.9+20140118-1 ii libv4l-01.2.1-2 ii libva-glx1 1.3.1-3 ii libva-x11-1 1.3.1-3 ii libva1 1.3.1-3 ii libvdpau1 0.7-2 ii libwayland-client0 1.5.0-1 ii libwayland-cursor0 1.5.0-1 ii libwayland-egl1-mesa [libwayland-egl1] 10.2.3-1 ii libx11-62:1.6.2-2 ii libxext62:1.3.2-1 ii libxinerama12:1.1.3-1 ii libxkbcommon0 0.4.0-1 ii libxss1 1:1.2.2-1 ii libxv1 2:1.0.10-1 ii libxxf86vm1 1:1.1.3-1 ii zlib1g 1:1.2.8.dfsg-1 mpv recommends no packages. mpv suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#722997: File currently included as changelog is (at most) a NEWS file
reopen 722997 thanks Thanks for including upstream release notes. That file, however, seems at most a NEWS file: It is apparently an unmaintained broad overview of changes for some specific release - without mention of which one, but didn't at all since it was included and mentions only two git hashes, no version numbers. I recommend to do the following: a) Check with upstream if current file is expected to be maintained, and if so then ship it as NEWS file instead - else drop it. b) Manually generate at each upstream release a changelog file using a git checkout and the Debian package git2cl. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: File currently included as changelog is (at most) a NEWS file
Processing commands for cont...@bugs.debian.org:
reopen 722997
Bug #722997 {Done: Alessandro Ghedini gh...@debian.org} [mpv] mpv: Upstream
changelog is missing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mpv/0.4.0-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
722997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#754521: gnome-mplayer: Files with # in the name are not played
Package: gnome-mplayer Version: 1.0.9-1 Severity: normal Dear Maintainer, Files with # in the name are not opening in gnome-mplayer, if you try to open the video with direct terminal mplayer works perfectly, but with gnome-mplayer is stopped and can not be given play. Output terminal: $ gnome-mplayer #file.mkv GMLIB-Message: after init: position=0,000 length=0,000 start_time=0,000 run_time=0,000 volume=0,00 player=dead media=unknown uri= (gnome-mplayer:15084): GLib-CRITICAL **: Source ID 63 was not found when attempting to remove it (gnome-mplayer:15084): GLib-CRITICAL **: Source ID 64 was not found when attempting to remove it (gnome-mplayer:15084): GLib-CRITICAL **: Source ID 65 was not found when attempting to remove it (gnome-mplayer:15084): GLib-CRITICAL **: Source ID 63 was not found when attempting to remove it (gnome-mplayer:15084): GLib-CRITICAL **: Source ID 65 was not found when attempting to remove it (gnome-mplayer:15084): GLib-CRITICAL **: Source ID 64 was not found when attempting to remove it Not identify if the problem occurs with other special characters, but those tested, only # has made the video was not played. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-mplayer depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii libasound2 1.0.27.2-4 ii libc62.19-4 ii libcairo21.12.16-2 ii libcurl3-gnutls 7.37.0-1+b1 ii libdbus-1-3 1.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libgda-5.0-4 5.2.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgmlib11.0.9-1 ii libgmtk1 1.0.9-1 ii libgpod4 0.8.3-1.1+b1 ii libgtk-3-0 3.12.2-1+b1 ii libmusicbrainz3-63.0.2-2.1 ii libnautilus-extension1a 3.8.2-3 ii libnotify4 0.7.6-2 ii libx11-6 2:1.6.2-2 ii libxss1 1:1.2.2-1 ii mplayer2 [mplayer] 2.0-728-g2c378c7-2+b1 Versions of packages gnome-mplayer recommends: ii gnome-icon-theme-symbolic 3.12.0-1 ii xdg-utils 1.1.0~rc1+git20111210-7.1 Versions of packages gnome-mplayer suggests: pn gecko-mediaplayer none -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: bug 754435 is forwarded to http://bugzilla.libav.org/show_bug.cgi?id=716
Processing commands for cont...@bugs.debian.org: forwarded 754435 http://bugzilla.libav.org/show_bug.cgi?id=716 Bug #754435 [libavcodec55] libavcodec55.so crashes vlc while decoding Set Bug forwarded-to-address to 'http://bugzilla.libav.org/show_bug.cgi?id=716'. thanks Stopping processing here. Please contact me if you need assistance. -- 754435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
