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

[Ivan Vučica]

This has not happened yet. I hope to do it over this week.

Please let me know if you spot any critical bugs that should delay the
release.

On Sat, Sep 30, 2017 at 11:35 AM, Fred Kiefer  wrote:

> Fine by me, go ahead and cut a release.
>
> Fred
>
> On the road
>
> Am 27.09.2017 um 23:34 schrieb Ivan Vučica :
>
> > 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 Gmail Mobile on iPad
> > ___
> > Gnustep-dev mailing list
> > Gnustep-dev@gnu.org
> > https://lists.gnu.org/mailman/listinfo/gnustep-dev
>
>
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

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

[Fred Kiefer]

Fine by me, go ahead and cut a release.

Fred

On the road

Am 27.09.2017 um 23:34 schrieb Ivan Vučica :

> 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 Gmail Mobile on iPad
> ___
> Gnustep-dev mailing list
> Gnustep-dev@gnu.org
> https://lists.gnu.org/mailman/listinfo/gnustep-dev


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

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

[Ivan Vučica]

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 Gmail Mobile on iPad
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Ivan Vučica]

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 
> wrote:
> >
> > 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 needed).
> >
> > 1 -  rebuild gnustep-gui/back and see if all GNUstep apps still work
> > fine without rebuild them
> >
> > 2 - rebuild all GNUstep  apps with the new gnustep-gui/dev, and see if
> > they still build fine.
> >
> > 3 - repackage the new gnustep-gui/back, and see if debbuild show an
> > ABI/API breakage when building.
> > (to repackage I just have to copy the debian subdir into your source
> > tree checked out from GNUstep's Subversion,
> > and run debuild --
> > https://www.debian.org/doc/manuals/maint-guide/build.html#debuild).
> >
> > 4 - run lintian
> > (https://www.debian.org/doc/manuals/maint-guide/checkit.html#lintians)
> > on the new gui/back packages .
> > (I use lintian -i -I -E --show-overrides)
> >
> > Thanks
> >
> >> Le 04/04/2017 à 02:23, Ivan Vučica a écrit :
> >>
> >> 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 a particular
> time.
> >>
> >> What would you like me to do to prepare the source tree (do I need to
> >> obtain the debian/ directory, for example), and what would you like me
> >> to execute in order to validate that the ABI didn't break?
> >>
> >> Thanks!
> >>
> >> On Tue, Dec 20, 2016 at 5:44 PM, Eric Heintzmann
> >> mailto:heintzmann.e...@free.fr>> wrote:
> >>
> >>
> >>
> >>>Le 16/12/2016 à 17:16, Ivan Vučica a écrit :
> >>>
> >>> On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann
> >>> mailto:heintzmann.e...@free.fr>
> >>>>
> >>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 "transition freeze", it means
> >>>that all
> >>>ABI/API breakage will be refused by the official Debian
> >>release team)
> >>>
> >>>
> >>> Unless I missed something significant, the API/ABI should be
> >>backwards
> >>> compatible. (I'd go through the list of changes before the release.)
> >>>
> >>> Any easy way to test whether Debian will consider API/ABI
> >>breakage has
> >>> happened, which we could then add to the release docs?
> >>>
> >>
> >>https://www.debian.org/doc/debian-policy/ch-sharedlibs.
> html#s-sharedlibs-updates
> >> html#s-sharedlibs-updates>
> >>
> >>https://www.netfort.gr.jp/~dancer/column/libpkg-guide/
> libpkg-guide.html#sonameapiabi
> >> libpkg-guide.html#sonameapiabi>
> >>
> >>
> >
> >
>
>
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Gürkan Myczko]

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 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 needed).
> 
> 1 -  rebuild gnustep-gui/back and see if all GNUstep apps still work
> fine without rebuild them
> 
> 2 - rebuild all GNUstep  apps with the new gnustep-gui/dev, and see if
> they still build fine.
> 
> 3 - repackage the new gnustep-gui/back, and see if debbuild show an
> ABI/API breakage when building.
> (to repackage I just have to copy the debian subdir into your source
> tree checked out from GNUstep's Subversion,
> and run debuild --
> https://www.debian.org/doc/manuals/maint-guide/build.html#debuild).
> 
> 4 - run lintian
> (https://www.debian.org/doc/manuals/maint-guide/checkit.html#lintians)
> on the new gui/back packages .
> (I use lintian -i -I -E --show-overrides)
> 
> Thanks
> 
>> Le 04/04/2017 à 02:23, Ivan Vučica a écrit :
>> 
>> 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 a particular time.
>> 
>> What would you like me to do to prepare the source tree (do I need to
>> obtain the debian/ directory, for example), and what would you like me
>> to execute in order to validate that the ABI didn't break?
>> 
>> Thanks!
>> 
>> On Tue, Dec 20, 2016 at 5:44 PM, Eric Heintzmann
>> mailto:heintzmann.e...@free.fr>> wrote:
>> 
>> 
>> 
>>>Le 16/12/2016 à 17:16, Ivan Vučica a écrit :
>>> 
>>> On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann
>>> mailto:heintzmann.e...@free.fr>
>>>>
>>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 "transition freeze", it means
>>>that all
>>>ABI/API breakage will be refused by the official Debian 
>>release team)
>>> 
>>> 
>>> Unless I missed something significant, the API/ABI should be
>>backwards
>>> compatible. (I'd go through the list of changes before the release.)
>>> 
>>> Any easy way to test whether Debian will consider API/ABI
>>breakage has
>>> happened, which we could then add to the release docs?
>>> 
>> 
>>
>> https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates
>>
>> 
>> 
>>
>> https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi
>>
>> 
>> 
>> 
> 
> 


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Eric Heintzmann]

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 needed).
 
