Dear Markus, Please rename the previous ebuild to "itpp-3.10.4.ebuild" in order to bump the latest stable version of IT++. The latest release is mainly related to bugs found under MS Visual C++, so almost nothing changed from the Gentoo Linux perspective. Thanks in advance! BR, /ediap PS. I hope you remember about stabilisation procedure of itpp-3.10.3
Hi Adam, Thanks for the heads up and itpp-3.10.4 is in portage now. I've got the stabilization in my calendar for the upcoming weekend and will post a stabilization request to the x86 arch team and make sure to cc you on it. Thanks, Markus
Thanks for bumping IT++ to version 3.10.4. Unfortunately, I would like to request another bump of the ebuild into release 3.10.5. During last week, we managed to fix two important bugs, reported quite a long time ago. Therefore, we decided to release the next bug-fix version only one week after 3.10.4 was released. Since no interface changes have been done, a simple rename of the ebuild should suffice. BTW, thanks for your stabilisation request to x86 team. I guess, we have to wait with a stabilisation of version 3.10.5 for some time, starting from the moment it enters the portage tree. Anyway, I recommend this step due to the bugs we recently fixed in the library. BR, /ediap
Hi Adam, Thank you very much for your note! I just committed the ebuild for itpp-3.10.5 to portage cvs. Thanks, Markus
Hi Markus, Could you please consider asking the x86 team for marking the itpp-3.10.5 stable? This version is in portage since August the 15th, and no bugs have been reported since then. From the upstream perspective, this release fixed a few important bugs in communications module, which is one of the most commonly used part of the IT++ library. Thanks in advance! BR, /Adam
Hi Adam, Thanks for the note and I'll contact the x86 team as soon as the 30 day stabilization period is up. I hope that is early enough. Best, Markus
(In reply to comment #5) > Thanks for the note and I'll contact the x86 team as soon as > the 30 day stabilization period is up. I hope that is early enough. Sure! That's fine. However, it's a pity, there is no interest from other archs in testing and keywording itpp. BR, /Adam
Hi Adam, I don't think it is disinterest, but mostly the fact that the stabling of gcc-4.1.1 has taken a significant toll on all arch teams and moving a packages into ~arch probably isn't highest priority at the moment ;-). I think cryos has several amd dev boxes and I'll drop him an email to ask if he has time to do it. Best, Markus
Hi Markus, (In reply to comment #7) > I don't think it is disinterest, but mostly the fact > that the stabling of gcc-4.1.1 has taken a significant > toll on all arch teams and moving a packages into ~arch > probably isn't highest priority at the moment ;-). You are right... The migration from gcc-3.4 to gcc-4.1 caused a lot of work for devs. Besides, I think the IT++ library is a very specific kind of software, which is not commonly used, and therefore there is not too big interest for it. > I think cryos has several amd dev boxes and I'll drop him an > email to ask if he has time to do it. That's great! Thanks! BR, /Adam PS. Should you need any assistance in testing {blas,lapack}-atlas ebuilds you are going to work on this week, please let me know.
Hi Markus, Knock, knock... (In reply to comment #5) > Hi Adam, > > Thanks for the note and I'll contact the x86 team as soon as > the 30 day stabilization period is up. I hope that is early enough. > > Best, > Markus Just to refresh you memory a little bit ;-) BR, /Adam
Yeah, thanks and sorry for the delay! I haven't forgotten, but got bogged down with other things. I'll do it this weekend! Best, Markus