Hi All
Just a quick update.
On Sun, 23 Jul 2023 at 15:07, Graham Inggs wrote:
> For what it's worth, r-cran-afex[1] and r-cran-mertools[2] **are**
> passing in unstable. So perhaps whatever package fixed this condition
> has been uploaded, but not yet migrated.
Since rmatrix 1.6-0-1 migrated,
On 23 July 2023 at 11:03, Dirk Eddelbuettel wrote:
| Note that the mlmRev authors / maintainers are the same as / a subset of the
| lme4 authors. They may have an idea.
|
| https://cran.r-project.org/package=mlmRev
I just ran `R CMD check mlmRev_*tar.gz` on my amd64 (under Ubuntu 23.04), it
On 23 July 2023 at 15:07, Graham Inggs wrote:
| Hi
|
| On Sun, 23 Jul 2023 at 13:11, Nilesh Patra wrote:
| > How do you conclude that?
| > The versions of affected packages are same in unstable and testing. They
| > fail in i386 with a newer version of lme4.
|
| For what it's worth,
Hi,
On 23-07-2023 15:51, Dirk Eddelbuettel wrote:
But if you all think we are better auto-removing lme4 over i386 fails _of
packages using it_ as opposed to fails in itself then I cannot stop you.
As I mentioned already, we can't even do that easily because lme4 is
currently a key package,
Hi
On Sun, 23 Jul 2023 at 13:11, Nilesh Patra wrote:
> How do you conclude that?
> The versions of affected packages are same in unstable and testing. They
> fail in i386 with a newer version of lme4.
For what it's worth, r-cran-afex[1] and r-cran-mertools[2] **are**
passing in unstable. So
On 23 July 2023 at 18:42, Nilesh Patra wrote:
| On Sun, 23 Jul 2023 07:15:09 -0500 Dirk Eddelbuettel wrote
| > Is this is not an example of a release manager override? The affectect
| > packages all work together in unstable and could migrate.
|
| How do you conclude that?
| The versions of
On Sun, 23 Jul 2023 07:15:09 -0500 Dirk Eddelbuettel wrote
> Is this is not an example of a release manager override? The affectect
> packages all work together in unstable and could migrate.
How do you conclude that?
The versions of affected packages are same in unstable and testing. They
fail
Paul,
Is this is not an example of a release manager override? The affectect
packages all work together in unstable and could migrate.
Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Hi Dirk,
On 22-07-2023 23:14, Dirk Eddelbuettel wrote:
It could be an issue as simple as CRAN (and
upstream) no longer checking on i386 though it usually does not fail there.
This is what I suspected, but it needs to be resolved in Debian by
somebody, somehow. lme4 is a key package, removing
On 22 July 2023 at 21:45, Paul Gevers wrote:
| Source: lme4
| Version: 1.1-31-1
| Severity: serious
| Control: close -1 1.1-34-1
| X-Debbugs-CC: debia...@lists.debian.org
| Tags: sid trixie
| User: release.debian@packages.debian.org
| Usertags: out-of-sync
|
| Dear maintainer(s),
|
| The
Source: lme4
Version: 1.1-31-1
Severity: serious
Control: close -1 1.1-34-1
X-Debbugs-CC: debia...@lists.debian.org
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
11 matches
Mail list logo
