[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#673538: marked as done (transition: gnustep-base 1.24, gnustep-gui 0.22)



Your message dated Thu, 17 Jul 2014 01:16:01 +0200
with message-id <53C707B1.9000300@debian.org>
and subject line Re: Bug#673538: transition: gnustep-base, gnustep-gui
has caused the Debian Bug report #673538,
regarding transition: gnustep-base 1.24, gnustep-gui 0.22
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.)


-- 
673538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673538
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

We'd like to carry out a GNUstep transition prior to the forthcoming release:

libgnustep-base1.22 -> 1.24
libgnustep-gui0.20  -> 0.22
libobjc3	    -> 4 (on architectures where gcc-4.7 is the default)

I plan to upload the new GNUstep stack to experimental within a few
days, then make a test rebuild of all GNUstep packages and identify
all bugs (GCC-related bugs have already been reported); then I'll
follow up with a summary of affected packages.

Thanks.



--- End Message ---
--- Begin Message ---
On 07/07/14 10:32, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 07/07/14 09:47, Yavor Doganov wrote:
>> Yavor Doganov wrote:
>>> I'm waiting for gnustep-back to get ACCEPTed and built everywhere.
>>> Once done, we're basically ready (I only have to backport my
>>> gnustep-base patch for the gnutls transition).
>>
>> ACCEPTed and built on almost all release architectures (mipsen
>> slightly lagging behind).  Please let me know when it is OK to upload
>> to unstable.  I gather we must wait for the poppler transition to
>> complete.
> 
> poppler is almost ready and I can just delay binNMUing popplerkit.framework
> until the poppler transition is over. Everything else looks good, so please go
> ahead.

This migrated a few days ago. Closing.

Emilio

--- End Message ---

Reply to: