couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick North <nort...@gmail.com>
Subject Re: Testing Upgrade to 1.6.x
Date Sun, 27 Apr 2014 16:02:10 GMT
​1.6.0 RC3 was fine​ - I haven't tried since then though.

Nick


On 27 April 2014 16:27, Robert Samuel Newson <rnewson@apache.org> wrote:

>
> Excellent, so the problem no longer occurs with a clean 1.6.x build?
>
> On 27 Apr 2014, at 14:50, Nick North <north.n@gmail.com> wrote:
>
> > It does look like the Windows 1.5 problem where, as Robert says, I had
> not
> > cleaned up properly from a previous build.
> >
> > Nick
> >
> >
> > On 27 April 2014 00:38, Robert Samuel Newson <rnewson@apache.org> wrote:
> >
> >>
> >> Did you 'make clean' first? This looks like you have a module with the
> old
> >> #changes_args record and other modules with the new one.
> >>
> >> On 26 Apr 2014, at 23:04, Stefan Kögl <koeglstefan@gmail.com> wrote:
> >>
> >>> Hi,
> >>>
> >>> As I see that 1.6.x is coming along, I've tested upgrading an 1.5 db to
> >> the
> >>> current 1.6.x branch (26cff2d51473cbc8c0dfc655b2dbb986493bbcb8).
> >>>
> >>> I've stopped couch, compiled 1.6.x with R15B03 and installed the result
> >> on
> >>> an Ubuntu 12.04.4 LTS.
> >>>
> >>> The instance always failed with the logging output shown in
> >>>
> >>> https://gist.github.com/stefankoegl/11332148
> >>>
> >>> Is this a bug in the 1.6.x branch, or is my upgrade process somehow
> >> broken?
> >>>
> >>>
> >>> -- Stefan
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message