I just did another pull, and the branch tags showed up, so @drh, I think your rebuild helped somewhat. Now to find out how the repo got into it's "broken" state in the first place.
On 1/5/16, bch <brad.har...@gmail.com> wrote: > On 1/5/16, Richard Hipp <d...@sqlite.org> wrote: >> On 1/5/16, Richard Hipp <d...@sqlite.org> wrote: >>> On 1/5/16, David Vines <d...@zombi.eclipse.co.uk> wrote: >>>> >>>> One curious aspect I do see is that the web ui has the annotation of >>>> "unpublished" against the creation of the branch. I did start by have a >>>> private branch which I then published - I do wonder if this might be >>>> part of the problem. >>>> >>> >>> There was a "private" tag on that initial check-in. I have cancelled >>> that tag. But the check-in is still showing as "unpublished". Must >>> be a bug somewhere. A "fossil rebuild" will likely clear the problem. >>> I'll try that next... >> >> Even after rebuilding, the check-in shows up as "unpublished". >> There's a bug somewhere in the "private" tag handling. Who can be the >> first to find it! > > I think we've got a few hours until Stephan Beal wakes up... > > >> I went into the repository and manually did a "DELETE FROM private >> WHERE rid=(SELECT rid FROM blob WHERE uuid LIKE '5712fa8f133228f%')". >> That got the repo working again. But that entry in the private table >> will probably reappear the next time the repo is rebuilt. >> >> But in the meantime, you can all sync the public repo and try to >> figure out what is the problem. >> -- >> D. Richard Hipp >> d...@sqlite.org >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
