Your message dated Wed, 21 Dec 2011 10:56:01 +0100
with message-id <1324461361.3627.2.camel@alexander>
and subject line Re: rygel: FTBFS: configure: error: Package requirements 
(libsoup-2.4 >= 2.26.0
has caused the Debian Bug report #646663,
regarding rygel: FTBFS: configure: error: Package requirements (libsoup-2.4 >= 
2.26.0
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.)


-- 
646663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rygel
Version: 0.10.4-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20111022 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/build/rygel-FHhb8k/rygel-0.10.4'
> find . -name "*_vala.stamp" | xargs touch
> ./configure --prefix=/usr --mandir=\${prefix}/share/man \
>               --sysconfdir=/etc \
>               --enable-mediathek-plugin \
>               --enable-gst-launch-plugin \
>               CFLAGS=""
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for library containing strerror... none required
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for stdlib.h... (cached) yes
> checking for unistd.h... (cached) yes
> checking for sys/param.h... yes
> checking for getpagesize... yes
> checking for working mmap... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking whether to disable maintainer-specific portions of Makefiles... yes
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
> libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking for shl_load... no
> checking for shl_load in -ldld... no
> checking for dlopen... no
> checking for dlopen in -ldl... yes
> checking whether a program can dlopen itself... yes
> checking whether a statically linked program can dlopen itself... no
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for LIBGSSDP... yes
> checking for LIBGUPNP... yes
> checking for LIBGUPNP_AV... yes
> checking for LIBGUPNP_DLNA... yes
> checking for LIBGSTREAMER... yes
> checking for GSTREAMER_BASE... yes
> checking for GST_PBU... yes
> checking for LIBGIO... yes
> checking for GEE... yes
> checking for UUID... yes
> checking for LIBSOUP... no
> configure: error: Package requirements (libsoup-2.4 >= 2.26.0
>                            libsoup-2.4 <= 2.34.9999) were not met:
> 
> Requested 'libsoup-2.4 <= 2.34.9999' but version of libsoup is 2.36.0
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables LIBSOUP_CFLAGS
> and LIBSOUP_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/10/22/rygel_0.10.4-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



--- End Message ---
--- Begin Message ---
Version: 0.12.6-2

On Wed, 2011-10-26 at 02:34 +0200, Mònica Ramírez Arceda wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

rygel 0.12.6-2 currently in unstable builds just fine[0], so I'm closing
this bug now. Feel free to reopen if necessary.

Best regards

Alexander Kurtz

[0] https://buildd.debian.org/status/package.php?p=rygel

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to