borgbackup/scripts/upload-pypi

#!/bin/bash

R=$1

if [ "$R" = "" ]; then
    echo "Usage: upload-pypi 1.2.3 [test]"
    exit
fi

if [ "$2" = "test" ]; then
    export TWINE_REPOSITORY=testborgbackup
else
    export TWINE_REPOSITORY=borgbackup
fi

D=dist/borgbackup-$R.tar.gz

twine upload $D
update release workflow using twine (docs, scripts), see #4213 2019-02-01 15:57:47 -05:00			`#!/bin/bash`

			`R=$1`

			`if [ "$R" = "" ]; then`
			`echo "Usage: upload-pypi 1.2.3 [test]"`
			`exit`
			`fi`

			`if [ "$2" = "test" ]; then`
upload-pypi: use borg-specific repository names so it finds the right api token in .pypirc 2025-11-01 14:57:26 -04:00			`export TWINE_REPOSITORY=testborgbackup`
update release workflow using twine (docs, scripts), see #4213 2019-02-01 15:57:47 -05:00			`else`
fix pypi repo name in upload script it needs to be like this to support a ~/.pypirc like this, containing a separate upload token for the borgbackup project: [distutils] index-servers = borgbackup ... [borgbackup] repository = https://upload.pypi.org/legacy/ username = __token__ password = pypi-...(token)... 2024-07-20 11:47:59 -04:00			`export TWINE_REPOSITORY=borgbackup`
update release workflow using twine (docs, scripts), see #4213 2019-02-01 15:57:47 -05:00			`fi`

			`D=dist/borgbackup-$R.tar.gz`

fix pypi repo name in upload script it needs to be like this to support a ~/.pypirc like this, containing a separate upload token for the borgbackup project: [distutils] index-servers = borgbackup ... [borgbackup] repository = https://upload.pypi.org/legacy/ username = __token__ password = pypi-...(token)... 2024-07-20 11:47:59 -04:00			`twine upload $D`