arm01 CI: Pipelines fail if the package is already in the repo
When restarting a build that has already made it into the repository, the pipeline fails with a message like this:
+ aptly repo add scratch gnome-usage-dbgsym_3.30.0+534+git3b32647-1pureos0_arm64.deb gnome-usage_3.30.0+534+git3b32647-1pureos0_arm64.deb gnome-usage_3.30.0+534+git3b32647-1pureos0.dsc Loading packages... [!] Unable to add package to repo gnome-usage-dbgsym_3.30.0+534+git3b32647-1pureos0_arm64: conflict in package gnome-usage-dbgsym_3.30.0+534+git3b32647-1pureos0_arm64 [!] Unable to add package to repo gnome-usage_3.30.0+534+git3b32647-1pureos0_source: conflict in package gnome-usage_3.30.0+534+git3b32647-1pureos0_source [!] Unable to add package to repo gnome-usage_3.30.0+534+git3b32647-1pureos0_arm64: conflict in package gnome-usage_3.30.0+534+git3b32647-1pureos0_arm64 [!] Some files were skipped due to errors: gnome-usage-dbgsym_3.30.0+534+git3b32647-1pureos0_arm64.deb gnome-usage_3.30.0+534+git3b32647-1pureos0.dsc gnome-usage_3.30.0+534+git3b32647-1pureos0_arm64.deb ERROR: some files failed to be added
This usually isn't extremely important, but sometimes matters - for instance, seems like recently Jenkins has restarted bunch of jobs after it itself got restarted, leading to quite a few false-positive red lights on the dashboard that can't be fixed until there's a new commit in the project repo.