| Age | Commit message (Collapse) | Author |
|---|
|
Multi-Arch: same packages can be co-installed, but need to have the same
version for all installed packages (aka "siblings"). Otherwise the
unsynced versions will fight against each other and the auto-install as
wel as the problem resolver will later have to decide between holding the
packages or to remove one of the siblings (usually a foreign) taking a
bunch of packages (like the entire foreign setup) with them.
The idea here is now to be more pro-active: MarkInstall will fail for
a package if the siblings aren't synced, so we don't allow a situation
in which a resolver has to decide if to hold or to remove-upgrade under
the assumption that the remove-upgrade decision is always wrong and
doesn't deserve to be explored (expect valid out-of-syncs of course).
Thats a pretty bold move to take for a library which is used by
different solvers so this check is done in IsInstallOk and can be
overridden if front-ends want to.
|
|
The breakage is just to big for now, so guard the change with
#ifndef APT_8_CLEANER_HEADERS and be nice to library users
|
|
|
|
|
|
|
|
fix a cosmetic warning from cppcheck:
[apt-pkg/depcache.h:462] -> [apt-pkg/depcache.h:122]:
(style) Variable 'Purge' hides enumerator with same name
|
|
depcache by caching the install-recommends and install-suggests
values
|
|
|
|
|
|
|
|
- use a boolean instead of an int for Add/Remove in AddStates
similar to how it works with AddSizes
|
|
pseudo-package related and/or private
|
|
to Keep which happens for example if a user decides to "remove" a not
installed package to forbid that it's part of the solution
|
|
based on a very early draft for EDSP by Stefano
APT can now write a scenario as well as load most stuff from it.
|
|
|
|
seperate IsModeChangeOk which checks sanity and dpkg holds
|
|
Multi-Arch; instead, Arch: all packages only satisfy dependencies for
the native arch, except where the Arch: all package is declared
Multi-Arch: foreign. (Closes: #613584)
This has the sideeffect that arch:all packages internally show up as
coming from the native arch - so packages with the architecture "all"
doesn't exist any longer in the pkgcache
|
|
- add SetCandidateRelease() to set a candidate version and
the candidates of dependencies if needed to a specified
release (Closes: #572709)
- change pkg/release behavior to use the new SetCandidateRelease
so installing packages from experimental or backports is easier
|
|
- do not check endpointer packages instead of only those which prevented
NeverAutoRemove settings from having an effect (Closes: #598452)
|
|
- fix autoremove by using correct config-option name and
don't make faulty assumptions in error handling (Closes: #594689)
|
|
- add another round of const& madness as the previous round accidently
NOT override the virtual GetCandidateVer() method (Closes: #587725)
|
|
* apt-pkg/contrib/configuration.{cc,h}:
- add a wrapper to match strings against configurable regex patterns
|
|
- SetCandidateVer for all pseudo packages
- SetReInstall for the "all" package of a pseudo package
|
|
- switch i{Download,Usr}Size from double to (un)signed long long
The biggest reason is that this saves a lot of float point operations
we do in AddSizes() on integers. The only reason i see that this was
a double is that it was 64bit long and can therefore store bigger
values than int/long, but with the availablity of (un)signed long long
we are now also at 64bit and can store sizes more than 8 Exabytes big -
by the time this will be a limit the C/C++ Standard will have bigger types,
hopefully.
|
|
boolean instead to handle the sizes more gracefully.
|
|
in his package choices
The previous implementation tried to install the package for arch A and
if this fails B, C and so on. This results in wrong architecture choices
for packages which depend on other pseudo packages, so he will now try
to install the dependencies first before trying the package itself and
only if this fails he tries the next architecture.
|
|
|
|
but we support the usage of the new ABI so libapt users
can start to prepare for MultiArch (Closes: #536029)
|
|
- remove Auto-Installed information from extended_states
together with the package itself (Closes: #572364)
|
|
installed reverse dependency and which also doesn't provide something.
They cause problems if this pseudo packages get new dependencies.
As a consequence we also need to recheck the dependencies of a killed
pseudo package (and especially the providers of these dependencies)
to really kill all non required packages.
|
|
packages in a group if one is marked.
The auto-installed flag is from now on Architecture bound:
A section without an architecture tag will be treated as applying
to all architectures - the next write operation will take care of
this by creating separate sections for the architectures.
|
|
Arch all packages are now represented by arch depending packages which
all depend on a package with the same name and the special arch "all".
This packages has NO dependencies, but beside this the same information.
It is the only package which has a size, the arch depending ones all
have a zero size. While the arch depending pseudo packages are used
for dependency resolution the arch "all" package is used for downloading
and ordering of the package.
|
|
can be sure that a package comeing in as a dependency of this package
will be of the same architecture as itself (or all). We don't want to break
this, so internal an arch all package is represented as many arch depending
packages. The only problem we have now is that we only know that a arch
all package is installed or not - we don't know for which architecture it
was installed: So we will look at all these broken arch all pseudo packages
and "remove" them.
|
|
they have no effect anyway (thanks Daniel Burrows for noticing)
* improve documentation of the Is{Delete,Install}Ok methods a bit
* add the FromUser boolean to the debug output of the markers
|
|
* honor the dpkg hold state in new Marker hooks (closes: #64141)
Combine the proposed AutoInstOk and IsAutoInstallOk to more general hooks
for MarkInstall (and another one for MarkDelete) with the same parameters
as the call these hooks should check.
|
|
|
|
|
|
type triggers a autoinst (closes: #458389)
* add debug::pkgDepCache::Marker with more detailed debug output
(closes: #87520)
|
|
|
|
Daniel Burrows, closes: #429378)
* fix FTFBFS by changing build-depends to
libcurl4-gnutls-dev (closes: #428363)
|
|
|
|
|
|
|
|
|
|
- added "--fix-policy" option to make it easy to fix any not-install
recommends
* apt-pkg/depcache.{cc,h}
- MarkInstall() has a new "ForceImportantDeps" option (defaults to false)
to fice the install of recommends even for already installed pkgs
- a new PolicyBroken() function to see how much of the recommends are
broken
|
|
- added APT::Install-{Recommends,Suggests} global option
* depcache.h:
- added DepCache::State::InstPolicyBroken() to check if the
current install state violates the policy (compated with
InstBroken() that only checks for the minimal requirements)
|
|
Patches applied:
* dburrows@debian.org--2005/apt--auto-mark--0--base-0
tag of michael.vogt@ubuntu.com--2005/apt--auto-mark--0--patch-22
* dburrows@debian.org--2005/apt--auto-mark--0--patch-1
doxygenize the new automark stuff
* dburrows@debian.org--2005/apt--auto-mark--0--patch-2
Automatically update package markings after every state-changing public operation, and allow users of the dep-cache to group actions into a single action.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-3
Automatically update package markings after every state-changing public operation, and allow users of the dep-cache to group actions into a single action.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-4
Make action groups noncopyable
* dburrows@debian.org--2005/apt--auto-mark--0--patch-5
Typo fix
* dburrows@debian.org--2005/apt--auto-mark--0--patch-6
Add a FromUser flag to MarkKeep.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-7
Somehow the ActionGroup definition got duplicated; kill the duplicate.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-8
Cancel the automatic flag on packages that are being kept only if they are garbage.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-9
Don't clear the 'automatically installed' flag in MarkDelete.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-10
Add a FromUser flag to MarkInstall, and fix its handling of the Auto flag.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-11
Only clear the Auto flag on manual changes in MarkKeep.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-12
Make changes from the internal algorithms automatic.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-13
Use ActionGroups in algorithms that make lots of changes, and fix a compile error.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-14
Split the sweep code into a separate routine from pkgMarkUsed
* dburrows@debian.org--2005/apt--auto-mark--0--patch-15
Update another call of MarkKeep to indicate that it's automatic.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-16
Move the mark-and-sweep code into pkgDepCache; call Sweep and document what it and Garbage are for; add a hook that can be used to generate a custom root-set function; move the big blob of regexp stuff into the custom root-set; fix the memory leak in the regexp stuff.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-17
Make ActionGroup take a reference instead of a pointer to the cache.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-18
Don't mark already-to-be-deleted packages as garbage, to imitate aptitude's behavior.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-19
Update apt-get for the new auto-mark protocol.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-20
Add a setter method for the Auto flag.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-21
Fix the test in apt-get about what to delete.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-22
Add a zero-argument mark-and-sweep routine and use it to do a mark-and-sweep on startup (so the garbage flags are initialized properly).
* dburrows@debian.org--2005/apt--auto-mark--0--patch-23
Right, Status is 2 for new installs, not 0.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-24
POT updates.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-25
Actually initialize group_level to 0.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-26
Don't make an ActionGroup in Sweep, since there's no point and it also is an infinite loop.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-27
Add virtual hooks to control whether the garbage collector considers recommends and/or suggests to be strong links.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-28
Call the progress methods in the right order so we don't generate nonsensical progress notifications.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-29
Typo fix.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-30
Make RecommendsImportant default to true in apt, too.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-31
Add a release() method to action groups.
* dburrows@debian.org--2005/apt--auto-mark--0--patch-32
Add an 'autoremove' command that is synonymous to '--auto-remove remove'.
|
|
automatically installed packages
Patches applied:
* apt@packages.debian.org/apt--main--0--patch-98
Install only one keyring on each branch (Closes: #316119)
* apt@packages.debian.org/apt--main--0--patch-99
Finalize 0.6.39
* apt@packages.debian.org/apt--ubuntu--0--patch-7
Merge with mainline
* apt@packages.debian.org/apt--ubuntu--0--patch-8
install only the ubuntu keyring
* apt@packages.debian.org/apt--ubuntu--0--patch-9
Finalize 0.6.39
* apt@packages.debian.org/apt--ubuntu--0--patch-10
Merge with mainline
* apt@packages.debian.org/apt--ubuntu--0--patch-11
Update configure.in
|
|
|
|
|