1 -  rebuild gnustep-gui/back and see if all GNUstep apps still work
fine without rebuild them

2 - rebuild all GNUstep  apps with the new gnustep-gui/dev, and see if
they still build fine.

3 - repackage the new gnustep-gui/back, and see if debbuild show an
ABI/API breakage when building.
(to repackage I just have to copy the debian subdir into your source
tree checked out from GNUstep's Subversion,
and run debuild --
https://www.debian.org/doc/manuals/maint-guide/build.html#debuild).

4 - run lintian
(https://www.debian.org/doc/manuals/maint-guide/checkit.html#lintians)
on the new gui/back packages .
(I use lintian -i -I -E --show-overrides)
 
Thanks

Le 04/04/2017 à 02:23, Ivan Vučica a écrit :

> 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 a particular time.
>
> What would you like me to do to prepare the source tree (do I need to
> obtain the debian/ directory, for example), and what would you like me
> to execute in order to validate that the ABI didn't break?
>
> Thanks!
>
> On Tue, Dec 20, 2016 at 5:44 PM, Eric Heintzmann
> mailto:heintzmann.e...@free.fr>> wrote:
>
>
>
> Le 16/12/2016 à 17:16, Ivan Vučica a écrit :
> >
> > On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann
> > mailto:heintzmann.e...@free.fr>
> >>
> 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 "transition freeze", it means
> > that all
> > ABI/API breakage will be refused by the official Debian 
> release team)
> >
> >
> > Unless I missed something significant, the API/ABI should be
> backwards
> > compatible. (I'd go through the list of changes before the release.)
> >
> > Any easy way to test whether Debian will consider API/ABI
> breakage has
> > happened, which we could then add to the release docs?
> >
>
> 
> https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates
> 
> 
>
> 
> https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi
> 
> 
>
>



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Ivan Vučica]

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 a particular time.

What would you like me to do to prepare the source tree (do I need to
obtain the debian/ directory, for example), and what would you like me to
execute in order to validate that the ABI didn't break?

Thanks!

On Tue, Dec 20, 2016 at 5:44 PM, Eric Heintzmann 
wrote:

>
>
> Le 16/12/2016 à 17:16, Ivan Vučica a écrit :
> >
> > On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann
> > mailto:heintzmann.e...@free.fr>> 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 "transition freeze", it means
> > that all
> > ABI/API breakage will be refused by the official Debian  release
> team)
> >
> >
> > Unless I missed something significant, the API/ABI should be backwards
> > compatible. (I'd go through the list of changes before the release.)
> >
> > Any easy way to test whether Debian will consider API/ABI breakage has
> > happened, which we could then add to the release docs?
> >
>
> https://www.debian.org/doc/debian-policy/ch-sharedlibs.
> html#s-sharedlibs-updates
>
> https://www.netfort.gr.jp/~dancer/column/libpkg-guide/
> libpkg-guide.html#sonameapiabi
>
>
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Eric Heintzmann]

