Hi Graham,

On 20 November 2023 at 12:13, Graham Inggs wrote:
| On Sun, 19 Nov 2023 at 14:59, Dirk Eddelbuettel <e...@debian.org> wrote:
| > So it contains a patch by Mikael which had been applied _permitting Matrix
| > 1.6-2_ to get to CRAN. So for this particular pair it was the other way 
around.
| 
| Great, thanks for clearing that up.
| 
| > So I leave this in your hands. If you think that after all this needs a
| > transtion, I may shrug but will of course help.
| 
| Well, we are doing a transition (for some value of), just not a
| "rebuild everything" transition like we must do for C libraries, but a
| "rebuild only affected things" like we do for Python and other
| interpreted languages.
| 
| On Sun, 19 Nov 2023 at 17:28, Dirk Eddelbuettel <e...@debian.org> wrote:
| > Done in lme4 1.1-35.1-3.
| 
| Thanks.  I see now r-cran-lme4 now has a:
| Depends: r-cran-matrix (>= 1.6-2)
| ...however this is not correct, because dpkg considers r-cran-matrix
| 1.6-1.1-1 in testing to meet that requirement, and the tests still
| fail with that version.
| 
| $ dpkg --compare-versions 1.6-1.1-1 ge 1.6-2 && echo True
| True
| 
| Please change that to:
| Depends: r-cran-matrix (>= 1.6-2-1)
| ... and re-upload, because dpkg considers 1.6-2 to be upstream version
| 1.6 and Debian revision 2, whereas we need upstream version 1.6-2 and
| Debian revision 1.
| 
| $ dpkg --compare-versions 1.6-1.1-1 ge 1.6-2-1 && echo True
| <no output>

Dang. Fell into a well-known hole there.  Will fix ASAP. Had in the back of
my mind some notion of 'cannot express Debian build number' but that is
clearly wrong.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Reply via email to