Re: [Debian-med-packaging] Processed: These errors are caused by bug in libboost1.49-dev
On 05/16/2013 09:34 AM, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: reassign 708439 libboost1.49-dev Bug #708439 [src:autodock-vina] autodock-vina: FTBFS: xtime.hpp:23:5: error: expected identifier before numeric constant Bug reassigned from package 'src:autodock-vina' to 'libboost1.49-dev'. No longer marked as found in versions autodock-vina/1.1.2-2. Ignoring request to alter fixed versions of bug #708439 to the same values previously set reassign 708443 libboost1.49-dev Bug #708443 [src:dc-qt] dc-qt: FTBFS: xtime.hpp:23:5: error: expected identifier before numeric constant Bug #708445 [src:dc-qt] dc-qt: FTBFS: xtime.hpp:23:5: error: expected identifier before numeric constant Bug reassigned from package 'src:dc-qt' to 'libboost1.49-dev'. Bug reassigned from package 'src:dc-qt' to 'libboost1.49-dev'. No longer marked as found in versions dc-qt/0.2.0.alpha-4.1. No longer marked as found in versions dc-qt/0.2.0.alpha-4.1. Ignoring request to alter fixed versions of bug #708443 to the same values previously set ... Hello, Should I reassign the Bug#707416: tophat: FTBFS: as it was done with bugs above ? Or should I simply close it ? The problem with tophat is solved with the new libboost1.49-dev. Thanks, Alex -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5194b139.9080...@biotec.tu-dresden.de
Re: [Debian-med-packaging] Processed: These errors are caused by bug in libboost1.49-dev
Hi Alex, On Thu, May 16, 2013 at 12:13:13PM +0200, Alex Mestiashvili wrote: Hello, Should I reassign the Bug#707416: tophat: FTBFS: as it was done with bugs above ? Or should I simply close it ? The problem with tophat is solved with the new libboost1.49-dev. If its autofixed as you wrote in your answer I'd simply close the bug. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130516141922.gn22...@an3as.eu
Hint for some imaging software from Fedora Medical SIG
Hi, I want to draw your attention onto an extract of my posting I sended to Fedora medical SIG mailing list[1]. - Forwarded message from Andreas Tille andr...@an3as.eu - Date: Thu, 16 May 2013 11:07:54 +0200 From: Andreas Tille andr...@an3as.eu To: medical-...@lists.fedorahosted.org Subject: Re: Last updates Hi Mario, nice to hear about this success in Fedora medical SIG On Tue, May 14, 2013 at 12:24:08PM +0200, Mario Ceresa wrote: ... * Seg3D 2 - Segmentation * msvtk - Multi-scale visualization toolkit These are good hints also for Debian. We should put these on our todo list. ... An updated page with current status of all these packages is: https://fedoraproject.org/wiki/Medical_Imaging - End of extracted Forward You might like to check this Wiki page for further interesting programs besides Seg3D[2] and msvtk[3]. I might consider creating a packaging skeleton if this helps. Any takers for packaging? Kind regards Andreas. [1] https://lists.fedorahosted.org/pipermail/medical-sig/2013-May/000280.html [2] http://www.sci.utah.edu/cibc/software/42-seg3d.html (First hit at G) http://www.sci.utah.edu/software/seg3d.html (on Wiki) [3] http://www.msvtk.org/ -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130516092103.gj22...@an3as.eu
Re: Hint for some imaging software from Fedora Medical SIG
Hi Thorsten, thanks for your comments. On Thu, May 16, 2013 at 05:19:26PM +0200, Thorsten Alteholz wrote: Hi everybody, On Thu, 16 May 2013, Andreas Tille wrote: You might like to check this Wiki page for further interesting programs besides Seg3D[2] and msvtk[3]. I might consider creating a packaging skeleton if this helps. Any takers for packaging? shouldn't we begin with an entry in the task list Yes, I usually add programs were I'm pretty sure that they are useful (which is the case for both) quite soonish to the tasks. However, I somewhat stopped adding this information directly as prospective package entry. The rationale is: I need to assemble some information that is all needed in the packaging code. Since we do have the prospective package gatherer for our VCS we could easily just put this information into packaging code and let the automatic tools do their work. The advantage is that by doing so we are one step closer to a real package and there is no need in gathering the information twice. This becomes even more important if it comes to scientific citations (and Seg3D has a link to some publication). My plan is to obsolete the feature of adding citation data to the tasks files because they should rather be done in debian/upstream files to enable other use cases rather than beeing rendered on the tasks pages. In short: I'm in favour of mentioning on the tasks pages but via some (admittedly unfinished) code in VCS. and maybe a RFP-bug? I personally stopped filing RFP bugs because in my 15 years of beeing DD I do not remember that any of such bugs was closed by an upload. Usually it is noise in the BTS. I personally do not even file an ITP before I (nearly) finished the packaging in VCS. IMHO people will notice the work in VCS and considering the fact that we are really dealing with leaf packages the sense to send an ITP to avoid that somebody else is working in parallel is nearly void. From my personal perspective I regard it a good idea to issue an ITP only if I'm *really* sure that I'll be able to finally close this bug by an upload. Otherwise the same as for RFP is true. Sure, this is my personal point of view ... And if someone/Andreas is doing this, aren't the other software packages from SCI (the Seg3D developers) interesting as well? +1 to this question. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130516160302.ga21...@an3as.eu
sponsor upload aghermann-0.9.0.3 to fix #708557
Hi Yaroslav, There was a bug #708557 reported yesterday against aghermann, filed on behalf of all kfreebsd users. As I now stand accused of discrimination against these minority arches, I hasten to rectify this with 0.9.0.3, in which I accommodate the poor souls who have no mremap function in their glibc. So let us help them: http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_0.9.0.3-1.dsc Lastly, am I correct thinking that the bug in question will be automatically closed if I put the following entry in debian/changelog: aghermann (0.9.0.3-1) unstable; urgency=low * New upstream version. - fixed build on arches not providing mremap (Closes: #708557). and the build succeeds on kfreebsd-*? Cheers, Andrei signature.asc Description: PGP signature
Re: sponsor upload aghermann-0.9.0.3 to fix #708557
On Fri, 17 May 2013, andrei zavada wrote: Hi Yaroslav, There was a bug #708557 reported yesterday against aghermann, filed on behalf of all kfreebsd users. As I now stand accused of discrimination against these minority arches, I hasten to rectify this with 0.9.0.3, in which I accommodate the poor souls who have no mremap function in their glibc. And who gave an oath of non-disturbance for the next 3 weeks? ! ;) So let us help them: http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_0.9.0.3-1.dsc Lastly, am I correct thinking that the bug in question will be automatically closed if I put the following entry in debian/changelog: aghermann (0.9.0.3-1) unstable; urgency=low * New upstream version. - fixed build on arches not providing mremap (Closes: #708557). the answer to your question above would be -- YES and the build succeeds on kfreebsd-*? how would I know? have you tried this one on a kfreebsd? to not disturb the archive possibly without a reason then I will try to build it first on a local kfreebsd boxy -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130517030232.ga8...@onerussian.com
Re: sponsor upload aghermann-0.9.0.3 to fix #708557
On Thu, 16 May 2013, Yaroslav Halchenko wrote: and the build succeeds on kfreebsd-*? how would I know? have you tried this one on a kfreebsd? to not disturb the archive possibly without a reason then I will try to build it first on a local kfreebsd boxy sorry -- nope -- seems to fail at configure stage... find build.log attached (compressed) -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik build.log.gz Description: GNU Zip compressed data