salsa.d.o/ruby-team: please bump my access level

Dear team, I would like to change the settings of some of the packages I'm maintaining, ruby-mail-gpg for example, to modify the location of the GitLab CI config. However, currently, I'm unable to do so, due to my "Developer" level. Accordingly, could someone bump this please? "Maintainer"

Re: salsa.d.o/ruby-team: please bump my access level

Hi all, On 19-07-21 15:08:00, Georg Faerber wrote: > I would like to change the settings of some of the packages I'm > maintaining, ruby-mail-gpg for example, to modify the location of the > GitLab CI config. However, currently, I'm unable to do so, due to my > "Developer" l

Re: RFS: ruby-tty-screen, ruby-tty-reader and ruby-tty-prompt

Hi, On 20-02-13 02:49:38, Gabriel Filion wrote: > Could someone please review my work to make sure I haven't done > something wrong or forgotten details? I made some changes, see git for details, all uploaded to NEW. Thanks for pushing pdk! Cheers, Georg

Re: debian/salsa-ci.yml created by gem2deb [was: Re: RFS: ruby-wisper and ruby-necromancer]

On 20-02-11 19:12:45, Utkarsh Gupta wrote: > When packaging a new gem, using gem2deb doesn't create a > debian/salsa-ci.yml file. > For instance, gem2deb dry-types. This will not yield a salsa-ci.yml > file, whilst it should. Works for me (using 0.45), if it doesn't for you, we should

gem2deb: salsa-ci.yml vs. .gitattributes [was: Re: RFS: ruby-wisper and ruby-necromancer]

Hi, On 20-02-12 00:50:58, Daniel Leidert wrote: > JFTR: It is also missing debian/.gitattributes - probably for the same > reason. I just did a test: debian/salsa-ci.yml is created correctly, but debian/.gitattributes is not. I guess the current code doesn't handle files with a dot in the

Re: debian/salsa-ci.yml created by gem2deb [was: Re: RFS: ruby-wisper and ruby-necromancer]

Hi, On 20-02-12 15:40:23, Daniel Leidert wrote: >I think I found the culprit and also fixed it. The .gitattributes file >inside the template directory prevents itself and salsa-ci.yml from >being exported into the gem2deb source and therefor into the package, >where both are

Re: RM request for coquelicot and its reverse deps?

Hi Daniel, all, On 20-02-11 23:42:11, Georg Faerber wrote: > On 20-02-12 00:29:55, Daniel Leidert wrote: > > can we file RM requests for coquelicot and its reverse dependencies > > like ruby- haml-magic-translations? Both are dead upstream and have RC > > bugs. ruby-ham

Re: RM request for coquelicot and its reverse deps?

Hi Lunar, all, On 20-02-12 10:15:23, Jérémy Bobbio wrote: > I am sorry I dropped the ball like I did. I don't think I'll return to > developing Coquelicot anytime soon, even if there are still probably > interesting work to be done. I wouldn't mind RM requests, quite the > opposite. By all

Re: question about licensing for ruby-spdx-licenses

Hi, On 20-02-15 19:30:33, Gabriel Filion wrote: > There's one package that I need to create as a dependency of > puppet-development-kit for which I had some questions pop to mind > about licensing: ruby-spdx-licenses > > The code ships a json file that contains information about all of the >

Re: confirming some package names before creating them (was Re: [Pkg-puppet-devel] in need of a little help for packaing puppet development kit with all dependencies)

Hi, On 20-02-15 19:15:34, Gabriel Filion wrote: > For the following, here's what I'm intending to choose as a package > name (ITPs still need to ben sent). I think these are more probably OK > to be named without the "ruby-" prefix: > > * jgrep >-> this one seems rather clear to me since

Re: question about licensing for ruby-spdx-licenses

Hi, On 20-02-29 17:33:40, Gabriel Filion wrote: > I don't quite know what those feature are, but if I understand > correctly you mean you would remove the file to avoid the licensing > issue altogether? Exactly. > The problem is that this file is the core of this library's > functionality, e.g.

Bug reports Ruby 2.7 transition: please use usertags

Hi all, In case you report bugs related to the Ruby 2.7 transition, please use usertags, which allow to easily keep track of these bugs. To do so, add the following to your bug reporting templates: User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition Bugs

Re: RFS: ruby-wisper and ruby-necromancer

Hi, On 20-02-10 22:01:35, Gabriel Filion wrote: > I've pushed a bit more in my packaging work (and comprehension, thanks > all for the help on the IRC channel!) and I now have two more packages > that are ready: ruby-wisper and ruby-necromancer. > > Can someone please review my work in the salsa

Re: RFS: ruby-wisper and ruby-necromancer

Hi, Another note: Both (and ruby-tty-spinner) lacked debian/salsa-ci.yml. That is fixed now. Did you create all of them with the help of gem2deb? Cheers, Georg

debian/salsa-ci.yml created by gem2deb [was: Re: RFS: ruby-wisper and ruby-necromancer]

