Your message dated Sun, 10 Aug 2014 17:25:18 +0100 with message-id <[email protected]> and subject line Re: Bug#739295: python3-dbus: rebuild required for python 3.4 has caused the Debian Bug report #739295, regarding python3-dbus: rebuild required for python 3.4 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 [email protected] immediately.) -- 739295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739295 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python3-dbus Version: 1.2.0-2+b1 Severity: wishlist Dear Maintainer, The recent upload of python 3.4 to experimental causes this library to fail with _dbus_bindings not found. Please consider rebuilding this library before python 3.4 hits unstable. --Tom -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13.0-rc1-tm1 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3-dbus depends on: ii libc6 2.17-97 ii libdbus-1-3 1.8.0-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.38.2-5 ii python3 3.4~rc1-1 pn python3:any <none> Versions of packages python3-dbus recommends: ii python3-gi 3.10.2-2 Versions of packages python3-dbus suggests: pn python-dbus-doc <none> pn python3-dbus-dbg <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Mon, 17 Feb 2014 at 14:59:28 +0000, Simon McVittie wrote: > On 17/02/14 14:35, Tom Marble wrote: > > Please consider rebuilding this library before > > python 3.4 hits unstable. > > As far as I'm aware, it should just need a binNMU, which should be > scheduled by the Python maintainers (or some other interested party) > asking the release team to binNMU all packages in this state as a batch. This appears to have been done on all release architectures, 2 months ago. S
--- End Message ---
