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)
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)
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)
it this policy. I've heard many voices
telling that a package should either be in the team, or just not, and I
very much agree with this. This middle-ground makes no sense.
Cheers,
Thomas Goirand (zigo)
[1] I have no admin rights to add you, but welcome anyways...
/usr subdirs.
>
> yes, but that's something when 3.7 is removed.
>
> Matthias
Maybe that's a newbie question, sorry for this, but...
What happens when we upgrade to a minor Python 3 version? Do we get
everything recompiled? Is there a userland command to rebuild everything?
Cheers,
Thomas Goirand (zigo)
rational for #936307 (ie: claws-mail) and many
others either.
Cheers,
Thomas Goirand (zigo)
On 10/15/19 7:08 PM, Sandro Tosi wrote:
> On Tue, Oct 15, 2019 at 12:55 PM Thomas Goirand wrote:
>>
>> On 10/15/19 5:00 AM, Craig Small wrote:
>>>
>>>
>>> On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, >> <mailto:z...@debian.org>> wrote:
&
On 10/15/19 5:00 AM, Craig Small wrote:
>
>
> On Tue, 15 Oct. 2019, 1:04 pm Thomas Goirand, <mailto:z...@debian.org>> wrote:
>
> Please re-read the excellent contribution from Neil Williams
> in this thread, and explain again why we have a special case...
so let's not even consider that
> option.
Yes. Which is why we should raise severity of bugs to RC, and probably
even remove packages if we need to. Otherwise, this process will take
forever (ie: longer than a Debian release cycle).
Thomas Goirand (zigo)
On 10/14/19 11:05 PM, Craig Small wrote:
> Hi All,
> Just be careful with the bugs severity on complicated packages. I
> totally get the python only packages that produce a single binary, go
> for it for those.
>
> However consider the net-snmp python module. It's python 2 only and
> upstream
.
The issue is that, from a packaging standpoint, we cannot add a file if
it's not in the debian folder, because this makes change to the upstream
files. So, no choice...
Thomas Goirand (zigo)
ackage before the autorm. See the other thread I've
just started about this.
Cheers,
Thomas Goirand (zigo)
it feel
ok to raise the severity to serious, so that the package gets
auto-removed and then we can work on removing Python 2 from its
dependencies?
Cheers,
Thomas Goirand (zigo)
nd
come back to the list with the things corrected.
Cheers,
Thomas Goirand (zigo)
On 9/16/19 12:31 AM, Simon McVittie wrote:
> On Sun, 15 Sep 2019 at 23:39:46 +0200, Thomas Goirand wrote:
>> reverse-depends takes sometimes forever in Sid for a reason I
>> can't figure out. And if I'm not mistaking, that's the only tool we have
>> that can check
On 9/15/19 4:10 AM, Louis-Philippe Véronneau wrote:
> On 19-09-14 17 h 35, Thomas Goirand wrote:
>> On 9/13/19 11:08 PM, Louis-Philippe Véronneau wrote:
>>> On 19-09-13 05 h 57, Thomas Goirand wrote:
>>>> On 9/5/19 7:40 AM, Louis-Philippe Véronneau wrote:
>>&
ed them as Cc to this reply, in order to
warn the maintainers. I haven't done it for the BZR stuff, as obviously,
the package maintainer is aware now.
Again, sorry that it happened this way.
Cheers,
Thomas Goirand (zigo)
doing ANY work
on bzr anymore.
So I wonder: is it time to remove bazaar from Debian? Or is there any
vague plan to make it work with Python 3? If we are to remove it from
Debian, then we'd better do it ASAP.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
On 9/13/19 11:08 PM, Louis-Philippe Véronneau wrote:
> On 19-09-13 05 h 57, Thomas Goirand wrote:
>> On 9/5/19 7:40 AM, Louis-Philippe Véronneau wrote:
>>> Hello folks!
>>>
>>> I'd like to propose we start using Salsa CI for all the team packages. I
>>&g
provide decent runners?
Cheers,
Thomas Goirand (zigo)
On 9/12/19 9:22 AM, Michael Kesper wrote:
> Hi all,
>
> On 12.09.19 08:30, Thomas Goirand wrote:
>> I wont comment on the relative import ambiguity problem, as Ghislain
>> replied correctly. However, I do want to comment on 2to3.
>>
>> I generally recommend agains
ally written for OpenStack).
The advantage is that you'll get a source code that will work on both
Python 2 and 3. It's generally a way more easy to submit upstream, which
may not want to loose Python 2 compatibility.
Cheers,
Thomas Goirand (zigo)
ally written for OpenStack).
The advantage is that you'll get a source code that will work on both
Python 2 and 3. It's generally a way more easy to submit upstream, which
may not want to loose Python 2 compatibility.
Cheers,
Thomas Goirand (zigo)
things moving.
Please, let's generalize and see the whole picture. There will be A LOT
more cases like this one, and I don't think that waiting forever will
solve the situation. It is my opinion that we should set a kind of
policy (ie: wait for how long?) and then act...
Cheers,
Thomas Goirand
On 8/24/19 10:38 AM, Neil Williams wrote:
> How is that graph turned into a list of packages? It's too large to
> scan manually.
Well, I did it manually... and this is only a short list, as a
suggestion for a todo list, so nothing exhaustive... I very much would
welcome something automated.
BTW,
On 8/17/19 5:28 PM, Guðjón Guðjónsson wrote:
> Hi list
>
> I am upgrading my packages after the release of Buster and starting with
> eric.
>
> The get-orig-source target has been removed from the rules file and I know
> that
> is according to the current standard but I miss it :(
> In eric
, and didn't check if a package
is just a remaining curft, though it's hopefully still helpful as a TODO
list.
Cheers,
Thomas Goirand (zigo)
- python-libssh2
- python-pyip
- python-hunspell
- python-gpiv
- python-pyflot
- python-pyethash
- pydf
- pycmail
- python-libpcap
- python-pycallgraph
- pyblosxom
On 8/13/19 9:58 PM, Simon Josefsson wrote:
> Once python3-m2crypto is in Debian, I will port oz to python3.
>
> /Simon
Well, it's in unstable already...
Thomas Goirand (zigo)
On 8/13/19 3:30 PM, peter green wrote:
> IMO python-monotonic should be reinstated until it's reverse
> dependencies are sorted out.
There's now only oz, googleapi and duplicity. The last 2 both have Py3
support upstream in a newer version. Let's fix these, as I fixed all the
rest already. If
On 8/13/19 12:38 PM, peter green wrote:
> python-fasteners (has rdeps)
> python-oauth2client (via python-fasteners)
FYI, I removed Python 2 support from these 2 today! :)
Hopefully, Laszlo Boszormenyi (GCS) will do the work for googleapi, and
then we'll get another chain of Py2 removed. :)
all means, let's not play the dance of re-introducting Python 2 when
we can move forward on the right direction.
Thanks for taking the time to investigate this, this is very useful, and
I have to admit that, even though I know how to do the work, I am a bit
lost into knowing from were to begin. The release tracker is not very
helpful in this regard.
Cheers,
Thomas Goirand (zigo)
On 7/30/19 11:40 PM, Scott Talbert wrote:
> On Tue, 30 Jul 2019, Thomas Goirand wrote:
>> Do you mean, will python-foo be automatically removed from Sid/Testing,
>> after your upload? Normally yes, if nothing depends on it. And that's
>> probably harder to find o
's far from now...
Cheers,
Thomas Goirand (zigo)
on what criteria?
Also, if that application is important enough, why nobody worked on
porting it to Python 3?
Cheers,
Thomas Goirand (zigo)
On 7/9/19 12:22 AM, Scott Kitterman wrote:
> On Monday, July 8, 2019 5:45:17 PM EDT Thomas Goirand wrote:
>> How can I get debtree to use Sid instead of Buster (as I'd prefer to
>> keep this VM running Buster)? I could set this VM up and a cron job for
>> how long we need
On 7/9/19 12:05 AM, Rick Thomas wrote:
>
>
>> On Jul 8, 2019, at 2:45 PM, Thomas Goirand wrote:
>>
>> What I did so far:
>> debtree -R --rdeps-depth=100 python2.7 >py2.7.deps.dot
>> dot -Tsvg -o py2.7.deps.svg py2.7.deps.dot
>>
>> The res
On 7/8/19 6:28 PM, Stewart Ferguson wrote:
> On 2019-07-08 00:13:45, Thomas Goirand wrote:
>> On 7/7/19 5:31 PM, Matthias Klose wrote:
>>> you can start dropping it now, however please don't drop anything yet with
>>> reverse dependencies. So leaf packages first.
>
On 7/8/19 10:10 AM, Ansgar wrote:
> Thomas Goirand writes:
>> On 7/7/19 5:31 PM, Matthias Klose wrote:
>>> you can start dropping it now, however please don't drop anything yet with
>>> reverse dependencies. So leaf packages first.
>>
>> I'm sorry, but I thi
speed-up the Python 2
removal as much as possible, so that we can see what's remaining to be
done. If we don't do it fast, then we may end up in the very bad
situation you're describing.
Cheers,
Thomas Goirand (zigo)
on this simple case?
Last, a 2 years cycle to get rid of all traces of Python 2 *will* take
some time, maybe more than we can even think of, so we'd better take
some shortcuts if we can.
Cheers,
Thomas Goirand (zigo)
last):
> File "/usr/bin/pip3", line 9, in
> from pip import main
> ImportError: cannot import name 'main'
Hi,
The issue is probably pipenv breaking pip. If you try pip3 list before
installing pipenv, it does work.
Cheers,
Thomas Goirand (zigo)
r
version rather than the stretch one, as we've reworked it a lot.
Cheers,
Thomas Goirand (zigo)
Hi,
Clack Boylan, from the OpenStack infra team, wrote this patch:
https://github.com/pypa/pip/pull/6367/commits/f8292a304deebcf0e4cda2e40caa226c70030f11
which fixes this:
https://bugs.debian.org/837764
I do believe this should be part of Buster. Any objection?
Cheers,
Thomas Goirand (zigo)
give the feeling the "team"
is still very much dysfunctional,
Cheers,
Thomas Goirand (zigo)
ly. Often, it doesn't.
Cheers,
Thomas Goirand (zigo)
101 - 200 of 473 matches
Mail list logo
