Source: pacparser
Version: 1.3.6-1.4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>/src'
> cd pymod && ARCHFLAGS="" python3 setup.py build
> make[1]: git: No such file or directory
> python3 ../tests/runtests.py
> Traceback (most recent call last):
>   File "/<<PKGBUILDDIR>>/src/../tests/runtests.py", line 40, in runtests
>     pacparser_module_path = glob.glob(os.path.join(
>                             ^^^^^^^^^^^^^^^^^^^^^^^
> IndexError: list index out of range
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/<<PKGBUILDDIR>>/src/../tests/runtests.py", line 90, in <module>
>     main()
>   File "/<<PKGBUILDDIR>>/src/../tests/runtests.py", line 87, in main
>     runtests(pacfile, testdata, tests_dir)
>   File "/<<PKGBUILDDIR>>/src/../tests/runtests.py", line 43, in runtests
>     raise Exception('Tests failed. Could not determine pacparser path.')
> Exception: Tests failed. Could not determine pacparser path.
> make[1]: *** [Makefile:130: pymod] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/pacparser_1.3.6-1.4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231027&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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.

Reply via email to