summaryrefslogtreecommitdiff
path: root/debian
Commit message (Collapse)AuthorAgeFilesLines
* unbreak the copy-method claiming hashsum mismatch since ~exp9David Kalnischkies2015-11-041-1/+1
| | | | | | | | | | | | | | | | Commit 653ef26c70dc9c0e2cbfdd4e79117876bb63e87d broke the camels back in sofar that everything works in terms of our internal use of copy:/, but external use is completely destroyed. This is kinda the reverse of what happened in "parallel" in the sid branch, where external use was mostly fine, internal and external exploded on the GzipIndexes option. We fix this now by rewriting our internal use by letting copy:/ only do what the name suggests it does: Copy files and not uncompress them on-the-fly. Then we teach copy and the uncompressors how to deal with /dev/null and use it as destination file in case we don't want to store the uncompressed files on disk. Closes: 799158
* orderlist: Replace qsort() by thread-safe std::sort()Julian Andres Klode2015-10-301-1/+0
| | | | Gbp-Dch: ignore
* algorithms: Replace qsort() by thread-safe std::sort()Julian Andres Klode2015-10-301-1/+0
| | | | Gbp-Dch: ignore
* releasing 1.1~exp141.1_exp14Michael Vogt2015-10-201-0/+9
|
* releasing package apt version 1.1~exp131.1.exp13Michael Vogt2015-10-051-0/+28
|
* tests: don't use hardcoded port for http and httpsDavid Kalnischkies2015-09-151-1/+1
| | | | | | This allows running tests in parallel. Git-Dch: Ignore
* tests: try to support spaces in TMPDIRDavid Kalnischkies2015-09-141-1/+1
| | | | | | | | Not all tests work yet, most notable the cdrom tests, but those require changes in libapt itself to have a proper fix and what we have fixed so far is good enough progress for now. Git-Dch: Ignore
* dereference redirect in Vcs-Browser URI to cgitDavid Kalnischkies2015-09-141-1/+1
| | | | Git-Dch: Ignore
* include debug information in the autoremove-kernels fileDavid Kalnischkies2015-09-141-3/+23
| | | | | | | | Figuring out after the fact what went wrong in the kernel hook is kinda hart, also as the bugreports are usually very lacking on the details front. Collecting the internal variables in the debug output we attach to the generated file might help shine some light on the matter. It's at least not going to hurt…
* select kernels to protect from autoremove based on Debian versionDavid Kalnischkies2015-09-141-50/+24
| | | | | | | | | | | | | | | | | | This is basically a rewrite of the script with the general idea of finding the Debian version of the installed kernels – as multiple flavours will have the same Debian version – select the two newest of them and translate them back to versions found in package names. This way we avoid e.g. kernel and kernel-rt to use up the protected slots even through they are basically the same kernel (just a different flavour) so it is likely that if kernel doesn't work for some reason, kernel-rt will not either. This also deals with foreign kernel packages, kernels on hold and partly installed kernels (in case multiple kernels are installed in the same apt run) in a hopefully sensible way. Closes: 787827
* releasing package apt version 1.1~exp12Michael Vogt2015-09-111-0/+30
|
* remove Christian Perrier from Uploaders as requestedDavid Kalnischkies2015-08-311-1/+1
| | | | | Closes: #783337 Thanks: Christian for all the l10n, code & social contributions!
* Release 1.11~exp111.1.exp11Julian Andres Klode2015-08-271-0/+27
|
* debian/rules: Only do parallel build if specified in DEB_BUILD_OPTIONSJulian Andres Klode2015-08-271-0/+4
| | | | | | It was not nice to use 2 * number of cores in all cases. Thanks: Jakub Wilk for the suggestion
* fix various typos reported by codespellDavid Kalnischkies2015-08-271-41/+41
| | | | Reported-By: codespell
* lintian: don't show the typofix as a typoDavid Kalnischkies2015-08-271-3/+3
| | | | Git-Dch: Ignore
* add a libapt-pkg recommends aptDavid Kalnischkies2015-08-271-0/+1
| | | | | | | | | | | | For many usecases like the acquire system libapt-pkg actually needs tools and config found in the apt package. apt tends to be installed everywhere libapt-pkg appears usually anyhow, but just in case to nudge users (and tools) in the right direction. Note that this isn't and shouldn't be a hard depends as there are usecases working perfectly without 'apt' and as this is such an esoteric problem incurring the costs arising from a Depends-Breaks-loop isn't deemd as worth it.
* releasing package apt version 1.1~exp10Michael Vogt2015-08-241-0/+16
|
* postinst: Correctly pass --home instead of -home, and fixup old userJulian Andres Klode2015-08-201-1/+6
| | | | Thanks: Niels Thykier for reporting this on IRC
* releasing package apt version 1.1~exp9Michael Vogt2015-08-182-1/+283
|
* Re-add support for G++ 4.8 and configure travis to use itJulian Andres Klode2015-08-171-1/+1
| | | | | | This makes tests work again! Gbp-Dch: ignore
* debian/NEWS: Mention new pinning algorithm added in 2.0~exp1Julian Andres Klode2015-08-171-0/+12
|
* add {contrib,non-free}/{metapackages,oldlibs} to section specialhandlingDavid Kalnischkies2015-08-141-0/+4
| | | | Closes: 788320
* debian/control: Remove XS- from Testsuite and bump Standards-VersionJulian Andres Klode2015-08-141-2/+2
| | | | Thanks: Lintian
* debian/control: Drop the versioned python-apt conflictJulian Andres Klode2015-08-141-1/+0
| | | | Thanks: Lintian
* debian/control: Replace debian by DebianJulian Andres Klode2015-08-141-1/+1
| | | | Thanks: Lintian
* changelog: Replace reenable by re-enable everywhereJulian Andres Klode2015-08-141-5/+5
| | | | Thanks: Lintian
* document APT::Periodic::RandomSleepTomas Pospisek2015-08-121-0/+13
| | | | | | | | | | | | | | | | | | | | The documentation in the patch is from https://help.ubuntu.com/community/AutomaticSecurityUpdates That page is licensed under Creative Commons Attribution-ShareAlike 3.0. Because I'm unsure how that license meshes with apt's license I've not copied the text but formulated the same information freely in my own words. The original text was contributed by Chris Bainbridge [1][3] and Kees Cook [2]. Thanks to them. [1] https://help.ubuntu.com/community/AutomaticSecurityUpdates?action=diff&rev1=40&rev2=41 [2] https://help.ubuntu.com/community/AutomaticSecurityUpdates?action=diff&rev1=38&rev2=39 [3] https://help.ubuntu.com/community/AutomaticSecurityUpdates?action=diff&rev1=37&rev2=38 Closes: 776380 Thanks: Chris Bainbridge and Kees Cook for initial text
* 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
| | |
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 18:38:32 +0000