Bug#1017905: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: rust-glib-sys Version: 0.14.0-1 Severity: serious See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html For more details how to solve this in a way that makes ftp-masters happy, please

Bug#1017904: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: webkit2-sharp Version: 2.10.9+git20160917-1.1 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that

Bug#1017903: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: soup-sharp Version: 2.42.2+git20151219-3.1 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that

Bug#1017902: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: poppler-sharp Version: 0.0.3-4.1 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that were rejected,

Bug#1017901: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: gudev-sharp-3.0 Version: 3.0.0-1 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that were rejected,

Bug#1017900: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: gudev-sharp-1.0 Version: 0.1-4.1 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that were

Bug#1017898: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: appindicator3-sharp Version: 12.10.0+git20151221-5.1 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages

Bug#1017897: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: gtk-sharp3 Version: 2.99.3-4 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that were rejected, the

Bug#1017896: Ships copies of libraries that are packaged in Debian

Package: firefox-esr Version: 102.1.0esr-2 Severity: serious Hi, The firefox source package currently ships various libraries that are packaged in Debian, but at build time the local copies are used instead. The package build process should use the versions packaged in Debian. Examples of these

Bug#1017895: Ships copies of libraries that are packaged in Debian

Package: firefox Version: 103.0.2-2 Severity: serious Hi, The firefox source package currently ships various libraries that are packaged in Debian, but at build time the local copies are used instead. The package build process should use the versions packaged in Debian. Examples of these are

Bug#1017893: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: gtk-sharp2 Version: 2.12.40-3 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that were rejected,

Bug#1017892: Ships copies of libraries that are in Debian and autogenerated files that can't be renegerated with the code in Debian main

Source: librsvg Version: 2.54.4+dfsg-1 Severity: serious Tags: upstream Hi, See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html For more details how to solve this in a way that makes

Bug#1017891: Ships autogenerated files that can't be renegerated with the code in Debian main

Source: vala Version: 0.56.2-1 Severity: serious Tags: upstream Hi, See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that were rejected, the

Bug#1017890: Ships autogenerated files that can't be renegerated with the code in Debian main

Package: gobject-introspection Version: 1.72.0-1+b1 Severity: serious Tags: upstream Hi, See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages

Bug#1005120: wpewebkit: Fails to build with gstreamer 1.20

On Tue, 2022-02-08 at 18:10 +0100, Alberto Garcia wrote: > On Mon, Feb 07, 2022 at 10:53:56AM -0500, Jeremy Bicha wrote: > > wpewebkit fails to build from source, apparently because of the recent > > gstreamer 1.20 uploads. > > > > -- Checking for module 'gstreamer-codecparsers-1.0 >= 1.14.0' > >

Bug#1004438: reportbug: gstreamer1.0-plugins-bad 1.18.5-1+b4 has an invalid dependency on a contrib package

On Thu, 27 Jan 2022 18:31:37 +0100 Francois Gouget wrote: > > > gstreamer1.0-plugins-bad is part of the main archive area. However in > Debian Testing's version 1.18.5-1+b4 it depends on > libgstreamer-gl1.0-0 which is now in the contrib archive area. > > This is a violation of section 2.2.1 of

Bug#985358: pitivi: A/V out of sync in rendered videos

On Tue, 2021-03-16 at 13:39 -0300, Antonio Terceiro wrote: As a user, I don't even know about all the stuff that could be better; pitivi worked ok for me as an amateur video editor. It just failed at the end of the process, rendering the video. So from my PoV, the version in bullseye is fine once

Bug#985358: pitivi: A/V out of sync in rendered videos

On Tue, 2021-03-16 at 11:16 -0300, Antonio Terceiro wrote: Dear Maintainer, The version of pitivi in bullseye is affected by the bug listed above: rendered videos have A/V out of sync by a few seconds, while they sound just find in the preview. I'm attaching the upstream patch that fixed the

Bug#971754: ABI breakage from 1.4.1 to 1.4.2

On Sat, 2021-01-16 at 14:05 +0100, Paul Gevers wrote: > > I was expecting a new upstream release to be incorporated, but I > understand upstream didn't release anything new yet. For whatever > it's worth, your MR doesn't look too weird. Thanks, I've uploaded it to delayed/1 in case someone

