Hi Gregory (2024.11.17_22:59:49_+)
> I would like to join the Debian Python Team to take care of "ansible-lint"
> package.
Added, welcome to the team.
And thanks for the work on MiniDebConf Toulouse, it was excellent!
Stefano
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
On Monday, 18 November 2024 16:57:49 CET c.bu...@posteo.jp wrote:
>
> To my understand that wasn't answered.
Yes, the collection of licences is something distinct from the copyright
information. In REUSE, the copyright information is maintained in a manifest
that should be compatible with the D
On Mon, Nov 18, 2024 at 03:57:49PM +, c.bu...@posteo.jp wrote:
> > > To my understand the "copyright" file is something Debian specific.
> > > This does not exist in my upstream project but is "generated" by my
> > > Debian
> > > Package Maintainer.
> >
> > Correct. Which is what you were aski
On Mon, Nov 18, 2024 at 04:07:32PM +0100, Ole Streicher wrote:
> >>Build log is f.e.
> >>https://salsa.debian.org/debian-astro-team/pybdsf/-/jobs/6612895
> > The problem is most likely caused by "find_package(F2PY)", which does
> > not take different Python versions into account [1].
>
> This is i
On Monday, November 18, 2024 8:57:49 AM MST c.bu...@posteo.jp wrote:
> Regarding the lintian tag am I assuming correct that Debian GNU/Linux
> does not care about a LICENSE file or LICENSES folder?
> So there is no real problem to have a LICENSES folder?
> The "copyright" file will exist (downstrea
Hello Andrey,
Thank you for the reply.
Am 18.11.2024 15:26 schrieb Andrey Rakhmatullin:
On Mon, Nov 18, 2024 at 01:41:34PM +, c.bu...@posteo.jp wrote:
To my understand the "copyright" file is something Debian specific.
This does not exist in my upstream project but is "generated" by my
Deb
Hi Timo,
Timo Röhling writes:
> * Ole Streicher [2024-11-18 13:40]:
>>Build log is f.e.
>>https://salsa.debian.org/debian-astro-team/pybdsf/-/jobs/6612895
> The problem is most likely caused by "find_package(F2PY)", which does
> not take different Python versions into account [1].
This is indee
On Mon, Nov 18, 2024 at 01:41:34PM +, c.bu...@posteo.jp wrote:
> > > To my understanding of the policy the license file of package should
> > > be
> > > installed into
> > >
> > > /usr/share/doc//LICENSE
> >
> > It's spelled: /usr/share/doc//copyright
>
> To my understand the "copyright"
Hi Ole,
* Ole Streicher [2024-11-18 13:40]:
Build log is f.e.
https://salsa.debian.org/debian-astro-team/pybdsf/-/jobs/6612895
The problem is most likely caused by "find_package(F2PY)", which
does not take different Python versions into account [1].
Debian ships with f2pyX.Y scripts for each
Hello Stefano,
thank you for your reply.
Am 18.11.2024 13:55 schrieb Stefano Rivera:
To my understanding of the policy the license file of package should
be
installed into
/usr/share/doc//LICENSE
It's spelled: /usr/share/doc//copyright
To my understand the "copyright" file is somethin
Hello,
I was not sure which list is appropriate for this question. Because of
that I try it here because I am quit familiar with this community.
To my understanding of the policy the license file of package should be
installed into
/usr/share/doc//LICENSE
How to handle it if a project
Hi,
I have a package (pybdsf) that currently fails to compile when both
Python 3.12 and 3.13 are installed (current situation). From the log:
8<-
I: pybuild plugin_pyproject:129: Building wheel for python3.13 with "build"
module
I: pybuild base:311: py
Hi c.buhtz (2024.11.18_12:31:01_+)
> I was not sure which list is appropriate for this question. Because of that
> I try it here because I am quit familiar with this community.
>
> To my understanding of the policy the license file of package should be
> installed into
>
> /usr/share/doc/
On 11/13/24 15:44, Stefano Rivera wrote:
Hi buhtz (2024.11.13_12:06:33_+)
This was discussed at the Python BoF at DebConf in ROK earlier this
year.
OK, nice to know that there was a discussion before. Did I missed the
announcement of the results of this discussion in this mailing list?
T
14 matches
Mail list logo
