Hi Luigi, On Tue, Dec 04, 2018 at 10:46:41AM +0100, Luigi Toscano wrote: > On Tue, 4 Dec 2018 00:21:43 -0500 Nicholas D Steeves <nsteeves@gmail.com> wrote: > > > > > Sorry, I didn't notice that the non-English HTML docs had been dropped > > while the English ones remained...thank you for holding me > > accountable! Restoring non-English support is definitely something I > > will prioritise, but sadly very little free time at the moment, so > > please ping me if I seem to be taking too long. > > It's not an upstream issue: the orig tarballs used for this package is not > the tarball available on download.kde.org, which contains all the > translations: > https://download.kde.org/stable/kio-gdrive/1.2.5/src/ > > I suspect that the orig tarball was generated from the git tag - if it's the > case, please never use do that. Translations of projects by KDE are injected > in the tarballs when they are created. sha256sum of upstream released tarball: 1523c87f3f679cecbef0a2158a133f84379a0b276000c0233c34041b9c14d605 kio-gdrive-1.2.5.tar.xz sha256sum of the orig tarball for my upload: 41b836e268131dcb7e63ca5241fcc57b6c15fbcf0b72f7b65c44adbe9f8b8a9b kio-gdrive_1.2.5.orig.tar.xz Indeed, this was my mistake. Sorry, I'm still struggling with adapting to building from a packaging-only git repository--cherry picking and rebasing patches is particularly awkward. I also failed to notice that gbp generated the orig tarball from the upstream tag instead of from the uscan downloaded tarball. I've made the necessary changes in my devel repo to insure this won't happen again. Is this a case where the fix is an upload of 1.2.5.1~really1.2.5-1, where the new orig tarball will have a version of '1.2.5.1~really1.2.5', and which a hypothetical 1.2.5.1-1 will necessarily supersede (next release will probably be 1.2.6)? I've confirmed everything is as it should be when upstream release tarball with injected translations is used. Thank you! Nicholas P.S. I thought those post-tag autogenerated KDE translation commits were strange...now I know why...thank you for sharing this info, I didn't realise KDE project tags were non-authoritative milestones on a devel branch rather than releases.
Attachment:
signature.asc
Description: PGP signature