Platformio repository for lvgl not updating

Bug (archived)
1

Description

The platformio library has an old version v7.1.0 of lvgl as the latest version in its repository. Newer versions do not seem to get published in the Platformio repository.

What MCU/Processor/Board and compiler are you using?

ESP32

What do you experience?

Platformio has a vast repository of libraries, which makes it very easy to use them in projects and automatically keep them up-to-date. The lvgl library is stuck at v7.1.0 for the last 3 months, while lv_drivers is up-to-date with v7.7.0.

What do you expect?

Have the newest version of lvgl available on the platformio repository.

Code to reproduce

Screenshot and/or video

If possible, add screenshots and/or videos about the current issue.
image

2

@kisvegabor i guess, that’s because version number of .json in HEAD goes ahead of git tags.

3

Fixed here: https://github.com/lvgl/lvgl/blob/master/library.json
Let’s how it works now.

4

2 days passed but still sitting on the old version.
Any ideas?

5

I’m not sure, but I have a feeling it is related to https://github.com/lvgl/lvgl/blob/release/v7/library.properties
The branch file still has a version=.7.0 entry. This seems to throw of platformio as it is expecting a Semantic Version.

I was struggling with my forked submodule too, until I changed that to ´version=7.7.0`. Then the project compiled again.

Maybe the platformio scraper is erroring out over that file too?

6

I think yes. Initially, lvgl was published with library.properties only, and i guess sraper remembered it as source of version. Those 2 files must be in sync.

7

The version string is broken in both library.properties and library.json files of the releases\v7 branch only:

name=lvgl
version=.7.0       // should be 7.7.0

More corroborating evidence is that the updates in the library seems to have stopped since the library.propertiesand library.json files have been edited:

image

image

v7.1.0 still had correct semver, but v7.7.0 is currently broken at version=.7.0.

8

Interesting… if I recall correctly PlatformIO only looks at master when checking our releases, but maybe the other branch is confusing it.

9

OK, I looked a bit further and have found this github commit from 4 months back
It might be related to that manual update of the repository? I posted a comment on that thread…

I only consume the libraries through platformio, but I don’t maintain any myself.

10

@fvanroie personally, until regisry is not very stable, you an use git links as i did: https://github.com/speedcontrols/ac_sc_grinder/blob/master/platformio.ini#L22-L26

11

@ivankravets replied on github. It seems the scraper takes a week to update repos automatically. He refreshed it though, and now the most current version 7.7.2 of lvgl is showing in the library. Great!

He also mentioned to do a manual push to update, instead of relying on the scraper. Maybe that can be incorporated into the CI pipeline?

12

This is feature of new registry, not compatible with old one. Need to learn how o use.

13

Probably we should make the PIO manual update part of the release script.

1 Like