[Pkg-giraffe-maintainers] current work based on branch debian/7.1/sid

[Matthias Geerdsen]

Hi Carsten,

On 05/18/2014 08:47 AM, Carsten Schoenert wrote:
> Hello Matthias,
> 
> Am 18.05.2014 01:14, schrieb Matthias Geerdsen:
>> I just imported the upstream version 7.1.9 into upstream/7.1 and
>>  filtered these two files. I merged it into the debian branch
>> and made some fixes so that the package at least builds again.
> 
> Fine! Thank you!
> 
>> It would be really cool Carsten, if you could rebase and apply 
>> your patches.
> 
> I will do of course, locally it works again. But i think you have 
> forgotten to push the tags?

of course I did at 1 AM ;) I finally pushed them this morning.

> If I tag the import commit with '7.1.9' I can successful build the
>  current version with my changes. I also have rebuild the current 
> tree with the gcc-4.9, and it looks good from the packaging side. 
> But I haven't done any package testing, hopefully Robert will
> start up the virtual containers to test the latest builds of the
> giraffe packages in the upcoming week. But I don't think there will
> be big issues.
> 
> Unfortunately the import of the last upstream version brings up
> new JS files without any sources ... It's like a hydra. :)
> 
>> E: giraffe source: source-is-missing 
>> php-webclient-ajax/client/widgets/fckeditor/editor/js/fckeditorcode_gecko.js
>>
>>
>>
>>
>>
>>
>> 
E: giraffe source: source-is-missing
php-webclient-ajax/client/widgets/fckeditor/editor/js/fckeditorcode_ie.js
> 
> I believe we should drop the hole 
> php-webclient-ajax/client/widgets/fckeditor/ directory as it we
> can link it to the fckeditor package content. I rework my commit
> that was linking to some special fckeditor things. Otherwise it
> looks good and promising. *Like* :)
> 

Sounds promising so far, at least if one generously ignores everything
that is even remotely connected to javascript ;)
Thanks for looking into the fckeditor issue!

Cheers
Matthias