> Maintaining two source packages isn’t any harder than maintaining one, you
> just need to do it twice.
Yes source/binary packages are cheap ...
(but I'm still frightened by those with 5 lines of nodejs, WHY?).
I made a new dfsg tarball of the last release.
With the right tools it's just one command
"gbp import-orig --uscan" or similar.
The so called removed 246 files are these excluded using d/copyright:
>Files-Excluded:
> src/win
> lib/sounds/*.mp3
> lib/tiles/shockbolt/64x64.png
tchet@brix ~/git/angband $ gbp import-orig --uscan
gbp:info: Launching uscan...
Newest version of angband on remote site is 4.2.5, local version is 4.2.4
(mangled local version is 4.2.4)
=> Newer package available from:
=> https://github.com/angband/angband/archive/refs/tags/4.2.5.tar.gz
Successfully repacked ../4.2.5.tar.gz as
../angband_4.2.5+dfsg.orig.tar.xz, deleting 246 files from it
gbp:info: Using uscan downloaded tarball ../angband_4.2.5+dfsg.orig.tar.xz
What is the upstream version? [4.2.5+dfsg]
gbp:info: Importing '../angband_4.2.5+dfsg.orig.tar.xz' to branch 'upstream'...
gbp:info: Source package is angband
gbp:info: Upstream version is 4.2.5+dfsg
gbp:info: Replacing upstream source on 'master'
gbp:info: Successfully imported version 4.2.5+dfsg of
../angband_4.2.5+dfsg.orig.tar.xz
tchet@brix ~/git/angband $
