| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This is helpful for discovering when messages are being put on stderr,
we're collecting messages on stderr, but these could come from different
subprocesses leading to a confusing mixture of error messages.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously if we got a BaserockImportException which contained a '%' in
the message, you'd see this...
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/cliapp/app.py", line 190, in
_run
self.process_args(args)
File "/src/import/baserockimport/app.py", line 102, in process_args
super(BaserockImportApplication, self).process_args(args)
File "/usr/lib/python2.7/site-packages/cliapp/app.py", line 539, in
process_args
method(args[1:])
File "/src/import/baserockimport/app.py", line 185, in import_rubygems
loop.run()
File "/src/import/baserockimport/mainloop.py", line 176, in run
self.app.status(str(e), error=True)
File "/src/import/baserockimport/app.py", line 105, in status
text = msg % args
TypeError: not enough arguments for format string
|
|
|
|
|
|
|
| |
This isn't a perfect fix. If this situation occurs the tool will
generate an invalid stratum and the user will need to rename one of
the chunks. But this is a better than what would have happened before:
one of the chunks would have been silently ignored.
|
| |
|
|
|
|
|
| |
I think this makes the output a bit clearer to follow. Maybe. It's hard
to know these things until it's too late.
|
|
|
|
|
|
| |
I think this makes it clearer what the tool is actually doing, and
hopefully makes it clearer what the user should do in cases where the
tool couldn't determine which ref to use and reports an error.
|
|
|
|
|
| |
Sometimes this is due to weird version requirements caused by some other
package which isn't actually needed.
|
|
|
|
|
| |
This should be useful when a couple of components raise errors but
you know that you don't need them anyway.
|
|
|
|
|
|
| |
Previously it was hardcoded to just look for rubygems deps, which has
an obvious flaw. It now looks for all types of dependencies that were
enabled with enable_importer().
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was caused by a mistake in:
commit c8e156fe181c8e62fda9f9a999af1f0a0980a0ce
Author: Sam Thursfield <sam.thursfield@codethink.co.uk>
Date: Mon Nov 17 17:20:00 2014 +0000
Don't force the generated stratum through morphloader validation
We should be able to trust it, since we literally just generated it.
|
|
|
|
| |
We should be able to trust it, since we literally just generated it.
|
| |
|
|
|
|
| |
Now data/ actually gets installed too.
|
|
|
|
|
|
|
| |
If we create the definitions-dir we also initialise it as a Git repo,
now.
I also deleted a no-longer-needed hack.
|
|
|
|
|
| |
This version of the import tool requires morph.git commit
6779e46e880eec757a6923441accef2442007677 or newer.
|
| |
|
|
|
|
| |
Finally the repo starts to look a little more tidy!
|
|
|