Hi,
I'm packaging "depthcharge-tools", a Python project of mine that manages
the ChromeOS bootloader to make Debian natively bootable on Chromebooks.
My sponsor already cloned it to the python-team/packages Salsa namespace
and uploaded it to NEW with the Python Team as Maintainer. I want to
join t
Dear list,
I have committed to salsa the new version of sphinxext-opengraph [1].
If someone could have a look, that would be great.
Thanks!
Best,
Chiara
[1] https://salsa.debian.org/python-team/packages/sphinxext-opengraph
Source: ganeti-testsuite
Version: 3.0.2-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
X-Debbugs-Cc: debian-python@lists.debian.org
Previously yaml.load did not require a loader to be specified:
load(stream, Loader=None)
Now it does (starting in pyyaml 6.0):
> 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
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
>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: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
> 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
> export SETUPTOOLS_USE_DISTUTILS=stdlib
>
> in debian/rules does make it build for me. Do you consider that a fix?
thanks! that worked indeed
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi
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
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 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,
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 ?
hi Francois,
I took a look at the gtg package put up for sponsorship in the Python
team:
* changelog:
+ multiple entries for revisions that did enter the archive (0.3.1-2
through 4) appear to have gone missing?
+ there's about a dozen open bugs against the old package, yet only
a single o
14 matches
Mail list logo
