Your message dated Thu, 20 Oct 2016 22:14:11 +0200
with message-id <20161020201411.ga27...@fatal.se>
and subject line Re: Bug#841098: not fixed in rygel 0.32.1-1
has caused the Debian Bug report #841098,
regarding rygel: FTBFS (rygel-media-engine-test fails)
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 ow...@bugs.debian.org
immediately.)
--
841098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rygel
Version: 0.32.0-2
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
--------------------------------------------------------------------------------
[...]
debian/rules build-indep
dh build-indep --with autoreconf,gnome
dh_testdir -i
dh_update_autotools_config -i
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_autoreconf --as-needed
Copying file m4/codeset.m4
Copying file m4/extern-inline.m4
Copying file m4/fcntl-o.m4
Copying file m4/glibc2.m4
Copying file m4/glibc21.m4
Copying file m4/intdiv0.m4
[... snipped ...]
# TOTAL: 8
# PASS: 7
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: rygel-media-engine-test
=============================
(lt-rygel-media-engine-test:659): GStreamer-WARNING **: Element 'filesrc4'
already has parent
**
ERROR:rygel-media-engine-test.c:2035:__lambda19_: code should not be reached
FAIL rygel-media-engine-test (exit status: 134)
============================================================================
Testsuite summary for Rygel 0.32.0
============================================================================
# TOTAL: 8
# PASS: 7
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See tests/test-suite.log
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=Rygel
============================================================================
Makefile:1762: recipe for target 'test-suite.log' failed
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory '/<<PKGBUILDDIR>>/tests'
Makefile:1868: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/tests'
Makefile:1990: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/tests'
Makefile:596: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
Makefile:887: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------
The build was made on a QEMU/KVM virtual machine with a single CPU using sbuild.
The relevant part of the build log is included above.
If you need a full build log, just say so, I have plenty of them.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.32.1-1
Hello Santiago Vila.
The above mentioned upload was done as a source-only upload.
It built successfully not only in my local environment but also on *all*
architectures (and thus on atleast one buildd for each architecture).
This is obviously a problem in your environment.
The debian bug tracking system is not a support forum. If you need
personal support, then you need to negotiate a support contract first.
The debian bug tracking system is not the place for this.
Regards,
Andreas Henriksson
--- End Message ---
