Hi Andreas On Mon, 20 Nov 2023 at 06:59, Andreas Tille <ti...@debian.org> wrote: > > We liked the change you made to r-cran-tmb [2], as this allows the > > affected packages to be binNMU'd and gain a versioned dependency on > > r-cran-matrix. Would you please apply this to the other affected > > packages (only r-cran-irlba and r-cran-openmx, if I understand > > correctly)? > > Done.
Thanks! For the r-cran-tmb upload, I now see only autopkgtest regressions [1] for: r-cran-insight/0.19.6+dfsg-1 r-cran-parameters/0.21.2-1 I have not investigated, but these seem to be passing in unstable, so can be hinted if needed. For the r-cran-irlba upload, there's only one autopkgtest regression [2] for: r-cran-seurat/4.4.0-1 This autopkgtest currently fails in unstable as well, would you please investigate? It seems your r-cran-seuratobject 5.0.0-1 upload is blocked by this same regression for 19 days [3] and r-cran-seurat has not yet been updated to the new upstream version 5.0.1. Does something prevent you from updating? For the r-cran-openmx upload, there are no autopkgtest regressions [4] \o/ > I've reverted this but in previous discussion[4] with Paul we agreed > upon the strict version dependency. I think this is only necessary for > r-cran-tmb (where upstream is enforcing this with a test I'm hesitating > to patch out). But maybe upstream can work with the freshly implemented > R_MATRIX_ABI_VERSION and thus we can come back to upstream if the > autopkgtest will fire next time (which will happen now after the next > r-cran-matrix update). Thanks again. Yes, let's wait to see how TMB upstream deals with this. Regards Graham [1] https://qa.debian.org/excuses.php?package=r-cran-tmb [2] https://qa.debian.org/excuses.php?package=r-cran-irlba [3] https://qa.debian.org/excuses.php?package=r-cran-seuratobject [4] https://qa.debian.org/excuses.php?package=r-cran-openmx
