Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

2016-01-25 18:27 GMT+01:00 Mattia Rizzolo :

>
> So, given that those are still warnings (that would be nice to get rid
> of), and that are for sure not blockers, what would you think about
>
uploading it as it's now and work on it on a later time?
>

I think that's a good idea, we will sort it out later. The latest upload is
available on the mentors site.
Anyway this whole procedure was a really important experience, some
modification will be done on the upstream side to.
So I hope with the next release we will move forward much faster. Thank you
for being so patient with me. :)

BR,
Gergely

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

First of all, thank you for the help. :) The new package is on the mentors
site.

2016-01-17 14:09 GMT+01:00 Mattia Rizzolo :

>
> but most importantly, I couldn't get eclipse-titan build today.
> First it failed with
>
> /usr/bin/ld: LoggerPlugin_dynamic.o: undefined reference to symbol
> 'dlclose@@GLIBC_2.2.5'
> //lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO missing from
> command line
> collect2: error: ld returned 1 exit status
> Makefile:307: recipe for target 'libttcn3-dynamic.so' failed
>
>
> Then, I added -ldl to LDFLAGS and retried, just to have
>
> Parallel_main.o: In function `main':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:203: undefined reference
> to `TCov::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:208: undefined reference
> to `TTCN_Runtime::install_signal_handlers()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:209: undefined reference
> to `TTCN_Snapshot::initialize()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:210: undefined reference
> to `TTCN_Logger::initialize_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:211: undefined reference
> to `TTCN_Logger::set_executable_name(char const*)'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:212: undefined reference
> to `TTCN_Logger::set_start_time()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:218: undefined reference
> to `Module_List::pre_init_modules()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:219: undefined reference
> to `TTCN_Runtime::hc_main(char const*, char const*, unsigned short)'
> Parallel_main.o: In function `TTCN_Runtime::is_hc()':
> /build/eclipse-titan-5.4.1/core/Runtime.hh:92: undefined reference to
> `TTCN_Runtime::executor_state'
> Parallel_main.o: In function `main':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:246: undefined reference
> to `TTCN_Runtime::restore_signal_handlers()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:247: undefined reference
> to `TTCN_Logger::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:248: undefined reference
> to `TCov::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:251: undefined reference
> to `TTCN_Logger::clear_parameters()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:252: undefined reference
> to `PORT::clear_parameters()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:253: undefined reference
> to `COMPONENT::clear_component_names()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:254: undefined reference
> to `TTCN_EncDec::clear_error()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:256: undefined reference
> to `TTCN_Logger::terminate_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:257: undefined reference
> to `TTCN_Snapshot::terminate()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:223: undefined reference
> to `COMPONENT::clear_component_names()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:226: undefined reference
> to `TTCN_Logger::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:227: undefined reference
> to `TCov::close_file()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:229: undefined reference
> to `TTCN_Logger::set_start_time()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:233: undefined reference
> to `TTCN_Runtime::ptc_main()'
> Parallel_main.o: In function `process_options':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:136: undefined reference
> to `TTCN_Runtime::install_signal_handlers()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:137: undefined reference
> to `TTCN_Logger::initialize_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:138: undefined reference
> to `Module_List::pre_init_modules()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:139: undefined reference
> to `Module_List::list_testcases()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:143: undefined reference
> to `TTCN_Logger::terminate_logger()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:157: undefined reference
> to `Module_List::print_version()'
> Parallel_main.o: In function `main':
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:231: undefined reference
> to `TTCN_Runtime::mtc_main()'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:235: undefined reference
> to `TTCN_error(char const*, ...)'
> /build/eclipse-titan-5.4.1/core/Parallel_main.cc:242: undefined reference
> to `TTCN_Logger::log_str(TTCN_Logger::Severity, char const*)'
> Parallel_main.o: In function `__static_initialization_and_destruction_0':
> /build/eclipse-titan-5.4.1/core/../common/version.h:94: undefined
> reference to `reffer::reffer(char const*)'
> Parallel_main.o: In function `JSON_Tokenizer::JSON_Tokenizer(bool)':
> /build/eclipse-titan-5.4.1/core/../common/JSON_Tokenizer.hh:115: undefined
> reference to `JSON_Tokenizer::init(char const*, unsigned long)'
> Parallel_main.o: In function `__static_initialization_and_destruction_0':
> 

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

please check the new version. I fixed a couple of things, but the remaining
ones got me...

2016-01-13 15:22 GMT+01:00 Mattia Rizzolo :

