> Debian "py7zr" package has security issue CVE-2022-44900,
> and this issue affects Debian "calibre" package because "calibre" depends
> this "py7zr" module.
> https://tracker.debian.org/pkg/py7zr
>
> Please examine Debian bug report 1032091, and fix this issue.
>
On Mon, Feb 6, 2023 at 5:02 PM Pierre-Elliott Bécue wrote:
>
> Hans-Christoph Steiner wrote on 06/02/2023 at 22:35:44+0100:
>
> > paramiko 3.0.0 was released two weeks ago. Any reason to not upload
> > it now? It would be nice to get into bookworm.
why didnt you ask the maintainers of
On Wed, Jan 18, 2023 at 10:37 AM Andreas Tille wrote:
>
> Hi,
>
> when looking at bug #1026525 I intended to checkout mitmproxy
thanks, i was about to do the same (due to the implication to uvicorn
and the rest of the async packages depending on it)
> and realised
>
> $ apt showsrc mitmproxy |
thoughts from a concerned maintainer
On Wed, Dec 21, 2022 at 1:24 PM Matthias Klose wrote:
>
> while we have not an 100% agreement to go ahead, I think we should aim for
> 3.11.
>
> The following steps would be:
>
> - accept the current python3-defaults into
> testing (adding 3.11 as
i just uploaded multiplex_0.6.0-1 it's gonna reach the archive soon
On Mon, Dec 19, 2022 at 5:39 PM Marcel Partap
wrote:
>
> Hi deb-py,
> to simultanously write images of our debian-based live distro
> https://github.com/fsfw-dresden/usb-live-linux to USB pen drives, I've
> managed to create a
> >> My proposal as stated at the top is to start from now on to prepend
> >> `python` to all NEW source packages in DPT, with the option to rename
> >> existing packages at a later date.
> >>
> >> What are other team members' opinions on this?
> >
> > For packages that on contain a python
Proposal: the DPT will start adding a `python-` prefix to NEW source
packages names, unless the upstream project already contains it
AFAICT all other major languages ecosystems packaging teams use a
(semi?)mandatory tag to identify their source packages (results below
from a very quick look at
On Mon, Nov 21, 2022 at 12:03 PM Louis-Philippe Véronneau
wrote:
>
> On 2022-11-21 02 h 08, Julian Gilbey wrote:
> > I'm just flagging this up here, with a question about how we should
> > proceed. Certainly we are not ready to make Python 3.11 the default
> > Python version!!
>
> This is a
> 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
Hello,
with the recent upload of setuptools/65.3.0 (and following) in
unstable, numpy FTBFS[1]. The reason is that numpy build system (both
used internally and by other packages) customizes
setuptools/distutils.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020135
Upstream is
> Python 3.11 marks "mailcap" for removal in 3.13. The
> documentation speaks about "mimetypes" being a replacement,
> of sorts.
>
> However, I can't really see how "mimetypes" helps in
> replacing the functionality of "mailcap".
>
> Put another way: what is the suggested way of replacing that
>
> Well but that's the whole point of automated testing. There's no *need*
> to do it locally if it's already done by Salsa for you. What is already
> automated and working pretty well is:
>
> - amd64 build
> - i386 build
> - source build
> - autopkgtest
> - blhc
> - lintian
> - piuparts
> -
> Am 20.09.22 um 16:13 schrieb Emanuele Rocca:
> > Salsa CI is useful because it automatically performs binary/source builds,
> > arm64 crossbuilds, and it runs various pretty important tests such as
> > lintian,
> > piuparts, reproducible build testing, and more. It also runs autopkgtest in
> >
On Tue, Sep 20, 2022 at 4:33 AM Emanuele Rocca wrote:
> On 19/09 02:14, Sandro Tosi wrote:
> > what would the team get out of doing this?
>
> The way I see it, CI on Salsa is so useful that it should be enabled by
> default unless there are good reasons not to.
the way i
> I was wondering if it would make sense to enable CI/CD on Salsa for all
> projects owned by the Debian Python Team, or if there's any concern
> about scaling issues in terms of pipeline workers (or anything else
> really).
what would the team get out of doing this?
--
Sandro "morph" Tosi
My
> It's a salsa webhook:
> https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages
>
> We don't have tooling that automatically configures all the repos, but
> when we migrated to salsa, we set them all up for tagpending, and
> posting to #debian-python-changes on IRC
> I wonder whether you are able to reproduce the issue at your side since
> in one of your last mails you asked whether the new version might have
> fixed the issue. This might implicitly mean it works for you since I
> assume you fired up the command line at your side as well.
it never worked.
> No, the problem persists:
>
> $ py2dsp -v pystow
> D: py2dsp py2dsp:156: version: 3.20220707
> D: py2dsp py2dsp:157: ['/usr/bin/py2dsp', '-v', 'pystow']
> /usr/bin/py2dsp:163: DeprecationWarning: There is no current event loop
> loop = asyncio.get_event_loop()
> D: py2dsp py2dsp:44: args:
> Before I've sent my mail I also checked Git HEAD which was no change.
there was:
https://salsa.debian.org/python-team/tools/pypi2deb/-/commit/f9eda106f1514a1fff83fb3a8324817a91489879
> Are you sure thet the package version 3.20220721 contains the correct
> executables?
yes, i simply forgot
> $ py2dsp -v pystow
> D: py2dsp py2dsp:156: version: 3.20220707
> D: py2dsp py2dsp:157: ['/usr/bin/py2dsp', '-v', 'pystow']
> /usr/bin/py2dsp:163: DeprecationWarning: There is no current event loop
> loop = asyncio.get_event_loop()
> D: py2dsp py2dsp:44: args: Namespace(verbose=True,
On Tue, Jul 19, 2022 at 4:27 AM Thomas Goirand wrote:
>
> On 7/19/22 07:59, Andreas Tille wrote:
> > Hi Zigo,
> >
> > you asked me for a list of packages without autopkgtest sorted by popcon
> > value as we create it for Debian Med team also for Python team. I've
> > simply added it to the
Hello,
Piotr has kindly moved pypi2deb to salsa[1] and given me access to the
project so i was able to merge my changes and release[2] a new version
of this tool in Debian.
[1] https://salsa.debian.org/python-team/tools/pypi2deb
[2]
Hello Lucas,
the Debian Python Team is in the process of updating pytest to a new
upstream release. Given the substantial number of packages depending
on it, we'd like to leverage the mass rebuild infrastructure to build
the reverse dependencies against pytest/7.1.2-1 in experimental.
I've opened
> Sandro: you managed the numpy transition, it seems. What is involved
> in something like this? I would imagine something like:
>
> (1) Upload pytest 7.x to experimental
i took care of this just now, uploading pytest/7.1.2 to experimental
(and i've messed up the branches on salsa, so i've
> > I think this page includes debci results for experimental:
> >
> > https://release.debian.org/britney/pseudo-excuses-experimental.html
> >
> > It shows what would happen when migrating experimental to unstable.
>
> Oh wow, thanks! That's perfect. So we can upload the new pytest to
>
> I would suggest ratt-rebuilding all reverse dependencies. Could that be
> done?
there order of thousands rdeps, i dont think it's fair to ask any
individual contributor the time and resources to check that via ratt.
Something i've done in the past (f.e. with numpy and matplotlib) is
leveraging
> > I dont think it's a problem per se, but i also want to understand if
> > the time debian-python@ dedicates to solve your issues is well spent.
>
> I'd say it is well spent.
>
> Andreas is herding a lot of cattle for Debian (as in
> packages, or people, or mentees). He's inventor of Debian
>
?
thanks!
On Thu, Feb 17, 2022 at 12:39 PM Sandro Tosi wrote:
> Hello all,
> the question is essentially all in the subject line, and my answer is yes.
>
> I receive notifications for all MRs opened against DPT packages, and
> Janitor's are always pretty much ready to merge as is, and
Andreas,
> > Any hint would be welcome
>
> See: https://github.com/explosion/catalogue/issues/27
>
> TLDR: skip that test on Python 3.10 for now.
this seemed an easy enough issue that, with some common and expected
due diligence, you could have figured it out yourself: checking
upstream issue
> Sorry again. I recheck the #1007025 [0], it should be RFP tag.
> This is my misspelt in the first request email.
> So I think I can go to to work it :-)
OMG you're right! i guess morning coffee hadnt kicked in when first
replying. I would still contact anarcat before starting any work,
because
> >> My salsa account is vimerbf(but I do not know why it hint me
> >> @vimerbf-guest)
> >>
> >> I have read the document: [1] and understand and follow it.
> >
> >according to
> >https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#joining-the-team
> >you need to
Hello Bo,
> My name is Bo, and want to contribute to Debian. And I
> noticed the ITP[0] and want to help package it. Because
> python is my one of favorite program language also :-)
an ITP means someone else is already working on that package, so that
may not be the right first package for you.
> I need it to properly package an IRC bot designed for the
> DPT itself.
please share your ideas for such bot here, before installing it the
irc channels, thanks
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter:
> I however do not have enough powers to add you into
> the team.
that's good, because we have a procedure in place that perspective
team members need to follow to join the team:
https://wiki.debian.org/Teams/PythonTeam/HowToJoin and
> I admit I'm hesitating a bit for different reasons. While I agree that
> direct commits are better than MRs I found several DPT packages with
> very sensible changes in Git but no uploads following these. For
> instance fixing VCS fields and Maintainer name should be followed by an
> according
Hello all,
the question is essentially all in the subject line, and my answer is yes.
I receive notifications for all MRs opened against DPT packages, and
Janitor's are always pretty much ready to merge as is, and so i think
we should let Janitor commit directly to the team packages.
Jelmer is
> Or export SETUPTOOLS_SCM_PRETEND_VERSION.
> https://github.com/pypa/setuptools_scm#environment-variables
>
> pybuild does this for you.
i dont remember the exact details, but sometimes that doesnt work:
even just building the source package (which runs dh clean, which
invokes setup.py clean)
> I'd like other python team member's opinion on this, and I'm not eager
> to maintain that legacy package, as I tend to not want to maintain
> obsolete software. Still, I can do the initial work of creating it.
i wouldnt expect much maintenance needed tho: 0.8.4 is essentially
dead upstream, so
> I think the proper fix would be to ask people to move away from
> `py3versions -r` if there is no X-Python3-Version, and use`py3versions
> -s` instead.
>
> As such, I think we should ask the Lintian maintainers to:
>
> 1. Change the desc for tag declare-requested-python-versions-for-test to
>
>
> If they apt source their debian/control
> will have the obsolete Vcs-Browser information. I think there should at least
> be a tombstone there for them to understand where the team went.
since we moved these repos within salsa, they are actually being
redirected to the right repo location. I
> I intend to package paperless-ng.
>
> Many of its dependencies are packaged in Debian but in an older version.
> You can see the list at
> https://salsa.debian.org/mechtilde/paperless-ng/-/wikis/home
how did you come up with the list of packages that require updates? i
just checked one,
> > > Sandro, do you have any other packages in mind?
> >
> > too many to scan by-eyes only, so i planned on running some queries on
> > UDD to figure some other package out, but the udd-mirror is down, so
> > i'm going to provide a list (if any) later on.
>
> In general we are open to hand over
> Thus I moved mypy now and moved it to DPT[2]. Feel free to add yourself
> to Uploaders and upload with the new location.
thanks!
> Sandro, do you have any other packages in mind?
too many to scan by-eyes only, so i planned on running some queries on
UDD to figure some other package out, but
Andreas,
On Wed, Dec 22, 2021 at 1:42 PM Andreas Tille wrote:
>
> Am Wed, Dec 22, 2021 at 06:13:32PM +0100 schrieb Pierre-Elliott Bécue:
> >
> > Andreas Tille wrote on 21/12/2021 at 15:43:11+0100:
> >
> > > Ping? Could any admin of Debian Python Team help out? We can simply
> > > recreate the
> I'm in the process of writing a tool to uniform the repo configuration
> in python-team/package
>
> - add integration: Emails on push
> - remove integration Irker
> - add webhook: KGB (or edit to remove all the extra parameters set,
> which are the default values anyway)
> - add webhook:
> When we did the migration to git, there weren't good tools for managing
> the setup of the salsa repos (hooks, etc.) yet. I'd assume those exist
> now, we should check in with what other teams are doing. That stuff can
> all be fixed in one run of a tool, I'd assume.
yeah i figured that much,
Hello Chiara,
> I have committed to salsa a new version of sphinxext-opengraph running tests
> at the build time.
> There are no updates on upstream.
>
> It's not urgent, but if someone want to check my solution (as this is my
> first using autopkgtest)...
i dont think that's how you should
Hello Yago,
> I am the current maintainer of python-tabulate [1], and would like to
> join the team as I believe it makes more sense for the package to be
> under its roof. The goal is to prevent issues should I be unavailable
> in the future, but I will try continue maintaining it within the
Hello,
while working on something else[1], i noticed how many of the
repositories in the DPT salsa group are in poor shape:
* missing branches
* changes not pushed to salsa
* general misalignment in configuration/setup/organization
* many other small nuances
[1]
On Tue, Nov 23, 2021 at 10:40 PM Chiara Marmo wrote:
>
> Dear Sandro,
>
> thank you very much for your answer and your sponsoring.
>
>> If you want it to be sponsored,
>> please add a new entry to debian/changelog with a "source only
>> upload"-like text, set the suite to `unstable` (so not
i can sponsor this package, but...
> The package is tagged and ready for upload at
> https://salsa.debian.org/python-team/packages/sphinxext-opengraph
... that doesnt appear to be the case. If you want it to be sponsored,
please add a new entry to debian/changelog with a "source only
On Sun, Nov 14, 2021 at 8:52 PM Stefano Rivera wrote:
>
> Hi Sandro (2021.11.15_01:05:12_+)
> > > I filed https://github.com/Ousret/charset_normalizer/issues/138
> > > upstream.
> >
> > In the interest of moving things along, and while we wait for upstream
> > action on it, should we
> FWIW: $ grep charset-normalizer /srv/ftp-master.debian.org/log/2021-11
> 20211106022017|clean-queues|dak|move file to
> morgue|Incoming/REJECT|python-charset-normalizer_2.0.6-1_amd64.changes|/srv/ftp-master.debian.org/morgue/queues/2021/11/06
oh, didnt know we could search for that, thanks
>
Hello Dominik,
can you update the DPT on the status of python-charset-normalizer? it
used to be in NEW, but now i cant find it there and it's not in the
archive.
This package is needed at least by httpx, which cannot be upgraded to
its latest version, thus preventing a growing set of packages to
python-apt is not written nor maintained by this team, but rather
(from https://tracker.debian.org/pkg/python-apt) by the APT Dev team
and in particular by Julian Andres Klode (both in CC): please continue
the discussion with them
On Sun, Nov 7, 2021 at 6:21 PM Hunter Wittenborn
wrote:
>
> Hi!
-changes
I'm definitely no expert in autopkgtests, so if there's something to
improve, lemme know.
On Sun, Apr 25, 2021 at 12:22 AM Sandro Tosi wrote:
>
> Hello,
> recently i've been making some enhancements to py2dsp (part of
> pypi2deb[1] ); for those who dont know what that is, py2d
> I don't get why python-anyio is stuck ; I certainly didn't upload it
> without trying to build it, and I just tried again and there was no
> issue :
> https://buildd.debian.org/status/package.php?p=python-anyio
>
> Does someone have a clue what is happening?
it's marked as installed now, which
> I sometimes need to add or make updates to python packages. Currently, I
> just uploaded a newer upstream version of httpbin and I'd like to push
> the changes to the git repository, which resides in python-team/packages.
httpbin has been orphaned, so it appears as if this repo should be
moved
> That's an upstream bug then, and upstream should fix that and ship a complete
> source tarball.
>
> I always submit pull requests updating MANIFEST.in and until now, all
> upstreams have accepted them.
and that will require an upstream new release, which does not help
when you want/need to
> One note: I'd consider watching for PyPI instead of GitHub.
there was actually a recent discussion on this list, discouraging from
using PyPI in favor of github, since GH tarball usually contains docs,
tests, and other files useful when building from source, usually not
included in tarball
Please do report bugs in the BTS when there's a problem with a package
On Wed, Sep 29, 2021 at 10:32 AM Andreas Tille wrote:
>
> Hi,
>
> in the issue I filed against nipype I was asked to try to rebuild numpy
> and see whether this might make a diffence. So I tried
>
> dget
Hello Eberhard,
On Tue, Sep 28, 2021 at 12:10 PM Eberhard Beilharz wrote:
>
> Hi,
>
> I'm still looking for someone who'd be able and willing to upload the
> new version of sentry-python (1.4.2).
did you contact the current maintainer about this? Adding William to
the recipients list
> The
On Tue, Sep 21, 2021 at 5:00 PM Antonio Terceiro wrote:
>
> On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote:
> > > That's because gbp does not use pristine-tar by default, and
> > > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> &
On Mon, Sep 20, 2021 at 11:21 AM Andrey Rahmatullin wrote:
> On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote:
> > > That's because gbp does not use pristine-tar by default, and
> > > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
>
> That's because gbp does not use pristine-tar by default, and
> debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> fix that.
I dont think this is the right approach: the default options to work
on DPT packages should be in gbp default config file (or in another,
global,
> Now filed as
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pydbg-removal;users=debian-python@lists.debian.org
why "Severity: serious"? none of them violates the policy:
https://www.debian.org/Bugs/Developer#severities; please adjust to
normal or important. thanks
--
Sandro "morph" Tosi
Rajib,
thanks for your enthusiasm in learning python, but please note this
mailing list is dedicated to "Discussion of issues related to Python
on Debian systems with a stress on packaging standards. Therefore
relevant for maintainers of Python related packages.", while it
appears you have general
> After the upcoming release of bullseye, I plan to start uploading all
> packages that currently use Alioth to migrate them to Tracker (along
> with the other pending changes in the git repos).
progress for this work is now tracked at
https://github.com/sandrotosi/debian-python-team-tracker
Hello,
a long time ago, we decided to stop using Alioth for the team email
address in Maintainer/Uploaders fields, and onovy mass-committed this
change to our repo; several of our packages (736, according to [1])
are still using Alioth.
[1] https://lintian.debian.org/tags/python-teams-merged
On Tue, May 18, 2021 at 12:29 PM Roland Mas wrote:
> I just created a topic on discourse to announce my effort.
the link is https://discourse.jupyter.org/t/debian-packaging-effort/9240
for those who want to follow
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian:
On Sat, May 8, 2021 at 9:56 PM Emmanuel Arias wrote:
> On 5/8/21 10:37 PM, Sandro Tosi wrote:
> > On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias wrote:
> >> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi wrote:
> >>>> * poetry-core failing https://ci.
On Mon, Mar 15, 2021 at 10:29 AM Emmanuel Arias wrote:
> On Mon, Mar 15, 2021 at 4:22 AM Sandro Tosi wrote:
>>
>> > * poetry-core failing https://ci.debian.net/packages/p/poetry-core/
>>
>> are you handling this failure?
looks like this is fixed in git: do you
> > this solution also underestimates the in-progress migration towards
> > poetry and pyproject.toml, where `python3 setup.py sdist` is not
> > available.
>
> Where does the metadata come from for projects using these things?
that'd be pyproject.toml AFAIUI
the point i wanted to make is that it
> Right and thus I am wondering if we could work through this, somehow?
> That is, $something fetches the tarball, runs sdist or whatever, and
> then the py2dsp magic.
>
> P.S. I know this sounds a little ambitious but I believe this would
> really help, too.
i do not plan to implement such a
On Wed, May 5, 2021 at 2:58 PM Andrey Rahmatullin wrote:
>
> On Thu, May 06, 2021 at 12:08:06AM +0530, Utkarsh Gupta wrote:
> > However, I am running into an issue (or I guess I am just not doing it
> > correctly).
> > Whilst trying to package from the g/h source
> >
> > > or git repository (a directory) that one has already downloaded.
> >
> > i dont see how starting from a git repo is useful, can you expand?
>
> instead of generating a .dsc first and then importing it into a git
> repository, it's more logical to me to import an upstream tarball into a
> git
> It would be useful if it could also be run against a tarball
this is already supported (but in general by py2dsp and in the context
of --github), f.e.:
$ ./py2dsp --profile dpt --distribution unstable --revision 1 --gh
https://github.com/indygreg/python-zstandard
./zstandard_0.14.1.orig.tar.gz
Hello,
recently i've been making some enhancements to py2dsp (part of
pypi2deb[1] ); for those who dont know what that is, py2dsp is a tool
that, given a PyPI project, will create an (initial) Debian source
package.
[1] https://packages.qa.debian.org/p/pypi2deb.html
I've just finished a patch
> * poetry-core failing https://ci.debian.net/packages/p/poetry-core/
are you handling this failure?
> * python-cleo in review https://salsa.debian.org/python-team/packages/cleo I
> hope finished this week
> * poetry still in progress
> https://salsa.debian.org/python-team/packages/poetry ->
Hello Emmanuel,
> From the missing dependencies we have:
> * poetry-core in NEW [0]
> * pastel in NEW need for clikit [1]
> * pylev in NEW need for clikit [2]
> * crashtest has RFS need for clikit [3]
> * clikit is ready on salsa but waiting for crashtest before RFS [4]
> * cleo ready but waiting
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
Owner: Sandro Tosi
* Package name: pydata-sphinx-theme
Version : 0.5.0
Upstream Author : Joris Van den Bossche
* URL : https://github.com/pydata/pydata-sphinx
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org
X-Debbugs-Cc: debian-python@lists.debian.org
Owner: Sandro Tosi
* Package name: ppmd
Version : 0.3.3
Upstream Author : miur...@linux.com
* URL : https://github.com/miurahr/ppmd
* License
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org
X-Debbugs-Cc: debian-python@lists.debian.org
Owner: Sandro Tosi
* Package name: geventhttpclient
Version : 1.4.5
Upstream Author : Antonin Amand
* URL : http://github.com/gwik
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org
X-Debbugs-Cc: debian-python@lists.debian.org
Owner: Sandro Tosi
* Package name: flask-basicauth
Version : 0.2.0
Upstream Author : Janne Vanhala
* URL : https://github.com/jpvanhal/flask
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org
X-Debbugs-Cc: debian-python@lists.debian.org
Owner: Sandro Tosi
* Package name: locust
Version : 1.4.3
Upstream Author : Carl Byström, Jonatan Heyman
* URL : https://locust.io/
* License
+Steffen explicitly, given the team is not in Maintainer nor Uploaders
> How about renaming the current python3-louvain package to
> python3-community-louvain using a normal transition package.
that's incorrect: src:python-louvain builds a module called
`community` (that includes also a cli
> I would like to join DPT, I already maintain several packages under the DPT
> umbrella
how is this possible (maintaining packages in DPT without being a member)?
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter:
> > Added!
> >
> > Happy package maintenance :)
>
> Thanks <3
please name the project as the source package name, not "Easy Ansi"
https://salsa.debian.org/python-team/packages/easy-ansi; also
src:python-easy-ansi, the python- prefix is not strictly required --
anyhow, the salsa project name
> I injected a new tarball drained from Github. It seems to need lots of
> not yet packaged - I have no idea how to cope with this.
i dont understand what you're trying to say here; if it's that
diskcache requires modules/packages not present in debian yet, it's
simple: you need to package those
Andreas,
did you read the error before asking for help? i mean, it's literally
right there
On Mon, Jan 25, 2021 at 11:47 AM Andreas Tille wrote:
> ERROR: tox config file (either pyproject.toml, tox.ini, setup.cfg) not found
and that's because
Hello,
it looks like Barry (correct me if i'm wrong) set up
https://debian-python.readthedocs.io/en/latest/ but it has not been
updated in a while.
Do we know what's the status of this website, if we want to continue
to maintain it, or instead we should just consolidate onto
Package: wnpp
Severity: wishlist
Owner: Sandro Tosi
* Package name: python-multipart
Version : 0.0.5
Upstream Author : Andrew Dunham <>
* URL : http://github.com/andrew-d/python-multipart
* License : Apache
Programming Lang: Python
Descr
On Mon, Nov 23, 2020 at 6:50 PM Thomas Goirand wrote:
>
> On 11/23/20 10:10 PM, Sandro Tosi wrote:
> >>> First, an apology: it seems I misremembered being in the team, and
> >>> uploaded to
> >>> NEW a bunch of packages with the team in `Uploaders`.
&
> > First, an apology: it seems I misremembered being in the team, and uploaded
> > to
> > NEW a bunch of packages with the team in `Uploaders`.
>
> Please put the team as Maintainer, and yourself as Uploaders.
why? that's not a requirement:
>* Use git to generate upstream tarball, as the PyPi module doesn't include
> the test folder. Using the gen-orig-xz in debian/rules, as using the
> repack function of debian/watch doesn't make sense (why downloading a
> tarball that would be later on discarded? I'm open to a
> I'm looking for information about the work done by the Python Team for a
> talk to encourage the Cuban python community to collaborate in Debian.
why do you want to encourage people to contribute to a team you're not
part of, to which you never contributed to (at least that i could
quickly
attached the dd-list of the packages missing the pristine-tar branch (some
may have been moved/removed, but these are actual repos in DPT)
On Fri, Jul 10, 2020 at 12:38 AM Sandro Tosi wrote:
> Hello,
> i would like to propose a project to make sure our teams (DPMT/PAPT)
> repos
> New/correct address is:
> Maintainer: Debian Python Team
Was this discussed somewhere? i cant find references in the ml -- thanks
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi
To these days, this is still happening! can we finally get rid of
this? Piotr, it looks like you're the admin of the mailing list, can
you take care of it please? thanks!
On Mon, Jun 11, 2018 at 5:44 AM Ondrej Novy wrote:
>
> Hi,
>
> 2018-06-10 1:35 GMT+02:00 Sandro Tosi :
>>
argggh removed the wrong address, adding Nick
On Fri, Jul 31, 2020 at 1:27 PM Sandro Tosi wrote:
>
> >* d/control:
> > - Mark package python3-uflash-doc as M-A: foreign
>
> This -doc package doesnt follow the policy, of having a python- prefix
> and not a pytho
1 - 100 of 459 matches
Mail list logo
