Run of fresh-releases for gnome-shell-extensions

• Worker: atlas.kali.org
• Package: gnome-shell-extensions
• Change set: 8766e1ab-c056-4764-91de-fddec5f328fd
• Branch URL: https://gitlab.com/kalilinux/packages/gnome-shell-extensions.git
• Upstream Branch URL: https://gitlab.gnome.org/GNOME/gnome-shell-extensions.git/,branch=master
• Start time: 2021-02-15T02:23
• Duration: 1m2s
• Success probability: 0.02 (based on 202 previous runs)
• Status: unpack-unexpected-local-upstream-changes ( schedule control run )
• Description: Tree has local changes: 22 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

 gnome-shell-extensions-3.38.2/gnome-shell-extensions.doap
 gnome-shell-extensions-3.38.2/lint/eslintrc-gjs.yml
 gnome-shell-extensions-3.38.2/meson.build
 gnome-shell-extensions-3.38.2/meson/generate-stylesheets.py
 gnome-shell-extensions-3.38.2/po/ca.po
 gnome-shell-extensions-3.38.2/po/fur.po
dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/gnome-shell-extensions_3.38.2-1kali1~jan+nur2.diff.mKD12M
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
E: Failed to package source directory /tmp/tmpk9bhk_v2/build-area/gnome-shell-extensions-3.38.2
brz: ERROR: The build failed.

Full worker log

• Full build log

Summary

Merged new upstream version: 40.alpha.1 (was: 3.38.2).

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 8766e1ab-c056-4764-91de-fddec5f328fd is working
• ☑ no relevant previous merge proposals