summaryrefslogtreecommitdiff
path: root/debian
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.1.81.1.8Julian Andres Klode2015-12-261-0/+7
| | | | This release is made for Niels Thykier and apt-file.
* Release 1.1.71.1.7Julian Andres Klode2015-12-261-0/+10
|
* 1.1.6 Christmas releaseJulian Andres Klode2015-12-241-0/+22
|
* Release 1.1.51.1.5Julian Andres Klode2015-12-141-0/+29
|
* debian/apt.auto-removal.sh: Adjust -dbg exclusion for multi-archJulian Andres Klode2015-12-141-2/+1
| | | | Allow an optional colon followed by anything at the end.
* tests: Depend on libfile-fcntllock-perl to shut up dpkg-gencontrolJulian Andres Klode2015-12-141-1/+2
| | | | | | | | | | | Ubuntu's autopkgtest server always prints dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe which is somewhat annoying. Work around that by depending on that perl stuff for the test suite. Gbp-Dch: ignore
* redirect which stderr to /dev/null for consistencyDavid Kalnischkies2015-12-141-5/+5
| | | | | | | | | | | | | | | | The "standard" which (debianutils) has no output whatsoever on stderr, bash and dash which use this implementation therefore haven't either. In zsh 'which' is a shell built-in – and has no stderr output either, it does print an error message on stdout… So, realistically, a redirection isn't needed at all, but it also can't hurt (<- I have said that before in this context ->) so why not for consistency with… well, not with "command -v" as that hasn't an error message either. Lets say for consistency with my mental image of shell, as I am still a bit puzzled by zsh's which and now could imagine even more strange things in other shells. Closes: 807373
* update symbols files to 1.1.4 state of affairsDavid Kalnischkies2015-12-131-0/+5
|
* Release 1.1.41.1.4Julian Andres Klode2015-12-071-0/+22
|
* part revert, part redo 'which' replacementDavid Kalnischkies2015-12-072-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | In e75e5879 'replace "which" with "command -v" for portability' I missed that command -v isn't actually required to be available in debian, so for the 5 files we are using it: Two (abicheck/run_abi_test & test/integration/framework) are called in environments were I believe sh is at least dash or 'better' as the first one is "interactive" for apt developers and the later is sourced by ~200 tests in the same directory run by hand and ci-services – for the later we have pulled some uglier hacks for worser things already, so if there should actually end up needing something more compatible we will notice eventually (and the later actually had a command -v call for some time already and nobody came running). debian/rules and debian/apt.cron.daily I switched back to which as that is more or less debian-specific or at least highly non-critical. That leaves cmdline/apt-key.in with a bunch of calls where I will implement that functionality in shell as this is relatively short-lived as it is used to detect wget (for net-update, which Michael wants to revive and in that process will properly use apt-helper instead of wget) and to detect gpg vs. gpg2 systems, where the earlier is supposed to go away in the longrun (or the later, but by replacing the earlier…). [and this gpg/gpg2 detection is new in sid, so I have some sympathy for that being a problem now.] Thanks: Jakub Wilk for pointing out #747320
* replace "which" with "command -v" for portabilityDavid Kalnischkies2015-12-062-6/+6
| | | | | | | | which is a debian specific tool packaged in debianutils (essential) while command is a shell builtin defined by POSIX. Closes: 807144 Thanks: Mingye Wang for the suggestion.
* 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>
* release 1.1.31.1.3Michael Vogt2015-11-301-0/+13
| | | | Git-dch: ignore
* 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.
* use function pointers instead of weak symbols for cmdline parsingDavid Kalnischkies2015-11-291-4/+1
| | | | | | | | Passing function pointers around while working on this was very icky, but if weak symbols are too much to ask for… Reverts "do not use "-Wl,-Bsymbolic-functions" during the build to avoid breakage" aka a5fc9be36211a290a7abc3ca2a8bf98943bc1f57.
* Release 1.1.21.1.2Julian Andres Klode2015-11-281-0/+14
|
* do not use "-Wl,-Bsymbolic-functions" during the build to avoid breakageMichael Vogt2015-11-281-1/+4
|
* autopkgtest: use the quiet mode as for travis and coDavid Kalnischkies2015-11-281-1/+1
| | | | Git-Dch: Ignore
* update arch-specific symbols in symbols fileDavid Kalnischkies2015-11-271-11/+17
| | | | Git-Dch: Ignore
* prepare 1.1.1 releaseMichael Vogt2015-11-271-0/+13
|
* use pre-build hook to check for pre-export executionDavid Kalnischkies2015-11-271-2/+3
| | | | Git-Dch: Ignore
* debian/gbp.conf: point debian-branch to masterMichael Vogt2015-11-271-1/+1
| | | | Git-Dch: ignore
* release apt 1.11.1Michael Vogt2015-11-261-2/+5
|
* Do not run pre*export* functions in the pre*build* hookMichael Vogt2015-11-261-1/+2
| | | | | | | Unfortunately it seems like git-buildpackage does not have a pre-export hook so the hook is disabled for now. Git-Dch: ignore
* Prepare release 1.1~exp17Michael Vogt2015-11-251-0/+10
|
* typo: run s#frontend#front-end# on all of src:aptDavid Kalnischkies2015-11-251-4/+4
| | | | | | The manpages were fixed by Justin B Rye, lets deal with the rest now. Git-Dch: Ignore
* releasing package apt version 1.1~exp161.1_exp16Michael Vogt2015-11-241-0/+24
|
* fix a few typos in code-comments/apt manpageDavid Kalnischkies2015-11-201-1/+1
| | | | | Reported-By: codespell Git-Dch: Ignore
* do not rerun ./configure causing FTCBFS with newer autotools-devDavid Kalnischkies2015-11-191-1/+1
| | | | | | | | | | | | | | | | | | If the config.{sub,guess} files we linked in were newer than our configure script we ended up recreating configure and then rerun it without all the configuration options which were (potentially) present for a previous run. We avoid this by changing to the same ruleset as in the debian/rules file which compares the config.* files against a stamp file rather than the configure script itself as its the configuration itself which depends on all scripts, not configure on the config scripts. While at it, we also drop the 'make -s dirs' call as we don't need to do it explicitly here as proper dependencies will take care of it. Thanks: Helmut Grohne for the detailed bugreport. Closes: 804923
* update libapt-{pkg,inst} symbols filesDavid Kalnischkies2015-11-192-32/+88
|
* releasing package apt version 1.1~exp151.1_exp15Michael Vogt2015-11-111-0/+44
|
* 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
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 20:33:06 +0000