Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4.3 2017-01-19T14:59:38Z 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 2016-12-31T01:29:20Z David Kalnischkies david@kalnischkies.de 2016-12-29T11:41:23Z urn:sha1:abbe74b2b4690b9138da94d26a7e45ad80a3bf6c The config list APT::Build-Essential gets a similar treatment to other lists now by having the value of the option itself be an override for the list allowing to disable build-essentials entirely as well as adding/overriding as usual by now in other lists. Reported-By: Johannes 'josch' Schauer on IRC 2016-12-31T01:29:20Z David Kalnischkies david@kalnischkies.de 2016-12-29T11:12:01Z urn:sha1:0c646119dea438abb3ee8797994d016ba6834cd2 The implementation is quite different compared to --arch-only due to ABI reasons but functionality wise they are similar and usually both available for symmetry at least. Closes: #845775 2016-12-16T12:50:00Z David Kalnischkies david@kalnischkies.de 2016-11-25T16:42:47Z urn:sha1:d20643cc0ac89ee30cf0e546d689e67085294ace In bug #757534 the opposite direction was initially requested, but what we did end up with was having a possibility to configure the options passed to dpkg. The reasoning given their and in #724744 is specific why apt doesn't need the checks to be performed by dpkg. In fact, what these two reports show is that if those checks are run people end up being confused about the requirement of them being run, so given the best case those checks can do is do nothing (visibly) while the worst cases are warnings and errors which are neither we are from a security point better of with disabling them – as (as mentioned in the bugreports) false positives for issues are really really bad in a security context. Closes: 724744 2016-12-16T12:50:00Z David Kalnischkies david@kalnischkies.de 2016-11-25T15:23:02Z urn:sha1:fc336f09356c1db63094e377a65033d5ec00b983 We are calling system() in this code paths, so all we do here is having a single child performing the action while the parent waits for it to finish… with the added strangeness of not having our usual error message collection and giving up after first failure even if told to act on multiple packages. 2016-12-16T12:50:00Z David Kalnischkies david@kalnischkies.de 2016-11-25T14:51:21Z urn:sha1:58ebb3017baf46e33a9bb2c1779d6daede27d108 That was the case already for tar-only and diff-only, but in a more confusing way and without a message while dsc "worked" before resulting in a dpkg-source error shortly after as tar/diff files aren't available… 2016-11-09T15:18:54Z Johannes Schauer josch@debian.org 2016-11-09T14:28:15Z urn:sha1:c5f22e483cc0f31f2938874370ac776e40792069 These new enum values might cause "interesting" behaviour in tools not expecting them – like an old apt would think a Build-Conflicts-Arch is some sort of Build-Depends – but that can't reasonably be avoided and effects only packages using B-D/C-A so if there is any breakage the tools can easily be adapted. The APT_PKG_RELEASE number is increased so that libapt users can detect the availability of these new enum fields via: #if APT_PKG_ABI > 500 || (APT_PKG_ABI == 500 && APT_PKG_RELEASE >= 1) Closes: #837395 2016-07-22T14:05:09Z David Kalnischkies david@kalnischkies.de 2016-07-08T13:59:23Z urn:sha1:92296fe4b0862a04ea3d965b4cd2d4a420e3be9f We support installing ./foo.deb (and ./foo.dsc for source) for a while now, but it can be a bit clunky to work with those directly if you e.g. build packages locally in a 'central' build-area. The changes files also include hashsums and can be signed, so this can also be considered an enhancement in terms of security as a user "just" has to verify the signature on the changes file then rather than checking all deb files individually in these manual installation procedures. 2016-06-22T12:05:01Z David Kalnischkies david@kalnischkies.de 2016-06-18T07:59:08Z urn:sha1:60a0cb424e91acebc2bba0f9add220b474e432e6 If apt decides it can't download a file it is relatively pointless to try to tell dpkg-source to unpack it. 2016-05-27T17:14:38Z David Kalnischkies david@kalnischkies.de 2016-05-27T16:10:39Z urn:sha1:b58e2c7c56b1416a343e81f9f80cb1f02c128e25 Setting the C++ locale via std::locale::global(std::locale("")); which would otherwise default to the default C locale (aka: unaffected by setlocale) effects the formatting of numeric types in IO streams, which for output for humans is perfectly sensible, but breaks our many text interfaces used and parsed by us and others without expecting the numbers to be formatted. Closes: #825396