Bug#750399: marked as done (nmu: pyzmq_14.3.0-1)
Your message dated Fri, 13 Jun 2014 11:32:27 +0200
with message-id <539AC52B.4010900@debian.org>
and subject line Re: Bug#750399: nmu: pyzmq_14.3.0-1
has caused the Debian Bug report #750399,
regarding nmu: pyzmq_14.3.0-1
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 owner@bugs.debian.org
immediately.)
--
750399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750399
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
nmu pyzmq_14.3.0-1 . ALL . -m "rebuild against pypy 2.3+dfsg-3"
pypy-zmq currently depends on pypy (<2.3), hence is not installable in sid.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On 03/06/14 08:50, Ralf Treinen wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
>
> nmu pyzmq_14.3.0-1 . ALL . -m "rebuild against pypy 2.3+dfsg-3"
>
> pypy-zmq currently depends on pypy (<2.3), hence is not installable in sid.
Package: pypy-zmq
Version: 14.3.0-1+b1
Depends: gcc, libzmq3-dev, pypy (>= 2.2), pypy (<< 2.4), libc6 (>= 2.14),
libzmq3 (>= 4.0.1+dfsg)
Looks good to me now. It may not be fine on kfreebsd-* and mips* where it failed
to build, but binnmus there won't help... you need to investigate and fix the issue.
Regards,
Emilio
--- End Message ---
Reply to: