summaryrefslogtreecommitdiff
path: root/debian
Commit message (Collapse)AuthorAgeFilesLines
* apt.cron.daily: Reference 10periodic instead of 02periodicJulian Andres Klode2015-08-121-1/+1
| | | | LP: #1332106
* debian/control: Rename libapt-pkg4.15 -> libapt-pkg5.0Julian Andres Klode2015-08-111-1/+1
|
* debian/gbp.conf: Set multimaint-merge = TrueJulian Andres Klode2015-08-111-1/+2
| | | | Gbp-Dch: ignore
* Bump apt-inst SONAME to 2.0 to adjust for the ABI break in apt-pkgJulian Andres Klode2015-08-114-73/+73
|
* Merge changelog entries from sid-gcc5Julian Andres Klode2015-08-111-0/+56
|
* move manual-bit from 'oldlibs' pkg to its dependenciesDavid Kalnischkies2015-08-101-0/+4
| | | | | | | | | | | | | | | | | | | | | oldlibs used to be in APT::Never-MarkAuto-Sections so that old transition packages can be removed without causing the then (autoinstalled) renamed package to be autoremoved. It isn't ideal through as ideally you want the oldlibs package to be removed after nothing depends on it anymore regardless of if you have once installed it by hand or not – and if you had the package talking over (the dependencies) should carry the manual bit now as they are the real deal now. As an added bonus if the package has no dependencies because it is an oldlibs without a direct replacement you should move away from (like lib1 and lib2 are currently in the archive, but there will hopefully only be lib2 in the release) you get a lib1 marked as auto. If the user still needs the oldlibs package for some reason all he has to do is mark it as manual once as this move is only performed if a installed package changes its section from a not-Move-Autobit-Sections to a Move-Autobit-Sections.
* change to libapt-pkg abi 5.0 with versioned symbolsDavid Kalnischkies2015-08-104-1568/+1571
| | | | | | | | | | | We changed an aweful lot of stuff, so 5.0 is properly better than 4.X as a semantic version and as we are at it lets add some trivial symbol versioning as well: We just mark all exported symbols with the same version for now. This isn't really the proper thing to do as if we add symbols in later versions (with the same abi) they will get the same symbols version, but our .symbols file will protect us from the problems arising from this as it will ensure that a package acutally depends on a version of the abi high enough to include the symbol.
* update symbols file to current state of affairsDavid Kalnischkies2015-08-102-513/+563
| | | | | | | | | cxx11abi transition happens, we changed a bunch of methods and all that stuff which is really good™ for an abi. Lets just slowly start to stop changing more and a first step is to document the current so changes aren't hidding in a big wall of change anymore. Git-Dch: Ignore
* enforce GCC5 C++11 ABI and usageDavid Kalnischkies2015-08-101-1/+2
| | | | | | | | The library(s) make an API break anyhow, so lets ensure we use gcc5 for this break and enable c++11 as standard as gcc6 will use it as default and should provide some API parts for c++11 – beside that it can't hurt to use c++11 itself. We just have to keep our headers c++03 compatible to not enforce a standrd bump in our reverse dependencies.
* merge keyrings with cat instead of gpg in apt-keyDavid Kalnischkies2015-08-101-1/+1
| | | | | | | | | | | | | | | | | | | If all keyrings are simple keyrings we can merge the keyrings with cat rather than doing a detour over gpg --export | --import (see #790665), which means 'apt-key verify' can do without gpg and just use gpgv as before the merging change. We declare this gpgv usage explicit now in the dependencies. This isn't a new dependency as gnupg as well as debian-archive-keyring depend on and we used it before unconditionally, just that we didn't declare it. The handling of the merged keyring needs to be slightly different as our merged keyring can end up containing the same key multiple times, but at least currently gpg does remove only the first occurrence with --delete-keys, so we move the handling to a if one is gone, all are gone rather than an (implicit) quid pro quo or even no effect. Thanks: Daniel Kahn Gillmor for the suggestion
* Merge remote-tracking branch 'donkult/debian/experimental' into ↵Michael Vogt2015-06-234-415/+135
|\ | | | | | | debian/experimental
| * Merge branch 'debian/sid' into debian/experimentalMichael Vogt2015-05-221-0/+10
| |\ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: apt-pkg/pkgcache.h debian/changelog methods/https.cc methods/server.cc test/integration/test-apt-download-progress
| | * releasing package apt version 1.0.9.9Michael Vogt2015-04-281-0/+10
| | |
| * | sync TFRewrite*Order arrays with dpkg and dakDavid Kalnischkies2015-05-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dpkg and dak know various field names and order them in their output, while we have yet another order and have to play catch up with them as we are sitting between chairs here and neither order is ideal for us, too. A little testcase is from now on supposed to help ensureing that we do not derivate to far away from which fields dpkg knows and orders.
| * | Merge branch 'debian/jessie' into debian/experimentalDavid Kalnischkies2015-04-191-0/+19
| |\| | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: apt-pkg/acquire-item.cc cmdline/apt-key.in methods/https.cc test/integration/test-apt-key test/integration/test-multiarch-foreign
| | * release 1.0.9.8David Kalnischkies2015-04-131-0/+19
| | |
| * | merge debian/sid into debian/experimentalDavid Kalnischkies2015-03-163-1/+105
| |\|
| | * releasing package apt version 1.0.9.7Michael Vogt2015-02-231-0/+7
| | |
| | * prepare 1.0.9.6Michael Vogt2015-01-161-0/+12
| | |
| | * release 1.0.9.51.0.9.5David Kalnischkies2014-12-231-0/+26
| | |
| | * tighten filtering of kernel images in apt.auto-removalJames McCoy2014-12-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current filtering matches the names of the image metapackages on the i386 architecture: $ dpkg-query -l | awk '/^ii[ ]+(linux|kfreebsd|gnumach)-image-[0-9]/ && $2 !~ /-dbg$/ { print $2 }' linux-image-3.16.0-4-586 linux-image-586 This results in an extra image package being removed from APT::NeverAutoRemove, losing the intended effect of keeping the {current, previous, latest} set of images installed. Requiring a “.” in the package name tightens the matched package names to those that are installing a specific version of the image, thus eliding the meta-packages. Closes: 772732
| | * release 1.0.9.41.0.9.4David Kalnischkies2014-12-031-0/+41
| | |
| | * use 'best' hash for source authenticationDavid Kalnischkies2014-11-101-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Collect all hashes we can get from the source record and put them into a HashStringList so that 'apt-get source' can use it instead of using always the MD5sum. We therefore also deprecate the MD5 struct member in favor of the list. While at it, the parsing of the Files is enhanced so that records which miss "Files" (aka MD5 checksums) are still searched for other checksums as they include just as much data, just not with a nice and catchy name. This is a cherry-pick of 1262d35 with some dirty tricks to preserve ABI. LP: 1098738
| | * add a simple container for HashStringsDavid Kalnischkies2014-11-101-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | APT supports more than just one HashString and even allows to enforce the usage of a specific hash. This class is intended to help with storage and passing around of the HashStrings. The cherry-pick here the un-const-ification of HashType() compared to f4c3850ea335545e297504941dc8c7a8f1c83358. The point of this commit is adding infrastructure for the next one. All by itself, it just adds new symbols. Git-Dch: Ignore
| * | streamline display of --help in all toolsDavid Kalnischkies2014-11-091-0/+1
| | | | | | | | | | | | | | | | | | | | | By convention, if I run a tool with --help or --version I expect it to exit successfully with the usage, while if I do call it wrong (like without any parameters) I expect the usage message shown with a non-zero exit.
| * | restore ABI of pkgTagSectionDavid Kalnischkies2014-11-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | We have a d-pointer available here, so go ahead and use it which also helps in hidding some dirty details here. The "hard" part is keeping the abi for the inlined methods so that they don't break – at least not more than before as much of the point beside a speedup is support for more than 256 fields in a single section.
| * | explicit overload methods instead of adding parametersDavid Kalnischkies2014-11-081-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | Adding a new parameter (with a default) is an ABI break, but you can overload a method, which is "just" an API break for everyone doing references to this method (aka: nobody). Git-Dch: Ignore
| * | mark internal interfaces as hiddenDavid Kalnischkies2014-11-081-419/+0
| | | | | | | | | | | | | | | | | | | | | We have a bunch of classes which are of no use for the outside world, but were still exported and so needed to preserve ABI/API. Marking them as hidden to not export them any longer is a big API break in theory, but in practice nobody is using them – as if they would its a bug.
| * | better non-virtual metaIndex.LocalFileName() implementationDavid Kalnischkies2014-11-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | We can't add a new virtual method without breaking the ABI, but we can freely add new methods, so for older ABIs we just implement this method with a dynamic_cast, so that clients can be more ignorant about the API here and especially don't need to pull a very dirty trick by assuming internal knowledge (like apt-get did here).
* | | Add "ca-certificates" recommends to apt-transport-httpsMichael Vogt2015-03-171-0/+1
|/ / | | | | | | | | The rational is that https downloads fail with cryptic error messages if the certificates are missing.
* | releasing package apt version 1.1~exp8Michael Vogt2014-11-061-0/+21
| |
* | Update symbols fileMichael Vogt2014-11-061-10/+1
| | | | | | | | Git-Dch: ignore
* | Bump ABI to 4.15Michael Vogt2014-11-053-1/+1
| |
* | Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-11-051-0/+16
|\| | | | | | | | | Conflicts: debian/changelog
| * releasing package apt version 1.0.9.3Michael Vogt2014-10-151-0/+16
| |
* | Ensure /etc/apt/auth.conf has _apt:root ownerMichael Vogt2014-10-211-5/+0
| | | | | | | | | | Ensure in SetupAPTPartialDirectory() that the /etc/apt/auth.conf file can be read by the priv sep apt methods.
* | debian/apt.postinst: chown _apt:root /etc/apt/auth.confMichael Vogt2014-10-211-0/+5
| | | | | | | | | | If the methods drop privileges we need to ensure that /etc/apt/apt.conf is still readable by the _apt user.
* | releasing package apt version 1.1~exp7Michael Vogt2014-10-151-0/+8
| |
* | releasing package apt version 1.1~exp6Michael Vogt2014-10-151-0/+18
| |
* | Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-10-141-1/+1
|\|
| * add CVE-2014-7206 to 1.0.9.2Michael Vogt2014-10-081-1/+1
| |
* | releasing package apt version 1.1~exp5Michael Vogt2014-10-131-0/+20
| |
* | update symbols fileDavid Kalnischkies2014-10-131-36/+61
| | | | | | | | Git-Dch: Ignore
* | releasing package apt version 1.1~exp4Michael Vogt2014-10-081-1/+1
| |
* | prepare 1.1~exp4Michael Vogt2014-10-081-0/+80
| |
* | Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-10-081-0/+28
|\| | | | | | | | | Conflicts: debian/changelog
| * releasing package apt version 1.0.9.2Michael Vogt2014-10-021-0/+28
| |
| * debian/rules: add hardening=+allMichael Vogt2014-10-011-3/+6
| | | | | | | | | | | | | | Because of dpkg-buildflags we already get most of the hardening features, +all adds -fPIE and ld -z now Thanks: Simon Ruderich, Markus Waldeck
* | Merge remote-tracking branch 'upstream/debian/experimental' into ↵Michael Vogt2014-10-075-117/+316
|\ \ | | | | | | | | | | | | | | | | | | feature/acq-trans Conflicts: apt-pkg/acquire-item.cc
| * | Bump library version to libapt-pkg4.14Michael Vogt2014-10-033-2/+2
| | |