Re: Future of pygame in Debian.
Hi, > […] tagged accordingly in the BTS […] Oops, you are right. There are still two FTBFS bugs I failed to tag (but not to fix). Cheers, Nik signature.asc Description: PGP signature
Re: Future of pygame in Debian.
Hi, > pygame in Debian testing is currently python2 only, I am sure I am not > alone in thinking this is not a good state of affairs given that pygame is > frequently used for introducing people to programming. > > pygame in sid has python3 support but is held back from migrating to > testing by three rc bugs. None of which have had any response from the > maintainer. > > One of those is a FTBFS with python 3.7 which is apparently fixed > upstream. So presumably the best thing to do about this one would be to > update the package to the new upstream. I may have a go at this myself > but I'm not an expert in python packaging so I don't know how well I will > do. > > The other two are testsuite failures on architectures where frankly I > doubt pygame has many users*. I may also take a look at these after the > new upstream version is dealt with but I don't think it's worth putting > huge amounts of effort into pygame on architectures where I doubt it has > any users and I equally don't think it should be allowed to block the > availability of python3-pygame in testing on architectures people do > actually care about, so if the root cause cannot be found quickly I would > propose either disabling the tests on these architectures or requesting > the ftpmasters remove the binaries. > > Anyone have any comments or suggestions? Yes. I am the maintainer whom you accuse of not maintaining the package. Sorry to say that, but all your assumptions are wrong - all of the bugs you mention are handled, tagged accordingly in the BTS, new uploads are prepared in the packaging repository, and fixing last issues for the upload are being coordinated with upstream, keeping the buster release schedule in mind: https://github.com/pygame/pygame/issues/543 Anything more I can do for you? Cheers, Nik signature.asc Description: PGP signature
Re: Future of pygame in Debian.
On Sat, Oct 13, 2018 at 9:36 AM peter green wrote: > The other two are testsuite failures on architectures where frankly I doubt > pygame has many users* ... > *Both are very expensive architectures driven by IBM. Raptor Computing sells (expensive but less than IBM) POWER9 desktops with GPUs so it is conceivable that someone might want to use pygame based games on ppc64el at some point. https://www.raptorcs.com/ -- bye, pabs https://wiki.debian.org/PaulWise
Future of pygame in Debian.
pygame in Debian testing is currently python2 only, I am sure I am not alone in thinking this is not a good state of affairs given that pygame is frequently used for introducing people to programming. pygame in sid has python3 support but is held back from migrating to testing by three rc bugs. None of which have had any response from the maintainer. One of those is a FTBFS with python 3.7 which is apparently fixed upstream. So presumably the best thing to do about this one would be to update the package to the new upstream. I may have a go at this myself but I'm not an expert in python packaging so I don't know how well I will do. The other two are testsuite failures on architectures where frankly I doubt pygame has many users*. I may also take a look at these after the new upstream version is dealt with but I don't think it's worth putting huge amounts of effort into pygame on architectures where I doubt it has any users and I equally don't think it should be allowed to block the availability of python3-pygame in testing on architectures people do actually care about, so if the root cause cannot be found quickly I would propose either disabling the tests on these architectures or requesting the ftpmasters remove the binaries. Anyone have any comments or suggestions? *Both are very expensive architectures driven by IBM.
Re: Joining DMPT and PAPT
Welcome! El vie., 12 de oct. de 2018 a la(s) 16:57, Ondrej Novy (n...@ondrej.org) escribió: > Hi, > > st 3. 10. 2018 v 12:39 odesílatel Peter Pentchev > napsal: > >> I find myself doing more and more Python work on my own, so I thought >> I might also contribute to the Debian packaging. The first benefit >> would be to bring my gitless package under the PAPT umbrella, but >> I also have a couple of Python modules (some of which I've written >> myself) as candidates for DPMT packaging. >> > > welcome :) > > -- > Best regards > Ondřej Nový > > Email: n...@ondrej.org > PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: joining PAPT
Welcome! El vie., 12 de oct. de 2018 a la(s) 16:57, Ondrej Novy (n...@ondrej.org) escribió: > Hi, > > pá 12. 10. 2018 v 17:15 odesílatel Félix Sipma > napsal: > >> I'm already a member of DPMT, but I'd like to join PAPT to put some of the >> packages I maintain there (todoman and khard, and I still plan to work on >> these), and help in at least khal packaging. >> > > welcome :) > > -- > Best regards > Ondřej Nový > > Email: n...@ondrej.org > PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: joining PAPT
Hi, pá 12. 10. 2018 v 17:15 odesílatel Félix Sipma napsal: > I'm already a member of DPMT, but I'd like to join PAPT to put some of the > packages I maintain there (todoman and khard, and I still plan to work on > these), and help in at least khal packaging. > welcome :) -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Joining DMPT and PAPT
Hi, st 3. 10. 2018 v 12:39 odesílatel Peter Pentchev napsal: > I find myself doing more and more Python work on my own, so I thought > I might also contribute to the Debian packaging. The first benefit > would be to bring my gitless package under the PAPT umbrella, but > I also have a couple of Python modules (some of which I've written > myself) as candidates for DPMT packaging. > welcome :) -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
You are right , I did not noticed, that setuptools was not part of the build dependencies...
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
[PICCA Frederic-Emmanuel, 2018-10-12] > to my opinion, the code is modify in place with 2to3. > So the code on the source after the configuration is already converted to > python3. > And during the build process, with python2 the code is copied as it in the > .pybuild place for python2 > with python3 we see that the RefactoringTool, does nothing, it means the code > is already converted to python3. try adding python3-setuptools to Build-Depends -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Re: Request to join DPMT & PAPT Team
Thanks a lot. On Fri, Oct 12, 2018 at 5:36 PM eamanu15 wrote: > Welcome! =D > > El vie., 12 de oct. de 2018 a la(s) 04:12, Ondrej Novy (n...@ondrej.org) > escribió: > >> Hi, >> >> so 6. 10. 2018 v 17:53 odesílatel Manas Kashyap < >> manaskashyapt...@gmail.com> napsal: >> >>> ... i am asked to join dpmt and papt team so i am requesting to take me >>> in the team . >>> >> >> welcome :) >> >> -- >> Best regards >> Ondřej Nový >> >> Email: n...@ondrej.org >> PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B >> >> > > -- > Arias Emmanuel > http://eamanu.com > Github/Gitlab; @eamanu > Debian: @eamanu-guest >
RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Hello Andreas, it seems to me that the problem is due to the 2to3 conversion. I looked at the first failure when you re-activate the unit test[1] to my opinion, the code is modify in place with 2to3. So the code on the source after the configuration is already converted to python3. And during the build process, with python2 the code is copied as it in the .pybuild place for python2 with python3 we see that the RefactoringTool, does nothing, it means the code is already converted to python3. So I guess that the pythoncode used for python2 is already the code modified for python3... this is why the code failed for the unit test. [1] https://salsa.debian.org/debian/python-uncertainties/-/jobs/53314
joining PAPT
Hi, I'm already a member of DPMT, but I'd like to join PAPT to put some of the packages I maintain there (todoman and khard, and I still plan to work on these), and help in at least khal packaging. I still agree to follow the team policy. My login on salsa is felix-guest. Cheers, signature.asc Description: PGP signature
RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Hello Andreas, during the test does it load the moduels from the source files or does it use the one under the build directory. Maybe there is a missmatch between python2 code and 2to3 python code targeting python3. did it helped ? Fred
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Andreas, > Before I discuss this with upstream I'd like to share another observation: > There is some 2to3 magic applied to the source code which has the effect > that Assuming it's upstream's 2to3 magic, then I would speak to them. Alas, I am new to this package too — good luck and I hope I was of some initial help. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Hi again,
On Fri, Oct 12, 2018 at 02:44:26PM +0200, Andreas Tille wrote:
> >
> > > > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line
> > > > 946, in
> > > > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
> >
> > Please always provide a minimal testcase, otherwise people have to do a
> > lot of work simply to get where you are..
>
> Hmmm, I've thought the "test case" I've given in my first mail, just
> doing
>
>from uncertainties import core
>
> would be sufficient.
>
> > Under Python 2.x, list(TO_SUPERSCRIPT.items()) is:
> >
> > [(43, '\xe2\x81\xba'),
> >(45, '\xe2\x81\xbb'),
> >(48, '\xe2\x81\xb0'),
> >[…]
> > ]
> >
> > ie. strings with a length of 3 whilst ord() takes a single char. These
> > should therefore be probably defined as:
> >
> > TO_SUPERSCRIPT = {
> > 0x2b: u'⁺',
> > 0x2d: u'⁻',
> > […]
> >
> > .. instead, but I haven't tested or confirmed or anythinged that; I'll
> > leave it with you and upstream.
>
> I will contact upstream but I wanted to hear the opinion of the
> Uploaders of this package.
Before I discuss this with upstream I'd like to share another observation:
There is some 2to3 magic applied to the source code which has the effect
that the original source code file which has
$ grep -A4 "^TO_SUPERSCRIPT = {" uncertainties/core.py
TO_SUPERSCRIPT = {
0x2b: u'⁺',
0x2d: u'⁻',
0x30: u'⁰',
0x31: u'¹',
is turned into
grep -A4 "^TO_SUPERSCRIPT = {" uncertainties/core.py
TO_SUPERSCRIPT = {
0x2b: '⁺',
0x2d: '⁻',
0x30: '⁰',
0x31: '¹',
inside the pbuilder environment. I hacked around with the following code:
+
+override_dh_auto_test:
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
+ # for some very strange reason the RefactoringTool breaks the definions
in TO_SUPERSCRIPT
+ find . -name core.py -exec sed -i "s/^\([[:space:]]\+0x[0-9a-f]\{2\}:
\)'/\1u'/" \{\} \;
+ dh_auto_test
+endif
which left me with other test suite failures. Since I'm totally new to
this package and I have no idea whether this is some Debian specific
build (I had some quite unfriendly conversation with lmfit-py
upstream[1]) so would like to make sure there is no Debian specific
issue first. (Disclaimer: I'm totally new to this package as well as
lmfit-py - a Debian Med package just depends from the latter and nobody
else seem to have free time cycles to care. So please excuse my
naivity.)
Kind regards
Andreas.
[1] https://github.com/lmfit/lmfit-py/issues/502
--
http://fam-tille.de
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Hi Chris,
On Fri, Oct 12, 2018 at 12:32:18PM +0100, Chris Lamb wrote:
>
> > > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line
> > > 946, in
> > > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
>
> Please always provide a minimal testcase, otherwise people have to do a
> lot of work simply to get where you are..
Hmmm, I've thought the "test case" I've given in my first mail, just
doing
from uncertainties import core
would be sufficient.
> Under Python 2.x, list(TO_SUPERSCRIPT.items()) is:
>
> [(43, '\xe2\x81\xba'),
>(45, '\xe2\x81\xbb'),
>(48, '\xe2\x81\xb0'),
>[…]
> ]
>
> ie. strings with a length of 3 whilst ord() takes a single char. These
> should therefore be probably defined as:
>
> TO_SUPERSCRIPT = {
> 0x2b: u'⁺',
> 0x2d: u'⁻',
> […]
>
> .. instead, but I haven't tested or confirmed or anythinged that; I'll
> leave it with you and upstream.
I will contact upstream but I wanted to hear the opinion of the
Uploaders of this package.
> I also couldn't help notice:
>
> Vcs-Browser: https://salsa.debian.org/debian/python-uncertainties
> Vcs-Git: https://salsa.debian.org/debian/python-uncertainties.git
>
> .. yet:
>
> Maintainer: Debian Python Modules Team
>
That's probably explained in my other mail I've wrongly sent to
python-modules-team list where it might have not been noticed by you. I
wanted the Uploaders confirm the move to DPMT and make sure they have
commit permissions before the repository is moved.
Kind regards
Andreas.
[1] https://lists.debian.org/debian-python/2018/10/msg00020.html
[2]
https://alioth-lists.debian.net/pipermail/python-modules-team/2018-October/050019.html
--
http://fam-tille.de
Re: Request to join DPMT & PAPT Team
Welcome! =D El vie., 12 de oct. de 2018 a la(s) 04:12, Ondrej Novy (n...@ondrej.org) escribió: > Hi, > > so 6. 10. 2018 v 17:53 odesílatel Manas Kashyap < > manaskashyapt...@gmail.com> napsal: > >> ... i am asked to join dpmt and papt team so i am requesting to take me >> in the team . >> > > welcome :) > > -- > Best regards > Ondřej Nový > > Email: n...@ondrej.org > PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: Joining DMPT and PAPT
Welcome Joseph! =) El vie., 12 de oct. de 2018 a la(s) 04:12, Ondrej Novy (n...@ondrej.org) escribió: > Hi, > > st 3. 10. 2018 v 5:51 odesílatel Joseph Herlant > napsal: > >> I'm already in there as aerostitch-guest but I just got my DD account >> so I'd like to migrate my access to my new account: aerostitch. >> > > done. > > -- > Best regards > Ondřej Nový > > Email: n...@ondrej.org > PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Andreas,
> > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946,
> > in
> > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
Please always provide a minimal testcase, otherwise people have to do a
lot of work simply to get where you are..
$ cat testcase.py
# coding=utf-8
TO_SUPERSCRIPT = {
0x2b: '⁺',
0x2d: '⁻',
0x30: '⁰',
0x31: '¹',
0x32: '²',
0x33: '³',
0x34: '⁴',
0x35: '⁵',
0x36: '⁶',
0x37: '⁷',
0x38: '⁸',
0x39: '⁹'
}
#! Python 2.7+ can use a dictionary comprehension instead:
FROM_SUPERSCRIPT = {
ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
$ python2 testcase.py
Traceback (most recent call last):
File "testcase.py", line 18, in
ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
File "testcase.py", line 18, in
ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
TypeError: ord() expected a character, but string of length 3 found
Under Python 2.x, list(TO_SUPERSCRIPT.items()) is:
[(43, '\xe2\x81\xba'),
(45, '\xe2\x81\xbb'),
(48, '\xe2\x81\xb0'),
[…]
]
ie. strings with a length of 3 whilst ord() takes a single char. These
should therefore be probably defined as:
TO_SUPERSCRIPT = {
0x2b: u'⁺',
0x2d: u'⁻',
[…]
.. instead, but I haven't tested or confirmed or anythinged that; I'll
leave it with you and upstream.
I also couldn't help notice:
Vcs-Browser: https://salsa.debian.org/debian/python-uncertainties
Vcs-Git: https://salsa.debian.org/debian/python-uncertainties.git
.. yet:
Maintainer: Debian Python Modules Team
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Hi again, I've now stumbled upon the `export PYBUILD_DISABLE=test` some Uploader had commited. This is now deactivated in Git[2]. Any idea how to get this working? Kind regards Andreas. [2] https://salsa.debian.org/debian/python-uncertainties On Fri, Oct 12, 2018 at 08:19:02AM +0200, Andreas Tille wrote: > Hi, > > I need help with an issue in python-uncertainties[2]. It only occures > with Python 2: > > $ python > Python 2.7.15+ (default, Aug 31 2018, 11:56:52) > [GCC 8.2.0] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> from uncertainties import core > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python2.7/dist-packages/uncertainties/__init__.py", line > 224, in > from .core import * > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946, in > > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())} > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946, in > > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())} > TypeError: ord() expected a character, but string of length 3 found > >>> > > With Python 3 everything is fine. > > Any idea what might be wrong? > > Please note that I commited a new upstream tarball to Git. It has the > same release version but pypi contains a totally different release > tarball than Github (different file site and different dirs). I was > told that the Github version works "better" but this specific error > occures for both. I'd recommend to use the current HEAD in Git anyway > since that version looks more "sensible" in some way. > > I would also love if someone would check whether dh_auto_test is working > correctly. I somehow see no sign that the test suite is executed - thus > the problem above seems to remain hidden. > > Kind regards and thanks for any help > > Andreas. > > On Thu, Oct 11, 2018 at 01:06:43PM +0200, Andreas Tille wrote: > > Hi, > > > > I'm working on bugs #906381 and #906419 of package lmfit-py which should > > be solved in the latest upstream version. As it is documented in the > > lmfit-py issue tracker[1] this latest version needs python-uncertainties > > >= 3.0 which was prepared by Federico in Git[2]. Since it did not build > > I fixed the build issues and did a team upload (if I understood David > > Paleino correctly team maintenance in DPMT is fine and thus I have set > > the team as maintainer - I hope this is fine with you. Since another > > upload will be needed (see below) I'm fine with reverting this) of the > > upstream source that was injected. > > > > According to lmfit-py upstream[3] there is some issue with the > > uncertainties release and it seems we are now dealing with the wrong > > code. I just want to let you know you about my past upload and that > > I intend to do another upload until that issue[3] is fixed. > > > > Kind regards > > > > Andreas. > > > > PS: I'd consider it sensible to move the Git repository of > > python-uncertainties from debian/ group on Salsa to > > python-team/modules if you agree but before doing so I'd love > > to hear some confirmation that this is OK and that all Uploaders > > are member of DPMT and are able to keep on commiting. > > > > > > [1] https://github.com/lmfit/lmfit-py/issues/502 > > [2] https://salsa.debian.org/debian/python-uncertainties > > [3] https://github.com/lmfit/lmfit-py/issues/502#issuecomment-428638278 > > > > -- > > http://fam-tille.de > > -- > http://fam-tille.de > > -- http://fam-tille.de
Re: Joining DMPT and PAPT
Hi, pá 12. 10. 2018 v 5:50 odesílatel Joseph Herlant napsal: > I was just double-checking that my mail went through. I realized I forgot > to switch the subscription to debian-python@ to my debian email from my > old one ;) > sorry for waiting, I was a bit busy. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Request to join DPMT & PAPT Team
Hi, so 6. 10. 2018 v 17:53 odesílatel Manas Kashyap napsal: > ... i am asked to join dpmt and papt team so i am requesting to take me in > the team . > welcome :) -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Joining DMPT and PAPT
Hi, st 3. 10. 2018 v 5:51 odesílatel Joseph Herlant napsal: > I'm already in there as aerostitch-guest but I just got my DD account > so I'd like to migrate my access to my new account: aerostitch. > done. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: joining PAPT
Hi, ne 30. 9. 2018 v 8:08 odesílatel napsal: > I develop an equation editor in python3 > (https://github.com/daniel-molina/visualequation) and I would like to > mantain it within the team. > welcome :) -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Updated python-uncertainties
Hi, I need help with an issue in python-uncertainties[2]. It only occures with Python 2: $ python Python 2.7.15+ (default, Aug 31 2018, 11:56:52) [GCC 8.2.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from uncertainties import core Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/uncertainties/__init__.py", line 224, in from .core import * File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946, in ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())} File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946, in ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())} TypeError: ord() expected a character, but string of length 3 found >>> With Python 3 everything is fine. Any idea what might be wrong? Please note that I commited a new upstream tarball to Git. It has the same release version but pypi contains a totally different release tarball than Github (different file site and different dirs). I was told that the Github version works "better" but this specific error occures for both. I'd recommend to use the current HEAD in Git anyway since that version looks more "sensible" in some way. I would also love if someone would check whether dh_auto_test is working correctly. I somehow see no sign that the test suite is executed - thus the problem above seems to remain hidden. Kind regards and thanks for any help Andreas. On Thu, Oct 11, 2018 at 01:06:43PM +0200, Andreas Tille wrote: > Hi, > > I'm working on bugs #906381 and #906419 of package lmfit-py which should > be solved in the latest upstream version. As it is documented in the > lmfit-py issue tracker[1] this latest version needs python-uncertainties > >= 3.0 which was prepared by Federico in Git[2]. Since it did not build > I fixed the build issues and did a team upload (if I understood David > Paleino correctly team maintenance in DPMT is fine and thus I have set > the team as maintainer - I hope this is fine with you. Since another > upload will be needed (see below) I'm fine with reverting this) of the > upstream source that was injected. > > According to lmfit-py upstream[3] there is some issue with the > uncertainties release and it seems we are now dealing with the wrong > code. I just want to let you know you about my past upload and that > I intend to do another upload until that issue[3] is fixed. > > Kind regards > > Andreas. > > PS: I'd consider it sensible to move the Git repository of > python-uncertainties from debian/ group on Salsa to > python-team/modules if you agree but before doing so I'd love > to hear some confirmation that this is OK and that all Uploaders > are member of DPMT and are able to keep on commiting. > > > [1] https://github.com/lmfit/lmfit-py/issues/502 > [2] https://salsa.debian.org/debian/python-uncertainties > [3] https://github.com/lmfit/lmfit-py/issues/502#issuecomment-428638278 > > -- > http://fam-tille.de -- http://fam-tille.de
