After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656688 - Wrong version in info panel, help files partially untranslated
Wrong version in info panel, help files partially untranslated
Status: RESOLVED NOTABUG
Product: frogr
Classification: Other
Component: UI
0.6
Other Linux
: Normal normal
: ---
Assigned To: frogr maintainers
frogr maintainers
Depends on:
Blocks:
 
 
Reported: 2011-08-16 19:00 UTC by Mario Blättermann
Modified: 2011-08-18 10:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mario Blättermann 2011-08-16 19:00:16 UTC
Just compiled and installed Frogr 0.6 (see https://bugzilla.redhat.com/show_bug.cgi?id=708765#c67). All works fine so far, but the info panel still shows the version number "0.6~unreleased". Moreover, the help files don't reflect my latest changes in Git (before releasing 0.6, actually). Would be nice to fix it and roll a 0.6.1 bugfix release.
Comment 1 Mario Sánchez Prada 2011-08-16 21:30:53 UTC
Hi Mario,

Might sound a silly question but... where are you getting the code from? Both the tarball and the git commit tagged as RELEASE_0.6 do not show that "~unreleased" suffix in the about dialog. Actually that is one of the few changes I always do with the "release commit" whenever a new version is out.

e.g, see the commit for release 0.6:

http://git.gnome.org/browse/frogr/commit/?id=4bc6bfb6664f1bcdbbcde24811219a960ad4be12

Also, I have reviewed the three tarballs (xz, bzip2 and gz) and they seem to be ok as well. 

About the help files, I also don't understand what's happening... I see this is your last commit in frogr before the release: 

http://git.gnome.org/browse/frogr/commit/?id=46e4d76c36e067b004078b89a2c3788775fa08ea

... and if I check the tarball I see the changes in there as well


Maybe you're checking out the last commit from master? Or perhaps I'm doing something wrong, in which case I'm ok with releasing a new version asap (this Friday, if possible)
Comment 2 Mario Blättermann 2011-08-18 10:16:14 UTC
Sorry for the blurb... The bug was in my own system. I've installed a pre-version of Frogr 0.6 in /usr/local, and the shell had preferred that binary to the binary from the final 0.6 rpm. After removing the appropriate files, all is OK again.
Comment 3 Mario Sánchez Prada 2011-08-18 10:42:06 UTC
Good to see you sorted it out! :)