Accepted gitpkg 0.31 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 30 Sep 2023 18:12:57 +0930
Source: gitpkg
Architecture: source
Version: 0.31
Distribution: unstable
Urgency: medium
Maintainer: Ron Lee <ron@debian.org>
Changed-By: Ron Lee <ron@debian.org>
Closes: 734360
Changes:
gitpkg (0.31) unstable; urgency=medium
.
* Support exporting submodules as part of the superproject package.
Closes: #734360
It's been a while since we had any follow up or feedback on the discussion
in that bug, so it's not clear that submodules remain a wide use case, but
I've now got one upstream repo really using them (though it probably would
be better organised differently too) so I at least have something concrete
to base the gitpkg behaviour on rather than just a strawman speculation on
my part about how a repo with submodules might be arranged and operated.
.
The originally proposed patch had quite a few limitations, it only worked
on exports of the debian-treeish, not for a real orig-branch, and it used
git submodule foreach, which only works on the current checked out state
of the working dir and so breaks one of gitpkg's fundamental modes of
operation where any revision can be exported at any time, regardless of
the current state of the repo working dir. This implementation is quite a
bit more involved, but it should handle most or all cases, including where
submodules have been moved or later deleted, provided the local repo has
been fully initialised and all submodules which may need to be exported
have been cloned into the superproject and its full history is intact.
.
It will not simply export submodules by default, though it if finds them
present in a repo that has not been configured to export (or ignore) them
then it will prompt asking what immediate action should be taken and
suggest configuration to avoid be prompted again subsequently. This way
existing repos that have been silently ignoring submodules thus far will
not silently do something surprisingly different with this gitpkg release.
.
* Sanity check and/or warn if gitpkg is invoked from a submodule dir, since
that probably won't do what a lot of people might naively assume, but it
might still be something that some pathological repo actually has a use
case for. We probably shouldn't encourage it though.
.
* Bump to debhelper compat 12. That give us no-patch builds back to buster
which is still a supported release. We don't actually need anything from
newer dh in this package, so this is just to stay ahead of the arbitrary
'deprecated version' warnings rather than to actually fix anything.
Checksums-Sha1:
e6a27a77f3fd871039bf9403f275f9aacff40da1 1464 gitpkg_0.31.dsc
783908cf5bf9bb8eb4faf1c15e4b4c426ff86c70 55302 gitpkg_0.31.tar.gz
1b47ae2d84bce8fb52ae59c16030efd6415dac63 6460 gitpkg_0.31_amd64.buildinfo
Checksums-Sha256:
a2f135258dc23a894fba3d597e7cc873ec77d25017155d9a463e067b8bb57c14 1464 gitpkg_0.31.dsc
165159f4642a98fc5f942940d21a3a77fe76b27682be4ce39dcd076886984eda 55302 gitpkg_0.31.tar.gz
43bbbfb7dd747478d61d250d235bd0cce97b045cf354206e897d67b8e7cbe0f3 6460 gitpkg_0.31_amd64.buildinfo
Files:
f9f7836a9ec7840375d83bba81012aeb 1464 vcs optional gitpkg_0.31.dsc
812d5a2a7353b8227040379f9240f832 55302 vcs optional gitpkg_0.31.tar.gz
c875323c90153a3a23c3d4a852414087 6460 vcs optional gitpkg_0.31_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEqx7pre9F9heWxVV3JJaf2mDAcSwFAmUYBXgACgkQJJaf2mDA
cSy3sw//dpaP59aPgR8rAi/FZTTWk9A0sk6ezZaw2KFYozFe3kHLB5qB4m1ahJS9
oIEJ+Ffr44+OuyYEhfcGVfjqFoVhEUhUT2UwnHM1mS2yuP7etECw72FoyDD2wj76
/NZcuOPAes3PNzhh2Odrgj5esPRefpECGk1lRQRujfUWEH9DCW1Z0+oJqgQzx10M
l/3CqBOJFr3JaQeSzOpFGC7XTuAoP4mG1FuWRSGNvd6zkheCLa0GRl0RKLywWTlo
pzEIMnpEH57XqRRW3p+GQJeYobtEVNes1UWK9SLHVD0LIXfBFc8OXUPBsXSNVvW+
9hcgUg3gzuKuxQKEXM4eT7LYFvYjxfcYK7BvdMwwpy4upB3vFRZWdNJKiFYzOYMs
LRZRFsb3RBhirhFJLZK4ctcAoOcVbM7Oz+MXWSUd3HaVt+fi9IBMKBSAMFjbIoK3
wVrBxmAsdTYsEW7DP/U9Wsgd/IaxmGaI/18tzDduWE/cG1eSqhS6UsNysID6PQH4
kIhDKvLPhrjEVTuG5T1H4PWz2y3A9neG7Z1tj00e5Vs4LfIbup/YPy9XIpO6bNDY
zTjVMT5gdKhWv8NaR9kSgikprtV676MISLuR1vVXeb6FnKBeSUSwJ+kZCz9CpcIJ
DEIrsmvNhLz/rqdNtDP8Z7h7gF/OWipmrngFz2r1/bQCNFRkRPQ=
=RwYd
-----END PGP SIGNATURE-----
Reply to: