Source: dbus-sharp-glib
Version: 0.6.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>'
> make[3]: Nothing to be done for 'all-am'.
> make[3]: Leaving directory '/<<PKGBUILDDIR>>'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> mkdir -p /<<PKGBUILDDIR>>/doc;
> for LIB in /<<PKGBUILDDIR>>/src/dbus-sharp-glib.dll; do \
>       mdoc update \
>               -fno-assembly-versions \
>               --out=/<<PKGBUILDDIR>>/doc \
>               $LIB; \
>       mdoc assemble \
>               --format ecma \
>               --out ${LIB%.dll} \
>               /<<PKGBUILDDIR>>/doc; \
> done
> New Type: DBus.BusG
> Member Added: public static void Init ();
> Member Added: public static void Init (DBus.Connection conn);
> Namespace Directory Created: DBus
> New Namespace File: DBus
> Members Added: 2, Members Deleted: 0
> mdoc: Could not find file "/etc/localtime"
> See `mdoc help' for more information.
> debian/rules:16: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/dbus-sharp-glib_0.6.0-1_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to