Re: how to proceed with geany-plugins 0.19

2010-11-12 Thread Julien Cristau
On Sun, Oct 10, 2010 at 17:07:57 +0200, Evgeni Golov wrote: > On 10/02/2010 07:11 PM, Julien Cristau wrote: > > I added a removal hint for geany-plugins 0.18 to at least fix that issue > > for now. > > How about letting geany-plugins 0.19 go into Squeeze? It's been sitting > in Sid for 35 days, a

Re: how to proceed with geany-plugins 0.19

2010-10-10 Thread Evgeni Golov
On 10/02/2010 07:11 PM, Julien Cristau wrote: > I added a removal hint for geany-plugins 0.18 to at least fix that issue > for now. How about letting geany-plugins 0.19 go into Squeeze? It's been sitting in Sid for 35 days, and the only bug reported since then is "where is g-p in squeeze?". Adam

Re: how to proceed with geany-plugins 0.19

2010-10-02 Thread Julien Cristau
On Sun, Aug 22, 2010 at 14:57:02 +0100, Julien Cristau wrote: > On Sun, Aug 22, 2010 at 12:45:43 +0200, Evgeni Golov wrote: > > > the geany-plugins package is a compilation of plugins for the geany IDE. > > The current version in the archive (0.18) isn't compatible with the > > geany version (0.

Re: how to proceed with geany-plugins 0.19

2010-09-05 Thread Adam D. Barratt
On Sat, 2010-09-04 at 18:48 +0200, Evgeni Golov wrote: > On 09/02/2010 03:35 PM, Julien Cristau wrote: > > On Wed, Aug 25, 2010 at 12:37:23 +0200, Evgeni Golov wrote: > > > >> RT, is this ok for you? Even if it has to go through new? > >> > > Sorry for the delay. Are we missing out on a lot if we

Re: how to proceed with geany-plugins 0.19

2010-09-04 Thread Evgeni Golov
On 09/02/2010 03:35 PM, Julien Cristau wrote: > On Wed, Aug 25, 2010 at 12:37:23 +0200, Evgeni Golov wrote: > >> RT, is this ok for you? Even if it has to go through new? >> > Sorry for the delay. Are we missing out on a lot if we only ship the > existing plugins, and not the new ones? If not th

Re: how to proceed with geany-plugins 0.19

2010-09-04 Thread Chow Loong Jin
On Sunday 05,September,2010 12:48 AM, Evgeni Golov wrote: > On 09/02/2010 03:35 PM, Julien Cristau wrote: >> On Wed, Aug 25, 2010 at 12:37:23 +0200, Evgeni Golov wrote: >> >>> RT, is this ok for you? Even if it has to go through new? >>> >> Sorry for the delay. Are we missing out on a lot if we on

Re: how to proceed with geany-plugins 0.19

2010-09-02 Thread Julien Cristau
On Wed, Aug 25, 2010 at 12:37:23 +0200, Evgeni Golov wrote: > RT, is this ok for you? Even if it has to go through new? > Sorry for the delay. Are we missing out on a lot if we only ship the existing plugins, and not the new ones? If not then I think that would be best for now. Cheers, Julien

Re: how to proceed with geany-plugins 0.19

2010-08-25 Thread Evgeni Golov
On 08/22/2010 03:57 PM, Julien Cristau wrote: >> >From the users point of view, it would be best to upload ctpl (the >> missing library) and geany-plugins with all the new plugins enabled. >> However I can understand that you won't like this solution (even if >> geany-plugins and ctpl are already

Re: how to proceed with geany-plugins 0.19

2010-08-22 Thread Julien Cristau
On Sun, Aug 22, 2010 at 12:45:43 +0200, Evgeni Golov wrote: > [ please keep me CC'ed, I'm not subscribed to -release@ ] > > Dear RT, > > the geany-plugins package is a compilation of plugins for the geany IDE. > The current version in the archive (0.18) isn't compatible with the > geany version

Re: how to proceed with geany-plugins 0.19

2010-08-22 Thread Neil Williams
On Sun, 22 Aug 2010 12:45:43 +0200 Evgeni Golov wrote: > [ please keep me CC'ed, I'm not subscribed to -release@ ] > geany-plugins 0.19 ships 6 new plugins, one of which needs a yet > unpackaged (in Debian) library. For Squeeze, I'd recommend simply not packaging the one plugin which has a depe

how to proceed with geany-plugins 0.19

2010-08-22 Thread Evgeni Golov
[ please keep me CC'ed, I'm not subscribed to -release@ ] Dear RT, the geany-plugins package is a compilation of plugins for the geany IDE. The current version in the archive (0.18) isn't compatible with the geany version (0.19) in it (the plugins won't load). A binNMU won't help due to new API