Source: valinor
Version: 1.1.4-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20240115 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>>'
python3 setup.py egg_info
running egg_info
creating valinor.egg-info
writing valinor.egg-info/PKG-INFO
writing dependency_links to valinor.egg-info/dependency_links.txt
writing entry points to valinor.egg-info/entry_points.txt
writing requirements to valinor.egg-info/requires.txt
writing top-level names to valinor.egg-info/top_level.txt
writing manifest file 'valinor.egg-info/SOURCES.txt'
reading manifest file 'valinor.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'valinor.egg-info/SOURCES.txt' PYTHONPATH=/<<PKGBUILDDIR>> nosetests3 -s -v --where=valinor/test valinor.test.test_exporter.test_exporter_location ... ok
testARMNoneEABIGDB (valinor.test.test_outputdir.TestCLIOutputDirectory.testARMNoneEABIGDB) ...
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/<<PKGBUILDDIR>>/valinor/test/../../valinor/main.py", line 36, in main
version=pkg_resources.require("valinor")[0].version,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 968, in require
needed = self.resolve(parse_requirements(requirements))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 829, in resolve
dist = self._resolve_dist(
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 870, in _resolve_dist
raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'pylink-square<2.0,>=1.0' distribution was not found and is required by pyocd

FAIL

======================================================================
FAIL: testARMNoneEABIGDB (valinor.test.test_outputdir.TestCLIOutputDirectory.testARMNoneEABIGDB)
---------------------------------------------------------------------- Traceback (most recent call last):
File "/<<PKGBUILDDIR>>/valinor/test/test_outputdir.py", line 48, in testARMNoneEABIGDB
runWithDir()
File "/<<PKGBUILDDIR>>/valinor/test/test_outputdir.py", line 46, in runWithDir
out = self.runCheck(args)
^^^^^^^^^^^^^^^^^^^
File "/<<PKGBUILDDIR>>/valinor/test/test_outputdir.py", line 33, in runCheck
self.assertEqual(status, 0)
AssertionError: 1 != 0

----------------------------------------------------------------------
Ran 2 tests in 0.291s

FAILED (failures=1)
make[1]: *** [debian/rules:33: override_dh_auto_test] Error 1

The full build log is available from: http://qa-logs.debian.net/2024/01/15/valinor_1.1.4-7_unstable.log

All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lucas@debian.org
or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240115&fusertaguser=lucas@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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Sun, 04 Feb 2024 06:05:07 +0000
with message-id <E1rWVcp-0031Lv-8i@fasolo.debian.org>
and subject line Bug#1060933: fixed in valinor 1.1.4-8
has caused the Debian Bug report #1060933,
regarding valinor: FTBFS: AssertionError: 1 != 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 owner@bugs.debian.org
immediately.)


--
1060933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060933
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 16 Jan 2024 19:44:56 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-106.9 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,
FROMDEVELOPER,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,
UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST
autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 38; hammy, 150; neutral, 198; spammy,
0. spammytokens: hammytokens:0.000-+--python3,
0.000-+--Hx-spam-relays-external:sk:stravin, 0.000-+--H*RT:sk:stravin,
0.000-+--Hx-spam-relays-external:311, 0.000-+--H*RT:108
Return-path: <lucas@debian.org>
Received: from stravinsky.debian.org ([2001: