summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* metalink: Drop commit data from summary, add generic a{sv}wip/metalinksColin Walters2014-08-207-117/+10
| | | | | | | | Per discussion on IRC, really all we need in the summary is the ref -> commit data. We can easily fetch the commits in a separate phase, and avoiding duplication is good. Also, to allow future extensibility, add in a generic a{sv}.
* metalink: A bit more testing, tweak debug loggingColin Walters2014-08-202-10/+12
|
* fetcher: Close request body on error pathsColin Walters2014-08-201-0/+2
| | | | | | | Otherwise, we're potentially holding up subsequent requests. I was hitting this when testing the metalink code, where we want to continue doing more fetches after hitting a 404.
* Move sync fetches into pull code, add more testsColin Walters2014-08-195-61/+120
|
* More functional metalink codeColin Walters2014-08-191-5/+50
|
* More metalink work, plus a test caseColin Walters2014-08-198-53/+257
|
* A few more metalink updatesColin Walters2014-08-195-8/+13
|
* A bit more metalink workColin Walters2014-08-1811-48/+358
|
* Bump GIO dependency to 2.38 for GTaskColin Walters2014-08-182-2/+2
| | | | I'd like to use GTask, so bump the dependency.
* wipColin Walters2014-08-151-16/+134
|
* wipColin Walters2014-08-153-29/+172
|
* wipColin Walters2014-08-073-14/+54
|
* A bit of code for repo/summaryColin Walters2014-08-063-0/+84
|
* WIP: metalink codeColin Walters2014-08-044-8/+398
|
* pull-local: Write detached metadata into the correct repositoryColin Walters2014-07-222-1/+3
| | | | | | | | We want to write to the dest repo, not src. Noticed while reviewing this code for some other bug. https://bugzilla.gnome.org/show_bug.cgi?id=733579
* repofile: Avoid segfault if querying child in non-directoryColin Walters2014-07-212-0/+14
| | | | | | | | | | | | The user might "ostree ls /usr/bin/bash/blah", which previously would segfault. A somewhat related future enhancement here would be for "ostree ls" to follow symbolic links. Reported-by: Dusty Mabe <dustymabe@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=733476
* core: Do enumerate ff/ objects as wellColin Walters2014-07-212-1/+14
| | | | | | An embarassing off-by-one here. I noticed we weren't pruning them. https://bugzilla.gnome.org/show_bug.cgi?id=733458
* core: Do enumerate content objects in archive-z2 repositoriesColin Walters2014-07-211-1/+4
| | | | | | | | | | Prune has worked fine on bare repositories for some time, but now that I finally try to delete data on the server side, I notice we weren't actually enumerating content objects =/ That caused them to not be pruned. https://bugzilla.gnome.org/show_bug.cgi?id=733458
* core: Unify object deletion code with pruneColin Walters2014-07-202-22/+26
| | | | | | | | | | The prune API duplicated logic to delete objects, and furthermore the core API to delete an object didn't clean up detached metadata. Fix the duplication by doing the obvious thing: prune should call _delete. https://bugzilla.gnome.org/show_bug.cgi?id=733452
* Fix typo in previous commitColin Walters2014-07-181-1/+1
|
* ostree-repo-resolve-rev: Add function to accept a partial checksumAnne LoVerso2014-07-184-17/+171
| | | | | | | | | | | | | | | | | | | | | | | | | This patch adds a function that will parse a partial checksum when resolving a refspec. If the inputted refspec matches a truncated existing checksum, it will return that checksum to be parsed. If multiple truncated checksums match the partial refspec, it is not unique and will return false. This addition is inspired by the same functionality in Docker, which allows a user to reference a specific commit without typing the entire checksum. partial checksums: Add function to abstract comparison This modifies the list_objects and list_objects_at functions to take an additional argument for the string that a commit starts with. If this string arg is not null, it will only list commit objects beginning with that string. This allows for a new function ostree_repo_list_commit_objects_starting_with to pass a partial string and return a list of all matching commits. This improves on the previous strategy of listing refs because it will list all commit objects, even ones in past history. This update also includes bugfixes on error handling and string comparison, and changes the output structure of resolve_partial_checksum. The new strcuture will no longer return FALSE without error. Also, the hashtable foreach now uses iter. Also includes modified test file
* core: Use ostree_commit_get_parent in ostree_repo_resolve_revJames Antill2014-07-181-4/+1
|
* ostree-remount: mount a tmpfs on /var if necessary so /var is read-writeOwen W. Taylor2014-07-091-9/+44
| | | | | | | | | | | | | | /var needs to be read-write for a functioning system. Various systemd services will fail to start if /var is read-only. After we remount /var (or if we skip remounting /var because / is read-only), if /var is still readonly, mount a tmpfs file system on /var. While this isn't strictly part of ostree, keeping it here makes sense because it keeps twiddling around with the /var mount in one place for easier coordination and maintenance. This will likely need updating if systemd gains better support for a readonly root filesystem. https://bugzilla.gnome.org/show_bug.cgi?id=732979
* pull: Only set ca path if we actually have a setting for itColin Walters2014-07-011-5/+8
| | | | | | | Otherwise, GTlsFileDatabase ends up accepting NULL for anchors, and then we don't trust any CAs at all. https://bugzilla.gnome.org/show_bug.cgi?id=726256
* core: add "tls-ca-path" optionColin Walters2014-06-274-0/+34
| | | | | | | | | | | | | | Some organizations will want to use private Certificate Authorities to serve content to their clients. While it's possible to add the CA to the system-wide CA store, that has two drawbacks: 1) Compromise of that cert means it can be used for other web traffic 2) All of ca-certificates is trusted This patch allows a much stronger scenario where *only* the CAs in tls-ca-path are used for verification from the given repository. https://bugzilla.gnome.org/show_bug.cgi?id=726256
* Add --enable-libsoup-client-certsColin Walters2014-06-261-0/+8
| | | | | The goal of this is to hard-fail if the API isn't present in the buildroot, as some downstreams may explicitly require it.
* [trivial]: Update .gitignoreColin Walters2014-06-242-0/+4
|
* manpage: Add separate manpages for each commandAnne LoVerso2014-06-2335-290/+3311
| | | | | | | | | | Using docker as a model, this update creates separate manpages for each OSTree command, such that the main manpage is not cluttered and the separate pages can provide more in-depth detail and exanples that might be useful to a user. Each page includes synopsis, description, example, and a list of options if needd. This update also alphabetizes the usage error output for ostree and ostree admin so that it matches the list on the manpage.
* [staticanalysis]: Delete an unused variableColin Walters2014-06-211-2/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=732020
* [staticanalysis]: Fix in_status_lineColin Walters2014-06-211-6/+7
| | | | | | | We need to end the status line *after* we've done a pull, as ostree admin upgrade does. Also add the correct in_status_line assignment. https://bugzilla.gnome.org/show_bug.cgi?id=732020
* [staticanalysis]: Fix some dead codeColin Walters2014-06-212-9/+0
| | | | | | | One was an unused variable, the other is actually dead because we can't have mfile != NULL. https://bugzilla.gnome.org/show_bug.cgi?id=732020
* [staticanalysis]: Actually check errors on splice() of objectsColin Walters2014-06-211-1/+1
| | | | | | | | | | | We were using unsigned size when we should have been using signed, this means we basically weren't checking for errors on write...ouch. Luckily if we e.g. hit ENOSPC during a pull, the checksums wouldn't match and we'd return an error anyways. However when writing an object, we'd end up silently ignoring it =/ https://bugzilla.gnome.org/show_bug.cgi?id=732020
* [staticanalysis]: Add assertion to pacify analyzerColin Walters2014-06-211-2/+4
| | | | | | This condition can't actually be hit, let's hint that's the case. https://bugzilla.gnome.org/show_bug.cgi?id=732020
* [staticanalysis]: Add missing va_end()Colin Walters2014-06-211-0/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=732020
* [staticanalysis]: Fix two uses of uninitialized variablesColin Walters2014-06-212-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=732020
* packaging: BR e2pColin Walters2014-06-211-1/+2
|
* remote: Minor argument parsing cleanupColin Walters2014-06-211-1/+3
| | | | | | Only access relevant portion of argv after we've verified argc. https://bugzilla.gnome.org/show_bug.cgi?id=731984
* remote: Fix regression in previous commit wrt adding branchesColin Walters2014-06-211-2/+1
| | | | | | branches is always NULL at that point, we want to look at argc. https://bugzilla.gnome.org/show_bug.cgi?id=731984
* libostree: Add ostree_repo_remote_add() API, port "ostree remote add"Colin Walters2014-06-203-90/+163
| | | | | | | | At least one external tool is using the API, and wants to add a remote, but all of the logic right now is in the tool. Move it to the library. https://bugzilla.gnome.org/show_bug.cgi?id=731984
* tests: Add a test for an empty /etc directory gaining contentColin Walters2014-06-201-1/+26
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=731924
* doc: Update overview a bitColin Walters2014-06-201-16/+28
| | | | | Link to docker, note in introductory paragraph the goal of package composition on a server.
* doc: adapting-existing: Update story on latest /usr/lib/passwd bitsColin Walters2014-06-201-13/+19
|
* doc: No need to emphasize the poweroff vs other OSes so muchColin Walters2014-06-201-15/+4
|
* doc: Update links to ContinuousColin Walters2014-06-202-5/+6
|
* docs: overview: Explicitly call out dpkg/rpmColin Walters2014-06-201-5/+7
| | | | To be more clear that we don't handle "inventory".
* pull: Emit a better error if the remote isn't foundColin Walters2014-06-191-0/+8
| | | | | | | | | | The generic GKeyFile error isn't quite informative enough here. I hit this with the new compose process where we don't automatically inject a configured remote into the generated disk images; we expect people to add them. https://bugzilla.gnome.org/show_bug.cgi?id=731346
* tests: Add a test which exercises --fsync=falseColin Walters2014-06-181-0/+6
|
* core: Fix g_file_get_uri/get_parse_name for non-root ostree filesJames Antill2014-06-181-1/+2
|
* commit: Hide --disable-fsync option, add --fsync which takes a booleanJames Antill2014-06-181-1/+36
| | | | | Per discussion on mailing list, the --disable-fsync has a double-negative thing going on; --fsync=false is clearer.
* cat: Fix a typo in usage error printoutAnne LoVerso2014-06-171-1/+1
|
View Lorry Controller Status