On Thu, 18 Oct 2018, Andreas Tille wrote:
> On Thu, Oct 18, 2018 at 09:21:37AM -0400, Yaroslav Halchenko wrote:
> > On Thu, 18 Oct 2018, Yaroslav Halchenko wrote:
> > > Yet to look at your changes, but for now I have
> > > - pushed debian/2.3.1-1 packaging (withing "old" custom
> > > "on to
On Thu, Oct 18, 2018 at 09:21:37AM -0400, Yaroslav Halchenko wrote:
>
> On Thu, 18 Oct 2018, Yaroslav Halchenko wrote:
>
> > Yet to look at your changes, but for now I have
>
> > - pushed debian/2.3.1-1 packaging (withing "old" custom
> > "on top of upstream releases in git" dist/debian/prope
On Thu, 18 Oct 2018, Yaroslav Halchenko wrote:
> Yet to look at your changes, but for now I have
> - pushed debian/2.3.1-1 packaging (withing "old" custom
> "on top of upstream releases in git" dist/debian/proper branch)
> - force-pushed
> $> git push -f salsa debian/2.3.0-1 2.3.0
On Sun, 14 Oct 2018, Andreas Tille wrote:
> Hi Yaroslav,
> On Sat, Oct 13, 2018 at 08:29:53PM -0400, Yaroslav Halchenko wrote:
> > > I'd volunteer to check the diff between your current changes and my work
> > > and merge everything - but can I please use a branch named debian?
> > quick one
Hi Yaroslav,
On Sat, Oct 13, 2018 at 08:29:53PM -0400, Yaroslav Halchenko wrote:
>
> > I'd volunteer to check the diff between your current changes and my work
> > and merge everything - but can I please use a branch named debian?
>
> quick one: well, the main confusion stems from that fact th
On Sat, 13 Oct 2018, Andreas Tille wrote:
> On Fri, Oct 12, 2018 at 09:15:37AM -0400, Yaroslav Halchenko wrote:
> > > ok... will merge for the next upload to proceed -- we mitigated all
> > > known issues, and the beast builds fine all the way down to jessie, so
> > > release is coming soon now
On Fri, Oct 12, 2018 at 09:15:37AM -0400, Yaroslav Halchenko wrote:
> > ok... will merge for the next upload to proceed -- we mitigated all
> > known issues, and the beast builds fine all the way down to jessie, so
> > release is coming soon now
>
> oi... I guess we caused you confusion and unneed
On Fri, 12 Oct 2018, Yaroslav Halchenko wrote:
> On Tue, 09 Oct 2018, Andreas Tille wrote:
> > > 2.3.1 bugfix is around the corner
> > > https://github.com/nipy/nibabel/pull/667
> > > so I will aim to make sure the #909990 is fixed within it (for starters
> > > - I do not think I observed this
On Tue, 09 Oct 2018, Andreas Tille wrote:
> > 2.3.1 bugfix is around the corner
> > https://github.com/nipy/nibabel/pull/667
> > so I will aim to make sure the #909990 is fixed within it (for starters
> > - I do not think I observed this exception when building from current RC
> > branch)
> I
Hi Yaroslav,
On Mon, Oct 08, 2018 at 11:25:53AM -0400, Yaroslav Halchenko wrote:
> Thank you Andreas for looking into it
You are welcome.
> 2.3.1 bugfix is around the corner
> https://github.com/nipy/nibabel/pull/667
> so I will aim to make sure the #909990 is fixed within it (for starters
> - I
Thank you Andreas for looking into it
2.3.1 bugfix is around the corner
https://github.com/nipy/nibabel/pull/667
so I will aim to make sure the #909990 is fixed within it (for starters
- I do not think I observed this exception when building from current RC
branch)
On Mon, 08 Oct 2018, Andreas
Hi,
to see what I can do about bug #909990 I've imported the latest version
into the packaging Git[1]. When beeing inside the main dir of the Git
repository I can easily do
neurodebian-team/pynifti(debian) $ python3
Python 3.6.6 (default, Jun 27 2018, 14:44:17)
[GCC 8.1.0] on linux
Type "help",
12 matches
Mail list logo
