Re: bart version 0.9.00

Am Sonntag, dem 10.12.2023 um 21:37 -0800 schrieb tony mancill: > On Mon, Dec 11, 2023 at 12:11:38AM +0100, Martin Uecker wrote: > > I upgraded the BART package to the new upstream release. > > > > I would appreciate if someone could take a look and then > > upload it &

bart version 0.9.00

Hi, I upgraded the BART package to the new upstream release. I would appreciate if someone could take a look and then upload it Thanks! Martin

Re: BART 0.8.0

Am Donnerstag, den 27.10.2022, 07:26 +0530 schrieb Nilesh Patra: > On Wed, Oct 26, 2022 at 11:56:28AM +0200, Martin Uecker wrote: > > Thank you! It seems this is working correctly > > on all archs. > > > > I also finalized the bart-view update. Can > > you uplo

Re: BART 0.8.0

Am Dienstag, den 25.10.2022, 01:12 +0530 schrieb Nilesh Patra: > On Mon, Oct 24, 2022 at 09:20:21PM +0200, Martin Uecker wrote: > > Am Dienstag, den 25.10.2022, 00:41 +0530 schrieb Nilesh Patra: Hi Nilesh, > > > Also, salsa CI is failing the build pipeline, &g

Re: BART 0.8.0

Am Dienstag, den 25.10.2022, 00:41 +0530 schrieb Nilesh Patra: > Hello, > > On Mon, Oct 24, 2022 at 08:39:33PM +0200, Martin Uecker wrote: > > Hi Andreas and all, > > > > I updated the package and turned off some unit tests on > > i386 for now (and turned on ot

Re: BART 0.8.0

> [1] > https://buildd.debian.org/status/fetch.php?pkg=bart=i386=0.8.00-2=1665741010=0 > > Am Fri, Oct 14, 2022 at 08:53:00AM +0200 schrieb Andreas Tille: > > Hi Martin, > > > > Am Thu, Oct 13, 2022 at 09:41:19PM +0200 schrieb Martin Uecker: > >

Re: BART 0.8.0

022 at 08:53:00AM +0200 schrieb Andreas Tille: > > Hi Martin, > > > > Am Thu, Oct 13, 2022 at 09:41:19PM +0200 schrieb Martin Uecker: > > > > Yes, the issue is numerical unit tests failing on > > > > some archs. This not entirely surprising as we had this >

Re: BART 0.8.0

Hi Andreas, Am Sonntag, den 09.10.2022, 09:39 +0200 schrieb Martin Uecker: > Hi Andreas, > > Am Sonntag, den 09.10.2022, 06:39 +0200 schrieb Andreas Tille: > > > > > I will do this soon, but probably wait in case other issues > > > > emerge wi

Re: BART 0.8.0

Hi Andreas, Am Sonntag, den 09.10.2022, 06:39 +0200 schrieb Andreas Tille: > Hi Martin, > > Am Sat, Oct 08, 2022 at 05:45:43PM +0200 schrieb Andreas Tille: > > H, I need to check my upload - thanks for mentioning it. > > Bart-cuda arrived in unstable but bart is pending. I'll check later.

Re: BART 0.8.0

Hi Andreas, Am Freitag, den 07.10.2022, 15:18 +0200 schrieb Andreas Tille: > Hi Martin, > > Am Sat, Oct 01, 2022 at 02:45:21PM +0200 schrieb Martin Uecker: > > I updated the Debian packages for BART (bart and bart-cuda) > > to our new upstream version. > >

BART 0.8.0

Hi all, I updated the Debian packages for BART (bart and bart-cuda) to our new upstream version. This time I also managed to run the CI on salsa for bart-cuda There are still some failures, but it seems ok to me. Please upload if it looks ok to you. Martin

Re: [Fwd: Bug#1001916: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x]

Am Mittwoch, den 29.12.2021, 20:34 +0530 schrieb Nilesh Patra: > On 12/29/21 6:31 PM, Martin Uecker wrote: > > Am Mittwoch, den 29.12.2021, 11:06 +0100 schrieb Martin Uecker: > > > Hi Nilesh, > > ... > > > > > > - try to work around by patching? (

Re: [Fwd: Bug#1001916: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x]

Am Mittwoch, den 29.12.2021, 11:06 +0100 schrieb Martin Uecker: > Hi Nilesh, ... > > - try to work around by patching? (would be easy > >only with access to the affected architectures) > > > > This would be best. You could try with qemu to emulate these archs.

Re: [Fwd: Bug#1001916: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x]

Hi Nilesh, thanks! > On 12/28/21 5:36 PM, Martin Uecker wrote: > > Hi all, > > this is caused by some compiler bug in GCC 11. Any advice how > to proceed? > > - use GCC 11 (I meant GCC 10) > If this really is a bug in the _compiler itself_, maybe simply > fi

[Fwd: Bug#1001916: src:bart-view: fails to migrate to testing for too long: FTBFS on armel and s390x]

Hi all, this is caused by some compiler bug in GCC 11. Any advice how to proceed? - use GCC 11 - exclude affected architectures? - try to work around by patching? (would be easy only with access to the affected architectures) - talk to the release team? Best, Martin

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Hi Andreas, > For me the package is close to ready if I would understand why you > insist on the empty dir usr/lib/bart/commands/. I do not see any reason > for this since in /usr only packages can / should write and a package > that writes to this location would create the package itself.

Re: Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

> There are three remaining and easy to fix lintian issues: > > I: bart source: duplicate-short-description bart libbart-dev > W: bart: package-installs-into-obsolete-dir etc/bash_completion.d/ : > ^etc/bash_completion.d/ -> usr/share/bash-completion/completions (see also >

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Hi Ghislain, Ghislain Vaillant <ghisv...@gmail.com>: > On 08/01/16 19:29, Martin Uecker wrote: > Good. Then, you might want to use libbart-dev as the package name, which > is usually the naming convention for packages containing any libraries > (in shared or static form).

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Ghislain Vaillant : > > FYI, the same trick is used for other dependencies with multiple > backends such as OpenCL. What is the state of OpenCL on Debian? We only support CUDA in BART, but I always wanted to add OpenCL support and it should be fairly easy... Martin

Re: Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Hi Ghisvail! > - Binary packages split-up. > > I am not quite sure about the usefulness of the bart-dev package. The final > compilation line shows: ... > i.e. the final output is one executable (bart) with private libraries > (libbox, libgrecon...) linked statically. So it looks to me that

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Hi Andreas, > I get: > > ... >dh_clean > dpkg-source -i.git -I.git -b bart-0.2.09d > dpkg-source: info: using options from bart-0.2.09d/debian/source/options: > --extend-diff-ignore=(^|/)(version.(inc|txt)|commands.txt)$ > dpkg-source: info: using source format '3.0 (quilt)' >

Re: Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Hi Andreas, > On Mon, Dec 07, 2015 at 08:18:59AM +, Uecker, Martin wrote: > > > On Sun, Dec 06, 2015 at 11:59:02PM +, Uecker, Martin wrote: > > > > > Put simply, pristine-tar is our way to encapsulate access to the > > > > > source > > > > > tarball used for packaging. Someone who