• Your recent searches
Alien-SVN
22 results

 view release on metacpan or  search on metacpan

src/subversion/build/install-sh  view on Meta::CPAN 

    else
      # Rename the file to the real destination.
      $doit $mvcmd -f "$dsttmp" "$dst" 2>/dev/null ||

      # The rename failed, perhaps because mv can't rename something else
      # to itself, or perhaps because mv is so ancient that it does not
      # support -f.
      {
	# Now remove or move aside any old file at destination location.
	# We try this two ways since rm can't unlink itself on some
	# systems and the destination file might be busy for other
	# reasons.  In this case, the final cleanup might fail but the new
	# file should still install successfully.
	{
	  test ! -f "$dst" ||
	  $doit $rmcmd -f "$dst" 2>/dev/null ||
	  { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
	    { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
	  } ||
	  { echo "$0: cannot unlink or rename $dst" >&2
	    (exit 1); exit 1

src/subversion/doc/doxygen.conf  view on Meta::CPAN 

# be useful for C code in case the coding convention dictates that all compound
# types are typedef'ed and only the typedef is referenced, never the tag name.

TYPEDEF_HIDES_STRUCT   = NO

# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
# determine which symbols to keep in memory and which to flush to disk.
# When the cache is full, less often used symbols will be written to disk.
# For small to medium size projects (<1000 input files) the default value is
# probably good enough. For larger projects a too small cache size can cause
# doxygen to be busy swapping symbols to and from disk most of the time
# causing a significant performance penality.
# If the system has enough physical memory increasing the cache will improve the
# performance by keeping more symbols in memory. Note that the value works on
# a logarithmic scale so increasing the size by one will rougly double the
# memory usage. The cache size is given by this formula:
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
# corresponding to a cache size of 2^16 = 65536 symbols

SYMBOL_CACHE_SIZE      = 0

src/subversion/subversion/include/svn_error_codes.h  view on Meta::CPAN 

  /** @since New in 1.6.
   * @deprecated the internal sqlite support code does not manage schemas
   * any longer.  */
  SVN_ERRDEF(SVN_ERR_SQLITE_UNSUPPORTED_SCHEMA,
             SVN_ERR_MISC_CATEGORY_START + 32,
             "Unsupported schema found in SQLite db")

  /** @since New in 1.7. */
  SVN_ERRDEF(SVN_ERR_SQLITE_BUSY,
             SVN_ERR_MISC_CATEGORY_START + 33,
             "The SQLite db is busy")

  /** @since New in 1.7. */
  SVN_ERRDEF(SVN_ERR_SQLITE_RESETTING_FOR_ROLLBACK,
             SVN_ERR_MISC_CATEGORY_START + 34,
             "SQLite busy at transaction rollback; "
             "resetting all busy SQLite statements to allow rollback")

  /** @since New in 1.7. */
  SVN_ERRDEF(SVN_ERR_SQLITE_CONSTRAINT,
             SVN_ERR_MISC_CATEGORY_START + 35,
             "Constraint error in SQLite db")

  /** @since New in 1.8. */
  SVN_ERRDEF(SVN_ERR_TOO_MANY_MEMCACHED_SERVERS,
             SVN_ERR_MISC_CATEGORY_START + 36,
             "Too many memcached servers configured")

src/subversion/subversion/libsvn_fs_base/tree.c  view on Meta::CPAN 

   *
   * When you're ready to commit, here's what you have:
   *
   *    1. A transaction, with a mutable tree hanging off it.
   *    2. A base revision, against which TXN_TREE was made.
   *    3. A latest revision, which may be newer than the base rev.
   *
   * The problem is that if latest != base, then one can't simply
   * attach the txn root as the root of the new revision, because that
   * would lose all the changes between base and latest.  It is also
   * not acceptable to insist that base == latest; in a busy
   * repository, commits happen too fast to insist that everyone keep
   * their entire tree up-to-date at all times.  Non-overlapping
   * changes should not interfere with each other.
   *
   * The solution is to merge the changes between base and latest into
   * the txn tree [see the function merge()].  The txn tree is the
   * only one of the three trees that is mutable, so it has to be the
   * one to adjust.
   *
   * You might have to adjust it more than once, if a new latest

src/subversion/subversion/libsvn_fs_fs/tree.c  view on Meta::CPAN 

   *
   * When you're ready to commit, here's what you have:
   *
   *    1. A transaction, with a mutable tree hanging off it.
   *    2. A base revision, against which TXN_TREE was made.
   *    3. A latest revision, which may be newer than the base rev.
   *
   * The problem is that if latest != base, then one can't simply
   * attach the txn root as the root of the new revision, because that
   * would lose all the changes between base and latest.  It is also
   * not acceptable to insist that base == latest; in a busy
   * repository, commits happen too fast to insist that everyone keep
   * their entire tree up-to-date at all times.  Non-overlapping
   * changes should not interfere with each other.
   *
   * The solution is to merge the changes between base and latest into
   * the txn tree [see the function merge()].  The txn tree is the
   * only one of the three trees that is mutable, so it has to be the
   * one to adjust.
   *
   * You might have to adjust it more than once, if a new latest

src/subversion/subversion/libsvn_ra_serf/update.c  view on Meta::CPAN 



/* While we process the REPORT response, we will queue up GET and PROPFIND
   requests. For a very large checkout, it is very easy to queue requests
   faster than they are resolved. Thus, we need to pause the XML processing
   (which queues more requests) to avoid queueing too many, with their
   attendant memory costs. When the queue count drops low enough, we will
   resume XML processing.

   Note that we don't want the count to drop to zero. We have multiple
   connections that we want to keep busy. These are also heuristic numbers
   since network and parsing behavior (ie. it doesn't pause immediately)
   can make the measurements quite imprecise.

   We measure outstanding requests as the sum of NUM_ACTIVE_FETCHES and
   NUM_ACTIVE_PROPFINDS in the report_context_t structure.  */
#define REQUEST_COUNT_TO_PAUSE 50
#define REQUEST_COUNT_TO_RESUME 40


/* Forward-declare our report context. */

src/subversion/subversion/libsvn_subr/sqlite.c  view on Meta::CPAN 


          /* We don't catch the error here, since we care more about the open
             error than the close error at this point. */
          sqlite3_close(*db3);

          SQLITE_ERR_MSG(err_code, msg);
        }
    }
  }

  /* Retry until timeout when database is busy. */
  SQLITE_ERR_MSG(sqlite3_busy_timeout(*db3, BUSY_TIMEOUT),
                 sqlite3_errmsg(*db3));

  return SVN_NO_ERROR;
}