Le 16/12/2016 à 17:16, Ivan Vučica a écrit :
>
> On Fri, Dec 16, 2016 at 3:54 PM, Eric Heintzmann
> mailto:heintzmann.e...@free.fr>> 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 "transition freeze", it means
> that all
> ABI/API breakage will be refused by the official Debian  release team)
>
>
> Unless I missed something significant, the API/ABI should be backwards
> compatible. (I'd go through the list of changes before the release.)
>
> Any easy way to test whether Debian will consider API/ABI breakage has
> happened, which we could then add to the release docs?
>

https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates

https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Eric Heintzmann]

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 
> the latest release?
>
>

I've packaged gnustep-base trunk, and dpkg-gensymbols does not find any
ABI/API breakage.

(There are 6 symbol additions but this is not an issue:

GSPrivateCStringEncoding@Base
__objc_class_name_GSMimeSerializer@Base
__objc_class_name_GSQuickSortPlaceHolder@Base
__objc_class_name_GSTimSortPlaceHolder@Base
__objc_class_name_NSDataWithDeallocatorBlock@Base
__objc_class_name_NSMutableDataWithDeallocatorBlock@Base

)

So, I think that a release now would be a good idea.

Thanks
Eric


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Ivan Vučica]

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 <
riccardo.mott...@libero.it> wrote:

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 regressions we had compared the
past release I would have considered blocking.
Perhaps the fixes need a bit of testing? I already tested Wolfgang's fix on
a couple of systems and it works.
I tested Fred's fix for overlapping chars in GNUMail on one system and it
works and on the other laptop where it worked it continues to work. A test
with most GUI apps would be needed, I will try to find the time in the next
days.

I know of no other regressions in base or gui, that's a first thing.

Of course there are still bugs, but I see no blockers and there were
several fixes. Other do?

Riccardo



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Eric Heintzmann]

Le 16/12/2016 à 18:20, Eric Heintzmann a écrit :
> 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 the latest release?
>>
>>
> I suggets to make a pre-release of make|base|gui/back , and I will check. 
I don't know if a new release of gnustep-make is planned, but there is a
RC bug to fix first (see https://bugs.debian.org/838278 )
I'm not sure how to fix this issue, but i ve tried to write a patch (
see attached file).

Thanks
Eric

Description: Remove obsolete @setcontentsaftertitlepage command
Bug-Debian: https://bugs.debian.org/838278
Author: Eric Heintzmann 
Last-Update: 2016-12-19


--- a/Documentation/gnustep-howto.texi
+++ b/Documentation/gnustep-howto.texi
@@ -5,7 +5,6 @@
 @settitle GNUstep HOWTO
 @c %**end of header
 @set HOWTO
-@setcontentsaftertitlepage
 @smallbook
 
 @titlepage
--- a/Documentation/gnustep-filesystem.texi
+++ b/Documentation/gnustep-filesystem.texi
@@ -3,7 +3,6 @@
 @c %**start of header
 @settitle GNUstep Filesystem Hierarchy Document
 @c %**end of header
-@setcontentsaftertitlepage
 @smallbook
 
 @titlepage
--- a/Documentation/gnustep-make.texi
+++ b/Documentation/gnustep-make.texi
@@ -4,7 +4,6 @@
 @settitle GNUstep Makefile Package
 @c %**end of header
 
-@setcontentsaftertitlepage
 @smallbook
 @setchapternewpage odd
 
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Riccardo Mottola]

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 regressions we had compared the 
past release I would have considered blocking.
Perhaps the fixes need a bit of testing? I already tested Wolfgang's fix 
on a couple of systems and it works.
I tested Fred's fix for overlapping chars in GNUMail on one system and 
it works and on the other laptop where it worked it continues to work. A 
test with most GUI apps would be needed, I will try to find the time in 
the next days.


I know of no other regressions in base or gui, that's a first thing.

Of course there are still bugs, but I see no blockers and there were 
several fixes. Other do?


Riccardo


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Eric Heintzmann]

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 
> the latest release?
>
>
I suggets to make a pre-release of make|base|gui/back , and I will check. 

Thanks
Eric

___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Eric Heintzmann]

