Re: Update IO::Stringy
Andrew Ruthven <[email protected]>
| Newsgroups | gmane.linux.debian.devel.perl |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2024-07-17 at 21:34 +0200, gregor herrmann wrote: > 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 … Darn, I pushed the branches but not that. Fixed for real now. Enumerating objects: 1, done. Counting objects: 100% (1/1), done. Writing objects: 100% (1/1), 175 bytes | 175.00 KiB/s, done. Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) To salsa.debian.org:perl-team/modules/packages/io-stringy.git * [new tag] upstream/2.113 -> upstream/2.113 > > > * 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.) Fair call. I've patched my local copy now as well. > 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. > 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). I opted to re-import the renamed orig tarball. I've pushed the branches and new upstream/2.113 tag. > Funny how many small hurdles a simple source package rename poses > nowadays :) Yup, crazy. Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand [email protected] | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |