user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: meta@public-inbox.org
Subject: Re: getting started with local public-inbox - INSTALL
Date: Wed, 9 Jan 2019 23:15:36 +0000	[thread overview]
Message-ID: <20190109231536.i3ik3fqb7zdk6zgb@dcvr> (raw)
In-Reply-To: <1538164205.14416.76.camel@sipsolutions.net>

Johannes Berg <johannes@sipsolutions.net> wrote:
> Hi,
> 
> Sorry to interrupt ... Could somebody more knowledgeable with the code
> perhaps check and update the INSTALL file?

Hey, sorry for the not getting back to you.  Was busy and hoping
somebody else with more RPM experience would pipe up.

I work almost exclusively Debian nowadays and have been working
on just getting oldstable well-supported.  I just found
"supermin" and will learn to use it for Fedora...

> I've found that my install was always erroring out with the *strangest*
> errors, but now that I installed *all* the dependencies, not just the
> ones that seemed essential, things are working better.
> 
> So for example, I hadn't installed these:
> 
> perl-Plack     

Not optional at the moment.  Maybe it can be...

> perl-Plack-Test
> perl-Danga-Socket                 
> perl-Filesys-Notify-Simple        
> perl-Net-Server                   
> perl-PerlIO-gzip                  
> perl-Plack-Middleware-Deflater    
> perl-Plack-Middleware-ReverseProxy
> perl-Socket6                      
> 
> because they all sounded pretty optional in the INSTALL documentation,
> however, not doing so seems to have broken even "public-inbox-index"?

Hmm.. they should all be optional.

-index requires Xapian and SQLite dependencies right now.
Xapian can become optional in the future (right now, it can be
neutered using -init with "--indexlevel=basic" (sorry about the
lack of docs, ENOTIME)

> Additionally, FYI, on my system some tests fail - some due to git output
> differences:
> t/convert-compact.t .... 1/? public-inbox-compact /tmp/convert-compact-WOin0W/v1 failed: 512
> # Tests were run but no plan was declared and done_testing() was not seen.
> # Looks like your test exited with 2 just after 21.
> t/convert-compact.t .... Dubious, test returned 2 (wstat 512, 0x200)

Probably missing xapian-compact(1) from xapian-tools.  There
needs to be a better error...

> t/search.t ............. 1/? 
> #   Failed test 'got both matches'
> #   at t/search.t line 256.
> #          got: '0'
> #     expected: '2'
> 
> #   Failed test 'got a match for quoted text'
> #   at t/search.t line 261.
> #          got: '0'
> #     expected: '1'
> # Looks like you failed 2 tests of 111.
> t/search.t ............. Dubious, test returned 2 (wstat 512, 0x200)

> t/v2reindex.t .......... 103/? # Looks like you failed 1 test of 108.
> t/v2reindex.t .......... Dubious, test returned 1 (wstat 256, 0x100)

Not sure, probably missing Xapian entirely?

> Failed 1/108 subtests 
> t/v2writable.t ......... 1/? 
> #   Failed test 'commit message propagated to git'
> #   at t/v2writable.t line 230.
> #                   '28620ab0c87d9cd57067c9e0d8767de529aaf8e5 (HEAD -> master) test removal
> # '
> #     doesn't match '(?^s:\A[a-f0-9]+ test removal\n\z)'
> 
> #   Failed test 'only one commit written to git'
> #   at t/v2writable.t line 232.
> #     Structures begin differing at:
> #          $got->[0] = '9e621d1a25f5d7d1aa04153f1e22a1af0005a257 this is a subject
> #     '
> #     $expected->[0] = '9e621d1a25f5d7d1aa04153f1e22a1af0005a257 (HEAD -> master) this is a subject
> #     '
> t/v2writable.t ......... 101/? # Looks like you failed 2 tests of 111.
> t/v2writable.t ......... Dubious, test returned 2 (wstat 512, 0x200)

Patch coming to drop decorate.

> This is with git 2.14.4.

OK.  I noticed I broke git < 2.6.0 for V2, so I'll have to fix
that, too :x

> (Please CC me, I'm not subscribed here right now)

Yup, that's the default assumption :)

      reply	other threads:[~2019-01-09 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 19:50 getting started with local public-inbox - INSTALL Johannes Berg
2019-01-09 23:15 ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190109231536.i3ik3fqb7zdk6zgb@dcvr \
    --to=e@80x24.org \
    --cc=johannes@sipsolutions.net \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).