Control: tag -1 moreinfo unreproducible
Control: tag -1 important

Hi Lucas,

I was not able to reproduce, nor was reprobuilds on 2022-02-15 04:13:00 UTC:


https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/irony-mode_1.5.0-2.rbuild.log.gz

https://tests.reproducible-builds.org/debian/buildinfo/unstable/amd64/irony-mode_1.5.0-2_amd64.buildinfo

nor was DebCI on 2022-02-14 17:17:51 UTC:


https://ci.debian.net/data/autopkgtest/unstable/amd64/i/irony-mode/19201514/log.gz

https://ci.debian.net/data/autopkgtest/unstable/amd64/i/irony-mode/19201514/artifacts.tar.gz
  https://ci.debian.net/packages/i/irony-mode/unstable/amd64/

Reply follows inline:

Lucas Nussbaum <lu...@debian.org> writes:

> Source: irony-mode
> Version: 1.5.0-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220212 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):

[snip]

>> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version
"2.9.12")
>> CMake Error at /usr/lib/llvm-13/lib/cmake/clang/ClangTargets.cmake:737
(message):
>>   The imported target "RemoteIndexProto" references the file
>>
>>      "/usr/lib/llvm-13/lib/libRemoteIndexProto.a"
>>
>>   but this file does not exist.  Possible reasons include:
>>
>>   * The file was deleted, renamed, or moved to another location.
>>
>>   * An install or uninstall procedure did not complete successfully.
>>
>>   * The installation package was faulty and contained
>>
>>      "/usr/lib/llvm-13/lib/cmake/clang/ClangTargets.cmake"
>>
>>   but not all the files it references.
>>
>> Call Stack (most recent call first):
>>   /usr/lib/cmake/clang-13/ClangConfig.cmake:20 (include)
>>   src/CMakeLists.txt:4 (find_package)
>>
>>

"/usr/lib/llvm-13/lib/libRemoteIndexProto.a" comes from libclang-13-dev,
which is set up in L994 of your log, so this error doesn't make sense.
Forgive me for wondering if there's something wrong with your test system
;-)

[snip]

> If you fail to reproduce this, please provide a build log and diff it
with mine
> so that we can identify if something relevant changed in the meantime.
>

I didn't see anything meaningful in the diff of the build log, other
than the fact that your build system appears to have GCC preinstalled
(which shouldn't be meaningful).

Cheers,
Nicholas

Reply via email to