On 20-02-12 05:04:53, Utkarsh Gupta wrote: > Whilst there's debian/salsa-ci.yml in the template, it still doesn't > seem to work. > It didn't work for me either. And Antonio is aware of this. I'm not aware, mind to elaborate? What does not work, specifically?

Re: RM request for coquelicot and its reverse deps?

Hi, On 20-02-12 00:29:55, Daniel Leidert wrote: > can we file RM requests for coquelicot and its reverse dependencies > like ruby- haml-magic-translations? Both are dead upstream and have RC > bugs. ruby-haml- magic-translations further (build-)depends on a > non-available ruby-haml version and

Re: RFS: ruby-tty-cursor and ruby-tty-spinner

Hi, On 20-02-10 16:41:12, Gabriel Filion wrote: > ah! nice thanks for catching those. I've sent corrections to both > repos. Thanks for your work; ruby-tty-cursor was uploaded by Sebastien, ruby-tty-spinner by me. > I'm not sure that I know what this means. Just to confirm whether my >

Re: Ruby team sprint -- accomodation etc.

Hi Cédric, all, I planned to send this mail since quite some time, but failed to do -- sorry for this. On 19-11-27 10:08:43, Cédric Boutillier wrote: > I am a bit short on logistic power, and my initial idea of trying to > find one place to host you all has failed. Do you need any support? Not

Re: Joining Ruby team

Hi Markus, On 19-12-30 13:55:23, Markus Frosch wrote: > I'd like to continue my work on my ruby packages. > > So I would like to join the team as DD. > > Please approve my request on salsa: > https://salsa.debian.org/ruby-team Welcome back & done. Cheers, Georg

Re: Request to (re)join Ruby team

Hi Utkarsh, On 19-12-31 03:05:22, Utkarsh Gupta wrote: > I'd like to migrate my current membership of the Ruby team to use my > new Salsa login, i.e., utkarsh \o/ * > Also, many, many thanks to all for your help, guidance, mentorship, > and sponsorship! It was lovely meeting y'all at DC19, I

Re: Should libruby2.x have Provides: ruby-foo (= x.y.z) for the gems it ships?

Hi Daniel, all, On 20-04-13 01:03:47, Daniel Leidert wrote: > What are your thoughts? Sounds reasonable, and good! Thanks, cheers, Georg

Re: [DRE-maint] Bug#960229: RFP: pdfbeads -- utility to take scanned page images and convert them to a single PDF file

(Adding the Ruby team to the loop.) Hi team, Rogério, On 20-05-11 15:22:04, Rogério Brito wrote: > On May 10 2020, Georg Faerber wrote: > > On 20-05-10 17:24:12, Rogério Brito wrote: > > > Since I don't know much ruby, I guess that it would be best to > > > hav

Re: [DRE-maint] Bug#960229: RFP: pdfbeads -- utility to take scanned page images and convert them to a single PDF file

Hi Rogério, On 20-05-11 15:22:04, Rogério Brito wrote: > Thanks for the kind message. I gave it a shot with gem2deb and I > produced a (very) preliminary package. It is at: > > https://github.com/rbrito/pkg-pdfbeads Did you import the latest upstream release? The gemspec tells "2014-01-30",

Re: I didn't receive mails from alioth list since March 5th

Hi, On 20-03-22 23:43:38, Daniel Leidert wrote: > did you receive any mail from our alioth maintainers list recently? > The last mail I received is from March 5th, but the alioth > webinterface shows mails up to March 20th. I am subscribed. My logs > don't show any delivering attempts from the

Re: RFH: testing Rails 6 reverse dependencies

Hi, On 20-05-09 00:02:06, Utkarsh Gupta wrote: > [...] > > Please help us in getting Rails 6 to Sid & Bullseye, too :) > > If you have any questions, please don't hesitate to ask them here or > on IRC. I'm wondering how the help should look like, in detail.. that is: as far as I'm not mistaken,

Re: Backporting ruby 2.7 for gitlab

Hi, On 20-06-30 10:47:53, Antonio Terceiro wrote: > To be clear: my opinion is that such backport should not be uploaded > to Debian Backports, at all. I agree, for the reasons outlined, and personally, I'm not able to support such an effort. Cheers, Georg

Re: rails 6 will be uploaded to unstable in 8 weeks (August first week)

Hi, On 20-06-06 15:05:29, Pirate Praveen wrote: > It has a list of all packages that failed. Now we need to file bugs > for these packages. Let me know if you like to help filing bugs. Also > please start fixing the packages that failed. Thanks for this. In case you report bugs related to the

Re: RFS: ruby-spdx-licenses, metadata-json-lint and ruby-pathspec

Hi, On 20-12-21 01:57:14, Gabriel Filion wrote: > I've finally found some time and energy combined and was able to push > forward a bit in my project of getting puppet-development-kit in > debian. > > I think I'm done with three more of the dependencies: > > * metadata-json-lint > *

Re: RFS: ruby-spdx-licenses, metadata-json-lint and ruby-pathspec

