Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.0.9.4 2014-11-28T15:15:39Z 2014-11-28T15:15:39Z James McCoy jamessan@debian.org 2014-11-28T13:21:06Z urn:sha1:69d8b8537af1dd52db5f2e0e785bdce3e52fdf8d 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 2014-11-28T15:15:39Z David Kalnischkies david@kalnischkies.de 2014-11-17T23:59:39Z urn:sha1:299aea924ccef428219ed6f1a026c122678429e6 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 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-11-10T16:23:29Z David Kalnischkies david@kalnischkies.de 2014-10-18T12:44:41Z urn:sha1:8cc3535f2cdcfe1301b641dae8dfadf99658c732 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 2014-11-10T16:23:29Z David Kalnischkies kalnischkies@gmail.com 2013-08-18T21:27:24Z urn:sha1:3a2b39ee602dd5a98b8fdaee2f1c8e0b13a276e2 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 2014-10-15T13:56:53Z David Kalnischkies david@kalnischkies.de 2014-10-15T13:56:53Z urn:sha1:5afcfe2a51a9e47e95023b99bcab065d1975e950 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 2014-10-06T12:43:48Z josch j.schauer@email.de 2014-08-19T08:29:29Z urn:sha1:ac81c0f9b79351258d3a29212f7fda312e5afeb5 2014-09-25T13:23:14Z David Kalnischkies david@kalnischkies.de 2014-09-25T09:52:41Z urn:sha1:5f982b9d903b38bb5549479f0111d31e2695090c Git-Dch: Ignore 2014-09-21T08:18:03Z Michael Vogt mvo@debian.org 2014-09-21T08:18:03Z urn:sha1:b0f4b486e6850c5f98520ccf19da71d0ed748ae4 2014-09-19T22:12:13Z David Kalnischkies david@kalnischkies.de 2014-09-19T22:12:13Z urn:sha1:2bd6be8ad24583ed9935f5c5d57c04ba7344111e Git-Dch: Ignore