thanks you all,
I added a MANIFEST.in file and create an entry point for the application script
I end up with this error
adding 'xrdutils-0.0.4.dist-info/licenses/LICENSE'
adding 'xrdutils-0.0.4.dist-info/METADATA'
adding 'xrdutils-0.0.4.dist-info/WHEEL'
adding 'xrdutils-0.0.4.dist-info/entry_
I found the culprite :)..
a malformed entry_point.
"toto.test" instead of "toto.test:main"
Is there a linter for the pyprojects file ?
Thanks for your help.
Fred
Hi PICCA (2025.06.12_09:12:58_+)
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.13 with
"installer" module
E: pybuild pybuild:389: build: plugin pyproject failed with:
dh_auto_build: error: pybuild --build -i python{version} -p 3.13 returned exit
code 13
make: *** [debi
On Jun 11, 2025 18:51, Stefano Rivera wrote:
>
> Hi thomas (2025.06.11_16:30:15_+)
> >As for the version, setuptools-scm understand an env var that you may set
> >with something like:
> >export SETUPTOOLS_SCM_PRETEND_VERSION=$(shell dpkg-parsechangelog
> >-something)
>
> You don't
On Jun 11, 2025 17:57, PICCA Frederic-Emmanuel
wrote:
>
> > This is a sitation where upstream tarballs are preferable to git.
>
> Yes but for now the package is only distributed via git...
>
> Even worse, it is use via a checkout and that's all.
>
> > If you use an sdist, the egg-inf
> Hi thomas (2025.06.11_16:30:15_+)
>>As for the version, setuptools-scm understand an env var that you may set with
>>something like:
>>export SETUPTOOLS_SCM_PRETEND_VERSION=$(shell dpkg-parsechangelog -something)
the same kind of things is availalbe also for hatchling-vcs ?
Hi thomas (2025.06.11_16:30:15_+)
As for the version, setuptools-scm understand an env var that you may set with
something like:
export SETUPTOOLS_SCM_PRETEND_VERSION=$(shell dpkg-parsechangelog -something)
You don't need to do that, pybuild does it for you.
Stefano
--
Stefano Rivera
h
Hi PICCA (2025.06.11_17:14:36_+)
Hi thomas (2025.06.11_16:30:15_+)
As for the version, setuptools-scm understand an env var that you may set with
something like:
export SETUPTOOLS_SCM_PRETEND_VERSION=$(shell dpkg-parsechangelog -something)
the same kind of things is availalbe also for
Hi PICCA (2025.06.11_15:37:48_+)
There is no information about the data file list...
It is SOURCES.txt, see for example #1052854.
I don't think setuptools-scm is even parsing it (I can't see any code
doing so), it must be setuptools parsing it, itself.
Stefano
--
Stefano Rivera
http:
> However, it seems the upstream build actually depends on setuptools-scm now,
> they (you? :)) don't use any other way to tell the build system about
> the data files - the *.png images, the *.rst documentation, etc..
> This... may be a problem if the package is not built out of a Git checkout
> w
> This is a sitation where upstream tarballs are preferable to git.
Yes but for now the package is only distributed via git...
Even worse, it is use via a checkout and that's all.
> If you use an sdist, the egg-info / dist-info in the sdist will contain
> a file list that setuptools-scm can use.
On Wed, Jun 11, 2025 at 03:35:54PM +, Stefano Rivera wrote:
> Hi PICCA (2025.06.11_15:10:53_+)
> > And indded via sbuild there is no .git directory so setuptools-scm do not
> > provide the list.
> >
> > Do we know how to deal with this at the pacakging level. the upstream is
> > using th
> The version number is in the very first line of debian/changelog.
Yes I can use this and extract the version number by myself.
reading this,
https://salsa.debian.org/python-team/packages/setuptools-scm/-/blob/master/debian/README.Debian?ref_type=heads
There is no information about the data
On Wed, Jun 11, 2025 at 05:44:07PM +0200, PICCA Frederic-Emmanuel wrote:
> > However, it seems the upstream build actually depends on setuptools-scm now,
> > they (you? :)) don't use any other way to tell the build system about
> > the data files - the *.png images, the *.rst documentation, etc..
>
On Wed, Jun 11, 2025 at 05:25:41PM +0200, Santiago Vila wrote:
> El 11/6/25 a las 17:10, PICCA Frederic-Emmanuel escribió:
> > It seems that this is due to setuptools-scm which provide the list of the
> > data during the dpkg-buildpackage.
>
> That's it. You can now add setuptools-scm to build-co
Hi PICCA (2025.06.11_15:10:53_+)
And indded via sbuild there is no .git directory so setuptools-scm do not
provide the list.
Do we know how to deal with this at the pacakging level. the upstream is using
the code from the git repository, so it is not affected by this issue...
This is a
setuptools-scm is also use in order to generate the version number.
Our packaging tools are dealing with this ?
there is no policy requirement to add build-conflicts.
Or maybe it is but most people believe they are not really useful
if we all use minimal chroots.
El 11/6/25 a las 17:27, PICCA Frederic-Emmanuel escribió:
setuptools-scm is also use in order to generate the version number.
Our packaging tools are dealing with this ?
The version number is in the very first line of debian/changelog.
It seems that this is due to setuptools-scm which provide the list of the data
during the dpkg-buildpackage.
taken from the doc of setuptools-scm ---
Additionally setuptools-scm provides setuptools with a list of files that are
managed by the SCM (i.e. it automatically adds all the SCM-managed
El 11/6/25 a las 17:10, PICCA Frederic-Emmanuel escribió:
It seems that this is due to setuptools-scm which provide the list of the data
during the dpkg-buildpackage.
That's it. You can now add setuptools-scm to build-conflicts if it makes you
happy.
It might help some people (for example, yo
El 11/6/25 a las 16:52, PICCA Frederic-Emmanuel escribió:
When using dpkg-buildpackage, try at least using a chroot containing
only build-essential packages and the build-dependencies.
both are using the python -m build method...
so the setuptools build system has different behaviour depending
> When using dpkg-buildpackage, try at least using a chroot containing
> only build-essential packages and the build-dependencies.
both are using the python -m build method...
so the setuptools build system has different behaviour depending on other
installed packages ?
Fred
El 11/6/25 a las 15:39, PICCA Frederic-Emmanuel escribió:
Now if I build the package within sbuild I get this file list.
[...]
And with a simple dpkg-buildpackage on unstable distribution.
[...]
When using dpkg-buildpackage, try at least using a chroot containing
only build-essential packages
24 matches
Mail list logo
