[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ruby-cmdparse [was:] help welcome



Am Dienstag, den 10.11.2020, 16:23 +0100 schrieb Klaumi Klingsporn:
> Am / On Mon, 09 Nov 2020 23:28:01 +0100
> schrieb / wrote Daniel Leidert <dleidert@debian.org>:

[..]
> "/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:101:in
> `block in do_check_dependencies': E: dependency resolution
> check requested but no working gemspec available for binary
> package ruby-cmdparse (RuntimeError) 
> from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:89:in
> `each' 
> from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:89:in
> `do_check_dependencies' 
> from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:79:in
> `run_tests' from /usr/bin/gem2deb-test-runner:67:in
> `<main>' 
> autopkgtest [15:24:39]: test gem2deb-test-runner:
> -----------------------] 
> gem2deb-test-runner  FAIL non-zero exit status 1 
> autopkgtest [15:24:39]: test
> gem2deb-test-runner:  - - - - - - - - - - results - - - - -
> - - - - - 
> autopkgtest [15:24:39]: @@@@@@@@@@@@@@@@@@@@
> summary gem2deb-test-runner  FAIL non-zero exit status 1
> 
> WARNING: Test suite failed! Please verify before uploading"
> 
> I guess I have to worry about this ;-)

Ok. The github sources don't contain a .gemspec file but the gem does. The
.gemspec is created by a rake task in Rakefile.

Three options:
1) Add a patch to create the .gemspec file.
2) Run the rake task to create the gemspec file in debian/rules
3) Instead of using the github sources use the gem (delete the upstream/3.0.6
tag and re-import the source using the gem -> debian/watch needs to be reverted
to using gemwatch ... I know, sorry)

This project is working kind of differently compared to many other ruby
projects.

> > If you want to have someone take a look at your changes
> > please feel free to push your branch and the updated
> > upstream and pristine-tar branches to salsa.
> 
> As I work in a new created branch and the master-branch will
> stay as is, I think it will do no harm to push, so you can
> get a look. 
> 
> 'gbp push' refuses to work because I'm not in the
> master-branch, so I would try 
> 
> gbp push --debian-branch=debian-3.0.6
> 
> but whatever I would like to do or should do, even with
> --dry-run gbp only tells me:
> "You are not allowed to push code to this project."

I quickly checked. You don't seem to be a member of the ruby-team on
salsa.debian.org. If you want to push directly you need to apply for team
membership. Alternatively: if you have forked the repository from the Ruby team
into your own namespace then push the changes to your repository and create
merge requests against the team's repository.

Regards, Daniel
-- 
Regards,
Daniel Leidert <dleidert@debian.org> | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: