Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3_rc1 2016-08-10T23:36:23Z 2016-08-10T23:36:23Z David Kalnischkies david@kalnischkies.de 2016-08-10T23:36:23Z urn:sha1:0a7370ca91289db3d23d72aeac397edfe3dfb75b 2016-08-10T23:36:18Z David Kalnischkies david@kalnischkies.de 2016-08-10T23:36:18Z urn:sha1:6b3ddbd059c403efeb40d81c29f2cae6e8f5b1bf 2016-08-10T21:51:35Z David Kalnischkies david@kalnischkies.de 2016-07-28T07:13:24Z urn:sha1:28557f94578602f9ce0011501a2259bd98ab0688 With b4450f1dd6bca537e60406b2383ab154a3e1485f we dropped what we calculated here later on and now that we don't need it in the meantime either we can just skip the busy work by default and expect dpkg to do the right thing dropping also our little "last explicit configures" removal trick introduced in b4450f1dd6bca537e60406b2383ab154a3e1485f. This enables the last of a bunch of previously experimental options, some of them existing still, but are very special and hence not really worth documenting anymore (especially as it would need to be rewritten now entirely) which is why the documentation is nearly completely dropped. The order of configuration stanzas in the simulation code changes slightly as it isn't concerning itself with finding the 'right' order, but any order is valid anyhow as long as the entire set happens in the same call. 2016-08-10T21:51:34Z David Kalnischkies david@kalnischkies.de 2016-07-28T09:43:36Z urn:sha1:4326680d2ed23d597f45ca8872a7054368560acc If a planner lets actions to be figured out by dpkg in pending calls these actions aren't mentioned in a simulation. While that might be a good thing for debugging, it would be a change in behavior and especially if a planner avoids explicit removals could be confusing for users. As such we perform the same 'trick' as in the dpkg implementation by performing explicitly what would be done by the pending calls. To save us some work and avoid desyncs we perform a layer violation by using deb/ code in the generic simulation – and further we perform ugly dynamic_cast to avoid breaking the ABI for nothing; aptitude is the only other user of the simulation class according to codesearch.d.n and for that our little trick works. It just isn't working if you happen to extend pkgSimulate or otherwise manage to call the protected Go methods directly – which isn't very realistic/practical. 2016-08-10T21:51:34Z David Kalnischkies david@kalnischkies.de 2016-07-25T14:36:53Z urn:sha1:83e5cffc2015aa809acac84737756d292d7bf106 The user has to approve the removal of a crossgraded package as it might be needed to remove it (temporarily) in the process, but in most cases we can happily avoid it and let dpkg unpack over it skipping the remove. This has some effects on progress reporting and how deal with selections through which makes this a tiny bit complicated. 2016-08-10T21:20:15Z David Kalnischkies david@kalnischkies.de 2016-08-01T19:45:29Z urn:sha1:a1f3ac8aba0675321dd46d074af8abcbb10c19fd If the URI had no password the username was ignored 2016-08-10T21:19:44Z David Kalnischkies david@kalnischkies.de 2016-08-06T17:59:57Z urn:sha1:c9c910695185b59aa27b787c1a250497e47b492b To prevent accidents like adding http-sources while using tor+http it can make sense to allow disabling methods. It might even make sense to allow "redirections" and adding "symlinked" methods via configuration. This could e.g. allow using different options for certain sources by adding and configuring a "virtual" new method which picks up the config based on the name it was called with like e.g. http does if called as tor+http. 2016-08-10T21:19:44Z David Kalnischkies david@kalnischkies.de 2016-08-04T06:45:38Z urn:sha1:61db48241f2d46697a291bfedaf398a1ca9a70e3 Socks support is a requested feature in sofar that the internet is actually believing Acquire::socks::Proxy would exist. It doesn't and this commit isn't adding it as that isn't how our configuration works, but it allows Acquire::http::Proxy="socks5h://…". The HTTPS method was changed already to support socks proxies (all versions) via curl. This commit implements only SOCKS5 (RFC1928) with no auth or pass&user auth (RFC1929), but not GSSAPI which is required by the RFC. The 'h' in the protocol name further indicates that DNS resolution is delegated to the socks proxy rather than performed locally. The implementation works and was tested with Tor as socks proxy for which implementing socks5h only can actually be considered a feature. Closes: 744934 2016-08-10T21:19:44Z David Kalnischkies david@kalnischkies.de 2016-08-02T20:44:50Z urn:sha1:57401c48fadc0c78733a67294f9cc20a57e527c9 Having the detection handled in specific (http) workers means that a redirection loop over different hostnames isn't detected. Its also not a good idea have this implement in each method independently even if it would work 2016-08-10T21:19:44Z David Kalnischkies david@kalnischkies.de 2016-08-01T15:52:55Z urn:sha1:d0ef571416e1ff6266c89e6285898d269768cf8f apt-transports not shipped in apt directly are usually named apt-transport-% with % being what is in the name of the transport. tor additional introduced aliases via %+something, which isn't a bad idea, so be strip the +something part from the method name before suggesting the installation of an apt-transport-% package. This avoids us the maintainance of a list of existing transports creating a two class system of known and unknown transports which would be quite arbitrary and is unfriendly to backports.