Your message dated Wed, 20 Feb 2008 16:17:16 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#465177: fixed in mediatomb 0.10.0.dfsg1-2
has caused the Debian Bug report #465177,
regarding FTBFS: configure: error: unable to configure inotify support
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
465177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465177
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Source: mediatomb
Version: 0.10.0.dfsg1-1
Severity: serious
Mediatomb is failing to build on some architectures with these last entries.
The architectures it's failing to build on is powerpc and ia64.
checking sys/inotify.h usability... yes
checking sys/inotify.h presence... yes
checking for sys/inotify.h... yes
checking whether sys/inotify.h works... no, using own inotify headers
checking whether inotify-nosys.h works... no, disabling inotify support
configure: error: unable to configure inotify support
make: *** [configure-stamp] Error 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
For the powerpc, powerpc packages have been created before
(http://mediatomb.cc/pages/download#debian_ubuntu). The link to the powerpc
packages is dead however.
--
Regards,
Andres
--- End Message ---
--- Begin Message ---
Source: mediatomb
Source-Version: 0.10.0.dfsg1-2
We believe that the bug you reported is fixed in the latest version of
mediatomb, which is due to be installed in the Debian FTP archive:
mediatomb-common_0.10.0.dfsg1-2_i386.deb
to pool/main/m/mediatomb/mediatomb-common_0.10.0.dfsg1-2_i386.deb
mediatomb-daemon_0.10.0.dfsg1-2_all.deb
to pool/main/m/mediatomb/mediatomb-daemon_0.10.0.dfsg1-2_all.deb
mediatomb_0.10.0.dfsg1-2.diff.gz
to pool/main/m/mediatomb/mediatomb_0.10.0.dfsg1-2.diff.gz
mediatomb_0.10.0.dfsg1-2.dsc
to pool/main/m/mediatomb/mediatomb_0.10.0.dfsg1-2.dsc
mediatomb_0.10.0.dfsg1-2_all.deb
to pool/main/m/mediatomb/mediatomb_0.10.0.dfsg1-2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andres Mejia <[EMAIL PROTECTED]> (supplier of updated mediatomb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 19 Feb 2008 22:27:26 -0500
Source: mediatomb
Binary: mediatomb-common mediatomb-daemon mediatomb
Architecture: source all i386
Version: 0.10.0.dfsg1-2
Distribution: unstable
Urgency: low
Maintainer: Andres Mejia <[EMAIL PROTECTED]>
Changed-By: Andres Mejia <[EMAIL PROTECTED]>
Description:
mediatomb - UPnP MediaServer (main package)
mediatomb-common - UPnP MediaServer (base package)
mediatomb-daemon - UPnP MediaServer (daemon package)
Closes: 465177
Changes:
mediatomb (0.10.0.dfsg1-2) unstable; urgency=low
.
* Moved Debian packaging from svn to git.
+ Updated Vcs entries in debian/control.
* Fixing inotify build problems. An inotify check will be supported for
runtime. Closes: #465177
* Removing .pc directory when unpatching.
* Allowing options used in running configure to be overriden.
* Writing external script to generate orig source tarball and have
get-orig-source target in debian/rules call external script.
* Update copyright to mention two files that are removed from upstream.
* Add TODO about changing from using PNG Behavior fix from WebFX to using IE
PNG Fix delivered by TwinHelix.
* Adding TODO about ensuring that the WebUI works under any Mozilla based
browser.
+ There's a known problem with the WebUI under Konqueror.
Files:
6faef1f790b8f3678853e4b667d60c0e 978 net optional mediatomb_0.10.0.dfsg1-2.dsc
cd8c5c447b7d2db37444f25f6884507b 27567 net optional
mediatomb_0.10.0.dfsg1-2.diff.gz
7c2d927ef7cb2e6982688d67ba0ce172 17518 net optional
mediatomb-daemon_0.10.0.dfsg1-2_all.deb
4e8a3fd23a648bccea7302377f1c4f8e 16716 net optional
mediatomb_0.10.0.dfsg1-2_all.deb
74cd0aa28757930bc91aab6d1f6391c0 656714 net optional
mediatomb-common_0.10.0.dfsg1-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHvFDhDcs5RBTUBgsRAjgNAKCxrVmm2qbCwDNMHbWsISKEjnPK2QCfcm8x
D5lt8ezruB7HUCpvqvhEb+I=
=4CBa
-----END PGP SIGNATURE-----
--- End Message ---
