| Age | Commit message (Collapse) | Author |
|---|
|
The problemresolver will set the candidate version for pkg P back
to the current version if it encounters an impossible to satisfy
critical dependency on P. However it did not set the State of
the package back as well which lead to a situation where P is
neither in Keep,Install,Upgrade,Delete state.
Note that this can not be tested via the traditional sh based
framework. I added a python-apt based test for this.
LP: #1550741
[jak@debian.org: Make the test not fail if apt_pkg cannot be
imported]
|
|
|
|
Yay, newer server
Gbp-Dch: ignore
|
|
This auto-collapses the output and doesn't run the tests
if we compiling fails as a bonus.
Git-Dch: Ignore
|
|
This adds a vivid pinned to -1, cleans up the file a bit by
removing duplicate commands, and finally installs gettext
with a new apt-get run that is passed -t vivid.
The syntax for the pinning is some weird YAML stuff I don't
want to think about...
|
|
Git-Dch: Ignore
|
|
Git-Dch: Ignore
|
|
This makes tests work again!
Gbp-Dch: ignore
|
|
This makes travis-ci able to run our tests again.
Sometimes.
If it doesn't spontaneously fails with internal gcc errors…
Git-Dch: Ignore
|
|
Our integration tests need some additional dependencies to run and
function correctly, but while multiple places run them, there is no need
to also specify the these dependencies in multiple places.
Git-Dch: Ignore
|
|
|
|
I forgot to add libgtest-dev to the list of packages to install on
travis, so this slightly hacky oneliner might prevent us from having
the same problem again if we happen to change dependencies again.
Git-Dch: Ignore
|
|
stunnel4 is required for https tests
Git-Dch: Ignore
|
|
|
|
|
|
|
|
|
|
|
