| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes: #594211
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- don't use ReadOnlyGzip mode for PDiffs as this mode doesn't work
in combination with the AddFd methods of our hashclasses
Add also 2 testcases: one to test pdiffs in general and
one to test the handling of compressed indexes.
|
|
- some http servers violate HTTP1.1 by not issuing a Reason-Phrase
(or at least a space after the code) especially for 200, but lets
be nice and ignore it as we don't need the reason in general
|
|
- use the InstVer instead of the CurrentVer for the autobit transfer
Add also a small testcase to check the handling automatical
|
|
|
|
- set dir::state::status based at least on dir
|
|
- init valid-until correctly to prevent garbage entering Release file
|
|
- set the default values for dir::etc::trusted options correctly
|
|
|
|
ship the build packages in the correct distribution and section
|
|
|
|
archive building
|
|
- create backups for our extended_states file (Closes: #593430)
|
|
|
|
- fix error checking for read in case of failing bzip2/lzma/whatever
Spotted by -Wextra:
bzip2.cc: In member function ‘virtual bool Bzip2Method::Fetch(pkgAcqMethod::FetchItem*)’:
bzip2.cc:108:19: warning: comparison of unsigned expression < 0 is always false
bzip2.cc:111:19: warning: comparison of unsigned expression < 0 is always false
|
|
- fix error checking for vsnprintf in its safe variant
Spotted by -Wextra:
contrib/strutl.cc: In function 'char* safe_snprintf(char*, char*, const char*, ...)':
contrib/strutl.cc:1172:14: warning: comparison of unsigned expression < 0 is always false
|
|
in the FixByInstall code we currently "experiment" with
|
|
|
|
|
|
files for tests with "real" problems
|
|
|
|
- fix LongDesc handling in LANG=C environment
|
|
- fix LongDesc handling in LANG=C environment
|
|
as a needed remove nuked another or-member (helps for #591882)
- purge packages in 'rc' state, thanks Rogier! (Closes: #150831)
|
|
- let the problem resolver install packages to fix or-groups
as a needed remove nuked another or-member (helps for #591882)
The resolver sometimes need to break or-groups because he need to
remove the previous satisfier as a result of a breaks/conflicts.
In such broken or-groups he now tries to install a non-installed
non-deleted member of the or-group to statisfy it again.
This move is dangerous as it introduces the possibility of a
bunch of "new" broken breaks/conflicts on the new statisfier or
its dependencies and we don't know about them beforehand.
We also don't have the infrastructure to undo the decision later,
so we just do it and pray!
For now a test option is provided to disable this behavior on the
fly to test if the situation is worse: pkgProblemResolver::FixByInstall
|
|
|
|
* merge of the debian-expermental-ma branch
* refresh po/pot files in doc/ and po/
* apt-pkg/algorithms.cc:
- change the debug outputs to display also arch of the
package and version dependencies information
* cmdline/apt-get.cc:
- let APT::Get::Arch-Only in build-dep default to false again
(Closes: #592628) Thanks Mohamed Amine IL Idrissi for report!
* Swedish translation update. Closes: #592366
|
|
- let APT::Get::Arch-Only in build-dep default to false again
(Closes: #592628) Thanks Mohamed Amine IL Idrissi for report!
|
|
* Swedish translation update. Closes: #592366
* apt-pkg/pkgcache.cc:
- re-evaluate the architectures cache when the cache is (re)opened
* apt-pkg/cdrom.cc:
- fix off-by-one error in DropBinaryArch
* apt-pkg/contrib/fileutl.cc:
- Add WriteAtomic mode.
- Revert WriteEmpty to old behavior (LP: #613211)
* apt-pkg, methods:
- Convert users of WriteEmpty to WriteAtomic.
* apt-pkg/depcache.cc:
- Only try upgrade for Breaks if there is a newer version, otherwise
handle it as Conflicts (by removing it) (helps for #591882).
* debian/control:
- Add dependency on gnupg to apt, apt-key uses it.
|
|
- change the debug outputs to display also arch of the
package and version dependencies information
|
|
|
