Hi Paul (2024.07.12_10:59:43_+)
> > > The weird thing is that I can run "python3 -m build", even with the
> > > options that pybuild introduces, outside the gbp buildpackage environment,
> > > and it seems that the package data is obtained using setuptools_scm. But
> > > as part of the gbp invo
Hi Thomas (2024.07.12_12:53:54_+)
> The way to deal with it, is simply something like this:
>
> export SETUPTOOLS_SCM_PRETEND_VERSION=$(shell dpkg-parsechangelog -SVersion
> | sed -e 's/^[[:digit:]]*://' -e 's/[-].*//' -e 's/~git.*//' -e 's/~/.0/' -e
> 's/+dfsg1//' -e 's/+ds1//' | head -n 1)
>
Hi Paul!
On Fri, Jul 12, 2024 at 12:59:43PM +0200, Paul Boddie wrote:
> The packaging is in git, yes. I suppose what I don't understand is the role
> of
> setuptools_scm in building a package for installation (or the construction of
> a binary package). A source package will aim to incorporate
On 7/12/24 12:59, Paul Boddie wrote:
I suppose what I don't understand is the role of
setuptools_scm in building a package for installation (or the construction of
a binary package).
It has no role in it. For us (package maintainers), it's just an
annoyance that we need to deal with. For Python
On Friday, 12 July 2024 07:17:27 CEST Stefano Rivera wrote:
> Hi Paul (2024.07.12_00:05:03_+)
>
> > The weird thing is that I can run "python3 -m build", even with the
> > options that pybuild introduces, outside the gbp buildpackage environment,
> > and it seems that the package data is obtai
* Stefano Rivera: " Re: pybuild and setuptools_scm" (Thu, 11 Jul 2024 23:01:14
+):
Hi Stefano,
> > I have been struggling to get some software packaged that relies on
> > setuptools_scm. It seems to effectively ignore the package data section in
> > a pyproject.toml file and to include a b
6 matches
Mail list logo
