From 8c7b729abe2a0002d59b9191ff517f11b91e49b8 Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Tue, 6 Jan 2015 18:47:04 -0500 Subject: [PATCH] refs: Use G_IO_ERROR_NOT_FOUND when a ref lookup fails rpm-ostree had code to check for this, which didn't actually work. See https://github.com/projectatomic/rpm-ostree/pull/56 I don't see a no backwards compatibility concern in changing this, as it's unlikely a caller would try to sensibly disambiguate FAILED. --- src/libostree/ostree-repo-refs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/libostree/ostree-repo-refs.c b/src/libostree/ostree-repo-refs.c index ca584b6626..5588c8367f 100644 --- a/src/libostree/ostree-repo-refs.c +++ b/src/libostree/ostree-repo-refs.c @@ -259,7 +259,7 @@ resolve_refspec_fallback (OstreeRepo *self, } else if (!allow_noent) { - g_set_error (error, G_IO_ERROR, G_IO_ERROR_FAILED, + g_set_error (error, G_IO_ERROR, G_IO_ERROR_NOT_FOUND, "Refspec '%s%s%s' not found", remote ? remote : "", remote ? ":" : "",