Your message dated Sun, 01 May 2011 00:28:09 +0200 with message-id <4DBC8CF9.2010307@dogguy.org> and subject line Re: Bug#623719: nmu: Please bin nmu the following for a SONAME bump of libmuparser has caused the Debian Bug report #623719, regarding transition: muparser to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 623719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623719 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nmu: Please bin nmu the following for a SONAME bump of libmuparser
- From: Scott Howard <showard314@gmail.com>
- Date: Mon, 07 Mar 2011 05:49:05 -0500
- Message-id: <[🔎] 20110307104904.2045.12437.reportbug@debian-scott.sk1m>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: binnmu nmu libgetfem4++_4.1.1-2 . ALL . -m "Build against new libmuparser0debian1" nmu meshlab_1.3.0a+dfsg1-1 . ALL . -m "Build against new libmuparser0debian1" nmu ovito_0.9.2-1 . ALL . -m "Build against new libmuparser0debian1" nmu scidavis_0.2.4-3 . ALL . -m "Build against new libmuparser0debian1" For reference see: BTS bug 606120 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
--- End Message ---
--- Begin Message ---
- To: Scott Howard <showard314@gmail.com>, 623719-done@bugs.debian.org
- Cc: Julien Cristau <jcristau@debian.org>
- Subject: Re: Bug#623719: nmu: Please bin nmu the following for a SONAME bump of libmuparser
- From: Mehdi Dogguy <mehdi@dogguy.org>
- Date: Sun, 01 May 2011 00:28:09 +0200
- Message-id: <4DBC8CF9.2010307@dogguy.org>
- In-reply-to: <[🔎] BANLkTincj_VXnfv+0VOiT-Hvco5udhF3kg@mail.gmail.com>
- References: <[🔎] 20110307104904.2045.12437.reportbug@debian-scott.sk1m> <[🔎] 4DB18945.4000903@dogguy.org> <[🔎] 20110428082917.GK2809@radis.liafa.jussieu.fr> <[🔎] 4DB9266B.1090504@dogguy.org> <[🔎] BANLkTincj_VXnfv+0VOiT-Hvco5udhF3kg@mail.gmail.com>
On 04/28/2011 02:26 PM, Scott Howard wrote:On Thu, Apr 28, 2011 at 4:33 AM, Mehdi Dogguy<mehdi@dogguy.org> wrote:On 04/28/2011 10:29 AM, Julien Cristau wrote:On Fri, Apr 22, 2011 at 15:57:25 +0200, Mehdi Dogguy wrote:But, there is an issue with getfem++: It build depends on scilab-include which is not available everywhere: scilab-include | 5.3.1-3 | wheezy | amd64, armel, i386, ia64, mipsel, powerpc, s390, sparc scilab-include | 5.3.1-4 | sid | amd64, armel, i386, ia64, mipsel, powerpc, s390, sparc So, it's stuck on kfreebsd-* and mips (at least) and, thus, needs to be fixed. FWIW, csound and koffice build depend on libgmm++-dev.britney doesn't care about build-deps, though, so removing getfem++ temporarily would work, I think?Sure. I was just hoping/waiting for a comment from Scott.Yes, that would work - it looks like the transition went as expected. Everything is now build and the only failures were existing/unrelated failures or missing build-deps (I also fixed the FTBFSes in qtiplot and uploaded it, it now is linked against the new muparser as well)muparser migrated now. Closing. Thanks for your work! Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/
--- End Message ---