Bug#971754: ABI breakage from 1.4.1 to 1.4.2

Hi Paul, On Fri, 2021-01-15 at 22:37 +0100, Paul Gevers wrote: > > Can you do this please? srt is orphaned, your package depend on it, > could you please help us get us out of this situation? (if this > happens soon, we'll accept the transition to fix this). I've created a MR in salsa for this

Bug#971754: ABI breakage from 1.4.1 to 1.4.2

On Fri, 2021-01-15 at 22:37 +0100, Paul Gevers wrote: > Hi Sebastian, > > On Thu, 14 Jan 2021 11:39:24 +0200 Sebastian =?ISO-8859-1?Q?Dr=F6ge?= > wrote: > > Upstream fixed this now by making the soversion 1.4 and from now on > > guaranteeing that patch versions (1.4.0 -> 1.4.X) do not break ABI.

Bug#971754: ABI breakage from 1.4.1 to 1.4.2

On Wed, 13 Jan 2021 17:42:27 +0100 Andreas Beckmann wrote: > Control: tag -1 patch > > Hi, > > On Thu, 7 Jan 2021 20:52:39 +0100 Paul Gevers wrote: > > On Tue, 06 Oct 2020 16:38:49 +0300 =?utf-8?q?Sebastian_Dr=C3=B6ge?= > > wrote: > > > 1.4.2 broke ABI by adding some fields to the

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

On Tue, 5 Jan 2021 19:09:04 +0100 Paul Gevers wrote: > > > This is solely blocked on srt currently, and the maintainer will have > > to figure out a solution there for the ABI breakage. > > Ack. Although, you *could* help them find a solution. RC bugs in key > packages are a shared

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

On Mon, 28 Dec 2020 18:40:38 +0100 Paul Gevers wrote: > > If you believe your package is unable to migrate to testing due to > issues beyond your control, don't hesitate to contact the Release Team. > In this case, I think it may be wise to upload to > testing-proposed-updates and ask for an

Bug#971754: ABI breakage from 1.4.1 to 1.4.2

Source: srt Version: 1.4.2-1 Severity: serious Tags: upstream 1.4.2 broke ABI by adding some fields to the CBytePerfMon structure. See https://github.com/Haivision/srt/issues/1592 for details. There were also other ABI breakages in previous versions that are not reflected by the binary package

Bug#965007: pitivi: ships a copy of gstreamer libraries

On Wed, 2020-09-23 at 09:36 +0200, Gianfranco Costamagna wrote: > > Hello, I found that pitivi was using the gst-transcoder only if not found on > the system, > and upstream commit "51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e" worked in > fixing that. > > I prepared a version on Debomatic with

Bug#965007: pitivi: ships a copy of gstreamer libraries

On Mon, 2020-08-17 at 09:10 -0300, Antonio Terceiro wrote: > > This file is already present in pitivi on stable, and > gstreamer1.0-plugins-bad-apps is only present in experimental. testing > and unstable are unaffected by this, or testing would be unaffected if > this hadn't caused pitivi to be

Bug#963301: gstreamer1.0: FTBFS:

On Sun, 21 Jun 2020 21:53:15 +0200 Lucas Nussbaum wrote: > > > During a rebuild of all packages in sid, your package failed to build > on amd64. > [...] Thanks for reporting. This happens because GNU make was updated to 4.3, which includes backwards incompatible changes. Updating to that was

Bug#946329: valgrind-mpi FTBFS

Package: valgrind Version: 1:3.15.0-1 Severity: serious valgrind currently fails to build from source. The Ubuntu patch to drop MPI 1 support (drop-MPI-1-support.patch) probably fixes this. In file included from libmpiwrap.c:116: libmpiwrap.c: In function 'showTy':

Bug#927739: FTBFS: undefined reference to `yylex'

On Mon, 2019-04-22 at 14:22 +0200, Santiago Vila wrote: > > I can build libkate in my autobuilders. > > I also triggered a rebuild in reproducible-builds and it worked: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libkate.html > > Can you reproduce the failure in

Bug#927739: FTBFS: undefined reference to `yylex'

Source: libkate Version: 0.4.1-9 Severity: serious Hi, Something seems to have changed with flex, which causes the package to now fail to build: /bin/bash ../libtool --tag=CC --silent --mode=link gcc -Wall -W -I/usr/include/libpng16 -g -O2

Bug#894149: buzztrax FTBFS with gstreamer 1.14

On Wed, 2018-03-28 at 10:08 +0300, Juhani Numminen wrote: > Control: tags -1 fixed-upstream > > On Mon, 26 Mar 2018 22:31:51 +0300 Adrian Bunk > wrote: > > Source: buzztrax > > Version: 0.10.2-4 > > ... > > src/gst/dec/bt-dec.c:956:14: error: expected '=', ',', ';', 'asm' > > or

Bug#894076: Can't include GL and GLES headers simultaneously on non-64 bit architectures

Package: mesa Version: 17.3.7-1 Severity: serious Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=105328 Hi, Currently it's impossible to include the GL and GLES headers simultaneously on non-64 bit architectures, see e.g.

Bug#888501: gstreamer1.0-vaapi: Latests versions does not work at all

reassign 888501 libva thanks On Fri, 26 Jan 2018 10:40:36 -0200 Junior Polegato wrote: > libva info: VA-API version 0.40.0 > libva info: va_getDriverName() returns 0 > libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i965_drv_video.so > libva error:

Bug#883849: libwebkit2gtk-4.0-37 uninstallable because gst-plugins-bad1.0 is now at 1.12.4

On Fri, 2017-12-08 at 15:59 +0100, Emilio Pozuelo Monfort wrote: > On 08/12/17 15:44, Sebastian Dröge wrote: > > On Fri, 8 Dec 2017 11:17:22 +0100 Emilio Pozuelo Monfort <pochu@deb > > ian.org> wrote: > > > On 08/12/17 11:04, Paul Gevers wrote: > > > > Pac

Bug#883849: libwebkit2gtk-4.0-37 uninstallable because gst-plugins-bad1.0 is now at 1.12.4

On Fri, 8 Dec 2017 11:17:22 +0100 Emilio Pozuelo Monfort wrote: > On 08/12/17 11:04, Paul Gevers wrote: > > Package: libwebkit2gtk-4.0-37 > > Version: 2.18.3-1 > > Severity: grave > > Justification: renders package unusable > > > > While trying to build a new version of

Bug#879673: ffmpeg 3.4 API compat layer not 100% backwards compatible

On Tue, 2017-10-24 at 13:44 +0100, James Cowgill wrote: > > gst-libav upstream bug can be found here: > > https://bugzilla.gnome.org/show_bug.cgi?id=789193 > > OK, hopefully upstream ffmpeg can help fixing this bug, since I'm not > sure what I can do about it. It seems like it also introduces

Bug#879673: ffmpeg 3.4 API compat layer not 100% backwards compatible

Package: ffmpeg Version: 7:3.4-1 Severity: serious Hi, ffmpeg 3.4 comes with a new decoding API (among other things), and provides a compatibility layer around that for the old API. Unfortunately this compatibility layer is apparently not 100% backwards compatible or buggy. It breaks at least

Bug#878747: gst-plugins-bad1.0 FTBFS with libopenjp2-7-dev 2.3

On Mon, 2017-10-16 at 15:50 +0300, Adrian Bunk wrote: > Source: gst-plugins-bad1.0 > Version: 1.12.2-1 > Severity: serious > > https://buildd.debian.org/status/package.php?p=gst-plugins-bad1.0 > te=sid > > ... > > In file included from gstopenjpegdec.h:29:0, >  from

Bug#852594: buzztrax: Update udevadm path

severity 852594 minor thanks Hi, as this only affects a source code comment and not actual code, I'm downgrading the severity to minor. This is in no way serious. Sebastian signature.asc Description: This is a digitally signed message part

Bug#865423: gst-rtsp-server1.0: testsuite emits large amounts of multicast traffic

On Wed, 2017-06-21 at 11:47 +0100, James Cowgill wrote: > > Hi, > > While running the testsuite, the "gst/rtspserver" test emits about 200k > UDP packets into the local network. They are all sent to a multicast > address which will be forwarded to the router for the current subnet and > then

Bug#853723: tracker-extract gets killed by seccomp when gstreamer tries to regenerate cache (dup2 related)

On Tue, 2017-01-31 at 16:04 +0200, Sebastian Dröge wrote: > On Tue, 31 Jan 2017 11:33:34 +0100 Laurent Bigonville <bigon@debian.o > rg > > wrote: > > Package: tracker-extract > > Version: 1.10.4-1 > > Severity: serious > >   > > Hi, > >   > &

Bug#853723: tracker-extract gets killed by seccomp when gstreamer tries to regenerate cache (dup2 related)

On Tue, 31 Jan 2017 11:33:34 +0100 Laurent Bigonville wrote: > Package: tracker-extract > Version: 1.10.4-1 > Severity: serious >  > Hi, >  > tracker-extract gets killed by seccomp when gstreamer tries to > regenerate cache. >  > According to Simon, one of the solution would be

Bug#850266: Missing headers in -dev package

Package: libsrtp2-dev Severity: serious Version: 2.0.0-1 Hi, it seems like the headers in the crypto subdirectory should also be included, at least partially. Without this, constants like SRTP_AES_128_ICM SRTP_NULL_CIPHER and others are missing and they seem to be needed for usage of the

Bug#845037: libschroedinger-1.0-0: is this package fit for stretch?

On Mon, 2016-11-21 at 23:46 +0100, Andreas Cadhalpun wrote: > Hi Sebastian, > > On 21.11.2016 08:22, Sebastian Dröge wrote: > > On Sun, 2016-11-20 at 11:57 +0100, Moritz Muehlenhoff wrote: > > > > > > Thus I think stretch would be better of without this library

Bug#845037: libschroedinger-1.0-0: is this package fit for stretch?

On Sun, 2016-11-20 at 11:57 +0100, Moritz Muehlenhoff wrote: > > Thus I think stretch would be better of without this library. > > > > As replacement, ffmpeg has a decent dirac decoder and also a > > vc2 encoder, which is the intra-only subset of dirac that > > got standardized by the SMPTE. >

Bug#843908: API/ABI change without corresponding soname change

Package: zeromq3 Version: 4.2.0-1 Severity: grave Hi, the symbol zpoller_ignore_interrupts was removed in 4.2.0 (as also mentioned in the release notes), and replaced by zpoller_set_nonstop. Unfortunately this didn't go together with a change of the soname, thus breaking all existing packages

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

On Fri, 22 Jul 2016 13:27:09 +0300 Faidon Liambotis wrote: > I still don't exactly understand how H.264/VA-API are related when playing > just a .wav file, though... They are not, it's just that the initialization of this GStreamer plugin (the ffmpeg/libav one) is going

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

On Wed, 20 Jul 2016 22:06:05 +0300 Faidon Liambotis wrote: > Stack trace of thread 4122: > #0  0x7fa47ae7f1c8 raise (libc.so.6) > #1  0x7fa47ae8064a abort (libc.so.6) > #2  0x7fa4719b8f5b n/a

Bug#825150: pitivi: hard dependency is unmet -- gstgtk

On Fr, 2016-05-27 at 01:39 +0200, Martin Hanson wrote: > > > > You have gstreamer1.0-plugins-bad from Debian Multimedia installed. > > Try > > with the official Debian packages instead, they contain the > > GStreamer > > GTK integration. > I am running with a clean and new Jessie installation, no

Bug#825150: pitivi: hard dependency is unmet -- gstgtk

On Di, 2016-05-24 at 14:07 +0800, Nick Coleman wrote: > Package: pitivi > Version: 0.95-1+b1 > Severity: grave > Justification: renders package unusable > > Pitivi crashes on start with an unmet hard dependency, making the > package unusable.  The error message is: >  > - gstgtk not found on the

Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

reassign 816587 docbook-utils reassign 817026 docbook-utils reassign 817027 docbook-utils forcemerge 816587 817026 817027 thanks On Do, 2016-03-03 at 10:45 +0200, Sebastian Dröge wrote: > On Do, 2016-03-03 at 08:36 +, Chris Lamb wrote: > > > > Source: shared-mime-info >

Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

On Do, 2016-03-03 at 08:36 +, Chris Lamb wrote: > Source: shared-mime-info > Version: 1.5-2 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org > >

Bug#785924: [Freewx-maint] Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

On Mo, 2016-02-22 at 00:49 +1300, Olly Betts wrote: > > Sebastian Dröge <sl...@debian.org> wrote: > > How can I test the wxwidgets GStreamer integration? > You need to test via an application which uses it - something which > depends on the wx or wxpython media pac

Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

On So, 2016-02-21 at 12:29 +0200, Sebastian Dröge wrote: > On So, 2016-02-21 at 11:09 +0200, Sebastian Dröge wrote: > > On Di, 2015-11-10 at 20:28 +, Olly Betts wrote: > > >   > > > I'll try to find time to test it.  Also happy for someone else to > > >

Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

On So, 2016-02-21 at 11:09 +0200, Sebastian Dröge wrote: > On Di, 2015-11-10 at 20:28 +, Olly Betts wrote: > >   > > I'll try to find time to test it.  Also happy for someone else to > > test > > the amended patch and NMU if it works, but please keep me in the > &

Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

On Di, 2015-11-10 at 20:28 +, Olly Betts wrote: >  > I'll try to find time to test it.  Also happy for someone else to test > the amended patch and NMU if it works, but please keep me in the loop to > avoid duplicating effort. > > (If someone does NMU, you could usefully drop `--enable-sdl`

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

On So, 2015-12-06 at 12:17 +0100, Soeren D. Schulze wrote: > Am 06.12.2015 um 08:50 schrieb Sebastian Dröge: > > > Hello, > > > > > > it is not fixed, alas.  The following SIGSEGV backtrace is with > > > gstreamer1.0-plugins-bad 1.6.1-1+b1 and iceweasel

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

On Sa, 2015-12-05 at 16:28 +0100, Soeren D. Schulze wrote: > Am 12.11.2015 um 15:02 schrieb Sebastian Dröge: > > On Do, 2015-11-12 at 14:41 +0100, Soeren D. Schulze wrote: > > > Hello, > > > > > > the problem does not seem to occur any more with >

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

On Sa, 2015-11-21 at 17:06 +0100, Agustin Martin wrote: > 2015-11-14 15:25 GMT+01:00 Soeren D. Schulze >: > > I am not sure about those SIGPIPEs.  They occured to me, too, but I > > could > > just press 'c' in gdb and continue using iceweasel until the > > SIGSEGV.  On >

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

On Do, 2015-11-12 at 14:41 +0100, Soeren D. Schulze wrote: > Hello, > > the problem does not seem to occur any more with > gstreamer1.0-plugins-bad 1.6.1-1+b1 and iceweasel 38.4.0esr-1. > > Do you have any specific packages for me to test? Just a normal jessie installation without installing

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

On Do, 2015-11-12 at 15:35 +0100, Soeren D. Schulze wrote: > Am 12.11.2015 um 15:02 schrieb Sebastian Dröge: > > On Do, 2015-11-12 at 14:41 +0100, Soeren D. Schulze wrote: > > > Hello, > > > > > > the problem does not seem to occur any more with >

Bug#788708: Bug#799632: iceweasel: SIGSEGV when playing videos via gstreamer

On Di, 2015-11-10 at 20:31 +0100, Agustin Martin wrote: > On Mon, Sep 21, 2015 at 03:55:16AM +0200, Soeren D. Schulze wrote: > > Package: iceweasel > > Version: 38.2.1esr-1~deb8u1 > > Severity: important > > > > Approximately once every 10 hours of use, I experience a crash of > > Iceweasel. > >

Bug#788708: iceweasel: GStreamer causes segmentation fault

On Mo, 2015-11-09 at 18:45 +0100, Agustin Martin wrote: > Hi, gstreamer plugins maintainers > > I have unarchived this bug report to add more info on it. Not yet > reopened it for jessie because I am not fully sure that is is the one > to blame. > > I  am having some problems in jessie similar

Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

On Sa, 2015-10-31 at 20:39 +, Olly Betts wrote: > On Sat, Oct 31, 2015 at 02:16:28PM +0100, Moritz Muehlenhoff wrote: > > On Thu, May 21, 2015 at 02:31:29PM +0300, Sebastian Dröge wrote: > > > Hi Olly, > > > > > > On Do, 2015-05-21 at 01:24 +0100, Olly Bet

Bug#785926: Bug#731122: Initial patch for GStreamer 1.0 / farstream 0.2 support

On Fr, 2015-10-16 at 10:05 +0300, Sebastian Dröge wrote: > On Sun, 4 Oct 2015 22:51:55 +0200 Bernhard Schmidt wrote: > > > > I can't do that, as > > > > - my DD application is still in progress > > - I certainly don't want to NMU a multi-binary package wit

Bug#785926: Bug#731122: Initial patch for GStreamer 1.0 / farstream 0.2 support

On Sun, 4 Oct 2015 22:51:55 +0200 Bernhard Schmidt wrote: > > I can't do that, as > > - my DD application is still in progress > - I certainly don't want to NMU a multi-binary package with a library >   and five-digit popcon count as first action > > However, if someone

Bug#800660: gnome-keyring: crashes iceweasel when logging into a password-protected website

On Fri, 02 Oct 2015 10:20:49 +0200 =?utf-8?q?Rapha=C3=ABl_Hertzog?= wrote: > Since I upgraded to gnome-keyring 3.18, I'm no longer able to login into > password-protected website with iceweasel. It just gets stuck and I have > to kill it. > > In the logs I see this: > >

Bug#799677: pitivi: Incorrect depends, build-depends, and other issues

On Mon, 21 Sep 201509:27:23 -0400 Scott Kitterman wrote: > To start with, pitivi only builds against a single python3 version (the > default), not all versions, so it should build-dep on python3-dev vice > python3-all-dev. The python3-all-dev build-dep makes it appear on

Bug#799689: gst-python1.0: Missing python3 interpreter depends for python3-gst-1.0

On Mo, 2015-09-21 at 10:43 -0400, Scott Kitterman wrote: > The package uses python:Depends instead of python3:Depends for > python3-gst-1.0, so it does not end up with correct dependencies. > Fixing this gives a correct result. Please see the attached patch > which fixes this as well as

Bug#785840: gcompris: Please update to GStreamer 1.x

On So, 2015-09-20 at 15:33 +0200, Sebastian Dröge wrote: > Hi again, > > I shortly looked at the code in git in gstreamer.c. Not a single > change other than the build system and package dependencies should be > necessary here. FWIW, I'll send you a patch soonish. Seem to have s

Bug#785840: gcompris: Please update to GStreamer 1.x

On So, 2015-09-20 at 21:57 +0200, Yann Dirson wrote: > On Sun, Sep 20, 2015 at 08:36:06PM +0200, Sebastian Dröge wrote: > > On So, 2015-09-20 at 19:17 +0200, Sebastian Dröge wrote: > > > On So, 2015-09-20 at 15:33 +0200, Sebastian Dröge wrote: > > > > Hi again, >

Bug#785840: gcompris: Please update to GStreamer 1.x

Hi again, I shortly looked at the code in git in gstreamer.c. Not a single change other than the build system and package dependencies should be necessary here.

Bug#785840: gcompris: Please update to GStreamer 1.x

Hi, I forwarded this upstream a while ago without any response. Is gcompris still actively developed? https://bugzilla.gnome.org/show_bug.cgi?id=747949 Basically, replace the 0.10 build dependencies with 1.0. Then make things compile and work again. See this small porting guide here

Bug#785840: gcompris: Please update to GStreamer 1.x

On So, 2015-09-20 at 19:17 +0200, Sebastian Dröge wrote: > On So, 2015-09-20 at 15:33 +0200, Sebastian Dröge wrote: > > Hi again, > > > > I shortly looked at the code in git in gstreamer.c. Not a single > > change other than the build system and package dependencies

Bug#793628: Please remove unused build-dependency on liboil0.3-dev

On Sat, 25 Jul 2015 21:31:38 +0300 Sebastian =?ISO-8859-1?Q?Dr=F6ge?= wrote: > Package: psimedia > Severity: important > > Hi, > > please remove the build-dependency on liboil0.3-dev. It's apparently > not needed anymore as there is no binary dependency on the > corresponding

Bug#799174: Should not be part of next release

Package: liboil Severity: serious Tags: sid stretch liboil should not be part of the next release and should be removed, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792121 for the reasoning. Only one package is holding it back right now. signature.asc Description: This is a digitally

Bug#797227: segfault - gst_memory_unmap, libgstreamer

On Mi, 2015-09-02 at 17:32 +0900, Changwoo Ryu wrote: > Yes, I just have tested the patch on faad plugin at the GNOME > bugzilla 748571. And it fixes the problem. Thanks for testing, question is if I should upload a new package with the fix to unstable or we just wait until 1.6.0 is released...

Bug#797227: segfault - gst_memory_unmap, libgstreamer

Hi, On Mo, 2015-08-31 at 18:05 +0100, jnqnfe wrote: > > > Interesting... that doesn't make any sense unless something > > corrupted the stack :) Can you also run in valgrind with --track > > -origins=yes and provide the log? > > Sure. Just fyi, because loading iceweasel after a crash results

Bug#797227: segfault - gst_memory_unmap, libgstreamer

On Di, 2015-09-01 at 10:25 +0200, Vincent Lefevre wrote: > On 2015-09-01 11:07:28 +0300, Sebastian Dröge wrote: > > The gcc 5 transition might've broken something related to > > iceweasel, > > which is written in C++ and depends a lot on C++ libraries. Which >

Bug#797227: segfault - gst_memory_unmap, libgstreamer

On Di, 2015-09-01 at 11:28 +0300, Sebastian Dröge wrote: > On Di, 2015-09-01 at 10:25 +0200, Vincent Lefevre wrote: > > On 2015-09-01 11:07:28 +0300, Sebastian Dröge wrote: > > > The gcc 5 transition might've broken something related to > > > iceweasel, > > >

Bug#797227: segfault - gst_memory_unmap, libgstreamer

Hi, On Mo, 2015-08-31 at 16:41 +0100, jnqnfe wrote: > On Mon, 2015-08-31 at 17:36 +0300, Sebastian Dröge wrote: > > On Mo, 2015-08-31 at 15:29 +0100, jnqnfe wrote: > > > > > > > Can someone who is still able to reproduce this with 1.5.90 > > > > fr

Bug#797227: segfault - gst_memory_unmap, libgstreamer

Hi, On Sun, 30 Aug 2015 00:04:02 +0100 jnqnfe wrote: > Upgrading to gstreamer1.0-plugins-bad from experimental as someone > suggested resulted in the following package changes: > > The following NEW packages will be installed: > [...] > Iceweasel indeed no longer crashes now.

Bug#797227: segfault - gst_memory_unmap, libgstreamer

On Mo, 2015-08-31 at 15:29 +0100, jnqnfe wrote: > > > Can someone who is still able to reproduce this with 1.5.90 from > > experimental also install debug symbols for libc6, libglib2.0-0, > > all the GStreamer packages and then > > a) run with valgrind --track-origins=yes > > b) get a new

