Source: synthv1
Version: 0.8.6-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap
synthv1 fails to cross build from source, because configure.ac uses
AC_PATH_PROG for finding qmake. Thus it gets the build architecture
qmake. Since the behaviour of qmake is architecture-dependent
On Mon, Jun 04, 2018 at 12:47:48PM -0400, Reinhard Tartler wrote:
> Ok, thanks. That sounds like a good plan!
BTW, I'm not sure if Talos security actually reported these to the
censenta/mongoose upstream project or whether they're doing it
for the security buzz/advertising factor...
I saw that up
Your message dated Tue, 05 Jun 2018 10:34:54 +
with message-id
and subject line Bug#831630: fixed in idjc 0.8.17-1
has caused the Debian Bug report #831630,
regarding idjc: please make the build reproducible
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 05 Jun 2018 10:34:54 +
with message-id
and subject line Bug#888330: fixed in idjc 0.8.17-1
has caused the Debian Bug report #888330,
regarding idjc: FTBFS with FFmpeg 4.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Tue, 05 Jun 2018 10:34:54 +
with message-id
and subject line Bug#900754: fixed in idjc 0.8.17-1
has caused the Debian Bug report #900754,
regarding idjc: missing dependency on libogg
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Processing control commands:
> tag -1 pending
Bug #900754 [idjc] idjc: missing dependency on libogg
Added tag(s) pending.
--
900754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
__
Processing control commands:
> tag -1 pending
Bug #831630 [src:idjc] idjc: please make the build reproducible
Added tag(s) pending.
--
831630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> VA-API was not automatically probed in VLC 2.2. This is expected.
> VDPAU fails, and then VLC falls back to software decoding.
>
> In VLC 3.0, VA-API probing fails due to insufficient hardware
capabilities, so
> VLC uses software decoding as well. So no differences.
>
> --
> Rémi Denis-Courmont