Hi, 在 2022-11-13星期日的 14:01 +0000，Reuben Thomas写道： > I am the upstream maintainer of libpaper (which used to be a pure-Debian > project), and also a Debian Maintainer trying to get a new version of > libpaper into Debian. (It involves an API/ABI transition, from the current > libpaper1 to libpaper2.) > > I am a bit torn here: with my DM hat on, stripping out gnulib sources > where possible and using Debian's gnulib package seems the right thing to > do. With my upstream hat on it leads potentially to bug reports that don't > correspond to an upstream release; and further few Debian packages that > use gnulib actually seem to use this method (there are 26 build-rdeps of > gnulib).
With my _de facto_ Debian gnulib package maintainer on (background: package gnulib has been under Debian QA Group umbrella for many years; I have been maintaining it with QA uploads for several years.), I would be glad to help you either when you act as an upstream libpaper developer or as Debian's DM. I would encourage ensuring your project (libpaper) to keep source-level compatibility with gnulib src versions both in Debian's repo, in your (upstream) embedded gnulib copy, as well as the gnulib upstream trunk(!). Enforcing it with some unittests would be great. If you find the current version in Debian not appropriate, feel free to ping me for a patch / update. As you might know, gnulib hasn't been providing releases for over a decade. The current maintenance in Debian is about packaging a reasonably new upstream snapshot. I tried to enable as much as upstream test suites as possible to make sure that things don't break. If anything breaks and affects you, feel free to submit a bug report and ping me. Thanks, Boyuan Yang
signature.asc
Description: This is a digitally signed message part