Bug#785916: landell: Please update to GStreamer 1.x

On Fr, 2015-08-21 at 00:11 +0200, Andreas Cadhalpun wrote: If you need any help with porting or have further questions, please feel free to also contact me privately. I'm also going to request the removal of gstreamer0.10-ffmpeg, since it is the last reverse-dependency of src:libpostproc

Bug#767423: tracker-extract SIGSEGV

Hi, can you get a backtrace of the crash with the following packages installed? libglib2.0-0-dbg libgstreamer1.0-0-dbg gstreamer1.0-plugins-base-dbg gstreamer1.0-plugins-good-dbg gstreamer1.0-plugins-bad-dbg gstreamer1.0 -plugins-ugly-dbg gstreamer1.0-libav-dbg Also please check if the problem

Bug#788601: pitivi: segfaults on start, 100% of the time

On Mo, 2015-06-22 at 10:28 +0200, Open BSD wrote: I'm not sure how to do that, i run jessie with verion 0.93-4.2 and there's no newer version in jessie backports? I did download the universal bundle (0.94) from the pitivi website but that includes all the dependencies and i think, as such,

Bug#788601: pitivi: segfaults on start, 100% of the time

On Thu, 18 Jun 2015 12:45:00 +0200 Open BSD gulpenergladia...@gmail.com wrote: this might be the same thing as in #732813 but i haven't tried it with another version. Hi, not too useful backtrace of the crash unfortunately but that looks like a problem somewhere between python-gi, GDK/GTK and

