From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pylibfdt breakage
Date: Thu, 2 Feb 2023 09:00:05 -0600 [thread overview]
Message-ID: <CAL_Jsq+5ZrjQ5zVjjdmprW1+8nyTewXMb+0R+iyPG3J4xjkKPA@mail.gmail.com> (raw)
In-Reply-To: <CAL_Jsq+Lmkw51EAtBb62ET4xzChmTf6MGVq=pBjRoYY6Z+vQ6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Feb 2, 2023 at 8:15 AM Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>
> On Wed, Oct 19, 2022 at 3:09 AM David Gibson
> <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
> >
> > Hi Simon,
> >
> > I probably should have contacted you sooner about this. For some
> > time, I've been unable to compile and test the pylibfdt components on
> > my system (Fedora 36). I get this error:
> >
> > $ make
> > CHK version_gen.h
> > make[1]: Entering directory '/home/dwg/src/dtc'
> > CHK version_gen.h
> > PYMOD pylibfdt/_libfdt.so
> > /usr/lib/python3.10/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
> > warnings.warn(
> > /home/dwg/src/dtc/.eggs/setuptools_scm-7.0.5-py3.10.egg/setuptools_scm/version.py:84: UserWarning: tag 'path-ref-fixup-staging' no version found
>
> I think the problem is you have a git tag 'path-ref-fixup-staging'
> which doesn't match any version pattern (e.g. v1.0.0). The default
> pattern is:
>
> DEFAULT_TAG_REGEX =
> r"^(?:[\w-]+-)?(?P<version>[vV]?\d+(?:\.\d+){0,2}[^\+]*)(?:\+.*)?$"
>
> https://github.com/pypa/setuptools_scm/blob/main/src/setuptools_scm/config.py#L28
I tried adding non-version tags and still don't reproduce this.
What does this give you: python setup.py --version
Can you run the build with "SETUPTOOLS_SCM_DEBUG=1".
Rob
next prev parent reply other threads:[~2023-02-02 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 8:09 pylibfdt breakage David Gibson
2022-10-30 1:44 ` Simon Glass
[not found] ` <CAPnjgZ1SfQaBSmn-P6aGTNh0B1R2R4CbRXsRS9H4sF3VW4D=kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-21 3:29 ` David Gibson
2023-02-02 14:15 ` Rob Herring
[not found] ` <CAL_Jsq+Lmkw51EAtBb62ET4xzChmTf6MGVq=pBjRoYY6Z+vQ6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-02-02 15:00 ` Rob Herring [this message]
[not found] ` <CAL_Jsq+5ZrjQ5zVjjdmprW1+8nyTewXMb+0R+iyPG3J4xjkKPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-02-03 10:01 ` David Gibson
2023-02-03 10:17 ` David Gibson
2023-02-03 13:56 ` Rob Herring
[not found] ` <CAL_JsqLF-FGrMPb523MVbaJ=MkczNOaJTGg5zzpZfb3oEsv6+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-02-04 0:05 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL_Jsq+5ZrjQ5zVjjdmprW1+8nyTewXMb+0R+iyPG3J4xjkKPA@mail.gmail.com \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).