Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
[ Re-sent to the right recipients. ] On Tue, Jun 07, 2011 at 02:03:58AM +0300, Yavor Doganov wrote: All new versions of the core GNUstep packages are already in experimental. A routine rebuild revealed only 6 bugs, all of them having a fix available now: http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tagusers=pkg-gnustep-maintain...@lists.alioth.debian.orgdata=gnustep-base1.22-transition I added blocking bugs to the transition bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629477 They need to be handled before the transition can proceed further. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On Mon, Sep 05, 2011 at 08:37:35PM +0200, Julien Cristau wrote: We'd like to have a list of packages which are part of this transition. Dependency level 1 (build-depends only on libgnustep-base-dev): biococoa gnustep-netclasses mknfonts.tool oolite pantomime1.2 Dependency level 2 (build-depends on libgnustep-gui-dev): aclock.app addresses-for-gnustep adun.app affiche batmon.app biococoa.app camera.app cenon.app charmap.app cynthiune.app easydiff.app edenmath.app etoile ftp.app gnustep-examples gomoku.app gorm.app gridlock.app grr.app gtamsanalyzer.app helpviewer.app lusernet.app (also b-d on libpantomime1.2) lynkeos.app mines.app mpdcon.app paje.app plopfolio.app poe.app popplerkit.framework preview.app price.app projectcenter.app projectmanager.app renaissance shisen.app stepbill.app systempreferences.app talksoup.app (also b-d on libnetclasses-dev) terminal.app textedit.app timemon.app volumecontrol.app wrapperfactory.app Dependency level 3 (gnustep-gui + at least one GUI-based ObjC library) agenda.app (b-d on libaddresses-dev) gnumail (b-d on libaddresses-dev, libaddressview-dev, libpantomime1.2-dev) gnustep-dl2 (b-d on librenaissance0-dev, gorm.app) gworkspace (b-d on libpopplerkit-dev) viewpdf.app (b-d on libpopplerkit-dev) zipper.app (b-d on librenaissance0-dev) Dependency level 4 (gnustep-gui + a library from level 3) steptalk (b-d on libgnustep-dl2-dev) Either as an explicit list, or a description such as 'build-depends on foo or bar'. And then a way to check whether such a package is transitioned or not, e.g. 'depends on libfooX' vs 'depends on libfooY'. libgnustep-base1.20 vs libgnustep-base1.22 libgnustep-gui0.18 vs libgnustep-gui0.20 Please let me know if further information is required. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On Thu, Sep 08, 2011 at 10:48:57AM +0300, Yavor Doganov wrote: On Mon, Sep 05, 2011 at 08:37:35PM +0200, Julien Cristau wrote: We'd like to have a list of packages which are part of this transition. […] libgnustep-base1.20 vs libgnustep-base1.22 libgnustep-gui0.18 vs libgnustep-gui0.20 Ok, thanks, please go ahead. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
At Thu, 25 Aug 2011 21:39:10 +0200, Julien Cristau wrote: On Thu, Aug 18, 2011 at 12:13:47 +0200, Philipp Kern wrote: On Tue, Jun 07, 2011 at 02:03:58AM +0300, Yavor Doganov wrote: We would like to carry out a GNUstep transition (libgnustep-base1.20-1.22; libgnustep-gui0.18-0.20) *and* libobjc2-3, ideally coinciding with the migration of gcc-defaults to testing (or even better, before that). That seems pretty complex to check with our existing tools. But to get an overview, can you please tell us the relevant development packages people are build-depending on? And a list of affected packages to check the result. Ping? Apologies for the delay. I'm afraid I don't understand the question -- do you want a list of other (non-GNUstep) libraries possibly affecting the transition (poppler, ffmpeg, etc.) or you'd like to know which of the GNUstep packages depend on gnustep-gui and which only on gnustep-base? The GNU ObjC runtime (libobjc3) doesn't have a development package; any GNUstep package built with the current toolchain ends up linking against it, which inevitably leads to a crash when the program is being run. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On Mon, Sep 5, 2011 at 19:34:46 +0300, Yavor Doganov wrote: I'm afraid I don't understand the question -- do you want a list of other (non-GNUstep) libraries possibly affecting the transition (poppler, ffmpeg, etc.) or you'd like to know which of the GNUstep packages depend on gnustep-gui and which only on gnustep-base? We'd like to have a list of packages which are part of this transition. Either as an explicit list, or a description such as 'build-depends on foo or bar'. And then a way to check whether such a package is transitioned or not, e.g. 'depends on libfooX' vs 'depends on libfooY'. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On Thu, Aug 18, 2011 at 12:13:47 +0200, Philipp Kern wrote: On Tue, Jun 07, 2011 at 02:03:58AM +0300, Yavor Doganov wrote: We would like to carry out a GNUstep transition (libgnustep-base1.20-1.22; libgnustep-gui0.18-0.20) *and* libobjc2-3, ideally coinciding with the migration of gcc-defaults to testing (or even better, before that). That seems pretty complex to check with our existing tools. But to get an overview, can you please tell us the relevant development packages people are build-depending on? And a list of affected packages to check the result. Ping? Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On Tue, Jun 07, 2011 at 02:03:58AM +0300, Yavor Doganov wrote: We would like to carry out a GNUstep transition (libgnustep-base1.20-1.22; libgnustep-gui0.18-0.20) *and* libobjc2-3, ideally coinciding with the migration of gcc-defaults to testing (or even better, before that). That seems pretty complex to check with our existing tools. But to get an overview, can you please tell us the relevant development packages people are build-depending on? And a list of affected packages to check the result. Kind regards and thanks Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On 06/08/2011 08:19 PM, Yavor Doganov wrote: Julien Cristau wrote: On Tue, Jun 7, 2011 at 21:44:15 +0300, Yavor Doganov wrote: 1) The modified gnustep-make package will have no trouble migrating to testing (before the transition even commences), so it would make GNUstep development in wheezy broken, just like it is now in sid. Broken how? Packages end up linking with libobjc3, while -base and -gui are linked with libobjc2. is there any update on this? first packages are now linked against libobjc3 and the existing GNUstep libraries. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
Hi, I've a hard time understanding what the current status of this transition is. Anyone willing to sum up? (I'm interested in it as it blocks #619602 - ITP: theunarchiver.) Bye, -- intrigeri intrig...@boum.org | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc | If you must label the absolute, use it's proper name: Temporary. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On Tue, Jun 7, 2011 at 21:44:15 +0300, Yavor Doganov wrote: 1) The modified gnustep-make package will have no trouble migrating to testing (before the transition even commences), so it would make GNUstep development in wheezy broken, just like it is now in sid. Broken how? 2) Building the GNUstep packages with the non-default compiler on ia64 and sparc is, strictly speaking, a policy violation. What part of policy? Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
Julien Cristau wrote: On Tue, Jun 7, 2011 at 21:44:15 +0300, Yavor Doganov wrote: 1) The modified gnustep-make package will have no trouble migrating to testing (before the transition even commences), so it would make GNUstep development in wheezy broken, just like it is now in sid. Broken how? Packages end up linking with libobjc3, while -base and -gui are linked with libobjc2. 2) Building the GNUstep packages with the non-default compiler on ia64 and sparc is, strictly speaking, a policy violation. What part of policy? None; it appears I am making a mistake. I was pretty sure that there was something like Packages should be built with the default compiler, but it seems I was wrong. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On 06/07/2011 01:33 AM, Yavor Doganov wrote: Matthias Klose wrote: On 06/07/2011 01:03 AM, Yavor Doganov wrote: We would like to carry out a GNUstep transition (libgnustep-base1.20-1.22; libgnustep-gui0.18-0.20) *and* libobjc2-3, ideally coinciding with the migration of gcc-defaults to testing (or even better, before that). please make sure that you either use gobjc-4.6 explicitly, or that you allow differing defaults depending on the platform. gnustep-base/1.22.0-1 currently build-depends on gobjc (= 4:4.6). My plan was to change it to gobjc (= 4:4.6) [!ia64 !sparc], gobjc-4.6. Is that good enough? no, for that case, you need to use gcc-4.6 as the driver. If you want to do this, maybe make the change in gnustep-make and let the gnustep-make package depend on gcc-4.6. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
Matthias Klose wrote: On 06/07/2011 01:33 AM, Yavor Doganov wrote: gnustep-base/1.22.0-1 currently build-depends on gobjc (= 4:4.6). My plan was to change it to gobjc (= 4:4.6) [!ia64 !sparc], gobjc-4.6. Is that good enough? no, for that case, you need to use gcc-4.6 as the driver. If you want to do this, maybe make the change in gnustep-make and let the gnustep-make package depend on gcc-4.6. Two questions arise: 1) The modified gnustep-make package will have no trouble migrating to testing (before the transition even commences), so it would make GNUstep development in wheezy broken, just like it is now in sid. 2) Building the GNUstep packages with the non-default compiler on ia64 and sparc is, strictly speaking, a policy violation. If the release team does not object, we can go on and make gobjc-4.6 a strict requirement via gnustep-make. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition We would like to carry out a GNUstep transition (libgnustep-base1.20-1.22; libgnustep-gui0.18-0.20) *and* libobjc2-3, ideally coinciding with the migration of gcc-defaults to testing (or even better, before that). All new versions of the core GNUstep packages are already in experimental. A routine rebuild revealed only 6 bugs, all of them having a fix available now: http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tagusers=pkg-gnustep-maintain...@lists.alioth.debian.orgdata=gnustep-base1.22-transition The latest stable upstream release of gnustep-base (1.22.0) includes support for the new (modernized) Objective-C runtime in GCC 4.6 (libobjc3). About 3 months ago, the GCC maintainers asked us to postpone any GNUstep transitions until libobjc3 is available in unstable [*]; now the transition is inevitable because gcc-4.6 is the default compiler on most archs. [*] http://permalink.gmane.org/gmane.linux.debian.devel.gcc/37170 Expected problems: * gnustep-base now depends on ICU and is thus tied to future ICU transitions. * gcc-4.5 is still the default compiler on ia64 and sparc. As immediate solution, I intend to add (temporarily) gobjc-4.6 to gnustep-base' Build-Depends; that way the packages will still be built with the default compiler (4.5), but the new ObjC runtime will be used. * A few runtime bugs may pop-up as usual, and as per Murphy's Law will be discovered post-factum. I hope we can deal with them in due time, unless there is a scary arch-specific issue like the hppa excitement during the last transition. TBH, I am quite surprised by the low number of bugs so far as they hardly correspond to the drastic changes in -base. It makes me feel somewhat uneasy; we're used to battle with a lot more problems. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
On 06/07/2011 01:03 AM, Yavor Doganov wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition We would like to carry out a GNUstep transition (libgnustep-base1.20-1.22; libgnustep-gui0.18-0.20) *and* libobjc2-3, ideally coinciding with the migration of gcc-defaults to testing (or even better, before that). please make sure that you either use gobjc-4.6 explicitly, or that you allow differing defaults depending on the platform. * gcc-4.5 is still the default compiler on ia64 and sparc. As immediate solution, I intend to add (temporarily) gobjc-4.6 to gnustep-base' Build-Depends; that way the packages will still be built with the default compiler (4.5), but the new ObjC runtime will be used. it's 4.4. this transition should wait (for unstable) until the multiarch enabled GCC packages are in testing. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629477: transition: gnustep-base, gnustep-gui, libobjc
Matthias Klose wrote: On 06/07/2011 01:03 AM, Yavor Doganov wrote: We would like to carry out a GNUstep transition (libgnustep-base1.20-1.22; libgnustep-gui0.18-0.20) *and* libobjc2-3, ideally coinciding with the migration of gcc-defaults to testing (or even better, before that). please make sure that you either use gobjc-4.6 explicitly, or that you allow differing defaults depending on the platform. gnustep-base/1.22.0-1 currently build-depends on gobjc (= 4:4.6). My plan was to change it to gobjc (= 4:4.6) [!ia64 !sparc], gobjc-4.6. Is that good enough? * gcc-4.5 is still the default compiler on ia64 and sparc. it's 4.4. I stand corrected; it doesn't make any difference, I guess. this transition should wait (for unstable) until the multiarch enabled GCC packages are in testing. OK. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
