Package: minidlna
Version: 1.1.2+dfsg-1.1
Severity: minor
Tags: patch
Dear Maintainer,
Upstream published a pre-compiled, statically linked, tarball along with 3.1.3
named "minidlna-1.1.3_static". This causes uscan to think the "precompiled"
tarball is the new source tarball. It also adds a warni
Dear Matthias,
Looking at the minidlna 1.1.1 changelog makes me think this bug was
fixed with the recent upload and build of 1.1.2 in sid and testing:
> 1.1.1 - Released 01-Nov-2013 [...]
> - Don't require a configured network interface to start up.
There are some more related upstream fixes in
Control: forwarded -1 https://sourceforge.net/p/minidlna/bugs/246/
I observed the same thing after adding a new album with songs by various
artists: the "Albums" list has duplicated sub-directories with the
album's name for each artist. Each sub-directory contains only songs by
one artist.
Intere
Hi,
First of all, judging by the code, this is probably unrelated to
scanning media. Only 1 child process should be forked to scan the media
directory.
However, each HTTP request for media is serviced through a newly forked
child process. Requesting a lot of pics at a high rate (some clients
prob
Hi,
Perhaps part of a solution for this bug is to include and use the
upstream minidlna.service systemd unit, if that is allowed in Debian.
This bug sounds like minidlna works fine with SysV init anyway.
The unit file has "After=network.target". It works for me on my Arch
Linux install, which has
Package: minidlna
Version: 1.1.2+dfsg-1
Severity: normal
Dear Maintainer,
I was testing the libav10 patch and started minidlna with the -d
(debug / no-fork) option. minidlna instantly segfaulted.
Katsuhiko Takahashi already reported/commented on this on gitorious.org:
It is probably due to commi
Hi,
This could also be a bug in tracker, because gnome-music just queries
tracker for a list of music files instead of looking them up directly.
Tracker seems to break occasionally, for example it forgot about some
music files that I've added shortly before shutting down my computer.
You can use
tags 747813 fixed-upstream
thanks
Hi Benoit,
minidlna 1.1.3 claims support for libav10, so the patch is no longer
needed. Upgrading to the latest upstream release should fix this.
Cheers,
Florian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscr
Hi Plamen,
I think this bug report is a duplicate of bug 747813. Can you confirm
this? (Debian does not ship ffmpeg, only libav AFAIK.)
Cheers,
Florian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia
This is only tested to compile using libav10 from sid. While it fixes
the FTFBS for me, I haven't tested to see if it breaks any
functionality.
---
metadata.c | 44 ++--
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/metadata.c b/metadata.c
Have you checked to make sure users are allowed to create enough inotify
watches? This is a frequent minidlna issue when having more than just a
few media files.
It'd be nice to add a comment about this to minidlna.conf.
See the Arch wiki:
https://wiki.archlinux.org/index.php/MiniDLNA#Automatic_M
17 00:00:00 2001
From: Florian Will
Date: Thu, 15 May 2014 11:18:57 +0200
Subject: [PATCH] Fix FTBFS with libav10
Two upstream commits squashed into one:
361bc3: metadata: add libavcodec > 54 compatibility
05cde8: metadata: more libav10 compatibility changes
---
libav.h
Hi,
about the "undefined reference to `vpx_codec_destroy'" and similar vpx*
linker errors on armel and armhf:
The builds have "use_system_vpx=1" defined for gyp. However, upstream
probably dropped support for that flag, or never supported it -- there's
no appearance of that "use_system_vpx" strin
Hi,
there's actually a chromium addon (Chromium App? Or whatever Google
calls these..) for this feature available from the "Chrome WebStore".
It's called "AutoScroll".
https://chrome.google.com/webstore/detail/occjjkgifpmdgodlplnacmkejpdionan
I'm afraid the implementation might be a hack, as it
Hi,
On Wed, 13 Aug 2014 21:07:42 -0400 Reinhard Tartler
wrote:
> OK, I've let me amd64 workstation try to build all packages in jessie
> listed on the URL above. Here are the results:
[..]
> mediatomb PASS
> mlt PASS
[..]
Where's minidlna? It's in jessie since June and listed on the transition
t
Hi Ghis,
The tracker bug you noticed is fixed in 1.0.2. It was released and
uploaded to sid on July 10. Due to an ongoing upower transition, it is
not yet in testing.
Changelog:
https://mail.gnome.org/archives/tracker-list/2014-July/msg8.html
* Fixes: GB#729968, GLib-GIO-CRITICAL **: g_file_
Package: wnpp
Severity: wishlist
* Package name: screencloud
Version : 1.1.6
Upstream Author : Olav Sortland Thoresen
* URL : http://www.screencloud.net (online service)
http://www.github.com/olav-st/screencloud (source)
* License : GPL2 or
Package: libpythonqt-dev
Version: 2.1.0~svn247-1
Severity: normal
Dear Possible Future Maintainer,
The libpythonqt-dev package is missing one header file that is included with
the orig tarball but not getting installed, gui/PythonQtScriptingConsole.h.
Cheers,
Florian
-- System Information:
Deb
Source: pythonqt
Version: 2.1.0~svn247-1
Severity: normal
Dear Maintainer,
Some of the Qt classes are not available in python when using the debian
package. For example, the PythonQt.QtUiTools.QUiLoader class is missing.
CMakeLists.txt defines a "PythonQt_Wrap_QtAll" option that defaults to OFF.
24 14:35:19.0 +0200
@@ -1,3 +1,10 @@
+pythonqt (2.1.0~svn247-2) UNRELEASED; urgency=medium
+
+ * build wrapper for every supported Qt class
+ * install gui/PythonQtScriptingConsole.h
+
+ -- Florian Will Thu, 24 Jul 2014 14:19:52 +0200
+
pythonqt (2.1.0~svn247-1) unstable; urgenc
Control: tags -1 patch
The debdiff I posted for bug #755901 solves this bug as well.
A simple *.install change was not enough, since the upstream
CMakeLists.txt fails to install the header, too. I confirmed with
upstream (see link below) that this is indeed a bug and modified the
cmakebuildsystem
Hello again,
I actually tried to do this myself as a fun little "improve Debian
packaging skills" project, and it kind-of works already. It requires two
fixes for the pythonqt package (patches filed).
There is a github repository where plugins are downloaded from by
screencloud, and I just added
Hi,
Am 27.07.2014 um 04:27 schrieb Carlo Contavalli:
> It also describe a "listening_address"
> in the default config file, and corresponding man page.
I'm sure you meant "listening_ip" here, like in your mail subject.
> - the daemon rejects the option as invalid
The -a option was apparently re
Package: minidlna
Version: 1.1.4+dfsg-3
Severity: minor
Dear Maintainer,
I have the "db_dir" set to /tmp because the minidlna instance on my computer
is only for development purposes, the "actual" minidlna instance I use is on
another machine.
I've noticed that I no longer get logs in /var/log/m
Hi Simon,
> Is this a bug, or am I missing something?
Upstream ticket:
http://sourceforge.net/p/minidlna/bugs/218/
The -i cmdline and network_interface config options appear to be
unrelated to the HTTP listening socket. Maybe related to SSDP? I don't
really understand the code in getifaddr.c aft
Tags: fixed-upstream
Dear Benoît,
I have verified that minidlna 1.1.4, downloaded from upstream and
without any kind of patch, builds fine with gcc 5 from experimental. It
also solves all the related "inline function declared but never defined"
warnings.
I don't think there's an isolated patch /
Hi everyone,
On Tue, 3 Mar 2015 11:18:28 +0300 Alexander GQ Gerasiov
wrote:
> Could you try version 1.1.4 from unstable to check is this version
> still affected?
I think we can assume that this bug was fixed in 1.1.1, see the release
notes:
> - Don't require a configured network interface to s
Dear Roland,
> I start minidlnad with `./minidlnad -f /tmp/minidlna.conf -d`
Can you check if this bug report is a duplicate of bug #749265,
"debian-specific patch causes segfault with -d option"?
I think the bugs are the same, but maybe I've overlooked something.
Cheers,
Florian
BTW: That's a
Hello Alexander,
Yes, I can still reproduce this using the current Debian sid package.
Simply moving a new multi-artist album into the minidlna media directory
adds multiple new albums to the "Music/Album" DLNA directory as soon as
minidlna picks up the new files through inotify.
The workaround
Hi Mathieu,
This works for me using 1.1.4+dfsg-1 (and possibly earlier versions) if
I drop the quotation marks: (Also works without the "V," prefix)
media_dir=V,/var/lib/minidlna media
(I realize that it looks quite strange…)
The code you mention still appears to drop trailing and leading space
There might be another way to fix this, as can be seen in the tracker
package:
http://anonscm.debian.org/cgit/collab-maint/tracker.git/tree/debian/30-tracker.conf
Add a .conf to the package to increase the watches limit.
Regards,
Florian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@li
Hi Jakobus,
>Aug 17 21:36:51 aldebaran minidlnad[537]:
>utils.c:277: warn: make_dir: cannot create
>directory '/run/minidlna'
>Aug 17 21:36:51 aldebaran minidlnad[537]:
>minidlna.c:434: error: Unabl
Hi Michael,
This is a duplicate of (fixed) bug #756169, upstream dropped those options.
Maybe the existing bug for the -i flag is a better place to discuss the
security implications and/or state of that feature. (Maybe it works as
designed, but connections on the "lo" interface are always accepte
Hi Michele,
On Mon, 06 Oct 2014 22:38:38 +0200 Michele Cane
wrote:
> The version 1.1.3 adds libavcodec > 54 / libav 10 compatibility.
> I can help if needed.
FWIW, two commits that ensure libav10 compatibility have been patched
into the 1.1.2 package in Debian through a NMU.
See this bug, comme
Hi,
Please note that I'm not the bug submitter.
> Can you provide a patch, please?
As of now, I can't. :/ I don't have the hardware to reproduce this or to
verify the correctness of a patch.
So I can only give a few hints about the background of this bug report.
Anyone not planning to come up w
35 matches
Mail list logo
