Re: New gui release due to report of 0.25.1 abi incompatibility with 0.25.0

> > > > I will aim to do so this weekend. Please stop me now if you want to > submit something for the next gui release. > > -- > > Sent from Gmail Mobile on iPad > > ___ > > Gnus

New gui release due to report of 0.25.1 abi incompatibility with 0.25.0

Hi, On Debian packaging mailing list I observed a report of abi incompatibility with the previous release. A solution proposed is to cut a new release with bumped version. I will aim to do so this weekend. Please stop me now if you want to submit something for the next gui release. -- Sent from

Re: Cutting a gnustep-gui release

0.25.1 will not include the wayland backend. On Tue, Apr 4, 2017 at 8:15 AM, Gürkan Myczko wrote: > will it have the -wayland back? clang? yay > > :) thumbs up > > Gürkan > Tel. 076 436 72 00 > > > > On Apr 4, 2017, at 06:03, Eric Heintzmann

Re: Cutting a gnustep-gui release

will it have the -wayland back? clang? yay :) thumbs up Gürkan Tel. 076 436 72 00 > On Apr 4, 2017, at 06:03, Eric Heintzmann wrote: > > Hi, > > ( Debian is currently frozen, so new gnustep packages won't be included > in Debian 9. > But of course I will

Re: Cutting a gnustep-gui release

Hi, ( Debian is currently frozen, so new gnustep packages won't be included in Debian 9. But of course I will package it in experimental section) What I do at each release of gnustep-gui/back: 0 install all dev dependencies with apt (gnustep-base-dev & build-essential & all -dev packages

Re: Cutting a gnustep-gui release

It's not totally clear to me how to make a good use of this. Let's assume I have an existing .deb obtained via packages.debian.org (or an .so from that .deb), and I have a source tree checked out from GNUstep's Subversion. Let's assume I have no 'package tree' (i.e. one with debian/ directory) at

Re: Cutting a gnustep-gui release

Le 16/12/2016 à 17:16, Ivan Vučica a écrit : > > On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann > > wrote: > > Debian Stretch will be fully frozen on 2017-02-05. > A special release before this date, with all you want to see in >

Re: Cutting a gnustep-gui release

Hi, Le 16/12/2016 à 17:53, Richard Frith-Macdonald a écrit : > There are quite a lot of bugfixes in trunk, so perhaps it would be worth > doing another 1.28.x release ... does anyone know how to use the debian tools > for checking abi compatibility to see if trunk really is abi compatible with

Re: Cutting a gnustep-gui release

I also did not get around preparing for a release this weekend. I'll do some cursory testing myself, but because you have way more configurations and are regularly using or compiling many apps, help here would be appreciated. On Sun, Dec 18, 2016 at 10:52 PM, Riccardo Mottola <

Re: Cutting a gnustep-gui release

Hi, On 14/12/2016 19:02, Ivan Vučica wrote: I have seen some bug fixes flow by so I would like to dedicate some time to cutting a point release of gnustep-gui/back. Let me know if you would like me to delay or to sync with another release. Fred and Wolfgang fixed the only two bad

Re: Cutting a gnustep-gui release

Le 16/12/2016 à 17:35, Ivan Vučica a écrit : > On Fri, Dec 16, 2016 at 4:25 PM, Stefan Bidigaray > > wrote: > > Hi Ivan, > I would assume, as a minimum, the soname cannot change. GNUstep > does have a habit of incrementing the

Re: Cutting a gnustep-gui release

> On 15 Dec 2016, at 11:23, Ivan Vučica wrote: > > On Wed, Dec 14, 2016, 22:47 Riccardo Mottola > wrote: > Hi, > > Ivan Vučica wrote: > > Let me know if you would like me to delay or to sync with another release. > > current gui has some

Re: Cutting a gnustep-gui release

On Fri, Dec 16, 2016 at 4:25 PM, Stefan Bidigaray wrote: > Hi Ivan, > I would assume, as a minimum, the soname cannot change. GNUstep does have > a habit of incrementing the soname with MINOR release number bumps, even if > the ABI remains unchanged. > > For example,

Re: Cutting a gnustep-gui release

On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann wrote: > Debian Stretch will be fully frozen on 2017-02-05. > A special release before this date, with all you want to see in the next > debian stable distro, would be a good idea. > > (The current status of Stretch is

Re: Cutting a gnustep-gui release

Hi, Le 15/12/2016 à 12:23, Ivan Vučica a écrit : > On Wed, Dec 14, 2016, 22:47 Riccardo Mottola > > wrote: > > Hi, > > Ivan Vučica wrote: > > Let me know if you would like me to delay or to sync with > another

Re: Cutting a gnustep-gui release

On Wed, Dec 14, 2016, 22:47 Riccardo Mottola wrote: > Hi, > > Ivan Vučica wrote: > > Let me know if you would like me to delay or to sync with another > release. > > current gui has some important fixes done by fred: they could be > backported to stable in case? >

Cutting a gnustep-gui release

I have seen some bug fixes flow by so I would like to dedicate some time to cutting a point release of gnustep-gui/back. Let me know if you would like me to delay or to sync with another release. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org

gui release?

Hi, I just wanted to verify that gui isn't in code freeze, because I've been committing some new things lately. Does anyone have thoughts on when we should do a gui release?Maybe in September or October? Eric ___ Gnustep-dev mailing list Gnustep-dev

Re: gui release?

On 16.08.2011 19:36, Eric Wasylishen wrote: I just wanted to verify that gui isn't in code freeze, because I've been committing some new things lately. Does anyone have thoughts on when we should do a gui release?Maybe in September or October? That time frame sound good to me. And thank you

Re: Gui release

On 3 Dec 2008, at 09:17, Fred Kiefer wrote: I would like to see a gui release real soon now. The only open problem that should be investigated (not solved) is the segmentation fault from GWorkspace. (I will look into that as soon as I get GWorkspace to compile) Now that gui and back have

Gui release

I would like to see a gui release real soon now. The only open problem that should be investigated (not solved) is the segmentation fault from GWorkspace. (I will look into that as soon as I get GWorkspace to compile) Now that gui and back have been changed to respect the domain settings I would