[PATCH] Fix wrong path resolution
by Jan Tluka
In case when the recipe path was specified with prefix './' or none at
all, the root was incorrectly resolved to an empty string causing further
errors in path resolution.
To fix this the supplied recipe file path is converted to absolute path.
Signed-off-by: Jan Tluka <jtluka(a)redhat.com>
---
Common/RecipePath.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Common/RecipePath.py b/Common/RecipePath.py
index b5f650c..60d035d 100644
--- a/Common/RecipePath.py
+++ b/Common/RecipePath.py
@@ -20,7 +20,7 @@ def get_recipepath_class(root, path):
return HttpRecipePath(root, path)
else:
if os.access(path, os.R_OK):
- return FileRecipePath(root, path)
+ return FileRecipePath(None, os.path.realpath(path))
else:
raise Exception("Recipe path does not exist \"%s\"!" % path)
--
1.7.7.6
11 years, 6 months
[lnst trac] #35: Regression/sanity tests for LNST
by fedora-badges
#35: Regression/sanity tests for LNST
------------------------+-----------------------
Reporter: rpazdera | Owner: somebody
Type: task | Status: new
Priority: minor | Milestone:
Component: component1 | Version:
Keywords: | Blocked By:
Blocking: |
------------------------+-----------------------
We could use a set of regression tests for LNST in my opinion.
When doing big changes, it's hard to be entirely certain if the
change didn't break something.
I'm not really sure what would be the best way to do this.
We could have a set of very basic recipes each of which would
verify that at least the basic things in LNST work.
--
Ticket URL: <https://fedorahosted.org/lnst/ticket/35>
lnst <http://example.org/>
My example project
11 years, 6 months