summaryrefslogtreecommitdiff
path: root/debian/control
Commit message (Collapse)AuthorAgeFilesLines
* move 'dump' solver from apt-utils to apt packageDavid Kalnischkies2016-06-081-2/+2
|
* use https instead of git for Vcs-GitDavid Kalnischkies2016-05-241-1/+1
| | | | | Reported-By: lintian: vcs-field-uses-insecure-uri Git-Dch: Ignore
* no-change bump of Standards-Version to 3.9.8David Kalnischkies2016-05-241-1/+1
| | | | We don't have no menu file.
* move gnupg|gnupg2 from apt Depends to RecommendsDavid Kalnischkies2016-05-011-1/+2
| | | | | | | | | | | | apt doesn't need gnupg in its main execution paths to function, especially the Release file verification is done with gpgv only. It is only used by apt-key for advanced key management functionality most user will never use nor need. The intend is to demote it eventually to Suggests, but we opt here for a staged downgrade as there are still third-party repositories out there which require apt-key functionality without depending on gnupg (or apt for that matter).
* Use systemd.timer instead of a cron jobMichael Vogt2016-04-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | The rational is that we need to spread the load on the mirrors that apt update and unattended-upgrades cause. To do so, we leverage the RandomizeDelay feature of systemd. The other advantage is that the timer is not run at a fixed daily.daily time but instead every 24h. This also fixes the problem that the randomized deplay in the current apt.cron.daily causes other cron jobs to be deplayed. A compatibility cron job is also provided for systems that do not use systemd. Note that the time is fired two times a day, but the logic inside of apt.systemd.daily will ensure (via stamp files) that the servers are hit at most every 24h. Firing two times a day helps with the worst case update time and it also helps with systems that are not always on. LP: #246381, #727685 Closes: #600262, #709675, #663290
* debian/control: Set Standards-Version to 3.9.7Julian Andres Klode2016-03-061-1/+1
| | | | | | | We do not follow the recommendation with regards to placement of documentation in apt-doc, as we install in apt-doc, but it's only a recommendation and I don't want think we should move them.
* Drop the g++ build-dep, transition is doneJulian Andres Klode2016-02-031-2/+1
| | | | | | It's not cross-satisfiable. Reported-by: Helmut Grohne
* Version the build-depends on liblz4-dev to >= 0.0~r126Julian Andres Klode2016-01-091-1/+1
| | | | | We need r126 of lz4, as this introduces the lz4frame.h header.
* Bump dpkg-dev and debhelper build-dep to make lintian happyJulian Andres Klode2016-01-091-1/+1
| | | | | | | This is not really needed anymore, as those are in stable, but as they are versioned already, let's just do it. Gbp-Dch: ignore
* Do not break apt-file (<< 3.0~exp1~), 2.X works fineJulian Andres Klode2016-01-091-1/+1
| | | | | There's no point in breaking all older apt-file versions just because one old experimental upload was broken.
* Break apt-file (<< 3.0~exp1~)Julian Andres Klode2016-01-081-1/+1
| | | | Gbp-Dch: ignore
* libapt-pkg5.0: Add Breaks appstream (<< 0.9.0-3~)Julian Andres Klode2016-01-081-1/+1
| | | | | | This ensures that a compatible version of appstream is installed, that is, one that disables lz4 compression for its data.
* FileFd: (native) LZ4 supportJulian Andres Klode2016-01-071-1/+1
| | | | | Implement native support for LZ4 compression, using the official lz4 library.
* Allow building without libgtest-dev under <nocheck> build profileHelmut Grohne2016-01-031-1/+1
| | | | | | | | | | | | | | I'd like to avoid pulling libgtest-dev into the bootstrap set. Fortunately, libgtest-dev is only used for testing apt and apt correctly implements DEB_BUILD_OPTIONS=nocheck now. So this bug is about getting rid of the Build-Depends. Simply removing it (by adding a build profile) is not sufficient however as configure fails hard, so an additional bit is necessary to cover for that. Closes: #809726
* Add bash-completion support for the "apt" commandMichael Vogt2016-01-021-1/+1
| | | | | | | | | | | | | The apt bash-completion support was submited to the bash-completion package as a patch in May 2014. It is still not included to this date and because it is an important feature for many users it is now part of apt until the bash-completion package is mantained more actively again. Note that the "Relaces" line is only required for Ubuntu it will have no effect on Debian. Closes: #747094
* add a apt breaks (apt-utils << 1.1.3) for partial-upgradesDavid Kalnischkies2015-12-011-1/+1
| | | | | | | | You could think a0bf789783ea283914d059aea0f4d0f77d6bbaaf would be enough, but it turns out its only half of the puzzle. Closes: 806765 Suggested-By: Julian Andres Klode <jak@debian.org>
* add apt-utils Depends apt (= ${binary:Version})David Kalnischkies2015-11-291-1/+1
| | | | | | As we ship some tools in apt-utils which depend on our private library we have to ensure that apt-utils depends on a proper apt version. An exact version is probably a bit much, but the simplest way out.
* 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
* dereference redirect in Vcs-Browser URI to cgitDavid Kalnischkies2015-09-141-1/+1
| | | | Git-Dch: Ignore
* remove Christian Perrier from Uploaders as requestedDavid Kalnischkies2015-08-311-1/+1
| | | | | Closes: #783337 Thanks: Christian for all the l10n, code & social contributions!
* 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.
* 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/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
* debian/control: Rename libapt-pkg4.15 -> libapt-pkg5.0Julian Andres Klode2015-08-111-1/+1
|
* Bump apt-inst SONAME to 2.0 to adjust for the ABI break in apt-pkgJulian Andres Klode2015-08-111-1/+1
|
* 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
* 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.
* Bump ABI to 4.15Michael Vogt2014-11-051-1/+1
|
* Bump library version to libapt-pkg4.14Michael Vogt2014-10-031-1/+1
|
* adjust version numbers for the planed uploadMichael Vogt2014-09-301-1/+1
|
* Add missing "adduser" dependency (for the new _apt user)Michael Vogt2014-09-291-1/+1
| | | | | Closes: #763004 Thanks: Russ Allbery
* add and use 'apt-key verify' which prefers gpgv over gpgDavid Kalnischkies2014-09-271-1/+1
| | | | | | | | | | | | | gnupg/gnupg2 can do verify just fine of course, so we don't need to use gpgv here, but it is what we always used in the past, so there might be scripts expecting a certain output and more importantly the output of apt-cdrom contains messages from gpg and even with all the settings we activate to prevent it, it still shows (in some versions) a quiet scary: "gpg: WARNING: Using untrusted key!" message. Keeping the use of gpgv is the simplest way to prevent it. We are increasing also the "Breaks: apt" version from libapt as it requires a newer apt-key than might be installed in partial upgrades.
* support gnupg2 as drop-in replacement for gnupgDavid Kalnischkies2014-09-271-1/+1
| | | | | | If both are available APT will still prefer gpg over gpg2 as it is a bit more lightweight, but it shouldn't be a problem to use one or the other (at least at the moment, who knows what will happen in the future).
* restore breaks against libapt-inst1.5 (<< 0.9.9)Michael Vogt2014-07-101-1/+1
|
* Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-07-081-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: apt-pkg/deb/deblistparser.cc doc/po/apt-doc.pot doc/po/de.po doc/po/es.po doc/po/fr.po doc/po/it.po doc/po/ja.po doc/po/pl.po doc/po/pt.po doc/po/pt_BR.po po/da.po po/mr.po po/vi.po
| * build: Convert from DebianDoc SGML to DocBook XMLGuillem Jover2014-07-081-1/+1
| |
* | increase libapt-inst to version 1.6Michael Vogt2014-07-081-2/+2
| |
* | Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-05-071-6/+6
|\| | | | | | | | | | | | | | | | | | | | | | | Conflicts: apt-pkg/cachefilter.h apt-pkg/contrib/fileutl.cc apt-pkg/contrib/netrc.h apt-pkg/deb/debsrcrecords.cc apt-pkg/init.h apt-pkg/pkgcache.cc debian/apt.install.in debian/changelog
| * use Google C++ Testing Framework for libapt testsDavid Kalnischkies2014-04-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | My commit 45df0ad2 from 26. Nov 2009 had a little remark: "The commit also includes a very very simple testapp." This was never intended to be permanent, but as usually… The commit adds the needed make magic to compile gtest statically as it is required and links it against a small runner. All previous testcase binaries are reimplemented in gtest and combined in this runner. While most code is a 1:1 translation some had to be rewritten like compareversion_test.cc, but the coverage remains the same.
| * Add versioned openjdk-6-jdk breaksJulian Andres Klode2014-04-071-2/+2
| | | | | | | | | | This helps if people did unclean upgrades from squeeze, namely to jessie directly.
| * Version the Breaks/Replaces for sun-java{5,6}-jdk (LP: #1302736)Julian Andres Klode2014-04-071-2/+2
| | | | | | | | | | | | | | This is a *hack* to work around unofficial packages for Java 7 and 8 that wrongly provide the Java 5 and 6 packages. Closes: #743616
| * add sun-java{5,6}-jdk to breaks/replaces as that provided a "apt" binary as wellMichael Vogt2014-04-011-2/+2
| |
| * use liblzma-dev to provide xz/lzma supportDavid Kalnischkies2014-03-131-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | We have xz/lzma support for a while, but only via an external binary provided by xz-utils. Now that the Debian archive provides xz by default and dpkg pre-depends on the library provided by liblzma-dev we can switch now to use this library as well to avoid requiring an external binary. For now the binary is in a prio:required package, but this might change in the future. API wise it is quiet similar to bz2 code expect that it doesn't provide file I/O methods, so we piece this together on our own.
| * support DEB_BUILD_PROFILES and -P for build profilesDavid Kalnischkies2014-03-131-1/+1
| | | | | | | | | | | | | | | | | | | | Inspired by the rest of the patch in 661537, but abstract the parsing of various ways of setting the build profiles more so it can potentially be reused and all apt parts have the same behaviour. Especially config options, cmdline options and environment will not be combined as proposed as this isn't APTs usual behaviour and dpkg doesn't do it either, so one overrides the other as it normally does.
| * Promote xz-utils from apt Suggests to libapt-pkg DependsJulian Andres Klode2014-03-121-2/+2
| | | | | | | | | | | | libapt-pkg depends on the other compressors, and now that xz is the default in many cases, it should depend on that one as well.
* | Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-02-271-7/+8
|\| | | | | | | | | | | | | | | Conflicts: apt-private/private-list.cc configure.ac debian/apt.install.in debian/changelog
| * bump Standards-Version to 3.9.5 (no changes needed)David Kalnischkies2014-02-101-1/+1
| |
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-05-12 19:18:55 +0000