On Sat, May 31, 2014 at 09:16:10PM +0200, Benjamin Drung wrote:
There are discussions about supporting wx3.0 (and making it the
default), but no code changes has landed in SVN so far. I do not know
the current status and why there isn't any progress. Lack of
manpower/time or bugs? That's why I
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 27 May 2014 14:07:51 +0200
Source: libdvdread
Binary: libdvdread4 libdvdread-dbg libdvdread-dev
Architecture: source amd64
Version: 4.2.1-2~bpo70+1
Distribution: wheezy-backports
Urgency: medium
Maintainer: Debian
--
Γεια σας,
Σας ενδιαφέρει σε ένα οικονομικό δάνειο
στο 2%;
επικοινωνήστε μαζί μου για λεπτομέρειες
και προϋποθέσεις.
ταχυδρομείο μου: ap...@live.fr
σας ευχαριστώ
___
pkg-multimedia-maintainers mailing list
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 27 May 2014 12:15:20 +0200
Source: xbmc
Binary: xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev
xbmc-eventclients-wiiremote xbmc-eventclients-j2me xbmc-eventclients-ps3
xbmc-eventclients-xbmc-send
rtmidi_2.0.1~ds0-3.1_amd64.changes uploaded successfully to localhost
along with the files:
librtmidi1_2.0.1~ds0-3.1_amd64.deb
librtmidi-dev_2.0.1~ds0-3.1_amd64.deb
librtmidi-dbg_2.0.1~ds0-3.1_amd64.deb
rtmidi_2.0.1~ds0-3.1.dsc
rtmidi_2.0.1~ds0-3.1.debian.tar.xz
Greetings,
Your
control: reassign -1 src:rtmidi
control: tags -1 +patch
Hi,
It seems that is caused by lack of RtError.h in librtmidi-dev package.
I've updated it as attached patch and midisnoop built fine, so upload it
to 10-delay queue. Please check and consider to apply it, thanks.
--
Regards,
Hideki
Processing control commands:
reassign -1 src:rtmidi
Bug #747775 [src:midisnoop] midisnoop: FTBFS: error: RtError.h: No such file or
directory
Bug reassigned from package 'src:midisnoop' to 'src:rtmidi'.
No longer marked as found in versions midisnoop/0.1.2~repack0-2.
Ignoring request to alter
FYI: The status of the blender source package
in Debian's testing distribution has changed.
Previous version: 2.70a-1
Current version: 2.70a-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
forked-daapd_20.0+git20140530+gc740e6e-1_amd64.changes uploaded successfully to
localhost
along with the files:
forked-daapd_20.0+git20140530+gc740e6e-1_amd64.deb
forked-daapd_20.0+git20140530+gc740e6e-1.dsc
forked-daapd_20.0+git20140530+gc740e6e.orig.tar.xz
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 31 May 2014 23:17:37 +0700
Source: forked-daapd
Binary: forked-daapd
Architecture: source amd64
Version: 20.0+git20140530+gc740e6e-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
mpv_0.4.0~git20140601-1_amd64.changes uploaded successfully to localhost
along with the files:
mpv_0.4.0~git20140601-1_amd64.deb
mpv-dbg_0.4.0~git20140601-1_amd64.deb
libmpv0_0.4.0~git20140601-1_amd64.deb
libmpv-dev_0.4.0~git20140601-1_amd64.deb
libmpv-dbg_0.4.0~git20140601-1_amd64.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 01 Jun 2014 20:17:58 +0200
Source: mpv
Binary: mpv mpv-dbg libmpv0 libmpv-dev libmpv-dbg
Architecture: source amd64
Version: 0.4.0~git20140601-1
Distribution: experimental
Urgency: medium
Maintainer: Debian
Dan,
On Sat, May 31, 2014 at 12:39 AM, Debian testing autoremoval watch
nore...@release.debian.org wrote:
supercollider 1:3.6.3~repack-5 is marked for autoremoval from testing on
2014-06-14
It is affected by these RC bugs:
746917: supercollider: ftbfs with GCC-4.9
We need to fix this. I
libav_10.1-1~bpo70+1_amd64+source.changes uploaded successfully to localhost
along with the files:
libav_10.1-1~bpo70+1.dsc
libav_10.1.orig.tar.xz
libav_10.1-1~bpo70+1.debian.tar.gz
libav-doc_10.1-1~bpo70+1_all.deb
libavcodec-extra_10.1-1~bpo70+1_all.deb
binary:libavformat55 is NEW.
binary:libavdevice54 is NEW.
binary:libavutil53 is NEW.
binary:libavcodec55 is NEW.
binary:libavcodec-extra-55 is NEW.
binary:libavfilter4 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was
xbmc-pvr-addons_12.0+79+ge1c3fb1+dfsg1-5~bpo70+1_amd64.changes uploaded
successfully to localhost
along with the files:
xbmc-pvr-addons_12.0+79+ge1c3fb1+dfsg1-5~bpo70+1.dsc
xbmc-pvr-addons_12.0+79+ge1c3fb1+dfsg1-5~bpo70+1.debian.tar.gz
Your message dated Mon, 02 Jun 2014 10:10:49 +0700
with message-id 538beb39.6060...@balintreczey.hu
and subject line Re: forked-daapd: Does not start; using
/etc/init.d/forked-daapd start it gives an ERROR.
has caused the Debian Bug report #707630,
regarding forked-daapd: Does not start; using
Your message dated Mon, 02 Jun 2014 10:17:58 +0700
with message-id 538bece6.8010...@balintreczey.hu
and subject line Re: forked-daapd: Dies before scanning whole library with
ffmpeg error
has caused the Debian Bug report #702899,
regarding forked-daapd: Dies before scanning whole library with
binary:xbmc-pvr-vuplus is NEW.
binary:xbmc-pvr-tvheadend-hts is NEW.
binary:xbmc-pvr-njoy is NEW.
binary:xbmc-pvr-iptvsimple is NEW.
binary:xbmc-pvr-demo is NEW.
binary:xbmc-pvr-argustv is NEW.
binary:xbmc-pvr-vdr-vnsi is NEW.
binary:vdr-plugin-vnsiserver is NEW.
Hi,
There are quite a lot (18) security issues tracked as open for the
Libav Debian packages:
https://security-tracker.debian.org/tracker/source-package/libav
I think many of them have already been fixed, but I'm not familiar
enough with the Libav code to tell which ones.
Could someone actively
gxtuner 2.1-1 is marked for autoremoval from testing on 2014-06-16
It is affected by these RC bugs:
748545: gxtuner: Does not work - starts, but does nothing
___
pkg-multimedia-maintainers mailing list
21 matches
Mail list logo
