summaryrefslogtreecommitdiff
path: root/debian
AgeCommit message (Collapse)Author
2013-08-19prepare for releaseMichael Vogt
2013-08-17update changelogMichael Vogt
2013-08-17Merge remote-tracking branch 'mvo/feature/apt-binary2' into debian/sidMichael Vogt
Conflicts: cmdline/apt-get.cc
2013-08-17Merge branch 'debian/sid' of git://git.debian.org/git/apt/apt into debian/sidChristian PERRIER
2013-08-17French translation update.Christian PERRIER
2013-08-15* lp:~mvo/apt/add-glob-function:Michael Vogt
- add Glob() to fileutl.{cc,h} Conflicts: apt-pkg/contrib/fileutl.h debian/changelog
2013-08-15* lp:~mvo/apt/config-clear:Michael Vogt
- support Configuration.Clear() for a clear of the entire configuration Conflicts: debian/changelog
2013-08-15merge patch from Daniel Hartwig to Show a error message if {,dist-}upgrade ↵Michael Vogt
is used with additional arguments (closes: #705510)
2013-08-15merge patch from Daniel Hartwig to Clarify units of Acquire::http::Dl-Limit ↵Michael Vogt
(closes: #705445) Conflicts: debian/changelog
2013-08-12really build apt.installMichael Vogt
2013-08-12install libapt-private* into the apt binaryMichael Vogt
2013-08-12update changelog for upload0.9.10Michael Vogt
2013-08-12do not call 'apt-key update' in apt.postinstDavid Kalnischkies
The debian-archive-keyring package ships trusted.gpg.d fragment files for a while now and dropped their call to 'apt-key update', so there is no need for use to call it as the keys will always be available. This also finally allows a user to remove key(ring)s without APT to overriding this decision by readding them with this step. The functionality is kept around in the odd case that an old debian-archive-keyring package is used which still calls 'apt-key update' and depends on the import (hence, we also do not enforce a newer version of the debian-archive-keyring via our dependencies)
2013-08-12use a tmpfile for trustdb.gpg in apt-keyDavid Kalnischkies
for some "interesting" reason gpg decides that it needs to update its trustdb.gpg file in a --list-keys command even if right before gpg is asked to --check-trustdb. That wouldn't be as bad if it wouldn't modify the keyring being listed at that moment as well, which generates not only warnings which are not a problem for us, but as the keyring modified can be in /usr it modified files which aren't allowed to be modified. The suggested solution in the bugreport is running --check-trustdb unconditionally in an 'apt-key update' call, but this command will not be used in the future and this could still potentially bite us in net-update or adv calls. All of this just to keep a file around, which we do not need… The commit therefore switches to the use of a temporary created trusted.gpg file for everyone and asks gpg to not try to update the trustdb after its intial creation, which seems to avoid the problem altogether. It is using your also faked secring btw as calling the check-trustdb without a keyring is a lot slower … Closes: #687611 Thanks: Andreas Beckmann for the initial patch!
2013-08-10Japanese translation update. Closes: #719279Christian PERRIER
2013-08-03Vietnamese translation update. Closes: #718615Christian PERRIER
2013-07-27update the symbol files to reflect current stateDavid Kalnischkies
2013-07-26exclude config.{sub,guess} from source packageDavid Kalnischkies
Lintian complains about these links in the source package as they leave the source directory and as they are autogenerated there isn't that much sense in shipping them, we can just recreate them before calling configure.
2013-07-26implement debian/rules build-{arch,indep} as required by policy 3.9.4David Kalnischkies
2013-07-26correct management-typo in description found by lintianDavid Kalnischkies
2013-07-26make autoconf happy by "mv configure.{in,ac}"David Kalnischkies
Git-Dch: Ignore
2013-07-26update changelog for upload0.9.9.4Michael Vogt
2013-07-25skip all Description fields in apt-cache, not just first (Closes: 717254)0.9.9.3Michael Vogt
* skip all Description fields in apt-cache, not just first (Closes: 717254) * fix 'apt-cache search' crash with missing description (Closes: 647590)
2013-07-23debian/apt.postinst:Michael Vogt
* debian/apt.postinst: - run /etc/kernel/postinst.d/apt-auto-removal once on upgrade to ensure that the correct auto-removal list is generated (closes: #717615)
2013-07-23debian/apt.auto-removal.sh:Michael Vogt
* debian/apt.auto-removal.sh: - do not include debug symbol packages for the kernel in the blacklist (closes: #717616)
2013-07-17fix if-clause to generate hook-info for 'rc' packages (Closes: 717006)0.9.9.2Michael Vogt
2013-07-16Vietnamese updated by Tran Ngoc Quan. Closes: #717016Christian PERRIER
2013-07-11update changelog0.9.9.1Michael Vogt
2013-07-11debian/apt.auto-removal.sh: merge the remaining bitsMichael Vogt
2013-07-11* Fix up two things in debian/apt.auto-removal.sh:Adam Conrad
- Use exact matches with $-terminated regexes, so we don't get confusion between similarly-named kernel flavours. - Keep linux-backports-modules in sync with installed kernels. Conflicts: configure.in debian/changelog doc/apt-verbatim.ent
2013-07-11get dpkg from apt-config as well and add robustness against missing/failing ↵Michael Vogt
apt-config (for paranoia) Conflicts: debian/apt.auto-removal.sh
2013-07-11Make sure we always have at least two kernels marked not for removalSteve Langasek
2013-07-11cherry pick 39a07ec8f2c612a5af234c7713571362f7ca90b4Steve Langasek
2013-07-10apt-pkg/packagemanager.cc:Michael Vogt
* apt-pkg/packagemanager.cc: - increate APT::pkgPackageManager::MaxLoopCount to 5000
2013-07-05debian/rules:Michael Vogt
* debian/rules: - call dh_clean in clean (closes: #714980)
2013-07-02releasing version 0.9.90.9.9Michael Vogt
2013-07-02update changelogMichael Vogt
2013-07-02Merge remote-tracking branch 'donkult/debian/sid' into debian/sidMichael Vogt
Conflicts: debian/changelog
2013-07-02update changelogMichael Vogt
2013-06-20trigger NODATA error for invalid InRelease filesDavid Kalnischkies
With the selfgrown splitting we got the problem of not recovering from networks which just reply with invalid data like those sending us login pages to authenticate with the network (e.g. hotels) back. The good thing about the InRelease file is that we know that it must be clearsigned (a Release file might or might not have a detached sig) so if we get a file but are unable to split it something is seriously wrong, so there is not much point in trying further. The Acquire system already looks out for a NODATA error from gpgv, so this adds a new error message sent to the acquire system in case the splitting we do now ourselves failed including this magic word. Closes: #712486
2013-06-20do not redownload unchanged InRelease filesDavid Kalnischkies
Before we download the 'new' InRelease file the old file will be moved out of the way with the name 'foobar_InRelease.reverify', so if no partial file for the 'new' file exists take the modification time from this reverify file, so that if we get an IMS hit for the InRelease file we can move back the reverify file as new file rather than downloading the 'new' file even though we already have it. We do the same for Release files and this happened to work until the reverify renaming was corrected for InRelease files.
2013-06-20support \n and \r\n line endings in ReadMessagesDavid Kalnischkies
2013-06-20try defaults if auto-detection failed in apt-cdromDavid Kalnischkies
The default is to ask udev for location and mountpoints of CD-ROMs, but the old way of specifying the mountpoint is still available and is tried now in case udev doesn't find any CD-ROM. It probably fails, too, but we get a bunch of error messages this way and the user can get an idea of how to make his setup work even if udev can't be convienced to return something useful. Closes: #712433
2013-06-20handle missing "Description" in apt-cache showDavid Kalnischkies
do not blindly assume that all packages stanzas have a "Description:" field in 'apt-cache show' as well as in the cache creation itself. We instead assume now that if the stanza has a Description, it will not be the first field as we look out for "\nDescription" to take care of MD5sum as well as (maybe ignored) translated Descriptions embedded in the package stanza. Closes: #712435
2013-06-13fix file location for configure-index.gz in apt.conf(5)David Kalnischkies
Closes: #711921
2013-06-09ensure state-dir exists before coyping cdrom filesDavid Kalnischkies
We do the same in the acquire system which handles the 'normal' downloads, so do it here as well even though its unlikely anyone will ever notice (beside testcases of course …)
2013-06-09fail in CopyFile if the FileFds have error flag setDavid Kalnischkies
Testing for global PendingErrors in users of CopyFile is incorrect in so far as unrelated errors will prevent us from copying perfectly fine files and checking for the validity of the files is just better in CopyFiles as it already checks if files are at least opened. Add also a higher-level error message to the error stack if it fails.
2013-06-09OpenDescriptor should autoclose fd always on errorDavid Kalnischkies
OpenInternDescriptor failures would cause additional errors to be generated by double-closing an fd. Other errors (although these are generated if the method is used incorrectly, so unlikely) didn't close the fd aswell. Closes: 704608
2013-06-09don't explicitly init ExtractTar InFd with invalid fdDavid Kalnischkies
The default constructor of the FileFd will kick in anyway, which will know that the Fd is invalid while with this explicit call it must be assumed that the fd is in fact valid, which might generate errors in the future
2013-06-09set Fail flag in FileFd on all errors consistentlyDavid Kalnischkies
Previously some errors would set the Fail flag while some didn't without a clear reason as all errors leave a bad FileFd behind, so we use a helper now to ensure that all errors set the flag.