Re: RC bugs against your packages
Hi, On 2/8/20, Utkarsh Gupta wrote: > Otherwise, I propose to file an RM bug against them all very shortly (~2 > weeks). Feel free. I don't work with Chef for a long time, so I'm unable to properly maintain them. > If anyone else is willing to work on it, please let me know :) Chef community prefer to use bundler or even big deb package with everything required like ruby, gems and so on. I doubt that packaged berkshelf ever had real users.
Re: RFS: unicorn-4.5.1-2
I meant 5.4.1-2 :) On 1/13/19, Hleb Valoshka <375...@gmail.com> wrote: > Hi team! > > Please upload unicorn-4.5.1-2 (Closes: #918916) > > Thanks in advance. >
RFS: unicorn-4.5.1-2
Hi team! Please upload unicorn-4.5.1-2 (Closes: #918916) Thanks in advance.
Re: Error while building ruby-em-websocket
On 7/31/18, Manas Kashyap wrote: > yes , i packaged it , and yet to be uploaded , u can check it in > https://salsa.debian.org/ruby-team/ruby-em-websocket-client . So you packaged its old version which doesn't support 2nd argument to .connect method while ruby-em-websocket needs an updated version. PS: please don't top quote and don't reply personally
Re: Error while building ruby-em-websocket
On 7/31/18, Manas Kashyap wrote: > I am trying to package ruby-em-websocket. > I am getting an error while doing so (i do packaging work in a Debian Sid > container), can anyone help me out in resolving this error > > error :- http://paste.debian.net/1035969/ Do we have em-websocket-client packaged?
RFS: ruby-mixlib-config
Hi team! I've prepared a new version of ruby-mixlib-config, please upload it. Thanks in advance.
Re: ruby-gettext-setup: FTBFS
On 4/5/18, Georg Faerber wrote: >> /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb is UTF-8 file, Oops, wrong file. spec/lib/gettext-setup/gettext_setup_spec.rb is a proper one. > Please go ahead and feel free to fix the package; I failed to do so > yesterday, but I've to admit, I didn't spent much time. Also, my local > setup is currently broken. Please see attached file. It fixes the failure. diff -uNr gettext-setup-0.30.orig/spec/lib/gettext-setup/gettext_setup_spec.rb gettext-setup-0.30.new/spec/lib/gettext-setup/gettext_setup_spec.rb --- gettext-setup-0.30.orig/spec/lib/gettext-setup/gettext_setup_spec.rb 2018-02-21 05:04:10.0 +0300 +++ gettext-setup-0.30.new/spec/lib/gettext-setup/gettext_setup_spec.rb 2018-04-11 10:19:09.407049739 +0300 @@ -1,3 +1,4 @@ +# encoding: utf-8 require 'rspec/expectations' require 'spec_helper'
Re: ruby-gettext-setup: FTBFS [Re: RFS: ruby-tzinfo, ruby-gettext, ruby-kgio, ruby-solve]
On 4/4/18, Georg Faerber wrote: >> I've checked ruby-gettext-setup and can say that it doesn't actually >> use anything from gettext gem, only from fast-gettext. So its test >> failures caused by something else, not the new gettext version. > I would be interested in how you came to this conclusion: I did `fgrep -R require | fgrep gettext` and saw nothing (actually this gem uses rxgettext from ruby-gettext). > ruby-gettext-setup FTBFS now, with errors like > > /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in `gsub': invalid > byte sequence in US-ASCII (ArgumentError) > > See #894829 for details. > /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb is UTF-8 file, it contains japanese letters (こんにちは世界), of course these letters can't be processed in C locale. So you either patch it to remove UTF-8 characters or run tests in C.UTF-8. I don't think that the last ruby-gettext update introduced a regression as in the previous version it had a terrible insecure parser for ruby strings: begin; s = eval(s); rescue Exception; end Now it has a proper one.
Re: RFS: ruby-celulloid 0.16.0-5, fix for #892192
On 3/24/18, Cédric Boutillier wrote: > Uploaded. I added Testsuite: autopkgtests-pkg-ruby and a patch to create > the log used in specs in a temporary directory to fix autopkgtests. Thanks! I hope Buster won't have this package as it has fewer and fewer rev deps :)
RFS: ruby-celulloid 0.16.0-5, fix for #892192
Hi team! I've prepared updated ruby-celulloid 0.16.0-5 with fix for #892192 and usual updates like vcs-*, dh level etc. Please review and upload. Branch is debian/sid not master.
Re: RFS: ruby-tzinfo, ruby-gettext, ruby-kgio, ruby-solve
On 3/22/18, Cédric Boutillier wrote: > I would rather see this minimal patch to disallow gecode engine in > ruby-solve, and a Breaks: berkshelf (<= current version) > instead of the Conflicts: ruby-dep-selector. > I think it would ease a lot upgrade path if we just prevent ruby-solve > from using ruby-dep-selector instead of preventing coinstalling them. I've implemented your suggestion.
Re: RFS: ruby-tzinfo, ruby-gettext, ruby-kgio, ruby-solve
On 3/21/18, Cédric Boutillier wrote: > Is it "normal" that ruby-gettext-setup tests fail with the new > ruby-gettext? They seem to pass with the current version on > ci.debian.net. I've checked ruby-gettext-setup and can say that it doesn't actually use anything from gettext gem, only from fast-gettext. So its test failures caused by something else, not the new gettext version. > For ruby-solve, I couldn't run the tests for berkshelf with the new > ruby-solve in autopkgtest, because it would complain about unsatisfiable > dependencies. Berkshelf by default it uses gecode solver (so it needs to be patched). And Conflicts header in ruby-solve will prevent its upgrade if Berkshelf is installed, because the latter has Depends: ruby-dep-selector. > I was wondering if instead of conflicting with ruby-dep-selector, it was > possible to deactivate this engine in ruby-solve, just by forbidding the > use of :gecode key in solver_for_engine method in lib/solve.rb. I thought about this, maybe patching solve is a better idea, but see above. The only solve user is berkshelf so it seems better to patch it instead.
Re: RFS: ruby-tzinfo, ruby-gettext, ruby-kgio, ruby-solve
On 3/20/18, Cédric Boutillier wrote: > Could you please update the Standards-Version field and the debhelper > compatibility for these packages, as well as switching the debian/watch > to https? Done. I usually don't change them if lintian doesn't say to. > Can you clarify the situation of ruby-solve with respect to > ruby-dep-selector? The presence of ruby-dep-selector in itself is really > problematic for ruby-solve? Or is it just because ruby-dep-selector is > broken? I understand that it is the latter. > If it is indeed the case, is it not possible to upload an updated, non > broken > ruby-dep-selector before ruby-solve to avoid the extra Conflict: statement? Dep-selector is a one of two available solve backends. Unlike Molinillo based one it's optional. It's currently broken in Sid as it needs libgecode v4 while in Sid we have v5, so there is no lib.so for ruby 2.5. Therefore I just want to prevent broken package installation. I don't think that I can upload fixed dep-selector in reasonable time as it requires good knowledge of both libgecode and C++. My previous attempts to port it failed.
orphaned and to be removed packages
Hi team! A few years ago I've prepared several packages required to run berkshelf-api, a build dependency for berkshelf. Now berkshelf-api is deprecated, so I'm going to request its removal from Debian. As a preparation for this step I removed myself from uploaders from certain packages: * ruby-fuubar * ruby-grape * ruby-grape-entity * ruby-progressbar * ruby-rack-mount Those packages have other uploaders. But the following once don't: * ruby-gssapi (ruby-net-ssh-krb) * ruby-little-plugger (ruby-logging) * ruby-logging (ruby-googleauth, ruby-logging-rail) * ruby-websocket-extensions (ruby-websocket-driver -> obs-api, ruby-poltergeist) In parenthesis their reverse dependencies are. Please adopt these 4 packages. These 2 packages don't have reverse dependencies. But I have no decision whether to request their removal yet. * ruby-grape-msgpack * ruby-websocket-parser I will send request removal for the following packages: * ruby-nori * ruby-gyoku * reel * ruby-berkshelf-api-client * berkshelf-api They are not used anymore either deprecated or have dead upstream.
RFS: ruby-tzinfo, ruby-gettext, ruby-kgio, ruby-solve
Hi team! I've prepared new version for the following packages: * just a new minor version + vcs-* updated: - ruby-tzinfo - ruby-gettext - ruby-kgio * a new major version + d/control changes to prevent broken ruby-dep-selector installation - ruby-solve Please review and upload them. Thanks in advance!
Re: RFS: ruby-molinillo 0.6.4-1
On 3/14/18, Antonio Terceiro wrote: > This new version breaks the current version of bundler, I would expect > that to be specified in debian/control. Fixed.
RFS: ruby-buff-config 2.0.0-2
Hi team, Please review and upload ruby-buff-config 2.0.0-2 Thanks in advance!
RFS: ruby-molinillo 0.6.4-1
Hi team, I've prepared a new release of ruby-molinillo, required for bundler 0.16 and ruby-solve 4.0. Please review and upload. Thanks in advance.
Re: Renaming ruby-factory-girl to ruby-factory-bot
On 2/26/18, Georg Faerber wrote: > Could you / someone else continue with the review, or, in case > everything is fine, upload the package? Looks good for me, but I don't have upload privileges :)
RFS: ruby-ridley 5.1.1
Hi team, I've prepared ruby-ridley 5.1.1, please review and upload.
ruby-molinillo
Hi team, For ruby-solve update I need ruby-molinillo ~> 0.6, besides ruby-solve the only its reverse dependency is ruby-bundler. Current bundler version in sid (1.15.1) depends on 0.5 but prepared in git 0.16.1 needs 0.6. So I have 2 questions: 1. Any objections to upload ruby-molinillo 0.6.4? 2. Any volunteers to be its maintainers as currently it has nobody (I can be of course) I have pushed it to salsa.
Re: Uploading gitlab 9.5 to unstable
Hi Praveen! On 2/20/18, Pirate Praveen wrote: > Hleb, > Can you confirm if berkshelf-api is compatible with grape 0.19.2? Please ignore berkshelf-api, it's deprecated and should be removed from Debian.
Re: Renaming ruby-factory-girl to ruby-factory-bot
On 2/19/18, Georg Faerber wrote: > I've worked on this now, and would be more than happy, if someone could > review my work [1]. Note: That's not yet ready for upload, before, I d/changelog: Please remove this line as this is not an initial release: * Initial release. d/files, d/ruby-factory-bot.subsvars: Please remove these files as they are automatically generated during a build. d/gemspec: Why did you create it? d/control: For binary ruby-factory-bot: 1) Replace 4.7.0-1~ with ${source:Version} 2) Add Provides: ruby-factory-girl
RFS: a lot off
Hi team, I've prepared new versions for the following packages: * ruby-buff-ignore * ruby-semverse * ruby-tzinfo * ruby-raindrops * ruby-kgio * ruby-gettext Please upload them. Thanks in advance.
Re: RFS: berkshelf for bpo9
On 8/16/17, Antonio Terceiro wrote: > berkshelf must be in testing before being uploaded to backports. It was when I wrote RFS :)
Re: RFS: ruby-buff-config
On 8/14/17, Lucas Kanashiro wrote: > Could you fix these things below? > > * ruby-buff-config source: quilt-patch-missing-description remove-spork > * ruby-buff-config: extended-description-is-probably-too-short Done.
RFS: ruby-buff-config
Hi team, please upload a new version of ruby-buff-config. Thanks in advance.
RFS: ruby-varia-model
Hi team! Please upload new version of ruby-varia-model. It may break ruby-ridley and some other berkshelf related packages, but I'm preparing their updates. Thanks in advance.
RFS: berkshelf for bpo9
Hi team! Please upload berkshelf 4.3.5-2~bpo9+1 to backports. It was not fixed in time during the freeze so I was advised to provide it though backports. Branch stretch-backport in git repo. Thanks in advance.
RFS: berkshelf for bpo9
Hi team! Please upload berkshelf 4.3.5-2~bpo9+1 to backports. It was not fixed in time during the freeze so I was advised to provide it though backports. Branch stretch-backport in git repo. Thanks in advance.
RFS: ruby-varia-model
Hi team! Please upload new version of ruby-varia-model. It may break ruby-ridley and some other berkshelf related packages, but I'm preparing their updates. Thanks in advance.
Re: RFS: ruby-buff-extensions
On 7/27/17, Antonio Terceiro wrote: > these reverse dependencies will fail theirs tests with this update on > the dependency check step (they expect ~> 1.0): > > berkshelf > ruby-buff-config > ruby-varia-model ... > ruby-ridley > > I'm uploading anyway, can you please handle these, or at least > report suitable RC bugs against them? Hi Antonio, I will update all that packages.
RFS: ruby-buff-extensions
Hi team! I've prepared update for ruby-buff-extensions, please review and upload. Despite major version change it doesn't have incompatible changes so shouldn't break anything. Thanks in advance.
RFS: ruby-mixlib-archive with CVE fix
Hi team! I've prepared a fix for CVE-2017-126 (#868572) for Stretch, please review and upload (branch 'stretch'). Thanks in advance.
debdiff
Hi team, Could you advice how to make debdiff properly? When I do "debdiff berkshelf_4.3.5-1.dsc berkshelf_4.3.5-2.dsc" its output contains diff for changelog and lintian-overrides but not for patches/*.
RFS: berkshelf, fixing RC bug
Hi team, please upload berkshelf 4.5.3-2, it has 2 changes: - fix for failure in sbuild - fix new lintian warnings Thanks in advance.
RFS: reel, fix for the serious bug #841704
Hi team, please upload reel 0.6.1-2, it fixes #841704 (as ruby-certificate-authority is packaged then use it and don't provide pregenerated certificates). Thanks in advance.
Re: RFS: ruby-gettext
Please don't upload, I want to fix another issue. On 11/3/16, Hleb Valoshka <375...@gmail.com> wrote: > Hi team! > > Please upload ruby-gettext 3.2.2-2, it fixes #840789 among other changes. >
RFS: ruby-gettext
Hi team! Please upload ruby-gettext 3.2.2-2, it fixes #840789 among other changes.
Re: RFS: berkshelf
On 10/18/16, Cédric Boutillier wrote: > The autopkgtests fail (425 failures) because of permissions to create a > subdirectory (425 times the same error). > > 425) ::log returns Berkshelf::Logger >Failure/Error: FileUtils.mkdir_p(tmp_path) > >Errno::EACCES: > Permission denied @ dir_s_mkdir - /usr/lib/ruby/spec ># ./spec/support/path_helpers.rb:48:in `clean_tmp_path' ># ./spec/spec_helper.rb:47:in `block (2 levels) in ' > > Maybe the tmp_path function in spec/support/path_helpers.rb should > return some fixed subdir of /tmp? I have fixed this issue as well. Could you try to update and build?
Re: RFS: berkshelf
Hi Cédric! On 10/14/16, Cédric Boutillier wrote: > Failing Scenarios: > cucumber features/commands/install.feature:25 # Scenario: installing an > explicit version demand > cucumber features/commands/outdated.feature:55 # Scenario: the > dependency has a version constraint and there are new items that satisfy > it > cucumber features/commands/vendor.feature:85 # Scenario: vendoring > without an explicit path to vendor into > cucumber features/json_formatter.feature:126 # Scenario: JSON output > when running the outdated command It looks like you have not updated repository, because you have the same failures as Christian had, and they all are "fixed" (ignored actually).
Re: RFS: berkshelf
Hi! On 10/13/16, Christian Hofstaedtler wrote: >> I've disabled cucumber tests not working in sbuild. Please upload. > New build log with test failures attached. I managed to setup working sbuild on sid machine and found all failures at last. After several rebuild I have no new failures, please upload updated version.
Re: sbuild question
On 10/13/16, Hleb Valoshka <375...@gmail.com> wrote: >>> I've tried to rebuild berkshelf with sbuild, but the only result is the >>> message: >>> E: Core build dependencies not satisfied; skipping > I've rebuild my chroot using setup script and still have the same > error. What a crazy tool. But on sid sbuild works.
Re: sbuild question
On 10/12/16, Cédric Boutillier wrote: >> I've tried to rebuild berkshelf with sbuild, but the only result is the >> message: >> E: Core build dependencies not satisfied; skipping > or even rebuild one from scratch (using for example the setup script in > the team main repo) I've rebuild my chroot using setup script and still have the same error. What a crazy tool.
Re: RFS: berkshelf
On 10/10/16, Christian Hofstaedtler wrote: > Unfortunately it does not appear to build in sbuild. I'm attaching > the log. I've disabled cucumber tests not working in sbuild. Please upload.
sbuild question
Hi team. I've tried to rebuild berkshelf with sbuild, but the only result is the message: E: Core build dependencies not satisfied; skipping I've set up sbuild according with https://wiki.debian.org/sbuild Could anybody suggest anything? (--verbose and manual installation of all build dependencies to chroot are tried)
Re: RFS: berkshelf
Hi team! Kindly reminding about my request. On 9/27/16, Hleb Valoshka <375...@gmail.com> wrote: > Hi team! > > I've prepared berkshelf (tool to manage chef's cookbooks) for upload. > Please review and upload it if it's in a good shape. > > Thanks in advance. >
RFS: ruby-tzinfo, RC bug fixed
Hi team! Recently tzdata priority was lowered so in build environments its not installed anymore. This causes test failures for packages which depends on ruby-tzinfo. I've prepared a new release ruby-tzinfo, now it depends on tzdata. Please upload. Thanks in advance!
RFS: berkshelf
Hi team! I've prepared berkshelf (tool to manage chef's cookbooks) for upload. Please review and upload it if it's in a good shape. Thanks in advance.
Re: trying to update unicorn to 5.1, build failure: VERSION= must be specified
On 9/19/16, Pirate Praveen 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.
Re: Invalid gemspec in [pathname2.gemspec]: uninitialized constant Gem::Specification::FileList
On 9/19/16, Michael Crusoe wrote: > While updating ruby-pathname2 from 1.7.4 to 1.8.0 I received the > following error: > > dh_ruby --clean > Invalid gemspec in [pathname2.gemspec]: uninitialized constant > Gem::Specification::FileList > Did you mean? FileUtils >FileTest > Invalid gemspec in [pathname2.gemspec.gem2deb]: uninitialized constant > Gem::Specification::FileList > Did you mean? FileUtils >FileTest > > > I'm not a ruby user nor dev, just packaging this on behalf of another > project -- any suggestions? Hi Michael, this looks like upstream bug we unable to fix with patch as dh_ruby --clean will fail, so I just copied a fixed gemspec to debian/ and instructed dh_ruby to use it. My changes are pushed to alioth.
Re: RFS: ruby-aruba (RC bug fixing)
On 9/16/16, Cédric Boutillier wrote: > I activated the autopkgtest (see commit c06a49c), and when I try to run > the autopkgtests, I get one failure: > > > 1) Aruba::Api files #copy when source is existing when destination is > non-existing when source is file when source is contains "~" in path > Failure/Error: FileUtils.mkdir_p File.dirname(local_path) > > Errno::EACCES: >Permission denied @ dir_s_mkdir - /home/boutil > # ./spec/support/shared_contexts/aruba.rb:13:in `block in > create_test_files' > # ./spec/support/shared_contexts/aruba.rb:9:in `each' > # ./spec/support/shared_contexts/aruba.rb:9:in `create_test_files' > # ./spec/aruba/api_spec.rb:538:in `block (7 levels) in (required)>' > > Could you investigate this issue? (maybe just disable this test for > autopkgtest, e.g. by testing the existence of the AUTOPKGTEST_TMP > environment variable) I don't maintain ruby-aruba and so I know nothing about it, I've just found an issue with it while working on berkshelf, then and prepared a patch for it using upstream commit fixing it. And I know nothing about autopkgtest, so currently I'm unable to test whether I fix the failure you found correctly. So maybe it's better to release it without support for autopkgtest and then wait till maintainer fix it?
RFS: berkshelf-api
Hi team! Thanks to PET I've found that our berkshelf-api package is outdated, please upload the version from git. Thanks in advance.
RFS: ruby-aruba (RC bug fixing)
Hi team! Please upload ruby-aruba. It has RC bug fixed.
RFS: ruby-aruba (RC bug fixing)
Hi team! I've prepared NMU for ruby-aruba fixing #836735 (uninitialized constant Aruba::CommandMonitor::Utils). Please upload. Thanks in advance. Hideki Yamane, could you update pristine-tar branch as it's missing the latest orig.tar.gz?
Re: RFS: ruby-gettext, ruby-solve, ruby-mixlib-archive, test-kitchen
On 8/30/16, Antonio Terceiro wrote: > uploaded. I have made 1 commit on top (93fab5c) to bump debhelper > compat level and use https in Vcs-Git. Thank you! > I hope you have plans to push a good part of those patches upstream. ;-) They are very debian-specific, maybe I can drop some of them with --gem-install layout, but I prefer to have data in /usr/share.
Re: RFS: ruby-gettext, ruby-solve, ruby-mixlib-archive, test-kitchen
On 8/28/16, Hleb Valoshka <375...@gmail.com> wrote: >>> * test-kitchen (a new package) >> lib/vendor/hash_recursive_merge.rb is not properly namespaced. it is also >> under >> a different license than the rest of the package; this needs to be >> mentioned in dbeian/copyright >> debian/copyright is missing entries for at least these copyright >> holders:: > ... >> debian/rules has some commented boilerplate. Also, it would be nice to >> enable dependency resolution during the build. I've pushed changes for your notices, please review.
Re: RFS: ruby-gettext, ruby-solve, ruby-mixlib-archive, test-kitchen
On 8/27/16, Antonio Terceiro wrote: > uploaded these three Thanks! >> * test-kitchen (a new package) > > judging by the amount of patches, this seems to be a reasonably problematic > package! :-o > > lib/vendor/hash_recursive_merge.rb is not properly namespaced. it is also > under > a different license than the rest of the package; this needs to be mentioned > in dbeian/copyright One more patch to be done :) > debian/copyright is missing entries for at least these copyright > holders:: ... > lib/kitchen/driver/proxy.rb:5:# Copyright:: Copyright (c) 2013 Opscode, > Inc. Opscode, Inc. is Chef Software, Inc. now. should I use old or new name? > debian/rules has some commented boilerplate. Also, it would be nice to > enable dependency resolution during the build. will do.
Re: RFS: ruby-gettext, ruby-solve, ruby-mixlib-archive, test-kitchen
On 8/15/16, Hleb Valoshka <375...@gmail.com> wrote: > Hi team! > > Kindly reminding that I've pushed the following packages for review and > upload. Reminding again :) > * ruby-gettext (updated to the latest upstream version) > * ruby-solve (like above) > * ruby-mixlib-archive (a new package, dependency for berkshelf ITP) Maybe I should embed this gem to berkshelf as it looks like hack :) > * test-kitchen (a new package) > > Thanks in advance.
Re: RFS: ruby-fast-blank
On 8/17/16, Sruthi wrote: > I packaged the gem because it is listed as one of the dependencies for > Discourse. Why just not to patch Discourse?
Re: RFS: ruby-fast-blank
On 8/17/16, Sruthi Chandran wrote: > Hi,I prepared the packaging of ruby-fast-blank. It is lintian cleanand > I tested it with build-and-upload script from pkg-ruby-extras repo. > > As my membership request to alioth is still pending, I've added my > packageto the following > git-repo:https://git.fosscommunity.in/debian-ruby/ruby-fast-blank > > Please review and upload. I appreciate you intent to contribute to Debian, but do we really need this packaged? For me this gem is too trivial, and other gems which may use it should be patched not to use it. class String; def blank?; self.strip.empty?; end; end Does it worth to have its own gem? I did not patched ruby-buff-* usage in my packages only because ruby-buff-* was already packaged.
RFS: ruby-gettext, ruby-solve, ruby-mixlib-archive, test-kitchen
Hi team! Kindly reminding that I've pushed the following packages for review and upload. * ruby-gettext (updated to the latest upstream version) * ruby-solve (like above) * ruby-mixlib-archive (a new package, dependency for berkshelf ITP) * test-kitchen (a new package) Thanks in advance.
RFS: reel, ruby-gettext, ruby-raindrops, ruby-retryable, ruby-solve
Hi team. I've packages the latest upstream version for the following packages: * reel * ruby-gettext * ruby-raindrops * ruby-retryable * ruby-solve Please review and upload them.
RFS: ruby-mixlib-archive, test-kitchen
Hi team. I've prepared 2 new packages, please review and upload them. * ruby-mixlib-archive - a new package, required for berkshelf package i'm working on. * test-kitchen - a new package as well, the 2nd attempt, now without issues I hope. Thanks in advance.
we don't need ruby-tzinfo-data
Hi Andrew & team. We don't need ruby-tzinfo-data as ruby-tzinfo works perfectly with system tz data without any additional patches.
RFS: ruby-mixlib-install 1.1.0-1
Hi team! I've prepared a new version of ruby-mixlib-install (1.1.0-1), please review and upload it. Thanks in advance.
RFS: ruby-msgpack 1.0.0-1
Hi team. I've prepared a new upstream version of ruby-msgpack, it's required for a new version of ruby-grape-msgpack which is compatible with currently uploaded version of ruby-grape. Please review and upload, thanks in advance.
Re: RFS: ruby-mixlib-versioning, ruby-mixlib-shellout
On 5/13/16, Christian Hofstaedtler wrote: > Done. Thanks. > Note: current Standards-Version is 3.9.8, not 3.9.7. I suppose it was 3.9.7 when I prepared these packages (or my lintian is outdated).
RFS: ruby-mixlib-versioning, ruby-mixlib-shellout
Hi team. Please review and upload: 1. ruby-mixlib-shellout -- update to the latest upstream version 2. ruby-mixlib-versioning -- new package These uploads are required for test-kitchen package I'm working on. Thanks in advance.
Re: ghi: please review (new package, CLI interface to GitHub issue tracker)
On 4/25/16, Dmitry Smirnov wrote: >> 1) upstream is not merged to master > > Intentional. See gbp.conf. Okay, but it's not a layout used by ruby-pkg-extras team afaik. >> 2) as ghi is an application not a library I consider to rename the >> package to just ghi > > Sorry, I don't quite follow you... There are two binary packages: "ruby-ghi" > and "ghi". The latter installs executable binary. "ruby-ghi" is its library > that may or may not be used by others. > You suggest to merge "ruby-ghi" into "ghi", right? If ghi is the only consumer of ruby-ghi then I don't see any reason to introduce a new package. So I suggest to merge.
Re: ghi: please review (new package, CLI interface to GitHub issue tracker)
On 4/25/16, Dmitry Smirnov wrote: > Since I'm not very experienced in packaging Ruby apps may I ask for quick > review of my work please? Package repository can be found here: > >https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-ghi.git 1) upstream is not merged to master 2) as ghi is an application not a library I consider to rename the package to just ghi
RFS: ruby-mixlib-versioning, ruby-mixlib-shellout
Hi team. Please review and upload: 1. ruby-mixlib-shellout -- update to the latest upstream version 2. ruby-mixlib-versioning -- new package These uploads are required for test-kitchen package I'm working on. Thanks in advance.
Re: uploading to jessie-backports (Re: migrating to Debian gitlab)
On 4/10/16, Pirate Praveen wrote: > Here is the sequential list of dependencies > https://gitlab.com/debian-ruby/backportr/blob/master/lib/gitlab_sequential.txt You don't need to backport ruby-tzinfo. Current version in stable has required patch backported (#798348).
RFS: ruby-aruba, ruby-berkshelf-api-client
Hi team! Please upload: - ruby-aruba 0.14.1-2. I've only dropped unneeded ruby-event-bus from dependencies. - ruby-berkshelf-api-client 2.0.2-1. New upstream version and tests are run during build process. Thanks in advance.
RFS: ruby-aruba, ruby-berkshelf-api-client
Hi team! Please upload: - ruby-aruba 0.14.1-2. I've only dropped unneeded ruby-event-bus from dependencies. - ruby-berkshelf-api-client 2.0.2-1. New upstream version and tests are run during build process. Thanks in advance.
Re: RFS: ruby-grape-msgpack, berkshelf-api
On 3/24/16, Christian Hofstaedtler wrote: > Both uploaded. Thanks!
RFS: ruby-grape-msgpack, berkshelf-api
Hi team. Please upload new version of ruby-grape-msgpack. Besides of automated changes made by Cédric it has the following: - checks gem dependencies during a build process - relaxes ruby-grape dependency in gemfile And when it reaches archive then please upload berkshelf-api. It's a new package.
RFS: ruby-ridley
Hi team! Please upload ruby-ridley 4.4.3-2. It has several Depends and Build-Depends fixes. Thanks in advance.
Re: RFS: reel
On 3/18/16, Christian Hofstaedtler wrote: >> Please review and upload reel, a Celluloid::IO based web server. > > reel.git is empty? Git says "Everything up-to-date" https://anonscm.debian.org/cgit/pkg-ruby-extras/reel.git shows all data.
RFS: reel
Hi team! Please review and upload reel, a Celluloid::IO based web server. I need it for berkshelf-api. Thanks in advance.
Re: RFS: ruby-mixlib-install, ruby-berkshelf-api-client
On 3/10/16, Christian Hofstaedtler wrote: >> * ruby-mixlib-install > > Done/Uploaded. Thanks! >> * ruby-berkshelf-api-client > > Has distribution as UNSTABLE in d/changelog. > > For both, please fix the vcs-field-uses-insecure-uri vcs-git lintian Fixed. > hint. I /think/ the current gem2deb gets it right, but not too sure. They were created using quite outdated gem2deb backported for stable.
RFS: ruby-mixlib-install, ruby-berkshelf-api-client
Hi team, please review and upload these new packages: * ruby-mixlib-install * ruby-berkshelf-api-client I need to packages Chef related tools Berkshelf and Test-Kitchen. ruby-berkshelf-api-client's test are ignored as they need berkshelf-api server, which needs ruby-berkshelf-api-client. Thanks in advance.
Re: RFS: ruby-websocket-extensions, ruby-websocket-driver
On 3/6/16, Christian Hofstaedtler wrote: >> Please upload a new package ruby-websocket-extensions. > > Missing upstream + pristine-tar branches + tags in git :-) As usually :) Fixed.
RFS: ruby-websocket-extensions, ruby-websocket-driver
Hi team! Please upload a new package ruby-websocket-extensions. When it reaches unstable, please upload updated ruby-websocket-driver with fix for #816882 (I'll send additional request if it will take to long for ruby-websocket-extensions to enter archive). Thanks in advance.
RFS: ruby-mixlib-install, ruby-berkshelf-api-client
Hi team, please review and upload these new packages: * ruby-mixlib-install * ruby-berkshelf-api-client I need to packages Chef related tools Berkshelf and Test-Kitchen. Thanks in advance.
Re: RFS: ruby-raindrops
On 3/2/16, Christian Hofstaedtler wrote: >> I've pushed new version of ruby-raindrops, please upload. Thanks in >> advance. >> >> ruby-raindrops (0.16.0-1) unstable; urgency=medium > > Uploaded, thank you! Thank you :) > Hleb, are you in the DM keyring? I'm still not a DM, there are no acting DD around to sign my key.
RFS: ruby-raindrops
Hi team, I've pushed new version of ruby-raindrops, please upload. Thanks in advance. ruby-raindrops (0.16.0-1) unstable; urgency=medium * Imported Upstream version 0.16.0 * Drop 0003-test-test_linux.rb-use-plain-ASCII-in-tempfile-name.patch * Reflect license change to LGPL-2.1+ -- Hleb Valoshka <375...@gmail.com> Mon, 29 Feb 2016 16:44:41 +0300
Re: RFS: unicorn
On 2/14/16, Pirate Praveen wrote: >>I suppose it's to early to upload 5.0.1: > >>1) changelog does not mention all packaging changes between 4.8 and >>5.0.1 > > What are those changes? initscript changes, it does not use 'CONFIGURED' variable anymore, now it starts daemon only if config.rb in app path exists, it can do upgrades now. it has hints to start after mysql/postgres. native systemd service file. >>2) NEWS.Debian should be created to reflect the most important changes >>3) I'm still waiting systemd fanboys to provide service file or test >>one from upstream > > See my other mail for an idea. It's good idea, but it should supported not only with systemd but with sysv as well. > >>4) postinstall script should check for current init and run upgrade >>only with sysv or init sytem independent tool should be provided for >>upgrades > > Do we not have both init script and systemd unit files already? We have, but the main idea of systemd is to use upstream units, so why to have an own one?
Re: RFS: unicorn
On 2/12/16, Christian Hofstaedtler wrote: > Hleb, > > > * Rahulkrishnan R A [160212 16:52]: >> I have updated unicorn to the latest version. It is lintian clean and >> tested with pbuilder. Further information about this package can be >> accessed from the URL : >> *https://anonscm.debian.org/cgit/pkg-ruby-extras/unicorn.git > > I'd value your feedback on this. I suppose it's to early to upload 5.0.1: 1) changelog does not mention all packaging changes between 4.8 and 5.0.1 2) NEWS.Debian should be created to reflect the most important changes 3) I'm still waiting systemd fanboys to provide service file or test one from upstream 4) postinstall script should check for current init and run upgrade only with sysv or init sytem independent tool should be provided for upgrades 5) rainbows package should be updated to 5, as version in sid will not work with unicorn 5 I will be thankful if Rahulkrishnan will do that points because I don't have time for this.
Re: RFS: ruby-tzinfo for jessie, fixes #798348
On 9/14/15, Hleb Valoshka <375...@gmail.com> wrote: >>>> Please upload ruby-tzinfo from jessie branch. >>> >>> Did you talk to -release about this already? >> >> No. It's a first time I need to update a package in stable, so I don't >> know the procedure. > > > I've reported #798949 and received approve for upload. Could somebody > upload the package? Hi all! Could anybody upload ruby-tzinfo_1.1.0-2+deb8u1?
Re: Request review for ruby gem packages.
On 1/14/16, Andrew Lee wrote: common issue: compat sh'ld be 9, so debhlper version >= 9~ > 1. ruby-combustion install docs and templates patch source_root (generator.rb) to use templates from proper place > 2. ruby-appraiser-reek and > 3. ruby-appraiser-rubocop you sh'ld package reek (>= 0), ruby-appraiser (>= 1.0.3) use current long description instead of short one, expand a long one > 4. ruby-json-pure Not uploaded yet. We already have this gem, see ruby-json > 5. ruby-jeweler Do you really need this package? It used only by ruby-cocoon/Rakefile to generate new cocoon gem. > 6. ruby-psych in debian/ruby-tests.rake fix FileList['test/*_test.rb'] to FileList['test/psych/test_*.rb'] > 7. ruby-racc As I noted previously we already have this gem.
Re: Request review for ruby gem packages.
On 1/14/16, Andrew Lee wrote: > 7. ruby-racc We already have this package, it's called `racc'.
Re: Request review for ruby gem packages.
On 12/19/15, Andrew Lee wrote: > Would you mind to help to review again? I drop a look on git snapshot of Dec 30, so some notes may be outdated, I see you have updated some packages. Common: 0. A lot of missing years in copyrights > 1. ruby-acts-as-list, have you tried to build it? > terceiro told me I should use https://rubygems.org/gems/acts_as_list > instead. > I have updated the package with acts_as_list, please recheck this for me. - don't depend on bundler - test/helper.rb showl look as require "active_record" require "minitest/autorun" require "acts-as-list" require "shared" - you still need to add ruby-sqlite3 to Build-Depends - fix debian/copyright > 2. ruby-cliver. >> May be there is no need to install CONTRIBUTING.md it's useless >> for end user. >> Specs are nor Rspec3 compatible use transpec to convert. >> Patch cliver.rb to use require "core_ext/file" instead of require >> File.expand_path('../core_ext/file', __FILE__) >> > > Done. - previous fixed - new introduced, "bundler (>> 1.3), rake, ruby-rspec, ruby-appraiser-reek, ruby-appraiser-rubocop, yard" -- this should go to Build-Depends, you should not using bundler (and no need to use ruby-appraiser-reek, ruby-appraiser-rubocop, yard -- but I'm not sure) - copyright has no year > > 3. ruby-clockwork. >> In specs remove require "rubygems" and replace require >> File.expand_path('../../lib/clockwork', __FILE__) with require >> "clockwork". >> Fix Depends: in debian/control. >> Install clockworkd.1 as manpage and example.rb as example. >> > > Done. > - "bundler, rake, ruby-daemons, ruby-test-unit, ruby-minitest, ruby-mocha" -- this should go to Build-Depends, you should not using bundler > 4. ruby-cocoon. >> Fix Depends and Build-Depends. >> In install_generator.rb you should patch source_root >> File.expand_path('../templates', __FILE__), dunno what the proper >> value is. >> Instead of adding History.md to docs install it using >> override_dh_installchangelogs: >> dh_installchangelogs History.md -O--buildsystem=ruby >> > > Done as with previuos packages, several packages are listed in depends instead of build-depends > >> 5. ruby-codemirror-rails >> Don't embed 3rd party code (codemirror js/css) in your package. >> > Do you mean the files under vendor/? yes >> Fix Depends and Build-Depends. >> > Fixed Depends. Don't know what's need to be fix in Build-Depends? things marked as development, i.e. rails (>= 0, development), sqlite3 (>= 0, development), minitest (>= 0, development) > >> 6. ruby-innertube >> Remove from spec helper: >> $: << File.expand_path('../../lib', __FILE__) >> $: << File.expand_path('..', __FILE__) >> require 'rubygems' >> > > Done. - remove ruby-rspec (>> 2.10.0) from Depends - fix links in descrition: [Riak Ruby Client](/basho/riak-ruby-client), [Riak](/basho/riak) > >> 7. ruby-joiner >> Specs will not work w/o combustion, it's not packaged, consider >> packaging. >> > What do you mean? You mean 'ruby-combustion' needs to be packaging as well? yes > >> Fix Depends and Build-Depends. >> Remove from spec helper: >> require 'rubygems' >> require 'bundler/setup' >> > > Done. ruby-combustion, ruby-rails, ruby-rspec-rails, ruby-sqlite3 -- for Build-Depends, not Depends > >> 8. ruby-jquery-datatables-rails >> As usual, fix Depends. >> 3rd party data files should go into their own package, packages >> from their upstream, and embedded copy should be removed. >> > What do you mean exactly? consider packaging files in app/ to their our package, take them from their upstream, or at least fix debian/copyright to reflect all authors >> Ask somebody with good rail background to review. It seems to me >> that you should patch install_generator.rb: >> js_manifest = 'app/assets/javascripts/application.js' >> css_manifest = 'app/assets/stylesheets/application.css' >> > Does anyone who has idea on how should this be patched? > > > >> 10. ruby-pundit >> Fix Depends and Build-Depends. >> Do end user really needs CONTRIBUTING.md and CODE_OF_CONDUCT.md? >> > > Done. - description: expand "oo" - move several packages from depends to build-depends > >> 11. ruby-rails-tokeninput >> I'm not Rails expert, but do we actually need this package? It >> does nothing in Rails 4. >> And jquery tokeninput scripts and stylesheets should not be embedded. >> > You mean app/? yes - move several packages from depends to build-depends, don't use bundler > >> 12. ruby-riddle >> Fix Depends and Build-Depends (ruby-mysql2). >> Install HISTORY as in ruby-cocoon. >> Remove from spec helper: >> require 'rubygems' >> require 'bundler' >> >> $:.unshift File.dirname(__FILE__) + '/../lib' >> $:.unshift File.dirname(__FILE__) + '/..' >> >> Bundler.require :default, :development >> > > Done. rake, ruby-rspec, yard -- these thing has nothing to do in depends > >> 13. ruby-sprite-factory >> Fix Depends
Re: RFS: ruby-grape-msgpack ruby-websocket-parser ruby-httpclient ruby-tzinfo
On 10/14/15, Per Andersson wrote: >> and ruby-tzinfo to stable. > > From what I can see ruby-tzinfo still needs to be uploaded to stable, > is it so? Yes, so far.
Re: RFS: ruby-grape-msgpack ruby-websocket-parser ruby-httpclient
On 10/12/15, Per Andersson wrote: > Oh, forgot to say: Thanks for your work! :-) Thanks for your upload! I was waiting for ages for it :)
Re: RFS: ruby-grape-msgpack ruby-websocket-parser ruby-httpclient
On 10/1/15, Pirate Praveen wrote: > One test is failing in pbuilder, can you have a look at it? > > Error: test_basic_auth_post_with_multipart(TestAuth): > HTTPClient::KeepAliveDisconnected: HTTPClient::KeepAliveDisconnected: > Connection reset by peer Is it reproducible at your pbuilder? I was unable to reproduce it (but had other 2 rare random failures).
RFS: ruby-locale, ruby-gettext
Hi team, please upload new releases of ruby-locale and ruby-gettext, they fix #799050 and #799194. Thanks in advance.
Re: lintian. how to shut it up?
On 9/23/15, Antonio Terceiro wrote: > using the correct syntax for lintian overrides might do the trick: > > ruby-locale: package-contains-timestamped-gzip > usr/share/ruby-locale/data/languages.tab.gz > ruby-locale: package-contains-timestamped-gzip > usr/share/ruby-locale/data/regions.tab.gz Thanks. I was using this syntax but it did not help, may be was put into wrong place (d/source). Now it works.
lintian. how to shut it up?
Hi team. I'm using Lintian v2.5.35~bpo8+1, ruby-locales contains 2 gzipped files. As these files came from upstream I want make lintian to shut up. I put file debian/lintian-overrides with content: ruby-locale: package-contains-timestamped-gzip usr/share/ruby-locale/data/languages.tab.gz usr/share/ruby-locale/data/regions.tab.gz But it still reports W: ruby-locale: package-contains-timestamped-gzip usr/share/ruby-locale/data/languages.tab.gz W: ruby-locale: package-contains-timestamped-gzip usr/share/ruby-locale/data/regions.tab.gz How to silence it?
RFS: ruby-grape-msgpack ruby-websocket-parser ruby-httpclient ruby-tzinfo
Hi team. Please upload ruby-grape-msgpack ruby-websocket-parser to unstable, ruby-httpclient ot experimental (or unstable) and ruby-tzinfo to stable.