On Wed, 17 Jul 2024 10:13:18 +1200, Andrew Ruthven wrote:
Sure. - Some notes:
* It seems that the upstream/2.113 hasn't been pushed to salsa.
Darn. Fixed.
Hm …
% git tag
2.111
debian/1.105-1
debian/1.203-1
debian/1.207-3
debian/2.108-1
debian/2.110-1
debian/2.110-2
debian/2.110-3
debian/2.110-4
debian/2.110-5
debian/2.111-1
debian/2.111-2
debian/2.111-3
upstream/1.105
upstream/1.203
upstream/1.207
upstream/2.108
upstream/2.110
upstream/2.111
v2.112
v2.113
Either something's weird on my side or there's still no upstream/2.113
tag there.
And that's from
% git remote -v
origin
[email protected]:perl-team/modules/packages/io-stringy.git (fetch) origin
[email protected]:perl-team/modules/packages/io-stringy.git (push) upstream-repo
https://github.com/genio/IO-Stringy (fetch)
upstream-repo
https://github.com/genio/IO-Stringy (push)
Unfortunately I initially used `dpt salsa pushrepo` and that surprised me by making a new repo at https://salsa.debian.org/perl-team/modules/packages/libio-stringy-perl , which I can't delete. Can this please be deleted to make way for renaming
the old repo?
Sure, done.
* A couple minor commits pushed.
Thank you. I had tried setting Debian Policy to 4.7.0, but with lintian moaning, I dropped back to 4.6.2.
Oh, right, lintian hasn't been updated yet :/
(I always patch lintian locally when a new Policy is released.)
* And now I can't build the package, as gbp looks for
libio-stringy-perl_2.113.orig.tar.gz in the pristine-tar branch
where there is still io-stringy_2.113.orig.tar.gz :)
(Temporarily manually workarounded locally but this also needs to
be fixed at some point.)
This should be fixed now. (And I figure you meant to say it is only finding 2.111).
No, I think I saw io-stringy_2.113.orig.tar.gz* there and not libio-stringy-perl_2.113.orig.tar.gz* but as the source package is
called libio-stringy-perl now, that's what pristine-tar called from
gbp looked for.
% git checkout pristine-tar
Switched to branch 'pristine-tar'
Your branch is up to date with 'origin/pristine-tar'.
% ls -1
io-stringy_1.105.orig.tar.gz.delta
io-stringy_1.105.orig.tar.gz.id
io-stringy_1.203.orig.tar.gz.delta
io-stringy_1.203.orig.tar.gz.id
io-stringy_1.207.orig.tar.gz.delta
io-stringy_1.207.orig.tar.gz.id
io-stringy_2.108.orig.tar.gz.delta
io-stringy_2.108.orig.tar.gz.id
io-stringy_2.110.orig.tar.gz.delta
io-stringy_2.110.orig.tar.gz.id
io-stringy_2.111.orig.tar.gz.delta
io-stringy_2.111.orig.tar.gz.id
io-stringy_2.113.orig.tar.gz.delta
io-stringy_2.113.orig.tar.gz.id
I guess this needs either a rename (not sure if this works) or a
"re-import" (`pristine-tar commit libio-stringy-perl_2.113.orig.tar.gz upstream/2.113' - once the upstream/2.113 tag exists).
Funny how many small hurdles a simple source package rename poses
nowadays :)
Cheers,
gregor
--
.''`.
https://info.comodo.priv.at -- Debian Developer
https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmaYHK9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbSTBAAlJGjwsmplYp/WPn/SZrWaqAwydI77GmcsZxhr3EH8bHusAPjQ1vviwPw gioczTmVVVXC4iwaN6b6NXshNEtWj0jGIWt3Upygzo8XTG7Akm4UzaoGL3YCEOqZ 6uMThxOCtEPoYWKOD/5Vnml+1r+uALGDpj6tenBMRWcj66CBhNaft5KRXLCK5gqv qbJIcf/4893FfFxWzZkpBAjEkSKcu+DCte7UkAA/NPqPTirC216fVmNRV5T3mRsK GljRVGMcMLcVz7B2DnqeGI6tJc4cNVoooJ9IXgXxg5pRZcG0eE+yhIVbjqH7wVfY IfQhn96/ukA19dBVHnJnPeJEa1LbWSKxxf5tLuQAJYOQLetCr5S+guy0WjseN9QL wIVpRNPcfiQxS6DNKqrHbjt2PRJHrIGBY+eV0PUUyPfdbngqA0lRNrT+XnxpGjjP amtoPxfWEKE3mLjCeQCmlfaLpu48OMqqKHKSnZLwaOZLP3t7aVhaH5LtYjClRqQ4
66+5q3Pm