Bug#938909: Dealing with zope.interface unsatisfiable build-dependency.
zope.interface is currently rc buggy because of an unsatisfiable build-depenency on python-zope.event, the package is also orphaned. The package is a key package, so the issue won't be dealt with by autoremovals, furthermore the python-zope.interface package has quite a stack of reverse dependencies, so dropping it doesn't seem like a good option at this point. Testing reveals that the build-dependency in question is only needed by the test suite, so I believe the least-bad option is to drop the build-dependency and not run the testsuite. It would be preferable to only disable the testsuite for python2, but I have no idea how to do that, so my current debdiff disables the testsuite completely, I also ran into an issue with the package's clean target not cleaning up properly. If anyone can suggest how to modify the package so it runs the testsuite for python3 but not python2 that would be appreciated. I plan to go ahead with an upload next week. diff -Nru zope.interface-4.6.0/debian/changelog zope.interface-4.6.0/debian/changelog --- zope.interface-4.6.0/debian/changelog 2019-09-05 11:09:40.0 + +++ zope.interface-4.6.0/debian/changelog 2019-12-07 07:00:43.0 + @@ -1,3 +1,13 @@ +zope.interface (4.6.0-2) unstable; urgency=medium + + * QA upload. + * Drop build-dependency on nonexistent python-zope.event. Downgrades: #938909. + * Disable testsuite, it needs python-zope.event. + * Fix clean target. + * Add build-depends on moreutils, needed by fixed clean target. + + -- Peter Michael Green Sat, 07 Dec 2019 07:00:43 + + zope.interface (4.6.0-1) unstable; urgency=medium * QA upload. diff -Nru zope.interface-4.6.0/debian/control zope.interface-4.6.0/debian/control --- zope.interface-4.6.0/debian/control 2019-09-05 11:09:40.0 + +++ zope.interface-4.6.0/debian/control 2019-12-07 07:00:43.0 + @@ -12,11 +12,11 @@ python-all-dbg:any, python-all-dev:any, python-setuptools, - python-zope.event, python3-all-dbg:any, python3-all-dev:any, python3-setuptools, - python3-zope.event + python3-zope.event, + moreutils Standards-Version: 4.4.0 Testsuite: autopkgtest Homepage: http://pypi.python.org/pypi/zope.interface diff -Nru zope.interface-4.6.0/debian/rules zope.interface-4.6.0/debian/rules --- zope.interface-4.6.0/debian/rules 2016-07-05 21:43:11.0 + +++ zope.interface-4.6.0/debian/rules 2019-12-07 07:00:43.0 + @@ -97,3 +97,10 @@ override_dh_strip: dh_strip -p$(package) --dbg-package=$(package)-dbg dh_strip -p$(package3) --dbg-package=$(package3)-dbg + +override_dh_auto_test: + echo testsuite disabled + +override_dh_auto_clean: + rm -f .eggs/README.txt + rm -f src/zope.interface.egg-info/requires.txt
Bug#938909: Dealing with zope.interface unsatisfiable build-dependency.
On 07/12/2019 07:47, peter green wrote: It would be preferable to only disable the testsuite for python2, but I have no idea how to do that, so my current debdiff disables the testsuite completely, I also ran into an issue with the package's clean target not cleaning up properly. Just realized I added moreutils to the build-depends, planning to use it in the clean target fix, but in the end I decided to just delete the file in question. So that build-dep should be dropped before upload.
Bug#938909: Dealing with zope.interface unsatisfiable build-dependency.
If you still wish to disable tests for python 2, you might be looking for this export PYBUILD_DISABLE_python2=test That line in debian/rules should work. You have some more options here: https://wiki.debian.org/Python/Pybuild and perhaps the manpages. On 07.12.2019 09:12, peter green wrote: On 07/12/2019 07:47, peter green wrote: It would be preferable to only disable the testsuite for python2, but I have no idea how to do that, so my current debdiff disables the testsuite completely, I also ran into an issue with the package's clean target not cleaning up properly. Just realized I added moreutils to the build-depends, planning to use it in the clean target fix, but in the end I decided to just delete the file in question. So that build-dep should be dropped before upload.
Bug#938909: Dealing with zope.interface unsatisfiable build-dependency.
On 07/12/2019 15:09, Håvard Flaget Aasen wrote: If you still wish to disable tests for python 2, you might be looking for this export PYBUILD_DISABLE_python2=test That line in debian/rules should work. You have some more options here: https://wiki.debian.org/Python/Pybuild and perhaps the manpages. Thanks, I found I also had to add export PYBUILD_DISABLE_python2-dbg=test to disable the tests for the python2 debug interpreter. Looking at the log confirms it's running the tests for python 3.x and not python 2.x as desired. New debdiff is attached. diff -Nru zope.interface-4.6.0/debian/changelog zope.interface-4.6.0/debian/changelog --- zope.interface-4.6.0/debian/changelog 2019-09-05 11:09:40.0 + +++ zope.interface-4.6.0/debian/changelog 2019-12-07 07:00:43.0 + @@ -1,3 +1,13 @@ +zope.interface (4.6.0-2) unstable; urgency=medium + + * QA upload. + * Drop build-dependency on nonexistent python-zope.event. Downgrades: #938909. + * Disable testsuite for python 2, it needs python-zope.event. +(keep testsuite enabled for python 3) + * Fix clean target. + + -- Peter Michael Green Sat, 07 Dec 2019 07:00:43 + + zope.interface (4.6.0-1) unstable; urgency=medium * QA upload. diff -Nru zope.interface-4.6.0/debian/control zope.interface-4.6.0/debian/control --- zope.interface-4.6.0/debian/control 2019-09-05 11:09:40.0 + +++ zope.interface-4.6.0/debian/control 2019-12-07 07:00:43.0 + @@ -12,7 +12,6 @@ python-all-dbg:any, python-all-dev:any, python-setuptools, - python-zope.event, python3-all-dbg:any, python3-all-dev:any, python3-setuptools, diff -Nru zope.interface-4.6.0/debian/rules zope.interface-4.6.0/debian/rules --- zope.interface-4.6.0/debian/rules 2016-07-05 21:43:11.0 + +++ zope.interface-4.6.0/debian/rules 2019-12-07 07:00:43.0 + @@ -3,6 +3,8 @@ export PYBUILD_NAME=zope.interface #export PYBUILD_VERBOSE=1 #export DH_VERBOSE=1 +export PYBUILD_DISABLE_python2=test +export PYBUILD_DISABLE_python2-dbg=test %: dh $@ --with python2,python3 --buildsystem=pybuild @@ -97,3 +99,9 @@ override_dh_strip: dh_strip -p$(package) --dbg-package=$(package)-dbg dh_strip -p$(package3) --dbg-package=$(package3)-dbg + +override_dh_auto_clean: + dh_auto_clean + rm -f .eggs/README.txt + rm -f src/zope.interface.egg-info/requires.txt + rm -f src/zope/interface/_zope_interface_coptimizations.*.so
Bug#938675: marked as done (tofu: Python2 removal in sid/bullseye)
Your message dated Sun, 08 Dec 2019 07:30:18 + with message-id and subject line Bug#946350: Removed package(s) from unstable has caused the Debian Bug report #938675, regarding tofu: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tofu Version: 0.5-7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:tofu If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.5-7+rm Dear submitter, as the package tofu has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/946350 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#451413: marked as done (python-tofu: client/server demo fails)
Your message dated Sun, 08 Dec 2019 07:30:18 + with message-id and subject line Bug#946350: Removed package(s) from unstable has caused the Debian Bug report #451413, regarding python-tofu: client/server demo fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 451413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-tofu Version: 0.5-3 Severity: normal Running python run_demo.py --server in one window and python run_demo.py --client localhost username in the other window gives nothing but a blank game board. When you hit any key, you get an error message much like this: $ python run_demo.py --client localhost localhost * Tofu * IDLER created ! Exception in Tkinter callback Traceback (most recent call last): File "lib-tk/Tkinter.py", line 1348, in __call__ return self.func(*args) File "/usr/share/doc/python-tofu/examples/demo.py", line 419, in on_move_right def on_move_right (self, event = None): self.player_character.action = Action(ACTION_MOVE_RIGHT) AttributeError: 'NoneType' object has no attribute 'action' Traceback (most recent call last): File "run_demo.py", line 76, in ? tofu.client.serve_forever(hostname) File "/var/lib/python-support/python2.4/tofu/client.py", line 251, in serve_forever tofu.NOTIFIER.transport.loseConnection() AttributeError: 'Notifier' object has no attribute 'transport' $ Note that it works when run as: $ run_demo.py --single username -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages python-tofu depends on: ii python2.4.4-6An interactive high-level object-o ii python-support0.7.5 automated rebuilding support for p ii python-twisted-core 2.5.0-2Event-based framework for internet Versions of packages python-tofu recommends: ii python-cerealizer 0.6-1 secure pickle-like module for Pyth -- no debconf information --- End Message --- --- Begin Message --- Version: 0.5-7+rm Dear submitter, as the package tofu has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/946350 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#946350: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: python-tofu | 0.5-7 | all tofu | 0.5-7 | source --- Reason --- RoQA; dead upstream, dead name, python2 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/946350 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#946350: Removed package(s) from unstable
Version: 0.5-7+rm Dear submitter, as the package tofu has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/946350 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
