summaryrefslogtreecommitdiff
path: root/test/integration/test-architecture-specification-parsing
Commit message (Collapse)AuthorAgeFilesLines
* reimplement build-dep via apts normal resolverDavid Kalnischkies2016-01-251-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | build-dep was implemented by parsing the build-dependencies of a package and figuring out which packages to install/remove based on this. That means that for the first level of dependencies build-dep was implementing its very own resolver with all the benefits (aka: bugs) this gives us for not using the existing resolver for all levels. Making this work involves generating a dummy binary package with fitting Depends and Conflicts and as we can't create them out of thin air the cache generation needs to be involved so we end up writing a Packages file which we want to parse – after we have parsed the other Packages files already. With .dsc/.deb files we could add them before we started parsing anything. With a bit of care we can avoid generating too much data we have to throw away again (as many parts assume that e.g. the count of packages doesn't change midair), so that on a speed front there shouldn't be much of a difference, but output can be slightly confusing as if we have a completely valid cache on disk the "Reading package lists... Done" is printed two times – but apt is pretty quick about it in that case. Closes: #137560, #444930, #489911, #583914, #728317, #812173
* tests: support spaces in path and TMPDIRDavid Kalnischkies2015-12-191-2/+2
| | | | | | | This doesn't allow all tests to run cleanly, but it at least allows to write tests which could run successfully in such environments. Git-Dch: Ignore
* tests: apt build-dep actually reports no depends correctlyDavid Kalnischkies2015-12-021-0/+2
| | | | | | | | | | 'Regression' of 7d19ee92f2368a40e739cb27d22d6d28f37ebf45, just that it now works more as expected than previously. Of course, build-essentials are implicitly also build dependencies, so by definition all packages have build dependencies, but that isn't what this message wants to say and it isn't what the user expects. Git-Dch: Ignore
* Fix the test suite againJulian Andres Klode2015-08-171-3/+3
| | | | Gbp-Dch: ignore
* test exitcode as well as string equalityDavid Kalnischkies2015-03-161-10/+10
| | | | | | | | We use test{success,failure} now all over the place in the framework, so its only consequencial to do this in the situations in which we test for a specific output as well. Git-Dch: Ignore
* do use an 'unknown' arch-specification in testDavid Kalnischkies2014-09-071-4/+4
| | | | | | | | Using 'kfreebsd' here makes the test fail on a kfreebsd system (obviously), so we just use something totally madeup in the hope that this is less like to conflict in the future. Git-Dch: Ignore
* fix remaining testcase-bugs from my armel boxDavid Kalnischkies2014-02-101-39/+43
| | | | Git-Dch: Ignore
* * apt-pkg/cachefilter.cc:David Kalnischkies2012-07-121-1/+14
| | | | | | | - remove architecture-specific arch to tuple expansion-rules as they lead to the same tuples for different architectures (e.g. linux-arm for arm, armel and armhf) while the dpkg-architecture code uses triples which are different (in the first part, which we omit in our tuples), so e.g. build-dep restrictions for armel ended up effecting armhf as well
* add two tests for architecture specificationsDavid Kalnischkies2012-06-141-0/+96