2013/8/31 Sebastian Ramacher
>
> Done.
>
Thank you!
___
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 commands for cont...@bugs.debian.org:
> # Saturday 31 August 20:03:20 UTC 2013
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: href="http://packages.qa.debian.org/pyliblo";>pyliblo
> tags 705044 +
Your message dated Sat, 31 Aug 2013 15:39:29 +
with message-id
and subject line Bug#720440: fixed in mpg123 1.15.3-2
has caused the Debian Bug report #720440,
regarding mpg123: mpg123 does not build LFS wrappers on kfreebsd-i386
to be marked as done.
This means that you claim that the problem
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 31 Aug 2013 15:26:50 +0200
Source: mpg123
Binary: mpg123 libmpg123-0 libmpg123-dev
Architecture: i386 source
Version: 1.15.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
Changed-B
On Fri, Aug 30, 2013 at 11:01 PM, Christoph Egger wrote:
> mplayer2 segfaults here:
static void allocate_xvimage(struct vo *vo, int foo)
{
[..]
{
ctx->xvimage[foo] =
(XvImage *) XvCreateImage(x11->display, x11->xv_port,
ctx->xv_form
On Sat, Aug 31, 2013 at 2:26 PM, Thomas Orgis wrote:
> (I'm also CCing the FreeBSD port maintainer, as I imagine they want that
> handled, too.)
>
> Am Sat, 31 Aug 2013 10:03:46 +0200
> schrieb Reinhard Tartler :
>
>> Thomas, may I have your opinion on this patch? If you are d'accord,
>> I'd uploa
mpg123_1.15.3-2_multi.changes uploaded successfully to localhost
along with the files:
mpg123_1.15.3-2.dsc
mpg123_1.15.3.orig.tar.bz2
mpg123_1.15.3-2.debian.tar.gz
mpg123_1.15.3-2_i386.deb
libmpg123-0_1.15.3-2_i386.deb
libmpg123-dev_1.15.3-2_i386.deb
Greetings,
Your Debian que
(I'm also CCing the FreeBSD port maintainer, as I imagine they want that
handled, too.)
Am Sat, 31 Aug 2013 10:03:46 +0200
schrieb Reinhard Tartler :
> Thomas, may I have your opinion on this patch? If you are d'accord,
> I'd upload it to debian/unstable for further testing.
OK, I see that I ne
binary:python-liblo-docs is NEW.
binary:python3-liblo 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.
___
pyliblo_0.9.1-3_amd64.changes uploaded successfully to localhost
along with the files:
pyliblo_0.9.1-3.dsc
pyliblo_0.9.1-3.debian.tar.gz
python-liblo_0.9.1-3_amd64.deb
python3-liblo_0.9.1-3_amd64.deb
pyliblo-utils_0.9.1-3_all.deb
python-liblo-docs_0.9.1-3_all.deb
Greetings,
Yo
On 2013-08-31 12:37:30, Jaromír Mikeš wrote:
> 2013/8/30 Sebastian Ramacher
>
> >
> > On 2013-08-28 12:25:09, Jaromír Mikeš wrote:
> > > Should something else to be done?
> >
> > I added some files to debian/clean and code to remove build/ in
> > debian/rules prevent FTBFS if built twice in a row
2013/8/30 Sebastian Ramacher
>
> On 2013-08-28 12:25:09, Jaromír Mikeš wrote:
> > Should something else to be done?
>
> I added some files to debian/clean and code to remove build/ in
> debian/rules prevent FTBFS if built twice in a row. I also added a DEP-8
> test for the python3-liblo package.
Hi
On 2013-08-31 14:31:31, shirish शिरीष wrote:
> Hi all,
> Any update on getting the three packages from experimental to unstable.
>
> I am guessing these are the experimental versions which need to come
> down to sid/unstable.
>
> $ apt-cache policy libopencv-core2.4
> libopencv-core2.4:
> I
Hi all,
Any update on getting the three packages from experimental to unstable.
I am guessing these are the experimental versions which need to come
down to sid/unstable.
$ apt-cache policy libopencv-core2.4
libopencv-core2.4:
Installed: (none)
Candidate: 2.4.6.1+dfsg-0exp1
Version table:
On Wed, Aug 28, 2013 at 10:24 AM, Thomas Orgis wrote:
> The mpg123 header specifies off_t as argument.
> When off_t is always 64 bits (could you possibly set
> _FILE_OFFSET_BITS=32 ?!), there is no justification for _32 functions
> at all! So, you only want lfs_alias for [no suffix] -> _64. You do
15 matches
Mail list logo