Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4_rc2 2017-02-10T22:12:52Z 2017-02-10T22:12:52Z Julian Andres Klode jak@debian.org 2017-02-10T21:39:00Z urn:sha1:85ee4036c68d8ecd2c973d413a17aca81380900b In the case of build-dep and other commands where a file can be passed we must make sure not to normalize the path name as that can have odd side effects, or well, cause the operation to do nothing. Test for build-dep-file is adjusted to perform the vcard check once as "vcard" and once as "VCard", thus testing that this solves the reported bug. We inline the std::transform() and optimize it a bit to not write anything in the common case (package names are defined to be lowercase, the whole transformation is just for names that should not exist...) to counter the performance hit of the added find() call (it's about 0.15% more instructions than with the existing transform, but we save about 0.67% in writes...). Closes: #854794 2017-02-09T11:59:05Z David Kalnischkies david@kalnischkies.de 2017-02-09T11:50:14Z urn:sha1:89a2e40d14c29c66aead51df0d56c5c49776009a $ uname -m i686 $ date -d '0-12-25' date: invalid date '0-12-25' Test-Regression-In: 25a14d4ccfceb2698edce01092bc6a1dbe9fb217 2017-01-24T18:19:48Z Julian Andres Klode jak@debian.org 2017-01-24T18:11:30Z urn:sha1:bcb1919a88ea746460e623dd591f7a00135eadda This hides errors in the test suite because it will exit with 0 here. Instead, just do exit 1 in most traps, and do just the cleanup in the QUIT hook. This fixes a regression introduced with the caching of the GPG home directory in 4ce2f35248123ff2366c8c365ad6a94945578d66. 2017-01-19T14:59:38Z David Kalnischkies david@kalnischkies.de 2017-01-19T14:14:19Z urn:sha1:93cff633a830e222693fc0f3d78e6e534d1126ee Most of them in (old) code comments. The two instances of user visible string changes the po files of the manpages are fixed up as well. Gbp-Dch: Ignore Reported-By: spellintian 2017-01-19T10:50:41Z David Kalnischkies david@kalnischkies.de 2017-01-19T10:50:41Z urn:sha1:25a14d4ccfceb2698edce01092bc6a1dbe9fb217 Normal cows moo every time they feel like it and it might be a "moo", "moo!" or "moo?". This is completely unacceptable behaviour in our super cow through as as a superior being it has to show its superiority over the common cows and the meager easter eggs by being fully reproducible! The second version of Chris' patch is modified to include an array of tests for this feature – which doubles as explanation for some of the moo lines by giving more exact dates – and falling back to current time if the environment is invalid + passing time around instead of having an invalid environment be an unrecoverable error (aka: Guru Meditation) as that is more inline with how apt usually behaves: The wisdom of super cow should be available to everyone, even to the most misfortune users not capable of having a valid environment variable. That makes the code slightly more ugly, so instead of requiring a young follower to produce a third version a high priest of the cult applied the finishing touches as he is used to the pain by now – and another round with the slowpoke high priest would have been a serious threat to the Debian release schedule which the cow would not approve. Closes: #848721 Signed-off-by: Super Cow Thanks: Chris Lamb for initial patch and guru meditation 2017-01-19T02:57:45Z David Kalnischkies david@kalnischkies.de 2017-01-19T02:57:45Z urn:sha1:7ca83492e802967f183babf06ab541b1b51f1703 If apt renames a file to .FAILED it leaves its namespace and is never touched again – expect since 1.1~exp4 in which "apt clean" will remove those files. The usefulness of these files rapidly degrades if you don't keep the update log itself (together with debug output in the best case) through and on 99% of all system they will be kept around forever just to collect dust over time and eat up space. With this commit an update call will remove all FAILED files of previous runs, so that the FAILED files you have on disk are always only the ones related to the last apt run stopping apt from hoarding files. Closes: 846476 2017-01-19T02:06:00Z David Kalnischkies david@kalnischkies.de 2017-01-19T01:53:35Z urn:sha1:3313eaf97c83177433478505c05815ab02f9782b The mode wasn't working at all if not used together with --fix-missing which while likely to come in pairs its legal to use standalone. Regression-in: eb1f04dda07c2b69549ad9fd793cca0e91841b3e 2017-01-18T23:57:38Z David Kalnischkies david@kalnischkies.de 2017-01-18T10:31:13Z urn:sha1:33f982b90a4f77be18cb82daf8c79e9c5513761c Unlikely that anyone is actually running into this, but if we asked to not generate a cache and avoid it in the first step we shouldn't create one implicitly anyway by displaying the statistics. 2017-01-17T15:35:54Z Julian Andres Klode jak@debian.org 2017-01-17T15:31:30Z urn:sha1:803dabde5a4345ce83b3d2ffbd475786db9769d9 This prevents CI failures from happening in 1.3 and 1.2 and might actually be more complete. Gbp-Dch: ignore 2017-01-17T13:33:02Z Julian Andres Klode jak@debian.org 2017-01-17T13:33:02Z urn:sha1:b59a8c6e29015c4d19c4b39a63b328af7d87d1ee This will avoid people from thinking that they have to do nothing when they change the set of files. Gbp-Dch: ignore