Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.0.9.5 2014-12-23T10:43:16Z 2014-12-23T10:43:16Z David Kalnischkies david@kalnischkies.de 2014-11-18T18:53:56Z urn:sha1:a2a75ff4516f7609f4c55b42270abb8d08943c60 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 2014-12-23T10:43:16Z David Kalnischkies david@kalnischkies.de 2014-12-10T21:26:59Z urn:sha1:e18f6133b254db9e1dc7b202366b067b15a68123 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 2014-12-22T13:23:39Z David Kalnischkies david@kalnischkies.de 2014-11-29T16:59:52Z urn:sha1:92e8c1ff287ab829de825e00cdf94744e699ff97 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 2014-11-28T15:15:39Z David Kalnischkies david@kalnischkies.de 2014-11-17T14:06:35Z urn:sha1:9fc0b435593839de47098212f0ae5f15b6263099 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 2014-09-25T13:23:14Z David Kalnischkies david@kalnischkies.de 2014-09-25T09:52:41Z urn:sha1:5f982b9d903b38bb5549479f0111d31e2695090c Git-Dch: Ignore 2014-09-07T17:30:33Z David Kalnischkies david@kalnischkies.de 2014-09-07T17:30:33Z urn:sha1:27cb4f6c919921b04f3dddff069620ced250a94f Instead of trying to inspect /proc and the fds inside we use "test -t 1" instead as this is available and working on kfreebsd as well – not that something breaks if we wouldn't, but we like color. Git-Dch: Ignore 2014-09-07T17:23:28Z David Kalnischkies david@kalnischkies.de 2014-08-30T09:29:45Z urn:sha1:859093dae7dcadaff2e15a3885a1824b0d5f5913 apt-cache search supported this since ever and in the code for apt was a fixme indicating this should be added here as well, so here we go. 2014-07-07T20:41:07Z Michele Orrù maker@tumbolandia.net 2014-07-07T18:48:16Z urn:sha1:3c528b911af131028486d4873d5dcbd0682ed15e The behaviour of echo "\tA\t" differs between dash/zsh which interprets the \t as tab and bash which prints it literally. Similar things happen for other escape sequences – without the -e flag. Switching to printf makes this more painless^Wportable, so that the tests are also working correctly with bash as sh. (commit message by committer, patch otherwise unmodified) 2014-06-11T16:21:07Z Michael Vogt mvo@ubuntu.com 2014-06-11T16:17:45Z urn:sha1:3082603f0ef76876810cb8c6d02d03ba67ec8c6b 2014-06-11T12:50:48Z Michael Vogt mvo@ubuntu.com 2014-06-11T12:50:48Z urn:sha1:686b484b407fdbef47d9f2064284a567b72417fe