---- On Thu, 01 May 2025 00:40:22 -0700 Phil Wyett <philip.wy...@kathenas.org> wrote ---
Control: tags -1 -moreinfo Control: tags -1 +confirmed On Wed, 2025-04-30 at 23:52 -0700, Golf Team wrote: > Gliim LLC is my company. It owns copyright to Golf. Does copyright years etc. need to be updated in some source files, are you doing this when you touch each file? > Sorry, there were many emails and I lost sight of the instructions. Not a > problem though, I just recreated the Salsa repository based on your > instructions. I suppose it will watch for upstream releases based on the > "watch" file and perform CI/CD for each release? The 'debian/watch' file when working will indicate new upstream releases on the packages Debian tracker page if available. You can work in git and tag your releases or you can import ready packages from local into Salsa/Debian with the command below and following prompts. cd into git repo root gbp import-dsc --prinstine-tar --uscan -- Regards Phil Donate: https://buymeacoffee.com/kathenasorg -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg Threads: https://www.threads.net/@kathenasorg -- Hi Phil, The copyright for each file has been changed to include full "<start year>-<current year>" notation, and a script incorporated into the release process with updates of <current year> being done automatically when needed. The Salsa repo has also been updated with the latest version, and will continue to be updated automatically. One method we considered was: gbp import-orig --pristine-tar --uscan --no-interactive and that works, since the watch file points to a correct github location. However, when new releases/tags are created, there's a delay between updating github (upstream) repo and the creation of .tar.gz source files (by github). This means we'd have to poll github until it's done before we can issue import-orig as above. Since we already have all the needed files (.dsc, .orig.tar.gz and .tar.xz), the method we use is (from the folder where all branches of Salsa repo have been cloned into): gbp import-dsc --pristine-tar <path-to-dsc-file>/golf_${PACKAGE_VERSION}-1.dsc And then simply push all branches and tags to Salsa: git push --all git push --tags This is how the latest version has been pushed to Salsa - does this look good from the perspective of how Salsa expects it to be? If so, this method (the second one with import-dsc) will be an automatic push to Salsa from now on going forward whenever a new Golf release is available. This way, Salsa will always be in sync with upstream for official releases. Best, Sergio
