Run of fresh-releases for python-graphql-core

• Worker: atlas.kali.org
• Package: python-graphql-core
• Change set: 48e02d14-5582-4741-b502-45a2736e6ae3
• Branch URL: https://gitlab.com/kalilinux/packages/python-graphql-core.git
• Upstream Branch URL: https://github.com/graphql-python/graphql-core.git/,branch=main
• Start time: 2021-02-11T01:42
• Duration: 1m14s
• Success probability: 0.02 (based on 276 previous runs)
• Status: unpack-unexpected-local-upstream-changes ( schedule control run )
• Description: Tree has local changes: 323 files

• There are changes between the upstream tarball and the non-debian/ part of the packaging repository that are not accounted for by any of the patches under debian/patches.

• Diff: raw diff, binary diffs are not available (missing control run - schedule control run )
• Command: new-upstream
• Build Version: None

Reschedule Reschedule (from scratch) Reprocess logs

 python-graphql-core-2.2.1/tests/validation/test_unique_variable_names.py
 python-graphql-core-2.2.1/tests/validation/test_validation.py
 python-graphql-core-2.2.1/tests/validation/test_values_of_correct_type.py
 python-graphql-core-2.2.1/tests/validation/test_variables_are_input_types.py
 python-graphql-core-2.2.1/tests/validation/test_variables_in_allowed_position.py
 python-graphql-core-2.2.1/tox.ini
dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/python-graphql-core_2.2.1-0kali2~jan+nur13.diff.e6J9ne
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
E: Failed to package source directory /tmp/tmp64cjdewj/build-area/python-graphql-core-2.2.1
brz: ERROR: The build failed.

Full worker log

• Full build log

Summary

Merged new upstream version: 3.1.3 (was: 2.2.1).

Publish Blockers

• ☒ run was not successful
• ☑ package has not been removed from the archive
• ☒ command changed from new-upstream to deb-new-upstream --debian-revision=0kali1 --require-uscan --refresh-patches --skip-empty
• ☑ review not required
• ☑ 0 publish attempts so far.not currently attempting to back off
• ☑ proposals not currently being rate-limited for maintainer None
• ☒ change set 48e02d14-5582-4741-b502-45a2736e6ae3 is working
• ☑ no relevant previous merge proposals