Your message dated Fri, 8 Sep 2006 12:57:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in NMU of entity 1.0.1-7.2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: entity
Version: 1.0.1-7.1
Severity: serious
Hello,
> python: non-matching version installed (2.4.3-11 ! << 2.4)
Cheers,
--
Julien Danjou
.''`. Debian Developer
: :' : http://julien.danjou.info
`. `' http://people.debian.org/~acid
`- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.0.1-7.2
I've NMUed for this bug (fixing the bug to use versioning instead of the
"fixed" tag, to ease tracking through testing); here's the changelog:
> entity (1.0.1-7.2) unstable; urgency=low
> .
> * Non-maintainer upload.
> * Update Build-depends to the new Python policy; change build-dependency on
> python2.3-dev to one on python-dev, and remove the demand that python
> should be (<< 2.4). Fixes FTBFS. (Closes: #380787, 383989)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
