On Tue, Aug 23, 2022 at 04:59:10PM -0500, Steven Robbins wrote: > Commonly, I update a package that provides a shared library. Due to the > package naming convention, a new SOVERSION necessitates a trip through NEW, > which in turn means a binary upload. > > The binary upload cannot transition to testing -- a buildd binary build is > required. So far as I know -- assuming [1] is still up-to-date, this means a > nuisance upload just bumping the debian revision from -1 to -2. Is this > still > the recommended practice?
yes.
it's rather easy to do too, though maybe there should be something in
src:devscripts
implementing something along these lines:
dch -i -m "Source only upload for testing migration."
dch -r
debuild -S
cd .. ; dput $changes_file
# git commit & git tag
4 out of these 5 steps I've automated for myself with small scripts written
catering how "my" packages are maintained (which is the part where putting
this in src:devscripts is not that easy...).
"debuild -S" I do manually, because sometimes that's all I do and sometimes
I feed the resulting source package into yet another small script called
'spb', because it's running _s_udo _p_builder _b_uilt on the latest source
package in $PWD.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
When this virus is over, I still want some of you all to stay away from me.
signature.asc
Description: PGP signature