Hi, On 20-12-28 10:23:24, Georg Faerber wrote: > > * ruby-pathspec > > I've pushed two fixes regarding description and copyright to the > master branch. > > However, more important: this fails to build for me. As per discussion on IRC, this is fixed and the package was up

Re: RFS: jgrep, facterdb, ruby-rspec-puppet-facts

Hi, On 20-12-28 01:07:57, Gabriel Filion wrote: > Could someone please review my work on jgrep, facterdb and > ruby-rspec-puppet-facts and send the packages for me, or send me > correction suggestions if needed? All uploaded to NEW -- I've changed the section of jgrep to devel (although ruby

Re: RFS: ruby-spdx-licenses, metadata-json-lint and ruby-pathspec

Hi, On 20-12-21 01:57:14, Gabriel Filion wrote: > I think I'm done with three more of the dependencies: > > * metadata-json-lint > * ruby-spdx-licenses Both uploaded to NEW. > * ruby-pathspec I've pushed two fixes regarding description and copyright to the master branch. However, more

Re: RFS: facterdb and ruby-rspec-puppet-facts

Hi, On 21-08-21 19:21:26, Gabriel Filion wrote: > Today I've worked on fixing tests for autopkgtest for both facterdb > and ruby-rspec-puppet-facts. > > Since both of them never made it to testing (because of the failing > autopkgtest), I've also decided to upgrade both of them to the current >

Re: RFS: upgrade ruby-hitimes to 2.0.0

Hi, Daniel, as you did the last upload of ruby-hitimes, would you mind to have a look? On 21-08-21 19:12:25, Gabriel Filion wrote: > Since the package I'm working on, puppet-development-kit, requires a > more recent version of ruby-hitimes I've worked on importing the > latest upstream release,

Re: RFS: resending vagrant-librarian-puppet to unstable

Hi, On 21-08-21 19:41:24, Gabriel Filion wrote: > One of my packages was bumped out of testing during the freeze because > of a dependency problem in one of its requirements, ruby-puppet-forge > (e.g. #978228) This bug is still open, and due to its severity blocking migration. If this is not of

Re: RFS: facterdb and ruby-rspec-puppet-facts

Hi, On 21-09-07 18:43:58, Gabriel Filion wrote: > oh no, I'm embarrassed to have forgotten this. the "upstream" branch > was also missing. > > I've pushed both branches to both repositories. Took a while, but I've uploaded both now to unstable. Cheers, Georg

Re: Ruby team BoF at DebConf 22

Hi all, On 22-04-11 12:22:24, Lucas Kanashiro wrote: > Should we submit our regular BoF to DebConf this year? Are people > planning to attend in-person? Are there people willing to attend remotely? I won't attend, but will read minutes. Have fun! Cheers, Georg

Re: Gitlab packaging project funding status changed.

Hi, On 22-06-28 18:37:27, Pirate Praveen wrote: > 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

Bug#1009775: ITP: ruby-net-smtp -- library to send Internet mail via SMTP, the Simple Mail Transfer Protocol

Package: wnpp Owner: Georg Faerber Severity: wishlist X-Debbugs-CC: debian-ruby@lists.debian.org Control: affects -1 schleuder Control: block -1 by 1009774 Package name: ruby-net-smtp Version : 0.3.1 Upstream Author : Yukihiro Matsumoto, Minero Aoki URL : https

Bug#1009774: ITP: ruby-net-protocol -- Internal class for the other net-* libraries

Package: wnpp Owner: Georg Faerber Severity: wishlist X-Debbugs-CC: debian-ruby@lists.debian.org Control: affects -1 schleuder Package name: ruby-net-protocol Version : 0.1.3 Upstream Author : Yukihiro Matsumoto, Minero Aoki URL : https://github.com/ruby/net-protocol

RFC: rails: bookworm-pu: ruby-activerecord vs ruby-arel [was: RFC: ruby-arel: obsolete, remove?]

Dear team, I recently uploaded rails 2:6.1.7.3+dfsg-2 to unstable [1] with the following change: * debian/control: - Declare that ruby-activerecord breaks and replaces ruby-arel: it was merged five years ago, is therefore obsolete and to be removed. (Closes: #1038935) Please

Re: RFC: rails: bookworm-pu: ruby-activerecord vs ruby-arel [was: RFC: ruby-arel: obsolete, remove?]

Dear team, Any comments on the mail below? Thanks, Georg On 23-07-29 13:00:20, Georg Faerber wrote: > Dear team, > > I recently uploaded rails 2:6.1.7.3+dfsg-2 to unstable [1] with the > following change: > > * debian/control: > - Declare that ruby-activerecord bre

RFC: ruby-arel: obsolete, remove?

Hi all, It seems that #1038935 is happening if ruby-arel is installed. Looking at ruby-arel: Upstream tells, since 2018/04/24 [1]: Arel is now bundled in the Active Record gem, and maintained in the rails/rails repository. It seems it's only still required by ruby-premailer-rails

<    1   2