Sigh, this was kind of expected. gdb moved to 17.1 and the patchfile that comes with the upstream crash source doesn't apply cleanly anymore (because it's for 16.2) and the build blows up.
Building crash requires a specific version of the gdb source and using gdb-source as build-depends is problematic since that is a moving target. Unless I can pin to a specific version but I don't think that's possible, or is it? I could fix this for gdb 17.1 but we'll likely run into the same problem again when gdb updates in the future. Besides, this is also problematic for Debian derivatives that ship a different version of gdb. Another option is to go back to the previous packaging strategy and include the gdb source tarball in the crash source package. Or use a component tarball crash_<version>.orig-gdb.tar.gz. Not sure if component tarballs are still OK to use or a thing of the past. Please let me know how to proceed. Personally, I prefer to move away from build-depend on gdb-source... Thanks ...juerg
attachment.sig
Description: PGP signature
