wscott
February 9, 2019, 12:03pm
1
BitKeeper version 7.3.3 released Dec 29 2018
A bugfix release, but fixes build issues on current systems
This release fixes some problems where bk fails to build correctly
‘bk relink’ could assert in a certain corner casebk: remap.c:119: remap_lstat: Assertion sccs failed.
Fix a bug where ‘bk cp’ didn’t work correctly when run from outside
Fix ‘bk changes --html’ to handle quoting in comments.
difftool would use the wrong timestamp when extracting data from bk
Fixed a bug where ‘bk collapse’ could corrupt a repository by
This fixes the problems discussed in these threads:
I’d like to report 2 bugs in the output generated by bk changes --html ...:
the HTML is invalid (bad nesting of <tr> and <td> elements, sometimes not closed with </tr>, …etc.)
the bk comments making up the table content is not masked in HTML. If, for example, a ChangeSet contains a comment with special HTML characters like “I’m including <stdio.h> now” it’ll mess up the output.
While most browsers can handle the first topic gracefully, the second one becomes a real issue. Also, the output is …
Hi,
I’m a PhD student. I analyzed the BK source code and found some potential API bugs that may cause crashes.
These crashes are mainly caused by insufficient error handling of API functions like chdir, gethostbyname or XGetImage.
I think it’s unsafe to assume the library function would be correct. It would be better if we could handle the error properly.
I can’t upload the patch so far, so I post the patch (against version 7.3.2) here.
Best,
Zhouyang
diff --git a/src/gui/tcltk/tk/generi…
So I was looking to see who changed a line of code, and when. I fired up revtool and isolated the line. I fired up difftool from revtool and I see the before and after files with the differences.
In revtool, the “before” file is dated Jan xx, 2011, and the “after” file is dated Feb xx, 2011.
In difftool, the two files are dated “now”.
Is there a way I can tell difftool to show me the dates of the files I’m looking at instead of the current date/time??
Hi.
I did a “bk collapse -a 1.432 -e” thinking that 1.432 and 1.433 were my last two commits, and they’d be merged. No such luck.
Now “bk changes -vv” doesn’t show me any commits prior to 1.357 and 8/20/2000. What?!?!
Clearly I did something wrong.
The man page suggests that what I did isn’t yet final, but I can’t figure out how to undo it if it isn’t final.
Thanks,
-Philip
(From our-ref D128468)
This was perhaps our last commercial case with bk support. I don’t think Larry applied his fix. On email, Wayne mentioned having to “hunt it down or reproduce it”, which sounds painfully like he might not have easy access to the information below, which I think we’d be happy to share publicly.
-----Original Message-----
From: Martin Dorey
Sent: Friday, February 03, 2017 09:30
...
Subject: RE: bk relink fails with 3rdParty/HiStorAPI-5.11.0.3981
> If you want a trial …
One of my guys uses fedora 27 at his place, and he’s having a miserable time trying to get bk-7.3.2 built on this.
Any suggestions? He checked out the code from git, and the build fails because he doesn’t already have bk. He tries an earlier version of BK, and that fork-bombs on him.
I’m installing a fedora 27 workstation VM to see if I can get something going, but I wanted to get this thread started. I’ll be updating this with information as my efforts progress.
Hi Wayne,
I am trying to upgrade from 7.3.2 to 7.3.3 and I get the following error when pulling or cloning from bk://bkbits.net/bk/bugfix:
“ERROR-Could not lock product, mutex failed”. Any ideas?
Thanks,
Hasani
wscott
February 20, 2019, 3:39pm
3
There was an issue on that server. Should be fixed now.