Hello Sam, On Sun, May 10, 2020 at 5:41 PM Sam Hartman <hartm...@debian.org> wrote: > > I'm not sure I'm seeing how this comes up in practice for krb5-doc. > Would you mind helping my curiosity out.
It came up in practice for Ubuntu where i386 is now a "partial architecture". We first saw it in i386 autopackage tests, with an error like this when trying to setup the test environment (test run example below): (...) Depends: krb5-k5tls:i386 Depends: krb5-doc:i386 but it is not installable Depends: libkrb5-3:i386 (...) Testbed setup was: autopkgtest [21:10:49]: testbed running kernel: Linux 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 autopkgtest [21:10:49]: testbed dpkg architecture: amd64 autopkgtest [21:10:49]: testbed target architecture: i386 Log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/i386/k/krb5/20200108_211124_085e5@/log.gz > Also, I'm somewhat horrified that I didn't get a notification for your > MR. > My notification setting for debian/krb5 is watch. > Have you run into other cases where people were not notified of salsa > MRs? I have, for many packages. I heard that salsa email notifications were disabled by default for new projects, and that this might have been the reason.
