Bug#744115: codeblocks is marked for autoremoval from testing
Hi Olly, On Tue, Sep 9, 2014 at 11:16 AM, Olly Betts o...@survex.com wrote: On Tue, Aug 26, 2014 at 03:55:19PM +1200, Olly Betts wrote: On Tue, Jul 01, 2014 at 02:33:51PM -0700, Vincent Cheng wrote: according to the forwarded bug report, it sounds like upstream is going to take a look at this. There's been no update on the upstream ticket for ages, so I've pinged it to see if they have made a decision on whether to make a new major release with wx3 compatibility. It's been 2 weeks and no response from upstream. This is now one of 7 packages remaining in the wxwidgets3.0 transition, and most of those have a fix in progress. We really need to move things forwards if codeblocks is to make it into jessie. Maintainers - I think it's time to just make a call on this from the Debian side, unless you have connections with upstream which can get you an answer where I can't seem to. Nope, I have no connections with upstream and have no idea what's going on with the upstream wxwidgets3.0 port. I've sort of neglected to take care of this package lately...which is a bit ironic, given that the reason I added myself as an uploader in the first place was because codeblocks was just bitrotting in the archive at the time. Would you rather package a snapshot from the upstream VCS, or try to patch the currently packaged release for wx3? We have a patch for the latter, but Vincent reported some issues with it (which I've not tried to reproduce myself, but I could take a look if you want to go that route). In case I haven't made it clear previously, you're more than welcome to NMU codeblocks; I doubt David and/or Michael would object. I'm open to patching it if it's not too intrusive, otherwise I suggest just dropping it for jessie and carrying on with the wxwidgets transition. I don't think a package with maintainers that are more or less inactive should be blocking it. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Fri, Sep 12, 2014 at 12:35:00AM -0700, Vincent Cheng wrote: In case I haven't made it clear previously, you're more than welcome to NMU codeblocks; I doubt David and/or Michael would object. I'm open to patching it if it's not too intrusive, otherwise I suggest just dropping it for jessie and carrying on with the wxwidgets transition. My main qualm about dropping it is that it seems to have a reasonable user base. And while we have other IDEs packaged (even others based on wx), they're probably not easy for a user to migrate between. But since upstream seems to have fixed this on trunk (but hasn't yet made a release with those changes), perhaps the best answer is to provide a backport to jessie once upstream make a release. I don't think a package with maintainers that are more or less inactive should be blocking it. OK, cool. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Tue, Aug 26, 2014 at 03:55:19PM +1200, Olly Betts wrote: On Tue, Jul 01, 2014 at 02:33:51PM -0700, Vincent Cheng wrote: according to the forwarded bug report, it sounds like upstream is going to take a look at this. There's been no update on the upstream ticket for ages, so I've pinged it to see if they have made a decision on whether to make a new major release with wx3 compatibility. It's been 2 weeks and no response from upstream. This is now one of 7 packages remaining in the wxwidgets3.0 transition, and most of those have a fix in progress. We really need to move things forwards if codeblocks is to make it into jessie. Maintainers - I think it's time to just make a call on this from the Debian side, unless you have connections with upstream which can get you an answer where I can't seem to. Would you rather package a snapshot from the upstream VCS, or try to patch the currently packaged release for wx3? We have a patch for the latter, but Vincent reported some issues with it (which I've not tried to reproduce myself, but I could take a look if you want to go that route). Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Tue, Jul 01, 2014 at 02:33:51PM -0700, Vincent Cheng wrote: according to the forwarded bug report, it sounds like upstream is going to take a look at this. There's been no update on the upstream ticket for ages, so I've pinged it to see if they have made a decision on whether to make a new major release with wx3 compatibility. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Sun, Jul 27, 2014 at 9:39 PM, Debian testing autoremoval watch nore...@release.debian.org wrote: codeblocks 13.12-3 is marked for autoremoval from testing on 2014-07-31 It is affected by these RC bugs: 744115: codeblocks: Please update to use wxwidgets3.0 Ping. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On 31/07/14 09:09, Vincent Cheng wrote: On Sun, Jul 27, 2014 at 9:39 PM, Debian testing autoremoval watch nore...@release.debian.org wrote: codeblocks 13.12-3 is marked for autoremoval from testing on 2014-07-31 It is affected by these RC bugs: 744115: codeblocks: Please update to use wxwidgets3.0 Ping. Have you thought about this? Olly Betts wrote: The issue there is most likely because wx 3.0 enables WXDEBUG mode by default which includes checks for incorrect API usage, whereas with wx 2.8 you had to specify it explicitly when you built the library. In other words, codeblocks is misusing the wx API, but with 2.8 this gets quietly ignored by default, whereas 3.0 reports it by default. I bet if you rebuilt codeblocks using the WXDEBUG build of 2.8 (available in Debian in package libwxgtk2.8-dbg - despite the name, this isn't debug symbols, but a separate build of the library) you'd see this assertion too. The simplest way to address this is to build codeblocks with -DNDEBUG (pass it in CPPFLAGS usually), which makes wx 3.0 behave as a default build of 2.8 would. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Mon, Jul 7, 2014 at 9:39 PM, Debian testing autoremoval watch nore...@release.debian.org wrote: codeblocks 13.12-3 is marked for autoremoval from testing on 2014-07-16 It is affected by these RC bugs: 744115: codeblocks: Please update to use wxwidgets3.0 Ping... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Tue, Jun 17, 2014 at 9:39 PM, Debian testing autoremoval watch nore...@release.debian.org wrote: codeblocks 13.12-3 is marked for autoremoval from testing on 2014-07-02 It is affected by these RC bugs: 744115: codeblocks: Please update to use wxwidgets3.0 Pinging this bug report again to delay autoremoval; according to the forwarded bug report, it sounds like upstream is going to take a look at this. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Mon, Jun 16, 2014 at 9:11 PM, Olly Betts o...@survex.com wrote: On Mon, Jun 16, 2014 at 08:59:33PM -0700, Vincent Cheng wrote: This fell off my radar, sorry! Pinging the bug report to delay autoremoval from testing. It would be nice if you also actually responded to my last message (which I sent over 2 months ago). For your convenience I repeat it here: Sorry, must have missed that as well! --- I just tried to reproduce the issue described in #736368 using my 13.12-3.1 build, but I couldn't follow the steps described: | If I open a .c file, Ctrl+O and enter a path to a C file - OK | double click on a variable to mark it, Double click on a variable in the pane with the source code in - OK. | right click Menu appears - OK. | and selects from the menu permanentely highlight variable There's no such entry in the menu I have (or in any of its submenus). You'll need to install codeblocks-contrib first (the permanently highlight variable function is implemented as a plugin). I can reproduce the bug with codeblocks/13.12-1 (built with wx 3.0), but not codeblocks/13.12-3 (built with wx 2.8). Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
forwarded 744115 https://sourceforge.net/p/codeblocks/tickets/17/ thanks On Wed, May 28, 2014 at 9:39 PM, Debian testing autoremoval watch nore...@release.debian.org wrote: codeblocks 13.12-3 is marked for autoremoval from testing on 2014-06-13 It is affected by these RC bugs: 744115: codeblocks: Please update to use wxwidgets3.0 This fell off my radar, sorry! Pinging the bug report to delay autoremoval from testing. I did have a bug report on upstream's old Berlios bug tracker, but that got closed down a while ago, so marking this as forwarded to upstream's new sourceforge tracker. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks is marked for autoremoval from testing
On Mon, Jun 16, 2014 at 08:59:33PM -0700, Vincent Cheng wrote: This fell off my radar, sorry! Pinging the bug report to delay autoremoval from testing. It would be nice if you also actually responded to my last message (which I sent over 2 months ago). For your convenience I repeat it here: --- I just tried to reproduce the issue described in #736368 using my 13.12-3.1 build, but I couldn't follow the steps described: | If I open a .c file, Ctrl+O and enter a path to a C file - OK | double click on a variable to mark it, Double click on a variable in the pane with the source code in - OK. | right click Menu appears - OK. | and selects from the menu permanentely highlight variable There's no such entry in the menu I have (or in any of its submenus). --- Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
