OK thank you;  You have bested gpt-5.4 nano. That allowed the plugin to register.

Another error was fixed by gpt by replacing self.metadata_tree.header().setSectionResizeMode(QHeaderView.ResizeToContents)

with self.metadata_tree.header().setSectionResizeMode(
    QHeaderView.ResizeMode.Stretch
)
in the file hdf5_importer_dialog.py in the ~/.local/share/QGIS/QGIS4/profiles/default/python/plugins/hdf5_importer-main directory

Now I have a plugin screen displayed which I need to test.


On 6/26/26 12:31 AM, David Koster wrote:
Set |qgisMaximumVersion=4.99|  in your |metadata.txt und try again. |
||
|Greetings!
|
Am 26.06.2026 um 03:27 schrieb Don Harter via QGIS-User:

I worked with an ai bot (gpt 5.4 nano) trying to figure out why this plugin would install but not run do to an incompatible version message.

I had the bot summarize what we did:

Title: QGIS 4.0.3 incorrectly reports HDF5 Importer as incompatible (claims 3.4–3.99) despite plugin metadata lacking qgisMaximumVersion

Environment:

  * QGIS: 4.0.3-Norrköping (revision 70e40ae6e77)
  * OS/Package manager: Debian/Ubuntu (dpkg/apt purge used)
  * Plugin: “HDF5 Importer” (installed version 1.3.1 from GitHub ZIP;
    plugin code edited to use qgis.PyQt)
  * Profile: tested both existing and a brand-new QGIS profile; same
    behavior

Steps to reproduce:

 1. Install “HDF5 Importer” v1.3.1 from the GitHub ZIP into QGIS (via
    Plugins → manage/install from ZIP or local install, as applicable).
 2. Start QGIS 4.0.3 and open Plugins → Installed.
 3. Observe that QGIS shows an incompatibility warning: “This plugin
    is incompatible with this version of QGIS Plugin designed for
    QGIS 3.4 - 3.99”
 4. Even after removing and reinstalling the plugin and testing in a
    new profile, the same message appears.
 5. Inspect the installed plugin folder:
    
|~/.local/share/QGIS/QGIS4/profiles/<profile>/python/plugins/hdf5_importer-main/metadata.txt|
    The file contains only:
      * [general] name=HDF5 Importer qgisMinimumVersion=3.4 and does
        NOT include qgisMaximumVersion or any max version field.

What I expected:

  * Since the installed metadata.txt contains no upper bound, the
    plugin should not be blocked by QGIS as “designed for 3.4–3.99”
    on QGIS 4.0.3, or at least the blocking range should correspond
    to an actual declared maximum version.

What actually happens:

  * QGIS blocks the plugin based on an apparent compatibility range
    “3.4 - 3.99”, but that range cannot be found in the installed
    metadata.txt I inspected, and it persists across a new profile
    and after purging/reinstalling.

Additional troubleshooting performed:

  * Verified no other metadata.txt copies exist under the QGIS
    profile plugin directories.
  * Grepped for “3.4 - 3.99” and “Maximum” within the installed
    plugin and plugin working tree.
  * Installed/loaded in both existing and new QGIS profiles.
  * Purged older QGIS packages and reinstalled plugin.
  * Attempted to resolve earlier Qt binding crash (QHeaderView
    ResizeToContents / PyQt vs qgis.PyQt), but the incompatibility
    message blocks/complicates further testing.

Request:

  * Please advise where QGIS might be retrieving the “3.4 - 3.99”
    compatibility range when it is not present in the inspected
    metadata.txt, and/or confirm whether the plugin ZIP/package
    metadata includes an upper bound not represented in the installed
    metadata.txt.




_______________________________________________
QGIS-User mailing list
[email protected]
List info:https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
QGIS-User mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Reply via email to