Re: ruby-cmdparse [was:] help welcome

2020-11-11 Thread Klaumi Klingsporn
Am / On Wed, 11 Nov 2020 14:34:41 +0100 schrieb / wrote Daniel Leidert : > Nope. You didn't fork the project first. Merge requests > can only be created for projects with a > forking-relationship. So I learned the difference between importing and forking a project ;-) > Two options: > > 1) Cre

Re: ruby-cmdparse [was:] help welcome

2020-11-11 Thread Daniel Leidert
Am Mittwoch, den 11.11.2020, 14:00 +0100 schrieb Klaumi Klingsporn: > Am / On Wed, 11 Nov 2020 03:16:14 +0100 > schrieb / wrote Daniel Leidert : > > > I'll have a look. But you can still create the merge > > requests. It makes it easier to compare the changes. > > Because you updated to a newer up

Re: ruby-cmdparse [was:] help welcome

2020-11-11 Thread Klaumi Klingsporn
Am / On Wed, 11 Nov 2020 03:16:14 +0100 schrieb / wrote Daniel Leidert : > I'll have a look. But you can still create the merge > requests. It makes it easier to compare the changes. > Because you updated to a newer upstream versuon you must > create merge requests for all affacted branches inlcud

Re: ruby-cmdparse [was:] help welcome

2020-11-10 Thread Daniel Leidert
Am Mittwoch, den 11.11.2020, 00:42 +0100 schrieb Klaumi Klingsporn: > Am / On Tue, 10 Nov 2020 16:53:45 +0100 > schrieb / wrote Daniel Leidert : [..] > The package builds now and the tests ran without errors :-) > Only a few lintian warnings which I fixed, only the ones > about missing nmu-entries

Re: ruby-cmdparse [was:] help welcome

2020-11-10 Thread Klaumi Klingsporn
Am / On Tue, 10 Nov 2020 21:57:41 +0530 schrieb / wrote Pirate Praveen : > On 2020, നവംബർ 10 9:23:45 PM IST, Daniel Leidert > wrote: > >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

Re: ruby-cmdparse [was:] help welcome

2020-11-10 Thread Klaumi Klingsporn
Am / On Tue, 10 Nov 2020 16:53:45 +0100 schrieb / wrote Daniel Leidert : > 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 crea

Re: ruby-cmdparse [was:] help welcome

2020-11-10 Thread Pirate Praveen
On 2020, നവംബർ 10 9:23:45 PM IST, Daniel Leidert wrote: >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

Re: ruby-cmdparse [was:] help welcome

2020-11-10 Thread Daniel Leidert
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 : [..] > "/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:101:in > `block in do_check_dependencies': E: dependency resolution > check requested but no wor

Re: ruby-cmdparse [was:] help welcome

2020-11-10 Thread Klaumi Klingsporn
Am / On Mon, 09 Nov 2020 23:28:01 +0100 schrieb / wrote Daniel Leidert : > The ruby-tests.* file can be removed. Upstream doesn't > provide any tests anymore. Not sure why. The commit > message doesn't mention why the tests have been dropped. "Ok, I removed the ruby-tests.rb again, the package co

Re: ruby-cmdparse [was:] help welcome

2020-11-09 Thread Daniel Leidert
Am Montag, den 09.11.2020, 17:29 +0100 schrieb Klaumi Klingsporn: > Am / On Mon, 09 Nov 2020 00:28:53 +0100 > schrieb / wrote Daniel Leidert : > > > They use a different naming scheme for their source > > tarballs. This one works: > > > > version=4 > > https://github.com/gettalong/cmdparse/releas

Re: ruby-cmdparse [was:] help welcome

2020-11-09 Thread Klaumi Klingsporn
Am / On Mon, 09 Nov 2020 00:28:53 +0100 schrieb / wrote Daniel Leidert : > They use a different naming scheme for their source > tarballs. This one works: > > version=4 > https://github.com/gettalong/cmdparse/releases > .*/REL_(\d+)_(\d+)_(\d+)@ARCHIVE_EXT@ Thanks, that helped a lot, but I had t