Bug#677574: marked as done (transition: libv8)
Your message dated Sun, 17 Jun 2012 12:06:31 +0200
with message-id <4FDDAC27.7040408@melix.org>
and subject line Re: Bug#677574: transition: libv8
has caused the Debian Bug report #677574,
regarding transition: libv8
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.)
--
677574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677574
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: transition
Hi,
i'd like to update libv8 3.8.9.20 to 3.10.8.
* packages needing a simple rebuild (i checked them) :
+ libv8-i18n
+ osmium
+ drizzle
* packages needing more work :
nodejs (i'm maintaining it and it's ready to be uploaded)
Please note that SONAME is libv8.so.3.10.8 instead of libv8.so.3.10.8.15,
allowing libv8 maintainers to do patch-level updates without the need to
setup a transition. This will hopefully improve the current situation.
I started some discussion about that here :
http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2012-June/003683.html
Ben file:
title = "libv8";
is_affected = .depends ~ "libv8-3.8.9.20" | .depends ~ "libv8-3.10.8";
is_good = .depends ~ "libv8-3.10.8";
is_bad = .depends ~ "libv8-3.8.9.20";
Regards,
Jérémy.
--- End Message ---
--- Begin Message ---
Hi,
according to [1] we have
"After Sunday the 20th of May, any new transitions are likely not to be
processed until after the release."
So that transition is way too late, and the result is that libv8 3.10.8
should be uploaded to experimental instead.
Closing this bug.
Regards,
Jérémy.
[1]
https://lists.debian.org/debian-devel-announce/2012/05/msg00004.html
--- End Message ---
Reply to: