On Sun, Sep 12, 2010 at 09:41:26PM +0200, gregor herrmann wrote:
I've prepared a new libcoro-perl release in our svn repo which
- removes the cruft from debian/rules
- bumps the build and runtime dependency on libanyevent-perl to
= 5.271-2
Before I upload: Is this ok for the release
On Mon, Sep 13, 2010 at 13:46:49 +0300, Niko Tyni wrote:
From the release point of view, I think just unblocking libanyevent-perl
5.271-2 for squeeze should be enough. The libcoro-perl version in squeeze
(5.210) should indeed be fine, and if there's a need to get 5.230 in that
should be a
On Mon, 13 Sep 2010 13:46:49 +0300, Niko Tyni wrote:
I've prepared a new libcoro-perl release in our svn repo which
- removes the cruft from debian/rules
- bumps the build and runtime dependency on libanyevent-perl to
= 5.271-2
On a second thought: libcoro-perl 5.210-1 in testing
On Thu, 09 Sep 2010 22:49:50 +0200, gregor herrmann wrote:
Building against a modified libanyevent-perl_5.271-1 with a fixed
O_NONBLOCK value makes the test pass for me on both smetana (sparc)
and albeniz (alpha).
I think libanyevent-perl should be turned into an Architecture:any
clone 578458 -1
retitle -1 libanyevent-perl: architecture specific constants in an arch:all
package
reassign -1 libanyevent-perl 5.251-1
severity -1 grave
found -1 5.271-1
block 578458 by -1
submitter -1 !
notforwarded -1
thanks
On Mon, Aug 23, 2010 at 10:47:25AM +0300, Niko Tyni wrote:
On Fri,
On Thu, 09 Sep 2010 21:47:40 +0300, Niko Tyni wrote:
On Mon, Aug 23, 2010 at 10:47:25AM +0300, Niko Tyni wrote:
It looks like the test broke with libanyevent-perl_5.251-1. I don't have
the time to investigate more right now. FWIW, the current libanyevent-perl
version does pass its own test
found 578458 5.210-1
thanks
On Fri, Jun 18, 2010 at 03:03:38PM +0200, gregor herrmann wrote:
On Thu, 20 May 2010 18:05:09 +0200, gregor herrmann wrote:
5.230-1 still FTBFS on some architectures; and now in an earlier test
than the one I patched to get more informations :/
Actually it's
On Thu, 20 May 2010 18:05:09 +0200, gregor herrmann wrote:
5.230-1 still FTBFS on some architectures; and now in an earlier test
than the one I patched to get more informations :/
Actually it's probably the same test (t/19_handle.t) but we don't see
any output.
More frustrating info: I just
5.230-1 still FTBFS on some architectures; and now in an earlier test
than the one I patched to get more informations :/
Cheers,
gregor
--
.''`. http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
: :' : Debian GNU/Linux user, admin, developer - http://www.debian.org/
`.
9 matches
Mail list logo