Menu

#175 Version information missing in header (Perl)

closed
None
0.7.1
2015-12-30
2015-12-15
No

Version reports at "not found" in header of Perl files generated.

Discussion

  • Carsten Grohmann

    Hi,

    What version do you use? 0.7.0 or 0.7.1 RC2?

    Regards,
    Carsten

     
  • Carsten Grohmann

    • assigned_to: Carsten Grohmann
     
  • Michael Everitt

    Michael Everitt - 2015-12-20

    That's 0.7.0 from the tar.gz. Running in a gentoo linux environment.
    Perl v5.20.2
    wxPython 2.8.12.1

     
  • Carsten Grohmann

    That's a known and fixed bug in wxGlade 0.7.0.

    Now you have three possibilities
    1. ignore the wrong version string
    2. rebuild the wxglade package and add the patch wxglade_0.7.0+.diff from ArchLinux https://aur.archlinux.org/cgit/aur.git/tree/?h=wxglade
    3. wait for wxGlade 0.7.1, which will be released within the next few days

    Regards,
    Carsten

     
  • Carsten Grohmann

    • status: open --> closed
     
  • Michael Everitt

    Michael Everitt - 2015-12-21

    No problem. Thanks for info.

     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    FYI: Not fixed in 0.7.1 release package.

     
  • Carsten Grohmann

    Hi,

    could you check if your package contains a file named "version.py"?

    And could you share the first 10 lines, if you start wxGlade from a console window?

    Thanks,
    Carsten

     
  • Carsten Grohmann

    • status: closed --> open
     
  • Carsten Grohmann

    • Affected Version: --> 0.7.1
     
  • Carsten Grohmann

    Hi Michael,

    I can't reproduce the issue at my system. I've extracted the official 0.7.1 tar.gz into an separate directory and run wxGlade out of this directory.

    The version number is shown correctly in the about dialog as well as in the generated perl code.

    Could you check if your package / wxGlade directory contains a file named "version.py"?
    And could you share the first 10 lines, if you start wxGlade from a console window?

    Regards,
    Carsten

     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    No version.py that I see .. which is odd, does it get created, or should it be in the tar (I'm using bz2, but shouldn't be different!).

    INFO    : Starting wxGlade version "not found" on Python 2.7.6
    INFO    : Base directory:             /var/tmp/portage/dev-util/wxglade-0.7.1/work/wxGlade-0.7.1
    INFO    : Documentation directory:    /var/tmp/portage/dev-util/wxglade-0.7.1/work/wxGlade-0.7.1/docs
    INFO    : Icons directory:            /var/tmp/portage/dev-util/wxglade-0.7.1/work/wxGlade-0.7.1/icons
    INFO    : Build-in widgets directory: /var/tmp/portage/dev-util/wxglade-0.7.1/work/wxGlade-0.7.1/widgets
    INFO    : Template directory:         /var/tmp/portage/dev-util/wxglade-0.7.1/work/wxGlade-0.7.1/templates
    INFO    : Credits file:               /var/tmp/portage/dev-util/wxglade-0.7.1/work/wxGlade-0.7.1/CREDITS.txt
    

    (/var/tmp/portage being staging area)

    Nope, definitely not in tar, nor created at run-time.

     

    Last edit: Michael Everitt 2015-12-30
  • Carsten Grohmann

    Hi Michael,

    the file should be generated automatically during "make release".

    I've added the file manually to the stable branch "WXG-BRANCH-VERSION_0_7_1". All released files are generated from the stable branch.

    I also checked the local copies of the release files and all contains the file "version.py". How do you generate your bz2 file?

    Maybe you can use the "official" tar.gz, gunzip and bzip2 the file.

    Regards,
    Carsten

     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    I'm using the bz2 from the 'Downloads' page, rather than any build scripts.
    Should it be in the root of that archive? I don't see it .......

     

    Last edit: Michael Everitt 2015-12-30
  • Michael Everitt

    Michael Everitt - 2015-12-30

    Ah, if I patch the xsl sytlesheet location, and run "make release" I get a whole different story.

    Not only that, but I think it will package better for gentoo if I do use that, since you're generating the /usr/lib/wxglade and /usr/bin/wxglade wrapper/launcher script.

    FYI, I've not got the version info in my docbook .. its just /usr/share/sgml/docbook/xsl-stylesheets/manpages/docbook.xsl .

     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    Oh, here we go .. my version.py contains "Version not found" lol ... see attached!

     
  • Carsten Grohmann

    If you download the bz2 file from the "Branches" tab especially from the stable branch "WXG-BRANCH-VERSION_0_7_1" it already contains the right version.py file. "make release" doesn't update an existing version.py file.

     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    Gotcha on that. That works fine for a personal installation.
    Since that's a unique solution, I can't really submit that to the Gentoo portage tree, so will see if I can write a patch or somesuch to 'fix' the release tar for this version.

     
  • Carsten Grohmann

    I suggest downloading the source code from the SF download location for packaging purposes.

    The stable branch will get updates too. Such updates will fix reported issues within the official release.

    Some packages of the old release 0.7.0 uses a hard-coded version number in config.py like:

    def get_version(suffix=True):
        """\
        Return the release string.
    
        The release string contains a suffix if wxGlade runs as standalone
        edition.
    
        @param suffix: Append suffix for standalone edition
        @type suffix:  bool
    
        @rtype: str
        """
        release = "0.7.1"
    
        if suffix and hasattr(sys, 'frozen'):
            release = '%s (standalone edition)' % release
    
        return release
    

    Do you agree with closing this bug?

     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    Thanks Carsten. Gentoo has a special case for 'bleeding edge' source revisions, and it makes sense to apply this to your source tree.
    If there's anything I can generally assist with in the distro sense, don't hesitate to drop me a msg.

    Feel free to close the bug, I think we've traced it best we can. Thanks again for your help.

     
  • Carsten Grohmann

    Just a last comment :-):

    Maybe you install the Python Mercurial packages and remove the version.py file. In this case wxGlade (as well as setup.py) would generate a version number based on the last commit id.

     
  • Carsten Grohmann

    • status: open --> closed
     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    I'm sure I can probably make that happen with the right config options! :) Cheers!

     
  • Carsten Grohmann

    I'm still thinking about your "bleeding edge" comment.

    One intention with the version file is to simplify updating the version number without changing other files. In your case you may really write your own file "version.py" with your version specifier "0.7.1" resp. "0.7.1+f9879cd5e391" on demand.

     
  • Michael Everitt

    Michael Everitt - 2015-12-30

    Definitely do-able. I don't think I've (yet) seen a distro which handles sources directly, making small file changes via VCS more practical. So, for now, we're faced with dealing with tar/etc. packages, although certain hosts (I believe) will dynamically generate a tarball from repo sources if configured. Food for thought!

     

Log in to post a comment.