Re: Migrating custom rails assets smoke test to use gem2deb

[Pirate Praveen]

On 8/2/24 12:57 AM, Pirate Praveen wrote:
Though it looks this can't work during build when the asset is a link. 


We can track this in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063478


Meanwhile I got this method working with 
ruby-rails-assets-markdown-it-diaspora-mention which had the assets 
shipped directly in the source package.


See 
https://salsa.debian.org/ruby-team/ruby-rails-assets-markdown-it-diaspora-mention/-/commit/6d8fc2cf602493f0c0226345dcd973a6a96d00e5


1. Update build dependencies
2. Add debian/assets/javascripts
3. Drop debian/tests/{control,smoke-test)

Re: Migrating custom rails assets smoke test to use gem2deb

[Pirate Praveen]

On 7/2/24 9:13 PM, Pirate Praveen wrote:

Hi team,

We used to duplicate a dummy rails app to create a smoke test for rails 
assets pipeline, but this meant when there is a change in dependencies 
or dummy app, every package needs change. In gem2deb 2.2 we now have a 
single place to manage the dummy app and we only need to mention the 
assets to be tested.


Documentation: 
https://manpages.debian.org/unstable/gem2deb/dh_ruby.1.en.html#debian/tests/assets


Though it looks this can't work during build when the asset is a link. 
See ruby-jquery-rails for example.


I think this test should be run after dh_link or only run as autopkgtests.

The error when building,

rake aborted!
Sprockets::FileNotFound: couldn't find file 'jquery' with type 
'application/javascript'

Checked in these paths:
  /tmp/testapp/app/assets/javascripts

/usr/share/rubygems-integration/all/gems/actionview-6.1.7.3/lib/assets/compiled
/tmp/testapp/app/assets/javascripts/application.js:1
/usr/share/rubygems-integration/all/gems/sprockets-rails-3.4.1/lib/sprockets/rails/task.rb:67:in 
`block (3 levels) in define'
/usr/share/rubygems-integration/all/gems/sprockets-rails-3.4.1/lib/sprockets/rails/task.rb:66:in 
`block (2 levels) in define'

Tasks: TOP => assets:precompile
(See full trace by running task with --trace)

I have pushed the changes to debian-tests-assets branch.

Please add your name next to it and strike out once uploaded in the pad 
linked below


https://storm.debian.net/shared/3N_sZG2n5AiZAQWSVXenFc9Txd__cgwMna0Ue3cWYFz

Thanks
Praveen

Migrating custom rails assets smoke test to use gem2deb

[Pirate Praveen]

Hi team,

We used to duplicate a dummy rails app to create a smoke test for rails 
assets pipeline, but this meant when there is a change in dependencies 
or dummy app, every package needs change. In gem2deb 2.2 we now have a 
single place to manage the dummy app and we only need to mention the 
assets to be tested.


Documentation: 
https://manpages.debian.org/unstable/gem2deb/dh_ruby.1.en.html#debian/tests/assets


Please add your name next to it and strike out once uploaded in the pad 
linked below


https://storm.debian.net/shared/3N_sZG2n5AiZAQWSVXenFc9Txd__cgwMna0Ue3cWYFz

Thanks
Praveen

Re: RFS: ruby-flores 0.0.8

[Pirate Praveen]

On Fri, Dec 15 2023 at 12:32:17 +05:30:00, Abhijith PA 
 wrote:

Hello o/.

On 12/12/23 01:49 AM, Ajayi Olatunji O. wrote:

 Hi,

 I just packaged ruby-flores 0.0.8, a build dependency for arr-pm
 0.0.12, which is a build dependency for gitlab 15.11.6

 Kindly check the package out at
 

 Please review and sponsor. Thank you!


By the description of arr-pm, "Written in pure ruby because librpm is
not available on all systems". We already have librpm[1] in archive.
Perhaps we can depend on that ?

Also I am not sure why gitlab will be handling rpm packages, unless
its a core functionality I guess we can remove it.



Both suggestions would require more work/ruby skills and long term 
maintenance from us. Compared to that updating a ruby gem is lower 
barrier.


gitlab allows hosting deb/rpm repos from ci so we shouldn't disable it.

thanks.

--abhijith

[1] - 

Re: [RFS] ruby-activerecord-import 1.5.0-1

[Pirate Praveen]

On 15/10/23 9:58 AM, Ravish BC wrote:


Hello Pirate Praveen,
Looks like you have disabled the patch in 
https://salsa.debian.org/ravish0007/ruby-activerecord-import/-/commit/6e03aa382d26622f6487755a3263b162e143cb71


If this patch is no longer required, you should remove it.

The patch has been removed, as it is applied in the upstream. Thanks.


Uploaded, thanks for your contribution. Please start signing your 
commits from next time so it is easier to validate your contributions 
when you request for upload rights later.

Re: [RFS] ruby-activerecord-import 1.5.0-1

[Pirate Praveen]

On 3/10/23 5:49 PM, Ravish BC wrote:

Hi,

The following package is updated to 1.5.0 and ready to uploaded.

Could you please sponsor the following new package?

