[Pkg-gtkpod-devel] Bug#839411: libgpod: FTBFS: ../../../../../bindings/mono/libgpod-sharp-test/AssemblyInfo.cs(20, 12): error CS0647: Error during emitting `System.Reflection.AssemblyVersionAttribute' attribute. The reason is `Could not find file "/etc/localtime"'

[Lucas Nussbaum]

Source: libgpod
Version: 0.8.3-8
Severity: serious
Tags: stretch sid
User: debian-qa at 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[6]: Entering directory '/<<PKGBUILDDIR>>/build/mono/bindings/mono/libgpod-sharp-test'
> /usr/bin/mono-csc  -debug -unsafe -target:exe -out:libgpod-sharp-test.exe -r:../libgpod-sharp/libgpod-sharp.dll ../../../../../bindings/mono/libgpod-sharp-test/AssemblyInfo.cs ../../../../../bindings/mono/libgpod-sharp-test/Main.cs
> ../../../../../bindings/mono/libgpod-sharp-test/AssemblyInfo.cs(20,12): error CS0647: Error during emitting `System.Reflection.AssemblyVersionAttribute' attribute. The reason is `Could not find file "/etc/localtime"'
> Compilation failed: 1 error(s), 0 warnings
> Makefile:699: recipe for target 'libgpod-sharp-test.exe' failed
> make[6]: *** [libgpod-sharp-test.exe] 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/libgpod_0.8.3-8_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.