[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Issue 201 - "pull" and "db check" have different opinio
From: |
code |
Subject: |
[Monotone-devel] Issue 201 - "pull" and "db check" have different opinion on whether branch certs are needed (monotone) |
Date: |
Tue, 06 Dec 2011 20:33:20 +0100 |
Hello,
A new issue has been created and assigned
to you:
201 - "pull" and "db check" have different opinion on whether branch certs are
needed
Project: monotone
Status: New
Reported by: Michael Raskin
Labels:
Type:Defect
Priority:Medium
Description:
Steps to reproduce the problem:
-------------------------------
1. mtn pull mtn://code.monotone.ca/\?net.venge.monotone
2. mtn db check
Expected result:
----------------
Success
Actual results:
---------------
"serious problem" reported, mtn db check return code non-zero
Problem is:
-----------
mtn pull doesn't pull branch certs unless they match the pattern that I pull.
mtn db check considers missing branch certs a serious consistency problem.
It would be nice if monotone would pull all certs for pulled revisions. It
would be nice if I could force mtn db check to ignore some classes of
consistency half-problems. Two valid changelogs is not a problem worth my
attention in most cases.
It is a bug that succesful mtn pull can create whatever monotone can call a
serious problem. The simplest solution is probably to demote missing branch
certificates to an mtn db check warning.
--
Issue: https://code.monotone.ca/p/monotone/issues/201/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Monotone-devel] Issue 201 - "pull" and "db check" have different opinion on whether branch certs are needed (monotone),
code <=