apt/test/integration/test-multiarch-allowed, branch 1.1.exp11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.exp112015-08-17T16:37:18ZFix the test suite again2015-08-17T16:37:18ZJulian Andres Klodejak@debian.org2015-08-17T16:37:09Zurn:sha1:e7ebb41440cbe298b07c7fb7c6b20a64a17200f0
Gbp-Dch: ignore
just-in-time creation for (explicit) negative deps2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-17T08:53:01Zurn:sha1:bb0f6a34c4cebea7884de828c011dc85765ff820
Now that we deal with provides in a more dynamic fashion the last
remaining problem is explicit dependencies like 'Conflicts: foo' which
have to apply to all architectures, but creating them all at the same
time requires us to know all architectures ending up in the cache which
isn't needed to be the same set as all foreign architectures.
The effect is visible already now through as this prevents the creation
of a bunch of virtual packages for arch:all packages and as such also
many dependencies, just not very visible if you don't look at the stats…
Git-Dch Ignore
just-in-time creation for (implicit) Provides2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-16T17:41:45Zurn:sha1:ecc138f858fab61e0b888d3d13854d1422c3432b
Expecting the worst is easy to code, but has its disadvantages e.g.
by creating package structures which otherwise would have never
existed. By creating the provides instead at the time a package
structure is added we are well prepared for the introduction of partial
architectures, massive amounts of M-A:foreign (and :allowed) and co as
far as provides are concerned at least. We have something relatively
similar for dependencies already.
Many tests are added for both M-A states and the code cleaned to
properly support implicit provides for foreign architectures and
architectures we 'just' happen to parse.
Git-Dch: Ignore