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
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)
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
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)
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
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...
e 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)
ust right after a release
isn't the best time to start the work...
Cheers,
Thomas Goirand (zigo)
sition.
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)
someone have a clue what is happening?
>
> Cheers,
>
> J.Puydt
>
It looks fine to me, is there any issue?
Cheers,
Thomas Goirand (zigo)
t-packages \
dh_auto_test
endif
dh_install
override_dh_auto_test:
echo "Do nothing..."
I hope this helps,
Cheers,
Thomas Goirand (zigo)
has 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)
rball 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)
tar = False" in my ~/.gbp.conf, and it's all fine...
Cheers,
Thomas Goirand (zigo)
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
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 we can
decide what to do
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)
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
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)
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)
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)
gt;>> [..]
>> 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)
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)
;
> 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)
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)
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 wrote:
>&g
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)
ar, 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)
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.
Anyways,
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
* b4
* dehydrated-hook
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)
ust have added python-discogs-client to the RFS list :-)
Uploaded.
Thanks for your contribution to Debian.
Cheers,
Thomas Goirand (zigo)
ata would be a good idea.
Cheers,
Thomas Goirand (zigo)
all 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)
> 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't be
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)
iscard 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/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)
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 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 files are
re 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 marked with "copyright (c) yeah,
copyright-holder", and
ould we ask him to do such a massive
rebuilt? Or maybe you have other plans?
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)
> 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)
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"
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)
debian-python/2020/07/msg00057.html
>
>
> huh, this is a bit rude.
I don't agree Geert is being rude. Besides that, I know Geert (from
Debconfs) to be a nice and polite person that isn't rude with others.
Please assume good faith.
Thomas Goirand (zigo)
).
Otherwise, there's still Buster around for the next 4 years to come...
Cheers,
Thomas Goirand (zigo)
On 7/7/20 8:20 AM, Ondrej Novy wrote:
> Hi,
>
> po 6. 7. 2020 v 11:09 odesílatel Thomas Goirand <mailto:z...@debian.org>> napsal:
>
> This isn't about hating or loving pybuild. This is all about being able
> to control how this set of packages are bu
ld time: that's annoying and useless
(because at the end, only one of these versions will be in use).
Cheers,
Thomas Goirand (zigo)
kg-tools displays the output of "pip3 freeze", so I can do
report upstream more easily.
Each time, for all of these changes, I had to do a single unique change,
in a single place, without affecting other packages in the archive.
Hoping this explains well enough my choice, so that it mak
On 6/30/20 12:41 AM, Jeremy Stanley wrote:
> On 2020-06-29 23:55:49 +0200 (+0200), Thomas Goirand wrote:
> [...]
>> nodepool from OpenStack,
>
> Well, *formerly* from OpenStack, these days Nodepool is a component
> of the Zuul project gating system, which is developed by an
nch of package of the DPMT.
>
> Me too!
I shall resume packaging nodepool then...
Cheers,
Thomas Goirand (zigo)
into Salsa's CI to run it
automatically?
I'd very much would love to set this up, at least as a first
experimentation on a bunch of package of the DPMT.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
On 6/29/20 12:58 PM, Scott Kitterman wrote:
> On June 29, 2020 10:12:49 AM UTC, Thomas Goirand wrote:
>> On 6/29/20 8:34 AM, Ondrej Novy wrote:
>>> nope, this is not true. Using the newest debhelper compat level is
>>> recommended, see man page. There is no reason to __
man page. There is no reason to __not__ upgrade
> debhelper compat level. I will always upgrade debhelper in my packages
> to the newest debhelper as soon as possible. Please newer downgrade
> debhelper in my packages again without asking.
I don't agree this is best practice when backports are to be expected.
Cheers,
Thomas Goirand (zigo)
happen, is making sure that things don't break, and currently,
this isn't the case with this set of packages. And this isn't the first
time. So I'm proposing to take measures to make this stop. If you feel
it's a hostile take over, then ok we shall find another way. But then
What is your proposal so that it doesn't happen anymore then?
Cheers,
Thomas Goirand (zigo)
eam global-requirement pace. I'm confident
it's going to work well for me and the OpenStack team, but as well for
the rest of Debian.
Is anyone from the team opposing to this? If so, please explain the
drawbacks if the OpenStack team takes over.
Cheers,
Thomas Goirand (zigo)
On 6/25/20 3:13 AM, Louis-Philippe Véronneau wrote:
> Hello folks!
>
> As some of you might have seen, DebConf20 @ Home will be happening end
> of August.
>
> I was wondering if others would be interested in having a Python Team
> BoF to talk about ongoing work/issues (the Python 2 removals
On 5/27/20 11:26 AM, Dmitry Shachnev wrote:
> Hi all!
>
> On Tue, May 26, 2020 at 05:06:16PM -0400, Scott Talbert wrote:
>> On Tue, 26 May 2020, Thomas Goirand wrote:
>>> Hi there!
>>>
>>> Does any of you knows how to fix this bug?
>>>
Hi there!
Does any of you knows how to fix this bug?
https://bugs.debian.org/959558
Almost all of OpenStack can removed from Bullseye if not fixed in time,
so I tried to fix, but couldn't.
Cheers,
Thomas Goirand (zigo)
gree with it. Then you
can ask to join. If you're accepted, then you get write access to the
Git directly (and you can create new projects too).
Cheers,
Thomas Goirand (zigo)
t.
>>
>> https://salsa.debian.org/cloud-team/python-boto/-/merge_requests/1
>
> Could somebody from the cloud-team please merge and upload?
> I'm not a member of this team and can not do anything here.
>
> Thanks a lot
>
> Andreas.
>
Merged, built and uploaded.
Cheers,
Thomas Goirand (zigo)
ong
things, like Ubuntu was updating faster (which is wrong, as packages are
updated in Sid first). And many other things of that type. Isn't it
legitimate that I'm asking myself why? Shouldn't the Debian project try
to question its image?
Cheers,
Thomas Goirand (zigo)
On 5/15/20 10:42 PM, Scott Kitterman wrote:
> On Friday, May 15, 2020 4:36:52 PM EDT Thomas Goirand wrote:
>> On 5/15/20 7:09 PM, Scott Kitterman wrote:
>>> On Friday, May 15, 2020 12:55:48 PM EDT Thomas Goirand wrote:
>>>> On 5/15/20 5:43 PM, jojo wrote:
>>
On 5/15/20 7:09 PM, Scott Kitterman wrote:
> On Friday, May 15, 2020 12:55:48 PM EDT Thomas Goirand wrote:
>> On 5/15/20 5:43 PM, jojo wrote:
>>> Hi,
>>>
>>> I'd like to join the list because I think my software is a valuable
>>> addition to the debian
u intend to depend on it.
> Well enough already, let's discuss stuff when I am on the list :-)
You're talking about joining the list. But what about the Python APP
team? Do you intend to join it?
Thanks for your interest in Debian packaging and your intention to
package your app,
Cheers,
Thomas Goirand (zigo)
On 4/22/20 6:23 AM, Valentin Vidić wrote:
> On Tue, Apr 21, 2020 at 11:20:16PM +0200, Thomas Goirand wrote:
>> You can remove all of the python-oslo* from the list. The versions in
>> Experimental, which are the next version of OpenStack, are fixed. In 2
>> weeks of time, I
On 4/20/20 2:51 PM, peter green wrote:
> On 20/04/2020 08:57, Thomas Goirand wrote:
>>> Option 1: fix all four packages to be python 2 free.
>>>
>>> Option 2: Remove python2 stuff from traceback2, python-funcsigs and
>>> numba. Break the dependencies of
nsors like myself, just put your .dsc URL on *EVERY*
email follow-up... :)
Uploaded.
Thanks for your patience,
Thanks for your contribution to Debian,
Please be patient with FTP masters work,
Cheers,
Thomas Goirand (zigo)
h
dget and try yourself.
Cheers,
Thomas Goirand (zigo)
On 4/20/20 2:45 PM, Félix Sipma wrote:
> On 2020-04-20 12:06+0200, Thomas Goirand wrote:
>> I'm not sure, the doc still accounts for half of the package. But let's
>> pretend it's ok.
>
> We are talking about 80KB for the whole package. If it's not a blocker
> for you
On 4/20/20 11:13 AM, Félix Sipma wrote:
> On 2020-04-19 21:50+0200, Thomas Goirand wrote:
>> On 4/19/20 5:24 PM, Félix Sipma wrote:
>>> I hope I fixed the issues you found
>>
>> Not really... :(
>
> Let's try again, then...
>
>> Now the package
ers,
Thomas Goirand (zigo)
rom the build dependencies? Can't you set $clean_source = 0; in your
~/.sbuildrc instead?
I hope this helps,
Cheers,
Thomas Goirand (zigo)
;>
>>> There are only 25 packages that would need updating, and most of them
>>> are in DPMT/PAPT.
>>
>> Go for it.
>
> +1 from me too.
+1
Please publish a list here, so we can share the workload.
Cheers,
Thomas Goirand (zigo)
On 4/9/20 10:05 PM, PICCA Frederic-Emmanuel wrote:
> what about lintian brush ?
>
What's that?
Thomas
to
remove these. Maybe we could have some options for dh_sphinxdoc?
Thoughts anyone?
Cheers,
Thomas Goirand (zigo)
d as a result, which is kind of
controversial in itself). Piotr implemented something as well for
creating package to use pybuild, but I can't remember the name.
Cheers,
Thomas Goirand (zigo)
orial package.
It contains nice PDFs under /usr/share/doc/packaging-tutorial/
(translated in multiple languages). This is a very good start, IMO.
When you're done with that one, you may start reading the Debian Policy
Manual, which is probably a lot harder to read.
I hope this helps,
Cheers,
Thomas Goirand (zigo)
already use KGB.
>
> --
> Dmitry Shachnev
Hi Dmitry,
Thanks a lot for sharing, I've used this script to reconfigure all of
the OpenStack team's repos so that it logs with KGB in
#debian-openstack-commits. You made me save a lot of time! :)
Cheers,
Thomas Goirand (zigo)
On 3/30/20 11:44 AM, Andreas Tille wrote:
> I wonder whether we should take over python-boto into DPMT maintenance
> which would enable commits to Git way more easily.
I'd very much be in the favor of this, especially considering the
package history.
Cheers,
Thomas Goirand (zigo)
thoughts?
Cheers,
Thomas Goirand (zigo)
r in it. In other words, make upstream do:
mv src/tinyalign .
rmdir src
mv tests tinyalign
sed -i 's/packages=.*/packages=["tinyalign"],/' setup.py
Cheers,
Thomas Goirand (zigo)
On 2/11/20 4:45 PM, Sandro Tosi wrote:
>> In such case, could you provide me with the source package, rather than
>> just letting me try with Git? Maybe this is going to work then...
>
> whatever turns out to be, please ensure the package is buildable from
> the git repo. and matches what's going
n-free is not part of Debian, and the DFSG doesn't
apply there.
Cheers,
Thomas Goirand (zigo)
> I can't replicate this. I tried with cowbuilder/pbuilder and sbuild and
> the build completes fine on my systems.
>
> Håvard
In such case, could you provide me with the source package, rather than
just letting me try with Git? Maybe this is going to work then...
FYI, I'm just using plain sbuild with git-buildpackage.
Cheers,
Thomas Goirand (zigo)
(we use Dell LSI hardware RAID a lot), and my
colleagues would love to have this through the official channel, rather
than from your unofficial repository. Your thoughts?
Cheers,
Thomas Goirand (zigo)
_process_local_datas(sup, srcdir, destdir, force=force,
dump_json=dump_json)
File "scripts/import_cldr.py", line 435, in _process_local_datas
write_datafile(data_filename, data, dump_json=dump_json)
File "scripts/import_cldr.py", line 167, in write_datafile
with open(path, 'wb') as outfile:
IOError: [Errno 2] No such file or directory:
'/<>/babel/locale-data/root.dat'
Can you fix this?
Cheers,
Thomas Goirand (zigo)
d. So we have 2 choices:
1/ Fix python-xmlbuilder
2/ Get python-xmlbuilder and python-pbcommand removed from Debian.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
Hi,
I've seen that the package python2.7 is now of severity RC because of
the py2 removal process:
https://bugs.debian.org/937569
I wonder, is this a mistake done by the severity script? If so, are
there more mistakes?
Happy Chrismass,
Thomas Goirand (zigo)
ve a look and/or sponsor the package?
>
> Thanks a lot!
>
> Best regards
Well, remove the 2nd entry in debian/changelog: this package has never
been uploaded to Debian, so you are documenting something that never
happened in Debian.
Cheers,
Thomas Goirand (zigo)
more
cosmetic changes that I'm suggesting.
Cheers,
Thomas Goirand (zigo)
ve
Getmail stay on the next Ubuntu 20.04 LTS (Debian Bullseye is for in 2
years, so you may have more time for that one...).
Cheers,
Thomas Goirand (zigo)
On 11/13/19 3:31 PM, Iustin Pop wrote:
> On 2019-11-13 15:06:54, Thomas Goirand wrote:
>> On 11/12/19 4:37 PM, Osamu Aoki wrote:
>>> The related binary packages are available in 2 binary names (depending on
>>> release)
>>> getmail4 (version=4,5) popcon instal
So I see no reason to keep getmail
then. Maybe tell this to upstream, and they may think another time.
Cheers,
Thomas Goirand (zigo)
hopefully for
the better. Also, it's ok if we don't agree... :)
Cheers,
Thomas Goirand (zigo)
eady the current plain
reality (as the "unwritten policy" tells nobody else but you can touch
the package). So I don't see why anyone in the team would mind.
Cheers,
Thomas Goirand (zigo)
s when the Uploaders field contains the team address. It
only tells that it is possible to do that, not what it implies in our team.
Cheers,
Thomas Goirand (zigo)
ill come back on the table.
Thomas Goirand (zigo)
1 - 100 of 420 matches
Mail list logo
