check reports spurious unreferenced texts
Bug #165071 reported by
Matthew Fuller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Undecided
|
Robert Collins |
Bug Description
check output from below script shows unreferenced text versions where there shouldn't be any:
2 revisions
2 file-ids
2 unique file texts
1 repeated file texts
2 unreferenced text versions
#!/bin/sh -x
bzr="/home/
${bzr} init A
(
cd A ;
touch foo ;
${bzr} add ;
${bzr} ci -m '1' ;
touch bar ;
${bzr} add ;
${bzr} ci -m '2' ;
${bzr} check
)
Changed in bzr: | |
assignee: | nobody → lifeless |
Changed in bzr: | |
status: | New → Fix Committed |
Changed in bzr: | |
milestone: | none → 1.0rc1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Isn't this a duplicate of a bug that Alexander reported?
I know I've already written up a simple patch which fixes this. (no tests, etc)
Basically, I think when Andrew refactored the check code he changed it so that VersionedFileCh ecker was called with the complete list of revision ids in the repository. Rather than just the versions that were present in the knit file itself.
as a rough example
vfc.check_ file_verison_ parents( a_knit, file_id, repo.all_ revision_ ids()) file_verison_ parents( a_knit, file_id, a_knit.versions())
versus
vfc.check_
The former one gives an unreferenced text version for every version present in all_revision_ids() that is not present in a_knit.versions().
The patch should be at least on the mailing list, if not already associated with a bug.