Bug#788601: pitivi: segfaults on start, 100% of the time

Hi, On Fr, 2015-06-12 at 23:11 -0500, John Goerzen wrote: Package: pitivi Version: 0.93-4.2 Severity: grave Justification: renders package unusable It just doesn't even start: (pitivi:26977): Clutter-WARNING **: clutter_x11_set_use_argb_visual() can only be used before calling

Bug#777024: gst segfault

On Fr, 2015-02-13 at 15:14 -0500, Michael Gilbert wrote: control: tag -1 pending Hi, I've uploaded an nmu fixing this issue to delayed/2. Please let me know if I should delay longer. thanks for the NMU! signature.asc Description: This is a digitally signed message part

Bug#769941: libgstreamer-plugins-base1.0-0: Iceweasel crashes with gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed

On Mi, 2014-12-17 at 09:35 +0100, webmbackslash wrote: Hi, i have this bug too. Attached is the valgrind output and it ended for me loading iceweasel for a few moments and showing killed. This is the command i used: valgrind --track-origins=yes --trace-children=yes --leak-check=full

Bug#769941: libgstreamer-plugins-base1.0-0: Iceweasel crashes with gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed

On Mo, 2014-11-17 at 19:13 +, George B. wrote: Package: libgstreamer-plugins-base1.0-0 Version: 1.4.4-2 Severity: critical Justification: breaks unrelated software Hello, Iceweasel has started crashing when I try and login into Google Mail. Looking at the backtrace it appears to be

