18509 is 18510

[Dave_L]

I don't know if this is worthwhile correcting:

On your downloads page http://www.scootersoftware.com/beta.php?zz=beta4_dl, at least one of the downloads labelled as "build 18509" (4.0.0.18509_i386.deb) is actually build 18510.

[Aaron]

Thanks for the report. This is a small bug that is in the About dialog. The released version is actually 18509, but is reporting itself as 10 in the About dialog.

[Dave_L]

Here are the contents of the file DEBIAN/control in the .deb that contains the version number:

Package: bcompare
Version: [b]4.0.0-18510[/b]
Section: non-free/devel
Priority: optional
Architecture: i386
Installed-Size: 30208
Depends: libc6, libfontconfig1 (>= 2.4.0), libfreetype6, libgcc1 (>= 1:4.1.1), libice6 (>= 1:1.0.0), libsm6, libstdc++6 (>= 4.1.1), libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxft2 (>> 2.1.1), libxi6, libxinerama1, libxrandr2, libxrender1, libxt6, zlib1g (>= 1:1.1.4), fontconfig, libbz2-1.0
Maintainer: Scooter Software <[email protected]>
Homepage: http://www.scootersoftware.com/
Description: Beyond Compare 4
 Beyond Compare is a powerful time-saving utility for comparing files and
 folders.
 Use it to manage source code, keep folders in sync, compare program output,
 and validate copies of your data.  Beyond Compare can create a snapshot of a
 live directory structure, and compare it against the live copy at a later
 date.
 Beyond Compare helps you analyze differences in detail and carefully reconcile
 them.  It commands a wide range of file and text operations, as well as script
 commands for automating tasks.

The version field is "4.0.0-18510".

[Aaron]

Right, although there is a specific code change in build 18510 that we could verify isn't in the current release (a small fix to the File view -> Browse for File with Profile dialog that didn't quite make the cut for this beta build release cycle). So, the build is actually 18509, but is reporting as 18510. It's something that occurred during the build process that we found very shortly after release, but shouldn't cause any problems for the next release.

[Dave_L]

The file Debian/control is manually edited, and the build number there was mistakenly specified as 18510?

Ok, I understand.

The package manager apparently also uses this file, but hopefully this will not cause any upgrade issues.

[Zoë]

No, everything is automated. The build number is actually our Subversion repository revision, and it's pulled out as part of the build process to be used everywhere the version information is needed. The three platforms are each built on different build machines, so they each need a separate checkout of the source code. We create a branch for the release, so they all have the same source, but there was a commit made to trunk during the build, and the Subversion revision for the entire tree was bumped by the time the Linux/Mac builds asked for it. It won't affect the next release at all, since it will have a much higher build number. I just need to tweak the build scripts to make sure it's getting the Subversion revision from the right place.