Hi,
On Sun, Feb 16, 2014 at 07:41:02PM -0500, Reinhard Tartler wrote:
> On Sun, Feb 16, 2014 at 7:28 PM, peter green wrote:
> > We can't use the neon option because no arm port of debian gaurantees that
> > neon will be available. So I belive until the no-fpu options are made
> > compatible with
> -- Forwarded message --
> From: Thomas Orgis
> Date: Sun, Feb 16, 2014 at 5:46 AM
> Subject: Bug#738981: Switch to use generic_fpu for ARM
> To: 738...@bugs.debian.org
>
> There is no runtime detection in mpg123 for this and at least for the
> decision of fixed or floating poi
On 2014-02-16 22:50:40, Andrew Kelley wrote:
> Thank you for your feedback. I have addressed everything so far (in my own
> repository).
Great, I'll look at it.
> I tried to create a repository on alioth like this:
>
> $ ssh git.debian.org /git/pkg-multimedia/setup-repository libebur128.git
> Pe
Am Mon, 17 Feb 2014 10:00:48 +0200
schrieb Riku Voipio :
> Thanks Peter for explaining, this was how I ended up the suggestion
> in the bug.
>
> > I see. In that case, I'll have to leave the package as it until
> > something along those lines is implemented.
>
> Yes. The ideal solution is for t
caps_0.9.20-1_amd64.changes uploaded successfully to localhost
along with the files:
caps_0.9.20-1.dsc
caps_0.9.20.orig.tar.bz2
caps_0.9.20-1.debian.tar.xz
caps_0.9.20-1_amd64.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 17 Feb 2014 11:34:36 +0100
Source: caps
Binary: caps
Architecture: source amd64
Version: 0.9.20-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
Changed-By: Jaromír Mikeš
Description
On Mon, Feb 17, 2014 at 11:43:16AM +0100, Thomas Orgis wrote:
>Am Mon, 17 Feb 2014 10:00:48 +0200
>schrieb Riku Voipio :
>
>> Thanks Peter for explaining, this was how I ended up the suggestion
>> in the bug.
>>
>> > I see. In that case, I'll have to leave the package as it until
>> > something a
On 2014-02-16 22:50:40, Andrew Kelley wrote:
> Thank you for your feedback. I have addressed everything so far (in my own
> repository).
Looks good. Some comments on d/copyright: Please just use the short
name and not MIT License (Expat). For Modified BSD License this is
BSD-3-clause. You can also
Processing commands for cont...@bugs.debian.org:
> # unconfuse the bts
> notfixed 723172 1.3.2-1
Bug #723172 {Done: Aníbal Monsalve Salazar } [src:linbox]
linbox: FTBFS on s390: overloaded 'BlasMatrix(T&, size_t&, size_t&)' is
ambiguous
No longer marked as fixed in versions 1.3.2-1.
> found 7387
On Mon, Feb 17, 2014 at 2:18 PM, wrote:
> The following commit has been merged in the pristine-tar branch:
> commit 2a6a3866aebac28701e169bb9b86ce114c6adba7
> Author: Jaromír Mikeš
> Date: Mon Feb 17 15:17:15 2014 +0100
>
> pristine-tar data for eq10q_2.0~beta5.1.orig.tar.gz
Please repack
2014-02-17 15:35 GMT+01:00 Alessio Treglia :
> On Mon, Feb 17, 2014 at 2:18 PM,
> wrote:
> > The following commit has been merged in the pristine-tar branch:
> > commit 2a6a3866aebac28701e169bb9b86ce114c6adba7
> > Author: Jaromír Mikeš
> > Date: Mon Feb 17 15:17:15 2014 +0100
> >
> > pris
On Sun, Feb 16, 2014 at 5:14 AM, Jaromír Mikeš wrote:
> Hi Team.
>
> I prepared ste-plugins package a LADSPA plugins from Fons Adriaensen.
> Please can somebody review and possibly upload.
>
> DM flag would be great ;)
>
> I also searching for 2nd uploader :)
>
> best regards
Hi Jaromír,
I have
2014-02-17 16:31 GMT+01:00 Felipe Sateler :
> On Sun, Feb 16, 2014 at 5:14 AM, Jaromír Mikeš
> wrote:
> > Hi Team.
> >
> > I prepared ste-plugins package a LADSPA plugins from Fons Adriaensen.
> > Please can somebody review and possibly upload.
> >
> > DM flag would be great ;)
> >
> > I also sea
Source: cmus
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
Source: gmerlin-avdecoder
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/M
Source: gnash
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
Package: harvid
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/1
Hello,
On Thursday, 13 February 2014 at 17:27, Jean-Baptiste Kempf wrote:
> Dear Bálint,
>
> The new repository is a fork, and while I invited all the original
> developers to use a proper versionning system and join me, none of
> them seemed interested in that part. Adding developer keys to this
Source: k3b
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
C
FYI: The status of the caps source package
in Debian's testing distribution has changed.
Previous version: 0.9.16-2
Current version: 0.9.18-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
Source: linphone
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/
Package: vice
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
Package: lynkeos.app
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migrat
FYI: The status of the x42-plugins source package
in Debian's testing distribution has changed.
Previous version: 20140115-1
Current version: 20140115-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you wi
Dear Email Owner,
We are presently offering loans to interested persons at an affordable rate
with the help and assistance from our banks.
We offer secured loans to individuals and companies at low interest,we also
offer long and short term loans. Our firm has recorded a lot of breakthroughs
On Mon, Feb 17, 2014 at 1:56 PM, wrote:
> The annotated tag, debian/0.0.2-1 has been updated
> to f973a39b9f883387618687b078b1f6ef594a196d (tag)
> from 22596c5027bc0069cb3d0151440bd174fcb59c92 (which is now obsolete)
Jaromír (and anyone else that had cloned this repo), please del
ste-plugins_0.0.2-1_amd64.changes uploaded successfully to localhost
along with the files:
ste-plugins_0.0.2-1.dsc
ste-plugins_0.0.2.orig.tar.bz2
ste-plugins_0.0.2-1.debian.tar.xz
ste-plugins_0.0.2-1_amd64.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
binary:ste-plugins is NEW.
source:ste-plugins is NEW.
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override file about once a week.
___
Package: idjc
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
Source: gpac
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
Source: gst-libav1.0
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migrat
Package: guvcview
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration
Source: libquicktime
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migrat
Package: silan
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
Source: lives
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
Source: lightspark
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migratio
2014-02-17 17:57 GMT+01:00 Felipe Sateler :
> On Mon, Feb 17, 2014 at 1:56 PM,
> wrote:
> > The annotated tag, debian/0.0.2-1 has been updated
> > to f973a39b9f883387618687b078b1f6ef594a196d (tag)
> > from 22596c5027bc0069cb3d0151440bd174fcb59c92 (which is now
> obsolete)
>
> Jar
Source: libphash
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/
Package: mplayer2
Version: 2.0-701-gd4c5b7f-2
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
http
On Mon, Feb 17, 2014 at 3:28 PM, Jaromír Mikeš wrote:
> 2014-02-17 17:57 GMT+01:00 Felipe Sateler :
>
>> On Mon, Feb 17, 2014 at 1:56 PM,
>> wrote:
>> > The annotated tag, debian/0.0.2-1 has been updated
>> > to f973a39b9f883387618687b078b1f6ef594a196d (tag)
>> > from 22596c5027b
The package liblo runs a test suite at build time. This test suite
failed in mipsel (but not mips)[1]. I tried to reproduce the issue in
eder.d.o but it passed.
Liblo does use unaligned access (liblo had to be removed from sparc
for this reason).
But I'm confused as to why does the buildd error ou
2014-02-17 20:09 GMT+01:00 Felipe Sateler :
> On Mon, Feb 17, 2014 at 3:28 PM, Jaromír Mikeš
> wrote:
> > 2014-02-17 17:57 GMT+01:00 Felipe Sateler :
> >
> >> On Mon, Feb 17, 2014 at 1:56 PM,
> >> wrote:
> >> > The annotated tag, debian/0.0.2-1 has been updated
> >> > to f973a39b9f8833
On Mon, Feb 17, 2014 at 4:52 PM, Jaromír Mikeš wrote:
>
>
>
> 2014-02-17 20:09 GMT+01:00 Felipe Sateler :
>
>> On Mon, Feb 17, 2014 at 3:28 PM, Jaromír Mikeš
>> wrote:
>> > 2014-02-17 17:57 GMT+01:00 Felipe Sateler :
>> >
>> >> On Mon, Feb 17, 2014 at 1:56 PM,
>> >> wrote:
>> >> > The annotated
2014-02-17 21:00 GMT+01:00 Felipe Sateler :
> On Mon, Feb 17, 2014 at 4:52 PM, Jaromír Mikeš
> wrote:
> >
> >
> >
> > 2014-02-17 20:09 GMT+01:00 Felipe Sateler :
> >
> >> On Mon, Feb 17, 2014 at 3:28 PM, Jaromír Mikeš
> >> wrote:
> >> > 2014-02-17 17:57 GMT+01:00 Felipe Sateler :
> >> >
> >> >>
eq10q_2.0~beta5.1~repack0-1_amd64.changes uploaded successfully to localhost
along with the files:
eq10q_2.0~beta5.1~repack0-1.dsc
eq10q_2.0~beta5.1~repack0.orig.tar.gz
eq10q_2.0~beta5.1~repack0-1.debian.tar.xz
eq10q_2.0~beta5.1~repack0-1_amd64.deb
Greetings,
Your Debian queue dae
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 17 Feb 2014 15:19:16 +0100
Source: eq10q
Binary: eq10q
Architecture: source amd64
Version: 2.0~beta5.1~repack0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
Changed-By: Jaromír Mik
* Felipe Sateler (fsate...@gmail.com) [140217 20:33]:
> The package liblo runs a test suite at build time. This test suite
> failed in mipsel (but not mips)[1]. I tried to reproduce the issue in
> eder.d.o but it passed.
>
> Liblo does use unaligned access (liblo had to be removed from sparc
> for
On Mon, Feb 17, 2014 at 5:11 PM, Jaromír Mikeš wrote:
> 2014-02-17 21:00 GMT+01:00 Felipe Sateler :
>
>> On Mon, Feb 17, 2014 at 4:52 PM, Jaromír Mikeš
>> wrote:
>> >
>> >
>> >
>> > 2014-02-17 20:09 GMT+01:00 Felipe Sateler :
>> >
>> >> On Mon, Feb 17, 2014 at 3:28 PM, Jaromír Mikeš
>> >> wrote:
On Mon, Feb 17, 2014 at 6:28 PM, Andreas Barth wrote:
> * Felipe Sateler (fsate...@gmail.com) [140217 20:33]:
>> The package liblo runs a test suite at build time. This test suite
>> failed in mipsel (but not mips)[1]. I tried to reproduce the issue in
>> eder.d.o but it passed.
>>
>> Liblo does u
Processing control commands:
> forwarded -1 https://github.com/x42/harvid/pull/2
Bug #739304 [harvid] FTBFS with libav10
Set Bug forwarded-to-address to 'https://github.com/x42/harvid/pull/2'.
--
739304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739304
Debian Bug Tracking System
Contact o
Control: forwarded -1 https://github.com/x42/harvid/pull/2
On 2014-02-17 17:01:00, Moritz Muehlenhoff wrote:
> cc -c -o decoder_ctrl.o -g -O2 -fstack-protector --param=ssp-buffer-size=4
> -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2
>`pkg-config --cflags libavcodec libavformat libavut
Is there a reason to decide one way or the other to put dh_installexamples
into the debian/rules file versus creating a debian/.examples file?
On Mon, Feb 17, 2014 at 5:05 PM, wrote:
> The following commit has been merged in the experimental branch:
> commit 7e2ac941689af2ddc0039eae5f4fcf649470
Hi,
there are too many SPAM mails on this pkg-multimedia-maintainers list.
Please manually filter the mails from non-subscribers (excluding
white-listing known good addresses).
--
Benjamin Drung
Debian & Ubuntu Developer
___
pkg-multimedia-maintainer
Package: shotdetect
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migrati
Package: yorick-av
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migratio
Source: qmmp
Severity: important
Hi,
your package fails to build from source against libav 10 (currently
packaged in experimental). This bug will become release-critical
at some point when the libav10 transition starts.
Migration documentation can be found at
https://wiki.libav.org/Migration/10
On Mon, Feb 17, 2014 at 7:47 AM, Sebastian Ramacher wrote:
> Please include the patch in the Debian package.
>
OK I have done this and the copyright update. I also added your
GNUInstallDirs patch. Please take a look and make sure it is correct.
Lintian told me to add Pre-Depends: multiarch-suppor
2014-02-17 22:37 GMT+01:00 Felipe Sateler :
> On Mon, Feb 17, 2014 at 5:11 PM, Jaromír Mikeš
> wrote:
> > 2014-02-17 21:00 GMT+01:00 Felipe Sateler :
> >
> >> On Mon, Feb 17, 2014 at 4:52 PM, Jaromír Mikeš
> >> wrote:
> >> >
> >> >
> >> >
> >> > 2014-02-17 20:09 GMT+01:00 Felipe Sateler :
> >> >
On Sun, Feb 16, 2014 at 03:25:08PM -0500, Reinhard Tartler wrote:
> On Sun, Feb 16, 2014 at 12:58 PM, Reimar Döffinger
> wrote:
> > What would constitute a constructive comment?
>
> Ideally "I am interested in making mplayer work against the libavcodec
> that we have in Debian, and this is my wor
On 2014-02-17 18:36:45, Andrew Kelley wrote:
> On Mon, Feb 17, 2014 at 7:47 AM, Sebastian Ramacher
> wrote:
>
> > Please include the patch in the Debian package.
> >
>
> OK I have done this and the copyright update. I also added your
> GNUInstallDirs patch. Please take a look and make sure it is
libav_10~beta1-2_source+amd64.changes uploaded successfully to localhost
along with the files:
libav_10~beta1-2.dsc
libav_10~beta1.orig.tar.xz
libav_10~beta1-2.debian.tar.gz
libav-tools_10~beta1-2_amd64.deb
libav-dbg_10~beta1-2_amd64.deb
libavutil53_10~beta1-2_amd64.deb
libavcodec55_1
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 17 Feb 2014 22:07:03 +
Source: libav
Binary: libav-tools libav-dbg libav-doc libavutil53 libavcodec55 libavdevice54
libavformat55 libavfilter4 libswscale2 libavutil-dev libavcodec-dev
libavdevice-dev libavforma
Your message dated Tue, 18 Feb 2014 03:20:11 +
with message-id
and subject line Bug#738599: fixed in libav 6:10~beta1-2
has caused the Debian Bug report #738599,
regarding fails to decode H264: "Different bit depth between chroma and luma is
not implemented"
to be marked as done.
This means
Am Montag, den 17.02.2014, 17:19 -0500 schrieb Andrew Kelley:
> Is there a reason to decide one way or the other to put
> dh_installexamples into the debian/rules file versus creating a
> debian/.examples file?
Well, actually you need to have the call to dh_installexamples in
debian/rules in orde
64 matches
Mail list logo