> 2)
> hardening-wrapper can just go away, the package builds fine anyway.
> The canonical way to have hardening buildflags is to export
> DEB_BUILD_MAINT_OPTIONS=hardening=+all in d/rules (instead of
> DEB_BUILD_HARDENING).
> Having a look at Makefile.cfg I see:
> * CFLAGS ain't used (instead there is a CCFLAGS variable);
> * CXXFLAGS ignores the external env.
> You may need to patch it a bit.


 hardening-wrapper wiped out, but new lintian warning showed up:
hardening-no-relro.
Tried to DEB_BUILD_MAINT_OPTIONS=hardening=+all, warning still there.
Tried to set CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) and use it
in the Makefile, same result.


> 4)
> there are a bunch of debug-file-with-no-debug-symbols and that
> postinst-has-useless-call-to-ldconfig that makes me itch.  I feel there
> is something weird going on, but I wouldn't know what it is.
>

Can't find out what's this. Checked the Makefile, the standard output, but
I can't see anything related to this.

>
> 5)
> do you even look at what lintian says on mentors?
> I: eclipse-titan source: wildcard-matches-nothing-in-dep5-copyright
> mctr2/editline (paragraph at line 5)
> I: eclipse-titan source: unused-file-paragraph-in-dep5-copyright paragraph
> at line 5
>
> the order of the paragraphs in d/copyright is important.  the wildcard
> in the second paragraph overrides the first.  so you need to swap them.
>

Switched the paragraphs, deleted unnecessary white spaces, etc... didn't
worked.
Checked every part of
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0 but
nothing. No more ideas.


