Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
- Fixed lintian warnings "debian/rules ignores make errors".
* debian/control:
- Substituted outdated "Source-Version" fields with "binary:Version".
- Added 'python-apt' to Suggests, as apt-mark need it for work.
- Drop Debian revision from 'doc-base' build dependency, this fixes
appropriate lintian warning.
* debian/libapt-pkg-doc.doc-base.*:
- Changed section: from old 'Devel' to 'Debian'. This fixes appropriate
lintian warnings.
* debian/{postrm,prerm,preinst}:
- Added 'set -e', fixes lintian warnings
'maintainer-script-ignores-error'.
* dselect/makefile:
- Removed unneeded 'LOCAL' entry. This allows cleaning rule to run smoothly.
* share/lintian-overrides:
- Added with override of 'apt must depend on python'. Script 'apt-mark'
needs apt-python for working and checks this on fly. We don't want
python in most cases.
* cmdline/apt-key:
- Added 'unset GREP_OPTIONS' to the script. This prevents 'apt-key update'
failure when GREP_OPTIONS contains options that modify grep output.
(Closes: #428752)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(generic) acquire-item.cc code
|
|
|
|
|
|
- Added fallback to uncompressed 'Packages' if neither 'bz2' nor 'gz'
available. (Closes: #409284)
* apt-pkg/algorithm.cc:
- Strip username and password from source URL in error message.
(Closes: #425150)
|
|
|
|
|
|
|
|
|
|
|
|
and Packages)
|
|
|
|
|
|
- search command uses POSIX regex, and searches for virtual packages too
(closes: #277536)
* doc/offline.sgml: clarify remote and target hosts
(thanks to Nikolaus Schulz, closes: #175940)
* Fix several typos in docs, translations and debian/changelog
(thanks to timeless, Nicolas Bonifas and Josh Triplett,
closes: #368665, #298821, #411532, #431636, #461458)
* Document apt-key finger and adv commands
(thanks to Stefan Schmidt, closes: #350575)
* Better documentation for apt-get --option
(thanks to Tomas Pospisek, closes: #386579)
* Retitle the apt-mark.8 manpage (thanks to Justin Pryzby, closes: #471276)
* Better documentation on using both APT::Default-Release and
/etc/apt/preferences (thanks to Ingo Saitz, closes: #145575)
* fix FTBFS by changing build-depends to
* ABI library name change because it's built against
* Package that contains all the new features
* Branch that contains all the new features:
|
|
- search command uses POSIX regex, and searches for virtual packages too
(closes: #277536)
* doc/offline.sgml: clarify remote and target hosts
(thanks to Nikolaus Schulz, closes: #175940)
* Fix several typos in docs, translations and debian/changelog
(thanks to timeless, Nicolas Bonifas and Josh Triplett,
closes: #368665, #298821, #411532, #431636, #461458)
* Document apt-key finger and adv commands
(thanks to Stefan Schmidt, closes: #350575)
* Better documentation for apt-get --option
(thanks to Tomas Pospisek, closes: #386579)
* Retitle the apt-mark.8 manpage (thanks to Justin Pryzby, closes: #471276)
* Better documentation on using both APT::Default-Release and
/etc/apt/preferences (thanks to Ingo Saitz, closes: #145575)
* fix FTBFS by changing build-depends to
* ABI library name change because it's built against
* Package that contains all the new features
* Branch that contains all the new features:
|
|
|
|
|
|
|
|
|
|
- search command uses POSIX regex, and searches for virtual packages too
(closes: #277536)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/etc/apt/preferences (closes: #145575)
|
|
|
|
closes: #350575)
|
|
|
|
|
|
|
|
- move the state file writting into the Go() implementation
of dpkgpm (closes: #498799)
* apt-pkg/algorithms.cc:
- fix simulation performance drop (thanks to Ferenc Wagner
for reporting the issue)
|
|
The problem was that the size of pkgDpkgPM and its member offsets
changed because a map giving the names of the trigger states was
inserted into the middle of the structure. I fixed it by using a
statically allocated array instead. This changes the procedure for
looking up a string to a linear search, which should be fine (or
even faster than before) since there are only 4 state strings. If
it becomes a problem, sorting the array by key will allow us to use
std::equal_range(), but I would advise against this unless it's
really necessary, since sooner or later someone will forget to maintain
the sort order.
|