Bug#769941: libgstreamer-plugins-base1.0-0: Iceweasel crashes with gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed

On Di, 2014-11-18 at 11:37 +, George B. wrote: On 18/11/14 09:22, Sebastian Dröge wrote: I assume it first started to appear when upgrading from 1.4.3 to 1.4.4 yesterday? I noticed it with GMail yesterday, but I haven't used that for a long time (I usually connect via Icedove). I

Bug#761019: gstreamer1.0 nmu

On So, 2014-11-02 at 10:41 +0100, Laurent Bigonville wrote: On Sun, 2 Nov 2014 00:52:23 -0400 Michael Gilbert mgilb...@debian.org wrote: Hello, Hi, I've uploaded an nmu fixing this issue. Please see attached. Well this is certainly a solution, not the solution IMHO. The dependencies

Bug#761019: gstreamer1.0 nmu

On So, 2014-11-02 at 12:03 +0100, Laurent Bigonville wrote: Le Sun, 02 Nov 2014 11:35:21 +0100, Sebastian Dröge sl...@coaxion.net a écrit : On So, 2014-11-02 at 10:41 +0100, Laurent Bigonville wrote: On Sun, 2 Nov 2014 00:52:23 -0400 Michael Gilbert mgilb...@debian.org wrote: Hello

