Bug#1030752: request 8.3.0 to be packaged. 8.2.0 is known broken

2023-02-13 Thread Pilisi Gergely
Hi Harald, thanks for the update. I forwarded your bugreport to the leader of Titan Team, maybe he will ask some questions about the regression issues with 8.2.0. I'll create a 8.3.0 package for you soon. BR, Greg Harald Welte ezt írta (időpont: 2023. febr. 7., K, 10:36): > Package:

Bug#1000956: update eclipse-titan to upstream 8.0.0 or 8.1.0

2021-12-01 Thread Pilisi Gergely
Hi Harald, there was some misunderstanding here. Elemer has left the Titan team and the new manager didn't know enough about the Debian release process, so nobody asked me to create a new package. We just clarified the situation and everything will be smoother in the future. Actually the newest

Bug#954999: eclipse-titan still encodes an upper dependency on gcc

2020-07-12 Thread Pilisi Gergely
Hi, the new version of Titan (7.1.1) will tolerate the version change of the compiler. Here is the detailed forum post about this: https://www.eclipse.org/forums/index.php/t/1104359/ BR, Greg Adrian Bunk ezt írta (időpont: 2020. ápr. 24., P, 12:09): > On Thu, Mar 26, 2020 at 04:52:42PM

Bug#949102: eclipse-titan: FTBFS: fails to resolve the local hostname

2020-01-21 Thread Pilisi Gergely
Got it, thanks! Then the change will come with the next release. Mattia Rizzolo ezt írta (időpont: 2020. jan. 21., K 17:50): > On Tue, Jan 21, 2020 at 05:48:42PM +0100, Pilisi Gergely wrote: > > Upstream has modified the script, so if the nslookup fails, then it will > > try

Bug#949102: eclipse-titan: FTBFS: fails to resolve the local hostname

2020-01-21 Thread Pilisi Gergely
Fri, Jan 17, 2020 at 11:33:23AM +0100, Pilisi Gergely wrote: > > I'll contact upstream first, they should know about this. Will be back > soon > > with the solution. > > Thanks. Just a note on the urgency: it isn't at all. > The official buildds seems able to resolve their

Bug#949102: eclipse-titan: FTBFS: fails to resolve the local hostname

2020-01-17 Thread Pilisi Gergely
Hi, Mattia Rizzolo ezt írta (időpont: 2020. jan. 16., Cs, 23:30): > > your package failed to rebuild in a standard sid/amd64 chroot. > > It seems it's trying to resolve the hostname of the box (i.e. > `nslookup $HOSTNAME`) and failing. Alas, I don't think there is a > consensus of whether

Bug#936464: eclipse-titan: diff for NMU version 6.6.0-1.1

2020-01-12 Thread Pilisi Gergely
Hi, thank you for your upload. Currently I'm preparing the 6.6.1 version without python2 dependency. But we still need python3 because the package installs a python script to this path: /usr/share/titan/etc/scripts So I suggest to use python3 instead of completely removing this dependency. BR,

Bug#879816: The bug just happened *again*

2018-08-26 Thread Pilisi Gergely
Hi, the new release will fix this, in just a couple of weeks. You can check the related commit on GitHUB: https://github.com/eclipse/titan.core/commit/425a11165fa7b88ca36ca363fc714432e46822fb Please standby. BR, Gergely Pilisi Harald Welte ezt írta (időpont: 2018. aug. 25., Szo, 12:57): >

Bug#879816: the gcc check is by design, won't be patched out

2018-08-04 Thread Pilisi Gergely
Upstream information: Sadly the situation is not that simple. In the past we have run into several situations when surprisingly small differences in gcc made it binary incompatible. For example at one of our users had “gcc 4.1.2 20070115 (prerelease) (SUSE Linux)” we had built titan for “gcc

Bug#901463: will be fixed soon

2018-08-04 Thread Pilisi Gergely
Upstream information: Decision was taken to migrate the documentation to asciidoc; work is ongoing, it will be started with test ports and protocol modules; ETA is end of 2018.

Bug#884303: not a bug

2018-08-04 Thread Pilisi Gergely
Upstream information: The assumption with the Makefile is always that it needs to be adjusted manually to a lesser or greater degree. It was never meant to be fully automated; this might change in the future but it will need some development that is not on our roadmap for this year.

Bug#879816: eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0

2018-01-31 Thread Pilisi Gergely
Hi, I'll try the patch to keep the gcc dependency. I'll also ask upstream about the version check strictness. 2018-01-30 16:45 GMT+01:00 Harald Welte : > Hi! > > The problem just re-appeared as gcc was updated to 7.3.0 in unstable: > > g++ -c -DLINUX -I/usr/include

Bug#883071: [release.debian.org] need to recompile eclipse-titan (6.1.0-1) in stable

2017-11-29 Thread Pilisi Gergely
2017-11-29 11:55 GMT+01:00 Adam D. Barratt : > > Please use "reportbug release.debian.org" when filing such bugs, it will > automatically set most of the metadata correctly for you. > > I did. After 5 attempts I gave up. It couldn't send the email via my gmail account,

Bug#883071: [release.debian.org] need to recompile eclipse-titan (6.1.0-1) in stable

2017-11-29 Thread Pilisi Gergely
Package: release.debian.org Severity: grave --- Please enter the report below this line. --- The Titan compiler needs the same gcc version (major.minor) which compiled the eclipse/titan binaries. When the package was built for stretch, the gcc version was 6.2.x, now it is 6.3.x Now if the user

Bug#879816: eclipse-titan depends on gcc-6.3.0, but unstable has gcc-7.2.0

2017-10-28 Thread Pilisi Gergely
Hi Harald, I know it's a big problem, and working on the solution. This issue is a bit strange, 'cause the compiler should accept gcc 6.2.1 too, not just 6.2.0. Titan only checks the first two version numbers (major and minor), but the third level (change) is not important. I'm investigating

Bug#879815: Acknowledgement (eclipse-titan not installable on current stretch/amd64)

2017-10-27 Thread Pilisi Gergely
Hi, first of all, thank you for the bug report. I really love to hear about eclipse-titan, because it's an important project for me. :) The next release is coming soon, it will close the bug report if it's still open. BR, Gergely Pilisi 2017-10-26 14:11 GMT+02:00 Harald Welte

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

2016-01-26 Thread 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

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

2016-01-22 Thread 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

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

2016-01-14 Thread 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

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

2016-01-13 Thread 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

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

2016-01-13 Thread Pilisi Gergely
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 >> defau

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

2016-01-13 Thread 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,

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

2016-01-13 Thread 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

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

2016-01-11 Thread 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