summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Upload 1.5~alpha1 to experimental1.5_alpha1Julian Andres Klode2017-06-2860-847/+3385
|
* Strip 0: epochs from the version hashJulian Andres Klode2017-06-282-0/+49
| | | | | | | This should fix some issues with dpkg normalizing such values. Suprisingly enough apt treats the Version: field the same, even with epoch vs without, but not when searching, and does not strip the 0: from the output.
* Merge branch 'feature/releaseinfochange'David Kalnischkies2017-06-2817-58/+416
|\
| * ask for releaseinfo change interactively in aptDavid Kalnischkies2017-06-286-13/+42
| | | | | | | | | | | | | | If we have a user sitting around we can let 'apt' ask the user for a confirmation rather than print errors at the end and require the user to figure out which commandline flags are needed to confirm the changes non-interactively.
| * allow frontends to override releaseinfo change behaviourDavid Kalnischkies2017-06-283-30/+105
| | | | | | | | | | | | | | | | Having messages being printed on the error stack and confirm them by commandline flags is an okayish first step, but some frontends will probably want to have a more interactive feeling here with a proper question the user can just press yes/no for as for some frontends a commandline flag makes no sense…
| * show a Release-Notes URI if infos were changedDavid Kalnischkies2017-06-285-2/+22
| | | | | | | | | | | | | | | | This gives the repository owner a chance to explain why this change was needed – e.g. explaining the organisational changes or simply detailing the changes in the new release made. Note that this URI is also shown if the change is accepted, so it also draws attention to release notes of minor updates (if users watch apt output closely).
| * error in update on Release information changesDavid Kalnischkies2017-06-2811-43/+277
|/ | | | | | | | | | | The value of Origin, Label, Codename and co can be used in user configuration from apts own pinning to unattended upgrades. A repository changing this values can therefore have serious effects on the behaviour of apt and other tools using these values. In a first step we will generate error messages for these changes now explaining the need for explicit confirmation and provide config options and commandline flags to accept them.
* fail instead of warn on insecure repositories in apt-getDavid Kalnischkies2017-06-286-19/+23
| | | | | | | | | The exception was made to give (script) users a one-release grace period to adapt their setup to deal with apt enforcing signing of repositories. As we are now at the start of a new release cycle its as good a time as any to lift it now. Removes-Exception: 952ee63b0af14a534c0aca00c11d1a99be6b22b2
* Merge branch 'feature/http-https'Julian Andres Klode2017-06-2819-272/+601
|\
| * Introduce Acquire::AllowTLS to turn off TLS supportJulian Andres Klode2017-06-283-0/+14
| | | | | | | | | | | | As requested by Henrique de Moraes Holschuh, here comes an option to disable TLS support. If the option is set to false, the internal TLS layer is disabled.
| * Fix test suite and enable non-curl testing on travis, shippableJulian Andres Klode2017-06-283-1/+8
| | | | | | | | Gbp-Dch: ignore
| * Fix https->http redirect issuesDavid Kalnischkies2017-06-282-8/+4
| | | | | | | | Gbp-Dch: ignore
| * methods: http: Drain pending data before selectingJulian Andres Klode2017-06-283-1/+20
| | | | | | | | | | | | | | | | GnuTLS can already have data pending in its buffers, we need to to drain that first otherwise select() might block indefinitely. Gbp-Dch: ignore
| * Allow building without curlJulian Andres Klode2017-06-283-7/+30
| | | | | | | | | | This makes testing easier and prepares us for the transition.
| * methods: Add HTTPS support to http method, using GnuTLSJulian Andres Klode2017-06-287-182/+385
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The http method will eventually replace the curl-based https method, but for now, this is an opt-in experiment that can be enabled by setting Dir::Bin::Methods::https to "http". Known issues: - We do not support HTTPS proxies yet - We do not support proxying HTTPS connections yet (CONNECT) - IssuerCert and SslForceVersion are unsupported Gbp-Dch: Full
| * methods: connect: Switch from int fds to new MethodFdJulian Andres Klode2017-06-286-72/+126
| | | | | | | | | | | | | | | | Use std::unique_ptr<MethodFd> everywhere we used an integer-based file descriptor before. This allows us to implement stuff like TLS support easily. Gbp-Dch: ignore
| * methods: connect: Change PkgAcqMethod to aptMethodJulian Andres Klode2017-06-284-12/+14
| | | | | | | | | | | | | | This will allow us to access ConfigFind() and stuff which makes it possible for us to implement TLS support. Gbp-Dch: ignore
| * Add clang-format definitionsJulian Andres Klode2017-06-282-0/+11
| | | | | | | | | | | | Also add git-clang-format helper to help with }}} Gbp-Dch: ignore
* | Skip test-apt-download-progressJulian Andres Klode2017-06-281-0/+0
|/ | | | | The test keeps failing continously on Ubuntu, so let's fix it for now.
* travis: ignore profiling warning in progress linesDavid Kalnischkies2017-06-271-2/+2
| | | | | | | | | | On Travis CI running tests with code coverage enabled sometimes generates profiling lines, which we filter out for a while now, but that misses lines generated showing progress still causing test failures, so more sed logic is added in the hopes to ignore them. Extends: 58608941e6b58a46109b7cd875716b3d8054c4bf Gbp-Dch: Ignore
* fix some unlikely memory leaks in error casesDavid Kalnischkies2017-06-264-42/+24
| | | | | | | | The error cases are just as unlikely as the memory leaks to ever cause real problems, but lets play it safe for correctness. Reported-By: scan-build & clang Gbp-Dch: Ignore
* deal with 3xx httpcodes as required by HTTP/1.1 specDavid Kalnischkies2017-06-263-14/+15
| | | | | | | | | | | | | | An unknown code should be handled the same as the x00 code of this group, but for redirections we used to treat 300 (and a few others) as an error while unknown codes were considered redirections. Instead we check now explicitly for the redirection codes we support for redirecting (and add the 308 defined in RFC 7538) to avoid future problems if new 3xx codes are added expecting certain behaviours. Potentially strange would have been e.g. "305 Use Proxy" sending a Location for the proxy to use – which wouldn't have worked and resulted in an error anyhow, but probably confused users in the process.
* fail InRelease on non-404 HTTP errorcodesDavid Kalnischkies2017-06-262-1/+14
| | | | | | | | | | | | | | There are very many HTTP errorcodes which indicate that the repository isn't available at the moment or the connection has some kind of problem. Given that we do not require Release files the result was that these errors were ignored and the user presented with a message like "Repository is no longer signed" which sends the user in the wrong direction. Instead of trying to figure out which http errorcodes indicate a global problem we accept only 404 for ignoring and consider all the rest as hard errors now causing us to stop instantly after the InRelease file and print the errorcode (with short description from server) received.
* show .diff/Index properly as ignored if we fallbackDavid Kalnischkies2017-06-263-111/+94
| | | | | | | | | | Moving the code responsible for parsing the Index file from ::Done into the slightly earlier ::VerifyDone allows us to still "fail" the download if we can't make use of the Index for whatever reason, so that the progress log correctly displays "Ign" instead of "Get" for the file. This also makes quiet a few debug messages proper error messages (but those are still hidden by default for Ign lines).
* warn if an expected file can't be acquiredDavid Kalnischkies2017-06-267-5/+83
| | | | | | | | | | | | | | If we couldn't find an entry for a Sources file we would generate an error while for a Packages file we would silently skip it due to assuming it is missing because it is empty. We can do better by checking if the repository declares that it supports a component we want to get the file from and if not say so and hint at the user making a typo. An example were this helps is mozilla.debian.net which dropped the firefox-aurora component (as upstream did) meaning no upgrades until the user notices manually that the repository doesn't provide packages anymore. With this commit warnings are raised hopefully causing the user to investigate what is wrong (sooner).
* avoid changing directory in mirror methodDavid Kalnischkies2017-06-261-17/+13
|
* clean archives without changing directoryDavid Kalnischkies2017-06-264-28/+50
| | | | | Adopting this change in other frontends will require source changes as well similar to our own changes in apt-private/.
* ident a CD without changing directoryDavid Kalnischkies2017-06-261-23/+23
|
* Avoid chdir in acquire clean with unlinkatDavid Kalnischkies2017-06-263-32/+40
| | | | | | | | | | | | POSIX.1-2008 gives us a range of *at calls to deal with files including the unlinkat so we can remove a file from a directory based on a path to the file relative to the directory. (In our case here the path we have is just the filename) We avoid changing directories in this way which e.g. fails if the directory we started in no longer exists or is otherwise inaccessible. Closes: 860738
* make the create-test-data script great againDavid Kalnischkies2017-06-262-19/+32
| | | | | | | | Changes in the past to the buildsystem and the testing framework broke this little helper script – lets fix those problems to restore functionality. Gbp-Dch: Ignore
* Show permission error if ProxyAutoDetect cmd can't be executedDavid Kalnischkies2017-06-263-1/+12
| | | | | | | | | | As the proxy commands are not executed as root, a user can run into permission errors (s)he isn't expecting – as our switching is an implementation detail – so the error message in that case should really be better than a generic "error code 100" sending the user in the wrong direction as that implies the command was executed, but errored out. Closes: 857885
* Refactor to avoid loop/dangling gcc warningsDavid Kalnischkies2017-06-264-9/+11
| | | | Gbp-Dch: Ignore
* Annotate intended switch fall through in httpsDavid Kalnischkies2017-06-261-0/+1
| | | | | Reported-By: gcc-7 Gbp-Dch: Ignore
* Refactor finding compressor by name to avoid code dupDavid Kalnischkies2017-06-261-46/+33
| | | | Git-Dch: Ignore
* Call update from apt-key test for a strange path testDavid Kalnischkies2017-06-262-1/+17
| | | | | | | | | | We setup a "horrible" environment in the apt-key testcase to check all kinds of things, but we really should be making also at least a simple apt update call, as that in turn will call apt-key which is how apt-key is used in the non-testcase world, so that calling should be able to deal with such environments as well. Gbp-Dch: Ignore
* Add a few more Auto-Detect-Proxy testsDavid Kalnischkies2017-06-262-6/+31
| | | | Gbp-Dch: Ignore
* don't show incorrect 'How odd' errror in no-download modeDavid Kalnischkies2017-06-261-22/+27
| | | | | | | | | | | | Showing messages related to downloading in a mode which can't download is pretty pointless, so instead of trying harder to make it so that these messages do not trigger just skip them entirely. That the message triggered here is an artifact of the implementation in which the download items are finished, while the code expects them to be still pending – even the in a previous run completely downloaded files. Closes: 863635
* avoid explicit types for pkg counts by autoDavid Kalnischkies2017-06-267-49/+59
| | | | | | | | | Changes nothing on the program front and as the datatypes are sufficently comparable fixes no bug either, but problems later on if we ever change the types of those and prevent us using types which are too large for the values we want to store waste (a tiny bit of) resources. Gbp-Dch: Ignore
* schedule the correct side of the conflict for removalDavid Kalnischkies2017-06-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | In complex situations in which we want to unpack a package which has a conflict/breaks on another package which must be removed due this conflict apt can decide to perform this remove earlier than initially planned. Problem: For three years apt wouldn't remove that package, but the package which has the conflict… The situation isn't very common and easily hidden as the package which is removed is unpacked a few actions later – it becomes visible for packages which protect themselves from removal through like systemd as the running init resulting in upgrade failures (#854041). Note that the package isn't purged, so data shouldn't be lost even if a user runs into a "hidden" case of it as long as the package sticks to the policy of removing data only on purge. Reaching this situation artificially is hard, which is why no testcase is included, as the situation is highly state dependent. Testing with "real" systems indicate that slight modifications in the installed packages set can make the bug not trigger. Regression-Of: 0eb4af9d3d0c524c7afdc684238aa263ac287449 Thanks: Michael Biebl for helping find this with countless tests
* tests: fix gpg-agent killing in testcasesDavid Kalnischkies2017-06-261-1/+1
| | | | | | | We want to kill the agent if its home directory exists at that location, not if it isn't there (leaving an army of processes around). Gbp-Dch: Ignore
* Merge triehash v0.2Julian Andres Klode2017-06-261-49/+80
|\
| * Squashed 'triehash/' changes from 565fde4e7..0ca66b761Julian Andres Klode2017-06-261-49/+80
| | | | | | | | | | | | | | | | | | | | 0ca66b761 Redefine ambiguous to be much more simple 3d9adfb3f Add more comments 2896e78c2 Render C code to match longest prefix 21e620cf0 fix various typos reported by spellintian git-subtree-dir: triehash git-subtree-split: 0ca66b761aa56d42d35c4cc254f455424764895a
* | pkgcache: Bump major version to 12Julian Andres Klode2017-06-261-1/+1
| | | | | | | | | | | | We need to be able to update 1.4.y in different ways than later apt versions, and thus need to bump the major version so there is no collision in the minor version at some point.
* | Release 1.4.61.4.6Julian Andres Klode2017-06-0114-15/+24
| |
* | apt.systemd.daily: Use unattend-ugrade --download-only if availableJulian Andres Klode2017-06-011-2/+2
| | | | | | | | | | | | | | | | | | | | | | Using dry-run as in the previous commit is not really correct, as it logs dpkg debugging output too. So, let's assume unattended-upgrade gets a --download-only option and use that if it is available. This lets us add the downloading part to unattended-upgrades later on, without requiring versioned dependencies between the two. Closes: #863859
* | apt.systemd.daily: Pass --dry-run to unattended-upgrade, not -dJulian Andres Klode2017-06-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | We want to download stuff: --dry-run Simulation, download but do not install not debug: -d, --debug print debug messages Confusion everywhere! Closes: #863859
* | Release 1.4.51.4.5Julian Andres Klode2017-05-3114-15/+21
| |
* | Fix parsing of or groups in build-deps with ignored packagesJulian Andres Klode2017-05-312-1/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the last alternative(s) of an Or group is ignored, because it does not match an architecture list, we would end up keeping the or flag, effectively making the next AND an OR. For example, when parsing (on amd64): debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386] => debhelper (>= 9), libnacl-dev | Which can cause python-apt to crash. Even worse: debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386], foobar => debhelper (>= 9), libnacl-dev [amd64] | foobar By setting the previous alternatives Or flag to the current Or flag if the current alternative is ignored, we solve the issue. LP: #1694697
* | Release 1.4.41.4.4Julian Andres Klode2017-05-1614-15/+22
| |
* | apt.systemd.daily: Drop the LOCKFD variableJulian Andres Klode2017-05-161-6/+3
| | | | | | | | Gbp-Dch: ignore
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 15:38:36 +0000