Re: Bug#578458: still fails to build
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 team, and can -- provided
> libcoro-perl builds everywhere -- both package be unblocked?
>
> On a second thought: libcoro-perl 5.210-1 in testing should be fine
> with the newer libanyevent-perl and a round of binNMUs; and we can
> still test this and do the cleanup by uploading 5.230-4 to unstable.
> Hm.
+1 to the second thought, except that I don't see any need for binNMUs.
Uploading libcoro-perl 5.230-4 to sid doesn't change anything wrt. squeeze
(squeeze and sid already have different versions) and therefore isn't
really in the release team domain. However, it's the easiest way to
confirm that the fix works and to clean away the unnecessary backend
selection code. I think you should go ahead.
If 5.230-4 builds everywhere, I think this bug (#578458) should be closed
outright. I should really have reassigned it instead of cloning.
>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 separate discussion.
Apologies, the confusion was probably because of my earlier comment about
cleaning the backend selection code for squeeze. That's not necessary
because the code never got in squeeze in the first place.
--
Niko Tyni ntyni@debian.org
Reply to: