summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* release 1.0.9.51.0.9.5David Kalnischkies2014-12-2349-2516/+2307
|
* 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
* pass-through stdin fd instead of content if not a terminalDavid Kalnischkies2014-12-232-6/+32
| | | | | | | | | | | | | | | | | | Commit 299aea924ccef428219ed6f1a026c122678429e6 fixes the problem of not logging terminal in case stdin & stdout are not a terminal. The problem is that we are then trying to pass-through stdin content by reading from the apt-process stdin and writing it to the stdin of the child (dpkg), which works great for users who can control themselves, but pipes and co are a bit less forgiving causing us to pass everything to the first child process, which if the sending part of the pipe is e.g. 'yes' we will never see the end of it (as the pipe is full at some point and further writing blocks). There is a simple solution for that of course: If stdin isn't a terminal, we us the apt-process stdin as stdin for the child directly (We don't do this if it is a terminal to be able to save the typed input in the log). Closes: 773061
* always run 'dpkg --configure -a' at the end of our dpkg callingsDavid Kalnischkies2014-12-237-56/+146
| | | | | | | | | | | | | | | | | | | | | | | | | | dpkg checks now for dependencies before running triggers, so that packages can now end up in trigger states (especially those we are not touching at all with our calls) after apt is done running. The solution to this is trivial: Just tell dpkg to configure everything after we have (supposely) configured everything already. In the worst case this means dpkg will have to run a bunch of triggers, usually it will just do nothing though. The code to make this happen was already available, so we just flip a config option here to cause it to be run. This way we can keep pretending that triggers are an implementation detail of dpkg. --triggers-only would supposely work as well, but --configure is more robust in regards to future changes to dpkg and something we will hopefully make use of in future versions anyway (as it was planed at the time this and related options were implemented). Note that dpkg currently has a workaround implemented to allow upgrades to jessie to be clean, so that the test works before and after. Also note that test (compared to the one in the bug) drops the await test as its is considered a loop by dpkg now. Closes: 769609
* do not make PTY slave the controlling terminalDavid Kalnischkies2014-12-233-45/+70
| | | | | | | | | | | | | | | | | | | If we have no controlling terminal opening a terminal will make this terminal our controller, which is a serious problem if this happens to be the pseudo terminal we created to run dpkg in as we will close this terminal at the end hanging ourself up in the process… The offending open is the one we do to have at least one slave fd open all the time, but for good measure, we apply the flag also to the slave fd opening in the child process as we set the controlling terminal explicitely here. This is a regression from 150bdc9ca5d656f9fba94d37c5f4f183b02bd746 with the slight twist that this usecase was silently broken before in that it wasn't logging the output in term.log (as a pseudo terminal wasn't created). Closes: 772641
* dispose http(s) 416 error page as non-contentDavid Kalnischkies2014-12-229-112/+241
| | | | | | | | | | | | | | | | | | | | | | | Real webservers (like apache) actually send an error page with a 416 response, but our client didn't expect it leaving the page on the socket to be parsed as response for the next request (http) or as file content (https), which isn't what we want at all… Symptom is a "Bad header line" as html usually doesn't parse that well to an http-header. This manifests itself e.g. if we have a complete file (or larger) in partial/ which isn't discarded by If-Range as the server doesn't support it (or it is just newer, think: mirror rotation). It is a sort-of regression of 78c72d0ce22e00b194251445aae306df357d5c1a, which removed the filesize - 1 trick, but this had its own problems… To properly test this our webserver gains the ability to reply with transfer-encoding: chunked as most real webservers will use it to send the dynamically generated error pages. (The tests and their binary helpers had to be slightly modified to apply, but the patch to fix the issue itself is unchanged.) Closes: 768797
* Thai program translation updateTheppitak Karoonboonyanan2014-12-221-9/+9
| | | | Closes: 772913
* Japanese program translation updateKenshi Muto2014-12-221-4/+4
| | | | Closes: 772678
* Chinese (simplified) program translation updateZhou Mo2014-12-221-19/+20
| | | | Closes: 771982
* French manpages translation updateJean-Pierre Giraud2014-12-221-204/+373
| | | | Closes: 771967
* release 1.0.9.41.0.9.4David Kalnischkies2014-12-0348-60769/+60881
|
* Spanish program translation updateManuel "Venturi" Porras Peralta2014-12-031-1451/+1517
| | | | Closes: 771815
* support long keyids in "apt-key del" instead of ignoring themJames McCoy2014-11-282-1/+7
| | | | | | | | | | | apt-key given a long keyid reports just "OK" all the time, but doesn't delete the mentioned key as it doesn't find the key. Note: In debian/experimental this was closed with 29f1b977100aeb6d6ebd38923eeb7a623e264ffe which just added the testcase as the rewrite of apt-key had fixed this as well. Closes: 754436
* fix PTY interaction on linux and kfreebsdDavid Kalnischkies2014-11-282-47/+92
| | | | | | | | | | | | | | | | | | | | | | | | | We run dpkg on its own pty, so we can log its output and have our own output around it (like the progress bar), while also allowing debconf and configfile prompts to happen. In commit 223ae57d468fdcac451209a095047a07a5698212 we changed to constantly reopening the slave for kfreebsd. This has the sideeffect though that in some cases slave and master will lose their connection on linux, so that no output is passed along anymore. We fix this by having always an fd referencing the slave open (linux), but we don't use it (kfreebsd). Failing to get our PTY up and running has many (bad) consequences including (not limited to, nor all at ones or in any case) garbled ouput, no output, no logging, a (partial) mixture of the previous items, … This commit is therefore also reshuffling quiet a bit of the creation code to get especially the output part up and running on linux and the logging for kfreebsd. Note that the testcase tries to cover some cases, but this is an interactivity issue so only interactive usage can really be a good test. Closes: 765687
* close leaking slave fd after setting up pty magicDavid Kalnischkies2014-11-284-61/+109
| | | | | | | The fd moves out of scope here anyway, so we should close it properly instead of leaking it which will tickle down to dpkg maintainer scripts. Closes: 767774
* Japanese program translation updateKenshi Muto2014-11-281-26/+24
| | | | Closes: 763033
* Turkish program translation updateMert Dirik2014-11-281-91/+88
| | | | Closes: 763379
* Czech program translation updateMiroslav Kure2014-11-281-10/+10
| | | | Closes: 764055
* Chinese (simplified) program translation updateZhou Mo2014-11-281-147/+203
| | | | Closes: 766170
* French program translation updateJulien Patriarca2014-11-281-1791/+1547
| | | | Closes: 766755
* Dutch program translation updateFrans Spiesschaert2014-11-281-418/+498
| | | | Closes: 771039
* change codenames to jessie as stable POV in docsDavid Kalnischkies2014-11-101-4/+4
|
* reenable support for -s (and co) in apt-get sourceDavid Kalnischkies2014-11-102-1/+5
| | | | | | | | The conversion to accept only relevant options for commands has forgotten another one, so adding it again even through the usecase might very well be equally good served by --print-uris. Closes: 742578
* allow options between command and -- on commandlineDavid Kalnischkies2014-11-103-10/+81
| | | | | | | This used to work before we implemented a stricter commandline parser and e.g. the dd-schroot-cmd command constructs commandlines like this. Reported-By: Helmut Grohne
* deprecate the Section member from package structDavid Kalnischkies2014-11-104-4/+18
| | | | | | | | | | | | | | | A version belongs to a section and has hence a section member of its own. A package on the other hand can have multiple versions from different sections. This was "solved" by using the section which was parsed first as order of sources.list defines, but that is obviously a horribly unpredictable thing. Users are way better of with the Section() as returned by the version they are dealing with. It is likely the same for all versions of a package, but in the few cases it isn't, it is important (like packages moving from main/* to contrib/* or into oldlibs …). Backport of 7a66977 which actually instantly removes the member.
* use 'best' hash for source authenticationDavid Kalnischkies2014-11-107-60/+445
| | | | | | | | | | | | | | | | 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-104-27/+247
| | | | | | | | | | | | | 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
* Fix incorrect comparison between signed/unsignedMichael Vogt2014-10-231-1/+1
| | | | Git-Dch: ignore
* Use sysconf(_SC_ARG_MAX) to find the size of Dpkg::MaxArgBytesMichael Vogt2014-10-231-2/+21
| | | | | Instead of hardcoding Dpkg::MaxArgBytes find out about it using the sysconf(_SC_ARG_MAX) call.
* doc/examples/configure-index: make "Dpkg::Max{Arg,ArgBytes} match realityMichael Vogt2014-10-221-2/+2
| | | | Git-Dch: ignore
* releasing package apt version 1.0.9.3Michael Vogt2014-10-151-0/+16
|
* don't cleanup cdrom files in apt-get updateDavid Kalnischkies2014-10-152-14/+50
| | | | | | | | | | Regression from merging 801745284905e7962aa77a9f37a6b4e7fcdc19d0 and b0f4b486e6850c5f98520ccf19da71d0ed748ae4. While fine by itself, merged the part fixing the filename is skipped if a cdrom source is encountered, so that our list-cleanup removes what seems to be orphaned files. Closes: 765458
* Update Status field values handlingGuillem Jover2014-10-082-35/+11
| | | | | | | | | | | | | Remove long obsolete (hold, hold-reinstreq, removal-failed) or just wrong (post-inst-failed vs postinst-failed) values, that have been autoconverted by dpkg at run-time to their new equivalents, so there should not be any such instance in any recent system (removal-failed since dpkg 1.1.4 in Apr 1996, hold and hold-reinstreq since dpkg 1.2.0 in May 1996). dpkg even stopped doing the mapping in 1.15.4 and 1.15.8 respectively. At the same time sort the list in the same order as they appear in the dpkg code.
* methods/rsh.cc: replace strcat with std::stringMichael Vogt2014-10-081-5/+8
| | | | | | | Instead of using strcat use a C++ std::string to avoid overflowing this buffer. Thanks to David Garfield Closes: #76442
* add CVE-2014-7206 to 1.0.9.2Michael Vogt2014-10-081-1/+1
|
* implement the updated build profile specjosch2014-10-063-97/+130
|
* releasing package apt version 1.0.9.2Michael Vogt2014-10-021-0/+28
|
* apt-get: Create the temporary downloaded changelog inside tmpdirGuillem Jover2014-10-021-1/+1
| | | | | | | | The code is creating a secure temporary directory, but then creates the changelog alongside the tmpdir in the same base directory. This defeats the secure tmpdir creation, making the filename predictable. Inject a '/' between the tmpdir and the changelog filename.
* 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
* Set STRIP_FROM_PATH for doxygenTrần Ngọc Quân2014-09-281-2/+2
| | | | Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
* Merge remote-tracking branch 'donkult/feature/generalize-gzipindex' into ↵Michael Vogt2014-09-268-171/+216
|\ | | | | | | debian/sid
| * rewrite compressed indexes test to check with all compressorsDavid Kalnischkies2014-09-253-122/+135
| | | | | | | | Git-Dch: Ignore
| * generalize Acquire::GzipIndexMichael Vogt2014-09-217-58/+90
| |
* | Ensure that iTFRewritePackageOrder is "MD5sum" to match apt-ftparchiveMichael Vogt2014-09-211-1/+1
| | | | | | | | | | | | | | The iTFRewritePackageOrder is used in indexcopy to copy and normalize cdrom Packages files. This change will ensure that there is no "normalization" that changes MD5sum -> MD5Sum which alters the hash of the Packages file on disk (oh the irony).
* | Fix regression for cdrom: sources from latest security updateMichael Vogt2014-09-211-0/+6
|/ | | | | | | | | | Skip a reverify for cdrom: sources. The reverify step is actually harmful here because the apt-cdrom add code uses the indexcopy.cc which will "normalize" the Packages file from the cdrom when it writes it to the local disk. This leads to changing the "MD5sum" field (notice the lower case "s") on the cdrom Packages file to a "MD5Sum" field on the local file in /var/lib/apt/lists. Which of course alters the hash and makes apt fail to reverify the file.
* relax grep to support newer curl output formatDavid Kalnischkies2014-09-201-1/+6
| | | | Git-Dch: Ignore
* disable timestamps in the footer of docs by doxygenJérémy Bobbio2014-09-191-1/+1
| | | | | The default being 'yes', but this spoils the effort of reproducible builds for no real gain. (https://wiki.debian.org/ReproducibleBuilds)
* German program translation updateHolger Wansing2014-09-191-10/+13
| | | | Closes: 762223
* Fix regression when copy: is used for a relative pathMichael Vogt2014-09-192-6/+8
| | | | | | | | | When we do a ReverifyAfterIMS() we use the copy: method to verify the hashes again. If the user uses -o Dir=./something/relative this fails because we use the URI class in copy.cc that strips away the leading relative part. By not using URI this is fixed. Closes: #762160
* test/integration/test-apt-update-file: improve testMichael Vogt2014-09-192-0/+17
|
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 17:38:11 +0000