On Wed, Mar 13, 2013 at 10:17 PM, Paul Gevers elb...@debian.org wrote:
On 03/11/13 10:40, Fabian Greffrath wrote:
/usr/bin/gcc -pipe -fmessage-length=0 -Wall -g2 -O3 -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -D__LIBHB__
Your message dated Thu, 14 Mar 2013 11:17:45 +
with message-id e1ug6al-0003m3...@franck.debian.org
and subject line Bug#692381: fixed in yafaray 0.1.2+really0.1.2~beta5-4
has caused the Debian Bug report #692381,
regarding yafaray: FTBFS against python3.3
to be marked as done.
This means that
On 2013-02-21 18:35, Reuben Thomas r...@sc3d.org wrote:
The 2.1.8 release itself removes the Debian packaging, so I can't
install it as easily as I did the pre-release, so it would be even
nicer therefore if the Debian package were updated!
I updated the packaging, which can be found at:
tag 701114 confirmed
___
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:
tag 701114 confirmed
Bug #701114 [easytag] easytag: Please update to 2.1.8
Added tag(s) confirmed.
End of message, stopping processing here.
Please contact me if you need assistance.
--
701114:
#
# bts-link upstream status pull for source package vlc
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #665732 (http://bugs.debian.org/665732)
# Bug title: vlc: GUI latency/unresponsiveness to
Hello,
It was suggested I write to this address for questions about packaging
liblo. I am the liblo maintainer, and I'm starting to prepare for a
new upstream release 0.27 of this library. I just wanted to verify a
few things before doing the release.
My goal for this release is to ensure that
On 14-03-13 07:11, Reinhard Tartler wrote:
On Wed, Mar 13, 2013 at 10:17 PM, Paul Gevers elb...@debian.org wrote:
Yes, well, they replaced their (first) liba52 patch by a different one.
So, how to handle this? (My C knowledge is not so good that I can see
the solution).
- I have no clue if
