Fix pungi call with extra argument

The script gets a label as a command line argument, and this is manually
handled by adding it as `--label=$1` to the pungi-koji command. We
should not add this argument to another time.

This avoid problem with Pungi 4.1.17 which reports an error when seeing
unknown arguments (which were silently ignored before).

Fixes: https://pagure.io/pungi/issue/682
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
This commit is contained in:
Lubomír Sedlář 2017-07-24 14:22:00 +02:00
parent a7a3eebfcc
commit 85036765a7
4 changed files with 12 additions and 0 deletions

View File

@ -5,6 +5,9 @@
export LC_ALL=C
LABEL=$1
# Remove the label from arguments. It gets special treatment. Other arguments
# to the script are passed to pungi-koji directly.
shift
CONFIG="fedora-cloud.conf"
TARGET_DIR="/mnt/koji/compose/"

View File

@ -3,6 +3,9 @@
export LC_ALL=C
LABEL=$1
# Remove the label from arguments. It gets special treatment. Other arguments
# to the script are passed to pungi-koji directly.
shift
CONFIG="fedora-docker.conf"
TARGET_DIR="/mnt/koji/compose/"

View File

@ -3,6 +3,9 @@
export LC_ALL=C
LABEL=$1
# Remove the label from arguments. It gets special treatment. Other arguments
# to the script are passed to pungi-koji directly.
shift
CONFIG="fedora-final.conf"
TARGET_DIR="/mnt/koji/compose/25"
#OLD_COMPOSES_DIR="--old-composes=/mnt/fedora_koji/compose/f23 --old-composes=$TARGET_DIR"

View File

@ -3,6 +3,9 @@
export LC_ALL=C
LABEL=$1
# Remove the label from arguments. It gets special treatment. Other arguments
# to the script are passed to pungi-koji directly.
shift
CONFIG="fedora-atomic.conf"
TARGET_DIR="/mnt/koji/compose/twoweek"