Hi Dirk,

On 10-02-2019 15:20, Dirk Eddelbuettel wrote:
> | Currently this regression is blocking the migration of lme4 to testing
> | [1]. Due to the nature of this issue, I filed this bug report against
> | both packages. Can you please investigate the situation and reassign the
> | bug to the right package? If needed, please change the bug's severity.
> 
> Sorry I don't really have the time for this. I maintain r-cran-lme4; it
> passes.

Although I understand your emotions, this isn't really constructive in
Debian. *Your* package lme4 isn't migrating to testing due to these
regressions. If you want your package in buster, it is better to at
least communicate with your reverse dependencies with regressing
autopkgtests.

> The relevant page for me is
> 
>    https://cloud.r-project.org/web/checks/check_results_lme4.html

Well, for me it is https://qa.debian.org/excuses.php?package=lme4 and
your package will not migrate if it remains like that.

> The package has MANY reverse dependencies but I am responsible for
> those. Talk to _their_ maintainers.  Thanks for your understandind.

I do talk to their maintainers by filing this bug report against your
package and their package at the same time. Without inside knowledge of
the r stack I can't judge the situation and I can only assume that you
may have to discuss together how to resolve this issue. Me understanding
you isn't going to have your package migrate, fixing the regression is.

Paul

PS: due to the tone of your response, it took me some days to reply.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to