| Age | Commit message (Collapse) | Author |
|---|
|
run-tests code
|
|
|
|
- continue after test failure but preserve exit status
|
|
- prefer to install packages which have an already installed M-A:same
sibling while choosing providers (LP: #1130419)
|
|
- do not call Mark{Install,Delete} from the autoremove code with
the FromUser bit set to avoid modifying the auto-installed bit
|
|
- ignore negative dependencies applying in the same group for
M-A:same packages on the real package name as self-conflicts
|
|
- ensure that dependencies for packages:none are always generated
|
|
by introducing a pseudo-architecture 'none' so that the small group of
users with these packages can get right of them without introducing too
much hassle for other users (Closes: #686346)
|
|
- copy only configured translation files from a CD-ROM and not all
available translation files preventing new installs with d-i from
being initialized with all translations (Closes: #678227)
- handle Components in the reduction for the source.list as multi-arch CDs
otherwise create duplicated source entries (e.g. "wheezy main main")
|
|
- unpack versions in case a different version from the package
is currently in unpack state to recover from broken system states
(like different file in M-A:same package and other dpkg errors)
|
|
cases we have to choose a provider by defaulting on host-arch
instead of build-arch
|
|
purely virtual and shouldn't error out cause of that
|
|
- error out on (unsatisfiable) build-deps on purly virtual packages
instead of ignoring these dependencies; thanks to Johannes Schauer
for the detailed report! (Closes: #683786)
|
|
- handle :all and :native correctly as architectures again
in the commandline parsing (regression in 0.9.7)
|
|
- 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
|
|
- negative dependencies need to apply to all architectures,
but those with a specific architecture only apply to this one
|
|
- run autoclean against pkg:arch and not always against pkg:native as
this removes valid cache entries (Closes: #679371)
|
|
- arch:all packages are treated as arch:native packages, but dpkg
expects pkg:all for selections, so use the arch of the installed
version instead of the package structure if possible.
Thanks to Stepan Golosunov for the report! (Closes: #680041)
|
|
- print a friendly message in 'download' if a package can't be
downloaded (Closes: #677887)
|
|
|
|
|
|
|
|
|
|
- print URIs for all changelogs in case of --print-uris,
thanks to Daniel Hartwig for the patch! (Closes: #674897)
|
|
- do not run into loop on new-pre-depends-breaks (Closes: #673536)
|
|
- use the host architecture, not the build architecture for matching
of [architecture restrictions] in Build-Depends (Closes: #672927)
*
|
|
|
|
|
|
- clearly separate 'positive' and 'negative' dependencies and
their upgrade-resolution tries in MarkInstall and especially don't
treat Conflicts differently compared to Breaks here
|
|
- actually return to the fallback modifier if we have detected we
should for packagenames which look like modifiers (Closes: #669591)
|
|
|
|
|
|
output in the testcases by redirecting to /dev/null
|
|
|
|
|
|
- print list of autoremoves in alphabetical order (Closes: #639008)
|
|
ignore the presents (or absence) of lzma if we decided to use xz
|
|
- distinguish information about 'apt-get autoremove' based on the
number of auto-removed packages both before and after the list
of packages (Closes: #665833)
|
|
and add a comment about the need of this number
|
|
|
|
|
|
|
|
of specific packages as long as the order is okay in general
|
|
for said package i can't use it anymore in the testcase, so use another name
|
|
|
|
- do not try to a void a breaks if the broken package pre-depends
on the breaker, but let dpkg auto-deconfigure it
|
|
|
|
|
|
e.g. in a Depends line and are now requested for removal
|
|
- if a package can't be removed as it is not installed, suggest to
the user an (installed) multiarch silbing with 'Did you mean?'
|