Le 16/12/2016 à 17:35, Ivan Vučica a écrit :
> On Fri, Dec 16, 2016 at 4:25 PM, Stefan Bidigaray
> mailto:stefanb...@gmail.com>> 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, Debian's current version of GNUstep base in testing
> is 1.24.9, and the package name is libgnustep-base1.24. If a new,
> 1.25 release, is pushed out, the new package name would be
> libgnustep-base1.25, and likely not accepted.
>
>
> Actually, the latest bump of -gui (to 0.25, the first release I was
> cutting) was actually pushed due to issues while doing Debian
> packaging. Eric *requested* that we bump the soname.
Yes, if there is ABI/API breakage, the soname must be bumped. I don't
think it is Debian specific.
>
> While searching for how to reply to this, I actually found Eric's
> off-list email, where he was running dpkg-gensymbols to generate this
> information.
>
> However, at this point, I am not sure how to go about running this
> type of thing myself. I could probably investigate, but short
> instructions or a pointer to useful documentation would be very
> time-saving.
>
> Preferably, I would be able to avoid doing a full binary package
> build, of course :)
>
> Rubber duck 
> tells me I could use 'nm' or 'readelf' or 'objdump', and then diff the
> output, but dpkg-gensymbols and its ilk might be doing much more.

I quote Yavor:

"Dpkg-gensymbols  can occasionally detect API additions or ABI breaks -- an
addition or removal of a function or of an entire class (or class
category).  However, that is completely unreliable because method
addition/removal (the most common case) is undetected."


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Richard Frith-Macdonald]

> 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 important fixes done by fred: they could be
> backported to stable in case?
> 
> Ok, thanks for the response to both yourself and Fred.
> 
> I am not sure what we should backport, we should probably just cut a release 
> and not worry much about a separate "stable" branch. Unless a distribution 
> packager voices interest in us doing so?
> 
> @Richard: Are you interested in cutting a -base release soon?

I have this problem that, when I did the last release I announced that it would 
be the final one of the 1.24.x sequence, and that the next one would be 1.25.0 
breaking binary compatibility ... that was because I wanted to get support for 
the debian multi-arch layout into the code (which means gnustep-make installing 
some things in slightly different places, and gnustep-base looking up resources 
differently at runtime).  Also I wanted to use the 'ng' runtime library 
designation work nicely  for turning on all the latest objc-2+ features, and I 
wanted to allow other binary compatibility breakages that people had waiting.

Due to ill health this year, I have had very little time to do any of that 
stuff, and while I made the basic changes for resource lookup, there has been 
no testing to speak of
On the other hand, this should really only effect non-flattened versions of the 
code (and most people use the flattened filesystem layout) and should not 
change the actual abi (in terms of symbols exposed in the library).  So maybe 
we could do another release in the 1.24.x series if we think the code is still 
binary compatible for practical purposes (ie the way distributions like debian 
currently build it).  I am not certain that it is though.

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 the 
latest release?



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Ivan Vučica]

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, Debian's current version of GNUstep base in testing is
> 1.24.9, and the package name is libgnustep-base1.24. If a new, 1.25
> release, is pushed out, the new package name would be libgnustep-base1.25,
> and likely not accepted.
>

Actually, the latest bump of -gui (to 0.25, the first release I was
cutting) was actually pushed due to issues while doing Debian packaging.
Eric *requested* that we bump the soname.

While searching for how to reply to this, I actually found Eric's off-list
email, where he was running dpkg-gensymbols to generate this information.

However, at this point, I am not sure how to go about running this type of
thing myself. I could probably investigate, but short instructions or a
pointer to useful documentation would be very time-saving.

Preferably, I would be able to avoid doing a full binary package build, of
course :)

Rubber duck  tells me
I could use 'nm' or 'readelf' or 'objdump', and then diff the output, but
dpkg-gensymbols and its ilk might be doing much more.
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Stefan Bidigaray]

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, Debian's current version of GNUstep base in testing is 1.24.9,
and the package name is libgnustep-base1.24. If a new, 1.25 release, is
pushed out, the new package name would be libgnustep-base1.25, and likely
not accepted.

On Dec 16, 2016 11:17, "Ivan Vučica"  wrote:


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 "transition freeze", it means that all
> ABI/API breakage will be refused by the official Debian  release team)
>

