Package: mediatomb
Version: 0.12.1-4
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
The current version of mediatomb (in wheezy) fails to build from source
with libmp4v2 support enabled.
* What exactly
Package: mediatomb
Version: 0.12.1-4
Severity: serious
Tags: upstream patch
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
The current version of mediatomb (in wheezy) fails to build from source
with the current version of libavformat.
*
Hi team,
in order to keep the differences between patches that are worked on by
different people as small as possible, I propose to present a common
~/.quiltrc file and recommend its usage on our
DebianMultimedia/DevelopPackaging [0] wiki page.
As already suggested by Jonas in [1] I suppose
Package: mediatomb
Version: 0.12.1-4
Severity: normal
Tags: upstream patch
Mediatomb does not recognize symbolics links to media files.
* What exactly did you do (or not do) that was effective (or
ineffective)?
1. Add directory to Mediatomb's index through web interface.
On 12-06-18 at 10:58am, Fabian Greffrath wrote:
in order to keep the differences between patches that are worked on by
different people as small as possible, I propose to present a common
~/.quiltrc file and recommend its usage on our
DebianMultimedia/DevelopPackaging [0] wiki page.
...as
On Mon, Jun 18, 2012 at 10:58:54AM +0200, Fabian Greffrath wrote:
Hi team,
in order to keep the differences between patches that are worked on
by different people as small as possible, I propose to present a
common ~/.quiltrc file and recommend its usage on our
Hi all,
good idea, Fabian!
On Mon, Jun 18, 2012 at 10:58 AM, Fabian Greffrath fab...@greffrath.com wrote:
$ cat ~/.quiltrc
QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
The following is the content of my ~/.quiltrc:
QUILT_PATCHES=debian/patches
QUILT_DIFF_OPTS=--show-c-function
Il 18/06/2012 11:22, Jonas Smedegaard ha scritto:
On 12-06-18 at 10:58am, Fabian Greffrath wrote:
...but why only team-wide? How about instead pushing it as a Debian-wide
common practice (which I believe some already consider it - try search
wiki and other places for existing guides) and
jalv_1.0.0~dfsg0-2_amd64.changes uploaded successfully to localhost
along with the files:
jalv_1.0.0~dfsg0-2.dsc
jalv_1.0.0~dfsg0-2.debian.tar.gz
jalv_1.0.0~dfsg0-2_amd64.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Accepted:
jalv_1.0.0~dfsg0-2.debian.tar.gz
to main/j/jalv/jalv_1.0.0~dfsg0-2.debian.tar.gz
jalv_1.0.0~dfsg0-2.dsc
to main/j/jalv/jalv_1.0.0~dfsg0-2.dsc
jalv_1.0.0~dfsg0-2_amd64.deb
to main/j/jalv/jalv_1.0.0~dfsg0-2_amd64.deb
Changes:
jalv (1.0.0~dfsg0-2) unstable; urgency=low
.
*
Am 18.06.2012 12:39, schrieb Giulio Paci:
Here are the Debian-wide suggestions:
http://www.debian.org/doc/manuals/maint-guide/modify.en.html
Indeed, thank you very much for the pointer.
Should we refer to this chapter in our wiki page?
- Fabian
On 12-06-18 at 01:08pm, Fabian Greffrath wrote:
Am 18.06.2012 12:39, schrieb Giulio Paci:
Here are the Debian-wide suggestions:
http://www.debian.org/doc/manuals/maint-guide/modify.en.html
Indeed, thank you very much for the pointer.
Should we refer to this chapter in our wiki page?
Fine
Am 18.06.2012 13:25, schrieb Jonas Smedegaard:
Only problem I can se is the risk of our team documentation getting too
big - but that's not an issue here IMO (also not your original proposal
of writing things locally). On the contrary I appreciate your pushing
to _more_ documentation. Thanks!!
libffado_2.0.99+svn2163-2_amd64.changes uploaded successfully to localhost
along with the files:
libffado_2.0.99+svn2163-2.dsc
libffado_2.0.99+svn2163-2.debian.tar.gz
ffado-mixer-qt4_2.0.99+svn2163-2_all.deb
libffado-dev_2.0.99+svn2163-2_amd64.deb
libffado2_2.0.99+svn2163-2_amd64.deb
Accepted:
ffado-dbus-server_2.0.99+svn2163-2_amd64.deb
to main/libf/libffado/ffado-dbus-server_2.0.99+svn2163-2_amd64.deb
ffado-mixer-qt4_2.0.99+svn2163-2_all.deb
to main/libf/libffado/ffado-mixer-qt4_2.0.99+svn2163-2_all.deb
ffado-tools_2.0.99+svn2163-2_amd64.deb
to
petri-foo_0.0.2+20120606.gitd2f92c9-1_amd64.changes uploaded successfully to
localhost
along with the files:
petri-foo_0.0.2+20120606.gitd2f92c9-1.dsc
petri-foo_0.0.2+20120606.gitd2f92c9.orig.tar.gz
petri-foo_0.0.2+20120606.gitd2f92c9-1.debian.tar.gz
Your message dated Mon, 18 Jun 2012 16:18:21 +
with message-id e1sgeej-0007xk...@franck.debian.org
and subject line Bug#670985: fixed in libffado 2.0.99+svn2163-2
has caused the Debian Bug report #670985,
regarding jackd2: firewire ERR: Incompatible libffado version!
to be marked as done.
Accepted:
petri-foo-dbg_0.0.2+20120606.gitd2f92c9-1_amd64.deb
to main/p/petri-foo/petri-foo-dbg_0.0.2+20120606.gitd2f92c9-1_amd64.deb
petri-foo_0.0.2+20120606.gitd2f92c9-1.debian.tar.gz
to main/p/petri-foo/petri-foo_0.0.2+20120606.gitd2f92c9-1.debian.tar.gz
#
# bts-link upstream status pull for source package src:gnome-mplayer
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #677233 (http://bugs.debian.org/677233)
# Bug title: gnome-mplayer: please
Hi,
m68k currently has no libpostproc-dev and friends, built from src:libav.
How do you recommend to bootstrap this, considering several (at least
four) build dependencies of libav, all codecs or something like that,
build-depend on libav’s binaries again? Can libav be built without any
of those
Carnaby Street, Covent Garden
Soho, Londres WC2H
Reino Unido
E-mail del usuario,
¡Felicitaciones! Su correo electrónico fue seleccionado ganador del 14 º Premio
de la suerte FACEBOOK LA CARIDAD ESPAÑOLA 500.000.00GBP.We de organizar este
programa de forma aleatoria usando todos los
καλές ειδήσεις, καλές ειδήσειςρολόι μάρκας, φωτογραφική μηχανή, φορητό υπολογιστή, τηλεόραση, iPhone, iPad .η τιμή είναι πολύ χαμηλότερη, η ναυτιλία είναι ελεύθερη
www. mnhraal.com___
pkg-multimedia-maintainers mailing list
22 matches
Mail list logo
