Hi, On 13-12-2023 17:08, Andreas Tille wrote:
Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migrationI do not understand this line. What exact package needs a source-only upload?
You uploaded binaries together with the source. Because this is an arch:all binary we can't binNMU in a meaningful way and we don't accept uploader built binaries in testing anymore. Currently the only way to solve this is by doing a source-only (so, no binaries) upload (of r-bioc-biocgenerics).
Remember, all r-bioc-* packages need to migrate together, so all of your uploads need to be ready before r-bioc-biocgenerics can migrate. I checked only the first few "Migrates after" links from [1], and found at least these packages still show autopkgtest regressions [2][3][4][5][6].Thank you for these links. Could you please explain how I can obtain these myself? Is there any page I could look at for some kind of summary?
I read in Graham's message that he started at [1] and just clicked the links. I don't think there's a great web site yet ([tracker] comes close), except udd has all the information which can be queried and *all* excuses can be viewed too [excuses] (or processed [yaml]).
[2] https://tracker.debian.org/pkg/r-bioc-beachmatThis shows: autopkgtest for r-bioc-biocsingular/1.16.0+ds-1: amd64: Regression or new test...
but that version of r-bioc-biocsingular is in testing and bound to fail. Version 1.18.0+ds matches to BioC API 3.18.
I wonder if it might be that britney2 doesn't notice that if it needs to take r-bioc-biocgenerics from unstable to run a test, that r-api-bioc-3.17 is no longer provided and hence also the test needs to come from unstable. Obviously there's room for improvement there, but the amount of code to determine the set of pinned packages from unstable is already rather long. [britney2]
I admit I have no idea what to do. If the migration issues are caused by running tests against versions in testing which can't pass something is broken.
They *should* be scheduled with the test from unstable, as the binaries depend on r-api-bioc-3.17 which will no longer be available when r-bioc-biocgenerics is used from unstable.
Please let me know if I can do something to fix the situation, but for the moment I have no idea what to do.
Patches for britney2 please ;).I'll try to do some manual triggering of tests tonight/tomorrow, but after a quick glance, that might be too much to handle manually.
Paul [1] https://tracker.debian.org/pkg/r-bioc-biocgenerics[tracker] https://tracker.debian.org/teams/r-pkg-team/ the piece below Packages with test failures: if it goes from passing in testing to fail in unstable there is potentially a problem
[excuses] https://release.debian.org/britney/update_excuses.html [yaml] https://release.debian.org/britney/excuses.yaml.gz[britney2] https://salsa.debian.org/release-team/britney2/-/blob/master/britney2/policies/autopkgtest.py#L622 until line 743
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature