Hello Paul, On Fri, Aug 03, 2018 at 10:55:50AM +0200, Paul Gevers wrote: > Dear Ralf, > > On 03-08-18 05:15, Ralf Treinen wrote: > > Now, some of these backends are not available on all architectures [3]. I > > was told to use the "flaky" restriction in this case but this is not > > the right solution since if the backend package is available and the > > test fails when it is executed then I still want the red lights to go on. > > > > An alternative solution in my use case would be to use the "skippable" > > restriction, apt-get install the backend in the test and exit 77 when > > this fails, but this would mean using root access without a good reason. > > Ok, so you actually don't want flaky, but you want to make your test > depends arch aware, (Depends: x y [amd64]),
no, I do not want to hardcode in my package the list of archtictures on which my Recommended packages build or do not build. This would be a maintenance nightmare. > in your test check if your > dependency is installed and if not, exit 0 (or 77 with skippable). This works only if the testbed will install as many of my *alternative* Recommends as possible. If I understand correctly, apt-get will just install the first of these alternatives if possible, which means that all the other tests are useless because their test-dependency will not be satisfied. > Please, don't use apt-get if you don't want to be testing apt. yes, we agree here. -Ralf.
