| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
instead use loglevels (critical, error, warn, info, debug). Default to WARN for repoman, which will print CRITICAL, ERROR, and WARN messages. one -v will print INFO messages and two -v's will print DEBUG messages, each -q will reduce the loglevel by one. -q and -v can be given in any order.
svn path=/main/trunk/; revision=8250
|
|
|
|
|
|
| |
it obvious as to why; lets try removing those dupe checks.
svn path=/main/trunk/; revision=8247
|
|
|
|
| |
svn path=/main/trunk/; revision=8246
|
|
|
|
|
|
| |
add some weird ass code, but it looked fine on sources.gentoo.org). Next time I'll try and either work in a branch or commit faster ;)
svn path=/main/trunk/; revision=8245
|
|
|
|
|
|
| |
over 80 columns.
svn path=/main/trunk/; revision=8243
|
|
|
|
| |
svn path=/main/trunk/; revision=8242
|
|
|
|
|
|
| |
files in dodoc arguments.
svn path=/main/trunk/; revision=8236
|
|
|
|
| |
svn path=/main/trunk/; revision=8235
|
|
|
|
|
|
|
| |
any existing resume lists from the mtimedb. Thanks to Arfrever
Frehtes Taifersar Arahesis for the initial patch.
svn path=/main/trunk/; revision=8224
|
|
|
|
|
|
| |
(bug #196565)
svn path=/main/trunk/; revision=8200
|
|
|
|
|
|
| |
is an existing directory and exit gracefully if not.
svn path=/main/trunk/; revision=8195
|
|
|
|
|
|
|
|
|
| |
command that is suitable for identifying all packages that own
one or more files when a file collision has occurred. This uses
dblink.isowner() so that the query works properly even when
paths are ambiguous due to symlinked directories.
svn path=/main/trunk/; revision=8154
|
|
|
|
|
|
|
| |
since it's mostly unsuitable for api consumers at
this time.
svn path=/main/trunk/; revision=8142
|
|
|
|
| |
svn path=/main/trunk/; revision=8140
|
|
|
|
|
|
| |
diff_command.
svn path=/main/trunk/; revision=8130
|
|
|
|
|
|
| |
when using_editor is true.
svn path=/main/trunk/; revision=8129
|
|
|
|
| |
svn path=/main/trunk/; revision=8125
|
|
|
|
|
|
| |
does not exist.
svn path=/main/trunk/; revision=8117
|
|
|
|
| |
svn path=/main/trunk/; revision=7996
|
|
|
|
|
|
|
| |
to avoid digest verification issues when FEATURES="strict"
is enabled.
svn path=/main/trunk/; revision=7995
|
|
|
|
|
|
| |
get confusing loops where portage claims there are things to update but etc-update claims there are not
svn path=/main/trunk/; revision=7994
|
|
|
|
| |
svn path=/main/trunk/; revision=7993
|
|
|
|
| |
svn path=/main/trunk/; revision=7992
|
|
|
|
| |
svn path=/main/trunk/; revision=7991
|
|
|
|
| |
svn path=/main/trunk/; revision=7990
|
|
|
|
| |
svn path=/main/trunk/; revision=7983
|
|
|
|
|
|
|
|
|
| |
a ValueError if cpv_expand() receives an ambiguous
atom. Therefore, move the ValueError handling code
out of match() and use it to handle all such errors
when appropriate.
svn path=/main/trunk/; revision=7944
|
|
|
|
|
|
| |
command.
svn path=/main/trunk/; revision=7918
|
|
|
|
|
|
| |
--force is disabled.
svn path=/main/trunk/; revision=7915
|
|
|
|
|
|
|
|
| |
access ebuild metadata for some reason. In this
case it's impossible to generate a Manifest and
therefore the --force option has to be disabled.
svn path=/main/trunk/; revision=7914
|
|
|
|
| |
svn path=/main/trunk/; revision=7908
|
|
|
|
| |
svn path=/main/trunk/; revision=7907
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for SRC_URI.syntax and digestentry.unused that are
reported when the SRC_URI for one or more ebuilds
can't be parsed for some reason. There's no point
in producing a false error here since the root
cause will produce a valid error elsewhere, such
as "SRC_URI.syntax" or "ebuild.sytax". Also,
update the docs for the "ebuild.syntax" error to
indicate that a digest verification failure can
trigger it.
svn path=/main/trunk/; revision=7905
|
|
|
|
| |
svn path=/main/trunk/; revision=7899
|
|
|
|
|
|
| |
much faster than readlines(), see http://dev.gentoo.org/~antarus/projects/portage/stats/StringIOVsFiles.txt
svn path=/main/trunk/; revision=7897
|
|
|
|
|
|
| |
and get them out of repoman in an attempt to start moving other checks out as well. Again wonder at the price of StringIO and N passes, is the readability worth it?
svn path=/main/trunk/; revision=7895
|
|
|
|
|
|
|
|
| |
the "diff" command so that any remnants of the previous
config are now shown with the current one.
command so that
svn path=/main/trunk/; revision=7893
|
|
|
|
| |
svn path=/main/trunk/; revision=7890
|
|
|
|
| |
svn path=/main/trunk/; revision=7887
|
|
|
|
| |
svn path=/main/trunk/; revision=7879
|
|
|
|
| |
svn path=/main/trunk/; revision=7878
|
|
|
|
|
|
|
|
| |
prevent spurious input characters from being interpreted
as user input (which can be quite confusing and gives
an "out of control" feeling).
svn path=/main/trunk/; revision=7877
|
|
|
|
| |
svn path=/main/trunk/; revision=7866
|
|
|
|
|
|
| |
to the call to die so we can print it out in our error message
svn path=/main/trunk/; revision=7852
|
|
|
|
| |
svn path=/main/trunk/; revision=7850
|
|
|
|
|
|
|
| |
errors. This patch uses a weird tr '\001' '\000' workaround since bash
doesn't echo null bytes like one might expect.
svn path=/main/trunk/; revision=7848
|
|
|
|
|
|
| |
phase when necessary.
svn path=/main/trunk/; revision=7846
|
|
|
|
|
|
|
|
|
| |
sourced since it is easy to ignore and ignorance of it often
leads to mysterious problems and general confusion. This
message should not show in cases where it is obviously
irrelevant, FEATURES=noauto, or PORTAGE_QUIET=1.
svn path=/main/trunk/; revision=7844
|
|
|
|
|
|
| |
it is much easier to read
svn path=/main/trunk/; revision=7842
|
|
|
|
| |
svn path=/main/trunk/; revision=7839
|