[Pkg-ace-devel] Bug#746825: ACE+TAO 6.2.7

Pau Garcia i Quiles pgquiles at elpauer.org
Mon Jul 7 22:00:59 UTC 2014


On Mon, Jun 30, 2014 at 8:42 AM, Johnny Willemsen <jwillemsen at remedy.nl>
wrote:

> The large file support warning is easy to fix if MPC supports some
>
>> kind of "test" feature. I implemented that in CMake script for Wt a
>> while ago:
>>
>> https://github.com/pgquiles/wt/commit/90d5bfeb5f87232a8f074e2c7fe7eb
>> 0a92dd6d58
>>
>
> With MPC we can't do that, it would mean we compile this with each
> program. Maybe we can use some template meta programming to determine the
> size?
>
>

What we need is to try to compile the same small C program with different
preprocessor macros (-D_LARGEFILE_SOURCE, -DFILE_OFFSET_BITS=64, etc) to
determine which one we should pass in every call to gcc. I think template
metaprogramming won't help here.



>
>  The only thing that I am actually worried about is the licensing issue
>> with OpenSSL. If lintian is complaining, most probably GPL-code is
>> transitively being linked to OpenSSL, thus causing a licensing
>> problem.
>>
>
> To my idea this is not the case, the only GPL part I know is ace_gperf,
> that isn't linked with anything.
>
>
You are right. Apparently what was causing the problem was the
Bison-generated code but it's covered by the Bison GPL-exception.



> The Sun part is still part of TAO_IDL. That license is probably now owned
> by MicroFocus which bought all progress orbs some time ago. Another option
> is to replace TAO_IDL with RIDLC with a new C++ backend, but that will be a
> significant amount of work, that is something that has to be funded by
> someone.
>
>