ruby-activerecord-import 1.5.0-1 
(https://salsa.debian.org/ravish0007/ruby-activerecord-import/)


Thank you!


Looks like you have disabled the patch in 
https://salsa.debian.org/ravish0007/ruby-activerecord-import/-/commit/6e03aa382d26622f6487755a3263b162e143cb71


If this patch is no longer required, you should remove it.



---
Ravish B C

Re: [RFS] ruby-duo-api 1.3.0-1

[Pirate Praveen]

On 14/9/23 4:47 PM, Ravish BC wrote:

Hi,

The following package are ready to be uploaded and it is required for gitlab 
16.1.0

Could you please sponsor the following new package?

ruby-duo-api 1.3.0-1 (https://salsa.debian.org/ravish0007/ruby-duo-api/)


Uploaded, congrats on your first upload.


Thank you!

---
Ravish B C

Re: state of ruby-celluloid-* packages

[Pirate Praveen]

On 21/9/23 5:53 PM, Cédric Boutillier wrote:

Dear all,

I wanted to have your opinion on the status and the future of the
ruby-celluloid(-*) packages. My understanding is that the project is
unmaintained for several years (since 2016 it seems), and most project
using that moved away to something else (I saw a mention of
async-websocket).

The only package in Debian which uses ruby-celluloid are ruby-rubydns
and ruby-eye. Ruby-eye is a (build-)dependency for diaspora only, is
also kind of unmaintained for a long time.


I hope to have another look at diaspora when 1.0 is released 
https://github.com/diaspora/diaspora/milestone/35


The last version of ruby-eye 0.10.0, which is in git, but not in Debian
yet, requires a "newer" ruby-celluloid-io, which is also in git, which
requires a new package ruby-celluloid-rspec to run tests.

I was planning to maybe upload for now this celluloid-io without
enabling the tests for now, to solve  #1031479, but I was wondering if I
should put energy in trying to package the -rspec piece. Diaspora
maintainers, do you know if the eye gem is still essential for diaspora,
if they plan to move to something else?
If yes, we can think about phasing out this family of packages from
Debian.


We have managed to create systemd service files without using ruby-eye 
so we can get rid of ruby-eye


https://salsa.debian.org/ruby-team/diaspora-installer/-/commit/96160c7d54cad8e8475aaa9719480eac465addf9



Best wishes,

Cédric

Re: RFS: ruby-flores 0.0.8

[Pirate Praveen]

On 25/7/23 5:31 AM, thegodtune wrote:

Hi,

I just packaged ruby-flores 0.0.8, a build dependency for arr-pm
0.0.12, which is a build dependency for gitlab 15.11.6

Kindly check the package out at
https://salsa.debian.org/thegodtune/ruby-flores

Please review and sponsor. Thank you!


1. Please use pristine-tar branch and push
2. Please have separate commits for each logical change
3. Your override_dh_auto_install is unnecessary and currently no ruby 
files are included in the final deb file


For disabling a specific test, you can use patch like

--- a/spec/flores/pki_integration_spec.rb
+++ b/spec/flores/pki_integration_spec.rb
@@ -56,7 +56,7 @@
   end
 end

-it "should successfully connect as a client" do
+xit "should successfully connect as a client" do
   socket = TCPSocket.new(server_address, server_port)
   ssl_client = OpenSSL::SSL::SSLSocket.new(socket, client_context)
   ssl_client.connect

Re: Faraday 2 transition (was Re: Many ruby library transitions for gitlab reupload to experimental)

[Pirate Praveen]

On Mon, Jun 19 2023 at 03:21:54 PM +05:30:00 +05:30:00, Pirate Praveen 
 wrote:



On Sat, Jun 17 2023 at 06:50:02 PM +05:30:00 +05:30:00, Pirate 
Praveen  wrote:

I'm using this pad to track the reuploads
https://storm.debian.net/shared/KsibMVg-48Iaa_ooNGxsMxaFisv74u1tDeH_jX00GWJ




Since most the issues are fixed (only 3 packages remains to be fixed), 
I hope to upload ruby-faraday 2.0 to unstable around 1st August.


Summary (still help needed): ruby-puppet-forge 1025078, ruby-typhoeus 
1025075, ruby-gh 1025090


- fixed upstream: ruby-acme-client 1025098 (need new gem: 
ruby-faraday-retry in new - praveen), ruby-asana 1025097 (need new 
gems: faraday-multipart in new - praveen and 
faraday-follow_redirects), ruby-graphlient 1025084 (gitlab should be 
updated along with it), ruby-puppet-forge 1025078, rabbit 1037963


Now only one remaining in this - ruby-puppet-forge 1025078


- fixed in upstream pull request: ruby-azure-storage-common 1025095 
(need faraday-net_http_persistent)


This is done.


- fail: ruby-typhoeus 1025075 (need new gem typhoeus-faraday)

- reported upstream: ruby-gh 1025090,


These two still remaining.


- deprecated: ruby-faraday-middleware 1025092, ruby-ms-rest 1037992 
and ruby-ms-rest-azure 1037994 (these should be removed after 
https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/issues/3), 
ruby-google-cloud-translate 1025085 (leaf package, can be removed)




The main one remaining is ruby-faraday-middleware 1025092


- ignored (leaf package): ruby-behance 1025094

So I'm pausing this transition till gitlab upstream updates 
graphlient and gitlab-fog-azure-rm. Help is welcome on the new 
faraday gems (faraday-follow_redirects, faraday-net_http_persistent) 
updating packages already fixed upstream.




These are uploaded/accepted too.

Faraday 2 transition (was Re: Many ruby library transitions for gitlab reupload to experimental)

[Pirate Praveen]

On Sat, Jun 17 2023 at 06:50:02 PM +05:30:00 +05:30:00, Pirate Praveen 
 wrote:

I'm using this pad to track the reuploads
https://storm.debian.net/shared/KsibMVg-48Iaa_ooNGxsMxaFisv74u1tDeH_jX00GWJ


- ruby-countries - it built fine locally, but failed on the buildd so
help is welcome to check one failing test

skipped the failing test for now.



   ruby-faraday: will need fixing 15 packages, some of them already 
fixed upstream, though needs packaging some new gems which were split 
from faraday. Help is very much welcome here.


I have gone through all the failures and categorized the failures to,

- fixed upstream: ruby-acme-client 1025098 (need new gem: 
ruby-faraday-retry in new - praveen), ruby-asana 1025097 (need new 
gems: faraday-multipart in new - praveen and faraday-follow_redirects), 
ruby-graphlient 1025084 (gitlab should be updated along with it), 
ruby-puppet-forge 1025078, rabbit 1037963


- fixed in upstream pull request: ruby-azure-storage-common 1025095 
(need faraday-net_http_persistent)


- fail: ruby-typhoeus 1025075 (need new gem typhoeus-faraday)

- reported upstream: ruby-gh 1025090,

- deprecated: ruby-faraday-middleware 1025092, ruby-ms-rest 1037992 and 
ruby-ms-rest-azure 1037994 (these should be removed after 
https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/issues/3), 
ruby-google-cloud-translate 1025085 (leaf package, can be removed)


- ignored (leaf package): ruby-behance 1025094

So I'm pausing this transition till gitlab upstream updates graphlient 
and gitlab-fog-azure-rm. Help is welcome on the new faraday gems 
(faraday-follow_redirects, faraday-net_http_persistent) updating 
packages already fixed upstream.




All of these requploaded to unstable (now only ruby-recaptcha and 
ruby-ruby-parser is left)


These two reuploaded as well, ruby-ruby-parser test failure was fixed 
when ruby-sexp-processor was updated.

Re: Many ruby library transitions for gitlab reupload to experimental

[Pirate Praveen]

On Wed, Jun 14 2023 at 09:22:24 PM +05:30:00 +05:30:00, Praveen 
Arimbrathodiyil  wrote:

On 13/06/23 1:16 pm, Pirate Praveen wrote:

I'm using this pad to track the reuploads
https://storm.debian.net/shared/KsibMVg-48Iaa_ooNGxsMxaFisv74u1tDeH_jX00GWJ


about 32 packages have been re-uploaded so far, ruby-googleauth being 
a

major update among this.

- ruby-countries - it built fine locally, but failed on the buildd so
help is welcome to check one failing test
- ruby-rouge - redmine still needs fixing 1037465 (thanks to boutil 
and

terceiro for fixing asciidoctor/ruby-kramdown-parser-gfm and nanoc).


I proposed on the redmine bug to upload ruby-rouge on July 1st in case 
redmine is not fixed by then.



- ruby-cfpropertylist - fix ruby-fission ftbfs


fixed thanks to boutil.

- ruby-net-http-persistent - this has to go along with ruby-faraday,
which seems like a bigger transition


   ruby-faraday: will need fixing 15 packages, some of them already 
fixed upstream, though needs packaging some new gems which were split 
from faraday. Help is very much welcome here.


these are fixed upstream: ruby-acme-client 1025098 (new gem: 
ruby-faraday-retry - praveen, in new), ruby-asana 1025097 (new gems: 
faraday-multipart and faraday-follow_redirects),


not investigated upstream status yet: rabbit 1037963, 
ruby-azure-storage-common 1025095, ruby-behance 1025094, 
ruby-faraday-middleware 1025092, ruby-gh 1025090, ruby-google-cloud-env 
1025087, ruby-google-cloud-translate 1025085, ruby-graphlient 1025084, 
ruby-ms-rest 1037992, ruby-ms-rest-azure 1037994, ruby-octokit - 
indirectly via ruby-sawyer 1025077, ruby-puppet-forge 1025078, 
ruby-typhoeus 1025075




6 ruby-google-apis-* is probably a simple rebuild as ruby-googleauth 

1.3
and ruby-google-apis-core are available in unstable.


All of these requploaded to unstable (now only ruby-recaptcha and 
ruby-ruby-parser is left)

Many ruby library transitions for gitlab reupload to experimental

[Pirate Praveen]

Hi,

Bookworm is out and I am trying to reupload all gitlab dependencies 
staged in experimental during freeze to unstable.


I'm using this pad to track the reuploads
https://storm.debian.net/shared/KsibMVg-48Iaa_ooNGxsMxaFisv74u1tDeH_jX00GWJ

Some reuploads are breaking changes and we will need to test and fix 
packages other than gitlab, for example rouge is a major update and 
redmine and few other packages needs to be updated.


Help is welcome to get this completed, especially for the transitions 
like ruby-rouge.


If you'd like to pick any package, just add your name to the pad and if 
more work needs to be done, please file bugs and add notes to the pad 
(this pad can give an overview).


Thanks
Praveen

Re: Comments regarding ruby-ruby-openai_3.7.0-2_amd64.changes

[Pirate Praveen]

On Thu, May 11 2023 at 05:45:36 PM +00:00:00 +00:00:00, Thorsten 
Alteholz  wrote:

Hi,

ruby-ruby-... as package name is really intentional?



Yes, we had problems when multiple gems only differ in ruby prefix in 
there names. There was parser and ruby_parser gem which made things 
even more confusing. So now we add ruby- prefix to all gems even if the 
name themselves have ruby in it. This pattern is followed for node 
modules as well.



  Thorsten

Re: RFS: ruby-digest-crc 0.4.0-1

[Pirate Praveen]

On Sat, Apr 8 2023 at 05:39:35 AM +05:30:00 +05:30:00, Ravi Dwivedi 
 wrote:

Hi,

The following packages are ready to be uploaded (I also verified the
points listed on
http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship).

It is required for gitlab 15.9.2.

Could you please sponsor them?

 ruby-digest-crc 0.4.0-1
(https://salsa.debian.org/ruby-team/mentors/ruby-digest-crc)



Uploaded, thanks for your contribution!


Thank you!

---
Ravi Dwivedi

Re: [RFS] ruby-app-store-connect

[Pirate Praveen]

On Sat, Apr 1 2023 at 03:58:30 PM +05:30:00 +05:30:00, Vinay 
 wrote:

Hello Team,

Requesting sponsorship for the new package ruby-apps-store-connect 
[1] required for Gitlab.


[1] https://salsa.debian.org/ruby-team/ruby-app-store-connect


please remove debian directory from the gem file list, see this patch 
for example

https://salsa.debian.org/ruby-team/ruby-httparty/-/blob/master/debian/patches/git-in-gemspecs.patch

Thank You

Vinay 

2F7E32FC9C01622BC797E60AD3FDE3D93A1FCF50

Re: RFS: ruby-google-apis-cloudbilling-v1 0.21.0-1, ruby-google-apis-iam-v1 0.36.0-1

[Pirate Praveen]

On Thu, Apr 6 2023 at 12:52:02 AM +05:30:00 +05:30:00, Ravi Dwivedi 
 wrote:

Hi,

The following packages are ready to be uploaded (I also verified the
points listed on
http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship).

Both of them are required for gitlab 15.9.2

Could you please sponsor them?

 ruby-google-apis-cloudbilling-v1 0.21.0-1
(see
https://salsa.debian.org/ruby-team/mentors/ruby-google-apis-cloudbilling-v1)

 ruby-google-apis-iam-v1 0.36.0-1
(see 
https://salsa.debian.org/ruby-team/mentors/ruby-google-apis-iam-v1)




Uploaded, thanks for your contribution!


Thank you!

---
Ravi Dwivedi

Re: RFS: ruby-aws-sdk-core-3.170.0-1

[Pirate Praveen]

On Wed, Apr 5 2023 at 08:28:52 PM +05:30:00 +05:30:00, Ravi Dwivedi 
 wrote:

Forgot to give the repository link. Here it is
https://salsa.debian.org/ruby-team/mentors/ruby-aws-sdk-core



Uploaded, thanks for your work. Next time use ruby-team/mentors only 
for new packages. For updates, you can request access to the ruby-team 
group.



On 4/5/23 20:27, Ravi Dwivedi wrote:

Hi,

The following packages are ready to be uploaded (I also verified the
points listed on
http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship).

This is required for gitlab 15.9.2.

Could you please sponsor them?

  ruby-aws-sdk-core-3.170.0-1

Thank you!

---
Ravi Dwivedi

Re: [RFS] -- ruby-google-apis-cloudresourcemanager-v1

[Pirate Praveen]

On Wed, Apr 5 2023 at 07:17:52 PM +05:30:00 +05:30:00, Vinay 
 wrote:

Hello Team,

Requesting sponsorship for the new package 
ruby-google-apis-cloudresourcemanager-v1 [1] required for gitlab 
15.9.2


[1] 
https://salsa.debian.org/ruby-team/ruby-google-apis-cloudresourcemanager-v1




Uploaded, thanks for your work!

---

Thank You

Vinay  

2F7E32FC9C01622BC797E60AD3FDE3D93A1FCF50

Re: [RFS] ruby-et-orbi (1.2.7)

[Pirate Praveen]

On Mon, Mar 27 2023 at 07:12:07 PM +05:30:00 +05:30:00, Vinay 
 wrote:

Hello Team,

Requesting sponsorship/upload access for the package ruby-et-orbi 
[1], have updated it to v1.2.7 (targeting experimental)


Required for GitLab 15.9.2


[1] https://salsa.debian.org/ruby-team/ruby-et-orbi


Granted DM access for all the RFS. You can upload them directly.

Re: [RFS] -- ruby-recaptcha v5.12.3

[Pirate Praveen]

On Thu, Mar 9 2023 at 12:37:55 AM +05:30:00 +05:30:00, Vinay 
 wrote:

Hello Team,
 Requesting sponsorship for the package ruby-recaptcha [1], updated 
it to latest upstream version 5.12.3

 required for GitLab 15.8.4.



Uploaded, thanks for your work.

[1] https://salsa.debian.org/ruby-team/ruby-recaptcha


 Best

Vinay 

2F7E 32FC 9C01 622B C797 E60A D3FD E3D9 3A1F CF50

Re: [RFS] -- ruby-google-apis-sqladmin-v1beta4

[Pirate Praveen]

On Sun, Mar 5 2023 at 04:10:03 PM +05:30:00 +05:30:00, Vinay 
 wrote:

Hello Team,
 Requesting sponsorship for the new package 
ruby-google-apis-sqladmin-v1beta4  [1] ( targeting experimental)


Required for GitLab 15.7.6



Uploaded, thanks for your work.
[1] 
https://salsa.debian.org/ruby-team/ruby-google-apis-sqladmin-v1beta4




Vinay  

Re: RFS: ruby-google-apis-pubsub-v1 0.7.0-1

[Pirate Praveen]

On Sun, Mar 5 2023 at 04:11:23 PM +05:30:00 +05:30:00, Ravi Dwivedi 
 wrote:

Hi,

The following packages are ready to be uploaded (I also verified the
points listed on
http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship).

Reason: this gem is required to package gitlab. See
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191.

Could you please sponsor them?

ruby-google-apis-pubsub-v1 0.7.0-1

See https://salsa.debian.org/ravi/ruby-google-apis-pubsub-v1


Uploaded, thanks for your work.


Thank you!
---
Ravi Dwivedi

Re: [RFS] ruby-aws-sdk-s3 (1.117.2)

[Pirate Praveen]

On Sun, Feb 19 2023 at 10:22:25 PM +05:30:00 +05:30:00, Vinay 
 wrote:

Hello Team,

Requesting Sponsorship for the new package ruby-aws-sdk-s3 (1.117.2-1)

This gem is listed here [2] and is a dependency of Gitlab 15.7.6



Uploaded, thanks for your work.

[1] hhttps://salsa.debian.org/ruby-team/ruby-aws-sdk-s3

[2] https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191


Regards.

Vinay Keshava 

Re: [RFS] -- ruby-i18n-data 0.13.0

[Pirate Praveen]

On Wed, Mar 1 2023 at 01:00:15 AM +05:30:00 +05:30:00, Vinay 
 wrote:

Hello Team,
 Requesting sponsorship for the package ruby-i18n-data [1] required 
for GitLab 15.7.6


Have updated it to the version 0.13.0



Please merge the UNRELEASED entry with the latest entry in changelog.

[1] https://salsa.debian.org/ruby-team/ruby-i18n-data

---

Best

Vinay Keshava 

Re: [RFS] -- ruby-i18n-data 0.13.0

[Pirate Praveen]

On Tue, Feb 28 2023 at 07:49:16 PM -03:00:00 -03:00:00, Antonio 
Terceiro  wrote:

Hi,

On Wed, Mar 01, 2023 at 01:00:15AM +0530, Vinay wrote:

 Hello Team,
 Requesting sponsorship for the package ruby-i18n-data [1] required 
for

 GitLab 15.7.6

 Have updated it to the version 0.13.0


 [1] https://salsa.debian.org/ruby-team/ruby-i18n-data


Note that we are in the middle of the freeze in the preparation for 
the

next Debian release. Updating to new upstream releases is not really
something we should be doing at this point, unless the changes are
minimal/targetted enough and there is a really good reason to have 
them

*now*.


This is targetting experimental, which is expected way of using 
experimental. gitlab upstream only provides security updates for 3 
months, so only way to provide security support is to move to newer 
upstream versions. So we can't stop new version updates during freeze. 
All new upstream versions are uploaded to experimental (except for 
packages that has only gitlab as reverse dependency, and not very 
concerned about removal from testing in case issues arise in the 
version in testing).

Re: RFS: ruby-google-apis-iamcredentials-v1 0.16.0-1

[Pirate Praveen]

On Wed, Feb 15 2023 at 08:19:58 PM +05:30:00 +05:30:00, Ravi Dwivedi 
 wrote:

Hi,

The following packages are ready to be uploaded (I also verified the
points listed on 
http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship). 
I pushed it here 
https://salsa.debian.org/ravi1/ruby-google-apis-iamcredentials-v1.


The gem is required to package gitlab.

Could you please sponsor them?



Uploaded, thanks for your work.

From next time, make separate commits for each logical change, like 
updating copyright, description etc instead of a single commit for all 
changes.


Also next time create the repo under salsa.debian.org/ruby-team/mentors 
group.



 ruby-google-apis-iamcredentials-v1 0.16.0-1

Thank you!

---
Ravi Dwivedi
https://ravidwivedi.in

Re: [RFS] ruby-google-apis-dns-v1

[Pirate Praveen]

On 4/2/23 12:23 PM, Vinay wrote:

Hello Team,

Requesting Sponsorship for the new package ruby-google-apis-dns-v1 
(0.12.0) [1]


This gem is listed here [2] and is a dependency of Gitlab 15.6.1


[1] https://salsa.debian.org/ruby-team/mentors/ruby-google-apis-dns-v1

[2] https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191



Uploaded, thanks!

Re: [RFS] -- ruby-google-api-client 0.53.0

[Pirate Praveen]

On 5/2/23 8:31 AM, Vivek K J wrote:

Hi,

     I've updated ruby-google-api-client fromt 0.50.0 to 0.53.0. The 
updated package should be uploaded to experimental as it has dependency 
on ruby-google-apis-core which is on experimental. The updated package 
is available at 
https://salsa.debian.org/ruby-team/ruby-google-api-client/. Requesting 
for Sponsorship / Upload permission.




Granted upload access.

Re: new restriction in rubygems: installing symlink pointing to parent path not allowed - causes ruby-handlebars-assets to ftbfs

[Pirate Praveen]

On Fri, 03 Jun 2022 21:52:17 +0530 Pirate Praveen 
 wrote:

> May be we can copy during build and replace it by symlink in install?

This fixes the earlier issue, but now some tests fail

# Running:

..E.E..E

Finished in 18.138080s, 1.5437 runs/s, 2.4810 assertions/s.

 1) Error:
HandlebarsAssets::HamlbarsTest#test_render_haml:
ArgumentError: wrong number of arguments (given 2, expected 0..1)
   /usr/lib/ruby/vendor_ruby/temple/engine.rb:44:in `initialize'
   
/<>/lib/handlebars_assets/handlebars_template.rb:106:in 
`new'
   
/<>/lib/handlebars_assets/handlebars_template.rb:106:in 
`choose_engine'
   /<>/lib/handlebars_assets/handlebars_template.rb:26:in 
`prepare'

   /usr/lib/ruby/vendor_ruby/tilt/template.rb:99:in `initialize'
   /<>/test/handlebars_assets/hamlbars_test.rb:23:in `new'
   /<>/test/handlebars_assets/hamlbars_test.rb:23:in 
`test_render_haml'


 2) Error:
HandlebarsAssets::HandlebarsTemplateTest#test_multiple_frameworks_with_ember_render:
ArgumentError: wrong number of arguments (given 2, expected 0..1)
   /usr/lib/ruby/vendor_ruby/temple/engine.rb:44:in `initialize'
   
/<>/lib/handlebars_assets/handlebars_template.rb:106:in 
`new'
   
/<>/lib/handlebars_assets/handlebars_template.rb:106:in 
`choose_engine'
   /<>/lib/handlebars_assets/handlebars_template.rb:26:in 
`prepare'

   /usr/lib/ruby/vendor_ruby/tilt/template.rb:99:in `initialize'
   
/<>/test/handlebars_assets/tilt_handlebars_test.rb:14:in 
`new'
   
/<>/test/handlebars_assets/tilt_handlebars_test.rb:14:in 
`render_it'
   
/<>/test/handlebars_assets/shared/adapter_tests.rb:191:in 
`test_multiple_frameworks_with_ember_render'


 3) Error:
HandlebarsAssets::HandlebarsProcessorTest#test_multiple_frameworks_with_ember_render:
ArgumentError: wrong number of arguments (given 2, expected 0..1)
   /usr/lib/ruby/vendor_ruby/temple/engine.rb:44:in `initialize'
   
/<>/lib/handlebars_assets/handlebars_template.rb:106:in 
`new'
   
/<>/lib/handlebars_assets/handlebars_template.rb:106:in 
`choose_engine'
   /<>/lib/handlebars_assets/handlebars_template.rb:64:in 
`call'
   /<>/lib/handlebars_assets/handlebars_template.rb:49:in 
`call'
   
/<>/test/handlebars_assets/handlebars_processor_test.rb:14:in 
`render_it'
   
/<>/test/handlebars_assets/shared/adapter_tests.rb:191:in 
`test_multiple_frameworks_with_ember_render'


28 runs, 45 assertions, 0 failures, 3 errors, 0 skips
rake aborted!
Command failed with status (1)

Re: [RFS] -- ruby-asciidoctor-kroki

[Pirate Praveen]

On Sun, Jan 15 2023 at 07:45:53 PM +05:30:00 +05:30:00, Vivek K J 
 wrote:

Hi Team,

I've updated ruby-asciidoctor-kroki from 0.5.0 to 0.7.0. I've 
verified that the package is lintian clean and this package doesn't 
have any reverse (build) dependencies. Updated package is available 
at https://salsa.debian.org/ruby-team/ruby-asciidoctor-kroki/ . This 
package is a dependency for GitLab 15.6.1



Since gitlab 15.5 still needs asciidoctor-kroki ~> 0.5.0 in its 
Gemfile, please target experimental and reupload to unstable after 
gitlab 15.6.1 is uploaded.

Requesting for sponsorship / Upload access

--
Regards,

Vivek K J
Debian Maintainer
---
 .''`.
Personal Website:  https://vivekkj.codes: :'  
:

GPG Key: D017 9263 E202 0E40 7157  4073 A5FF 4BB3 EA53 C5DF `. `'`
  `-

Re: [RFS] -- ruby-google-api-client

[Pirate Praveen]

On Thu, Jan 12 2023 at 07:30:32 PM +05:30:00 +05:30:00, Vivek K J 
 wrote:

Hi Team,

I've added a patch in ruby-google-api-client to use latest 
version of ruby-googleauth gem (Which is in experimental). With the 
latest version, the package builds fine, and no errors were reported. 
This workaround will allow migrating ruby-googleauth from 
experimental to unstable (Closes: #1027047). In the newer versions, 
ruby-google-api-client doesn't have dependency on ruby-googleauth, 
but have dependency on a new gem google-apis-core (Which is also a 
dependency of gitlab). For packaging that gem, latest version 
ruby-googleauth needs to be in unstable. So in the future, we can 
safely remove that patch.


Why not upload ruby-google-apis-core to experimental? then you can 
upload the newer ruby-google-api-client to experimental and move all 
three packages together to unstable.


Also left a comment in salsa 
https://salsa.debian.org/ruby-team/ruby-google-api-client/-/commit/d767f08beadd78c0471d4818822c8fabe631590b#note_373436


Requesting for sponsorship / upload permissions.


https://salsa.debian.org/ruby-team/ruby-google-api-client


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027047

--
Regards,

Vivek K J
Debian Maintainer
---
 .''`.
Personal Website:  https://vivekkj.codes: :'  
:

GPG Key: D017 9263 E202 0E40 7157  4073 A5FF 4BB3 EA53 C5DF `. `'`
  `-

Re: RFS: ruby-fog-aws

[Pirate Praveen]

On 28/12/22 1:22 PM, Caleb Adepitan wrote:

Hello,

I just updated ruby-fog-aws from 3.14.0 to 3.15.0

Here is the repo that contains the changes made; 
https://salsa.debian.org/calebpitan/ruby-fog-aws


May be you forgot to push or the repo is private?


Cheers,

Caleb

Re: RFS: ruby-kaminari

[Pirate Praveen]

On 28/12/22 3:55 AM, Caleb Adepitan wrote:



On 12/27/22 21:53, Pirate Praveen wrote:


On 27/12/22 10:20 PM, Caleb Adepitan wrote:

Done


Please push the tags as well (upstream/1.2.2 tag is missing).


upstream/1.2.2 tag pushed



Uploaded, thanks for your contribution!







On 12/27/22 13:41, Pirate Praveen wrote:


On 27/12/22 3:47 PM, Caleb Adepitan wrote:

Hello,

I just updated ruby-kaminari from 1.2.1 to 1.2.2

Here is the repo that contains the changes made; 
https://salsa.debian.org/calebpitan/ruby-kaminari



Please change UNRELEASED in changelog.

Cheers,

Caleb

Re: RFS: ruby-kaminari

[Pirate Praveen]

On 27/12/22 10:20 PM, Caleb Adepitan wrote:

Done


Please push the tags as well (upstream/1.2.2 tag is missing).



On 12/27/22 13:41, Pirate Praveen wrote:


On 27/12/22 3:47 PM, Caleb Adepitan wrote:

Hello,

I just updated ruby-kaminari from 1.2.1 to 1.2.2

Here is the repo that contains the changes made; 
https://salsa.debian.org/calebpitan/ruby-kaminari



Please change UNRELEASED in changelog.

Cheers,

Caleb

Re: RFS: ruby-kaminari

[Pirate Praveen]

On 27/12/22 3:47 PM, Caleb Adepitan wrote:

Hello,

I just updated ruby-kaminari from 1.2.1 to 1.2.2

Here is the repo that contains the changes made; 
https://salsa.debian.org/calebpitan/ruby-kaminari



Please change UNRELEASED in changelog.

Cheers,

Caleb

Re: [RFS] -- ruby-googleauth 1.3.0

[Pirate Praveen]

On 26/12/22 8:59 PM, Vivek K J wrote:

Hi Team,

        I've updated ruby-googleauth package from 0.13.0 to 1.3.0. As 
its a major version upgrade, The following reverse(build) dependencies 
fails to rebuild against latest version.


grpc
grpc-java
ruby-google-api-client
ruby-google-cloud-translate

Among these, grpc and grpc-java is not failing because of this 
upgrade. For the remaining packages, I think, we can upload googleauth 
package to experimental and file bugs against individual packages. So 
requesting sponsorship for ruby-googleauth package. This package is 
updated for updating gitlab to 15.6.1 [1].
Thanks for your careful approach to a breaking change upload. I have 
uploaded, please file bugs against failing packages. If possible check 
if any new upstream versions of the failing packages are available. I 
think ruby-google-api-client is split into multiple gems, please check this.



ruby-googleauth -> ruby-google-apis-core -> gitlab


[1] -- https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191

Re: [RFS] telesign,request-store,view-component,fog-local,aws-sdk-s3,fogbugz

[Pirate Praveen]

On 23/12/22 7:04 PM, Vinay wrote:

Hello Team,
I have packaged the following new packages required for 15.6.1

1.  ruby-telesign 2.2.3 
https://salsa.debian.org/ruby-team/mentors/ruby-telesign


Moved repo to ruby-team and uploaded. Please upload to bullseye-* as well.


I have updated the packages to new upstream required for gitlab 15.6.1

1. ruby-request-store   1.5.0 -> 1.5.1 
https://salsa.debian.org/ruby-team/ruby-request-store



Uploaded. Please upload to bullseye-* as well.
2. ruby-view-component 2.74.0 -> 2.74.1 
https://salsa.debian.org/ruby-team/ruby-view-component

Uploaded. Please upload to bullseye-* as well.


3. ruby-fog-local 0.6.0 -> 0.8.0 
https://salsa.debian.org/ruby-team/ruby-fog-local
Please upload to experimental as it is a breaking change and will break 
gitlab 15.4 in experimental (until we upload gitlab 15.6). You can 
reupload this to unstable after gitlab 15.6 is uploaded to experimental.


4. ruby-aws-sdk-s3  1.114.0 ~> 1.117.1 
https://salsa.debian.org/ruby-team/ruby-aws-sdk-s3

Uploaded. Please upload to bullseye-* as well.


5. ruby-fogbugz   0.2.1 -> 0.3.0 
https://salsa.debian.org/ruby-team/ruby-fogbugz
Please upload to experimental as it is a breaking change and will break 
gitlab 15.4 in experimental (until we upload gitlab 15.6). You can 
reupload this to unstable after gitlab 15.6 is uploaded to experimental.



Reason for sending an RFS mail is that the packages are listed in this 
issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , so 
it will help in packaging gitlab 15.6.1.



Thank You
Vinay Keshava 

Re: [RFS] ruby-oj 3.13.23.2

[Pirate Praveen]

On 26/12/22 10:18 PM, Vinay wrote:



On 26/12/22 16:20, Pirate Praveen wrote:



On 24/12/22 11:37 PM, Vinay wrote:


Hello Team,
I have updated ruby-oj(3.13.23.1  -> 3.13.23.2 ) .The updated 
package is available at [0].



The versions here are 3.13.23-1  -> 3.13.23-2


ruby-oj (3.13.23 ) is required for the new gem of gitlab oj-introspect
<https://rubygems.org/gems/oj-introspect>

Reason for sending an RFS mail is that the package ruby-oj's header 
files were required by oj-introspect.


[0] https://salsa.debian.org/ruby-team/ruby-oj

Uploaded, thanks for your contribution! From next time, it is good to 
have changelog changes committed separately to easy branching and 
merging when backporting, fasttracking etc.


Okay will commit the changelog changes separately,but i also few 
changes to be done to d/rules again,as discussed here


https://lists.debian.org/debian-ruby/2022/12/msg00043.html
to install the headers in ruby specific directory instead of /usr/include

execute_before_dh_auto_install:
    for r in $$(ruby -rruby_debian_dev -e 'puts 
RubyDebianDev::SUPPORTED_RUBY_VERSIONS.values'); do \
    dh_install ext/oj/oj.h $$($$r -e 'puts 
RbConfig::CONFIG["vendorhdrdir"]'); \
    dh_install ext/oj/cache8.h $$($$r -e 'puts 
RbConfig::CONFIG["rubyhdrdir"]'); \
    dh_install ext/oj/rxclass.h $$($$r -e 'puts 
RbConfig::CONFIG["rubyhdrdir"]'); \
    dh_install ext/oj/parser.h $$($$r -e 'puts 
RbConfig::CONFIG["rubyhdrdir"]'); \
    dh_install ext/oj/buf.h $$($$r -e 'puts 
RbConfig::CONFIG["rubyhdrdir"]'); \
    dh_install ext/oj/usual.h $$($$r -e 'puts 
RbConfig::CONFIG["rubyhdrdir"]'); \

    done


Should it be as new changelog entry(3.13.23.3) or same entry 3.13.23.2


I have uploaded already, so it should be a new version (3.13.23-3 not 
3.13.23.3)

Re: [RFS] ruby-oj 3.13.23.2

[Pirate Praveen]

On 24/12/22 11:37 PM, Vinay wrote:


Hello Team,
I have updated ruby-oj(3.13.23.1  -> 3.13.23.2 ) .The updated package 
is available at [0].



The versions here are 3.13.23-1  -> 3.13.23-2


ruby-oj (3.13.23 ) is required for the new gem of gitlab oj-introspect


Reason for sending an RFS mail is that the package ruby-oj's header 
files were required by oj-introspect.


[0] https://salsa.debian.org/ruby-team/ruby-oj

Uploaded, thanks for your contribution! From next time, it is good to 
have changelog changes committed separately to easy branching and 
merging when backporting, fasttracking etc.




Thank You
Vinay Keshava  

Re: [RFS] -- ruby-signet

[Pirate Praveen]

On 23/12/22 7:13 PM, Vivek K J wrote:


On 23/12/22 18:49, Pirate Praveen wrote:


On 23/12/22 6:13 PM, Vivek K J wrote:

Hey team,


    I've updated ruby-signet to 0.17.0. I've verified the package is 
lintian clean and reverse dependencies are building perfectly. I'm a 
DM, but I don't have access to upload this updated package. This 
package is updated for updating gitlab to 15.6.1 [1].



Did you verify the upload to unstable don't break any reverse (build) 
dependencies? Please mention this point when uploading a breaking 
change.


Yes, I've verified and ensured that this update won't break any 
reverse dependencies in unstable.


(ruby-googleauth and ruby-google-api-client)


Good. Next time, for any breaking change, mention that in the RFS mail 
itself so we can avoid one back and forth.






ruby-signet -> ruby-googleauth -> ruby-google-apis-core -> gitlab

[1] -- 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191

Re: [RFS] -- ruby-signet

[Pirate Praveen]

On 23/12/22 6:13 PM, Vivek K J wrote:

Hey team,


    I've updated ruby-signet to 0.17.0. I've verified the package is 
lintian clean and reverse dependencies are building perfectly. I'm a 
DM, but I don't have access to upload this updated package. This 
package is updated for updating gitlab to 15.6.1 [1].



Did you verify the upload to unstable don't break any reverse (build) 
dependencies? Please mention this point when uploading a breaking change.




ruby-signet -> ruby-googleauth -> ruby-google-apis-core -> gitlab

[1] -- https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191

Re: [RFS] -- ruby-redis-namespace

[Pirate Praveen]

On ബു, ഡിസം 21 2022 at 07:01:52 വൈകു +05:30:00 
+05:30:00, Vivek K J  wrote:

Hey team,


I've updated ruby-redis-namespace to 1.9.0. I'm a DM, but I don't
have access to upload this updated package. This package is updated 
for

updating gitlab to 15.5.1 [1].



Uploaded, thanks for your contribution.



[1] -- 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191


--
Regards,

Vivek K J
Debian Maintainer
---
 .''`.
Personal Website:  https://vivekkj.codes: :'  
:

GPG Key: D017 9263 E202 0E40 7157  4073 A5FF 4BB3 EA53 C5DF `. `'`
  `-

Re: [RFS] ruby-oj 3.13.23

[Pirate Praveen]

On വ്യാ, ഡിസം 22 2022 at 12:52:28 രാവിലെ 
+05:30:00 +05:30:00, Vinay  wrote:

Hello Team,
 I have updated ruby-oj(3.13.21-> 3.13.23) .The updated package is 
available at [0].


ruby-oj (3.13.23 ) is required for the new gem of gitlab oj-introspect

could not push to https://salsa.debian.org/ruby-team/ruby-oj had no 
maintainer access, but have pushed to my fork [0]


Reason for sending an RFS mail is that the package ruby-oj is listed 
in this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.3.0.


 [0]  https://salsa.debian.org/vinay-keshava/ruby-oj


Uploaded, thanks for your contribution.



 Thank You
 Vinay Keshava 

Re: RFS: ruby-oauth2 2.0.6

[Pirate Praveen]

Hi Tunji,

Did you verify if the upload breaks any reverse dependencies in 
unstable?


$ reverse-depends ruby-oauth2
Reverse-Depends
* gitlab
* ruby-asana
* ruby-github-api
* ruby-omniauth-oauth2

Packages without architectures listed are reverse-dependencies in: all, 
amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x


$ reverse-depends -b ruby-oauth2
Reverse-Build-Depends
* ruby-asana
* ruby-github-api

For any breaking changes, we need to follow 
https://wiki.debian.org/Teams/Ruby/Packaging/#Updating_packages_with_API_breaking_changes

Re: [RFS] ruby-ipaddr , ruby-cvss-suite

[Pirate Praveen]

On Sat, Nov 12 2022 at 10:50:53 PM +05:30:00 +05:30:00, Vinay Keshava 
 wrote:

Hello Team,
I have packaged ruby-ipaddr and  ruby-cvss-suite

The package is available at [0] and [1]
Please review the packages and sponsor it.

Reason for sending an RFS mail is that the packages are listed in 
this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.5.1.


[0] https://salsa.debian.org/vinay-keshava/ruby-ipaddr

[1] https://salsa.debian.org/vinay-keshava/ruby-cvss-suite



Uploaded both, thanks for your contribution!

For ruby-cvss-suite, remove the full stop in short description for the 
next upload (after it is accepted).

Thank You
Vinay Keshava 

Re: [RFS] ruby-toml-rb , ruby-marginalia , ruby-rack-proxy

[Pirate Praveen]

On Sat, Nov 5 2022 at 05:51:32 PM +05:30:00 +05:30:00, Vinay Keshava 
 wrote:


On 31/10/22 17:14, Vinay Keshava wrote:

Hello Team,
I have updated ruby-toml-rb (2.1.0 -> 2.2.0) and ruby-marginalia 
(1.11.1 | 1.10.1) .The updated package is available at [0] and [1]
Reason for sending an RFS mail is that the package is listed in this 
issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.5.1.



I could not push to 
https://salsa.debian.org/ruby-team/ruby-marginalia because the 
branches were protected


should i remove it ?

remote: GitLab: You are not allowed to push code to protected 
branches on this project.

To salsa.debian.org:ruby-team/ruby-marginalia.git
 ! [remote rejected] master -> master (pre-receive hook declined)
 ! [remote rejected] pristine-tar -> pristine-tar (pre-receive hook 
declined)

 ! [remote rejected] upstream -> upstream (pre-receive hook declined)
 ! [remote rejected] upstream/1.11.1 -> upstream/1.11.1 (pre-receive 
hook declined)



[0] https://salsa.debian.org/ruby-team/ruby-toml-rb



Uploaded, thanks!


[1] https://salsa.debian.org/vinay-keshava/ruby-marginalia/


I have given you maintainer access for this repo and you should be able 
to push now. I have also pulled your changes and uploaded it.


I have also updated ruby-rack-proxy to 0.7.4
  [2] https://salsa.debian.org/ruby-team/ruby-rack-proxy


Did you verify if it breaks its reverse dependency ruby-webpacker?

In this specific case, it seems ruby-webpacker is already broken with 
ruby 3.1, so we can probably ignore it, but in future verify if 
breaking changes (as per semver.org) breaks other packages and follow 
https://wiki.debian.org/Teams/Ruby/Packaging/#Updating_packages_with_API_breaking_changes 
(give your reasoning why you think it is appropriate to upload it to 
unstable).


Additionally the dependency in ruby-webpacker seems very loose

 s.add_dependency "rack-proxy",">= 0.6.1"

I have uploaded it since ruby-webpacker is already broken and 
dependency is loose.

Re: RFS ruby-version-gem

[Pirate Praveen]

On Sat, Nov 5 2022 at 01:11:48 AM +01:00:00 +01:00:00, Ajayi Olatunji O 
 wrote:
Thank you Praveen, I have made the necessary changes as advised and 
the project still exist in the same repository, kindly checkout the 
work I have done.


Looks like you did a git push --force or recreated the repository. This 
time it is okay since we have not uploaded any version to archive yet, 
but be very careful when doing either of the two extreme actions next 
time.


I this case you only had to delete the tags.

Uploaded, thanks for your work!

Re: RFS ruby-version-gem

[Pirate Praveen]

On Mon, Oct 31 2022 at 06:16:02 PM +01:00:00 +01:00:00, Ajayi Olatunji 
O.  wrote:

Hey,

With the assistance of Vinay Keshava I was able to undo the issues 
with ruby-version-gem.


Kindly check it at   
https://salsa.debian.org/ruby-team/ruby-version-gem and help sponsor.




Please remove debian/1.1.1-1 tag, gbp import-dsc will add the tag, but 
we made further changes since the tag was created. So usually the 
person uploading the package creates the debian/version tag so all 
commits are included in the tag. Remember to do this for all newly 
created packages.




The package is required for gitlab 15.5.1.

Thank you.



From:Vinay Keshava
Sent:31 October 2022 17:15
To:Ajayi Olatunji O.
Cc:debian-ruby@lists.debian.org
Subject:Re: RFS ruby-version-gem





On 31/10/22 19:22, Ajayi Olatunji O. wrote:


Hi Vinay,

Thank you very much for helping out.

I have fixed the problem with the work on 
https://salsa.debian.org/ruby-team/ruby-version-gem.


Thank you very much for your work and your help.


Welcome (:




From:Vinay Keshava
Sent:31 October 2022 11:30
To:Ajayi Olatunji O.
Cc:debian-ruby@lists.debian.org
Subject:Re: RFS ruby-version-gem





On 31/10/22 15:52, Ajayi Olatunji O. wrote:


Hi Vinay,

Yeah I was having some issues regarding the implementation of the 
changes Praveen asked, and the problem is that the package looked 
okay when I pulled it to correct the errors Praveen mentioned, so I 
was quiet confused.


I tried to get help on the group chat but didn’t get any.

You can go on to get the sponsorship, but I’d appreciate if you 
could show me how you were able to fix the problem.


After fetching the gem and gem2deb'ed it , i did this gbp import-dsc 
--pristine-tar ruby-version-gem_1.1.1-1.dsc

and for each changes i did a separate commit.



Thank you.



From:Vinay Keshava
Sent:31 October 2022 11:14
To:Ajayi Olatunji O.
Cc:debian-ruby@lists.debian.org
Subject:Re: RFS ruby-version-gem





On 31/10/22 15:31, Ajayi Olatunji O. wrote:


Hi Vinay,

ruby-version-gem has already been packaged by me and is awaiting 
approval.



Hi Ajayi Olatunji O,

But the branch layout seems to wrong, there's only master branch 
,pristine-tar and upstream branches are missing


and all the changes have only one commit , praveen pointed it here 
https://lists.debian.org/debian-ruby/2022/10/msg1.html


You can make the appropriate changes



Thanks (:

Vinay




Thank you for your work.



From:Vinay Keshava
Sent:31 October 2022 09:45
To:debian-ruby@lists.debian.org
Subject:RFS ruby-version-gem



Hello Team,

I have packaged ruby-version-gem.

Reason for sending an RFS mail is that the package 
ruby-version-gem is


listed in this issue

https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 
, so


it will help in packaging gitlab 15.5.1.



https://lists.debian.org/debian-ruby/2022/10/msg1.html



the package was already packaged but the branch layout seems to be 
wrong


[1] so the updated repo is here [0]





[0]  https://salsa.debian.org/vinay-keshava/ruby-version-gem/

[1] https://salsa.debian.org/ruby-team/ruby-version-gem



Thank You

Vinay Keshava 

Re: [RFS] reuby-view-component 2.74.0

[Pirate Praveen]

On ശ, ഒക്ടോ 8 2022 at 12:30:13 വൈകു +05:30:00 
+05:30:00, Vinay Keshava  wrote:

Hello Team,
I have updated ruby-view-component (2.69.0 -> 2.74.0) .The updated 
package is available at [0].
Reason for sending an RFS mail is that the package ruby-diffy is 
listed in this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.4.0.


[0] https://salsa.debian.org/ruby-team/ruby-view-component


Uploaded, thanks for your contributions!

Re: [RFS] ruby-diffy 3.4.2

[Pirate Praveen]

On ശ, ഒക്ടോ 8 2022 at 08:56:36 രാവിലെ +05:30:00 
+05:30:00, Vinay Keshava  wrote:


On 08/10/22 02:05, Pirate Praveen wrote:



On വെ, ഒക്ടോ 7 2022 at 10:46:14 വൈകു +05:30:00 
+05:30:00, Vinay Keshava  wrote:

Hello Team,
I have updated ruby-diffy (3.3.0 -> 3.4.2) .The updated package is 
available at [0].
Reason for sending an RFS mail is that the package ruby-diffy is 
listed in this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 
, so it will help in packaging gitlab 15.4.0.


[0]  https://salsa.debian.org/ruby-team/ruby-diffy


Please merge the last two changelog entries, we don't keep 
UNRELEASED entries when uploading.

Updated it.


Uploaded, thanks for your contribution.

Re: [RFS] ruby-diffy 3.4.2

[Pirate Praveen]

On വെ, ഒക്ടോ 7 2022 at 10:46:14 വൈകു +05:30:00 
+05:30:00, Vinay Keshava  wrote:

Hello Team,
I have updated ruby-diffy (3.3.0 -> 3.4.2) .The updated package is 
available at [0].
Reason for sending an RFS mail is that the package ruby-diffy is 
listed in this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.4.0.


[0]  https://salsa.debian.org/ruby-team/ruby-diffy


Please merge the last two changelog entries, we don't keep UNRELEASED 
entries when uploading.

Re: RFS: ruby-version-gem 1.1.0

[Pirate Praveen]

On ബു, സെപ്റ്റം 21, 2022 at 4:54 വൈകു, 
Ajayi Olatunji O  wrote:

Hi,

In order to update git lab to version 15.3.0, ruby-oauth2 must be
updated from version 1.4.4 to version 2.0, and ruby-oauth requires a
ruby gem version-gem, but because of the absence of version-gem in the
Debian archive I had to package it for the ruby team.

It is currently at version 1.1.0 and the packaged gem exists at
https://salsa.debian.org/ruby-team/projects/ruby-version-gem.


Also the branch layout seems wrong. You have to use 'gbp import-dsc 
--pristine-tar' from the dsc file generated by gem2deb and commit all 
your logical changes separately. Currently it just have one branch and 
single commit for all changes.

Re: RFS: ruby-version-gem 1.1.0

[Pirate Praveen]

On ബു, സെപ്റ്റം 21, 2022 at 4:54 വൈകു, 
Ajayi Olatunji O  wrote:

Hi,

In order to update git lab to version 15.3.0, ruby-oauth2 must be
updated from version 1.4.4 to version 2.0, and ruby-oauth requires a
ruby gem version-gem, but because of the absence of version-gem in the
Debian archive I had to package it for the ruby team.

It is currently at version 1.1.0 and the packaged gem exists at
https://salsa.debian.org/ruby-team/projects/ruby-version-gem.



I have moved the repo to
https://salsa.debian.org/ruby-team/ruby-version-gem

projects sub group is for projects we are upstream.


Kindly help sponsor it, it is lintian clean.

In case there are any corrections, I am eager to implement them.


Thank you.

Re: [RFS] ruby-redis-actionpack

[Pirate Praveen]

On Fri, Sep 2 2022 at 12:19:49 AM +05:30:00 +05:30:00, Vinay Keshava 
 wrote:

Hello Team,
I have updated ruby-redis-actionpack (5.2.0 -> 5.3.0) .The updated 
package is available at [0].
Reason for sending an RFS mail is that the package 
ruby-redis-actionpack is listed in this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.3.0.


[0] https://salsa.debian.org/ruby-team/ruby-redis-actionpack/



Uploaded, thanks for your contribution.



Thank You
Vinay Keshava 

Re: [RFS] ruby-oj

[Pirate Praveen]

On Mon, Aug 29 2022 at 02:00:21 PM +05:30:00 +05:30:00, Vinay Keshava 
 wrote:

Hello Team,
I have updated ruby-oj(3.13.19 -> 3.13.21) .The updated package is 
available at [0].
Reason for sending an RFS mail is that the package ruby-oj is listed 
in this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.3.0.


[0]  https://salsa.debian.org/vinay-keshava/ruby-oj/



Uploaded, thanks for your contribution!

Re: [RFS] -- ruby-rails-i18n 7.0.5

[Pirate Praveen]

On Sun, Aug 28 2022 at 06:38:39 PM +05:30:00 +05:30:00, Vivek K J 
 wrote:

Hi Team,

I've updated the package ruby-rails-i18n from 6.0.0 to 7.0.5.
The package is lintian clean and the updated package is available at
https://salsa.debian.org/ruby-team/ruby-rails-i18n. This package have 
no

reverse build dependencies, so it is ready to upload to unstable. This
package is updated for gitlab 15.3.0.

Requesting for Sponsorship


Uploaded, thanks for your contribution!

Re: RFS: ruby-yajl 1.4.3

[Pirate Praveen]

On വ്യാ, ഓഗ 25, 2022 at 11:34 വൈകു, Ravi 
 wrote:

Hi,

The following packages are ready to be uploaded (I also verified the
points listed on 
http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship).


The reason I am sending this RFS mail is that the package 
ruby-fog-aws is listed in this issue 
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/191 , 
so it will help in packaging gitlab 15.3.0.


Could you please sponsor them?

  ruby-yajl 1.4.3 (it is at https://salsa.debian.org/ravi1/ruby-yajl)


Uploaded, thanks for your contribution!

Re: [RFS] ruby-truncato ,ruby-kubeclient

[Pirate Praveen]

On ബു, ഓഗ 24, 2022 at 12:56 രാവിലെ, Vinay Keshava 
 wrote:

Hello Team,
 updated ruby-truncato with changes available at

https://salsa.debian.org/vinay-keshava/ruby-truncato


Uploaded, both! thanks for your contribution.

Re: RFS: ruby-gpgme 2.0.20-1

[Pirate Praveen]

On ഞാ, ഓഗ 14, 2022 at 2:04 രാവിലെ, 'Tunji 
 wrote:
Hello, I made recommended changes to this package and it is now 
Lintian

clean.

I seek sponsorship for it to be uploaded to the archive.


Uploaded, thanks for your contribution!

Re: [RFS] -- ruby-grape-path-helpers 1.7.1

[Pirate Praveen]

On ബു, ഓഗ 24, 2022 at 7:00 വൈകു, Vivek K J 
 wrote:


On 24/08/22 18:19, Pirate Praveen wrote:



On ഞാ, ഓഗ 21, 2022 at 6:06 വൈകു, Vivek K J 
 wrote:

Hi Team,

I've updated ruby-grape-path-helpers package from 1.7.0 to 
1.7.1.

The updated package is available at
https://salsa.debian.org/ruby-team/ruby-grape-path-helpers. The 
package
is lintian clean and all reverse dependencies are building 
successfully.

Requesting For sponsorship.


The commit where you updated copyright is not correct. You cannot add
a newer year to my copyright notice. You can add a new entry with 
your

email for this year or ignore that message from lintian about
copyright year.



Fixed.

--- a/debian/copyright
+++ b/debian/copyright
@@ -7,7 +7,8 @@ Copyright: 2015 Harper Henn
 License: Expat

 Files: debian/*
-Copyright: 2018-2022 Pirate Praveen 
+Copyright: 2018 Pirate Praveen 
+  2022 Vivek K J 
 License: Expat


Uploaded, thanks for your contributions! Consider updating the version 
in fasttrack.debian.net as well.

Re: RFS: ruby-fog-aws 3.14.0

[Pirate Praveen]

On ബു, ഓഗ 24, 2022 at 1:59 രാവിലെ, Ravi 
 wrote:

Hi,

The following packages are ready to be uploaded (I also verified the
points listed on 
http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship).


Could you please sponsor them?

  ruby-fog-aws 3.14.0 (it is at 
https://salsa.debian.org/ravi1/ruby-fog-aws)


Uploaded! Welcome to ruby team and congrats on your first upload to 
debian!

Re: [RFS] -- ruby-grape-path-helpers 1.7.1

[Pirate Praveen]

On ഞാ, ഓഗ 21, 2022 at 6:06 വൈകു, Vivek K J 
 wrote:

Hi Team,

I've updated ruby-grape-path-helpers package from 1.7.0 to 1.7.1.
The updated package is available at
https://salsa.debian.org/ruby-team/ruby-grape-path-helpers. The 
package
is lintian clean and all reverse dependencies are building 
successfully.

Requesting For sponsorship.


The commit where you updated copyright is not correct. You cannot add a 
newer year to my copyright notice. You can add a new entry with your 
email for this year or ignore that message from lintian about copyright 
year.

Re: RFS: ruby-aws-sdk-s3 1.114.0-1, ruby-aws-eventstream 1.2.0-1, ruby-aws-sigv4 1.5.1-1

[Pirate Praveen]

On ശ, ഓഗ 20, 2022 at 8:52 വൈകു, 'Tunji 
 wrote:

Hi, thank you for informing me of the oversight.

Kindly check again, I have now pushed the packed to the right 
repository

(https://salsa.debian.org/thegodtune/ruby-aws-sigv4).



Uploaded both! Thanks for your contribution!

Next time try to look at the gemspec file for the actual minimum 
version to be added in control, aws-sdk-s3.gemspec has aws-sigv4 1.4 
and aws-sdk-core 1.127 as minimum versions (the package can be newer 
than that if not breaking change, but in control we can put the actual 
minimum version).

Re: RFS: ruby-aws-sdk-s3 1.114.0-1, ruby-aws-eventstream 1.2.0-1, ruby-aws-sigv4 1.5.1-1

[Pirate Praveen]

On ശ, ഓഗ 20, 2022 at 4:33 രാവിലെ, 'Tunji 
 wrote:

Hi,

I just updated the packages

ruby-aws-sdk-s3 from version 1.48.0-3 to 1.114.0-1,

ruby-aws-eventstream from version 1.1.0-1 to 1.2.0-1,

and ruby-aws-sigv4 from 1.1.0-3 to 1.5.1-1

Please note that ruby-aws-sdk-s3 requires ruby-aws-sigv4 1.5.1-1 and
ruby-aws-sdk-core 3.132.0-1 as it's build dependencies.
And ruby-aws-sdk-core has also been updated and bares a separate RFS.

Kindly check them out at

https://salsa.debian.org/thegodtune/ruby-aws-sdk-s3

https://salsa.debian.org/thegodtune/ruby-aws-eventstream

https://salsa.debian.org/thegodtune/ruby-aws-sigv4


I ensured that the packages are Lintian clean and changes are 
carefully

logged.

Kindly help sponsor them.

 ruby-aws-sdk-s3 1.114.0-1, ruby-aws-eventstream 1.2.0-1,
ruby-aws-sigv4 1.5.1-1



ruby-aws-eventstream was uploaded, but ruby-aws-sigv4 repo is not found 
in that url. May be you forgot to push?




Thank you!

Re: RFS: ruby-aws-sdk-core 3.132.0-1

[Pirate Praveen]

On ശ, ഓഗ 20, 2022 at 12:57 രാവിലെ, 'Tunji 
 wrote:

Hi,
I have updated the changelog as advised.

I still request sponsorship.



Uploaded, thanks for your contribution!


Thank you.

On 8/19/22 15:20, 'Tunji wrote:

Hi, I have implemented all the corrections stated, the package still
remains at https://salsa.debian.org/thegodtune/ruby-aws-sdk-core and 
I

still need sponsorship for it, thank you.

On 8/18/22 12:03, Pirate Praveen wrote:



On ബു, ഓഗ 17, 2022 at 7:03 വൈകു, 'Tunji
 wrote:

Hi,

I just updated the package ruby-aws-sdk-core from version 
3.104.3-3 to

3.132.0-1



Please update minimum versions of ruby-jmespath and ruby-beaneater 
in

Depends/Build-Depends. Also please doublecheck the line length of
changelog entries (lintian should have warned you about it).

Re: RFS: ruby-aws-sdk-core 3.132.0-1

[Pirate Praveen]

On ബു, ഓഗ 17, 2022 at 7:03 വൈകു, 'Tunji 
 wrote:

Hi,

I just updated the package ruby-aws-sdk-core from version 3.104.3-3 to
3.132.0-1



Please update minimum versions of ruby-jmespath and ruby-beaneater in 
Depends/Build-Depends. Also please doublecheck the line length of 
changelog entries (lintian should have warned you about it).

Re: RFS: ruby-jmespath 1.6.1-1, ruby-beaneater 1.1.1-1

[Pirate Praveen]

On ബു, ഓഗ 17, 2022 at 4:37 രാവിലെ, 'Tunji 
 wrote:

Hi,

I just updated the packages ruby-jmespath from version 1.4.0-3 to
1.6.1-1 and ruby-beaneater from version 1.0.0-2 to 1.1.1-1


Kindly check them out at
https://salsa.debian.org/thegodtune/ruby-jmespath and
https://salsa.debian.org/thegodtune/ruby-beaneater

I ensured that the packages are Lintian clean

Kindly help sponsor them.

ruby-jmespath 1.6.1-1, ruby-beaneater 1.1.1-1




Uploaded, thanks for your contribution!

In changelog you have,

* New upstream Release
* New upstream version 1.1.1

For future, keep only one of these.


Thank you!

Re: [RFS] -- ruby-graphql 2.10.0

[Pirate Praveen]

On Sun, Aug 14 2022 at 06:58:56 PM +05:30:00 +05:30:00, Vivek K J 
 wrote:

Updated to 1.13.15.

https://salsa.debian.org/ruby-team/ruby-graphql


Uploaded, thanks! Can you also update in bullseye-backports-staging too 
for gitlab in bullseye-fasttrack? See https://wiki.debian.org/FastTrack

Re: [RFS] -- ruby-graphql-client 0.18.0

[Pirate Praveen]

On Mon, Aug 15 2022 at 10:13:25 AM +05:30:00 +05:30:00, Vivek K J 
 wrote:


On 10/08/22 17:28, Pirate Praveen wrote:



On Mon, Aug 1 2022 at 05:58:53 PM +05:30:00 +05:30:00, Vivek K J
 wrote:

Hi Team,

I've updated the package ruby-graphql-client from 0.16.0 to
0.18.0. The package is lintian clean and the updated package is
available at 
https://salsa.debian.org/ruby-team/ruby-graphql-client. All

the reverse build dependencies are successfully built.

Requesting for Sponsorship


Gitlab 15.1.x needs only 0.17 (via graphlient 0.5) so I suggest to
update to 0.17 only or make sure the new version does not break
graphlient 0.5. Building fine is not necessarily enough if tests are
not enabled. Did you check if upstream tests are actually run?



The upstream doesn't provide any tests in their repo.



If you have not verified the update, which can include breaking changes 
as per semver.org, don't break a reverse dependency, it is safer to 
upload to experimental.



I wasn't able to build the package and there reverse build deps in a
sbuild environment due to this error:

```

dpkg: error processing archive
/tmp/apt-dpkg-install-dNHVwP/11-gcc-12_12.1.0-8_amd64.deb (--unpack):
 unable to make backup link of 
'./usr/lib/gcc/x86_64-linux-gnu/12/lto1'

before installing new version: No space left on device


This looks like your disk space is full.


dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../12-cpp-12_12.1.0-8_amd64.deb ...
Unpacking cpp-12 (12.1.0-8) over (12.1.0-7) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-dNHVwP/12-cpp-12_12.1.0-8_amd64.deb (--unpack):
 unable to make backup link of './usr/lib/gcc/x86_64-linux-gnu/12/cc1'
before installing new version: No space left on device

```


Anyway I've updated to 0.17.0 and pushed the changes. Please also 
enable

pipeline for the salsa repo.


Did you check if it breaks ruby-graphlient? If not it is safer to 
upload to experimental, as 0.x versions can include breaking changes as 
per semver.org.

Re: RFS: ruby-aes-key-wrap 1.1.0-1

[Pirate Praveen]

On Sat, Aug 13 2022 at 11:59:11 PM +01:00:00 +01:00:00, 'Tunji 
 wrote:

Hi, I have made all observed changes to this package and I am seeking
sponsorship.



Uploaded, thanks for your contributions!


thanks.

On 8/11/22 15:09, Pirate Praveen wrote:



On ഞാ, ഓഗ 7, 2022 at 2:44 രാവിലെ, 'Tunji
 wrote:

Hi,

I just updated the package ruby-aes-key-wrap from version 1.0.1-2 to
1.1.0-1


Kindly check it out at
https://salsa.debian.org/thegodtune/ruby-aes-key-wrap


Could you please sponsor it?

ruby-aes-key-wrap 1.1.0-1


Please make sure the package is lintian clean. There is long line in
changelog and you need Team Upload in changelog to fix
no-nmu-in-changelog warning.

Re: RFS: ruby-aws-partitions 1.618.0-1

[Pirate Praveen]

On Sun, Aug 14 2022 at 12:50:43 AM +01:00:00 +01:00:00, 'Tunji 
 wrote:

Hi,

I just updated the package ruby-aws-partitions from version 1.598.0-1 
to

1.618.0-1


Kindly check it out at
https://salsa.debian.org/thegodtune/ruby-aws-partitions

I ensured that the package is Lintian clean

Kindly help sponsor it.

ruby-aws-partitions 1.618.0-1



Uploaded, thanks for your contribution. See my small change in 
changelog.

Re: RFS: ruby-grape-logging 1.8.4-1

[Pirate Praveen]

On Fri, Aug 12 2022 at 11:39:07 PM +01:00:00 +01:00:00, 'Tunji 
 wrote:

Hello,


I just updated the package ruby-grape-logging from version 1.8.3-2  to
1.8.4-1


Kindly check it out at
https://salsa.debian.org/thegodtune/ruby-grape-logging

I ensured it is lintian clean.
Could you please sponsor it?

ruby-grape-logging 1.8.4-1


Uploaded, thanks for your contributions. See a small formatting change 
I did in changelog.

Re: RFS: ruby-aes-key-wrap 1.1.0-1

[Pirate Praveen]

On ഞാ, ഓഗ 7, 2022 at 2:44 രാവിലെ, 'Tunji 
 wrote:

Hi,

I just updated the package ruby-aes-key-wrap from version 1.0.1-2 to
1.1.0-1


Kindly check it out at
https://salsa.debian.org/thegodtune/ruby-aes-key-wrap


Could you please sponsor it?

ruby-aes-key-wrap 1.1.0-1


Please make sure the package is lintian clean. There is long line in 
changelog and you need Team Upload in changelog to fix 
no-nmu-in-changelog warning.

Re: RFS -- ruby-bootsnap 1.12.0

[Pirate Praveen]

On Thu, Aug 11 2022 at 06:05:34 PM +05:30:00 +05:30:00, Mohd Bilal 
 wrote:

Hello team,

I've updated ruby-bootsnap to 1.12.0. The package is lintian clean and
was successfully built using sbuild.

Requesting someone to review and sponsor my changes or you may 
consider

granting me DM access for the same.


You have DM access for this package now, wait for the confirmation mail 
before uploading. Thanks.

Re: [RFS] -- ruby-graphql-client 0.18.0

[Pirate Praveen]

On Mon, Aug 1 2022 at 05:58:53 PM +05:30:00 +05:30:00, Vivek K J 
 wrote:

Hi Team,

I've updated the package ruby-graphql-client from 0.16.0 to
0.18.0. The package is lintian clean and the updated package is
available at https://salsa.debian.org/ruby-team/ruby-graphql-client. 
All

the reverse build dependencies are successfully built.

Requesting for Sponsorship


Gitlab 15.1.x needs only 0.17 (via graphlient 0.5) so I suggest to 
update to 0.17 only or make sure the new version does not break 
graphlient 0.5. Building fine is not necessarily enough if tests are 
not enabled. Did you check if upstream tests are actually run?

Re: [RFS] -- ruby-graphql 2.10.0

[Pirate Praveen]

On Mon, Aug 1 2022 at 05:35:14 PM +05:30:00 +05:30:00, Vivek K J 
 wrote:

Hi Team,

I've updated the package ruby-grahql from 1.11.10 to 2.10.0.
The package is lintian clean and the updated package is available at
https://salsa.debian.org/ruby-team/ruby-graphql . While building 
reverse

build deps against updated version, some of the packages are failing.
The failing packages are :


ruby-batch-loader  rebuild
ruby-graphql-clientrebuild
ruby-graphql-errorsrebuild


among these ruby-graphql-client can be fixed by updating the package.

ruby-graphql-errors is a deprecated gem in favor of the new
GraphQL::Execution::Errors in the graphql gem.


Requesting for Sponsorship


Hi Vivek,

Gitlab Gemfile declare a dependency on grpahql 1.13.12 only. So I don't 
think it is a good idea to do a major update right now. We can't always 
update to a major version before all reverse dependencies are ported to 
work with the new version. So please update to the latest version in 
1.x series only till gitlab is updated to work with the new major 
version.


Thanks
Praveen

Re: [RFS] -- ruby-gitlab-fog-azure-rm 1.3.0

[Pirate Praveen]

On Mon, Aug 1 2022 at 07:29:38 PM +05:30:00 +05:30:00, Vivek K J 
 wrote:

Hi Team,

I've updated the package ruby-gitlab-fog-azure-rm  from 1.2.0
to 1.3.0. The package is lintian clean and the updated package is
available at
https://salsa.debian.org/ruby-team/ruby-gitlab-fog-azure-rm/. No 
reverse

dependencies for this package.


Requesting For Sponsorship


Uploaded, thanks for your contribution. It'd be nice if you can update 
the version in bullseye-backports too.


See 
https://salsa.debian.org/ruby-team/gitlab/-/wikis/bullseye-backports 
for steps.

Re: RFS: ruby-ipynbdiff 0.4.7-1

[Pirate Praveen]

On തി, 2022-07-04 at 00:04 +0200, Antoine Le Gonidec wrote:
> Hi,
> 
> I prepared an update of ipynbdiff Ruby gem from 0.4.6 to 0.4.7, as
> required for GitLab update to 15.0.4.
> The update is ready to be pulled from my fork on Salsa:
> https://salsa.debian.org/vv221/ruby-ipynbdiff
> 
> The package builds cleanly with pbuilder, and GitLab CI tests seem to
> be OK. I only did a basic update from upstream, no change has been
> done to Debian patches or any other Debian metadata (outside of
> debian/changelog).
> 
> Please tell me if anything seems to be missing (by e-mail or on IRC).

Uploaded, thanks for your work.

Re: Clarification for package naming policy

[Pirate Praveen]

On ചൊ, ജൂലൈ 12, 2022 at 7:40 വൈകു, Marc Dequènes 
(duck)  wrote:

Quack,

(sorry for the big lag)

On 2022-05-27 01:39, Daniel Leidert wrote:


What about a

Provides: ruby-deckar01-task-list

?


It already does that but apt search does not look at this field, so I 
did not find it.


Ideally apt should look in Provides too. In javascript team, use of 
Provides is very common. So I tend to use apt-file find often.


$ apt-file find deckar01
ruby-task-list: /usr/share/nodejs/deckar01-task_list/dist/task_list.js
ruby-task-list: /usr/share/nodejs/deckar01-task_list/package.json
ruby-task-list: 
/usr/share/rubygems-integration/all/specifications/deckar01-task_list-2.3.1gemspec


Also aptitude show can list Provides

$ aptitude show ruby-deckar01-task-list
No candidate version found for ruby-deckar01-task-list
Package: ruby-deckar01-task-list
State: not a real package
Provided by: ruby-task-list (2.3.1-1)

I know these are not ideal, but it works now.

So now I guess I need to remove this new package but I still disagree 
with the naming and I'm slightly fed up to have done this work for 
nothing.
I wanted to raise the problem so that we do not hit such problem 
again, especially if the original project happens to continue and 
diverge, but it does not seem to bring much attention.


I think it should be case by case, sometimes there is only a single 
reverse dependency as in this case and going via NEW when Provides can 
actually solve the problem is a barrier as NEW queue takes an 
unpredicatable amount of time and license review has already happened 
once.



Well, thanks for your reply Daniel.

Re: Gitlab packaging project funding status changed.

[Pirate Praveen]

On ചൊ, ജൂൺ 28 2022 at 06:13:32 വൈകു +00:00:00 
+00:00:00, Georg Faerber  wrote:

Hi,

On 22-06-28 18:37:27, Pirate Praveen wrote:

 <https://opencollective.com/debian-gitlab>


tells:

[...]
Gitlab Inc sponsored work on this project for 6+ years until recently.
Now we are looking for the community to support it

Did GitLab Inc. announce in public that they're not sponsoring this 
work

anymore? Besides, what's the reasoning of this decision, if any?



The sponsorship / payment was always through direct email 
communication. Initially it was just me and later Sruthi and Abhijith 
joined and we created a partnership firm just for this - 
https://untang.tech (also triggered by concerns from backports admins 
since it was a single person handling a large number of backports 
uploads, though since then, the number of uploads to backports reduced, 
and more uploads are not only in fasttrack.debian.net).


Before starting gitlab, I did a crowd funding of diaspora 
https://www.indiegogo.com/projects/make-diaspora-installation-one-step-on-debian#/ 
after this I asked if Gitlab Inc if they can fund half of the amount if 
I do a crowd funding. They said they can fund full and they kept 
funding until now from that point.


They said budget constraints, may be their priorities changed.


Thanks,
Georg

Re: Gitlab packaging project funding status changed.

[Pirate Praveen]

We have started an Open Collective to ask Free Software community to 
donate to continue maintaining gitlab and dependencies.




Spread the word.

coffeescript 2, rails, sprockets, and execjs

[Pirate Praveen]

Hi,

Recent major update of coffeescript broke rails build and now I'm stuck 
with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013218


coffeescript 2 produces ES6 by default but execjs don't support ES6 yet.

I tried with newer sprockets, but it seems not enough. In the short 
term, may be using babel to transpile to ES5 is the way forward.


Any help with fixing this is welcome.

Thanks
Praveen

Re: RFS: ruby-rack-proxy 0.7.2-1+nmu1

[Pirate Praveen]

On വ്യാ, ജൂൺ 16 2022 at 04:48:09 വൈകു +0200 
+0200, Antoine Le Gonidec  wrote:

Hi!

I’m willing to help with the packaging of Ruby gems required for 
packaging GitLab for Debian, so here is my first contribution.




thanks for your interest and happy to see the first contribution.

I’m providing the update as two distinct merge requests on Salsa:
- 
 
targets the "upstream" branch
- 
 
targets the "master" branch




You can just share the fork url as merging more branches is more work 
and for testing, we have to pull from your fork anyway.


Following the guidelines from 
, 
I checked that the package builds cleanly with pbuilder. In addition 
to the update to the current upstream release, I fixed a couple 
lintian warnings (not all of them, but I checked that I did not add 
any new warning). Everything on Salsa CI is green.


Since this is my first contribution to the Ruby team, feel free to 
report anything that I might have done wrong or in an unusual way. I 
have very little experience with Debian packaging (and none at all 
with Ruby gems), so I might have missed things that could seem 
obvious.


If everything seems OK, I would like to get a sponsor for:
ruby-rack-proxy 0.7.2-1+nmu1


You can keep note of the suggestions shared in irc. I have uploaded it. 
Thanks for your contribution.


I tested ruby-webpacker using ruby-team/meta on salsa scripts and it 
looks good. so we can reupload to unstable when this version of gitlab 
is uploaded.


I recommend using build script from meta repo and running tests for 
reverse dependencies, especially for potentially breaking changes 
(using semver.org as a baseline).




Thanks you!

Gitlab packaging project funding status changed.

[Pirate Praveen]

Hi Ruby team,

A bit of disappointing news: Gitlab Inc is stopping their funding for the 
packaging work. So we will have to find other sources of funding or reduce the 
scope of the Debian Packaging project (we will have to depend on rubygems.org 
more and stop updating ruby dependencies) or find more volunteers. So my 
involvement in ruby team might be lesser than what it used to be with funding.

Thanks
Praveen
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [RFS] -- ruby-omniauth-alicloud

[Pirate Praveen]

On തി, ജൂൺ 6 2022 at 06:41:28 വൈകു +05:30:00 
+05:30:00, Vivek K J  wrote:

Hi Team,

I've packed ruby-omniauth-alicloud which is a dependency of gitlab
package. The package is available at mentors repository (https://
salsa.debian.org/ruby-team/mentors/ruby-omniauth-alicloud ).



Please make sure your package builds fine in a clean chroot (for 
example using sbuild).


See git-in-gemspecs.patch in ruby-httparty package.


Regards,

Vivek K J

Re: Proposing to replace ruby-uglifier with ruby-terser and remove ruby-uglifier

[Pirate Praveen]

On ബു, ജൂൺ 1 2022 at 07:32:00 വൈകു +05:30:00 
+05:30:00, Pirate Praveen  wrote:

Looks like upstreams moved already
https://github.com/rails/sprockets/pull/713
https://github.com/rails/rails/blob/main/Gemfile#L33


$ reverse-depends -b ruby-uglifier
Reverse-Build-Depends
* open-build-service

$ reverse-depends ruby-uglifier
Reverse-Depends
* diaspora
* gitlab
* obs-api

diaspora and gitlab I plan to fix (gitlab is fixed already in 
experimental but will take time for a reupload to unstable).


Last unstable upload of open-build-service/obs-api is 2020-04-13 and 
already has two unfixed rc bugs and a request for help 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984462


If maintaining all ruby gem dependencies is the main problem, then may 
be a mixed approach of using unpackaged gems from rubygems.org and 
moving to contrib section could work.


You can see https://salsa.debian.org/ruby-team/pupilfirst as example of 
this approach (this would not require a lot of ruby specific knowledge).

https://salsa.debian.org/ruby-team/pupilfirst/-/blob/master/debian/postinst#L87

You just need to set GEM_HOME and GEM_PATH variables for bundler to 
install unpackaged gems.

Re: new restriction in rubygems: installing symlink pointing to parent path not allowed - causes ruby-handlebars-assets to ftbfs

[Pirate Praveen]

On വ്യാ, ജൂൺ 2 2022 at 08:58:37 വൈകു -03:00:00 
-03:00:00, Antonio Terceiro  wrote:

On Thu, Jun 02, 2022 at 06:03:47PM -0300, Lucas Kanashiro wrote:

 Em 01/06/2022 15:42, Pirate Praveen escreveu:
 > On Sun, 13 Feb 2022 08:59:18 +0100 Lucas Nussbaum 


 > wrote:
 > > During a rebuild of all packages in sid, your package failed to 
build

 > > on amd64.
 > >
 > >
 > > Relevant part (hopefully):
 > > > make[1]: Entering directory '/<>'
 > > > mkdir -p vendor/assets/javascripts
 > > > ln -s /usr/share/javascript/handlebars/handlebars.js
 > vendor/assets/javascripts/handlebars.js
 > > > ln -s
 > /usr/share/javascript/handlebars.runtime/handlebars.runtime.js
 > vendor/assets/javascripts/handlebars.runtime.js
 >
 > [...]
 >
 > > > Failed to load /dev/null because it doesn't contain valid 
YAML hash

 > > > ERROR:  While executing gem ... (Gem::Package::SymlinkError)
 > > > installing symlink 
'vendor/assets/javascripts/handlebars.js'
 > pointing to parent path 
/usr/share/javascript/handlebars/handlebars.js

 > of
 > 
/<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8

 > is not allowed
 >
 > How do we handle this issue? Should we copy instead? If that is 
the
 > solution, we will have to rebuild ruby package whenever the js 
package

 > changes. Can we modify rubygems to allow this link?


Can you try creating the symlink *after* rubygems has done its thing?
i.e. instead of creating the link in the source tree, create it at the
installation directory, after the installation has been done.


We won't be able to run the tests. If I comment out the ln commands, 
tests fail with


Errno::ENOENT: No such file or directory @ rb_sysopen - 
vendor/assets/javascripts/handlebars.js


May be we can copy during build and replace it by symlink in install?



 I believe this behavior was introduced by this rubygems upstream 
commit:


 
https://github.com/rubygems/rubygems/commit/555692b8deb8f6b27ce29b843dc59384d508e8c1


 One thing we could try is to revert it, but maybe we should try to
 create a good and convincing user story to file an upstream bug and 
get

 it fixed there.


This could be a flag to disable this check that gem2deb could use. I
don't know if that's simpler than working around the issue as I 
suggest

above (not tested, so not sure it works yet).

new restriction in rubygems: installing symlink pointing to parent path not allowed - causes ruby-handlebars-assets to ftbfs

[Pirate Praveen]

On Sun, 13 Feb 2022 08:59:18 +0100 Lucas Nussbaum  
wrote:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > mkdir -p vendor/assets/javascripts
> > ln -s /usr/share/javascript/handlebars/handlebars.js 
vendor/assets/javascripts/handlebars.js
> > ln -s 
/usr/share/javascript/handlebars.runtime/handlebars.runtime.js 
vendor/assets/javascripts/handlebars.runtime.js


[...]

> > Failed to load /dev/null because it doesn't contain valid YAML hash
> > ERROR:  While executing gem ... (Gem::Package::SymlinkError)
> > installing symlink 'vendor/assets/javascripts/handlebars.js' 
pointing to parent path /usr/share/javascript/handlebars/handlebars.js 
of 
/<>/debian/ruby-handlebars-assets/usr/share/rubygems-integration/all/gems/handlebars_assets-0.23.8 
is not allowed


How do we handle this issue? Should we copy instead? If that is the 
solution, we will have to rebuild ruby package whenever the js package 
changes. Can we modify rubygems to allow this link?

Re: Proposing to replace ruby-uglifier with ruby-terser and remove ruby-uglifier

[Pirate Praveen]

On ബു, ജൂൺ 1 2022 at 07:25:14 വൈകു +05:30:00 
+05:30:00, Pirate Praveen  wrote:

* rails (for ruby-uglifier)



I'm uploading a fix.


Looks like upstreams moved already
https://github.com/rails/sprockets/pull/713
https://github.com/rails/rails/blob/main/Gemfile#L33

Re: Proposing to replace ruby-uglifier with ruby-terser and remove ruby-uglifier

[Pirate Praveen]

On ബു, ജൂൺ 1 2022 at 06:21:34 വൈകു +05:30:00 
+05:30:00, Utkarsh Gupta  wrote:

$ reverse-depends src:ruby-uglifier
Reverse-Recommends
* nanoc (for ruby-uglifier)



This needs update.


Reverse-Depends
* diaspora  (for ruby-uglifier)
* gitlab(for ruby-uglifier)


already switched upstream. gitlab is fixed in experimental and need 
grpc/protobuf reuploads in unstable before it can be reuploaded. 
diaspora package is in my low priority list.



* obs-api   (for ruby-uglifier)


This seems abandoned in debian.


* rails (for ruby-uglifier)



I'm uploading a fix.


Packages without architectures listed are reverse-dependencies in:
all, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el,
s390x

$ reverse-depends -b src:ruby-uglifier
Reverse-Build-Depends
* nanoc (for ruby-uglifier)
* open-build-service(for ruby-uglifier)
* rails (for ruby-uglifier)


see above.


* ruby-sprockets(for ruby-uglifier)
* ruby-sprockets-rails  (for ruby-uglifier)



These two I will have a look soon.


As long as nothing breaks here and the transition from ruby-uglifier
to ruby-terser is smooth, it's all good. Whilst at it, you might also
want to open respective upstream issues so that we don't carry this
delta forever.


from gitlab and diaspora updates, it looks like a drop in replacement.

Proposing to replace ruby-uglifier with ruby-terser and remove ruby-uglifier

[Pirate Praveen]

We have a long standing rc bug (we have not updated to latest upstream for long)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981224#10

Also it caused autopkgtest regression for node-source-map update 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-uglifier/22232351/log.gz

terser is better maintained fork of uglify-js and ruby-terser its gem 
equivalent.

Anyone wants to keep maintaining ruby-uglifier ?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Proposal to remove ruby-rack-mount from the archive

[Pirate Praveen]

Hi,

ruby-rack-mount had last upstream release in 2011 and its only reverse 
build dependency was ruby-addressable which did not use it anymore (I 
update the package to remove this build dependency). There is 
autopkgtest regression with ruby-rack 2.2.3 so if anyone is still 
interested to keep this package, please fix the regression. If no one 
is interested, I propose we remove this package.


Thanks
Praveen

Re: Change in bundler behaviour for gems installed in vendor_ruby directory?

[Pirate Praveen]

On ഞാ, ജനു 23 2022 at 08:09:19 വൈകു +0100 +0100, 
Daniel Leidert  wrote:

Am Sonntag, dem 23.01.2022 um 14:31 -0300 schrieb Antonio Terceiro:

 On Sun, Jan 23, 2022 at 03:18:36PM +0530, Pirate Praveen wrote:
 > On ഞാ, ജനു 23 2022 at 08:20:38 രാവിലെ +0100 
+0100, Cédric Boutillier

 >  wrote:
 > > Hi Praveen,
 > >
 > > Thanks for all the converted packages!
 > >
 >
 > So many packages just for gitaly, and I think gitlab will have 
even more
 > packages to convert. So more hands to convert the remaining ones 
welcome. I

 > will share the list of gitlab dependencies later.

 I'm not sure "just converting" everything in a hurry is a good way 
of
 going about this.  Even though we do want to standardize on that 
layout
 at some point, maybe we should wait a little bit for a fix in 
rubygems.


But could we make it the default? Maybe with the current 
debhelper-compat
level? Then we don't have to write the "magic" lines in d/rules every 
time we

touch a package. What do you think?


It will break packages with patches which assumes the older layout. May 
be only fixing those after making this default is easier. Btw many 
recently created packages have it already as default so only a subset 
of all the packages we touch will need this change (not all packages).

Re: Change in bundler behaviour for gems installed in vendor_ruby directory?

[Pirate Praveen]

On ഞാ, ജനു 23 2022 at 02:31:29 വൈകു -0300 -0300, 
Antonio Terceiro  wrote:

On Sun, Jan 23, 2022 at 03:18:36PM +0530, Pirate Praveen wrote:
 On ഞാ, ജനു 23 2022 at 08:20:38 രാവിലെ +0100 
+0100, Cédric Boutillier

  wrote:
 > Hi Praveen,
 >
 > Thanks for all the converted packages!
 >

 So many packages just for gitaly, and I think gitlab will have even 
more
 packages to convert. So more hands to convert the remaining ones 
welcome. I

 will share the list of gitlab dependencies later.


I'm not sure "just converting" everything in a hurry is a good way of
going about this.  Even though we do want to standardize on that 
layout
at some point, maybe we should wait a little bit for a fix in 
rubygems.


Since this was blocking clean build of gitaly, I converted all build 
deps of gitaly for now. I will slow down for gitlab dependencies since 
I can hold ruby-bundler on an older version till this is fixed.

Re: Change in bundler behaviour for gems installed in vendor_ruby directory?

[Pirate Praveen]

On ഞാ, ജനു 23 2022 at 03:18:36 വൈകു +0530 +0530, 
Pirate Praveen  wrote:



On ഞാ, ജനു 23 2022 at 08:20:38 രാവിലെ +0100 
+0100, Cédric Boutillier  wrote:

Hi Praveen,

Thanks for all the converted packages!



So many packages just for gitaly, and I think gitlab will have even 
more packages to convert. So more hands to convert the remaining ones 
welcome. I will share the list of gitlab dependencies later.


So around 87 packages (may be more indirect dependencies we will see 
once we fix these)


List is here, most of the time it is a one line fix, but sometimes we 
have to fix some problems.


https://pad.riseup.net/p/bundle-local-gem-install-transition-keep

Just pick any gem from the list and move it to IN PROGRESS section and 
fix. Once completed, move it to DONE.

Re: Change in bundler behaviour for gems installed in vendor_ruby directory?

[Pirate Praveen]

On ഞാ, ജനു 23 2022 at 08:20:38 രാവിലെ +0100 
+0100, Cédric Boutillier  wrote:

Hi Praveen,

Thanks for all the converted packages!



So many packages just for gitaly, and I think gitlab will have even 
more packages to convert. So more hands to convert the remaining ones 
welcome. I will share the list of gitlab dependencies later.



 ruby-stringex introduces an autopkgtest regression when switching to
 gem-install layout. I could not figure out why from the error 
messages.

 Can someone check the salsa repo?


I have checked ruby-stringex and could fix the autotests by adding
locales/* to DH_RUBY_GEM_INSTALL_INCLUDE in debian/rules, and removing
overrides of dh_auto_{build,clean} which was used to move them around 
in

the old layout, and dropped the corresponding patch.

I have uploaded your package with my change on top of it.



Thanks, I also figured it out and tried to upload it without seeing 
your upload.



Best wishes,

Cédric

Re: Change in bundler behaviour for gems installed in vendor_ruby directory?

[Pirate Praveen]

On ശ, ജനു 22 2022 at 06:11:08 വൈകു +0530 +0530, Pirate 
Praveen  wrote:



On ശ, ജനു 22 2022 at 04:33:05 വൈകു +0530 +0530, 
Pirate Praveen  wrote:

Hi,

I noticed gitaly is failing to build now as bundle install --local 
is failing to find locally installed gems. It is trying to install 
some gems now which are not using the gem-install layout. Is this 
expected? Then we will have to update all gems using old layout to 
use the new gem-install layout.


After switching ruby-zeitwerk to gem-install layout, bundler can find 
this gem now, there are more gems to fix.


Any help in fixing these welcome.


I fixed many packages, the remaining ones

Installing rack 2.1.4
Installing dotenv 2.4.0
Installing charlock_holmes 0.7.7
Installing escape_utils 1.2.1
Installing multipart-post 2.0.0
Installing mini_mime 1.1.1
Installing github-markup 1.7.0
Installing stringex 2.8.5
Installing addressable 2.8.0
Installing rails-dom-testing 2.0.3

ruby-stringex introduces an autopkgtest regression when switching to 
gem-install layout. I could not figure out why from the error messages. 
Can someone check the salsa repo?

Re: Change in bundler behaviour for gems installed in vendor_ruby directory?

[Pirate Praveen]

On ശ, ജനു 22 2022 at 04:33:05 വൈകു +0530 +0530, Pirate 
Praveen  wrote:

Hi,

I noticed gitaly is failing to build now as bundle install --local is 
failing to find locally installed gems. It is trying to install some 
gems now which are not using the gem-install layout. Is this 
expected? Then we will have to update all gems using old layout to 
use the new gem-install layout.


After switching ruby-zeitwerk to gem-install layout, bundler can find 
this gem now, there are more gems to fix.


Any help in fixing these welcome.

Installing concurrent-ruby 1.1.6
Installing minitest 5.13.0
Installing zeitwerk 2.4.2
Installing erubi 1.9.0
Installing crass 1.0.2
Installing rack 2.2.3
Installing dotenv 2.4.0
Installing charlock_holmes 0.7.7
Installing multipart-post 2.0.0
Installing escape_utils 1.2.1
Installing mini_mime 1.1.1
Installing github-markup 1.7.0
Installing mime-types-data 3.2015.1120
Installing stringex 2.8.5
Installing opentracing 0.5.0
Installing thrift 0.14.0
Installing rubyzip 2.3.0
Installing tomlrb 1.3.0
Installing xml-simple 1.1.5
Installing msgpack 1.4.2

Change in bundler behaviour for gems installed in vendor_ruby directory?

[Pirate Praveen]

Hi,

I noticed gitaly is failing to build now as bundle install --local is 
failing to find locally installed gems. It is trying to install some 
gems now which are not using the gem-install layout. Is this expected? 
Then we will have to update all gems using old layout to use the new 
gem-install layout.


# Test if ruby dependencies are satisfied
TMPDIR=$(mktemp -d); cp ruby/Gemfile $TMPDIR; cd $TMPDIR;\
   RAILS_ENV=development bundle install --local || exit 1;\
   rm $TMPDIR/Gemfile* $TMPDIR/.bundle/config;\
   rmdir $TMPDIR/config; rmdir $TMPDIR
`/sbuild-nonexistent` is not a directory.
Bundler will use `/tmp/bundler20220122-94087-1o9vyh594087' as your home 
directory temporarily.

Resolving dependencies...
Installing concurrent-ruby 1.1.6
Installing minitest 5.13.0
Using builder 3.2.4
Installing zeitwerk 2.4.2
Installing erubi 1.9.0
Using racc 1.4.16
Installing crass 1.0.2
Installing rack 2.2.3
Using public_suffix 4.0.6
Using bundler 2.3.5
Installing dotenv 2.4.0
Installing charlock_holmes 0.7.7
Installing multipart-post 2.0.0
Installing escape_utils 1.2.1
Using ruby2_keywords 0.0.5
Using ffi 1.15.4
Using json 2.3.0
Installing mini_mime 1.1.1
Using rugged 1.2.0
Installing github-markup 1.7.0
Installing mime-types-data 3.2015.1120
Using rouge 3.26.1
Installing stringex 2.8.5
Using google-protobuf 3.19.3
Installing opentracing 0.5.0
Installing thrift 0.14.0
Installing rubyzip 2.3.0
Using redis 4.5.1
Using thor 1.0.1
Installing tomlrb 1.3.0
Using with_env 1.1.0
Using grpc-tools 1.30.2
Installing xml-simple 1.1.5
Using rdoc 6.2.1.1
Installing msgpack 1.4.2
Using optimist 3.0.0
Using nokogiri 1.11.7
Bundler::GemNotFound: Could not find concurrent-ruby-1.1.6.gem for 
installation

/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/source/rubygems.rb:181:in
`install'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/gem_installer.rb:54:in
`install'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/gem_installer.rb:16:in
`install_from_spec'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/parallel_installer.rb:186:in
`do_install'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/parallel_installer.rb:177:in
`block in worker_pool'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:62:in
`apply_func'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:57:in
`block in process_queue'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:54:in
`loop'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:54:in
`process_queue'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:91:in
`block (2 levels) in create_threads'

An error occurred while installing concurrent-ruby (1.1.6), and Bundler 
cannot

continue.

In Gemfile:
 gitlab-labkit was resolved to 0.21.2, which depends on
   actionpack was resolved to 6.1.4.1, which depends on
 actionview was resolved to 6.1.4.1, which depends on
   rails-dom-testing was resolved to 2.0.3, which depends on
 activesupport was resolved to 6.1.4.1, which depends on
   i18n was resolved to 1.8.11, which depends on
 concurrent-ruby


Bundler::GemNotFound: Could not find zeitwerk-2.4.2.gem for installation
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/source/rubygems.rb:181:in
`install'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/gem_installer.rb:54:in
`install'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/gem_installer.rb:16:in
`install_from_spec'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/parallel_installer.rb:186:in
`do_install'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/installer/parallel_installer.rb:177:in
`block in worker_pool'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:62:in
`apply_func'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:57:in
`block in process_queue'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:54:in
`loop'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:54:in
`process_queue'
/usr/share/rubygems-integration/all/gems/bundler-2.3.5/lib/bundler/worker.rb:91:in
`block (2 levels) in create_threads'

An error occurred while installing zeitwerk (2.4.2), and Bundler cannot
continue.

In Gemfile:
 gitlab-labkit was resolved to 0.21.2, which depends on
   actionpack was resolved to 6.1.4.1, which depends on
 actionview was resolved to 6.1.4.1, which depends on
   rails-dom-testing was resolved to 2.0.3, which depends on
 activesupport was resolved to 6.1.4.1, which depends on
   zeitwerk
make[1]: *** [debian/rules:53: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: ***