Le 18/04/2019 à 16:07, Raphaël Hertzog a écrit : > Package: devscripts > Version: 2.19.4 > Severity: normal > User: [email protected] > Usertags: origin-kali > > I'm running this command: > $ salsa --conf-file salsa-auth.conf --conf-file +./salsa-packages.conf > update_safe --all --yes --no-fail --verbose > > salsa-auth.conf has my token and the API URL, and salsa-packages contains > instructions to configure my package repositories: > $ cat salsa-packages.conf > #SALSA_GROUP=kalilinux/packages > SALSA_GROUP_ID=5034987 > > SALSA_DESC_PATTERN="%p packaging for Kali Linux" > SALSA_DESC=yes > > SALSA_EMAIL=yes > SALSA_EMAIL_RECIPIENTS="[email protected]" > > SALSA_SOURCE_BRANCH=master > SALSA_DEST_BRANCH=kali/master > SALSA_RENAME_HEAD=yes > > SALSA_ENABLE_MR=yes > SALSA_ENABLE_ISSUES=no > > > Among all my repositories, I have some that have a "master" branch that > needs to be renamed into "kali/master" but I also have some repositories > that lack both "master" and "kali/master" and instead they have > "kali/dev". The --rename-head fails on the last set of repositories but > they are a minority so I wanted to go ahead anyway with the --no-fail. > But despite the --no-fail, the above command failed right after the first > error message: > > $ salsa --conf-file salsa-auth.conf --conf-file +./salsa-packages.conf > update_safe --all --yes --no-fail --verbose > [...] > salsa info: Error PUTing https://gitlab.com/api/v4/projects/11904256 (HTTP > 400): Bad Request {"message":{"base":["Could not change HEAD: branch... at > /usr/share/perl5/Devscripts/Salsa/update_repo.pm line 83. > $
Looking at code, salsa display this error because --verbose is set and then launch a "next" to manage next repository. Perhaps was it the last or is there another log after? > Note that it seems to work with "update_repo" however: > $ salsa --conf-file salsa-auth.conf --group-id 5034987 update_repo --no-fail > --all --rename-head --source-branch master --dest-branch kali/master > You're going to configure 811 projects. Continue (N/y) y > salsa warn: Branch rename has failed for ruby-ruby-progressbar. Use --verbose > to see errors > [...] > > You might find "update_safe --yes" a bit weird, but I don't want the > noise/busy work of update_repo redoing all the configuration that hasn't > changed... I wrote --yes exactly for that ;-) Cheers, Xavier
