I'm using the standard trac from Ubuntu Intrepid : 0.11-2.<br><br>Thanks for the information :-)<br><br>Lionel<br><br><div class="gmail_quote">On Sat, Oct 25, 2008 at 6:50 PM, John Szakmeister <span dir="ltr"><<a href="mailto:john@szakmeister.net">john@szakmeister.net</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">On Sat, Oct 25, 2008 at 6:31 AM, Lionel Dricot <<a href="mailto:zeploum@gmail.com">zeploum@gmail.com</a>> wrote:<br> > Hello,<br> ><br> > I've a svn repository on an HTTP server with a Trac interface and it works<br> > well.<br> ><br> > I've done a bzr branch (using svn+http because the svn requires<br> > authentication and a known bug in bazaar prevent using direct bzr-svn with<br> > HTTP url).<br> ><br> > I've then commited a file and pushed the change back to the svn repository.<br> > It works great because the svn checkout see the file perfectly. This change<br> > is the commit 70.<br> ><br> > The problem is Trac : Trac doesn't show anything in its timeline. In "browse<br> > source", the new file is visible but if I try to click on it, I receive the<br> > answer : "No changeset 70 in the repository"<br> ><br> > That makes using bzr-svn with trac pretty annoying. Anybody has any idea on<br> > what's going on ?<br> <br> </div></div>What version of Trac are you using?  There was a couple Repository<br> caching bugs in the past that would this same behavior.  I suspect<br> this is your problem.<br> <font color="#888888"><br> -John<br> </font></blockquote></div><br>