On 28 June 2023 at 17:39, Jeremy Bícha wrote: | Control: severity -1 serious | | On Wed, Jun 28, 2023 at 5:29 PM Dirk Eddelbuettel <e...@debian.org> wrote: | > Feel free to change the severity back if you truly think it is that serious. | | Done. | | Feel free to close the bug once r-base is ready to migrate to Testing. | This is mostly just a tracking bug that people may find easier than | browsing the mailing list. | | > I maintain that r-base is fine. I have no control over how other people use | > my package, and if all other maintainers put breaking autopkgtests in well | > yes then they do hold r-base hostage and it will take "forever" to migrate to | > testing. We have been there before. | | Some just set this field in debian/control: | Testsuite: autopkgtest-pkg-r
Of course. That is just the mechanical 'how does one'. The actual problem is combining this with letting the packages get out of sync, or in the case of the API change, not yet having rebuilt. I just filed bug reports against (somewhat popular) packages r-cran-ragg (a graphics device) and r-cran-svglite (ditto). Once those are remade this self-inflicted autopkgtest "issue" will improve. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
