Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
On Wed 2018-02-21 21:27:09 +0900, Osamu Aoki wrote: > Please merge. Do you wish to be a uploader? If so add yourself. thanks! i've done so, and 5.5-3 has now been uploaded. Regards, --dkg
Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
Hi, On Tue, Feb 20, 2018 at 11:47:01PM -0800, Daniel Kahn Gillmor wrote: > On Tue 2018-02-20 23:36:49 +0900, Osamu Aoki wrote: ... > I've pushed a few minor changes, including this change, to the master > branch. Your report on situation was convincing enough. I agree to use python2.7 dependency. > I've also pushed a new branch called to-python2.7 so that we have > something concrete to consider when asking about consensus on the > dependency change. It works for me, and i can now purge python from > a machine without having to remove getmail. Please merge. Do you wish to be a uploader? If so add yourself. Osamu PS: I was talking "security fix by backporting newer version" https://packages.qa.debian.org/g/getmail4.html 4.46.0-1~deb7u1 4.46.0-1+deb8u1
Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
On Tue 2018-02-20 23:36:49 +0900, Osamu Aoki wrote: > That's I think this line of your message was truncated. > I moved getmail to salsa. You are added as developer. cool, thanks! I've just submitted https://salsa.debian.org/salsa/AliothRewriter/merge_requests/169 so that the old alioth git repo now re-points to salsa :) > "python2.7" is an idea but that may prevent backporting. > Is it important as distribution to do this? > (Not all previous release had python2.7 for sure) According to rmadison, oldoldstable has python2.7. I don't think we should care about backporting beyond that. > Please talk to other devs maintaining python packages. > > I tends to limit changes to the minimal friction path. We do need to > backport for security fixes. I'm assuming you're talking about backporting individual fixes when you say "backports", and not about "stretch-backports" or any of the other repos described at https://backports.debian.org/, since the stuff at backports.d.o is really not supposed to be a security fix channel. I'm not sure how a change in the packaging in debian unstable would affect our ability to backport specific fixes > Please make such decision not by your preference but with consensus. I asked over on py3porters-devel and only got a response from Scott Kitterman, who doesn't seem to think that this is an outright wrong thing to do, but thinks that it's a distraction, because he doesn't seem to care about anything that is not in debian: https://lists.alioth.debian.org/pipermail/py3porters-devel/Week-of-Mon-20180212/thread.html https://lists.alioth.debian.org/pipermail/py3porters-devel/Week-of-Mon-20180219/thread.html So, how should we measure consensus? > Having said this, I will let you have commit access. thanks -- i have commit access anyway because any DD has commit access to projects in the debian/ namespace, but i wouldn't want to use it anyway without your blessing, since you're the maintainer. > YES #!/usr/bin/python2 > > This fix can be applied... I've pushed a few minor changes, including this change, to the master branch. I've also pushed a new branch called to-python2.7 so that we have something concrete to consider when asking about consensus on the dependency change. It works for me, and i can now purge python from a machine without having to remove getmail. --dkg signature.asc Description: PGP signature
Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
Hi, On Mon, Feb 19, 2018 at 07:04:57PM -0800, Daniel Kahn Gillmor wrote: > On Wed 2018-02-14 16:28:37 -0500, Daniel Kahn Gillmor wrote: > > On Wed 2018-02-14 01:15:17 +0900, Osamu Aoki wrote: > >> YES #!/usr/bin/python2 > >> > >> NO #!/usr/bin/env python2 > > > > Works for me, thanks! > > It occurs to me that it might also be nice to adjust the dependency from > python to python2.7 if we do make this change, as it would allow a local > administrator who wants to experiment with this to "apt purge > python-minimal" and manually install their own symlink to python3 at > /usr/bin/python. That's > Would you like me to send a patch? > > Is there a plan to move getmail from alioth to salsa? I'd be happy to > help with that as well, if you're interested in that kind of help. > > --dkg I moved getmail to salsa. You are added as developer. "python2.7" is an idea but that may prevent backporting. Is it important as distribution to do this? (Not all previous release had python2.7 for sure) Please talk to other devs maintaining python packages. I tends to limit changes to the minimal friction path. We do need to backport for security fixes. getmail usually just pushes newer upstream release as security upload recently. (Yes, this is not normal for security but this is what happened.) Please make such decision not by your preference but with consensus. Having said this, I will let you have commit access. YES #!/usr/bin/python2 This fix can be applied... Regards, Osamu
Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
On Wed 2018-02-14 16:28:37 -0500, Daniel Kahn Gillmor wrote: > On Wed 2018-02-14 01:15:17 +0900, Osamu Aoki wrote: >> YES #!/usr/bin/python2 >> >> NO #!/usr/bin/env python2 > > Works for me, thanks! It occurs to me that it might also be nice to adjust the dependency from python to python2.7 if we do make this change, as it would allow a local administrator who wants to experiment with this to "apt purge python-minimal" and manually install their own symlink to python3 at /usr/bin/python. Would you like me to send a patch? Is there a plan to move getmail from alioth to salsa? I'd be happy to help with that as well, if you're interested in that kind of help. --dkg signature.asc Description: PGP signature
Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
On Wed 2018-02-14 01:15:17 +0900, Osamu Aoki wrote: > YES #!/usr/bin/python2 > > NO #!/usr/bin/env python2 Works for me, thanks! All the best, --dkg
Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
HI, On Mon, Feb 12, 2018 at 04:53:26PM -0500, Daniel Kahn Gillmor wrote: > Package: getmail > Version: 5.5-2 > Severity: normal > > Getmail does not work with python3, and upstream has indicated that > they are not likely to port it. > > According to PEP 394 [0], it should use a python2 shebang line, so > that systems can eventually switch /usr/bin/python to be supplied by > python3. YES #!/usr/bin/python2 NO #!/usr/bin/env python2 Please read Debian Python policy. https://www.debian.org/doc/packaging-manuals/python-policy/programs.html#interpreter-directive 4.1. Interpreter directive (“Shebang”) Executables written for interpretation by Python must use an appropraite interpreter directive, or “shebang”, as the first line of the program. This line should be of the form #!interpreter_location. See Section 2.4.1, “Interpreter Name” for the interpreter name to use. As noted in Section 2.4.2, “Interpreter Location”, the form #!/usr/bin/env interpreter_name is deprecated. . I see typo. s/appropraite/appropriate/
Bug#890282: getmail: please ship with shebang line of #!/usr/bin/env python2
Package: getmail Version: 5.5-2 Severity: normal Getmail does not work with python3, and upstream has indicated that they are not likely to port it. According to PEP 394 [0], it should use a python2 shebang line, so that systems can eventually switch /usr/bin/python to be supplied by python3. Regards, --dkg [0] https://www.python.org/dev/peps/pep-0394 -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages getmail depends on: ii python 2.7.14-4 getmail recommends no packages. getmail suggests no packages. -- no debconf information
