Right, tried that for one of the failing recipes (python3-zwave-me-ws):

UPSTREAM_CHECK_URI="https://pypi.org/simple/zwave-me-ws";
UPSTREAM_CHECK_REGEX="zwave-me-ws-(?P<pver>(\d+[\.\-_]*)+).(tar\.gz|tgz|zip|tar\.bz2)"

Then the problem is clear: UPSTREAM_CHECK_REGEX takes PN as the first
argument, but since these are python recipes and the default there is
to use a '_' as a separator these are fixed in all the Python recipes
via adjusting 'PYPI_PACKAGE' to ensure that there is adherence to both
Yocto with '-' separator and Python with '_' separator. If I adjust
the UPSTREAM_CHECK_REGEX to:

UPSTREAM_CHECK_REGEX =
"${PYPI_PACKAGE}-(?P<pver>(\d+[\.\-_]*)+).(tar\.gz|tgz|zip|tar\.bz2)"

It finds a match perfectly.

Well these were two problems I would never have found without your
help both of you thanks.

One last question: in the upgrade-helper.conf file. What is expected
in the 'layerdir' variable? A relative path? The documentation is a
bit lacking there.

Tom

On Mon, Feb 17, 2025 at 8:42 PM Alexander Kanavin
<alex.kana...@gmail.com> wrote:
>
> If upstream version check doesn't return sensible values, run 'bitbake
> -e recipename', and look for UPSTREAM_CHECK_URI and
> UPSTREAM_CHECK_REGEX. What do they contain, and does the regex match
> what is available when opening the uri?
>
> Alex
>
> On Mon, 17 Feb 2025 at 20:26, Tom Geelen <t.f.g.gee...@gmail.com> wrote:
> >
> > Well I checked with python3-zwave-me-ws
> > (https://github.com/meta-homeassistant/meta-homeassistant/blob/main/recipes-devtools/python/python3-zwave-me-ws_0.4.3.bb)
> > with the proposed command and the latest version is empty.
> > Adding the recipe maintainer here does not change anything.
> >
> > NOTE: Starting bitbake server...
> > Loading cache: 100%
> > |#########################################################################################################################################################################################################################################|
> > Time: 0:00:00
> > Loaded 5028 entries from dependency cache.
> > Parsing recipes: 100%
> > |#######################################################################################################################################################################################################################################|
> > Time: 0:00:00
> > Parsing of 2998 .bb files complete (2996 cached, 2 parsed). 5026
> > targets, 295 skipped, 0 masked, 0 errors.
> > --2025-02-17 19:14:49--  https://pypi.org/simple/zwave-me-ws
> > Resolving pypi.org (pypi.org)... 151.101.0.223, 151.101.64.223,
> > 151.101.128.223, ...
> > Connecting to pypi.org (pypi.org)|151.101.0.223|:443... connected.
> > HTTP request sent, awaiting response... 301 Moved Permanently
> > Location: https://pypi.org/simple/zwave-me-ws/ [following]
> > --2025-02-17 19:14:49--  https://pypi.org/simple/zwave-me-ws/
> > Reusing existing connection to pypi.org:443.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 39845 (39K) [text/html]
> > Saving to: ‘/tmp/wget-index-cpaiwajr/wget-listing-nzx5eu24’
> >
> >
> > 2025-02-17 19:14:49 (6.80 MB/s) -
> > ‘/tmp/wget-index-cpaiwajr/wget-listing-nzx5eu24’ saved [39845/39845]
> >
> > INFO: Current version: 0.4.3
> > INFO: Latest version:
> >
> > On the other hand: adding the recipe maintainer here: python3-zigpy
> > (https://github.com/meta-homeassistant/meta-homeassistant/blob/main/recipes-devtools/python/python3-zigpy_0.74.0.bb)
> > does actually fix the issue for this recipe.
> >
> > Am I missing something else still Alexander?
> >
> > On Mon, Feb 17, 2025 at 7:58 PM Alexander Kanavin
> > <alex.kana...@gmail.com> wrote:
> > >
> > > For auh to work, upstream version check needs to function properly and 
> > > quite often it doesn’t because no one ensured that when writing the 
> > > recipe. Can you show the recipe and the output of ‘devtool latest-version 
> > > recipename’ ?
> > >
> > > Alex
> > >
> > > On Mon 17. Feb 2025 at 19.09, Tom Geelen <t.f.g.gee...@gmail.com> wrote:
> > >>
> > >> Hi all,
> > >>
> > >> I am currently trying to set up AUH locally in order to ease the
> > >> maintenance of the layer I'm maintaining (meta-homeassistant).
> > >> I have followed the steps given here
> > >> https://docs.yoctoproject.org/dev-manual/upgrading-recipes.html and
> > >> have configured it to parse all the recipes in my layer (99% python
> > >> based recipes).
> > >>
> > >> Now I have a problem. It correctly parses all recipes, however it
> > >> finds no upgrade candidates. This is strange as I know some are in
> > >> need of an upgrade, and a newer version is available on pypi for
> > >> instance. Moreover I get quite some skips with the following error:
> > >>
> > >> Skip package meta-homeassistant/python3-hass-nabucasa (status =
> > >> UNKNOWN_BROKEN, current version = 0.87.0, next version = 0.80.0)
> > >>
> > >> Where does it get the 'next version' value from as the latest version
> > >> upstream is 0.92.0.
> > >> I might have misconfigured something. I used the default
> > >> upgrade-helper.conf with the following additions:
> > >>
> > >> layer_mode=yes
> > >> layer_name=meta-homeassistant
> > >> layer_dir=BUILDDIR/../sources/meta-homeassistant
> > >> layer_machines=qemux86-64
> > >>
> > >> Thanks in advance,
> > >>
> > >> Tom
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64826): https://lists.yoctoproject.org/g/yocto/message/64826
Mute This Topic: https://lists.yoctoproject.org/mt/111236531/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to