Control: tag -1 - patch Control: tag -1 - moreinfo Control: tag -1 + help Hi,
Helmut Grohne (2021-03-20): >> > 4. Then it uses AC_CHECK_FILE to locate a header. Bad idea. >> > AC_CHECK_FILE is for host files, not for build files. Please use >> > test -e instead. > > https://gitlab.com/apparmor/apparmor/-/merge_requests/728 was merged > quickly. It's part of the Debian package since 3.0.3-1. >> > 6. The configure script assumes that $PYTHON-config is right. >> > Unfortunately, the Python interpreter is not usually prefixed with >> > a triplet whereas the -config tool is. Thus we get the build >> > architecture python-config here, but we should use the host one. >> > AC_PATH_TOOL is required here. > > https://gitlab.com/apparmor/apparmor/-/merge_requests/729 is just > reported. It's also part of the Debian package since 3.0.3-1. intrigeri (2021-04-02): > Here's what I'd like to review: > > - atomic patches (ideally as a MR on Salsa, but if that's too > inconvenient for you, I can live with the email workflow; it's just > less motivating, so you should expect longer delays): all changes > bundled in one single diff is too painful for me to review and to > selectively apply This is still true. > - based on the current 3.x (debian/experimental) codebase: both the > upstream code and the packaging have changed quite a bit since > 2.13.x and I'd rather not have to forward-port these changes Given testing/sid now have 3.x, this is not merely my preference anymore, but a requirement ⇒ removing the "patch" tag. > Additionally, I'm considering dropping the Perl extension in the 3.x > packaging: This happened in 3.0.3-3. I hope it makes your work on this front easier :) Cheers!