Your message dated Thu, 6 Jun 2024 15:12:12 +0900
with message-id <[email protected]>
and subject line Re: [R-pkg-team] Bug#1072661: r-cran-popepi: Please update to
current version
has caused the Debian Bug report #1072661,
regarding r-cran-popepi: Please update to current version
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1072661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072661
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: r-cran-popepi
Version: 0.4.11+dfsg-1
This package is holding CRAN package 'survival' (aka r-cran-survival, a
package listed as part of the 'recommended' set by R Core and hence in
r-recommended) back from migrating and is now threatening removal. See
#1072648 for details.
And that is of course ridiculous. The package has been in Debian for 20 years
and is in perfect standing. As it is at CRAN. Consider:
- package survival is in _perfect_ condition at CRAN, see
https://cloud.r-project.org/web/checks/check_results_survival.html
- package popEpi is in _perfect_ condition at CRAN, see
https://cloud.r-project.org/web/checks/check_results_popEpi.html
- But it is at version 0.4.12 (one release ahead) and its changelog / news
https://cloud.r-project.org/web/packages/popEpi/news/news.html
says
News for version 0.4.12
Unit tests
No changes in the package itself — fixed a unit test that used the output
of survival::summmary.survfit which had improved slightly in 3.6-4.
suggesting that you may get your autopkgtest failure fixed for free if you
update. Please consider doing so, and the sooner the better.
I remain underimpressed by autopkgtest scatter for healthly packages (where
current, ie CRAN) that are left behind upstream.
Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | [email protected]
--- End Message ---
--- Begin Message ---
Hi Dirk and everybody,
I just updated r-cran-popepi using our routine-update script.
If you need to bump the priority of a package update, please do not
hesitate to just email this list instead of opening a bug. This plays
better with the routine-update worflow, which does not include manual
edition of the Debian changelog.
At least on my side, priority for updates is pretty random at the
moment, because I do not have a good tool to see where in our dependency
tree stand the packages that have bug, new upstream release, or
autopkgtest failure. Suggestions are welcome.
Best,
Charles
--
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from work, https://fediscience.org/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy
--- End Message ---
