You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by till <kl...@gmail.com> on 2012/06/10 20:46:54 UTC
Re: CouchDB packaging for Ubuntu
Hey,
[ CC'd user@ to get more feedback. ]
I made some progress.
I have builds for the following more or less ready:
* karmic
* lucid
* maverick
* oneiric
* natty
* precise
It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer.
https://launchpad.net/~till-php/+archive/couchdb
Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it.
(Also, @Jan:)
I'm trying to figure out how to setup more automated testing. "make check" always requires the source tree to be present, I'd like "make check" against my installed binaries. I saw the "verify installation" in Futon – something like that for the command line so I can iterate on these builds and trigger a "test this" in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm.
Till
On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> Hi,
>
> I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> Unfortunately, I've never built a deb package, so, I cannot provide such a
> package. Nevertheless, if you have any problem in building it, just let me
> know and I will try to help.
>
> About the mailing list, I suppose adding the CouchDB users (to get an idea
> which is the desired Ubuntu distro) and/or Debian (you may get support in
> testing and debugging) lists wouldn't be such a bad idea, but it's your
> call here.
>
> CGS
>
>
>
>
> On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
>
> > Hey,
> >
> > I've been scratching my own itch and started building 1.2.0 for a couple
> > Ubuntu distributions.
> >
> > It's a WIP but I was wondering the following:
> >
> > 1) It builds – but does it work? Is the best bet to run the test suite in
> > futon, or is there something I could run on the command line when the
> > package is installed? I'd prefer the command line to include it in some
> > sort of continuous testing without a browser.
> >
> > 2) Who'd have some interest in testing this?
> >
> > 3) Which distributions are wanted – I started with karmic and lucid and
> > had planned to build all the way up to 12.10.
> >
> > 4) Is there a mailing list to discuss this, or is dev@ fine?
> >
> > Till
RE: CouchDB packaging for Ubuntu
Posted by Thomas Hommers <th...@ebalu.com>.
Hi,
would it be possible to use this as a base for a Debian Squeeze package ?
I would be able to help. Testing for sure and eventually also building the package, tough I am not experienced in building Debian packages.
Regards
Thomas
________________________________________
From: ipad.wenk@googlemail.com [ipad.wenk@googlemail.com] On Behalf Of Andy Wenk [andy@nms.de]
Sent: Tuesday, June 12, 2012 4:12 AM
To: user@couchdb.apache.org
Cc: dev@couchdb.apache.org
Subject: Re: CouchDB packaging for Ubuntu
Till - awesome work! I just gave the link to your github repo to my
mates at S2 ;-)
On 11 June 2012 18:57, CGS <cg...@gmail.com> wrote:
> Let us know if any test fail and give us the log of the tests. The tests
> themselves are pretty self explanatory. If not, at least some tests are
> using the CouchDB log. So, I think there will be enough info for debugging.
>
> CGS
>
>
>
>
>
> On Mon, Jun 11, 2012 at 5:12 PM, till <kl...@gmail.com> wrote:
>
>> Ok,
>>
>> my working repo is here:
>> https://github.com/till/couchdb-deb
>>
>> So does anyone have any idea how to debug failed test cases? They never
>> failed for me before. :D
>>
>> Till
>>
>>
>> On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
>>
>> > Not at all. After all, I do not do this for my personal interest, but for
>> > this community. I am glad if I can help.
>> >
>> > Cheers,
>> > CGS
>> >
>> >
>> >
>> >
>> > On Mon, Jun 11, 2012 at 3:58 PM, till <klimpong@gmail.com (mailto:
>> klimpong@gmail.com)> wrote:
>> >
>> > > Hey,
>> > >
>> > > thanks, I'm gonna test this shortly. Do you mind if I push it one of my
>> > > repo?
>> > >
>> > > Till
>> > >
>> > >
>> > > On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I isolated the tests which are started with make check and make them
>> run
>> > > over the default installation under Ubuntu 12.10. Please, let me know
>> if it
>> > > is what you need (there is a README file in the archive).
>> > > >
>> > > > CGS
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:
>> klimpong@gmail.com) (mailto:
>> > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
>> > > > > Hey,
>> > > > >
>> > > > > [ CC'd user@ to get more feedback. ]
>> > > > >
>> > > > > I made some progress.
>> > > > >
>> > > > > I have builds for the following more or less ready:
>> > > > >
>> > > > > * karmic
>> > > > > * lucid
>> > > > > * maverick
>> > > > > * oneiric
>> > > > > * natty
>> > > > > * precise
>> > > > >
>> > > > > It's building and I am trying to refine the process a bit. So it
>> might
>> > > break in between [aka WIP]. I'm just adding this as a disclaimer.
>> > > > >
>> > > > > https://launchpad.net/~till-php/+archive/couchdb<
>> https://launchpad.net/%7Etill-php/+archive/couchdb>
>> > > > >
>> > > > > Would you mind testing my builds? :) So far, I only tested lucid
>> > > briefly (and ran into the xulrunner issue, which I think I have
>> auto-fixed
>> > > now). Besides I just started it up, created a DB and entered some docs
>> into
>> > > it.
>> > > > >
>> > > > > (Also, @Jan:)
>> > > > >
>> > > > > I'm trying to figure out how to setup more automated testing. "make
>> > > check" always requires the source tree to be present, I'd like "make
>> check"
>> > > against my installed binaries. I saw the "verify installation" in
>> Futon –
>> > > something like that for the command line so I can iterate on these
>> builds
>> > > and trigger a "test this" in a continuous integration setup. Building
>> is
>> > > part of it, but since building a binary and installing it are two
>> separate
>> > > steps I want to ensure that the second step also works. I am still
>> trying
>> > > to wrap my head around a setup where I can maybe knife up a few
>> instances
>> > > in THE CLOUD, install my package, run its test-suite and confirm.
>> > > > >
>> > > > > Till
>> > > > >
>> > > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
>> > > running.
>> > > > > > Unfortunately, I've never built a deb package, so, I cannot
>> provide
>> > > > >
>> > > >
>> > >
>> > > such a
>> > > > > > package. Nevertheless, if you have any problem in building it,
>> just
>> > > > >
>> > > >
>> > >
>> > > let me
>> > > > > > know and I will try to help.
>> > > > > >
>> > > > > > About the mailing list, I suppose adding the CouchDB users (to
>> get
>> > > an idea
>> > > > > > which is the desired Ubuntu distro) and/or Debian (you may get
>> > > > >
>> > > >
>> > >
>> > > support in
>> > > > > > testing and debugging) lists wouldn't be such a bad idea, but
>> it's
>> > > > >
>> > > >
>> > >
>> > > your
>> > > > > > call here.
>> > > > > >
>> > > > > > CGS
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com(mailto:
>> klimpong@gmail.com) (mailto:
>> > > klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
>> > > > > >
>> > > > > > > Hey,
>> > > > > > >
>> > > > > > > I've been scratching my own itch and started building 1.2.0
>> for a
>> > > couple
>> > > > > > > Ubuntu distributions.
>> > > > > > >
>> > > > > > > It's a WIP but I was wondering the following:
>> > > > > > >
>> > > > > > > 1) It builds – but does it work? Is the best bet to run the
>> test
>> > > suite in
>> > > > > > > futon, or is there something I could run on the command line
>> when
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > > the
>> > > > > > > package is installed? I'd prefer the command line to include
>> it in
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > > some
>> > > > > > > sort of continuous testing without a browser.
>> > > > > > >
>> > > > > > > 2) Who'd have some interest in testing this?
>> > > > > > >
>> > > > > > > 3) Which distributions are wanted – I started with karmic and
>> > > lucid and
>> > > > > > > had planned to build all the way up to 12.10.
>> > > > > > >
>> > > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
>> > > > > > >
>> > > > > > > Till
>> > > >
>> > > >
>> > > > Attachments:
>> > > > - couchdb_etap.tgz
>> > > >
>> > >
>> > >
>> >
>> >
>> >
>>
>>
>>
--
Andy Wenk
Hamburg - Germany
RockIt!
"CouchDB - Das Praxisbuch für Entwickler und Administratoren"
http://www.galileocomputing.de/2462
http://www.couchdb-buch.de
+++ english version is coming +++
http://www.couchdb-book.com
"PostgreSQL 8.4: Das Praxisbuch"
http://www.galileocomputing.de/2008
http://www.pg-praxisbuch.de
Re: CouchDB packaging for Ubuntu
Posted by Andy Wenk <an...@nms.de>.
Till - awesome work! I just gave the link to your github repo to my
mates at S2 ;-)
On 11 June 2012 18:57, CGS <cg...@gmail.com> wrote:
> Let us know if any test fail and give us the log of the tests. The tests
> themselves are pretty self explanatory. If not, at least some tests are
> using the CouchDB log. So, I think there will be enough info for debugging.
>
> CGS
>
>
>
>
>
> On Mon, Jun 11, 2012 at 5:12 PM, till <kl...@gmail.com> wrote:
>
>> Ok,
>>
>> my working repo is here:
>> https://github.com/till/couchdb-deb
>>
>> So does anyone have any idea how to debug failed test cases? They never
>> failed for me before. :D
>>
>> Till
>>
>>
>> On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
>>
>> > Not at all. After all, I do not do this for my personal interest, but for
>> > this community. I am glad if I can help.
>> >
>> > Cheers,
>> > CGS
>> >
>> >
>> >
>> >
>> > On Mon, Jun 11, 2012 at 3:58 PM, till <klimpong@gmail.com (mailto:
>> klimpong@gmail.com)> wrote:
>> >
>> > > Hey,
>> > >
>> > > thanks, I'm gonna test this shortly. Do you mind if I push it one of my
>> > > repo?
>> > >
>> > > Till
>> > >
>> > >
>> > > On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I isolated the tests which are started with make check and make them
>> run
>> > > over the default installation under Ubuntu 12.10. Please, let me know
>> if it
>> > > is what you need (there is a README file in the archive).
>> > > >
>> > > > CGS
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:
>> klimpong@gmail.com) (mailto:
>> > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
>> > > > > Hey,
>> > > > >
>> > > > > [ CC'd user@ to get more feedback. ]
>> > > > >
>> > > > > I made some progress.
>> > > > >
>> > > > > I have builds for the following more or less ready:
>> > > > >
>> > > > > * karmic
>> > > > > * lucid
>> > > > > * maverick
>> > > > > * oneiric
>> > > > > * natty
>> > > > > * precise
>> > > > >
>> > > > > It's building and I am trying to refine the process a bit. So it
>> might
>> > > break in between [aka WIP]. I'm just adding this as a disclaimer.
>> > > > >
>> > > > > https://launchpad.net/~till-php/+archive/couchdb<
>> https://launchpad.net/%7Etill-php/+archive/couchdb>
>> > > > >
>> > > > > Would you mind testing my builds? :) So far, I only tested lucid
>> > > briefly (and ran into the xulrunner issue, which I think I have
>> auto-fixed
>> > > now). Besides I just started it up, created a DB and entered some docs
>> into
>> > > it.
>> > > > >
>> > > > > (Also, @Jan:)
>> > > > >
>> > > > > I'm trying to figure out how to setup more automated testing. "make
>> > > check" always requires the source tree to be present, I'd like "make
>> check"
>> > > against my installed binaries. I saw the "verify installation" in
>> Futon –
>> > > something like that for the command line so I can iterate on these
>> builds
>> > > and trigger a "test this" in a continuous integration setup. Building
>> is
>> > > part of it, but since building a binary and installing it are two
>> separate
>> > > steps I want to ensure that the second step also works. I am still
>> trying
>> > > to wrap my head around a setup where I can maybe knife up a few
>> instances
>> > > in THE CLOUD, install my package, run its test-suite and confirm.
>> > > > >
>> > > > > Till
>> > > > >
>> > > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
>> > > running.
>> > > > > > Unfortunately, I've never built a deb package, so, I cannot
>> provide
>> > > > >
>> > > >
>> > >
>> > > such a
>> > > > > > package. Nevertheless, if you have any problem in building it,
>> just
>> > > > >
>> > > >
>> > >
>> > > let me
>> > > > > > know and I will try to help.
>> > > > > >
>> > > > > > About the mailing list, I suppose adding the CouchDB users (to
>> get
>> > > an idea
>> > > > > > which is the desired Ubuntu distro) and/or Debian (you may get
>> > > > >
>> > > >
>> > >
>> > > support in
>> > > > > > testing and debugging) lists wouldn't be such a bad idea, but
>> it's
>> > > > >
>> > > >
>> > >
>> > > your
>> > > > > > call here.
>> > > > > >
>> > > > > > CGS
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com(mailto:
>> klimpong@gmail.com) (mailto:
>> > > klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
>> > > > > >
>> > > > > > > Hey,
>> > > > > > >
>> > > > > > > I've been scratching my own itch and started building 1.2.0
>> for a
>> > > couple
>> > > > > > > Ubuntu distributions.
>> > > > > > >
>> > > > > > > It's a WIP but I was wondering the following:
>> > > > > > >
>> > > > > > > 1) It builds – but does it work? Is the best bet to run the
>> test
>> > > suite in
>> > > > > > > futon, or is there something I could run on the command line
>> when
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > > the
>> > > > > > > package is installed? I'd prefer the command line to include
>> it in
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > > some
>> > > > > > > sort of continuous testing without a browser.
>> > > > > > >
>> > > > > > > 2) Who'd have some interest in testing this?
>> > > > > > >
>> > > > > > > 3) Which distributions are wanted – I started with karmic and
>> > > lucid and
>> > > > > > > had planned to build all the way up to 12.10.
>> > > > > > >
>> > > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
>> > > > > > >
>> > > > > > > Till
>> > > >
>> > > >
>> > > > Attachments:
>> > > > - couchdb_etap.tgz
>> > > >
>> > >
>> > >
>> >
>> >
>> >
>>
>>
>>
--
Andy Wenk
Hamburg - Germany
RockIt!
"CouchDB - Das Praxisbuch für Entwickler und Administratoren"
http://www.galileocomputing.de/2462
http://www.couchdb-buch.de
+++ english version is coming +++
http://www.couchdb-book.com
"PostgreSQL 8.4: Das Praxisbuch"
http://www.galileocomputing.de/2008
http://www.pg-praxisbuch.de
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Hi,
Sorry for delay, but I had an "emergency" at a project and I didn't have
time to work on the tests. My apologies.
I restructured all the paths in order for you to work easier with them.
That means:
COUCHDB_TEST_ETAP_PATH "./tests"
COUCHDB_TEST_LIB_PATH "/usr/local/lib/couchdb/erlang/lib"
COUCHDB_TEST_ETC_PATH "/usr/local/etc/couchdb"
COUCHDB_TEST_WEB_PATH "/usr/local/share/couchdb"
COUCHDB_TEST_DBS_PATH "/usr/local/var/lib/couchdb"
COUCHDB_TEST_EBIN "ebin"
COUCHDB_TEST_VERSION "-1.2.0"
COUCHDB_TEST_ETAP_VERSION ""
COUCHDB_TEST_EJSON_VERSION "-0.1.0"
COUCHDB_TEST_ERLANG_OAUTH_VERSION ""
COUCHDB_TEST_IBROWSE_VERSION "-2.2.0"
COUCHDB_TEST_MOCHIWEB_VERSION "-1.4.1"
COUCHDB_TEST_SNAPPY_VERSION "-1.0.3"
You have the explained in README. Nevertheless, knowing the odds for
someone to read a README file, here there is a copy:
COUCHDB_TEST_ETAP_PATH - It's the path toward the tests. E.g.,
"/home/couchdb/couchdb_etap/tests". It accepts "./tests"
COUCHDB_TEST_LIB_PATH - It's the absolute path toward the CouchDB library
directory. E.g., "/usr/local/lib/couchdb/erlang/lib"
COUCHDB_TEST_ETC_PATH - It's the absolute path toward the CouchDB etc
directory. E.g., "/usr/local/etc/couchdb"
COUCHDB_TEST_WEB_PATH - It's the absolute path toward the web directory
(where www and server directories are). E.g., "/usr/local/share/couchdb"
COUCHDB_TEST_DBS_PATH - It's the absolute path toward the databases
directory. E.g., "/usr/local/var/lib/couchdb"
COUCHDB_TEST_EBIN - It's the location of the .beam files. E.g., "ebin"
COUCHDB_TEST_VERSION - It's the CouchDB library directory suffix. E.g.,
"-1.2.0"
COUCHDB_TEST_ETAP_VERSION - It's the ETap library directory suffix
(installed in CouchDB). E.g., ""
COUCHDB_TEST_EJSON_VERSION - It's the EJSON library directory suffix. E.g.,
"-0.1.0"
COUCHDB_TEST_ERLANG_OAUTH_VERSION - It's the Erlang OAuth library directory
suffix. E.g., ""
COUCHDB_TEST_IBROWSE_VERSION - It's the iBrowse library directory suffix.
E.g., "-2.2.0"
COUCHDB_TEST_MOCHIWEB_VERSION - It's the Mochiweb library directory suffix.
E.g., "-1.4.1"
COUCHDB_TEST_SNAPPY_VERSION - It's the Snappy library directory suffix.
E.g., "-1.0.3"
Don't forget to run the tests with root privileges (a.k.a., sudo
./test.sh). ;)
Forgive my "verbosity". If you have more questions or problems, let me know.
Cheers,
CGS
On Tue, Jun 12, 2012 at 7:34 PM, till <kl...@gmail.com> wrote:
> Attachment didn't make it through – can you a patch/file?
>
>
> On Tuesday, June 12, 2012 at 6:22 PM, CGS wrote:
>
> > OK. I understand.
> >
> > For the moment, replace test_util.erl from utils with the file attached
> here. This should remove COUCHDB_TEST_PATH from the path. I will rewrite
> test_util.erl to get the paths independently for your repo.
> >
> > CGS
> >
> >
> >
> >
> >
> > On Tue, Jun 12, 2012 at 6:06 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> > > 3> test_util:config_files().
> > > ["/usr/etc/couchdb/default.ini",
> > > "/home/vagrant/buildbox/testsuite/tests/random_port.ini",
> > > "/usr/etc/couchdb/local.ini"]
> > >
> > > This is the problem – the prefix is not used for sysconfdir. The dir
> is in /etc not in PREFIX/etc.
> > >
> > > Till
> > >
> > > --
> > > till
> > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > >
> > >
> > > On Tuesday, June 12, 2012 at 5:52 PM, CGS wrote:
> > >
> > > > Can you do a test for me? Please, open an Erlang shell (erl) in
> tests/
> > > > directory (hopefully you will still have the test_util.beam file) and
> > > > copy-paste these lines (exit with CTRL+g and q<Enter>):
> > > >
> > > > l(test_util).
> > > > test_util:init_code_path().
> > > > test_util:config_files().
> > > > l(couch_config).
> > > > couch_config:start_link(test_util:config_files()).
> > > > l(couch_drv).
> > > > couch_drv:start_link().
> > > >
> > > > Your result should look like this:
> > > >
> > > > 1> l(test_util).
> > > > {module,test_util}
> > > > 2> test_util:init_code_path().
> > > > ok
> > > > 3> test_util:config_files().
> > > > ["/usr/etc/couchdb/default.ini",
> > > > "<path_to_tests_dir>/random_port.ini",
> > > > "/usr/etc/couchdb/local.ini"]
> > > > 4> l(couch_config).
> > > > {module,couch_config}
> > > > 5> couch_config:start_link(test_util:config_files()).
> > > > {ok,<0.38.0>}
> > > > 6> l(couch_drv).
> > > > {module,couch_drv}
> > > > 7> couch_drv:start_link().
> > > > {ok,<0.41.0>}
> > > >
> > > > where <path_to_local_dir> should be the same set
> COUCHDB_TEST_ETAP_PATH and
> > > > the same with the result of pwd (considering you are still in tests
> > > > directory). Let me know the output, please.
> > > >
> > > > CGS
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Jun 12, 2012 at 5:21 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > > >
> > > > >
> > > > >
> > > > > On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
> > > > >
> > > > > > COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX
> from
> > > > > > configure options. The rest gets this variable in front (e.g.,
> if PREFIX
> > > > > > was set to "/" at the configuration stage, then
> COUCHDB_TEST_PATH should
> > > > > >
> > > > >
> > > > > be
> > > > > > set to ""). E.g., few things from my installation, I have:
> > > > > >
> > > > > > - default.ini and local.ini in /usr/local/etc/coucdb/ and that
> requires:
> > > > > > COUCHDB_TEST_PATH "/usr/local"
> > > > > > COUCHDB_TEST_ETC_PATH "etc/couchdb"
> > > > > >
> > > > >
> > > > >
> > > > > Ok, so basically I am trying to integrate as much as possible with
> Ubuntu
> > > > > – so I set my prefix to /usr (see github link).
> > > > >
> > > > > COUCHDB_TEST_PATH "/usr"
> > > > > >
> > > > > > - CouchDB .beam files path in
> > > > > > /usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that
> requires:
> > > > > > COUCHDB_TEST_PATH "/usr/local"
> > > > > > COUCHDB_TEST_LIB_PATH "lib/couchdb"
> > > > > > COUCHDB_TEST_EXTRA "erlang/lib"
> > > > > > COUCHDB_TEST_VERSION "-1.2.0"
> > > > > > COUCHDB_TEST_EBIN "ebin"
> > > > > >
> > > > >
> > > > >
> > > > > This is the path when I install my package:
> > > > > /usr/lib/couchdb/erlang/lib/couch-1.2.0/
> > > > >
> > > > >
> > > > > >
> > > > > > The problem may be in COUCHDB_TEST_ETAP_PATH "./tests"
> (preferable full
> > > > > > path and not relative because the tests don't know too much about
> > > > > >
> > > > >
> > > > > relative
> > > > > > paths). Can you try to set it as a full path and execute the
> tests again?
> > > > > > You don't need to clean anything from the previous executions.
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > I just did that – tests fail the same way.
> > > > >
> > > > > I can't really tell what the cause is since the erl_crash.dump is
> kinda
> > > > > hard to read. Signal vs. noise. :)
> > > > >
> > > > > Till
> > > > > >
> > > > > > CGS
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Jun 12, 2012 at 4:06 PM, till <klimpong@gmail.com(mailto:
> klimpong@gmail.com) (mailto:klimpong@gmail.com) (mailto:
> > > > > klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> klimpong@gmail.com))> wrote:
> > > > > >
> > > > > > > Yes, pretty much:
> > > > > > >
> https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
> > > > > > >
> > > > > > > I haven't checked in detail, but – do those lib/etc paths get
> prefixed
> > > > > > > with COUCHDB_TEST_PATH?
> > > > > > >
> > > > > > > Till
> > > > > > >
> > > > > > > --
> > > > > > > till
> > > > > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > > > > >
> > > > > > >
> > > > > > > On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
> > > > > > >
> > > > > > > > Have you modified the parameters from test.cfg to point to
> your
> > > > > CouchDB
> > > > > > > > installation?
> > > > > > > >
> > > > > > > > CGS
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com(mailto:
> klimpong@gmail.com) (mailto:klimpong@gmail.com) (mailto:
> > > > > klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> klimpong@gmail.com)) (mailto:
> > > > > > > klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> klimpong@gmail.com))> wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> > > > > > > > >
> > > > > > > > > > Well, the default installation requires root permissions
> as many
> > > > > > > paths
> > > > > > > > > are
> > > > > > > > > > accessible only as root (you did 'sudo make install',
> didn't
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > > you?).
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Also,
> > > > > > > > > > you do sudo apt-get install, so, the tests will be run
> under root
> > > > > > > > > > permissions. That's why I said in the README file that
> these
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > > tests
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > should
> > > > > > > > > > be run as root (a.k.a. sudo command).
> > > > > > > > > >
> > > > > > > > > > CGS
> > > > > > > > > Sorry, over read that before, but the failures are still
> happening
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > > with
> > > > > > > > > sudo:
> > > > > > > > > https://gist.github.com/2917336
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
Attachment didn't make it through – can you a patch/file?
On Tuesday, June 12, 2012 at 6:22 PM, CGS wrote:
> OK. I understand.
>
> For the moment, replace test_util.erl from utils with the file attached here. This should remove COUCHDB_TEST_PATH from the path. I will rewrite test_util.erl to get the paths independently for your repo.
>
> CGS
>
>
>
>
>
> On Tue, Jun 12, 2012 at 6:06 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
> > 3> test_util:config_files().
> > ["/usr/etc/couchdb/default.ini",
> > "/home/vagrant/buildbox/testsuite/tests/random_port.ini",
> > "/usr/etc/couchdb/local.ini"]
> >
> > This is the problem – the prefix is not used for sysconfdir. The dir is in /etc not in PREFIX/etc.
> >
> > Till
> >
> > --
> > till
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> >
> >
> > On Tuesday, June 12, 2012 at 5:52 PM, CGS wrote:
> >
> > > Can you do a test for me? Please, open an Erlang shell (erl) in tests/
> > > directory (hopefully you will still have the test_util.beam file) and
> > > copy-paste these lines (exit with CTRL+g and q<Enter>):
> > >
> > > l(test_util).
> > > test_util:init_code_path().
> > > test_util:config_files().
> > > l(couch_config).
> > > couch_config:start_link(test_util:config_files()).
> > > l(couch_drv).
> > > couch_drv:start_link().
> > >
> > > Your result should look like this:
> > >
> > > 1> l(test_util).
> > > {module,test_util}
> > > 2> test_util:init_code_path().
> > > ok
> > > 3> test_util:config_files().
> > > ["/usr/etc/couchdb/default.ini",
> > > "<path_to_tests_dir>/random_port.ini",
> > > "/usr/etc/couchdb/local.ini"]
> > > 4> l(couch_config).
> > > {module,couch_config}
> > > 5> couch_config:start_link(test_util:config_files()).
> > > {ok,<0.38.0>}
> > > 6> l(couch_drv).
> > > {module,couch_drv}
> > > 7> couch_drv:start_link().
> > > {ok,<0.41.0>}
> > >
> > > where <path_to_local_dir> should be the same set COUCHDB_TEST_ETAP_PATH and
> > > the same with the result of pwd (considering you are still in tests
> > > directory). Let me know the output, please.
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > > On Tue, Jun 12, 2012 at 5:21 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > >
> > > >
> > > >
> > > > On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
> > > >
> > > > > COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
> > > > > configure options. The rest gets this variable in front (e.g., if PREFIX
> > > > > was set to "/" at the configuration stage, then COUCHDB_TEST_PATH should
> > > > >
> > > >
> > > > be
> > > > > set to ""). E.g., few things from my installation, I have:
> > > > >
> > > > > - default.ini and local.ini in /usr/local/etc/coucdb/ and that requires:
> > > > > COUCHDB_TEST_PATH "/usr/local"
> > > > > COUCHDB_TEST_ETC_PATH "etc/couchdb"
> > > > >
> > > >
> > > >
> > > > Ok, so basically I am trying to integrate as much as possible with Ubuntu
> > > > – so I set my prefix to /usr (see github link).
> > > >
> > > > COUCHDB_TEST_PATH "/usr"
> > > > >
> > > > > - CouchDB .beam files path in
> > > > > /usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
> > > > > COUCHDB_TEST_PATH "/usr/local"
> > > > > COUCHDB_TEST_LIB_PATH "lib/couchdb"
> > > > > COUCHDB_TEST_EXTRA "erlang/lib"
> > > > > COUCHDB_TEST_VERSION "-1.2.0"
> > > > > COUCHDB_TEST_EBIN "ebin"
> > > > >
> > > >
> > > >
> > > > This is the path when I install my package:
> > > > /usr/lib/couchdb/erlang/lib/couch-1.2.0/
> > > >
> > > >
> > > > >
> > > > > The problem may be in COUCHDB_TEST_ETAP_PATH "./tests" (preferable full
> > > > > path and not relative because the tests don't know too much about
> > > > >
> > > >
> > > > relative
> > > > > paths). Can you try to set it as a full path and execute the tests again?
> > > > > You don't need to clean anything from the previous executions.
> > > > >
> > > >
> > > >
> > > >
> > > > I just did that – tests fail the same way.
> > > >
> > > > I can't really tell what the cause is since the erl_crash.dump is kinda
> > > > hard to read. Signal vs. noise. :)
> > > >
> > > > Till
> > > > >
> > > > > CGS
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Jun 12, 2012 at 4:06 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com) (mailto:
> > > > klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com))> wrote:
> > > > >
> > > > > > Yes, pretty much:
> > > > > > https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
> > > > > >
> > > > > > I haven't checked in detail, but – do those lib/etc paths get prefixed
> > > > > > with COUCHDB_TEST_PATH?
> > > > > >
> > > > > > Till
> > > > > >
> > > > > > --
> > > > > > till
> > > > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > > > >
> > > > > >
> > > > > > On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
> > > > > >
> > > > > > > Have you modified the parameters from test.cfg to point to your
> > > > CouchDB
> > > > > > > installation?
> > > > > > >
> > > > > > > CGS
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com) (mailto:
> > > > klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com)) (mailto:
> > > > > > klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com))> wrote:
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> > > > > > > >
> > > > > > > > > Well, the default installation requires root permissions as many
> > > > > > paths
> > > > > > > > are
> > > > > > > > > accessible only as root (you did 'sudo make install', didn't
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > you?).
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Also,
> > > > > > > > > you do sudo apt-get install, so, the tests will be run under root
> > > > > > > > > permissions. That's why I said in the README file that these
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > tests
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > should
> > > > > > > > > be run as root (a.k.a. sudo command).
> > > > > > > > >
> > > > > > > > > CGS
> > > > > > > > Sorry, over read that before, but the failures are still happening
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > with
> > > > > > > > sudo:
> > > > > > > > https://gist.github.com/2917336
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
OK. I understand.
For the moment, replace test_util.erl from utils with the file attached
here. This should remove COUCHDB_TEST_PATH from the path. I will rewrite
test_util.erl to get the paths independently for your repo.
CGS
On Tue, Jun 12, 2012 at 6:06 PM, till <kl...@gmail.com> wrote:
> 3> test_util:config_files().
> ["/usr/etc/couchdb/default.ini",
> "/home/vagrant/buildbox/testsuite/tests/random_port.ini",
> "/usr/etc/couchdb/local.ini"]
>
> This is the problem – the prefix is not used for sysconfdir. The dir is in
> /etc not in PREFIX/etc.
>
> Till
>
> --
> till
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>
>
> On Tuesday, June 12, 2012 at 5:52 PM, CGS wrote:
>
> > Can you do a test for me? Please, open an Erlang shell (erl) in tests/
> > directory (hopefully you will still have the test_util.beam file) and
> > copy-paste these lines (exit with CTRL+g and q<Enter>):
> >
> > l(test_util).
> > test_util:init_code_path().
> > test_util:config_files().
> > l(couch_config).
> > couch_config:start_link(test_util:config_files()).
> > l(couch_drv).
> > couch_drv:start_link().
> >
> > Your result should look like this:
> >
> > 1> l(test_util).
> > {module,test_util}
> > 2> test_util:init_code_path().
> > ok
> > 3> test_util:config_files().
> > ["/usr/etc/couchdb/default.ini",
> > "<path_to_tests_dir>/random_port.ini",
> > "/usr/etc/couchdb/local.ini"]
> > 4> l(couch_config).
> > {module,couch_config}
> > 5> couch_config:start_link(test_util:config_files()).
> > {ok,<0.38.0>}
> > 6> l(couch_drv).
> > {module,couch_drv}
> > 7> couch_drv:start_link().
> > {ok,<0.41.0>}
> >
> > where <path_to_local_dir> should be the same set COUCHDB_TEST_ETAP_PATH
> and
> > the same with the result of pwd (considering you are still in tests
> > directory). Let me know the output, please.
> >
> > CGS
> >
> >
> >
> >
> > On Tue, Jun 12, 2012 at 5:21 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> >
> > >
> > >
> > > On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
> > >
> > > > COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
> > > > configure options. The rest gets this variable in front (e.g., if
> PREFIX
> > > > was set to "/" at the configuration stage, then COUCHDB_TEST_PATH
> should
> > > >
> > >
> > > be
> > > > set to ""). E.g., few things from my installation, I have:
> > > >
> > > > - default.ini and local.ini in /usr/local/etc/coucdb/ and that
> requires:
> > > > COUCHDB_TEST_PATH "/usr/local"
> > > > COUCHDB_TEST_ETC_PATH "etc/couchdb"
> > > >
> > >
> > >
> > > Ok, so basically I am trying to integrate as much as possible with
> Ubuntu
> > > – so I set my prefix to /usr (see github link).
> > >
> > > COUCHDB_TEST_PATH "/usr"
> > > >
> > > > - CouchDB .beam files path in
> > > > /usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
> > > > COUCHDB_TEST_PATH "/usr/local"
> > > > COUCHDB_TEST_LIB_PATH "lib/couchdb"
> > > > COUCHDB_TEST_EXTRA "erlang/lib"
> > > > COUCHDB_TEST_VERSION "-1.2.0"
> > > > COUCHDB_TEST_EBIN "ebin"
> > > >
> > >
> > >
> > > This is the path when I install my package:
> > > /usr/lib/couchdb/erlang/lib/couch-1.2.0/
> > >
> > >
> > > >
> > > > The problem may be in COUCHDB_TEST_ETAP_PATH "./tests" (preferable
> full
> > > > path and not relative because the tests don't know too much about
> > > >
> > >
> > > relative
> > > > paths). Can you try to set it as a full path and execute the tests
> again?
> > > > You don't need to clean anything from the previous executions.
> > > >
> > >
> > >
> > >
> > > I just did that – tests fail the same way.
> > >
> > > I can't really tell what the cause is since the erl_crash.dump is kinda
> > > hard to read. Signal vs. noise. :)
> > >
> > > Till
> > > >
> > > > CGS
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Jun 12, 2012 at 4:06 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com) (mailto:
> > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > >
> > > > > Yes, pretty much:
> > > > > https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
> > > > >
> > > > > I haven't checked in detail, but – do those lib/etc paths get
> prefixed
> > > > > with COUCHDB_TEST_PATH?
> > > > >
> > > > > Till
> > > > >
> > > > > --
> > > > > till
> > > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > > >
> > > > >
> > > > > On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
> > > > >
> > > > > > Have you modified the parameters from test.cfg to point to your
> > > CouchDB
> > > > > > installation?
> > > > > >
> > > > > > CGS
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com(mailto:
> klimpong@gmail.com) (mailto:
> > > klimpong@gmail.com (mailto:klimpong@gmail.com)) (mailto:
> > > > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> > > > > > >
> > > > > > > > Well, the default installation requires root permissions as
> many
> > > > > paths
> > > > > > > are
> > > > > > > > accessible only as root (you did 'sudo make install', didn't
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > you?).
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > Also,
> > > > > > > > you do sudo apt-get install, so, the tests will be run under
> root
> > > > > > > > permissions. That's why I said in the README file that these
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > tests
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > should
> > > > > > > > be run as root (a.k.a. sudo command).
> > > > > > > >
> > > > > > > > CGS
> > > > > > > Sorry, over read that before, but the failures are still
> happening
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > with
> > > > > > > sudo:
> > > > > > > https://gist.github.com/2917336
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
3> test_util:config_files().
["/usr/etc/couchdb/default.ini",
"/home/vagrant/buildbox/testsuite/tests/random_port.ini",
"/usr/etc/couchdb/local.ini"]
This is the problem – the prefix is not used for sysconfdir. The dir is in /etc not in PREFIX/etc.
Till
--
till
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, June 12, 2012 at 5:52 PM, CGS wrote:
> Can you do a test for me? Please, open an Erlang shell (erl) in tests/
> directory (hopefully you will still have the test_util.beam file) and
> copy-paste these lines (exit with CTRL+g and q<Enter>):
>
> l(test_util).
> test_util:init_code_path().
> test_util:config_files().
> l(couch_config).
> couch_config:start_link(test_util:config_files()).
> l(couch_drv).
> couch_drv:start_link().
>
> Your result should look like this:
>
> 1> l(test_util).
> {module,test_util}
> 2> test_util:init_code_path().
> ok
> 3> test_util:config_files().
> ["/usr/etc/couchdb/default.ini",
> "<path_to_tests_dir>/random_port.ini",
> "/usr/etc/couchdb/local.ini"]
> 4> l(couch_config).
> {module,couch_config}
> 5> couch_config:start_link(test_util:config_files()).
> {ok,<0.38.0>}
> 6> l(couch_drv).
> {module,couch_drv}
> 7> couch_drv:start_link().
> {ok,<0.41.0>}
>
> where <path_to_local_dir> should be the same set COUCHDB_TEST_ETAP_PATH and
> the same with the result of pwd (considering you are still in tests
> directory). Let me know the output, please.
>
> CGS
>
>
>
>
> On Tue, Jun 12, 2012 at 5:21 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
>
> >
> >
> > On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
> >
> > > COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
> > > configure options. The rest gets this variable in front (e.g., if PREFIX
> > > was set to "/" at the configuration stage, then COUCHDB_TEST_PATH should
> > >
> >
> > be
> > > set to ""). E.g., few things from my installation, I have:
> > >
> > > - default.ini and local.ini in /usr/local/etc/coucdb/ and that requires:
> > > COUCHDB_TEST_PATH "/usr/local"
> > > COUCHDB_TEST_ETC_PATH "etc/couchdb"
> > >
> >
> >
> > Ok, so basically I am trying to integrate as much as possible with Ubuntu
> > – so I set my prefix to /usr (see github link).
> >
> > COUCHDB_TEST_PATH "/usr"
> > >
> > > - CouchDB .beam files path in
> > > /usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
> > > COUCHDB_TEST_PATH "/usr/local"
> > > COUCHDB_TEST_LIB_PATH "lib/couchdb"
> > > COUCHDB_TEST_EXTRA "erlang/lib"
> > > COUCHDB_TEST_VERSION "-1.2.0"
> > > COUCHDB_TEST_EBIN "ebin"
> > >
> >
> >
> > This is the path when I install my package:
> > /usr/lib/couchdb/erlang/lib/couch-1.2.0/
> >
> >
> > >
> > > The problem may be in COUCHDB_TEST_ETAP_PATH "./tests" (preferable full
> > > path and not relative because the tests don't know too much about
> > >
> >
> > relative
> > > paths). Can you try to set it as a full path and execute the tests again?
> > > You don't need to clean anything from the previous executions.
> > >
> >
> >
> >
> > I just did that – tests fail the same way.
> >
> > I can't really tell what the cause is since the erl_crash.dump is kinda
> > hard to read. Signal vs. noise. :)
> >
> > Till
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > > On Tue, Jun 12, 2012 at 4:06 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > >
> > > > Yes, pretty much:
> > > > https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
> > > >
> > > > I haven't checked in detail, but – do those lib/etc paths get prefixed
> > > > with COUCHDB_TEST_PATH?
> > > >
> > > > Till
> > > >
> > > > --
> > > > till
> > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > >
> > > >
> > > > On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
> > > >
> > > > > Have you modified the parameters from test.cfg to point to your
> > CouchDB
> > > > > installation?
> > > > >
> > > > > CGS
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> > klimpong@gmail.com (mailto:klimpong@gmail.com)) (mailto:
> > > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> > > > > >
> > > > > > > Well, the default installation requires root permissions as many
> > > > paths
> > > > > > are
> > > > > > > accessible only as root (you did 'sudo make install', didn't
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > you?).
> > > > > >
> > > > >
> > > >
> > > >
> > > > Also,
> > > > > > > you do sudo apt-get install, so, the tests will be run under root
> > > > > > > permissions. That's why I said in the README file that these
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > tests
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > should
> > > > > > > be run as root (a.k.a. sudo command).
> > > > > > >
> > > > > > > CGS
> > > > > > Sorry, over read that before, but the failures are still happening
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > with
> > > > > > sudo:
> > > > > > https://gist.github.com/2917336
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Can you do a test for me? Please, open an Erlang shell (erl) in tests/
directory (hopefully you will still have the test_util.beam file) and
copy-paste these lines (exit with CTRL+g and q<Enter>):
l(test_util).
test_util:init_code_path().
test_util:config_files().
l(couch_config).
couch_config:start_link(test_util:config_files()).
l(couch_drv).
couch_drv:start_link().
Your result should look like this:
1> l(test_util).
{module,test_util}
2> test_util:init_code_path().
ok
3> test_util:config_files().
["/usr/etc/couchdb/default.ini",
"<path_to_tests_dir>/random_port.ini",
"/usr/etc/couchdb/local.ini"]
4> l(couch_config).
{module,couch_config}
5> couch_config:start_link(test_util:config_files()).
{ok,<0.38.0>}
6> l(couch_drv).
{module,couch_drv}
7> couch_drv:start_link().
{ok,<0.41.0>}
where <path_to_local_dir> should be the same set COUCHDB_TEST_ETAP_PATH and
the same with the result of pwd (considering you are still in tests
directory). Let me know the output, please.
CGS
On Tue, Jun 12, 2012 at 5:21 PM, till <kl...@gmail.com> wrote:
>
>
> On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
>
> > COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
> > configure options. The rest gets this variable in front (e.g., if PREFIX
> > was set to "/" at the configuration stage, then COUCHDB_TEST_PATH should
> be
> > set to ""). E.g., few things from my installation, I have:
> >
> > - default.ini and local.ini in /usr/local/etc/coucdb/ and that requires:
> > COUCHDB_TEST_PATH "/usr/local"
> > COUCHDB_TEST_ETC_PATH "etc/couchdb"
> >
> >
>
> Ok, so basically I am trying to integrate as much as possible with Ubuntu
> – so I set my prefix to /usr (see github link).
>
> COUCHDB_TEST_PATH "/usr"
> >
> > - CouchDB .beam files path in
> > /usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
> > COUCHDB_TEST_PATH "/usr/local"
> > COUCHDB_TEST_LIB_PATH "lib/couchdb"
> > COUCHDB_TEST_EXTRA "erlang/lib"
> > COUCHDB_TEST_VERSION "-1.2.0"
> > COUCHDB_TEST_EBIN "ebin"
> >
> >
>
> This is the path when I install my package:
> /usr/lib/couchdb/erlang/lib/couch-1.2.0/
>
>
> >
> > The problem may be in COUCHDB_TEST_ETAP_PATH "./tests" (preferable full
> > path and not relative because the tests don't know too much about
> relative
> > paths). Can you try to set it as a full path and execute the tests again?
> > You don't need to clean anything from the previous executions.
> >
> >
>
>
> I just did that – tests fail the same way.
>
> I can't really tell what the cause is since the erl_crash.dump is kinda
> hard to read. Signal vs. noise. :)
>
> Till
> >
> > CGS
> >
> >
> >
> >
> > On Tue, Jun 12, 2012 at 4:06 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> >
> > > Yes, pretty much:
> > > https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
> > >
> > > I haven't checked in detail, but – do those lib/etc paths get prefixed
> > > with COUCHDB_TEST_PATH?
> > >
> > > Till
> > >
> > > --
> > > till
> > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > >
> > >
> > > On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
> > >
> > > > Have you modified the parameters from test.cfg to point to your
> CouchDB
> > > > installation?
> > > >
> > > > CGS
> > > >
> > > >
> > > >
> > > > On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com) (mailto:
> > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > >
> > > > >
> > > > >
> > > > > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> > > > >
> > > > > > Well, the default installation requires root permissions as many
> > > paths
> > > > > are
> > > > > > accessible only as root (you did 'sudo make install', didn't
> you?).
> > > > >
> > > > >
> > > >
> > >
> > > Also,
> > > > > > you do sudo apt-get install, so, the tests will be run under root
> > > > > > permissions. That's why I said in the README file that these
> tests
> > > > > >
> > > > >
> > > >
> > >
> > > should
> > > > > > be run as root (a.k.a. sudo command).
> > > > > >
> > > > > > CGS
> > > > > Sorry, over read that before, but the failures are still happening
> with
> > > > > sudo:
> > > > > https://gist.github.com/2917336
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
> COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
> configure options. The rest gets this variable in front (e.g., if PREFIX
> was set to "/" at the configuration stage, then COUCHDB_TEST_PATH should be
> set to ""). E.g., few things from my installation, I have:
>
> - default.ini and local.ini in /usr/local/etc/coucdb/ and that requires:
> COUCHDB_TEST_PATH "/usr/local"
> COUCHDB_TEST_ETC_PATH "etc/couchdb"
>
>
Ok, so basically I am trying to integrate as much as possible with Ubuntu – so I set my prefix to /usr (see github link).
COUCHDB_TEST_PATH "/usr"
>
> - CouchDB .beam files path in
> /usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
> COUCHDB_TEST_PATH "/usr/local"
> COUCHDB_TEST_LIB_PATH "lib/couchdb"
> COUCHDB_TEST_EXTRA "erlang/lib"
> COUCHDB_TEST_VERSION "-1.2.0"
> COUCHDB_TEST_EBIN "ebin"
>
>
This is the path when I install my package: /usr/lib/couchdb/erlang/lib/couch-1.2.0/
>
> The problem may be in COUCHDB_TEST_ETAP_PATH "./tests" (preferable full
> path and not relative because the tests don't know too much about relative
> paths). Can you try to set it as a full path and execute the tests again?
> You don't need to clean anything from the previous executions.
>
>
I just did that – tests fail the same way.
I can't really tell what the cause is since the erl_crash.dump is kinda hard to read. Signal vs. noise. :)
Till
>
> CGS
>
>
>
>
> On Tue, Jun 12, 2012 at 4:06 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
>
> > Yes, pretty much:
> > https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
> >
> > I haven't checked in detail, but – do those lib/etc paths get prefixed
> > with COUCHDB_TEST_PATH?
> >
> > Till
> >
> > --
> > till
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> >
> >
> > On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
> >
> > > Have you modified the parameters from test.cfg to point to your CouchDB
> > > installation?
> > >
> > > CGS
> > >
> > >
> > >
> > > On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > >
> > > >
> > > >
> > > > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> > > >
> > > > > Well, the default installation requires root permissions as many
> > paths
> > > > are
> > > > > accessible only as root (you did 'sudo make install', didn't you?).
> > > >
> > > >
> > >
> >
> > Also,
> > > > > you do sudo apt-get install, so, the tests will be run under root
> > > > > permissions. That's why I said in the README file that these tests
> > > > >
> > > >
> > >
> >
> > should
> > > > > be run as root (a.k.a. sudo command).
> > > > >
> > > > > CGS
> > > > Sorry, over read that before, but the failures are still happening with
> > > > sudo:
> > > > https://gist.github.com/2917336
> > > >
> > >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
configure options. The rest gets this variable in front (e.g., if PREFIX
was set to "/" at the configuration stage, then COUCHDB_TEST_PATH should be
set to ""). E.g., few things from my installation, I have:
- default.ini and local.ini in /usr/local/etc/coucdb/ and that requires:
COUCHDB_TEST_PATH "/usr/local"
COUCHDB_TEST_ETC_PATH "etc/couchdb"
- CouchDB .beam files path in
/usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
COUCHDB_TEST_PATH "/usr/local"
COUCHDB_TEST_LIB_PATH "lib/couchdb"
COUCHDB_TEST_EXTRA "erlang/lib"
COUCHDB_TEST_VERSION "-1.2.0"
COUCHDB_TEST_EBIN "ebin"
The problem may be in COUCHDB_TEST_ETAP_PATH "./tests" (preferable full
path and not relative because the tests don't know too much about relative
paths). Can you try to set it as a full path and execute the tests again?
You don't need to clean anything from the previous executions.
CGS
On Tue, Jun 12, 2012 at 4:06 PM, till <kl...@gmail.com> wrote:
> Yes, pretty much:
> https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
>
> I haven't checked in detail, but – do those lib/etc paths get prefixed
> with COUCHDB_TEST_PATH?
>
> Till
>
> --
> till
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>
>
> On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
>
> > Have you modified the parameters from test.cfg to point to your CouchDB
> > installation?
> >
> > CGS
> >
> >
> >
> > On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> >
> > >
> > >
> > > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> > >
> > > > Well, the default installation requires root permissions as many
> paths
> > > are
> > > > accessible only as root (you did 'sudo make install', didn't you?).
> Also,
> > > > you do sudo apt-get install, so, the tests will be run under root
> > > > permissions. That's why I said in the README file that these tests
> should
> > > > be run as root (a.k.a. sudo command).
> > > >
> > > > CGS
> > > Sorry, over read that before, but the failures are still happening with
> > > sudo:
> > > https://gist.github.com/2917336
> > >
> >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
Yes, pretty much:
https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
I haven't checked in detail, but – do those lib/etc paths get prefixed with COUCHDB_TEST_PATH?
Till
--
till
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
> Have you modified the parameters from test.cfg to point to your CouchDB
> installation?
>
> CGS
>
>
>
> On Tue, Jun 12, 2012 at 2:57 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
>
> >
> >
> > On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> >
> > > Well, the default installation requires root permissions as many paths
> > are
> > > accessible only as root (you did 'sudo make install', didn't you?). Also,
> > > you do sudo apt-get install, so, the tests will be run under root
> > > permissions. That's why I said in the README file that these tests should
> > > be run as root (a.k.a. sudo command).
> > >
> > > CGS
> > Sorry, over read that before, but the failures are still happening with
> > sudo:
> > https://gist.github.com/2917336
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Have you modified the parameters from test.cfg to point to your CouchDB
installation?
CGS
On Tue, Jun 12, 2012 at 2:57 PM, till <kl...@gmail.com> wrote:
>
>
> On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
>
> > Well, the default installation requires root permissions as many paths
> are
> > accessible only as root (you did 'sudo make install', didn't you?). Also,
> > you do sudo apt-get install, so, the tests will be run under root
> > permissions. That's why I said in the README file that these tests should
> > be run as root (a.k.a. sudo command).
> >
> > CGS
> Sorry, over read that before, but the failures are still happening with
> sudo:
> https://gist.github.com/2917336
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
> Well, the default installation requires root permissions as many paths are
> accessible only as root (you did 'sudo make install', didn't you?). Also,
> you do sudo apt-get install, so, the tests will be run under root
> permissions. That's why I said in the README file that these tests should
> be run as root (a.k.a. sudo command).
>
> CGS
Sorry, over read that before, but the failures are still happening with sudo:
https://gist.github.com/2917336
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Well, the default installation requires root permissions as many paths are
accessible only as root (you did 'sudo make install', didn't you?). Also,
you do sudo apt-get install, so, the tests will be run under root
permissions. That's why I said in the README file that these tests should
be run as root (a.k.a. sudo command).
CGS
On Tue, Jun 12, 2012 at 2:25 PM, till <kl...@gmail.com> wrote:
>
>
> On Tuesday, June 12, 2012 at 2:09 PM, CGS wrote:
>
> > "Dubious, test returned 1 (wstat 256, 0x100)" says that the permissions
> are
> > not in place (therefore, files cannot be created/access, processes are
> not
> > started/accessible and so on). Could you tell me where exactly you got
> that
> > error?
> >
> > CGS
> E.g. icu_driver.t test – and a couple others.
>
> I am re-running it with sudo now. But that strikes me as odd.
>
> Till
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
On Tuesday, June 12, 2012 at 2:09 PM, CGS wrote:
> "Dubious, test returned 1 (wstat 256, 0x100)" says that the permissions are
> not in place (therefore, files cannot be created/access, processes are not
> started/accessible and so on). Could you tell me where exactly you got that
> error?
>
> CGS
E.g. icu_driver.t test – and a couple others.
I am re-running it with sudo now. But that strikes me as odd.
Till
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
"Dubious, test returned 1 (wstat 256, 0x100)" says that the permissions are
not in place (therefore, files cannot be created/access, processes are not
started/accessible and so on). Could you tell me where exactly you got that
error?
CGS
On Tue, Jun 12, 2012 at 1:46 PM, till <kl...@gmail.com> wrote:
>
>
> On Monday, June 11, 2012 at 6:57 PM, CGS wrote:
>
> > Let us know if any test fail and give us the log of the tests. The tests
> > themselves are pretty self explanatory. If not, at least some tests are
> > using the CouchDB log. So, I think there will be enough info for
> debugging.
> >
> > CGS
> Ok,
>
> so I started a clean VM with lucid and apt-get install apache-couchdb.
>
> Then a couple tests produce erlang_crash.dump files and others fail with
> "Dubious, test returned 1 (wstat 256, 0x100)".
>
> Can't figure out what that means though? Googled it a bit but none of the
> errors seem to relate this.
>
> Till
>
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
"Dubious, test returned 1 (wstat 256, 0x100)" says that the permissions are
not in place (therefore, files cannot be created/access, processes are not
started/accessible and so on). Could you tell me where exactly you got that
error?
CGS
On Tue, Jun 12, 2012 at 1:46 PM, till <kl...@gmail.com> wrote:
>
>
> On Monday, June 11, 2012 at 6:57 PM, CGS wrote:
>
> > Let us know if any test fail and give us the log of the tests. The tests
> > themselves are pretty self explanatory. If not, at least some tests are
> > using the CouchDB log. So, I think there will be enough info for
> debugging.
> >
> > CGS
> Ok,
>
> so I started a clean VM with lucid and apt-get install apache-couchdb.
>
> Then a couple tests produce erlang_crash.dump files and others fail with
> "Dubious, test returned 1 (wstat 256, 0x100)".
>
> Can't figure out what that means though? Googled it a bit but none of the
> errors seem to relate this.
>
> Till
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
On Monday, June 11, 2012 at 6:57 PM, CGS wrote:
> Let us know if any test fail and give us the log of the tests. The tests
> themselves are pretty self explanatory. If not, at least some tests are
> using the CouchDB log. So, I think there will be enough info for debugging.
>
> CGS
Ok,
so I started a clean VM with lucid and apt-get install apache-couchdb.
Then a couple tests produce erlang_crash.dump files and others fail with "Dubious, test returned 1 (wstat 256, 0x100)".
Can't figure out what that means though? Googled it a bit but none of the errors seem to relate this.
Till
Re: CouchDB packaging for Ubuntu
Posted by Andy Wenk <an...@nms.de>.
Till - awesome work! I just gave the link to your github repo to my
mates at S2 ;-)
On 11 June 2012 18:57, CGS <cg...@gmail.com> wrote:
> Let us know if any test fail and give us the log of the tests. The tests
> themselves are pretty self explanatory. If not, at least some tests are
> using the CouchDB log. So, I think there will be enough info for debugging.
>
> CGS
>
>
>
>
>
> On Mon, Jun 11, 2012 at 5:12 PM, till <kl...@gmail.com> wrote:
>
>> Ok,
>>
>> my working repo is here:
>> https://github.com/till/couchdb-deb
>>
>> So does anyone have any idea how to debug failed test cases? They never
>> failed for me before. :D
>>
>> Till
>>
>>
>> On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
>>
>> > Not at all. After all, I do not do this for my personal interest, but for
>> > this community. I am glad if I can help.
>> >
>> > Cheers,
>> > CGS
>> >
>> >
>> >
>> >
>> > On Mon, Jun 11, 2012 at 3:58 PM, till <klimpong@gmail.com (mailto:
>> klimpong@gmail.com)> wrote:
>> >
>> > > Hey,
>> > >
>> > > thanks, I'm gonna test this shortly. Do you mind if I push it one of my
>> > > repo?
>> > >
>> > > Till
>> > >
>> > >
>> > > On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I isolated the tests which are started with make check and make them
>> run
>> > > over the default installation under Ubuntu 12.10. Please, let me know
>> if it
>> > > is what you need (there is a README file in the archive).
>> > > >
>> > > > CGS
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:
>> klimpong@gmail.com) (mailto:
>> > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
>> > > > > Hey,
>> > > > >
>> > > > > [ CC'd user@ to get more feedback. ]
>> > > > >
>> > > > > I made some progress.
>> > > > >
>> > > > > I have builds for the following more or less ready:
>> > > > >
>> > > > > * karmic
>> > > > > * lucid
>> > > > > * maverick
>> > > > > * oneiric
>> > > > > * natty
>> > > > > * precise
>> > > > >
>> > > > > It's building and I am trying to refine the process a bit. So it
>> might
>> > > break in between [aka WIP]. I'm just adding this as a disclaimer.
>> > > > >
>> > > > > https://launchpad.net/~till-php/+archive/couchdb<
>> https://launchpad.net/%7Etill-php/+archive/couchdb>
>> > > > >
>> > > > > Would you mind testing my builds? :) So far, I only tested lucid
>> > > briefly (and ran into the xulrunner issue, which I think I have
>> auto-fixed
>> > > now). Besides I just started it up, created a DB and entered some docs
>> into
>> > > it.
>> > > > >
>> > > > > (Also, @Jan:)
>> > > > >
>> > > > > I'm trying to figure out how to setup more automated testing. "make
>> > > check" always requires the source tree to be present, I'd like "make
>> check"
>> > > against my installed binaries. I saw the "verify installation" in
>> Futon –
>> > > something like that for the command line so I can iterate on these
>> builds
>> > > and trigger a "test this" in a continuous integration setup. Building
>> is
>> > > part of it, but since building a binary and installing it are two
>> separate
>> > > steps I want to ensure that the second step also works. I am still
>> trying
>> > > to wrap my head around a setup where I can maybe knife up a few
>> instances
>> > > in THE CLOUD, install my package, run its test-suite and confirm.
>> > > > >
>> > > > > Till
>> > > > >
>> > > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
>> > > running.
>> > > > > > Unfortunately, I've never built a deb package, so, I cannot
>> provide
>> > > > >
>> > > >
>> > >
>> > > such a
>> > > > > > package. Nevertheless, if you have any problem in building it,
>> just
>> > > > >
>> > > >
>> > >
>> > > let me
>> > > > > > know and I will try to help.
>> > > > > >
>> > > > > > About the mailing list, I suppose adding the CouchDB users (to
>> get
>> > > an idea
>> > > > > > which is the desired Ubuntu distro) and/or Debian (you may get
>> > > > >
>> > > >
>> > >
>> > > support in
>> > > > > > testing and debugging) lists wouldn't be such a bad idea, but
>> it's
>> > > > >
>> > > >
>> > >
>> > > your
>> > > > > > call here.
>> > > > > >
>> > > > > > CGS
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com(mailto:
>> klimpong@gmail.com) (mailto:
>> > > klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
>> > > > > >
>> > > > > > > Hey,
>> > > > > > >
>> > > > > > > I've been scratching my own itch and started building 1.2.0
>> for a
>> > > couple
>> > > > > > > Ubuntu distributions.
>> > > > > > >
>> > > > > > > It's a WIP but I was wondering the following:
>> > > > > > >
>> > > > > > > 1) It builds – but does it work? Is the best bet to run the
>> test
>> > > suite in
>> > > > > > > futon, or is there something I could run on the command line
>> when
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > > the
>> > > > > > > package is installed? I'd prefer the command line to include
>> it in
>> > > > > >
>> > > > >
>> > > >
>> > >
>> > > some
>> > > > > > > sort of continuous testing without a browser.
>> > > > > > >
>> > > > > > > 2) Who'd have some interest in testing this?
>> > > > > > >
>> > > > > > > 3) Which distributions are wanted – I started with karmic and
>> > > lucid and
>> > > > > > > had planned to build all the way up to 12.10.
>> > > > > > >
>> > > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
>> > > > > > >
>> > > > > > > Till
>> > > >
>> > > >
>> > > > Attachments:
>> > > > - couchdb_etap.tgz
>> > > >
>> > >
>> > >
>> >
>> >
>> >
>>
>>
>>
--
Andy Wenk
Hamburg - Germany
RockIt!
"CouchDB - Das Praxisbuch für Entwickler und Administratoren"
http://www.galileocomputing.de/2462
http://www.couchdb-buch.de
+++ english version is coming +++
http://www.couchdb-book.com
"PostgreSQL 8.4: Das Praxisbuch"
http://www.galileocomputing.de/2008
http://www.pg-praxisbuch.de
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
On Monday, June 11, 2012 at 6:57 PM, CGS wrote:
> Let us know if any test fail and give us the log of the tests. The tests
> themselves are pretty self explanatory. If not, at least some tests are
> using the CouchDB log. So, I think there will be enough info for debugging.
>
> CGS
Ok,
so I started a clean VM with lucid and apt-get install apache-couchdb.
Then a couple tests produce erlang_crash.dump files and others fail with "Dubious, test returned 1 (wstat 256, 0x100)".
Can't figure out what that means though? Googled it a bit but none of the errors seem to relate this.
Till
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Let us know if any test fail and give us the log of the tests. The tests
themselves are pretty self explanatory. If not, at least some tests are
using the CouchDB log. So, I think there will be enough info for debugging.
CGS
On Mon, Jun 11, 2012 at 5:12 PM, till <kl...@gmail.com> wrote:
> Ok,
>
> my working repo is here:
> https://github.com/till/couchdb-deb
>
> So does anyone have any idea how to debug failed test cases? They never
> failed for me before. :D
>
> Till
>
>
> On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
>
> > Not at all. After all, I do not do this for my personal interest, but for
> > this community. I am glad if I can help.
> >
> > Cheers,
> > CGS
> >
> >
> >
> >
> > On Mon, Jun 11, 2012 at 3:58 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> >
> > > Hey,
> > >
> > > thanks, I'm gonna test this shortly. Do you mind if I push it one of my
> > > repo?
> > >
> > > Till
> > >
> > >
> > > On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
> > >
> > > > Hi,
> > > >
> > > > I isolated the tests which are started with make check and make them
> run
> > > over the default installation under Ubuntu 12.10. Please, let me know
> if it
> > > is what you need (there is a README file in the archive).
> > > >
> > > > CGS
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com) (mailto:
> > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > > > Hey,
> > > > >
> > > > > [ CC'd user@ to get more feedback. ]
> > > > >
> > > > > I made some progress.
> > > > >
> > > > > I have builds for the following more or less ready:
> > > > >
> > > > > * karmic
> > > > > * lucid
> > > > > * maverick
> > > > > * oneiric
> > > > > * natty
> > > > > * precise
> > > > >
> > > > > It's building and I am trying to refine the process a bit. So it
> might
> > > break in between [aka WIP]. I'm just adding this as a disclaimer.
> > > > >
> > > > > https://launchpad.net/~till-php/+archive/couchdb<
> https://launchpad.net/%7Etill-php/+archive/couchdb>
> > > > >
> > > > > Would you mind testing my builds? :) So far, I only tested lucid
> > > briefly (and ran into the xulrunner issue, which I think I have
> auto-fixed
> > > now). Besides I just started it up, created a DB and entered some docs
> into
> > > it.
> > > > >
> > > > > (Also, @Jan:)
> > > > >
> > > > > I'm trying to figure out how to setup more automated testing. "make
> > > check" always requires the source tree to be present, I'd like "make
> check"
> > > against my installed binaries. I saw the "verify installation" in
> Futon –
> > > something like that for the command line so I can iterate on these
> builds
> > > and trigger a "test this" in a continuous integration setup. Building
> is
> > > part of it, but since building a binary and installing it are two
> separate
> > > steps I want to ensure that the second step also works. I am still
> trying
> > > to wrap my head around a setup where I can maybe knife up a few
> instances
> > > in THE CLOUD, install my package, run its test-suite and confirm.
> > > > >
> > > > > Till
> > > > >
> > > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
> > > running.
> > > > > > Unfortunately, I've never built a deb package, so, I cannot
> provide
> > > > >
> > > >
> > >
> > > such a
> > > > > > package. Nevertheless, if you have any problem in building it,
> just
> > > > >
> > > >
> > >
> > > let me
> > > > > > know and I will try to help.
> > > > > >
> > > > > > About the mailing list, I suppose adding the CouchDB users (to
> get
> > > an idea
> > > > > > which is the desired Ubuntu distro) and/or Debian (you may get
> > > > >
> > > >
> > >
> > > support in
> > > > > > testing and debugging) lists wouldn't be such a bad idea, but
> it's
> > > > >
> > > >
> > >
> > > your
> > > > > > call here.
> > > > > >
> > > > > > CGS
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com(mailto:
> klimpong@gmail.com) (mailto:
> > > klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > > > > >
> > > > > > > Hey,
> > > > > > >
> > > > > > > I've been scratching my own itch and started building 1.2.0
> for a
> > > couple
> > > > > > > Ubuntu distributions.
> > > > > > >
> > > > > > > It's a WIP but I was wondering the following:
> > > > > > >
> > > > > > > 1) It builds – but does it work? Is the best bet to run the
> test
> > > suite in
> > > > > > > futon, or is there something I could run on the command line
> when
> > > > > >
> > > > >
> > > >
> > >
> > > the
> > > > > > > package is installed? I'd prefer the command line to include
> it in
> > > > > >
> > > > >
> > > >
> > >
> > > some
> > > > > > > sort of continuous testing without a browser.
> > > > > > >
> > > > > > > 2) Who'd have some interest in testing this?
> > > > > > >
> > > > > > > 3) Which distributions are wanted – I started with karmic and
> > > lucid and
> > > > > > > had planned to build all the way up to 12.10.
> > > > > > >
> > > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > > > > >
> > > > > > > Till
> > > >
> > > >
> > > > Attachments:
> > > > - couchdb_etap.tgz
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
I submitted a bunch of new builds to the launchpad farm.
I tested Lucid (Ubuntu 10.04 LTS) so far (hit "verify installation" in futon).
If anyone wants to give one of these builds a go and give me feedback – feel free to. ;-)
Till
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
I submitted a bunch of new builds to the launchpad farm.
I tested Lucid (Ubuntu 10.04 LTS) so far (hit "verify installation" in futon).
If anyone wants to give one of these builds a go and give me feedback – feel free to. ;-)
Till
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Let us know if any test fail and give us the log of the tests. The tests
themselves are pretty self explanatory. If not, at least some tests are
using the CouchDB log. So, I think there will be enough info for debugging.
CGS
On Mon, Jun 11, 2012 at 5:12 PM, till <kl...@gmail.com> wrote:
> Ok,
>
> my working repo is here:
> https://github.com/till/couchdb-deb
>
> So does anyone have any idea how to debug failed test cases? They never
> failed for me before. :D
>
> Till
>
>
> On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
>
> > Not at all. After all, I do not do this for my personal interest, but for
> > this community. I am glad if I can help.
> >
> > Cheers,
> > CGS
> >
> >
> >
> >
> > On Mon, Jun 11, 2012 at 3:58 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> >
> > > Hey,
> > >
> > > thanks, I'm gonna test this shortly. Do you mind if I push it one of my
> > > repo?
> > >
> > > Till
> > >
> > >
> > > On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
> > >
> > > > Hi,
> > > >
> > > > I isolated the tests which are started with make check and make them
> run
> > > over the default installation under Ubuntu 12.10. Please, let me know
> if it
> > > is what you need (there is a README file in the archive).
> > > >
> > > > CGS
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com) (mailto:
> > > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > > > Hey,
> > > > >
> > > > > [ CC'd user@ to get more feedback. ]
> > > > >
> > > > > I made some progress.
> > > > >
> > > > > I have builds for the following more or less ready:
> > > > >
> > > > > * karmic
> > > > > * lucid
> > > > > * maverick
> > > > > * oneiric
> > > > > * natty
> > > > > * precise
> > > > >
> > > > > It's building and I am trying to refine the process a bit. So it
> might
> > > break in between [aka WIP]. I'm just adding this as a disclaimer.
> > > > >
> > > > > https://launchpad.net/~till-php/+archive/couchdb<
> https://launchpad.net/%7Etill-php/+archive/couchdb>
> > > > >
> > > > > Would you mind testing my builds? :) So far, I only tested lucid
> > > briefly (and ran into the xulrunner issue, which I think I have
> auto-fixed
> > > now). Besides I just started it up, created a DB and entered some docs
> into
> > > it.
> > > > >
> > > > > (Also, @Jan:)
> > > > >
> > > > > I'm trying to figure out how to setup more automated testing. "make
> > > check" always requires the source tree to be present, I'd like "make
> check"
> > > against my installed binaries. I saw the "verify installation" in
> Futon –
> > > something like that for the command line so I can iterate on these
> builds
> > > and trigger a "test this" in a continuous integration setup. Building
> is
> > > part of it, but since building a binary and installing it are two
> separate
> > > steps I want to ensure that the second step also works. I am still
> trying
> > > to wrap my head around a setup where I can maybe knife up a few
> instances
> > > in THE CLOUD, install my package, run its test-suite and confirm.
> > > > >
> > > > > Till
> > > > >
> > > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
> > > running.
> > > > > > Unfortunately, I've never built a deb package, so, I cannot
> provide
> > > > >
> > > >
> > >
> > > such a
> > > > > > package. Nevertheless, if you have any problem in building it,
> just
> > > > >
> > > >
> > >
> > > let me
> > > > > > know and I will try to help.
> > > > > >
> > > > > > About the mailing list, I suppose adding the CouchDB users (to
> get
> > > an idea
> > > > > > which is the desired Ubuntu distro) and/or Debian (you may get
> > > > >
> > > >
> > >
> > > support in
> > > > > > testing and debugging) lists wouldn't be such a bad idea, but
> it's
> > > > >
> > > >
> > >
> > > your
> > > > > > call here.
> > > > > >
> > > > > > CGS
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com(mailto:
> klimpong@gmail.com) (mailto:
> > > klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > > > > >
> > > > > > > Hey,
> > > > > > >
> > > > > > > I've been scratching my own itch and started building 1.2.0
> for a
> > > couple
> > > > > > > Ubuntu distributions.
> > > > > > >
> > > > > > > It's a WIP but I was wondering the following:
> > > > > > >
> > > > > > > 1) It builds – but does it work? Is the best bet to run the
> test
> > > suite in
> > > > > > > futon, or is there something I could run on the command line
> when
> > > > > >
> > > > >
> > > >
> > >
> > > the
> > > > > > > package is installed? I'd prefer the command line to include
> it in
> > > > > >
> > > > >
> > > >
> > >
> > > some
> > > > > > > sort of continuous testing without a browser.
> > > > > > >
> > > > > > > 2) Who'd have some interest in testing this?
> > > > > > >
> > > > > > > 3) Which distributions are wanted – I started with karmic and
> > > lucid and
> > > > > > > had planned to build all the way up to 12.10.
> > > > > > >
> > > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > > > > >
> > > > > > > Till
> > > >
> > > >
> > > > Attachments:
> > > > - couchdb_etap.tgz
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
Ok,
my working repo is here:
https://github.com/till/couchdb-deb
So does anyone have any idea how to debug failed test cases? They never failed for me before. :D
Till
On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
> Not at all. After all, I do not do this for my personal interest, but for
> this community. I am glad if I can help.
>
> Cheers,
> CGS
>
>
>
>
> On Mon, Jun 11, 2012 at 3:58 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
>
> > Hey,
> >
> > thanks, I'm gonna test this shortly. Do you mind if I push it one of my
> > repo?
> >
> > Till
> >
> >
> > On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
> >
> > > Hi,
> > >
> > > I isolated the tests which are started with make check and make them run
> > over the default installation under Ubuntu 12.10. Please, let me know if it
> > is what you need (there is a README file in the archive).
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > >
> > > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > > Hey,
> > > >
> > > > [ CC'd user@ to get more feedback. ]
> > > >
> > > > I made some progress.
> > > >
> > > > I have builds for the following more or less ready:
> > > >
> > > > * karmic
> > > > * lucid
> > > > * maverick
> > > > * oneiric
> > > > * natty
> > > > * precise
> > > >
> > > > It's building and I am trying to refine the process a bit. So it might
> > break in between [aka WIP]. I'm just adding this as a disclaimer.
> > > >
> > > > https://launchpad.net/~till-php/+archive/couchdb<https://launchpad.net/%7Etill-php/+archive/couchdb>
> > > >
> > > > Would you mind testing my builds? :) So far, I only tested lucid
> > briefly (and ran into the xulrunner issue, which I think I have auto-fixed
> > now). Besides I just started it up, created a DB and entered some docs into
> > it.
> > > >
> > > > (Also, @Jan:)
> > > >
> > > > I'm trying to figure out how to setup more automated testing. "make
> > check" always requires the source tree to be present, I'd like "make check"
> > against my installed binaries. I saw the "verify installation" in Futon –
> > something like that for the command line so I can iterate on these builds
> > and trigger a "test this" in a continuous integration setup. Building is
> > part of it, but since building a binary and installing it are two separate
> > steps I want to ensure that the second step also works. I am still trying
> > to wrap my head around a setup where I can maybe knife up a few instances
> > in THE CLOUD, install my package, run its test-suite and confirm.
> > > >
> > > > Till
> > > >
> > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
> > running.
> > > > > Unfortunately, I've never built a deb package, so, I cannot provide
> > > >
> > >
> >
> > such a
> > > > > package. Nevertheless, if you have any problem in building it, just
> > > >
> > >
> >
> > let me
> > > > > know and I will try to help.
> > > > >
> > > > > About the mailing list, I suppose adding the CouchDB users (to get
> > an idea
> > > > > which is the desired Ubuntu distro) and/or Debian (you may get
> > > >
> > >
> >
> > support in
> > > > > testing and debugging) lists wouldn't be such a bad idea, but it's
> > > >
> > >
> >
> > your
> > > > > call here.
> > > > >
> > > > > CGS
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> > klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > > > >
> > > > > > Hey,
> > > > > >
> > > > > > I've been scratching my own itch and started building 1.2.0 for a
> > couple
> > > > > > Ubuntu distributions.
> > > > > >
> > > > > > It's a WIP but I was wondering the following:
> > > > > >
> > > > > > 1) It builds – but does it work? Is the best bet to run the test
> > suite in
> > > > > > futon, or is there something I could run on the command line when
> > > > >
> > > >
> > >
> >
> > the
> > > > > > package is installed? I'd prefer the command line to include it in
> > > > >
> > > >
> > >
> >
> > some
> > > > > > sort of continuous testing without a browser.
> > > > > >
> > > > > > 2) Who'd have some interest in testing this?
> > > > > >
> > > > > > 3) Which distributions are wanted – I started with karmic and
> > lucid and
> > > > > > had planned to build all the way up to 12.10.
> > > > > >
> > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > > > >
> > > > > > Till
> > >
> > >
> > > Attachments:
> > > - couchdb_etap.tgz
> > >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
Ok,
my working repo is here:
https://github.com/till/couchdb-deb
So does anyone have any idea how to debug failed test cases? They never failed for me before. :D
Till
On Monday, June 11, 2012 at 4:37 PM, CGS wrote:
> Not at all. After all, I do not do this for my personal interest, but for
> this community. I am glad if I can help.
>
> Cheers,
> CGS
>
>
>
>
> On Mon, Jun 11, 2012 at 3:58 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
>
> > Hey,
> >
> > thanks, I'm gonna test this shortly. Do you mind if I push it one of my
> > repo?
> >
> > Till
> >
> >
> > On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
> >
> > > Hi,
> > >
> > > I isolated the tests which are started with make check and make them run
> > over the default installation under Ubuntu 12.10. Please, let me know if it
> > is what you need (there is a README file in the archive).
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > >
> > > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> > klimpong@gmail.com (mailto:klimpong@gmail.com))> wrote:
> > > > Hey,
> > > >
> > > > [ CC'd user@ to get more feedback. ]
> > > >
> > > > I made some progress.
> > > >
> > > > I have builds for the following more or less ready:
> > > >
> > > > * karmic
> > > > * lucid
> > > > * maverick
> > > > * oneiric
> > > > * natty
> > > > * precise
> > > >
> > > > It's building and I am trying to refine the process a bit. So it might
> > break in between [aka WIP]. I'm just adding this as a disclaimer.
> > > >
> > > > https://launchpad.net/~till-php/+archive/couchdb<https://launchpad.net/%7Etill-php/+archive/couchdb>
> > > >
> > > > Would you mind testing my builds? :) So far, I only tested lucid
> > briefly (and ran into the xulrunner issue, which I think I have auto-fixed
> > now). Besides I just started it up, created a DB and entered some docs into
> > it.
> > > >
> > > > (Also, @Jan:)
> > > >
> > > > I'm trying to figure out how to setup more automated testing. "make
> > check" always requires the source tree to be present, I'd like "make check"
> > against my installed binaries. I saw the "verify installation" in Futon –
> > something like that for the command line so I can iterate on these builds
> > and trigger a "test this" in a continuous integration setup. Building is
> > part of it, but since building a binary and installing it are two separate
> > steps I want to ensure that the second step also works. I am still trying
> > to wrap my head around a setup where I can maybe knife up a few instances
> > in THE CLOUD, install my package, run its test-suite and confirm.
> > > >
> > > > Till
> > > >
> > > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
> > running.
> > > > > Unfortunately, I've never built a deb package, so, I cannot provide
> > > >
> > >
> >
> > such a
> > > > > package. Nevertheless, if you have any problem in building it, just
> > > >
> > >
> >
> > let me
> > > > > know and I will try to help.
> > > > >
> > > > > About the mailing list, I suppose adding the CouchDB users (to get
> > an idea
> > > > > which is the desired Ubuntu distro) and/or Debian (you may get
> > > >
> > >
> >
> > support in
> > > > > testing and debugging) lists wouldn't be such a bad idea, but it's
> > > >
> > >
> >
> > your
> > > > > call here.
> > > > >
> > > > > CGS
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:
> > klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > > > >
> > > > > > Hey,
> > > > > >
> > > > > > I've been scratching my own itch and started building 1.2.0 for a
> > couple
> > > > > > Ubuntu distributions.
> > > > > >
> > > > > > It's a WIP but I was wondering the following:
> > > > > >
> > > > > > 1) It builds – but does it work? Is the best bet to run the test
> > suite in
> > > > > > futon, or is there something I could run on the command line when
> > > > >
> > > >
> > >
> >
> > the
> > > > > > package is installed? I'd prefer the command line to include it in
> > > > >
> > > >
> > >
> >
> > some
> > > > > > sort of continuous testing without a browser.
> > > > > >
> > > > > > 2) Who'd have some interest in testing this?
> > > > > >
> > > > > > 3) Which distributions are wanted – I started with karmic and
> > lucid and
> > > > > > had planned to build all the way up to 12.10.
> > > > > >
> > > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > > > >
> > > > > > Till
> > >
> > >
> > > Attachments:
> > > - couchdb_etap.tgz
> > >
> >
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Not at all. After all, I do not do this for my personal interest, but for
this community. I am glad if I can help.
Cheers,
CGS
On Mon, Jun 11, 2012 at 3:58 PM, till <kl...@gmail.com> wrote:
> Hey,
>
> thanks, I'm gonna test this shortly. Do you mind if I push it one of my
> repo?
>
> Till
>
>
> On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
>
> > Hi,
> >
> > I isolated the tests which are started with make check and make them run
> over the default installation under Ubuntu 12.10. Please, let me know if it
> is what you need (there is a README file in the archive).
> >
> > CGS
> >
> >
> >
> >
> >
> > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> > > Hey,
> > >
> > > [ CC'd user@ to get more feedback. ]
> > >
> > > I made some progress.
> > >
> > > I have builds for the following more or less ready:
> > >
> > > * karmic
> > > * lucid
> > > * maverick
> > > * oneiric
> > > * natty
> > > * precise
> > >
> > > It's building and I am trying to refine the process a bit. So it might
> break in between [aka WIP]. I'm just adding this as a disclaimer.
> > >
> > > https://launchpad.net/~till-php/+archive/couchdb<https://launchpad.net/%7Etill-php/+archive/couchdb>
> > >
> > > Would you mind testing my builds? :) So far, I only tested lucid
> briefly (and ran into the xulrunner issue, which I think I have auto-fixed
> now). Besides I just started it up, created a DB and entered some docs into
> it.
> > >
> > > (Also, @Jan:)
> > >
> > > I'm trying to figure out how to setup more automated testing. "make
> check" always requires the source tree to be present, I'd like "make check"
> against my installed binaries. I saw the "verify installation" in Futon –
> something like that for the command line so I can iterate on these builds
> and trigger a "test this" in a continuous integration setup. Building is
> part of it, but since building a binary and installing it are two separate
> steps I want to ensure that the second step also works. I am still trying
> to wrap my head around a setup where I can maybe knife up a few instances
> in THE CLOUD, install my package, run its test-suite and confirm.
> > >
> > > Till
> > >
> > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> > >
> > > > Hi,
> > > >
> > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
> running.
> > > > Unfortunately, I've never built a deb package, so, I cannot provide
> such a
> > > > package. Nevertheless, if you have any problem in building it, just
> let me
> > > > know and I will try to help.
> > > >
> > > > About the mailing list, I suppose adding the CouchDB users (to get
> an idea
> > > > which is the desired Ubuntu distro) and/or Debian (you may get
> support in
> > > > testing and debugging) lists wouldn't be such a bad idea, but it's
> your
> > > > call here.
> > > >
> > > > CGS
> > > >
> > > >
> > > >
> > > >
> > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > > >
> > > > > Hey,
> > > > >
> > > > > I've been scratching my own itch and started building 1.2.0 for a
> couple
> > > > > Ubuntu distributions.
> > > > >
> > > > > It's a WIP but I was wondering the following:
> > > > >
> > > > > 1) It builds – but does it work? Is the best bet to run the test
> suite in
> > > > > futon, or is there something I could run on the command line when
> the
> > > > > package is installed? I'd prefer the command line to include it in
> some
> > > > > sort of continuous testing without a browser.
> > > > >
> > > > > 2) Who'd have some interest in testing this?
> > > > >
> > > > > 3) Which distributions are wanted – I started with karmic and
> lucid and
> > > > > had planned to build all the way up to 12.10.
> > > > >
> > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > > >
> > > > > Till
> > >
> >
> >
> > Attachments:
> > - couchdb_etap.tgz
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Not at all. After all, I do not do this for my personal interest, but for
this community. I am glad if I can help.
Cheers,
CGS
On Mon, Jun 11, 2012 at 3:58 PM, till <kl...@gmail.com> wrote:
> Hey,
>
> thanks, I'm gonna test this shortly. Do you mind if I push it one of my
> repo?
>
> Till
>
>
> On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
>
> > Hi,
> >
> > I isolated the tests which are started with make check and make them run
> over the default installation under Ubuntu 12.10. Please, let me know if it
> is what you need (there is a README file in the archive).
> >
> > CGS
> >
> >
> >
> >
> >
> > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> > > Hey,
> > >
> > > [ CC'd user@ to get more feedback. ]
> > >
> > > I made some progress.
> > >
> > > I have builds for the following more or less ready:
> > >
> > > * karmic
> > > * lucid
> > > * maverick
> > > * oneiric
> > > * natty
> > > * precise
> > >
> > > It's building and I am trying to refine the process a bit. So it might
> break in between [aka WIP]. I'm just adding this as a disclaimer.
> > >
> > > https://launchpad.net/~till-php/+archive/couchdb<https://launchpad.net/%7Etill-php/+archive/couchdb>
> > >
> > > Would you mind testing my builds? :) So far, I only tested lucid
> briefly (and ran into the xulrunner issue, which I think I have auto-fixed
> now). Besides I just started it up, created a DB and entered some docs into
> it.
> > >
> > > (Also, @Jan:)
> > >
> > > I'm trying to figure out how to setup more automated testing. "make
> check" always requires the source tree to be present, I'd like "make check"
> against my installed binaries. I saw the "verify installation" in Futon –
> something like that for the command line so I can iterate on these builds
> and trigger a "test this" in a continuous integration setup. Building is
> part of it, but since building a binary and installing it are two separate
> steps I want to ensure that the second step also works. I am still trying
> to wrap my head around a setup where I can maybe knife up a few instances
> in THE CLOUD, install my package, run its test-suite and confirm.
> > >
> > > Till
> > >
> > > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> > >
> > > > Hi,
> > > >
> > > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and
> running.
> > > > Unfortunately, I've never built a deb package, so, I cannot provide
> such a
> > > > package. Nevertheless, if you have any problem in building it, just
> let me
> > > > know and I will try to help.
> > > >
> > > > About the mailing list, I suppose adding the CouchDB users (to get
> an idea
> > > > which is the desired Ubuntu distro) and/or Debian (you may get
> support in
> > > > testing and debugging) lists wouldn't be such a bad idea, but it's
> your
> > > > call here.
> > > >
> > > > CGS
> > > >
> > > >
> > > >
> > > >
> > > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > > >
> > > > > Hey,
> > > > >
> > > > > I've been scratching my own itch and started building 1.2.0 for a
> couple
> > > > > Ubuntu distributions.
> > > > >
> > > > > It's a WIP but I was wondering the following:
> > > > >
> > > > > 1) It builds – but does it work? Is the best bet to run the test
> suite in
> > > > > futon, or is there something I could run on the command line when
> the
> > > > > package is installed? I'd prefer the command line to include it in
> some
> > > > > sort of continuous testing without a browser.
> > > > >
> > > > > 2) Who'd have some interest in testing this?
> > > > >
> > > > > 3) Which distributions are wanted – I started with karmic and
> lucid and
> > > > > had planned to build all the way up to 12.10.
> > > > >
> > > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > > >
> > > > > Till
> > >
> >
> >
> > Attachments:
> > - couchdb_etap.tgz
> >
>
>
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
Hey,
thanks, I'm gonna test this shortly. Do you mind if I push it one of my repo?
Till
On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
> Hi,
>
> I isolated the tests which are started with make check and make them run over the default installation under Ubuntu 12.10. Please, let me know if it is what you need (there is a README file in the archive).
>
> CGS
>
>
>
>
>
> On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
> > Hey,
> >
> > [ CC'd user@ to get more feedback. ]
> >
> > I made some progress.
> >
> > I have builds for the following more or less ready:
> >
> > * karmic
> > * lucid
> > * maverick
> > * oneiric
> > * natty
> > * precise
> >
> > It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer.
> >
> > https://launchpad.net/~till-php/+archive/couchdb
> >
> > Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it.
> >
> > (Also, @Jan:)
> >
> > I'm trying to figure out how to setup more automated testing. "make check" always requires the source tree to be present, I'd like "make check" against my installed binaries. I saw the "verify installation" in Futon – something like that for the command line so I can iterate on these builds and trigger a "test this" in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm.
> >
> > Till
> >
> > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> >
> > > Hi,
> > >
> > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> > > Unfortunately, I've never built a deb package, so, I cannot provide such a
> > > package. Nevertheless, if you have any problem in building it, just let me
> > > know and I will try to help.
> > >
> > > About the mailing list, I suppose adding the CouchDB users (to get an idea
> > > which is the desired Ubuntu distro) and/or Debian (you may get support in
> > > testing and debugging) lists wouldn't be such a bad idea, but it's your
> > > call here.
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > >
> > > > Hey,
> > > >
> > > > I've been scratching my own itch and started building 1.2.0 for a couple
> > > > Ubuntu distributions.
> > > >
> > > > It's a WIP but I was wondering the following:
> > > >
> > > > 1) It builds – but does it work? Is the best bet to run the test suite in
> > > > futon, or is there something I could run on the command line when the
> > > > package is installed? I'd prefer the command line to include it in some
> > > > sort of continuous testing without a browser.
> > > >
> > > > 2) Who'd have some interest in testing this?
> > > >
> > > > 3) Which distributions are wanted – I started with karmic and lucid and
> > > > had planned to build all the way up to 12.10.
> > > >
> > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > >
> > > > Till
> >
>
>
> Attachments:
> - couchdb_etap.tgz
>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
I agree – I also don't have to maintain this alone.
Once this is working as expected, I wanted to push the build stuff into a repo where more people have access to and we could also created a 'team' on launchpad to have more people contribute to this (or at least be able to).
Till
On Monday, June 11, 2012 at 3:06 PM, Jan Lehnardt wrote:
> A patch and/or a repo somewhere would be nice :)
>
> On Jun 11, 2012, at 09:08 , CGS wrote:
>
> > Hi,
> >
> > I isolated the tests which are started with make check and make them run over the default installation under Ubuntu 12.10. Please, let me know if it is what you need (there is a README file in the archive).
> >
> > CGS
> >
> >
> >
> >
> >
> > On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
> > Hey,
> >
> > [ CC'd user@ to get more feedback. ]
> >
> > I made some progress.
> >
> > I have builds for the following more or less ready:
> >
> > * karmic
> > * lucid
> > * maverick
> > * oneiric
> > * natty
> > * precise
> >
> > It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer.
> >
> > https://launchpad.net/~till-php/+archive/couchdb
> >
> > Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it.
> >
> > (Also, @Jan:)
> >
> > I'm trying to figure out how to setup more automated testing. "make check" always requires the source tree to be present, I'd like "make check" against my installed binaries. I saw the "verify installation" in Futon – something like that for the command line so I can iterate on these builds and trigger a "test this" in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm.
> >
> > Till
> >
> > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> >
> > > Hi,
> > >
> > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> > > Unfortunately, I've never built a deb package, so, I cannot provide such a
> > > package. Nevertheless, if you have any problem in building it, just let me
> > > know and I will try to help.
> > >
> > > About the mailing list, I suppose adding the CouchDB users (to get an idea
> > > which is the desired Ubuntu distro) and/or Debian (you may get support in
> > > testing and debugging) lists wouldn't be such a bad idea, but it's your
> > > call here.
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
> > >
> > > > Hey,
> > > >
> > > > I've been scratching my own itch and started building 1.2.0 for a couple
> > > > Ubuntu distributions.
> > > >
> > > > It's a WIP but I was wondering the following:
> > > >
> > > > 1) It builds – but does it work? Is the best bet to run the test suite in
> > > > futon, or is there something I could run on the command line when the
> > > > package is installed? I'd prefer the command line to include it in some
> > > > sort of continuous testing without a browser.
> > > >
> > > > 2) Who'd have some interest in testing this?
> > > >
> > > > 3) Which distributions are wanted – I started with karmic and lucid and
> > > > had planned to build all the way up to 12.10.
> > > >
> > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > >
> > > > Till
> >
> >
> > <couchdb_etap.tgz>
Re: CouchDB packaging for Ubuntu
Posted by Jan Lehnardt <ja...@apache.org>.
A patch and/or a repo somewhere would be nice :)
On Jun 11, 2012, at 09:08 , CGS wrote:
> Hi,
>
> I isolated the tests which are started with make check and make them run over the default installation under Ubuntu 12.10. Please, let me know if it is what you need (there is a README file in the archive).
>
> CGS
>
>
>
>
>
> On Sun, Jun 10, 2012 at 8:46 PM, till <kl...@gmail.com> wrote:
> Hey,
>
> [ CC'd user@ to get more feedback. ]
>
> I made some progress.
>
> I have builds for the following more or less ready:
>
> * karmic
> * lucid
> * maverick
> * oneiric
> * natty
> * precise
>
> It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer.
>
> https://launchpad.net/~till-php/+archive/couchdb
>
> Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it.
>
> (Also, @Jan:)
>
> I'm trying to figure out how to setup more automated testing. "make check" always requires the source tree to be present, I'd like "make check" against my installed binaries. I saw the "verify installation" in Futon – something like that for the command line so I can iterate on these builds and trigger a "test this" in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm.
>
> Till
>
> On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
>
> > Hi,
> >
> > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> > Unfortunately, I've never built a deb package, so, I cannot provide such a
> > package. Nevertheless, if you have any problem in building it, just let me
> > know and I will try to help.
> >
> > About the mailing list, I suppose adding the CouchDB users (to get an idea
> > which is the desired Ubuntu distro) and/or Debian (you may get support in
> > testing and debugging) lists wouldn't be such a bad idea, but it's your
> > call here.
> >
> > CGS
> >
> >
> >
> >
> > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
> >
> > > Hey,
> > >
> > > I've been scratching my own itch and started building 1.2.0 for a couple
> > > Ubuntu distributions.
> > >
> > > It's a WIP but I was wondering the following:
> > >
> > > 1) It builds – but does it work? Is the best bet to run the test suite in
> > > futon, or is there something I could run on the command line when the
> > > package is installed? I'd prefer the command line to include it in some
> > > sort of continuous testing without a browser.
> > >
> > > 2) Who'd have some interest in testing this?
> > >
> > > 3) Which distributions are wanted – I started with karmic and lucid and
> > > had planned to build all the way up to 12.10.
> > >
> > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > >
> > > Till
>
>
> <couchdb_etap.tgz>
Re: CouchDB packaging for Ubuntu
Posted by Jan Lehnardt <ja...@apache.org>.
A patch and/or a repo somewhere would be nice :)
On Jun 11, 2012, at 09:08 , CGS wrote:
> Hi,
>
> I isolated the tests which are started with make check and make them run over the default installation under Ubuntu 12.10. Please, let me know if it is what you need (there is a README file in the archive).
>
> CGS
>
>
>
>
>
> On Sun, Jun 10, 2012 at 8:46 PM, till <kl...@gmail.com> wrote:
> Hey,
>
> [ CC'd user@ to get more feedback. ]
>
> I made some progress.
>
> I have builds for the following more or less ready:
>
> * karmic
> * lucid
> * maverick
> * oneiric
> * natty
> * precise
>
> It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer.
>
> https://launchpad.net/~till-php/+archive/couchdb
>
> Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it.
>
> (Also, @Jan:)
>
> I'm trying to figure out how to setup more automated testing. "make check" always requires the source tree to be present, I'd like "make check" against my installed binaries. I saw the "verify installation" in Futon – something like that for the command line so I can iterate on these builds and trigger a "test this" in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm.
>
> Till
>
> On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
>
> > Hi,
> >
> > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> > Unfortunately, I've never built a deb package, so, I cannot provide such a
> > package. Nevertheless, if you have any problem in building it, just let me
> > know and I will try to help.
> >
> > About the mailing list, I suppose adding the CouchDB users (to get an idea
> > which is the desired Ubuntu distro) and/or Debian (you may get support in
> > testing and debugging) lists wouldn't be such a bad idea, but it's your
> > call here.
> >
> > CGS
> >
> >
> >
> >
> > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
> >
> > > Hey,
> > >
> > > I've been scratching my own itch and started building 1.2.0 for a couple
> > > Ubuntu distributions.
> > >
> > > It's a WIP but I was wondering the following:
> > >
> > > 1) It builds – but does it work? Is the best bet to run the test suite in
> > > futon, or is there something I could run on the command line when the
> > > package is installed? I'd prefer the command line to include it in some
> > > sort of continuous testing without a browser.
> > >
> > > 2) Who'd have some interest in testing this?
> > >
> > > 3) Which distributions are wanted – I started with karmic and lucid and
> > > had planned to build all the way up to 12.10.
> > >
> > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > >
> > > Till
>
>
> <couchdb_etap.tgz>
Re: CouchDB packaging for Ubuntu
Posted by till <kl...@gmail.com>.
Hey,
thanks, I'm gonna test this shortly. Do you mind if I push it one of my repo?
Till
On Monday, June 11, 2012 at 9:08 AM, CGS wrote:
> Hi,
>
> I isolated the tests which are started with make check and make them run over the default installation under Ubuntu 12.10. Please, let me know if it is what you need (there is a README file in the archive).
>
> CGS
>
>
>
>
>
> On Sun, Jun 10, 2012 at 8:46 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
> > Hey,
> >
> > [ CC'd user@ to get more feedback. ]
> >
> > I made some progress.
> >
> > I have builds for the following more or less ready:
> >
> > * karmic
> > * lucid
> > * maverick
> > * oneiric
> > * natty
> > * precise
> >
> > It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer.
> >
> > https://launchpad.net/~till-php/+archive/couchdb
> >
> > Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it.
> >
> > (Also, @Jan:)
> >
> > I'm trying to figure out how to setup more automated testing. "make check" always requires the source tree to be present, I'd like "make check" against my installed binaries. I saw the "verify installation" in Futon – something like that for the command line so I can iterate on these builds and trigger a "test this" in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm.
> >
> > Till
> >
> > On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
> >
> > > Hi,
> > >
> > > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> > > Unfortunately, I've never built a deb package, so, I cannot provide such a
> > > package. Nevertheless, if you have any problem in building it, just let me
> > > know and I will try to help.
> > >
> > > About the mailing list, I suppose adding the CouchDB users (to get an idea
> > > which is the desired Ubuntu distro) and/or Debian (you may get support in
> > > testing and debugging) lists wouldn't be such a bad idea, but it's your
> > > call here.
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com) (mailto:klimpong@gmail.com)> wrote:
> > >
> > > > Hey,
> > > >
> > > > I've been scratching my own itch and started building 1.2.0 for a couple
> > > > Ubuntu distributions.
> > > >
> > > > It's a WIP but I was wondering the following:
> > > >
> > > > 1) It builds – but does it work? Is the best bet to run the test suite in
> > > > futon, or is there something I could run on the command line when the
> > > > package is installed? I'd prefer the command line to include it in some
> > > > sort of continuous testing without a browser.
> > > >
> > > > 2) Who'd have some interest in testing this?
> > > >
> > > > 3) Which distributions are wanted – I started with karmic and lucid and
> > > > had planned to build all the way up to 12.10.
> > > >
> > > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > > >
> > > > Till
> >
>
>
> Attachments:
> - couchdb_etap.tgz
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Hi,
I isolated the tests which are started with make check and make them run
over the default installation under Ubuntu 12.10. Please, let me know if it
is what you need (there is a README file in the archive).
CGS
On Sun, Jun 10, 2012 at 8:46 PM, till <kl...@gmail.com> wrote:
> Hey,
>
> [ CC'd user@ to get more feedback. ]
>
> I made some progress.
>
> I have builds for the following more or less ready:
>
> * karmic
> * lucid
> * maverick
> * oneiric
> * natty
> * precise
>
> It's building and I am trying to refine the process a bit. So it might
> break in between [aka WIP]. I'm just adding this as a disclaimer.
>
> https://launchpad.net/~till-php/+archive/couchdb
>
> Would you mind testing my builds? :) So far, I only tested lucid briefly
> (and ran into the xulrunner issue, which I think I have auto-fixed now).
> Besides I just started it up, created a DB and entered some docs into it.
>
> (Also, @Jan:)
>
> I'm trying to figure out how to setup more automated testing. "make check"
> always requires the source tree to be present, I'd like "make check"
> against my installed binaries. I saw the "verify installation" in Futon –
> something like that for the command line so I can iterate on these builds
> and trigger a "test this" in a continuous integration setup. Building is
> part of it, but since building a binary and installing it are two separate
> steps I want to ensure that the second step also works. I am still trying
> to wrap my head around a setup where I can maybe knife up a few instances
> in THE CLOUD, install my package, run its test-suite and confirm.
>
> Till
>
> On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
>
> > Hi,
> >
> > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> > Unfortunately, I've never built a deb package, so, I cannot provide such
> a
> > package. Nevertheless, if you have any problem in building it, just let
> me
> > know and I will try to help.
> >
> > About the mailing list, I suppose adding the CouchDB users (to get an
> idea
> > which is the desired Ubuntu distro) and/or Debian (you may get support in
> > testing and debugging) lists wouldn't be such a bad idea, but it's your
> > call here.
> >
> > CGS
> >
> >
> >
> >
> > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> >
> > > Hey,
> > >
> > > I've been scratching my own itch and started building 1.2.0 for a
> couple
> > > Ubuntu distributions.
> > >
> > > It's a WIP but I was wondering the following:
> > >
> > > 1) It builds – but does it work? Is the best bet to run the test suite
> in
> > > futon, or is there something I could run on the command line when the
> > > package is installed? I'd prefer the command line to include it in some
> > > sort of continuous testing without a browser.
> > >
> > > 2) Who'd have some interest in testing this?
> > >
> > > 3) Which distributions are wanted – I started with karmic and lucid and
> > > had planned to build all the way up to 12.10.
> > >
> > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > >
> > > Till
>
>
Re: CouchDB packaging for Ubuntu
Posted by CGS <cg...@gmail.com>.
Hi,
I isolated the tests which are started with make check and make them run
over the default installation under Ubuntu 12.10. Please, let me know if it
is what you need (there is a README file in the archive).
CGS
On Sun, Jun 10, 2012 at 8:46 PM, till <kl...@gmail.com> wrote:
> Hey,
>
> [ CC'd user@ to get more feedback. ]
>
> I made some progress.
>
> I have builds for the following more or less ready:
>
> * karmic
> * lucid
> * maverick
> * oneiric
> * natty
> * precise
>
> It's building and I am trying to refine the process a bit. So it might
> break in between [aka WIP]. I'm just adding this as a disclaimer.
>
> https://launchpad.net/~till-php/+archive/couchdb
>
> Would you mind testing my builds? :) So far, I only tested lucid briefly
> (and ran into the xulrunner issue, which I think I have auto-fixed now).
> Besides I just started it up, created a DB and entered some docs into it.
>
> (Also, @Jan:)
>
> I'm trying to figure out how to setup more automated testing. "make check"
> always requires the source tree to be present, I'd like "make check"
> against my installed binaries. I saw the "verify installation" in Futon –
> something like that for the command line so I can iterate on these builds
> and trigger a "test this" in a continuous integration setup. Building is
> part of it, but since building a binary and installing it are two separate
> steps I want to ensure that the second step also works. I am still trying
> to wrap my head around a setup where I can maybe knife up a few instances
> in THE CLOUD, install my package, run its test-suite and confirm.
>
> Till
>
> On Saturday, June 9, 2012 at 11:13 PM, CGS wrote:
>
> > Hi,
> >
> > I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running.
> > Unfortunately, I've never built a deb package, so, I cannot provide such
> a
> > package. Nevertheless, if you have any problem in building it, just let
> me
> > know and I will try to help.
> >
> > About the mailing list, I suppose adding the CouchDB users (to get an
> idea
> > which is the desired Ubuntu distro) and/or Debian (you may get support in
> > testing and debugging) lists wouldn't be such a bad idea, but it's your
> > call here.
> >
> > CGS
> >
> >
> >
> >
> > On Sat, Jun 9, 2012 at 9:15 PM, till <klimpong@gmail.com (mailto:
> klimpong@gmail.com)> wrote:
> >
> > > Hey,
> > >
> > > I've been scratching my own itch and started building 1.2.0 for a
> couple
> > > Ubuntu distributions.
> > >
> > > It's a WIP but I was wondering the following:
> > >
> > > 1) It builds – but does it work? Is the best bet to run the test suite
> in
> > > futon, or is there something I could run on the command line when the
> > > package is installed? I'd prefer the command line to include it in some
> > > sort of continuous testing without a browser.
> > >
> > > 2) Who'd have some interest in testing this?
> > >
> > > 3) Which distributions are wanted – I started with karmic and lucid and
> > > had planned to build all the way up to 12.10.
> > >
> > > 4) Is there a mailing list to discuss this, or is dev@ fine?
> > >
> > > Till
>
>