| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
| |
Hello Jesse,
using the stream keyword caused an error on python 2.6.
So I have remove this keyword.
Best Regards:
Jochen Schmitt
|
|
|
|
| |
Just raise it, let the caller figure out what to do.
|
| |
|
|
|
|
|
| |
The output of 'git branch' is not guaranteed to remain constant. Using
the for-each-ref plumbing command should work reliably for longer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bash completion 'filenames' option prevents proper completion of
local refs like tmz/f13.
On systems with bash-completion >= 1.2, this should have little effect
because the _filedir command sets the option as needed (or emulates it
on older bash releases that lack compopt).
On systems with older bash-completion (like EL-5 currently), there is a
minor downside in that filename completion won't append trailing slashes
to directories without the 'filenames' option. Ideally, bash-completion
will be updated on EL-5 and this minor inconvenience will vanish
sometime soon.
|
|
|
|
|
| |
The _filedir function is a bit more robust than using compgen directly.
A wrapper function is used to filter out .git directories from results.
|
|
|
|
|
|
| |
Make sure that WARN, ERROR, and CRITICAL go to stderr, and that DEBUG
and INFO go to stdout. This involves more configuration than it aught
to, but that's python logging for ya.
|
|
|
|
|
|
| |
It's of my opinion that only errors should go to stderr. For that
reason I'll have all logger stuff to go stdout and any errors I'll use
print() on.
|
|
|
|
| |
Again this is just because rpmbuild does some stupid things.
|
| |
|
| |
|
|
|
|
|
|
| |
command
From Jochen@herr-schmitt.de
|
|
|
|
|
|
|
|
|
|
|
| |
Hello Jesse,
because I don't like duplicate code, I have create a getuser() function
which determinate the userid of the fas account.
Best Regards:
Jochen Schmitt
|
|
|
|
|
|
|
|
| |
The _get_comp_words_by_ref is provided by bash-completion >= 1.2, which
EL-5 lacks. Attempting to use fedpkg completion on EL-5 results in
errors: $ fedpkg <TAB>-bash: _get_comp_words_by_ref: command not found
Fall back to using ${COMP_WORDS[COMP_CWORD]}.
|
|
|
|
|
|
|
|
|
|
|
| |
If there is a entry which matches the filename we're about to add
already in the gitignore file, we don't need to bother adding another
entry.
This adds a match() method to GitIgnore which uses fnmatch. Under the
hood, this is what git uses. It doesn't catch some of the special cases
git has, but it should simply fail to match in those cases and will add
a potentially redundant entry -- no different than previously.
|
|
|
|
|
| |
- completes koji targets, sytem architectures, git branches, filenames
and SRPM names after specific options
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
I don't like doing this, but I'm failing at coming up with a clever way
to only do it in cases we know we want it, such as rpmbuild calls.
Since that's the only thing we're piping right now, call it good, but I
still don't like it.
|
| |
|
|
|
|
| |
We should just remove this at some point soon
|
|
|
|
| |
One of these times I'll get it right.
|
|
|
|
|
| |
Saves a bunch of time waiting for the srpm creation and koji to figure
out what n-v-r we're trying to build. Ticket #27
|
| |
|
|
|
|
| |
This might only effect running from a checkout.
|
| |
|
|
|
|
| |
clone: set repo's push.default to tracking
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Outside of clog, there is no reason why commit should need data from the
spec file. This fixes a bug when marking a package as dead so that one
can commit again. Ticket #54
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A function call used as a default parameter value is evaluated
once when the module code is first read in. However, the
os.getcwd() function might give different results at run time
than at module reading time.
This replaces those default param values with None, and has the
function bodies call os.getcwd() if the param happens to be None.
See also
http://docs.python.org/reference/compound_stmts.html#function-definitions
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We were not setting up the chains right, and our logging was all funky.
We now handle chains properly and log it sensibly
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
RHBZ 620254 Arguably we should also check in the library, but I'm too
lazy to do that right now.
|