7;s no need to wait 75 hours on this
case, as Jojo previously introduced himself in this list. He's been
doing good packaging work so far, and hopefully, his 3 packages will
soon make it to Debian.
Cheers,
Thomas Goirand (zigo)
On 7/16/20 6:03 PM, Sandro Tosi wrote:
> it is my opinion that that's what we should do: not ship `python` at
> all and have users/packagers/developers use either python2 or python3
> as needed, and not to reintroduce `python` at a later time.
I agree.
It's trivial for anyone to manually "fix" (o
Regards,
Thanks a lot for your work, on this specifically, and on the Python 2
removal in general.
I guess a lot of things are unlocked now. I wonder how we can help
fixing what's remaining. Please do share your thoughts on that.
Cheers,
Thomas Goirand (zigo)
t live in the OpenStack team namespace, but I don't have
enough rights to delete the Git repositories. Can someone do it for me
please?
There's 2 more for which I'm listed, I'll see if I can fix.
Cheers,
Thomas Goirand (zigo)
ervice, should we ask him to do such a massive
rebuilt? Or maybe you have other plans?
Cheers,
Thomas Goirand (zigo)
RS list as per what PBR builds. If
we are to care that much in OpenStack, then the license must be changed.
In Debian, quite the opposite, and like it or not (I personally don't
really feel the policy is right, but that's how it is), what Debian
cares is what's in the source code m
On 10/31/20 1:10 PM, Jeremy Stanley wrote:
> On 2020-10-31 12:03:50 +0100 (+0100), Thomas Goirand wrote:
> [...]
>> On 10/31/20 3:07 AM, Jeremy Stanley wrote:
>>> I have to agree, though in the upstream projects with which I'm
>>> involved, those generated file
ply invoking "pytest-3" is not enough, one should be using:
for pyvers in $$(py3versions -vr 2>/dev/null) ; do \
python$$pyvers -m pytest ; \
done
otherwise, only the default version of Python3 is tested, and we really
want to test with all available versions (so we get results whenever
we're transitioning to a new Python 3 version).
Cheers,
Thomas Goirand (zigo)
On 11/9/20 10:19 AM, Matthias Klose wrote:
> https://bugs.debian.org/973239 src:python-fixtures
Does anyone else than me think it's probably OK to just disable to 2
broken tests?
Cheers,
Thomas Goirand (zigo)
om github, and *then* only, I can
discard what's been downloaded, and fetch stuff from github with git.
Is there a solution here, so that uscan uses a repack script directly
without attempting to download first?
Cheers,
Thomas Goirand (zigo)
On 11/23/20 2:15 PM, nicoo wrote:
> Hi everyone!
>
> 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.
Cheers,
Thomas Goirand (zigo)
> why? that's not a requirement:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership
Because joining a team, putting packages in them, and enforcing strong
ownership, is not logic at all. I know you like to do this way, but this
shouldn
doc is small and could be integrated in python3-babel as
well).
If that's the way to go, then python3-babel needs a Breaks+Replaces:
python-babel-localedata.
Cheers,
Thomas Goirand (zigo)
ata would be a good idea.
Cheers,
Thomas Goirand (zigo)
> and just have added python-discogs-client to the RFS list :-)
Uploaded.
Thanks for your contribution to Debian.
Cheers,
Thomas Goirand (zigo)
>
> If anyone wants to try it, the git repository is up to date.
Hi,
Eventlet looks broken beyond just the unit tests. I did a deployment of
OpenStack on unstable, and there's lots of issues on absolutely all
daemons. Hopefully, I can fine time to investigate this next week.
Cheers,
Thomas Goirand (zigo)
nspython? Or will it break some other reverse-dependencies? Is there
another way to fix the current situation?
Cheers,
Thomas Goirand (zigo)
P.S: The current reverse-dependency tree is:
Reverse-Recommends
==
* 2ping
* calibre
* dnstwist
Reverse-Depends
===
* ansible
*
On 2/2/21 7:46 PM, Thomas Goirand wrote:
> Both Eventlet and DNSPython are monkey patching the standard SSL library
> in potentially conflicting ways
After checking, that's *NOT* the case. Though Eventlet is doing
monkey-patching of dnspython, in a possible not-compatible with 2.x.
Any
3-dev-full" or something similar, as
from the distribution perspective, we see them as developer use only.
Don't confuse our users so that they install something they don't need.
Hoping that what I wrote is making sense,
Cheers,
Thomas Goirand (zigo)
27;s not
for our users.
> If it doesn't include distutils, venv, lib2to3, etc. then it doesn't
> solve any problem we currently have, and we don't need it. The purpose
> is to provide a package that gives you the entire stdlib.
>
> SR
What I read from Elana, is that *upstream* think we have a problem. But
do we really have one? Or are we just being influenced by upstream who
is trying to impose a view we don't necessary share?
Cheers,
Thomas Goirand (zigo)
Hi,
Looks like once more I've been not able to express myself clearly enough
in the first message. Hopefully, what's bellow contain *all* of my
thoughts, and that it brings value to this thread.
On 2/12/21 9:30 AM, Raphael Hertzog wrote:
> On Fri, 12 Feb 2021, Thomas Goirand wro
g the list
of dependency you need, and the tooling would either fetch the Debian
package (if available) or through PyPi, and it would always work,
without ever needing to care about versions (here, from your side, with
pinning and version bounds), and without ever needing to isolate things
in a venv/chroot.
Cheers,
Thomas Goirand (zigo)
We had a discussion on the principle of the change, but nobody has
> responded to the policy wording yet.
>
> Anyone seconds / objections?
>
> SR
>
It's fine, thanks for working on this.
Cheers,
Thomas Goirand (zigo)
On 5/12/21 11:21 PM, Stefano Rivera wrote:
> Matthias Klose gave a presentation at the Python Language Summit on the
> Challenges packaging Python for a Linux distro.
> [..]
This looks great. Is there a video of it somewhere?
Cheers,
Thomas Goirand (zigo)
[..]
>> This looks great. Is there a video of it somewhere?
>
> No, there won't be videos published, only blog posts written.
>
> SR
Matthias, if you read this: you *MUST* make such a presentation at the
next debconf, *PLEASE* !!!
Cheers,
Thomas Goirand (zigo)
;re never doing "apt-get dist-upgrade", it means
your system is full of security issues that aren't getting fixed.
Hopefully, the computer system(s) you're talking about isn't connected
to internet, right?
Cheers,
Thomas Goirand (zigo)
ntime that would result is a huge risk,
> plus learning a new distro also compromises my effectiveness which
> also results in further lost income.
Then learn how to reproducibly build chroot and venvs.
> what i am saying is: this is serious - i am effectlvely financially
> trapped and critically dependent on the decisions that you make,
> even though i am not paying you money for the work that you do.
IMO, you've trapped yourself here... but there's exist strategies. :)
I sincerely hope you will find a solution that matches your need,
hopefully by continuing to use Debian.
Cheers,
Thomas Goirand (zigo)
ver, spawners, proxy, etc or does your target also include
> some work on the jupyter interfaces/core side?
>
> I wonder if it is time to have a distinct jupyter packaging team given
> the (perhaps concerningly?) growing size of this software stack [1].
We're talking about 2 dozen of Python packages. Do you really think
that's a lot?
Cheers,
Thomas Goirand (zigo)
On 6/12/21 10:20 PM, Louis-Philippe Véronneau wrote:
> Hey folks,
>
> The deadline to submit talks for DebConf21 is June 20th and I was
> thinking it would be a good idea to have a Python BoF, as we always do.
>
> Anyone opposed to the idea?
Thanks, go ahead! :)
Did you also register a BoF for
cat debian/source/options
extend-diff-ignore = "^[^/]*[.]egg-info/"
That's a way more simple, as sometimes, upstream ships an egg-info and
building *modifies* it (and then, nightmare starts...).
Just my 2 cents of experience... :)
Thomas Goirand (zigo)
a
good idea (also so that Piotr can tell his opinion).
Also Piotr, can I add myself as uploader for all of these?
Your thoughts?
Cheers,
Thomas Goirand (zigo)
P.S: I do believe that uploading to Experimental is harmless (when we're
not in freeze), so I may go ahead before getting a reply, and
On 9/18/21 3:02 PM, Thomas Goirand wrote:
> Dear Python Team, Dear Piotr,
>
> As I was packaging Cloudkitty (that is: OpenStack rating of resources,
> typically used in a public cloud) for the next Xena release, I went into
> this chain of dependency:
>
> cloudkitty: needs
even have
"pristine-tar = False" in my ~/.gbp.conf, and it's all fine...
Cheers,
Thomas Goirand (zigo)
eds to remember to explicitly
generate the tarball with "gbp export-orig", OR (preferred) directly
fetch the orig.tar.{gz,xz} from the Debian archive. If you forget, gbp
complains about it and stops building (that is, as long as you have the
option "no-create-orig = True" in your ~/.gbp.conf).
Cheers,
Thomas Goirand (zigo)
started to depend on
> libisal-dev, and this
> now is limited to the few archs isal supports. So it would be really
> nice if isal
> can build on more archs.
>
> Please do let me know.
>
> Nilesh
Hi,
Did you look into the source package? isal is written in assembly
language...
Cheers,
Thomas Goirand (zigo)
ython3/dist-packages \
dh_auto_test
endif
dh_install
override_dh_auto_test:
echo "Do nothing..."
I hope this helps,
Cheers,
Thomas Goirand (zigo)
> Does someone have a clue what is happening?
>
> Cheers,
>
> J.Puydt
>
It looks fine to me, is there any issue?
Cheers,
Thomas Goirand (zigo)
a
smoother transition.
Note that it's possible that for many packages mentioned, only removing
the dependency should be enough. Still, that's some work to do... :/
Other alternative would be: help with NMU fixes (or I can add any of you
in the OpenStack team if you need...).
Cheers,
Thomas Goirand (zigo)
..), but just right after a release
isn't the best time to start the work...
Cheers,
Thomas Goirand (zigo)
OST_ARCH, AFAIK there is no 100% reliable way to do this.
I would also advise to use DEB_HOST_ARCH... Maybe with some fallbacks if
you wish to upstream it?
Cheers,
Thomas Goirand (zigo)
we could do a mass bug filling for this. Your thoughts?
Cheers,
Thomas Goirand (zigo)
P.S: I'm not volunteering for doing it, just giving the idea...
On 11/11/21 1:33 PM, Dmitry Shachnev wrote:
> Hi Thomas!
>
> On Thu, Nov 11, 2021 at 11:04:10AM +0100, Thomas Goirand wrote:
>> On 10/24/21 3:24 PM, Dmitry Shachnev wrote:
>>> If anyone is still using nose (1.x), please port your packages to nose2,
>>> pure unitte
ssets have reverse dependencies.
I am therefore hereby proposing the removal of python-flask-script and
flask-assets from unstable/testing, which by the way will allow Flask to
migrate to Bookworm.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
ay yes. python-cryptography >= v3.4.6 is needed to update
> python-autobahn [1]. Thomas Goirand (in CC) said [2] he is already
> working on python-cryptography, thus it would be best to coordinate
> uploads with him.
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
know what is the minimum version of each
component for your application. However, running internal tests at build
time may help you to know.
I hope this helps,
Cheers,
Thomas Goirand (zigo)
On 1/17/22 18:47, Louis-Philippe Véronneau wrote:
Hey folks,
I'm following up on bug #1001677 [1] on the DPT's list to try to reach
consensus, as I think the Lintian tags that were created to fix this bug
are not recommending the proper thing.
As a TL;DR for those of you who don't want to read
reas.
[1]
https://salsa.debian.org/med-team/community/helper-scripts/-/blob/master/missing-autopkgtest
Hi Andreas,
It does help a lot. Thanks a lot for this.
We're really missing you in Prizren, btw.
Cheers,
Thomas Goirand (zigo)
RY, it's not a so bad idea... Hopefully, we can
take the decision to reverse if needed.
Cheers,
Thomas Goirand (zigo)
lease help fixing these.
Cheers,
Thomas Goirand (zigo)
nion that we should go ahead and
make 3.11 the default.
I'd be happy to have the opinion of the rest of the team, especially
Doko and Stefano.
Cheers,
Thomas Goirand (zigo)
On 11/22/22 10:59, Julian Gilbey wrote:
On Tue, Nov 22, 2022 at 09:22:05AM +0100, Thomas Goirand wrote:
this, 100 times
I very much don't agree. I think it's going pretty well, and the number of
breakage isn't high. We just need a little bit of effort to make it in go
r wait for upstream to sort bytecode and pydevd
and Piotr (and possibly upstream) to sort parso, or to mark them as
Python 3.10 only.
Well, hopefully for you, you'll get it fixed before next January, or we
go back to 3.10 only (or both?).
Cheers,
Thomas Goirand (zigo)
is hard, and IMO we
started this process a way too late. Hopefully, Trixie will be
nose-free! In the mean time, it is unfortunately my opinion that it's
too late for Bookworm and that we must keep Nose for one more release.
Cheers,
Thomas Goirand (zigo)
Julian
Hi Julian,
It's probably ok if it's a *TEMPORARY* solution until upstream fixes
everything in time for the release (which is months after the freeze).
The question is: do you believe this may happen for let's say next March?
Cheers,
Thomas Goirand (zigo)
erkzeug 2.2.2 rather
than Python 3.11.
Help would be greatly appreciated fixing this bug. Hopefully, I can get
this done during my holidays (and avoid any other work...).
Cheers,
Thomas Goirand (zigo)
On 12/15/22 16:18, Thomas Goirand wrote:
On 12/13/22 00:51, Graham Inggs wrote:
Dear Python Team
Looking at the current state of the 'adding Python 3.11 as a supported
version' transition [1], the tracker [2] shows only 12 red packages
(excluding unknowns and packages not in testing)
the side of breaking things that close
to a release, and would also feel it very painful if one of the above
bugs isn't fixed in time, I don't feel like you guys are giving good
point of argumentation, or a solution to improve the process. Doko
already explained that switching the interpreter (the hard way) is the
only viable way to find out the remaining bugs. Do you have a better
solution in mind?
Cheers,
Thomas Goirand (zigo)
OpenPGP_signature
Description: OpenPGP digital signature
e removed because of Python 3.11. Well, please consider that
it would also be very disappointing to *not* have Python 3.11 for those
who managed constantly fix issues for it.
The timing was exactly what was discussed during Debconf: it's very
annoying that this year, upstream Python release was one month late...
we're only trying to deal with it.
Cheers,
Thomas Goirand (zigo)
d that it
will spoil the whole release process.
I'm sad to read this. Hopefully, this is truth only for some of the
packages you care, and the vast majority of the packages are fine? I'm
unfortunately not in a good position to tell (I didn't run any survey of
broken packages...).
Cheers,
Thomas Goirand (zigo)
How about fixing the 3.11 issues if you hit them ? How about using Buster and
3.9 if 3.11 doesn't work (yet) for you ?
Thomas Goirand (zigo)
On Feb 5, 2023 11:38, Julian Gilbey wrote:
>
> Why is the current intention not to ship the python3.10 package in
> bookworm?
>
>
mpt to open merge requests
against the affected modules, to fix the situation.
Cheers,
Thomas Goirand (zigo)
ll, as this should not happen, IMO.
Now, I still think this is a minor issue... :)
Cheers,
Thomas Goirand (zigo)
to write
such a courteous message...).
Note that I am also planing a few changes, like the package is currently
using the pypi tarball, I'd like to switch to using tags from github and
probably other stuff.
Please let me know,
Cheers,
Thomas Goirand (zigo)
/88d40f1225de8f7b42413b56206b41a6155fcf09
Unfortunately, it doesn't apply on top of 4.4.12-2, which is the current
version of the package (in Bookworm, Unstable and Testing).
Would you be able to rebase your patch on top of 4.4.12-2? Then I'll do
the work to get this into Bookworm (and Unstable/Testing).
Cheers,
Thom
On 9/13/23 13:43, Adam Cecile wrote:
On 9/13/23 12:55, Thomas Goirand wrote:
On 9/12/23 18:16, Adam Cecile wrote:
Hello,
No hurry, I think we might want to wait for upstream to respond to my
PR regarding double awaitable fix.
It is indeed lextudio upstream that took over the PySNMP package
On 9/13/23 14:29, Vincent Bernat wrote:
On 2023-09-13 09:29, Thomas Goirand wrote:
OpenStack networking-generic-switch needs 4.1.2, from last August, so
I'm about to upload that version to Experimental right away. Since
you, Vincent, is listed in the Maintainer: field, and the team is
e: can you make your pull request against the new
Salsa repository?
Cheers,
Thomas Goirand (zigo)
ate. I take care
of too many packages already, I'd love if someone stepped in.
Cheers,
Thomas Goirand (zigo)
s can at least test and see if everything goes well with the
new packages, without destroying them. I also continue to have OpenStack
packages working this way, and I'm not destroying reverse dependencies
carelessly.
Please share your thoughts on how to do it,
Cheers,
Thomas Goirand (zigo)
g=1053134
ITP of simplemonitor: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016113
Sorry, I wont have time for this right now, but if nobody does it, feel
free to ping me in a week or 2.
Cheers,
Thomas Goirand (zigo)
like me, someone may wrongly close the
bugs after a successful rebuild.
Cheers,
Thomas Goirand (zigo)
On 10/31/23 13:27, Lucas Nussbaum wrote:
Hi Thomas,
On 31/10/23 at 13:08 +0100, Thomas Goirand wrote:
Hi,
I'm not really sure what's going on, but I saw many packages marked as RC
buggy with Sphinx 7.1, docutils 0.20, however, both are still in
Experimental, not in Unstabl
fine now. The only thing is
that the packages will produce a different doc package if rebuilt (ie:
new theme), but there's going to be another OpenStack release in 5
months, so it should be fine.
Cheers,
Thomas Goirand (zigo)
s I'm taking days off starting tomorrow morning),
but it looks like everything is fine now... :)
Cheers,
Thomas Goirand (zigo)
i Matthias,
Thanks a lot for all the work you're doing on the Python interpreter.
When 3.12 because an available version, it would help a lot to have
someone like Lucas Nusbaumm to rebuild all reverse dependencies of
Python. Is that something planned?
Cheers,
Thomas Goirand (zigo)
destroying everything at once...
Cheers,
Thomas Goirand (zigo)
of the package, and you're done. So it's quite easy to do.
As we removed Python 2.7 2 releases ago, it's probably a good time to
finish the transition... :)
Cheers,
Thomas Goirand (zigo)
bbi: please package
v2.10.0 and remove dependency on python3-six
For these, I'm planning to do them when Caracal is released (ie: this
spring), if you don't mind.
Cheers,
Thomas Goirand (zigo)
On 1/17/24 14:25, Alexandre Detiste wrote:
Le jeu. 11 janv. 2024 à 10:47, Thomas Goirand a écrit :
I'm busy with the (tentative-) removal of python3-unittest2.
unitest2 is an old version of what has become "unittest" in the
standard library
90% of dependencies are stale and on
way clearer.
So I'm 100% with you for the removal of this policy.
To everyone else in the team: please also state your opinion, so we can
make a collective decision.
Cheers,
Thomas Goirand (zigo)
hers also receive
this kind of demotivating message anymore.
Cheers,
Thomas Goirand (zigo)
e, is that this policy is not obvious at
all, and it's easy to either not understand it, or not know about it.
Cheers,
Thomas Goirand (zigo)
t a few
instances, that the tooling (py2dsp you wrote?) made him wrongly put the
team as uploader. There's porbably other cases as well.
Cheers,
Thomas Goirand (zigo)
On 2/28/24 12:44, Scott Kitterman wrote:
Everyone in Debian is already bound by the code of conduct already, so it seems
redundant to add it here again.
I agree.
Thomas
ds were the tiger of this policy change,
though we need to take a step back, and understand the policy was bad
anyways.
So indeed, we have read the same things, but have very different
perspectives. None of them are completely wrong, we simply have very
different feelings. And despite all of this, it's a good thing you also
agree to get rid of this part of this policy.
Cheers,
Thomas Goirand (zigo)
the said transitioning package. I very much hope we
all move into this direction, even if that means more work and follow-up
with reverse dependency maintainers.
Cheers,
Thomas Goirand (zigo)
that
sometimes, I just do the quick fix by myself in debian/ptaches, and
don't have enough energy to report or fix upstream, thinking that
upstream will hit the (python 3.x for example) bug themselves, and fix
anyways. :/
Cheers,
Thomas Goirand (zigo)
g, always with the same
thing, with the same kind of assignation of a reference the op progress
callback address.
I tried a few dumb things, but can't find out what to do to fix. Does
anyone know what's going on, and how I can patch Ceph to have rbd.pyx to
build?
Cheers,
Thomas Goirand (zigo)
On 3/3/24 21:08, Thomas Goirand wrote:
Hi,
I'm long overdue for an upload of Ceph 18.2.x in Unstable. I'm currently
stuck with the below build failure:
Error compiling Cython file:
...
"""
> read constructive arguments instead of silent leaving the team (in the
> sense of not informing the team mailing list about the leave).
Me too. But I'm not surprised.
Cheers,
Thomas Goirand (zigo)
probably also need to keep pydot in shape.
Cheers,
Thomas Goirand (zigo)
ll let you know my
progress (currently, my contextily package is empty... :/ not sure what
I'm doing wrong with pybuid again...).
Cheers,
Thomas Goirand (zigo)
and you're doing it in a timely manner. :)
Cheers,
Thomas Goirand (zigo)
On 3/15/24 13:52, Scott Kitterman wrote:
On March 15, 2024 7:19:16 AM UTC, Thomas Goirand wrote:
On 3/14/24 08:52, Andreas Tille wrote:
I would have prefered to
read constructive arguments instead of silent leaving the team (in the
sense of not informing the team mailing list about the
and used to convert all of OpenStack to python2 + 3 using six. Once it
has found all the things that may use six, you can manually convert to
*not* use six anymore. I did this multiple times, and it worked well for
me at least.
I hope this helps,
Cheers,
Thomas Goirand (zigo)
On 3/15/24 12:40, Thomas Goirand wrote:
On 3/15/24 10:59, Andreas Tille wrote:
Hi Timo,
Am Fri, Mar 15, 2024 at 09:50:39AM +0100 schrieb Timo Röhling:
* Julian Gilbey [2024-03-14 06:20]:
#1065198 O: networkx -- tool to create, manipulate and study
complex
networks language
I use this
* the
packages from one namespace to another, so that there's redirections,
rather than copying somewhere else and deleting. This can be done by a
simple ticket at:
https://salsa.debian.org/salsa/support
Or is it too late, and you already cloned, and don't want to bother?
Cheers,
pysnmp situation. I'm still
not sure what road it's going to take, but we'll have to act.
So at the end: I'm happy I left things untouched and did something else. ;)
Cheers,
Thomas Goirand (zigo)
On 3/27/24 14:31, Jeroen Ploemen wrote:
On Wed, 27 Mar 2024 00:33:15 +0100
Thomas Goirand wrote:
On 3/19/24 13:41, Jeroen Ploemen wrote:
Dear team admins,
please delete the following packages from the DPT namespace on
salsa:
cheetah
jaraco.classes
jaraco.collections
jaraco.context
On 3/29/24 21:18, Timo Röhling wrote:
Hi Thomas,
* Thomas Goirand [2024-03-17 23:09]:
Anyone is welcome to join, it's just that I'm using git tag workflow,
so it doesn't fit in the DPT, but that's the only thing.
I am not familiar with that workflow and could not find any
401 - 500 of 518 matches
Mail list logo
