summaryrefslogtreecommitdiff
path: root/apt-pkg
AgeCommit message (Collapse)AuthorFilesLines
2013-10-05* move upgrade releated code into upgrade.{cc,h}Michael Vogt5-255/+300
The upgrade releated code is moved into upgrade.{cc,h} and all pkg*Upgrade* prototypes are included in algorihms.h to avoid breaking API (unless build with APT_9_CLEANER_HEADERS).
2013-10-05cleanup upgrade API some more (thanks for the feedback from David)Michael Vogt2-14/+21
2013-09-18improve the API for Upgrade()Michael Vogt2-10/+40
2013-08-31fix typo (mkostemp->mkstemp)Michael Vogt1-1/+1
2013-08-28Merge remote-tracking branch 'mvo/feature/install-progress' into debian/sidMichael Vogt2-1/+18
2013-08-27use mkstemp instead of mkostemp in FileFd::Open()David Kalnischkies1-8/+4
FileFd currently supports no fileflags which would make sense to provide via mkostemp, so we can just use mkstemp here which is a standard function compared to glib extension mkostemp. O_CREAT (Create) and O_TRUNC (Empty) are implied by O_EXCL, which is the mode mkstemp uses by default. The file description is opened ReadWrite, but that used to be the default for FileFd in the old times and not a problem as the difference is needed by FileFd to decide in which way the compressor pipeline needs to be created (if any). Git-Dch: Ignore
2013-08-27replace usage of potential dangerous mktemp with mkstempAngel Guzman Maeso1-5/+19
Avoid the warning "the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp'". It is not strictly necessary to change the usage from a security point of view here, but mktemp is also removed from the standard since POSIX.1-2008. The mkostemp call returns a file descriptor the logic for TemporaryFileName has been changed accordingly to get the same results. The file permissions are corrected by using fchmod() as the default for FileFd is 666 while mkstemp creates files with 600 by default.
2013-08-22do chdir("/") after chroot()Michael Vogt2-2/+2
2013-08-22apt-pkg:contrib Avoid compiler warning about sign-compareÁngel Guzmán Maeso1-1/+2
The fix avoid the warning "comparison between signed and unsigned integer expressions [-Wsign-compare]"· The index for the loop needs to be unsigned for compare with globbuf.gl_pathc structure member
2013-08-22Merge remote-tracking branch 'mvo/bugfix/coverity' into debian/sidMichael Vogt5-1/+16
Conflicts: apt-pkg/tagfile.h
2013-08-17Merge remote-tracking branch 'mvo/feature/apt-binary2' into debian/sidMichael Vogt10-6/+291
Conflicts: cmdline/apt-get.cc
2013-08-16allow Pre-Install-Pkgs hooks to get info over an FD != stdinDavid Kalnischkies1-5/+15
This adds ::InfoFD option alongside the ::Version one to request sending the information to the specified FD, by default it is STDIN as it was the case before. The environment variable APT_HOOK_INFO_FD contains the FD the data is on as a confirmation that the APT version used understood the request. Allowing the hook to choose the FD is needed/helpful e.g. for shellscripts which have a hard time accessing FDs above 9 (as >= 10 are usually used internally by them) Closes: #671728
2013-08-15use malloc instead of new[] in pkgTagFileDavid Kalnischkies1-15/+15
We don't need initialized memory for pkgTagFile, but more to the point we can use realloc this way which hides the bloody details of increasing the size of the buffer used. Git-Dch: Ignore
2013-08-15ensure that pkgTagFile isn't writing past Buffer lengthDavid Kalnischkies2-9/+25
In 91c4cc14d3654636edf997d23852f05ad3de4853 I removed the +256 from the pkgTagFile call parsing Release files as I couldn't find a mentioning of a reason for why and it was marked as XXX which suggested that at least someone else was suspicious. It turns out that it is indeed "documented", it just didn't found it at first but the changelog of apt 0.6.6 (29. Dec 2003) mentions: * Restore the ugly hack I removed from indexRecords::Load which set the pkgTagFile buffer size to (file size)+256. This is concealing a bug, but I can't fix it right now. This should fix the segfaults that folks are seeing with 0.6.[45]. The bug it is "hiding" is that if pkgTagFile works with a file which doesn't end in a double newline it will be adding it without checking if the Buffer is big enough to store them. Its also not a good idea to let the End pointer be past the end of our space, even if we don't access the data. Closes: 719629
2013-08-15init the pkgTagFile with the size of the Release fileDavid Kalnischkies2-2/+2
Release files are basically one big Section, so we might safe some Resize circles by starting with the filesize. Git-Dch: Ignore
2013-08-15add PACKAGE_MATCHER_ABI_COMPAT mode for now so that this branch can be ↵Michael Vogt1-1/+62
merged without breaking ABI
2013-08-15* lp:~mvo/apt/add-glob-function:Michael Vogt2-0/+34
- add Glob() to fileutl.{cc,h} Conflicts: apt-pkg/contrib/fileutl.h debian/changelog
2013-08-15* lp:~mvo/apt/config-clear:Michael Vogt2-0/+13
- support Configuration.Clear() for a clear of the entire configuration Conflicts: debian/changelog
2013-08-15make destructors virtualMichael Vogt1-3/+3
2013-08-12squash merge of the feature/apt-binary branch without the changes from ↵Michael Vogt10-12/+236
experimental
2013-08-12use our _error stack to generate openpty errorsDavid Kalnischkies1-7/+13
While we don't want these error messages on our usual stack, we can use our usual infrastructure to generate an error message with all the usual bells like errno and strerror attached. Git-Dch: Ignore
2013-08-12do not try to chown if not run as rootDavid Kalnischkies1-8/+9
If this code is run as non-root we are in a special situation (e.g. in our testcases) where it is obvious that we can't enforce user/group on any file, so skip this code altogether instead of bugging users with an error message – which we also switch to a warning as a failure to open the file is "just" a warning, so the 'wrong' owner shouldn't be that much of an issue. The file is still handled with chmod, so all the security we can enforce is still enforced of course, which also gets a warning if it fails. Git-Dch: Ignore
2013-08-12fix: --print-uris removes authenticationDavid Kalnischkies2-4/+29
The constructors of our (clear)sign-acquire-items move a pre-existent file for error-recovery away, which gets restored or discarded later as the acquire progresses, but --print-uris never really starts the acquire process, so the files aren't restored (as they should). To fix this both get a destructor which checks for signs of acquire doing anything and if it hasn't the file is restored. Note that these virtual destructors theoretically break the API, but only with classes extending the sign-acquire-items and nobody does this, as it would be insane for library users to fiddle with Acquire internals – and these classes are internals. Closes: 719263
2013-08-12some more coverity fixesMichael Vogt3-0/+5
2013-08-08fix -Wall errorsMichael Vogt3-4/+6
2013-08-08use pkgTagFile to parse "header" of Release filesDavid Kalnischkies1-85/+19
The handwritten parsing here was mostly done as we couldn't trust the Release file we got, but nowadays we are sure that the Release file is valid and contains just a single section we want it to include. Beside reducing code it also fixes a bug: Fieldnames in deb822 formatted files are case-insensitive and pkgTagFile does it correctly, but this selfbuilt stuff here didn't.
2013-08-08stop skipping "-----" sections in Release filesDavid Kalnischkies1-11/+6
The file we read will always be a Release file as the clearsign is stripped earlier in this method, so this check is just wasting CPU Its also removing the risk that this could ever be part of a valid section, even if I can't imagine how that should be valid. Git-Dch: Ignore
2013-08-08specific pins below 1000 cause downgradesDavid Kalnischkies1-7/+18
We start your quest by using the version of a package applying to a specific pin, but that version could very well be below the current version, which causes APT to suggest a downgrade even if it is advertised that it never does this below 1000. Its of course questionable what use a specific pin on a package has which has a newer version already installed, but reacting with the suggestion of a downgrade is really not appropriated (even if its kinda likely that this is actually the intend the user has – it could just as well be an outdated pin) and as pinning is complicated enough we should atleast do what is described in the manpage. So we look out for the specific pin and if we haven't seen it at the moment we see the installed version, we ignore the specific pin. Closes: 543966
2013-08-06memset() pkgTagSections data to make coverity happyMichael Vogt2-1/+11
2013-08-05Merge remote-tracking branch 'upstream/debian/sid' into bugfix/coverityMichael Vogt5-15/+41
2013-08-05fix some unitialized data membersMichael Vogt3-3/+5
2013-08-01prefer native arch over higher priority for providersColin Watson1-3/+3
The rational from the buglog: > The problem here is that the Priority field in one of the Packages files > is incorrect due to a mishap with reprepro configuration, […] the > amd64 version is Priority: standard but the arm64 version is Priority: > optional (and has a stray "optional: interpreters" field). > […] > However, Priority is a rather weak property of a package because it's > typically applied via overrides, and it's easy for maintainers of > third-party repositories to misconfigure them so that overrides aren't > applied correctly. It shouldn't be ranked ahead of choosing packages > from the native architecture. In this case, I have no user-mode > emulation for arm64 set up, so choosing m4:arm64 simply won't work. This effectly makes the priority the least interesting data point in chosing a provider, which is in line with the other checks we have already order above priority in the past and also has a certain appeal by the soft irony it provides. Closes: #718482
2013-07-28Merge remote-tracking branch 'mvo/bugfix/coverity' into debian/sidMichael Vogt9-18/+22
2013-07-26fix another missing va_end()Michael Vogt1-3/+3
2013-07-26fix some coverity chroot() releated warningsMichael Vogt2-2/+3
2013-07-26ensure that FileFd::Size returns 0 in error casesDavid Kalnischkies1-5/+18
2013-07-26proper cleanup varargs in _error (uncovered by Coverity)David Kalnischkies1-4/+6
Git-Dch: Ignore
2013-07-25pick up Translation-* even if only compressed availableDavid Kalnischkies1-2/+13
On CD-ROMs Translation-* files are only in compressed form included in the Release file. This used to work while we had no record of Translation-* files in the Release file at all as APT would have just guessed the (compressed) filename and accepted it (unchecked), but now that it checks for the presents of entries and if it finds records it expects the uncompressed to be verifiable. This commit relaxes this requirement again to fix the regression. We are still secure "enough" as we can validate the compressed file we have downloaded, so we don't loose anything by not requiring a hashsum for the uncompressed files to double-check them. Closes: 717665
2013-07-25add missing "free(buffer) for allocated bufferMichael Vogt1-1/+0
2013-07-25delete targets dataMichael Vogt1-0/+1
2013-07-25fix resource leak when verification failsMichael Vogt1-0/+1
2013-07-25apt-pkg/indexcopy.cc: check for pending errors before calling fdopen()Michael Vogt1-1/+1
2013-07-25call fdopen() after FileFd was checkedMichael Vogt1-1/+1
2013-07-25fix resource leak (thanks coverity)Michael Vogt1-4/+8
2013-07-25rework the code in cdromutl.cc to make coverity (more) happyMichael Vogt1-1/+2
2013-07-25fix off-by-one error and do not use magic constant of 100 when checking ↵Michael Vogt1-1/+1
StackPost
2013-07-25always "delete d" in FileFd::~FileFd to coverity happyMichael Vogt1-4/+2
2013-07-24Merge remote-tracking branch 'upstream/debian/sid'Michael Vogt23-351/+553
2013-07-23remove double list includeMichael Vogt1-1/+0
2013-07-16fix if-clause to generate hook-info for 'rc' packagesDavid Kalnischkies1-1/+1
The code incorrectly skips printing of current version information, if the package has no current version (for APT, but for dpkg as it is the case for packages which are removed but not purged) by using an unintended "else if" rather than an "if". Closes: 717006