Unless I missed something significant, the API/ABI should be backwards
compatible. (I'd go through the list of changes before the release.)

Any easy way to test whether Debian will consider API/ABI breakage has
happened, which we could then add to the release docs?


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Ivan Vučica]

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 "transition freeze", it means that all
> ABI/API breakage will be refused by the official Debian  release team)
>

Unless I missed something significant, the API/ABI should be backwards
compatible. (I'd go through the list of changes before the release.)

Any easy way to test whether Debian will consider API/ABI breakage has
happened, which we could then add to the release docs?
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Eric Heintzmann]

Hi,


Le 15/12/2016 à 12:23, Ivan Vučica a écrit :
> On Wed, Dec 14, 2016, 22:47 Riccardo Mottola
> mailto:riccardo.mott...@libero.it>> 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?
>
>
> Ok, thanks for the response to both yourself and Fred.
>
> I am not sure what we should backport, we should probably just cut a
> release and not worry much about a separate "stable" branch. Unless a
> distribution packager voices interest in us doing so?
>
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 "transition freeze", it means that all
ABI/API breakage will be refused by the official Debian  release team)

Thanks
Eric


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Ivan Vučica]

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?
>

Ok, thanks for the response to both yourself and Fred.

I am not sure what we should backport, we should probably just cut a
release and not worry much about a separate "stable" branch. Unless a
distribution packager voices interest in us doing so?

@Richard: Are you interested in cutting a -base release soon?


> However, I just proved that TalkSoup crashing is caused by current
> gui... reverting to a couple of months ago (1st October) makes it work.
> I will try bisecting and understand which change(s) cause this crash.
>

Acknowledged.

I'll wait for that or try helping with that myself.

Does this happen on multiple archs/configurations?

>
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Riccardo Mottola]

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?


However, I just proved that TalkSoup crashing is caused by current 
gui... reverting to a couple of months ago (1st October) makes it work.

I will try bisecting and understand which change(s) cause this crash.

Riccardo

___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Cutting a gnustep-gui release

[Fred Kiefer]

> Am 14.12.2016 um 19:02 schrieb Ivan Vučica :
> 
> 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.

I think syncing the guy/back release with a base release is a great idea. Also 
I have a few uncommitted changes I would like to land before a release. And 
then there is the big drawing in NSBitmapImage change that I would like to 
make, but we better not wait for that…

Fred 


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Cutting a gnustep-gui release

[Ivan Vučica]

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
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: gui release?

[Fred Kiefer]

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 for all your great 
contributions to gui!


You would definitely know if gui where in code freeze :-)

Fred

___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

gui release?

[Eric Wasylishen]

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@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: Gui release

[Richard Frith-Macdonald]

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 been changed to respect the domain  
settings I
would advocate to do a base and gui release together. It would be  
rather

confusing to have base and gui behave differently.


Sounds good to me ... I think I've given up on the idea of OSX10.5 API  
compatibility in base for the next release (nobody seems to want to  
work on it), so we may as well make a new release without it.


Can we do this as new 'unstable' release branches, so that the  
unstable releases have a higher version number than the stable ones  
again?
If you want to do it as a new stable release branch, can we do a new  
unstable branch at the same time?


Also, perhaps we can release a new gnustep-make, and get gnustep-make  
to not install stuff in /usr/GNUstep/System/... by default and  
certainly not overwrite /usr/GNUstep/GNUstep.conf by default?
I know that, when make is installed, there is notionally no gnustep  
installation domain in place, so it's not installing into a particular  
domain, but for consistency it ought to act is if it is installing  
into a domain somehow ...
If you are installing it in the system domain, it should overwrite the  
file.
If you are installing it in the local domain, I guess it shouldask  
before overwriting (and back up the original)

Probably it should do the same for the network domain.
And in the user domain, it should just write a copy in the user's home  
directory, so that the use can specify it using the environment  
variable.



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Gui release

[Fred Kiefer]

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 advocate to do a base and gui release together. It would be rather
 confusing to have base and gui behave differently.

Fred


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Upcoming GUI release

[Gregory John Casamento]

All,I'd like to do an unstable release of GUI at the end of July.  Please let me know what you're working on, so that we can decide if it should go into this release or not.I am currently working on getting Nib writing support to work (to some degree) before the next release.Thanks, GJC--Gregory John Casamento___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev