unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Hleb Valoshka <375gnu@gmail.com>
Cc: debian-ruby <debian-ruby@lists.debian.org>,
	Pirate Praveen <praveen@onenetbeyond.org>,
Subject: Re: trying to update unicorn to 5.1, build failure: VERSION= must be specified
Date: Fri, 28 Oct 2016 00:23:15 +0000	[thread overview]
Message-ID: <20161028002315.GA15205@starla> (raw)
In-Reply-To: <CAAB-Kcnwzc8Tcszv3FCPkyJRKRCsHRH6k_qBhKfBpSODxqKy5g@mail.gmail.com>

Hleb Valoshka <375gnu@gmail.com> wrote:
> On 9/19/16, Pirate Praveen <praveen@onenetbeyond.org> wrote:
> > Its pushed to alioth. Can someone check?
> >
> > Error below:
> >
> > $ clean
> > dh clean --buildsystem=ruby --with ruby,systemd
> >    dh_testdir -O--buildsystem=ruby
> >    dh_auto_clean -O--buildsystem=ruby
> > 	dh_ruby --clean
> >    dh_ruby --clean
> > VERSION= must be specified
> > dh_auto_clean: dh_ruby --clean returned exit code 1
> > debian/rules:6: recipe for target 'clean' failed
> > make: *** [clean] Error 1
> This is not the only problem, then you should have olddoc gem, I
> remember that I tried to fix these error, but I don't see my changes,
> maybe I did this on my home pc, I'll look there.

(oops, missed this earlier)

I understand olddoc may not be worth the effort to package in
Debian.  (I already tried to reduce dependencies in olddoc
compared to wrongdoc, but a package is a package...)

Anyways, I suggest you guys grab the generated gemspec from the
Rubygem or tar.gz.  You already seem to be doing that with NEWS
and the manpages to avoid a build-dep on pandoc(*).

Maybe the gemspec in git could have olddoc become optional, too,
while still remaining DRY.  The email address for the public
mailing list is already specified in multiple places, so maybe
over-DRY-ing isn't worth it...

Anyways, feel free to email me + Cc: unicorn-public@bogomips.org
w.r.t. any packaging/integration issues for any Free Software
systems (not just Debian)

(*) - I'll be switching over to perlpod at some point and
      pod2man is standard in Debian.  I hate having to spend
      ~30MB of bandwidth fees to get ghc + pandoc to build

       reply	other threads:[~2016-10-28  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f1d5eacb-b6a2-be96-34aa-fe061a194a62@onenetbeyond.org>
     [not found] ` <CAAB-Kcnwzc8Tcszv3FCPkyJRKRCsHRH6k_qBhKfBpSODxqKy5g@mail.gmail.com>
2016-10-28  0:23   ` Eric Wong [this message]
2016-11-03 15:46     ` trying to update unicorn to 5.1, build failure: VERSION= must be specified Pirate Praveen
2017-03-23 23:34       ` [PATCH] gemspec: remove olddoc from build dependency Eric Wong

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:

  List information: https://yhbt.net/unicorn/

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

  git send-email \
    --in-reply-to=20161028002315.GA15205@starla \
    --to=e@80x24.org \
    --cc=375gnu@gmail.com \
    --cc=debian-ruby@lists.debian.org \
    --cc=praveen@onenetbeyond.org \
    --cc=unicorn-public@bogomips.org \


* 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


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).