| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
usage: fedpkg.py initial-merge [-h] [-n] [repo-path [repo-path ...]]
Performs a 'git merge' of all git branches with the same content
(i.e. with the same package spec files, patch files, etc.), regardless
of their history.
This is useful after Fedora's dist-cvs to dist-git migration, as often
different branches have different histories but the same content on the
filesystem.
After these initial merges of identical trees, future merges between
the branches will be a lot easier: Easier to follow in the dependency
graph, and easier to perform without conflicts.
positional arguments:
repo-path Path to a repo to initial-merge
optional arguments:
-h, --help show this help message and exit
-n, --dry-run Whether to run without actually merging
|
|
|
|
|
|
|
|
|
| |
The function call is evaluated once when the module code is
read. However, the os.getcwd() function might give different
results at run time than at module reading time.
Replaced those default param values with None, and let the
functions call os.getcwd() if the param happens to be None.
|
|
|
|
|
|
| |
Fix rawhide branch detection (define .distshort)
Also define PackageModule.distshort for rawhide branches.
|
|
|
|
|
| |
Without rpm content, we can't init the packagemodule, so don't try to do
that when switching branches.
|
|
|
|
| |
It's redundant.
|
| |
|
|
|
|
|
| |
We could probably use this in more places, but this is a good start.
Ticket #30
|
|
|
|
| |
fedora-release and redhat-release. fixes a bug on local rpm creation
|
| |
|
| |
|
|
|
|
| |
Need more logic here to work with other chainable targets like epel.
|
|
|
|
| |
Also works for el? and olpc?
|
|
|
|
| |
This should make things work on el4/5
|
|
|
|
|
| |
This might work around a weird issue where the koji builders can't read
the git config strings in the chroot
|
| |
|
| |
|
|
|
|
| |
Comes from https://fedorahosted.org/fedora-packager/ticket/25
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Create a new list_branches function to discover the local and remote
branches. Allow creating a new branch if the requested local branch
doesn't already exist.
|
| |
|
|
|
|
|
|
|
| |
E.g. when the handshake fails, because your certificate is too old,
fedpkg will gracefully fail and not completely crash.
Signed-off-by: Thomas Spura <tomspur@fedoraproject.org>
|
|
|
|
|
|
|
|
|
|
| |
This requires that remote branches follow a naming scheme of
<release>/master and <release>/topic where release is like "f13" or
"epel6". If we don't find a f<something, epel<something>, or
olpc<something>, we assume that it is either master, or a branch of
master for rawhide, and treat it like rawhide. To determine rawhide
target we look at all the f branches, find the latest one and add 1 to
the number. Seems to work and will keep working until Fedora 99.
|
| |
|
| |
|
|
|
|
|
| |
Even though we don't use koji directly, it's helpful to users if we show
them the command they would have to use to duplicate what we are doing.
|
| |
|
|
|
|
| |
The idea here came from Xavier Lamien. I just modified it slightly.
|
| |
|
|
|
|
|
|
| |
In the case of a fresh module created upstream, we don't have a spec
file to use for information, so we have to make a git repo outside of
the module.
|
|
|
|
|
| |
This can happen if somebody uses the "upload" target on the same file
more than once.
|
| |
|
|
|
|
|
|
| |
This way we can reuse it for new-sources as well as just plain upload.
The difference is new-sources replaces current content, upload just adds
additional content.
|
|
|
|
|
| |
This is the easy way out until we have a progress bar support via the
pycurl method.
|
|
|
|
|
|
| |
The otherside will reduce it down to basename when it stores the file.
Frequently I upload source from a different directory (say an upstream
clone and source build)
|
|
|
|
|
| |
Introduces Lookaside object for interacting with the cache, as well as a
GitIgnore object for managing the project's .gitignore file.
|
| |
|
| |
|
|
|
|
| |
Also get rid of fedpkg.git and improve some documentation
|
| |
|
|
|
|
|
| |
This should work well whether you're on a real tty or not, but I didn't
test it for the "not a tty" aspect.
|
|
|
|
| |
Hurray for code removal!
|
| |
|
|
|
|
|
| |
This saves some code duplication and allows us to actually stream output
as it happens, when on a real tty. Woo!
|
|
|
|
|
| |
This is so that we can use it before we have a full fledged module to
deal with, like creating something local to play with.
|
|
|
|
|
| |
This will be useful when we start importing into fresh blank repos, but
that still needs more work.
|
| |
|