> Furthermore I don't see a paragraph for debian/, as I can read it now
> the copyright for debian/* is of "Ericsson Telecom AB".
>

Is this a problem? I'm working at Ericcson, and I'm doing it as part of my
job. :)


>
>
>
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  http://mapreri.org  : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

sorry for removing the bug from my mail, won't happen again. :)
I'm trying to reproduce this:

"About ditching hardening-wrapped in favour of just using what
dpkg-buildflags do:
whatever I use the .dsc you provided, just removed hardening-wrapper or
enable the hardening build flags using DEB_BUILD_MAINT_OPTIONS, the
build fails with

In file included from jnimw.cc:8:0:
jnimw.h:14:17: fatal error: jni.h: No such file or directory
compilation terminated.
../Makefile.genrules:87: recipe for target 'jnimw.o' failed "

This is a typical error message if the compiler can't find a valid JDK on
your system. Do you have /usr/lib/jvm/default-java on your system?
It's a symlink to the default jdk: default-java -> java-1.7.0-openjdk-amd64
I think if openjdk-7-jdk is installed then then the default-java symlink
must be there.

BR,
Gergely

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

The new package is done, everything is fixed, I hope. I didn't changed
anything in the source, just under the debian/ directory. Should I upload
the package as before or use the dquilt method as
https://www.debian.org/doc/manuals/maint-guide/update suggests?
If I'm right, the update method is for the change in the upstream source,
or?

2016-01-13 12:38 GMT+01:00 Pilisi Gergely <mail.pili...@gmail.com>:

>
>
> 2016-01-13 12:24 GMT+01:00 Mattia Rizzolo <mat...@debian.org>:
>
>>
>> mattia@chase ~ % apt-file search /usr/lib/jvm/default-java
>> default-jre-headless: /usr/lib/jvm/default-java
>>
>> Indeed adding it to build-deps the package builds.
>> Make sure to do your test builds inside a clean chroot.
>>
>
> Oh, just missed this dep, thank you.
>
>
>>
>> BTW, I don't see an update package on mentors (if you meant to upload
>> one).  I can't do much if I can't see what you've done till now :)
>
>
> I want to fix everything what you asked. I'm almost done, just testing the
> copyright part. If it looks good then I'll upload the new package. ;)
> Will back to you soon.
>
>

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

2016-01-13 12:24 GMT+01:00 Mattia Rizzolo :

>
> mattia@chase ~ % apt-file search /usr/lib/jvm/default-java
> default-jre-headless: /usr/lib/jvm/default-java
>
> Indeed adding it to build-deps the package builds.
> Make sure to do your test builds inside a clean chroot.
>

Oh, just missed this dep, thank you.


>
> BTW, I don't see an update package on mentors (if you meant to upload
> one).  I can't do much if I can't see what you've done till now :)


I want to fix everything what you asked. I'm almost done, just testing the
copyright part. If it looks good then I'll upload the new package. ;)
Will back to you soon.

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

the new package is available on the mentors site:

https://mentors.debian.net/package/eclipse-titan

BR,
Gergely

2016-01-13 14:13 GMT+01:00 Gianfranco Costamagna <
costamagnagianfra...@yahoo.it>:

> Hi,
> >The new package is done, everything is fixed, I hope. I didn't changed
> anything in the source, just under the debian/ directory. Should I upload
> the package as >before or use the dquilt method as
> https://www.debian.org/doc/manuals/maint-guide/update suggests?
> >If I'm right, the update method is for the change in the upstream source,
> or?
>
>
> please read
>
> http://mentors.debian.net/intro-maintainers
>
> (TL:TR)
> gbp buildpackage -S -sa
> dput mentors ../filename_foo_source.changes
>
>
> cheers
>
> G.
>

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

just a quick report on my progress...

2015-12-17 18:18 GMT+01:00 Mattia Rizzolo :

>
> Ok, first, a question: do you do your debian packaging in git?
>

I'm cloning form a git repository, then clean up everything which is git
related. Why do you ask? Is there a problem with that?


And, here is a review:
>
> * trailing whitespace on the changelog line.
>

FIXED


> * maybe you're happy to discover tools like `wrap-and-sort`, to wrap the
>   Build-Depends and Depends line (and sort other stuff, and removing
>   trailing whitespaces in some other files)
>

Thank you for the hint, it's a really useful tool. ;)


> * please don't cp files that way in d/rules, I find that ugly. instead,
>   use a debian/eclipse-titan.install file.  See dh_install(1) for more
>   info.  On a related note, I prefer using $(CURDIR) instead of $$(pwd)
>   + this will also make debian/eclipse-titan.dirs useless
>   + if you need to rename files dh-exec can help you a bit, if you want
>

FIXED


> * during the compilation there are several errors like
> ./TTCN3.hh:58:39: fatal error: RT1/TitanLoggerApiSimple.hh: No such
> file or directory
>   is this to be expected & ok?
>

It's expected and it's OK.


> * is there a way to have a more verbose build, showing all the command
>   line?
>

Added --verbose to debian/rules, I hope it'll help.


> * you told me that you could get it to build with hardening-wrapper,
>   well, to me it doesn't (see below) :)
>

Working on it, currently I don't know what is the reason of this. :/


> * can you enable parallel building? (see debhelper(7))
>

DONE


> * debian/copyright is totally inadequate.
>   + personally I won't be totally happy without a copyright following
> copyright-format 1.0
>   + anyway, please pick a random package from the archive and try having
> a look at what a copyright file normally looks like.
>

Will do after the hardening issue is resolved.

I move forward a little bit slow because I had a lot to do in these days
but now I can work on this almost full time, so I'll back to you soon with
all these corrections done I hope. ;)

Happy New Year
Gergely Pilisi

[no subject]

[Pilisi Gergely]

Dear Mentors,

I'm struggling with the creation of a Debian package. The problem is the
hardening part. I tried everything what the Hardening Guide suggested, but
no success so far.
Lintian always throws a lot of warning  about hardening-no-relro:

Now running lintian...
W: eclipse-titan: hardening-no-relro usr/bin/compiler
W: eclipse-titan: hardening-no-relro usr/bin/mctr_cli
W: eclipse-titan: hardening-no-relro usr/bin/tcov2lcov
W: eclipse-titan: hardening-no-relro usr/bin/ttcn3_logfilter

... and so on.

Here is my debian/rules file:

#!/usr/bin/make -f
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
%:
dh $@

override_dh_auto_install:
$(MAKE) DESTDIR=$$(pwd)/debian/eclipse-titan prefix=/usr install
cp -aR $$(pwd)/Install/bin/* $$(pwd)/debian/eclipse-titan/usr/bin/
cp -aR $$(pwd)/Install/include/*
$$(pwd)/debian/eclipse-titan/usr/include/titan/
cp -aR $$(pwd)/Install/lib/* $$(pwd)/debian/eclipse-titan/usr/lib/titan/
cp -aR $$(pwd)/Install/man/man1/*
$$(pwd)/debian/eclipse-titan/usr/share/man/man1/
cp -aR $$(pwd)/Install/demo/*
$$(pwd)/debian/eclipse-titan/usr/share/titan/demo/
cp -aR $$(pwd)/Install/etc/*
$$(pwd)/debian/eclipse-titan/usr/share/titan/etc/
mv $$(pwd)/debian/eclipse-titan/usr/bin/ttcn3_archive.pl
$$(pwd)/debian/eclipse-titan/usr/share/titan/etc/scripts/
rm -fR $$(pwd)/debian/eclipse-titan/usr/share/titan/etc/asciiart/
cp -aR $$(pwd)/Install/help/*
$$(pwd)/debian/eclipse-titan/usr/share/titan/help/

I don't know what's the problem here. Can somebody help me to solve this
please?

Thank you very much!

BR,
Gergely Pilisi