On 02/07/14 12:48, Ricardo Mones wrote: > On Mon, 9 Jun 2014 16:47:27 +0200 > Ricardo Mones <mo...@debian.org> wrote: > >> On Mon, Jun 09, 2014 at 04:32:30PM +0200, Emilio Pozuelo Monfort wrote: >>> On 09/06/14 15:44, Ricardo Mones wrote: >>>> Hi, >>>> >>>> On Sun, May 25, 2014 at 02:38:47AM +0200, Ricardo Mones wrote: >>>>> Hi Emilio, >>>>> >>>>> On Sat, May 24, 2014 at 07:16:32PM +0200, Emilio Pozuelo Monfort >>>>> wrote: >>>>>> Hi, >>>>>> >>>> […] >>>>>> Can you upload this to experimental so it can go through NEW? >>>>> >>>>> Sure, done. >>>> […] >>>> >>>> Libetpan 1.4.1 has been in experimental for a week, and seems a >>>> transition tracker is already created. >>>> >>>> Does it mean is it ok to upload it to unstable? >>> >>> What's the status of claws-mail? You said you were waiting for upstream >>> to make a release that works with the new libetpan. If that's still a >>> blocker, then do not proceed with this, but if that release is out, then >>> go ahead and upload both libetpan and claws-mail to unstable. >> >> Well, that already happened for Claws Mail 3.10.0, and today again >> for 3.10.1, so I'll proceed :) > > AFAICS everything is built fine¹, but PTS/testing migration excuses² says > there's a missing libetpan16, which of course won't be since this was a > soname bump and now its libetpan17...
That's because libetpan needs to be decrufted (i.e. the old libetpan16 need to be removed). However I haven't asked for a decruft yet because the transition isn't quite finished, as cairo-dock-plug-ins hasn't been rebuilt yet because of #751171, and now also because of bd-uninst issue with gnutls26/gnutls28. So once cairo-dock-plug-ins build-depends on libgnutls28-dev (so that the build dependencies can be satisfied), then as soon as #751171 is fixed the package will build on s390x and the migration will be done. So, can you file a bug for the bd-uninst issue on cairo-dock-plug-ins and make it block this bug? Thanks, Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b3f75e.7060...@debian.org
