err, privacy breach*
On 14 July 2024 2:29:46 am UTC, weepingclown wrote:
>That'd be a nice thing to do. I believe there will already be
>privacy-beach-generic complaints by lintian. The worst part is that they end
>up appearing in all rdeps IIRC.
>
>Best,
>Ananthu
>
>
That'd be a nice thing to do. I believe there will already be
privacy-beach-generic complaints by lintian. The worst part is that they end up
appearing in all rdeps IIRC.
Best,
Ananthu
On 13 July 2024 10:19:43 pm UTC, Salvo Tomaselli wrote:
>Sorry for the OT, but should we consider patching
Hi,
Thanks for bringing up this topic. #1064952 is something that goes well with
this discussion. I myself am an active user of pypi2deb and also have a pending
MR, and I'd love to see the package getting more attention. I am also very much
willing to contribute to improve the tooling. It
Hi,
I do support the idea of an IRC meeting. although the availability of others
(maybe even myself) is something I can't comment on. But I still think trying
this out, at the very least, would be nice. Hopefully this can be a catalyst
for finishing up the 3.12 migration. 3.13 migration is
Hi,
The ruby team has a similar ruby-team/mentors namespace for newcomers. That
works quite nicely.
Best,
Ananthu
On 13 June 2024 11:13:33 am UTC, "Pierre-Elliott Bécue" wrote:
>Andrey Rakhmatullin wrote on 13/06/2024 at 12:48:36+0200:
>
>> On Thu, Jun 13, 2024 at 07:28:32AM +0100, Phil
Hi,
I have always found most of issues mentioned in the thread a welcome change
instead, and if anything the far superior ability of apt to automatically
remove all the installed dependencies in case of the removal of a package
compared to the complete inability of pip has always left me in
Hi,
As an addendum, there is also dedicated wiki pages[0] intended to be of help to
newcomers. Not saying that solves everything mentioned before, but it does help
quite a lot. As I understand it, the current problem we have is more about the
wiki being less organized than there not being
Hello Christian,
Without knowing what exactly fails for you, it is quite difficult to point out
anything. The steps documented in the wiki are supposed to be working.
That said, the current packaging go to tool for the DPT should be py2dsp, if
what you are working on is a python package. `apt
Hi,
I have done the last two updates of python-mongoengine, and it is a module that
we use regularly at our work . So I can adopt python-mongoengine.
Best,
Ananthu
On 22 March 2024 7:18:49 am UTC, "Håvard F. Aasen"
wrote:
>Hi,
>
>I intend to orphan two of my team maintained packages, I am
Hi Christian,
Improving docs is a very important thing, I appreciate your effort.
I quickly went through thr diff off your changes and it seems that you've
changed the wiki to mention that using quilt is not recommended. While gbp pq
is what the python team prefers indeed, the python team
While perfectly understanding the weak collaboration model reasoning, I've
still always found DPT as uploader and not maintainer rather absurd TBH. The
current go to tool (as I understand it) for python packaging, py2dsp, also
creates an initial packaging with team in uploaders section and the
Hello Debian Python Team,
I would like to request for DPT salsa access so that I can work on
packages with the Python Team. I have a few packages that I would like
to work on and am currently packaging yte and its dependency dpath-python.
My salsa username is weepingclown. I have read
12 matches
Mail list logo