/* APR cleanup function used to close the database when its pool is destroyed.
   DATA should be the svn_sqlite__db_t handle for the database. */
static apr_status_t
close_apr(void *data)

src/subversion/subversion/libsvn_subr/sqlite.c  view on Meta::CPAN 

      err2 = get_internal_statement(&stmt, db,
                                    STMT_INTERNAL_ROLLBACK_TRANSACTION);
      if (!err2)
        err2 = svn_sqlite__step_done(stmt);

      if (err2 && err2->apr_err == SVN_ERR_SQLITE_BUSY)
        {
          /* ### Houston, we have a problem!

             We are trying to rollback but we can't because some
             statements are still busy. This leaves the database
             unusable for future transactions as the current transaction
             is still open.

             As we are returning the actual error as the most relevant
             error in the chain, our caller might assume that it can
             retry/compensate on this error (e.g. SVN_WC_LOCKED), while
             in fact the SQLite database is unusable until the statements
             started within this transaction are reset and the transaction
             aborted.

             We try to compensate by resetting all prepared but unreset
             statements; but we leave the busy error in the chain anyway to
             help diagnosing the original error and help in finding where
             a reset statement is missing. */

          err2 = reset_all_statements(db, err2);
          err2 = svn_error_compose_create(
                      svn_sqlite__step_done(stmt),
                      err2);
        }

      return svn_error_compose_create(err,

src/subversion/subversion/libsvn_wc/conflicts.c  view on Meta::CPAN 

    {
      const svn_string_t *conflict_base_val;
      const char *file_name;

      if (! svn_string_compare(base_val, incoming_old_val))
        {
          /* What happens if 'base' and 'old' don't match up?  In an
             ideal situation, they would.  But if they don't, this is
             a classic example of a patch 'hunk' failing to apply due
             to a lack of context.  For example: imagine that the user
             is busy changing the property from a value of "cat" to
             "dog", but the incoming propchange wants to change the
             same property value from "red" to "green".  Total context
             mismatch.

             HOWEVER: we can still pass one of the two base values as
             'base_file' to the callback anyway.  It's still useful to
             present the working and new values to the user to
             compare. */

          if (working_val && svn_string_compare(base_val, working_val))

src/subversion/subversion/po/de.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1293
msgid "Attempted to write to readonly SQLite db"
msgstr "Versuch, in eine nur lesbare SQLite-Datenbank zu schreiben"

#: ../include/svn_error_codes.h:1300
msgid "Unsupported schema found in SQLite db"
msgstr "Nicht unterstütztes Schema in SQLite-Datenbank gefunden"

#: ../include/svn_error_codes.h:1305
msgid "The SQLite db is busy"
msgstr "Die SQLite-Datenbank ist beschäftigt"

#: ../include/svn_error_codes.h:1310
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr "SQLite ist mit dem Rollback einer Transaktion beschäftigt; Alle SQLite-Anweisungen werden für Rollback zurückgesetzt"

#: ../include/svn_error_codes.h:1316
msgid "Constraint error in SQLite db"
msgstr "Constraint-Fehler in SQLite-Datenbank"

#: ../include/svn_error_codes.h:1321
msgid "Too many memcached servers configured"
msgstr "Zu viele memcached-Server konfiguriert"

src/subversion/subversion/po/es.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1330
msgid "Attempted to write to readonly SQLite db"
msgstr "Intento de escribir en una base SQLite de sólo lectura"

#: ../include/svn_error_codes.h:1335
msgid "Unsupported schema found in SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1340
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1345
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1352
msgid "Error parsing arguments"
msgstr "Error analizando parámetros"

#: ../include/svn_error_codes.h:1356
msgid "Not enough arguments provided"
msgstr "No se dieron suficientes parámetros"

src/subversion/subversion/po/fr.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1378
msgid "Attempted to write to readonly SQLite db"
msgstr "Tentative d'écriture vers base SQLite en lecture seule"

#: ../include/svn_error_codes.h:1385
msgid "Unsupported schema found in SQLite db"
msgstr "Schema non supporté dans une base SQLite"

#: ../include/svn_error_codes.h:1390
msgid "The SQLite db is busy"
msgstr "La base SQLite est occupée"

#: ../include/svn_error_codes.h:1395
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr "SQLite occupé à annuler une transaction ; remise à zéro des opérations SQLite pour le permettre"

#: ../include/svn_error_codes.h:1401
msgid "Constraint error in SQLite db"
msgstr "Violation de contraintes dans une base SQLite"

#: ../include/svn_error_codes.h:1406
msgid "too many memcached servers configured"
msgstr "Trop de serveurs de cache mémoire configurés"

src/subversion/subversion/po/it.po  view on Meta::CPAN 

#: ../include/svn_error_codes.h:1330
#, fuzzy
msgid "Attempted to write to readonly SQLite db"
msgstr "Tentativo di scrittura in una non-transazione"

#: ../include/svn_error_codes.h:1335
msgid "Unsupported schema found in SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1340
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1345
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1352
msgid "Error parsing arguments"
msgstr "Errore nell'analisi degli argomenti"

#: ../include/svn_error_codes.h:1356
msgid "Not enough arguments provided"
msgstr "Numero insufficiente di argomenti"

src/subversion/subversion/po/ja.po  view on Meta::CPAN 

#: ../include/svn_error_codes.h:1330
#, fuzzy
msgid "Attempted to write to readonly SQLite db"
msgstr "トランザクションでないものに書き込もうとしました"

#: ../include/svn_error_codes.h:1335
msgid "Unsupported schema found in SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1340
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1345
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1352
msgid "Error parsing arguments"
msgstr "引数をパースする際にエラーが生じました"

#: ../include/svn_error_codes.h:1356
msgid "Not enough arguments provided"
msgstr "十分な引数が与えられていません"

src/subversion/subversion/po/ko.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1335
msgid "Attempted to write to readonly SQLite db"
msgstr "읽기전용 SQLite db에 쓰기시도를 하였습니다"

#: ../include/svn_error_codes.h:1340
msgid "Unsupported schema found in SQLite db"
msgstr "SQLite db에 지원하지 않는 스키마가 발견되었습니다"

#: ../include/svn_error_codes.h:1345
msgid "The SQLite db is busy"
msgstr "SQLite DB가 바쁩니다"

#: ../include/svn_error_codes.h:1350
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr "트랜잭션 롤백시에 SQLite가 분주하여, 롤백이 가능하도록 모든 SQLite statement를 리셋합니다"

#: ../include/svn_error_codes.h:1357
msgid "Error parsing arguments"
msgstr "인자를 분석 도중 오류 발생"

#: ../include/svn_error_codes.h:1361
msgid "Not enough arguments provided"
msgstr "인자가 충분히 주어지지 않았습니다"

src/subversion/subversion/po/nb.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1330
msgid "Attempted to write to readonly SQLite db"
msgstr "Forsøkte å skrive til skrivebeskyttet SQLite-database"

#: ../include/svn_error_codes.h:1335
msgid "Unsupported schema found in SQLite db"
msgstr "Fant skjema som ikke er støttet i SQLite-database"

#: ../include/svn_error_codes.h:1340
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1345
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1352
msgid "Error parsing arguments"
msgstr "Feil under tolking av argumenter"

#: ../include/svn_error_codes.h:1356
msgid "Not enough arguments provided"
msgstr "Ikke nok argumenter angitt"

src/subversion/subversion/po/pl.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1330
msgid "Attempted to write to readonly SQLite db"
msgstr "Próba zapisu do bazy danych SQLite otwartej w trybie tylko do odczytu"

#: ../include/svn_error_codes.h:1335
msgid "Unsupported schema found in SQLite db"
msgstr "Nieobsługiwany schemat znaleziony w bazie danych SQLite"

#: ../include/svn_error_codes.h:1340
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1345
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1352
msgid "Error parsing arguments"
msgstr "Błąd podczas parsowania parametrów"

#: ../include/svn_error_codes.h:1356
msgid "Not enough arguments provided"
msgstr "Zbyt mało parametrów"

src/subversion/subversion/po/pt_BR.po  view on Meta::CPAN 

#: ../include/svn_error_codes.h:1330
#, fuzzy
msgid "Attempted to write to readonly SQLite db"
msgstr "Tentativa de escrever em não transacional"

#: ../include/svn_error_codes.h:1335
msgid "Unsupported schema found in SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1340
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1345
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1352
msgid "Error parsing arguments"
msgstr "Erro ao realizar parsing de argumentos"

#: ../include/svn_error_codes.h:1356
msgid "Not enough arguments provided"
msgstr "Poucos argumentos fornecidos"

src/subversion/subversion/po/subversion.pot  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1293
msgid "Attempted to write to readonly SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1300
msgid "Unsupported schema found in SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1305
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1310
msgid ""
"SQLite busy at transaction rollback; resetting all busy SQLite statements to "
"allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1316
msgid "Constraint error in SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1321
msgid "Too many memcached servers configured"
msgstr ""

src/subversion/subversion/po/sv.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1293
msgid "Attempted to write to readonly SQLite db"
msgstr "Försök att skriva till skrivskyddad SQLite-databas"

#: ../include/svn_error_codes.h:1300
msgid "Unsupported schema found in SQLite db"
msgstr "Schemat i SQLite-databasen stöds ej"

#: ../include/svn_error_codes.h:1305
msgid "The SQLite db is busy"
msgstr "SQLite-databasen är upptagen"

#: ../include/svn_error_codes.h:1310
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr "SQLite upptagen vid transaktionsåterladding; återställer alla upptagna SQLite-satser för att tillåta återladdning"

#: ../include/svn_error_codes.h:1316
msgid "Constraint error in SQLite db"
msgstr "Restriktionsfel i SQLite-databas"

#: ../include/svn_error_codes.h:1321
msgid "Too many memcached servers configured"
msgstr "För många konfigurerade memcached-servrar"

src/subversion/subversion/po/zh_CN.po  view on Meta::CPAN 


#: ../include/svn_error_codes.h:1293
msgid "Attempted to write to readonly SQLite db"
msgstr "试图写至只读 SQLite 数据库"

#: ../include/svn_error_codes.h:1300
msgid "Unsupported schema found in SQLite db"
msgstr "不支持 SQLite 数据库中的方案"

#: ../include/svn_error_codes.h:1305
msgid "The SQLite db is busy"
msgstr "SQLite 数据库繁忙"

#: ../include/svn_error_codes.h:1310
msgid ""
"SQLite busy at transaction rollback; resetting all busy SQLite statements to "
"allow rollback"
msgstr "SQLite 忙于回滚事务; 请重置所有繁忙的 SQLite 语句，以便允许回滚"

#: ../include/svn_error_codes.h:1316
msgid "Constraint error in SQLite db"
msgstr "在 SQLite 数据库中的约束出错"

#: ../include/svn_error_codes.h:1321
msgid "Too many memcached servers configured"
msgstr "配置了太多的 memcached 服务器"

src/subversion/subversion/po/zh_TW.po  view on Meta::CPAN 

#: ../include/svn_error_codes.h:1330
#, fuzzy
msgid "Attempted to write to readonly SQLite db"
msgstr "企圖寫至非異動"

#: ../include/svn_error_codes.h:1335
msgid "Unsupported schema found in SQLite db"
msgstr ""

#: ../include/svn_error_codes.h:1340
msgid "The SQLite db is busy"
msgstr ""

#: ../include/svn_error_codes.h:1345
msgid "SQLite busy at transaction rollback; resetting all busy SQLite statements to allow rollback"
msgstr ""

#: ../include/svn_error_codes.h:1352
#, fuzzy
msgid "Error parsing arguments"
msgstr "用戶端於剖析引數時發生錯誤"

#: ../include/svn_error_codes.h:1356
#, fuzzy
msgid "Not enough arguments provided"

src/subversion/tools/dev/benchmarks/suite1/generate_charts  view on Meta::CPAN 

SVN_A_NAME="1.7.0"
SVN_B_NAME="trunk"

# benchmark script and parameters...
benchmark="$PWD/benchmark.py"

db="$PWD/${SVNBENCH_DEBUG}benchmark.db"

chartsdir="$PWD/charts"

mkdir -p "$chartsdir/.busy"

if [ ! -e "$chartsdir/README" ]; then
  cat > "$chartsdir/README" <<END
These charts are generated by svn benchmark suite1.
http://svn.apache.org/repos/asf/subversion/trunk/tools/dev/benchmarks/suite1

*DISCLAIMER* - This tests only file://-URL access on a GNU/Linux VM.
This is intended to measure changes in performance of the local working
copy layer, *only*. These results are *not* generally true for everyone.
END

src/subversion/tools/dev/benchmarks/suite1/generate_charts  view on Meta::CPAN 

  if [ -z "$levelspread" ]; then
    lsarg=""
    lstitle=""
  else
    lsarg=",$levelspread"
    lstitle=", WC dir levels x spread = $levelspread"
  fi
  N=12
  "$benchmark" -f "$db" chart compare \
     ${SVN_A_NAME}$lsarg ${SVN_B_NAME}@last${N}$lsarg \
     -o "$chartsdir/.busy/compare_${SVN_A_NAME}_${SVN_B_NAME}@last${N}$lsarg.svg" \
     -t "svn client benchmarks, file:// access *only*$lstitle"
done

mv "$chartsdir/.busy/"*.svg "$chartsdir/"
rmdir "$chartsdir/.busy"



( run in 0.368 second using v1.01-cache-2.11-cpan-87723dcf8b7 )