On Saturday 12 November 2011 09:55:39 Kay Hayen wrote:
>
> I created an ITP for Nuitka here:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648489
I've been following Nuitka, and I think it's great to see how it has
progressed over time. Since I've been trying to package Shedskin for Debian
On Saturday 12 November 2011 22:50:13 Jakub Wilk wrote:
> * Paul Boddie , 2011-11-12, 15:08:
> >If Nuitka aims to be a Python alternative, shouldn't it use the
> >alternatives mechanism in Debian?
>
> We don't use alternatives for Python interpreters, for g
Hello,
As I mentioned in the thread concerning Nuitka, I've been trying for a while
to get Shedskin packaged for Debian, and I've sent the occasional RFS to the
Mentors list, but I'd be interested to know if anyone is interested in taking
this work further and/or sponsoring it. Here's the Mento
On Friday 21 September 2012 20:13:22 Yaroslav Halchenko wrote:
>
> eh -- I cannot recommend any specific tutorial, especially tailored toward
> Python (yet). Lucas' packaging-tutorial is quite nice but IMHO for 1/2 hour
> introduction into packaging tutorial should be more concise and more
> speci
On Thursday 27 September 2012 17:50:04 Paul Tagliamonte wrote:
> On Thu, Sep 27, 2012 at 08:51:37AM -0400, Yaroslav Halchenko wrote:
> > not a single comment... bad... I guess I need to work on the text
> > more if even hardcore Debian people do not feel 'moved' ;-)
>
> Well, i'll give my 2c as a p
On Friday 28 September 2012 00:23:10 Yaroslav Halchenko wrote:
> Thank you Paul ;-)
>
> Good comments -- once again, arguments seems to be oriented mostly
> toward developers... I guess I should explicitly guide the
> abstract more toward 'user-' and "sysadmin-" use cases: people
> in need to hav
Hello,
It has been quite some time since I contributed any packaging to Debian, but
in the last year or so I have been trying to put together some packaging for
MoinMoin 2. As many of you will be aware, MoinMoin (colloquially referenced as
"Moin" hereafter) is currently used by Debian for the D
On Friday, 18 August 2023 09:51:29 CEST Carles Pina i Estany wrote:
>
> I'm not a Debian developer but I have some experience on Salsa CI, so I
> thought that I might be able to help... but then I was confused by a
> specific part of the message:
>
> On 17 Aug 2023 at 17:1
On Friday, 18 August 2023 16:12:19 CEST Carles Pina i Estany wrote:
>
> For the jobs it is happening via
> https://salsa.debian.org/salsa-ci-team/pipeline/#using-automatically-built-
apt-repository
Reviewing this documentation is actually more helpful than I thought it would
be. I had noticed t
On Friday, 18 August 2023 18:21:00 CEST Andrey Rakhmatullin wrote:
> On Thu, Aug 17, 2023 at 05:10:08PM +0200, Paul Boddie wrote:
> > Here, it would seem that the most prudent approach is to use the Salsa CI
> > service instead of trying to get the test suite to run during the pa
On Friday, 18 August 2023 19:54:55 CEST Carles Pina i Estany wrote:
>
> Ha! I wasn't aware of the aptly option
> (https://salsa.debian.org/salsa-ci-team/pipeline/#using-automatically-built->
> apt-repository and SALSA_CI_DISABLE_APTLY=0).
> I think that I might have re-invented the wheel in a tin
On Saturday, 19 August 2023 20:32:59 CEST Carles Pina i Estany wrote:
>
> Quick answer for now...
And a very quick reply from me... :-)
[...]
> I don't know if a .asc files are allowed. Actually, from my
> .bash_history:
> ---
> wget -O- https://www.virtualbox.org/download/oracle_vbox_2016.asc
On Sunday, 20 August 2023 14:06:37 CEST Carles Pina i Estany wrote:
>
> Interesting approach, but if you could use the variables and ship the
> shell script it might reduce some duplication between jobs (if possible,
> I haven't look into too much detail in your case) and more importantly
> you mi
On Monday, 21 August 2023 15:01:26 CEST Carles Pina i Estany wrote:
>
> If you want, you can simplify more (it's not exactly the same, so it
> might or might not help). There is a way on GitLab to point to the
> latest build of a job. For example, you have the following URL for one
> of the git re
Hello,
A few weeks ago, I asked about techniques for making new packages available to
other new packages so that the autopkgtest job could be run successfully in a
pipeline in the Salsa CI environment. Eventually, this was made to work by
taking advantage of the aptly job defined in the standar
On Friday, 15 September 2023 16:33:25 CEST Philip Hands wrote:
>
> For another angle, see:
>
> https://salsa.debian.org/philh/user-setup/-/pipelines/576662
>
> In which I have a `harvest-repos` job that grabs artifacts from `build`
> jobs in other pipelines, and an `aptly-plus` job that's got a
Hello,
I would like to request membership of the Debian Python Team. For a while, I
have been working on a package for Shed Skin (shedskin) which is a compiler
for a dialect of Python.
I previously maintained a package for this software in the Python 2 era, and
since it has been made compatibl
On Friday, 29 March 2024 09:52:14 CET Carsten Schoenert wrote:
>
> Starting with Debian packaging isn't a easy thing and there is *not* the
> one way to do it right. And there are for sure hundreds of HowTos out
> there. You will need to try a few of them and chose in the end the
> workflow that f
On Friday, 29 March 2024 17:39:04 CET c.bu...@posteo.jp wrote:
>
> On 2024-03-29 16:23 Carsten Schoenert wrote:
> > You need to use "opts=mode=git, ...", see the man page of uscan.
>
> Are you sure. For example this watch file do not use "opts="
> https://sources.debian.org/src/backintime/1.4.3-
On Sunday, 31 March 2024 15:31:36 CEST c.bu...@posteo.jp wrote:
>
> Don't write and explain such things in emails. Save your time and
> resources. Write it into the wiki just one time and then you can link
> to it. You wrote it. I won't copy and paste your stuff. Ladies and
> Gentlemen please do e
On Wednesday, 3 April 2024 15:56:48 CEST Pierre-Elliott Bécue wrote:
>
> I've granted you developer access to the package subgroup. You can
> create a shedskin project here if you want.
Many thanks for giving me access! Would it make sense to move the existing
project into the Python Team's pack
On Wednesday, 3 April 2024 16:25:10 CEST Andrey Rakhmatullin wrote:
> On Wed, Apr 03, 2024 at 04:21:05PM +0200, Paul Boddie wrote:
> >
> > Many thanks for giving me access! Would it make sense to move the existing
> > project into the Python Team's packages colle
On Wednesday, 3 April 2024 16:51:33 CEST Andrey Rakhmatullin wrote:
>
> Then putting the repo in the team namespace makes sense.
OK. I will aim to do that.
> On Wed, Apr 03, 2024 at 04:48:44PM +0200, Paul Boddie wrote:
> > However, I did not presume that I could just set the Main
On Wednesday, 3 April 2024 19:03:44 CEST Pierre-Elliott Bécue wrote:
> Paul Boddie wrote on 03/04/2024 at 16:21:05+0200:
> >
> > Many thanks for giving me access! Would it make sense to move the existing
> > project into the Python Team's packages collection on
On Thursday, 4 April 2024 18:02:42 CEST Pierre-Elliott Bécue wrote:
>
> I've bumped your access to maintainer, let's try, and I'll downgrade
> when you're done.
The project has been transferred and now resides here:
https://salsa.debian.org/python-team/packages/shedskin
Many thanks once again!
On Sunday, 26 May 2024 03:33:09 CEST Ian Norton wrote:
> I am puzzled about some of the responses there, how can anyone expect to
> randomly update packages on the system using pip and not have it go wrong
> on any distribution? This is why things like pipenv exist.
Or whatever today's tool is cal
On Monday, 27 May 2024 04:07:34 CEST Scott Kitterman wrote:
>
> While there are technical concerns on both sides, socially I think the
> Python community isn't that interested in outside perspectives.
I managed to dig up these notes from the packaging summit at PyCon:
https://hackmd.io/@pradyuns
On Monday, 3 June 2024 16:27:29 CEST Donald Stufft wrote:
>
> In the interim the packaging toolchain evolved to the point that having
> distutils in the stdlib was no longer of general benefit, and in fact made
> things worse because people had grown accustomed to things like `from
> distutils imp
Package: shedskin
Version: 0.9.9
X-Debbugs-Cc: debian-python@lists.debian.org
After discussion on the Debian Python mailing list, the packaging repository
for this software now resides at the following location:
https://salsa.debian.org/python-team/packages/shedskin
Having updated the packaging
Hello,
I wonder if anyone can provide some advice about setuptools_scm interactions
with pybuild.
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 broader collec
On Friday, 12 July 2024 01:01:14 CEST Stefano Rivera wrote:
>
> Which source package is this?
This is the source for MoinMoin 2.0 which is currently unpackaged in Debian.
> Where did the source come from? Git or PyPI tarball?
It is actually an archive from the GitHub release page, integrated in
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
On Thursday, 18 July 2024 11:10:01 CEST Mathias Behrle wrote:
>
> I have no clue why this is working for you.
>
> I removed the patch, tried your proposal and the build just fails because
> setuptools-scm writes again a dev version to src/csb43/_version.py:
>
> https://salsa.debian.org/tryton-te
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 Monday, 2 December 2024 03:56:54 CET Sean Whitton wrote:
>
> The script in mailscripts that depends on python-pgpy,
> email-print-mime-structure, is a nice, well-documented piece of
> software, and it would be a great shame to lose it.
I had a look at this script, which I found here when doing
On Tuesday, 21 January 2025 15:53:24 CET Carsten Schoenert wrote:
>
> The size of the license text is rather short compared to the current
> version of PSF-2.0.
I presume that by PSF-2.0 you mean the licensing details found in debian/
copyright that largely reproduce the summary here:
https://do
36 matches
Mail list logo