Bug#764100: gst-plugins-bad1.0: build-depends on libgnutls-dev

On So, 2014-10-05 at 14:57 +0200, Andreas Metzler wrote: Package: gst-plugins-bad1.0 Version: 1.4.3-1 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ametz...@debian.org Usertags: gnutls3 gst-plugins-bad1.0 build-depends

Bug#764133: librtmp-dev misses dependency on libgnutls-dev and zlib1g-dev

Package: librtmp-dev Version: 2.4+20131018.git79459a2-4 Severity: serious Hi, librtmp-dev should have a dependency on libgnutls-dev and zlib1g-dev according to the pkg-config file: [...] Requires.private: gnutls,hogweed,nettle Libs: -L${libdir} -lrtmp -lz -lgmp [...] Without this packages

Bug#764133: librtmp-dev misses dependency on libgnutls-dev and zlib1g-dev

On So, 2014-10-05 at 20:29 +0300, Sebastian Dröge wrote: Package: librtmp-dev Version: 2.4+20131018.git79459a2-4 Severity: serious Hi, librtmp-dev should have a dependency on libgnutls-dev and zlib1g-dev according to the pkg-config file: [...] Requires.private: gnutls,hogweed,nettle

Bug#763433: Color format emulation breaks GStreamer's V4L2 support since 1.4.0

Package: libv4l-0 Version: 1.4.0-1 Severity: serious Hi, since version 1.4.0 the color format emulation in libv4l breaks GStreamer's v4l2 support. See this bug report for more details: https://bugzilla.gnome.org/show_bug.cgi?id=737521 In specific, this commit breaks it:

Bug#732680: insanity is no longer maintained upstream

Package: gst-qa-system Severity: serious Hi, please get the insanity/gst-qa-system package removed from Debian. It is no longer maintained upstream since years and there never was a release. This was mostly an experiment if such an approach can lead to useful results or not, and it failed. This

  1   2   3   4   >