Hi! Check out https://salsa.debian.org/otto/rocksdb/
It has the import you did plus some tweaks: - branches follow DEP-14 and instead of 'master' and 'upstream' there is 'debian/latest' and 'upstream/latest' - the same repo is a fork of the upstream repo so that it is easy to cherry-pick/backport/upstream fixes from Debian to upstream or from unreleased upstream to Debian patches - config debian/gbp.conf has been created so you can run effortlessly 'gbp import-ref' etc commands and git-buildpackage automatically knows about correct branch names and upstream release tag naming scheme - there is no tarball import process configured, as upstream releases are pure tag releases (plus notes) at https://github.com/facebook/rocksdb/releases - also Salsa-CI added and ensured it passes (see https://salsa.debian.org/otto/rocksdb/-/pipelines) On my own local repo I have these remotes configured now so I can help you with maintenance on Salsa yet automatically push to GitHub as well: git remote -v origin g...@salsa.debian.org:otto/rocksdb.git (fetch) origin g...@salsa.debian.org:otto/rocksdb.git (push) origin g...@gitlab.com:ottok/rocksdb.git (push) origin g...@github.com:ottok/rocksdb.git (push) upstream https://github.com/facebook/rocksdb.git (fetch) upstream https://github.com/facebook/rocksdb.git (push) Are you OK if I push this to https://salsa.debian.org/debian/rocksdb ? Next time there is a release the commands to import would be: git fetch upstream --tags gbp import-ref --verbose --upstream-version 9.2.2 Does this make sense to you?
