Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4_beta2 2016-01-08T20:20:25Z 2016-01-08T20:20:25Z Julian Andres Klode jak@debian.org 2016-01-08T10:12:14Z urn:sha1:60d523e2ae93a6c5bc396b6bede2544271fb1f2e By storing the size of the string in the cache, we can make use of it when comparing the names in the hashtable in pkgCache::FindGrp. 2015-12-11T14:02:24Z Julian Andres Klode jak@debian.org 2015-12-11T14:02:24Z urn:sha1:f9d8a91570788b676cabceede3229860ad76734e Fixes a warning reported by gcc. Gbp-Dch: ignore 2015-11-19T23:54:07Z David Kalnischkies david@kalnischkies.de 2015-11-19T23:54:07Z urn:sha1:6789e01e9370b3b7f65d52138c5657eaa712b4d1 Out of memory and similar circumstanzas could cause MMap::Map to fail and especially the mmap/malloc calls in it. With some additional checking we can avoid segfaults and similar in such situations – at least in theory as if this is a real out of memory everything we do to handle the error could just as well run into a memory problem as well… But at least in theory (if MMap::Map is made to fail always) we can deal with it so good that a user actually never sees a failure (as the cache it tries to load with it fails and is discarded, so that DynamicMMap takes over and a new one is build) instead of segfaulting. Closes: 803417 2015-09-14T13:22:18Z David Kalnischkies david@kalnischkies.de 2015-09-10T17:00:51Z urn:sha1:95278287f4e1eeaf5d96749d6fc9bfc53fb400d0 Our error reporting is historically grown into some kind of mess. A while ago I implemented stacking for the global error which is used in this commit now to wrap calls to functions which do not report (all) errors via return, so that only failures in those calls cause a failure to propergate down the chain rather than failing if anything (potentially totally unrelated) has failed at some point in the past. This way we can avoid stopping the entire acquire process just because a single source produced an error for example. It also means that after the acquire process the cache is generated – even if the acquire process had failures – as we still have the old good data around we can and should generate a cache for (again). There are probably more instances of this hiding, but all these looked like the easiest to work with and fix with reasonable (aka net-positive) effects. 2014-03-13T12:58:45Z David Kalnischkies david@kalnischkies.de 2014-03-05T21:11:25Z urn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f Beside being a bit cleaner it hopefully also resolves oddball problems I have with high levels of parallel jobs. Git-Dch: Ignore Reported-By: iwyu (include-what-you-use) 2014-03-13T12:58:45Z David Kalnischkies david@kalnischkies.de 2014-02-27T01:18:11Z urn:sha1:e788a834ce421042e727b72e43177edaa47e53a7 Git-Dch: Ignore Reported-By: gcc -Wuseless-cast 2014-01-16T18:51:23Z David Kalnischkies david@kalnischkies.de 2014-01-16T18:51:23Z urn:sha1:62d8a765b9b37354efab6ca838cbdb7f347f7cac No visible functional changes, just code moved around and additional checks to eliminate impossible branches Reported-By: scan-build Git-Dch: Ignore 2012-08-04T08:24:47Z David Kalnischkies kalnischkies@gmail.com 2012-08-04T08:24:47Z urn:sha1:e3348f474f0251a4be0cb0cb7ae8a07ad746311b it is used for the msync call 2012-08-04T08:20:30Z Pino Toscano pino@debian.org 2012-08-04T08:20:30Z urn:sha1:3ac981df108470b42b89d0d4a816a5e3ba58c501 - guard only the msync call with _POSIX_SYNCHRONIZED_IO rather than also the fallback code as it breaks APT on hurd since 0.9.7.3 as the fallback is now always used on non-linux (Closes: #683354) 2012-07-24T15:22:25Z David Kalnischkies kalnischkies@gmail.com 2012-07-24T15:22:25Z urn:sha1:fbda0ee9d9f5ecd34d38f0e416837e8ef3a10f68 SyncToFd dummy just as we did for compressed files in 0.9.5