| 2013-04-05 18:20:57 |
Julian Taylor |
bug |
|
|
added bug |
| 2013-04-05 18:23:24 |
Julian Taylor |
description |
now that we have armhf in the qa jenkins builds we now get failures due to uninstallable packages.
See https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python-scipy-armhf/
Here openblas does not install because it does not exist for != x86,ppc
The most logical way to fix this is to properly support the dpkg dependency syntax including architecture qualifications.
Then autopkgtest can simply skip the tests where the used architecture is excluded in a dependency. |
now that we have armhf in the qa jenkins builds we now get failures due to uninstallable packages.
See https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python-scipy-armhf/
Here openblas does not install because it does not exist for != x86,ppc
The most logical way to fix this is to properly support the dpkg dependency syntax as stated in the DEP8 spec. This includes architecture qualifications.
Then autopkgtest can simply skip the tests where the used architecture is excluded in a dependency. |
|
| 2013-04-05 18:24:15 |
Julian Taylor |
description |
now that we have armhf in the qa jenkins builds we now get failures due to uninstallable packages.
See https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python-scipy-armhf/
Here openblas does not install because it does not exist for != x86,ppc
The most logical way to fix this is to properly support the dpkg dependency syntax as stated in the DEP8 spec. This includes architecture qualifications.
Then autopkgtest can simply skip the tests where the used architecture is excluded in a dependency. |
now that we have armhf in the qa jenkins builds we now get failures due to uninstallable packages.
See https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python-scipy-armhf/
Here openblas does not install because it does not exist for != x86,ppc
The most logical way to fix this is to properly support the dpkg dependency syntax as stated in the DEP8 spec. This includes architecture qualifications.
Then autopkgtest can simply skip the tests where the used architecture is excluded in a dependency.
Alternatively one could extend the spec to add an Architecture field. |
|
| 2013-07-19 09:24:23 |
Martin Pitt |
autopkgtest (Ubuntu): status |
New |
Triaged |
|
| 2013-07-19 09:24:28 |
Martin Pitt |
autopkgtest (Ubuntu): importance |
Undecided |
Medium |
|
| 2013-07-19 09:42:11 |
Martin Pitt |
autopkgtest (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2013-07-19 09:42:43 |
Martin Pitt |
summary |
skip tests where a dependency limits architecture |
support architecture specifiers in Depends: |
|
| 2013-07-19 16:19:38 |
Launchpad Janitor |
branch linked |
|
lp:debian/autopkgtest |
|
| 2013-07-19 17:23:39 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/saucy-proposed/autopkgtest |
|
| 2013-07-19 17:40:09 |
Launchpad Janitor |
autopkgtest (Ubuntu): status |
Fix Committed |
Fix Released |
|
