empty branches are not supported?

Bug #524325 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trac-Bzr
Fix Released
Medium
Martin von Gagern

Bug Description

trac-bzr 0.3.

If I have empty branch on the trac server (i.e. it has 0 commits) then such branch shown as plain directory in source browser, but I can't enter in it, I got error. If my branch named as "empty" then error says following:

--------------------------------------
No node empty at revision current:
--------------------------------------

Also in this case Timeline with Repository checkins does not work: it failed with InternalError and following error message:

-----------------------------
Repository checkins event provider (ChangesetModule) failed:

NoSuchRevision: KnitPackRepository('file:///C:/work/trac/bjt/htdocs/branches/empty/.bzr/repository/') has no revision null:
-----------------------------

Changed in trac-bzr:
assignee: nobody → Martin von Gagern (gagern)
importance: Undecided → Medium
milestone: none → 0.3.1
status: New → Triaged
Changed in trac-bzr:
status: Triaged → In Progress
Revision history for this message
Martin von Gagern (gagern) wrote :

Can you please check whether the attached branch lp:~gagern/trac-bzr/bug524325 does fix the issues for you? And give any other thing that might go wrong with an empty branch a check as well? If everything works as expected, I'll merge this into the 0.3 branch and release it soon.

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 524325] Re: empty branches are not supported?

Martin von Gagern пишет:
> Can you please check whether the attached branch lp:~gagern/trac-
> bzr/bug524325 does fix the issues for you? And give any other thing that
> might go wrong with an empty branch a check as well? If everything works
> as expected, I'll merge this into the 0.3 branch and release it soon.

Works for me for 2 tests mentioned in the bug report.

Changed in trac-bzr:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.