Age | Commit message (Collapse) | Author | Files | Lines |
|
* src/generic/apt/download_install_manager.cc:
When in download_only mode:
- report download errors;
- post_dpkg save/reload cycle (fix for #429388) is not needed;
- ignore aptitude::Forget-New-On-Install;
- avoid dpkg and a potential infinite loop;
- do not run {Pre,Post}-Invoke scripts.
Closes: #629266
|
|
Left over from commit 6dcafe7716dc7974576d3e83d3b9fa740ab215d2.
|
|
|
|
Previously non-regex terms had to use a grouping policy such as:
pattern(~ramd64 => amd64)
to specify the title. This change permits some terms to define
the title, and using shorter grouping policies like:
pattern(~ramd64)
pattern(~r)
* src/generic/apt/matching/match.{cc,h}:
- support non-regex terms generating titles;
|
|
|
|
|
|
* configure.ac:
- check for MultiArch support in APT (requires at least 0.8);
* src/generic/apt/apt.cc:
- support libapt-pkg 0.8.16 in multiarch_type;
* src/generic/apt/matching/match.cc:
- tweak multiarch;
|
|
|
|
Closes: #651748
|
|
|
|
|
|
A search pattern with no explicit term, "s", is equivalent to
"?name(s)". This changes modifies these semantics when the
pattern is arch-qualified, "name:arch" which is now equivalent
to "?exact-name(name) ?architecture(arch)".
These are the semantics used by apt-get and others which are
internally derived from pkgCache::FindPkg("name:arch").
On the command-line, it is possible to specify both an architecture
and an archive/version, as well as an override specifier:
# aptitude install an:armel/sid tf:armel-
* src/generic/apt/matching/parse.cc:
- extended semantics as per above.
* src/cmdline/cmdline_versions.cc:
- modify argument processing to use the extended semantics.
|
|
Architecture is not a property of the dependency, it is the particular
packages which determine whether they can satisfy a given dependency.
The old view:
--\ Depends (1)
--\ libc6:armel (>= 2.4) (UNSATISFIED)
p 2.13-27
--\ PreDepends (1)
--\ multiarch-support:armel
i multiarch-support 2.13-27
p 2.13-27
The new view is much clearer and does not mislead about the dependency
requirements:
--\ Depends (1)
--\ libc6 (>= 2.4) (UNSATISFIED)
p libc6:armel 2.13-27
--\ PreDepends (1)
--\ multiarch-support
i multiarch-support 2.13-27
p multiarch-support:armel 2.13-27
|
|
* src/generic/apt/apt.{cc,h}:
- new functions is_native_arch, is_foreign_arch.
* src/generic/apt/matching/*:
* doc/en/aptitude.xml:
- support 'native' and 'foreign' as arguments to ?architecture.
|
|
~V was not recognizing the special values CURRENT, CANDIDATE, TARGET.
* src/generic/apt/matching/parse.cc:
- move choice of ?version implementation to separate function and
use that function when parsing the short form ~V.
|
|
|
|
|
|
|
|
|
|
to 14…"
This is mainly for commit "a303dcaceacdc6299b9f23cc2375b9e403d20da0"
which was ineffective.
* src/pkg_columnizer.cc:
- really change default width of version columns to 14.
* doc/en/aptitude.xml:
- document changes to default widths of version columns.
* po/{dz,nb}.po:
- clear bad msgstr at src/pkg_columnizer.cc:86.
* po/ru.po:
- default width of 'downloadsize' column: 25 -> 19.
|
|
Recent commit using pkg_name_lt was an oversight.
There are a couple of places that use the 3-way compare of sort
policies, ideally they should be eliminated in favour of a straight
less-than. This would permit further with performance benefits, such
as eliminating the pkg_sortpolicy_wrapper.
|
|
* src/generic/apt/apt.h:
- consider arch in pkg_name_lt and use this in ver_name_lt.
* src/pkg_sortpolicy.cc:
- use pkg_name_lt instead of duplicated code.
|
|
This reverts commit fd28ea8c2af0786d3a426d06ea3527aa48de96ac.
That was a bit too hackish and subject to security issues. Much
more work is needed to address the issue, and probably should
be implemented within APT.
|
|
|
|
Usually we use APT to call dpkg, which handles all sorts of nice
option parsing. However, if an install run fails then we to call
'dpkg --configure -a' ourselves to see if this fixes the problem.
APT passes various options to dpkg, so we should also.
* src/generic/apt/download_install_manager.cc:
- pass DPkg::Options when invoking dpkg. LP: #257279
LP: #257279
|
|
Thanks: Colin Watson
Thanks: Michael Vogt
Closes: #497539
|
|
A package's full name includes the architecture, so consider
this when using sort policies.
|
|
* src/generic/apt.{cc,h}:
- make deptype_to_int an independent function, rename to
get_deptype_order
* src/generic/infer_reason.cc:
- replace cmp_dep_types with get_deptype_order
|
|
|
|
The order is defined by APT::Architectures, with "all" being first.
* src/generic/apt/apt.h:
- New function get_arch_order looks up an arch's position in the
order.
- New functor arch_lt sorts by the prefered order.
|
|
Searches for an action of 'reinstall', 'upgrade', 'downgrade' were
matching incorrectly.
* src/generic/apt/matching/match.cc: Add missing 'break' statements.
Thanks: Rogier <rogier777@gmail.com> for the patch.
Closes: #603862
|
|
'deptype' is now used consistently to indicate direct use of
pkgCache::Dep::DepType as opposed to pkgCache::Dep.
* src/generic/apt/apt.h (deptype_lt): also condense a trivial switch
statement.
|
|
Dependencies on Arch: all packages are still handling incorrectly.
This patch thoroughly exposes this issue in the curses interface.
Where previously aptitude would show (aboot-cross:amd64 info):
--\ Depends (2)
--- aboot-base (UNAVAILABLE)
which is incorrect (as aboot-base *is* available), we now see:
--\ Depends (2)
--- aboot-base:amd64 (UNAVAILABLE)
which makes it clear why the package is *considered* unavailable.
APT tools (at least, 0.8.15 series) exhibit this same problem
when displaying dependencies.
Exposing this issue enables improvements to the dependency
parser/handling to be made.
Non-multi-arch systems are unaffected.
|
|
* src/ui.{cc,h}:
- New functions show_info_screen, show_dep_screen, show_ver_screen
that combine make_x_screen and insert_main_widget with standard
descriptions.
* src/pkg_item.cc:
* src/pkg_ver_item.cc:
* src/solution_item.cc:
- Migrate duplicated code for above to ui.cc.
|
|
|
|
|
|
* ?architecture(architecture)
Select packages for the given architecture (such as
"amd64", or "all").
* ?multiarch(multiarch)
Select packages with a multi-arch capability of multiarch
(that is, either "foreign", "same", "allowed", or "none").
|
|
|
|
* src/generic/apt/apt.{cc,h}:
- New function multiarch_type returns a string describing
a multi-arch type.
* src/cmdline/cmdline_show.cc, src/pkg_info_screen.cc:
- Show Multi-Arch field on packages where this is set.
|
|
|
|
|
|
|
|
Previously a multi-arch setup would confuse the package states,
with packages available on multiple architectures overriding
the states of each other in a non-deterministic way. This
resulted in much annoying behaviour, such as packages being
perpetually marked as new.
No more! Package states are now stored with both the name
and architecture to uniquely identify each package.
Closes: #659079
Closes: #661744
|
|
This ammends commit 965412eea0846427fdd00fc04d436e0bc030f53b.
Some changes reverted or cleaned up due to inconsistencies with the
rest of the code base:
- changes to #include directives;
- use of CamelCase in identifiers;
- general formatting of the code (indentation, etc.)
|
|
|
|
policies by using boost::tokenizer…"
This reverts commit 965412eea0846427fdd00fc04d436e0bc030f53b.
|
|
|
|
many packages contain long versions, and 14 character limit still respects the 80-column width in package view list (slightly changing initial suggestion from Osamu Aoki <osamu@debian.org> due to related commit changing 'sizechange'/%Z field) (Closes: #624542)
|
|
Michał Kułach <michalkulach@gmail.com>) (Closes: #599209)
|
|
mainly by referring to them by the name actually used in the command line (the one that users know), rather than by their 'internal' name (Closes: #231595)
|