Hello guys!
Could someone help me to find out the error of this package?
https://salsa.debian.org/nilsonfsilva/librosa/-/jobs/3528766
Thanks!
Nilson F. Silva
Hi,
Cannot be because of the i386 arch?
Cheers,
Emmanuel
On Thu, Nov 17, 2022 at 2:58 PM Nilson Silva
wrote:
> Hello guys!
>
> Could someone help me to find out the error of this package?
>
> https://salsa.debian.org/nilsonfsilva/librosa/-/jobs/3528766
>
> Thanks!
>
> Nilson F. Silva
>
>
>
>
: build package
Hello guys!
Could someone help me to find out the error of this package?
https://salsa.debian.org/nilsonfsilva/librosa/-/jobs/3528766
Thanks!
Nilson F. Silva
Hello Frederic,
please could you provide next time direct links to the VCS/Tracker of
your package, that prevents time to search for the correct package on my
or others people side. Also a speaking subject content is helping me to
decide if I want to spend time on taking a look, you've choose
> Hello Frederic,
Hello Carsten
> please could you provide next time direct links to the VCS/Tracker of
> your package, that prevents time to search for the correct package on my
> or others people side. Also a speaking subject content is helping me to
> decide if I want to spend time on takin
Hello Frederic,
Am 31.10.22 um 08:57 schrieb PICCA Frederic-Emmanuel:
I can build the package basically doing these modifications and by
adding the additional B-D package Scott did mention. Simply let
dh_sphinxdoc build the documentation and adding the additional needed
package dependencies.
[
On Monday, October 31, 2022 1:26:03 PM EDT Carsten Schoenert wrote:
> Hello Frederic,
>
> Am 31.10.22 um 08:57 schrieb PICCA Frederic-Emmanuel:
> >> I can build the package basically doing these modifications and by
> >> adding the additional B-D package Scott did mention. Simply let
> >> dh_sphin
thanks for your help.
I have one more question
I have this command from the previous build
{interpreter} setup.py build_man
how can I translate this with the new build systeme ?
On Tuesday, November 1, 2022 11:15:59 AM EDT PICCA Frederic-Emmanuel wrote:
> thanks for your help.
>
> I have one more question
>
> I have this command from the previous build
>
> {interpreter} setup.py build_man
>
> how can I translate this with the new build systeme ?
As far as I can see,
On Tuesday, November 1, 2022 2:42:22 PM EDT PICCA Frederic-Emmanuel wrote:
> > As far as I can see, the package doesn't ship any files in /usr/bin.
> > Why do you need to build man pages (I'm assuming that's what
> > that's for? More generically, what problem did that step in the
> > process solv
On Tuesday, November 1, 2022 2:48:12 PM EDT Scott Kitterman wrote:
> On Tuesday, November 1, 2022 2:42:22 PM EDT PICCA Frederic-Emmanuel wrote:
> > > As far as I can see, the package doesn't ship any files in
> > > /usr/bin.
> > > Why do you need to build man pages (I'm assuming that's what
> > > t
> As far as I can see, the package doesn't ship any files in /usr/bin.
> Why do
> you need to build man pages (I'm assuming that's what that's
> for? More
> generically, what problem did that step in the process solve that's not
> solved
> now?
this is for the pyfai package which I need to
On Tuesday, November 1, 2022 3:02:00 PM EDT PICCA Frederic-Emmanuel wrote:
> >It looks to me like the current pyproject.toml file for pyfai is not
> >sufficient>
> > to build the package, so I would tempted to keep what you have now.
>
> Due to the presence of this file, pybuild try to build using
>It looks to me like the current pyproject.toml file for pyfai is not
>sufficient
> to build the package, so I would tempted to keep what you have now.
Due to the presence of this file, pybuild try to build using the "new way"
instead of building with setup.py.
I do not know if other package a
On Tuesday, November 1, 2022 3:31:47 PM EDT PICCA Frederic-Emmanuel wrote:
> > I don't think it should do that, so we need to investigate. Where
> > can I find the updated packaging?
>
> I did not push the change right now, I will push once I solve this issue :).
>
> my opinion is that I should
> I don't think it should do that, so we need to investigate. Where can I
> find
> the updated packaging?
I did not push the change right now, I will push once I solve this issue :).
my opinion is that I should force via PYBUILD_SYSTEM=distutils
Fred
;/usr/bin/python3.10', '-m', 'pip',
'--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmppdpybvy1',
'--quiet', 'setuptools<60.0.0']' returned non-zero exit status 1.
- Mail
Ok, I understand better what is going on.
in pyproject.toml there is these lines.
[build-system]
requires = [
"wheel",
"setuptools<60.0.0",
"oldest-supported-numpy",
"scipy",
"sphinx",
"nbsphinx",
"silx>=0.10",
"Cython>=0.25"
]
indeed the setuptools < 60, can not
us 2
- Mail d’origine -
De: PICCA Frederic-Emmanuel
<frederic-emmanuel.pi...@synchrotron-soleil.fr>
À: Scott Kitterman <deb...@kitterman.com>
Cc: debian-python@lists.debian.org
Envoyé: Wed, 02 Nov 2022 09:03:45 +0100 (CET)
Objet: Re: build package xrayutilities - wheel and pip w
Hi Fred, Hi all other DD,
I am the upstream author of pyFAI and fabio, I wish to thank you for
taking care of the packaging of those software. I am aware there is an
issue with the usage of those software since they use numpy.distutils
(deprecated, to be removed in python3.12 and requires setuptoo
Hello, just for info.
I can confirm that the probleme was in the upstream build system, which was not
compatible with the setuptools > 60.
After patching the build system, I can confirm that without any change to the
rules files. It works out of the box.
So there is no issue in pybuild :)), or a
Hi,
as you might have noticed I finalised the preconditions to build
python-moto which is in salsa.d.o[1]. When trying to build I get:
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py test
running test
running egg_info
writing requirements to moto.egg-info/requi
- Mail original -
> De: "Andreas Tille"
> À: 777...@bugs.debian.org
> Cc: debian-python@lists.debian.org, "Debian Science List"
>
> Envoyé: Vendredi 2 Février 2018 09:16:55
> Objet: Preconditions for python-moto finished - help needed to build
Hi Andreas,
I checked the packaging, and my debuild ended up with an
error different from
> AttributeError: 'module' object has no attribute 'backport_assert_raises'
According to a quick investigation on this problem, I'm sure there
are still some missing B-Ds in control file.
With patch [1]
Hi Lumin,
On Tue, Feb 06, 2018 at 03:27:22PM +, Lumin wrote:
> I checked the packaging,
Thanks a lot!
> and my debuild ended up with an
> error different from
>
>> AttributeError: 'module' object has no attribute 'backport_assert_raises'
>
> According to a quick investigation on this p
Hi,
On 6 February 2018 at 15:56, Andreas Tille wrote:
> Would you mind pushing your patch directly? I do not see any advantage
> if I would proxy your patch. ;-)
Done.
> I admit up to know I have not checked this file but probably having
> these will help.
Then I believe it worth a try and w
Hi Lumin,
On Tue, Feb 06, 2018 at 03:27:22PM +, Lumin wrote:
> With patch [1] dpkg-buildpackage can go a bit further while building
> this package.
> See requirements-dev.txt. And new problems arose:
I've added python-flask to Build-Depends and can reproduce this issue:
> 1. $ make test #
27 matches
Mail list logo