:-(



> At the moment you have everything compiling, could you document the steps
> to provide a new release to debian, than we can integrate a future release
> into the debian as part of the release progress.
>
>
Far too many steps are still manual.

In particular, cleaning all the complaints by lintian will take quite some
work, and I think we will not get ACE into Debian until lintian reports
zero warnings. I am slowly going through them but there are two which are
causing me a nightmare:

- Hardening binaries. I'm trying to figure how to force MPC to take the gcc
hardening flags.

- Large-file support. I can check for the right flag in debian/rules,
outside MPC , and just pass MPC the proper flag, but I feel it's not the
proper way. Any idea?






> Thanks for your work.
>
> Johnny
>
>
>
>>
>>
>> On Sun, Jun 29, 2014 at 10:30 PM, Pau Garcia i Quiles
>> <pgquiles at elpauer.org> wrote:
>>
>>> Hello,
>>>
>>> Sure, I'll dump lintian output to a file and upload it. Still compiling
>>> :-)
>>>
>>> On Sun, Jun 29, 2014 at 10:28 PM, Johnny Willemsen <jwillemsen at remedy.nl>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Are you able to share the warnings, maybe host them somewhere?
>>>>
>>>> Johnny
>>>>
>>>> Op zondag 29 juni 2014 heeft Pau Garcia i Quiles <pgquiles at elpauer.org>
>>>> het
>>>> volgende geschreven:
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> Yes, it did but apparently I didn't notice :-/ In fact, it's been so
>>>>> long since I did anything in ACE packaging that my packaging for 6.2.7
>>>>> (available in pgquiles-6.2.7-wrong) was missing some of my own changes
>>>>> in git from a long time ago (!!!)
>>>>>
>>>>> I have taken your branch, fixed a few unimportant issues, and added
>>>>> the useful parts from my branch: lintian overrides, fix some typos,
>>>>> remove privacy breach complaints and little more. It's available in
>>>>> the jwi+pgquiles-6.2.7 branch (building right now for the first time).
>>>>> There is still quite some work to do to clean all the lintian
>>>>> warnings, especially in regards to large file support
>>>>> (_FILE_OFFSET_BITS=64, etc).
>>>>>
>>>>> Also, what is the licensing issue with TAO that Steven Hartmann
>>>>> mentioned in the 6.2.7 thread? The Sun-licensed files? I seem to
>>>>> remember something from a long time ago but I cannot find the
>>>>> specifics, only this from Fedora:
>>>>>
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=450164
>>>>>
>>>>> And lintian is also complaining about mixed OpenSSL + GPL code but I
>>>>> have not verified yet:
>>>>>
>>>>> E: libtao-orbsvcs-2.2.7: possible-gpl-code-linked-with-openssl
>>>>> N:
>>>>> N:    This package appears to be covered by the GNU GPL but depends on
>>>>> the
>>>>> N:    OpenSSL libssl package and does not mention a license exemption
>>>>> or
>>>>> N:    exception for OpenSSL in its copyright file. The GPL (including
>>>>> version
>>>>> N:    3) is incompatible with some terms of the OpenSSL license, and
>>>>> therefore
>>>>> N:    Debian does not allow GPL-licensed code linked with OpenSSL
>>>>> libraries
>>>>> N:    unless there is a license exception explicitly permitting this.
>>>>> N:
>>>>> N:    If only the Debian packaging, or some other part of the package
>>>>> not
>>>>> N:    linked with OpenSSL, is covered by the GNU GPL, please add a
>>>>> lintian
>>>>> N:    override for this tag. Lintian currently has no good way of
>>>>> N:    distinguishing between that case and problematic packages.
>>>>> N:
>>>>> N:    Severity: serious, Certainty: wild-guess
>>>>> N:
>>>>> N:    Check: copyright-file, Type: binary
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Jun 29, 2014 at 8:45 PM, Johnny Willemsen <
>>>>> jwillemsen at remedy.nl>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Did post that on the list, didn't that post got through it?
>>>>>>
>>>>>> Johnny
>>>>>>
>>>>>> Op zondag 29 juni 2014 heeft Pau Garcia i Quiles <
>>>>>> pgquiles at elpauer.org>
>>>>>> het
>>>>>> volgende geschreven:
>>>>>>
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> No, I started from the 6.1.2 packaging. I didn't know you had started
>>>>>>> work on a branch :-/ I'll check
>>>>>>>
>>>>>>> On Sun, Jun 29, 2014 at 6:13 PM, Johnny Willemsen
>>>>>>> <jwillemsen at remedy.nl>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Great, did you use the branch I created earlier this week?
>>>>>>>>
>>>>>>>> Johnny
>>>>>>>>
>>>>>>>> Op zondag 29 juni 2014 heeft Pau Garcia i Quiles
>>>>>>>> <pgquiles at elpauer.org>
>>>>>>>> het
>>>>>>>> volgende geschreven:
>>>>>>>>
>>>>>>>>  Hello,
>>>>>>>>>
>>>>>>>>> I am packaging ACE+TAO 6.2.7, which should solve #746825
>>>>>>>>>
>>>>>>>>> Packaging is done. Now I need to do some QA. There are hundreds of
>>>>>>>>> lintian issues, some of them serious (e. g. a licensing problem
>>>>>>>>> with
>>>>>>>>> OpenSSL).
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Pau Garcia i Quiles
>>>>>>>>> http://www.elpauer.org
>>>>>>>>> (Due to my workload, I may need 10 days to answer)
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Pkg-ace-devel mailing list
>>>>>>>>> Pkg-ace-devel at lists.alioth.debian.org
>>>>>>>>>
>>>>>>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
>>>>>>>>> pkg-ace-devel
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Pau Garcia i Quiles
>>>>>>> http://www.elpauer.org
>>>>>>> (Due to my workload, I may need 10 days to answer)
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Pau Garcia i Quiles
>>>>> http://www.elpauer.org
>>>>> (Due to my workload, I may need 10 days to answer)
>>>>>
>>>>
>>>
>>>
>>> --
>>> Pau Garcia i Quiles
>>> http://www.elpauer.org
>>> (Due to my workload, I may need 10 days to answer)
>>>
>>
>>
>>
>>  Hi,
>
>


-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-ace-devel/attachments/20140708/4d049e82/attachment.html>


More information about the Pkg-ace-devel mailing list