summaryrefslogtreecommitdiff
path: root/apt-private/private-update.cc
AgeCommit message (Collapse)AuthorFilesLines
2017-01-19don't lock dpkg in update commandsDavid Kalnischkies1-2/+2
The update command acquires a lock on lists/, but at the end it will also require the dpkg/lock while building the binary caches. That seems rather pointless as we are only reading those files, not causing writing in them. This can also cause problems if a package installation is running and a background process (like cron) starts an update: If you are "lucky" enough the update process will pick the dpkg lock in between apt calls causing the installation process to fail.
2017-01-19don't show update stats if cache generation is disabledDavid Kalnischkies1-6/+6
Unlikely that anyone is actually running into this, but if we asked to not generate a cache and avoid it in the first step we shouldn't create one implicitly anyway by displaying the statistics.
2016-05-27prevent C++ locale number formatting in text APIsDavid Kalnischkies1-2/+2
Setting the C++ locale via std::locale::global(std::locale("")); which would otherwise default to the default C locale (aka: unaffected by setlocale) effects the formatting of numeric types in IO streams, which for output for humans is perfectly sensible, but breaks our many text interfaces used and parsed by us and others without expecting the numbers to be formatted. Closes: #825396
2015-11-04new quiet level -qq for apt to hide progress outputDavid Kalnischkies1-8/+7
-q is for logging and -qqq (old -qq) basically kills every output expect errors, so there should be a way of declaring a middleground in which the output of e.g. 'update' isn't as verbose, but still shows some things. The test framework was actually making use of by accident as it ignored the quiet level in output setup for apt before. Eventually we should figure out some better quiet levels for all tools…
2015-08-15update: Check if the cache could be opened, don't just assume itJulian Andres Klode1-1/+2
This seems to cause Bug#756162, as in that case the depcache was NULL. I'm not entirely sure how that happens, but it's better to be check here rather then crash later on. Closes: #756162
2015-04-10add a simple unit test for acquire progressDavid Kalnischkies1-2/+2
This isn't testing much of the 'complex' parts, but its better than nothing for now. Git-Dch: Ignore
2014-10-07ensure partial dirs are 0700 and owned by _apt:rootDavid Kalnischkies1-3/+1
Reworks the API involved in creating and setting up the fetcher to be a bit more pleasent to look at and work with as e.g. an empty string for no lock isn't very nice. With the lock we can also stop creating all our partial directories "just in case". This way we can also be a bit more aggressive with the partial directory itself as with a lock, we know we will gone need it.
2014-09-21generalize Acquire::GzipIndexMichael Vogt1-1/+8
2014-07-08Only show packages as upgradable if the have a CandidateVer != 0Michael Vogt1-1/+1
Closes: #753297
2014-06-18use P_ instead of ngettext to compiling with --disable-nlsFredrik Fornwall1-1/+1
Closes: 751857
2014-06-18Tell the user if no updates are available after apt updateMichael Vogt1-1/+4
Thanks to Jakub Wilk for the suggestion. Closes: #751388
2014-05-22show upgradable packages after apt updateMichael Vogt1-0/+18
Closes: 748389
2014-03-13cleanup headers and especially #includes everywhereDavid Kalnischkies1-27/+12
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-13warning: no previous declaration for foobar() [-Wmissing-declarations]David Kalnischkies1-0/+1
Git-Dch: Ignore Reported-By: gcc -Wmissing-declarations
2013-10-05Move ListUpdate/AquireUpdate into update.{cc,h}Michael Vogt1-0/+1
This moves the ListUpdate/AquireUpdate out of the "catch-all" algorithm.{cc,h} file into its own update.{cc,h}
2013-08-12squash merge of the feature/apt-binary branch without the changes from ↵Michael Vogt1-0/+93
experimental