From: Eric Wong <email@example.com> To: Hleb Valoshka <firstname.lastname@example.org> Cc: debian-ruby <email@example.com>, Pirate Praveen <firstname.lastname@example.org>, email@example.com Subject: Re: trying to update unicorn to 5.1, build failure: VERSION= must be specified Date: Fri, 28 Oct 2016 00:23:15 +0000 Message-ID: <20161028002315.GA15205@starla> (raw) In-Reply-To: <CAAB-Kcnwzc8Tcszv3FCPkyJRKRCsHRH6k_qBhKfBpSODxqKy5g@mail.gmail.com> Hleb Valoshka <firstname.lastname@example.org> wrote: > On 9/19/16, Pirate Praveen <email@example.com> 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: firstname.lastname@example.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 manpages.
next parent reply index Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> [not found] ` <CAAB-Kcnwzc8Tcszv3FCPkyJRKRCsHRH6k_qBhKfBpSODxqKy5g@mail.gmail.com> 2016-10-28 0:23 ` Eric Wong [this message] 2016-11-03 15:46 ` Pirate Praveen 2017-03-23 23:34 ` [PATCH] gemspec: remove olddoc from build dependency Eric Wong
Reply instructions: You may reply publically 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: https://bogomips.org/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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help Archives are clonable: git clone --mirror https://bogomips.org/unicorn-public git clone --mirror http://ou63pmih66umazou.onion/unicorn-public Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.unicorn note: .onion URLs require Tor: https://www.torproject.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox