Reprepro claim its database is locked and fails
Type of work:
ssh email@example.com reprepro list bugfix-7636-printers-configuration repeatedly fails. This prevents me from finishing review and merges:
The lock file './db/lockfile' already exists. There might be another instance with the same database dir running. To avoid locking overhead, only one process can access the database at the same time. Do not delete the lock file unless you are sure no other version is still running! There have been errors!