On 06.11.2013 08:49, Andreas Tille wrote:
> Hi,
Hello Andreas,
> general statement for everybody: Please use
>
>Priority: optional
>
> for all your packages which are not *-dbg (Debug) packages. Everything
> else is some kind of wrong shyness / understatement because you might
> think your
Hi Alexandre,
On Tue, Nov 05, 2013 at 05:52:29PM +0100, Alexandre Gramfort wrote:
> please have a look at our debian branch:
>
> https://github.com/mne-tools/mne-python/tree/debian
Looks good from quick view without doing an actual build. I have
attached a fix for the debian/watch file - the fi
hi Andreas,
> On Tue, Nov 05, 2013 at 05:52:29PM +0100, Alexandre Gramfort wrote:
>> please have a look at our debian branch:
>>
>> https://github.com/mne-tools/mne-python/tree/debian
>
> Looks good from quick view without doing an actual build. I have
> attached a fix for the debian/watch file -
On Wed, 06 Nov 2013, Andreas Tille wrote:
> > > In any case it has several advantages to at least maintain a clone in
> > > one of our repositories at git.debian.org because we have some tools
> > > browsing the repositories and doing some general analysis over the
> > > VCS status. It would be go
Hi Alexandre,
On Wed, Nov 06, 2013 at 05:26:13PM +0100, Alexandre Gramfort wrote:
> > Looks good from quick view without doing an actual build. I have
> > attached a fix for the debian/watch file - the file in your repository
> > does not report anything when trying `uscan --verbose --report`.
>
Hi,
just one point I always forget to append at the end of my mails: I'm
personally quite irritated when the language a program is written in is
part of the name. Considering a
linux-c/asm
apache-c
kde-c++
eclipse-java
...
you get the idea. From a users perspective it is perfec
On Wed, Nov 06, 2013 at 11:06:16PM +0100, Andreas Tille wrote:
> Hi,
>
> just one point I always forget to append at the end of my mails: I'm
> personally quite irritated when the language a program is written in is
> part of the name. Considering a
>
>linux-c/asm
>apache-c
>kde-c++
Hi Steve, Dominique, Marco, [list-cross-post]
Jean-Christophe noted this bug [1] at the CTK hackfest, which is
blocking CTK for other architectures. Is it possible to get some of
these architectures reporting nightly builds [2] to the ITK software
quality dashboard [3], so they can be cleaned up?
Hi Matt,
Thank you for looking into this. Per Debian policy the build machines
cannot submit any build reports,
but you can get all build logs (with all failing tests) here:
https://buildd.debian.org/status/logs.php?pkg=insighttoolkit4
I see that the ITK build time on Debian's build machines can
Hello Matt,
On November 6, 2013 05:43:37 PM Matt McCormick wrote:
> Jean-Christophe noted this bug [1] at the CTK hackfest, which is
> blocking CTK for other architectures. Is it possible to get some of
> these architectures reporting nightly builds [2] to the ITK software
> quality dashboard [3
Hi Dominique and Steve,
As Dominique mentioned, policy for the official build daemon machines
> forbids
> network access from the build. So, a while back, I asked around for some
> other machines to use for nightly builds. I got a couple of offers of a
> login,
> but I lacked the time to set up
- re-send with address for lists -
Hi Dominique and Steve,
> As Dominique mentioned, policy for the official build daemon machines forbids
> network access from the build. So, a while back, I asked around for some
> other machines to use for nightly builds. I got a couple of offers of a
> lo
12 matches
Mail list logo
