Building against Proposed, but Testing against Release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bileto |
Opinion
|
Undecided
|
Unassigned |
Bug Description
Hi,
I've run into an issue where I happened to build a package in a bileto ppa but failed testing.
In that particular case the reason is as following:
1. Upload Package to Bileto PPA
2. PPA Builds against proposed and picks up new library dependencies
3. Dep8 tests are scheduled later
4. Dep8 tests fail due to the new library not being in release (only proposed atm)
The Tests appear as "failed due to uninstallable test dependencies", that comes from the
package in the ppa requiring the new lib from proposed, but can't reach it in the Test env that
Bileto/Britney set up.
Since I usually use Bileto as great sniff Tester of all-arch build+test before publishing or uploading to a devel release this kind of breaks my use case.
From the discussions we had before on Bileto I'd have assumed it builds AND tests against proposed.
Therefore my Questions would be:
1. is it intentional to test against Release and not proposed (even for a Dev release)?
2. (I assume there is a reason for #1), but would it make sense to provide a config switch on a ticket to select what it will be tested against on Britney.
It might just be a lack of understanding of the Bileto/Britney infrastructure on my side, but in that cases the bug can serve to educate me and anybody else finding it later.
I even found that when trying to mitigate the issue by uploading the source of the "only in proposed" lib that is missing in the test into the bileto ppa I get warnings like:
"Needs rebuild due to burned version number (zesty/xen). Pending binary packages"
I know the number is burnt, but it won't be there when testing it so I need you to burn :-)
Or just allow to run the dep8s against proposed.