"Invalid revision range" if pushing to pkg-ruby-extras/$repo on git.d.o

Hi all, Not sure if this is specific to repos inside pkg-ruby-extras/, or if this is a more general problem, but just wanted to make sure to report this, at least: I've just pushed three tags in three different repos, and each time I got: # git push --tags Counting objects: 1, done. Writing

Re: Packing a RoR-Application

Hi Jan, On 17-09-30 17:20:14, Jan Luehr wrote: > I set up a small RoR-Application using Stretch's RoR version [1] > > [...] > > [1] https://github.com/yanosz/ansible-wireguard-rest Is this the correct link? Cheers, Georg signature.asc Description: Digital signature

Renaming ruby-factory-girl to ruby-factory-bot

Hi all, Upstream decided [1] to rename factory-girl to factory-bot, because "The name "Factory Girl" was confusing to some developers who encountered this library, and offensive or problematic to others." [2] We're using this in schleuder, therefore I would like to update the name accordingly.

Re: A Debian Ruby Sprint in Europe (France?) during the fourth semester 2018?

Hi all, On 18-05-27 23:56:09, Cédric Boutillier wrote: > I have been thinking for some time now about the idea of another > sprint for the Ruby team. After Curitiba two years ago, what about > having a new meeting, in Europe this time? Yeah yeah yeah! I would like to join, even if I'm right now

Re: Alioth repository becoming R/O and moving to salsa.debian.org

On 18-01-05 18:45:44, Chris Hofstaedtler wrote: > * Georg Faerber <ge...@riseup.net> [180105 18:44]: > > On 18-01-05 18:35:38, Georg Faerber wrote: > > > Am I right, that accounts aren't migrated, and one has to create a new > > > one, on s.d.o? > > > >

Re: Alioth repository becoming R/O and moving to salsa.debian.org

On 18-01-05 18:35:38, Georg Faerber wrote: > Am I right, that accounts aren't migrated, and one has to create a new > one, on s.d.o? That is, for people not being DD. According to the wiki, that's the case, therefore I've created an account for myself named "georg-guest". Coul

Re: Migrating off alioth

Hi all, On 17-12-26 20:59:22, Pirate Praveen wrote: > On 12/26/2017 08:28 PM, Chris Hofstaedtler wrote: > > 1) provide a working mail adress in the Maintainer field. > > > > Right now, most packages have this set: > > Maintainer: Debian Ruby Extras Maintainers > >

RFS: ruby-arel 9.0.0-1 (and some questions)

Dear Debian Ruby people, While trying to upload a new upstream release of schleuder, I've ran into the following problem while testing the package with ruby2.5: 1) Schleuder::LoggerNotifications notifies admins of multiple text-messages Failure/Error: list = create(:list,

Re: RFS: ruby-arel 9.0.0-1 (and some questions)

Hi, On 18-02-08 23:59:26, Georg Faerber wrote: > Therefore, I would like to update ruby-arel. The only reverse > dependency seems to be ruby-activerecord. However, the control file of > this packages specifies ruby-arel >= 6.0, ruby-arel << 7.0. However, &

Re: RFS: ruby-arel 9.0.0-1 (and some questions)

On 18-02-09 23:32:57, Georg Faerber wrote: > On 18-02-08 23:59:26, Georg Faerber wrote: > > Therefore, I would like to update ruby-arel. The only reverse > > dependency seems to be ruby-activerecord. However, the control file of > > this packages specifies ruby-arel >

Re: Migrating off alioth

Hi Antonio, On 18-02-11 16:14:14, Antonio Terceiro wrote: > On Thu, Feb 08, 2018 at 12:30:01AM +0100, Georg Faerber wrote: > > On 17-12-26 20:59:22, Pirate Praveen wrote: > > > On 12/26/2017 08:28 PM, Chris Hofstaedtler wrote: > > > > 1) provide a working mail

Re: salsa.d.o: Enabling CI / shared runners by default

Hi all, On 18-02-13 15:40:45, Balasankar C wrote: > On 02/13/2018 03:05 PM, Christian Hofstaedtler wrote: > >> On 13.02.2018, at 06:25, Georg Faerber <ge...@riseup.net> wrote: > >> > >> I've pushed a commit to schleuder [1] to make use of the GitLab CI. > &g

salsa.d.o: Enabling CI / shared runners by default

Hi all, I've pushed a commit to schleuder [1] to make use of the GitLab CI. However, it seems, CI / shared runners aren't enabled for this repo, and I'm not able to enable them on my own. Therefore: Could someone do this, please? Also: Would it make sense, to do this by default, for all repos?

Accepted ruby-gpgme 2.0.16-1~bpo9+1 (source) into stretch-backports

org> Changed-By: Georg Faerber <ge...@riseup.net> Description: ruby-gpgme - Ruby GPGME binding Changes: ruby-gpgme (2.0.16-1~bpo9+1) stretch-backports; urgency=medium . * Rebuild for stretch-backports. . ruby-gpgme (2.0.16-1) unstable; urgency=medium . * New upstream release.

RFS: ruby-arel 6.0.4-1

Dear ruby people, I've now prepared ruby-arel 6.0.4-1. I've made some changes to the packaging to make lintian happy and enabled autopkgtest, the release tarball contained the test suite. The version currently in unstable doesn't work with ruby2.5, and it blocks the upload of the new schleuder

RFS: ruby-nokogiri 1.8.2-1

Hi all, I've updated ruby-nokogiri to the latest upstream release and fixed some things to make lintian happy. .dsc: https://mentors.debian.net/debian/pool/main/r/ruby-nokogiri/ruby-nokogiri_1.8.2-1.dsc In git in branch debian/1.8.2-1. Thanks and cheers, Georg signature.asc Description:

salsa.d.o: How to create a new repo

Hi all, I would like to tackle renaming ruby-factory-girl to ruby-factory-bot [1], but unfortunately, I've failed to set up a new repo on salsa. According to the wiki [2], one should run ./setup-project. But this complains about a missing salsarc file in the parent dir. After creating the file,

Re: RFS: ruby-nokogiri 1.8.2-1

Hi, On 18-02-20 00:46:39, Cédric Boutillier wrote: > Thanks for this update. Thanks for your review. > I was just wondering why you removed the Testsuite field in the control > file and added a debian/tests/control file. > > The autopkgtest-pkg-ruby value of the Testsuite: field is a way to >

Re: Renaming ruby-factory-girl to ruby-factory-bot

Hi all, On 17-12-01 00:14:14, Georg Faerber wrote: > Upstream decided [1] to rename factory-girl to factory-bot, because > "The name "Factory Girl" was confusing to some developers who > encountered this library, and offensive or problematic to others." [2] >

Re: Migrating off alioth

On 18-02-15 09:59:27, Antonio Terceiro wrote: > On Tue, Feb 13, 2018 at 09:50:48PM +0100, Georg Faerber wrote: > > Hi Antonio, > > > > On 18-02-11 16:14:14, Antonio Terceiro wrote: > > > On Thu, Feb 08, 2018 at 12:30:01AM +0100, Georg Faerber wrote: > > >

Re: Renaming ruby-factory-girl to ruby-factory-bot

Hi Hleb, Thanks a lot for the review, I've created a repo now [1]. On 18-02-19 10:53:00, Hleb Valoshka wrote: > On 2/19/18, Georg Faerber <ge...@riseup.net> wrote: > > I've worked on this now, and would be more than happy, if someone could > > review my work [1]. Note:

One package: Two subdirs below /usr/lib/ruby/vendor_ruby/ {possible,policy-compliant}?

Dear ruby team, Due to recent upstream changes in schleuder, the package would now install two subdirectories, namely /usr/lib/ruby/vendor_ruby/schleuder and /usr/lib/ruby/vendor_ruby/schleuder-api-daemon. Is this possible, and in compliance with the policy? (I wasn't able to find anything on

Re: Renaming ruby-factory-girl to ruby-factory-bot

Hi Cédric, all, On 18-03-04 22:04:46, Georg Faerber wrote: > On 18-03-03 16:30:36, Cédric Boutillier wrote: > > ruby-factory-girl-rails fails to build because of dependency > > checking looking for a factory_girl gemspec file instead of a > > factory_bot. > > >

Re: Renaming ruby-factory-girl to ruby-factory-bot

On 18-03-13 16:30:16, Antonio Terceiro wrote: > On Sun, Mar 04, 2018 at 10:04:46PM +0100, Georg Faerber wrote: > > On 18-03-03 16:30:36, Cédric Boutillier wrote: > > > ruby-factory-girl-rails fails to build because of dependency checking > > > looking for a factor

Re: Renaming ruby-factory-girl to ruby-factory-bot

On 18-03-14 16:53:42, Georg Faerber wrote: > On 18-03-14 10:18:24, Antonio Terceiro wrote: > > On Wed, Mar 14, 2018 at 11:36:14AM +0100, Georg Faerber wrote: > > > On 18-03-13 16:30:16, Antonio Terceiro wrote: > > > > On Sun, Mar 04, 2018 at 10:04:46PM +0100, Georg

Re: Migrating off alioth

Hi all, On 18-02-11 16:14:14, Antonio Terceiro wrote: > It has been announced since then that there are plans to provide > continuity to the alioth mailing lists, so for now I would say let's > stick to the current maintainer address (i.e. > pkg-ruby-extras-maintain...@lists.alioth.debian.org)

RFS: ruby-factory-bot 4.8.2-1

Hi all, Please review and sponsor ruby-factory-bot 4.8.2-1, find the initial packaging in branch debian/4.8.2-1. Thanks in advance, cheers, Georg signature.asc Description: Digital signature

Re: Renaming ruby-factory-girl to ruby-factory-bot

On 18-03-14 10:18:24, Antonio Terceiro wrote: > On Wed, Mar 14, 2018 at 11:36:14AM +0100, Georg Faerber wrote: > > On 18-03-13 16:30:16, Antonio Terceiro wrote: > > > On Sun, Mar 04, 2018 at 10:04:46PM +0100, Georg Faerber wrote: > > > > On 18-03-03 16:

Re: ruby-loofah 2.0.3-2 (stretch) update (CVE-2018-8048)

Hi all, On 18-04-03 11:53:08, Salvatore Bonaccorso wrote: > On Sun, Mar 25, 2018 at 07:10:40PM +0200, Georg Faerber wrote: > > On 18-03-22 17:23:48, Moritz Muehlenhoff wrote: > > > On Thu, Mar 22, 2018 at 05:21:15PM +0100, Georg Faerber wrote: > > > > I would li

Re: build-and-upload: autopkgtest fails

Hi all, I'm not sure if I'm on the right track here, but: - Using a stretch container, AUTOPKGTEST_NORMAL_USER is set to 'nobody'. - Using a unstable container, AUTOPKGTEST_NORMAL_USER is set to 'systemd-coredump'. That is the default, without setting -u/--user explicitly.

Re: ruby-gettext-setup: FTBFS

Hi, On 18-04-04 23:58:32, Hleb Valoshka wrote: > On 4/4/18, Georg Faerber <ge...@riseup.net> wrote: > > ruby-gettext-setup FTBFS now, with errors like > > > > /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in `gsub': > > invalid byte sequence in US-

Re: build-and-upload: autopkgtest fails

Hi Antonio, I hoped you would jump in here, as I'm quite clueless what this is about, or what is wrong: On 18-04-05 08:10:09, Antonio Terceiro wrote: > On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > > On 18-04-05 07:53:57, Cédric Boutillier wrote: > > > On

Re: build-and-upload: autopkgtest fails

On 18-04-05 07:53:57, Cédric Boutillier wrote: > On Wed, Apr 04, 2018 at 10:56:31PM +0200, Georg Faerber wrote: > > flock: failed to execute mispipe: No such file or directory > > mispipe is in the moreutils package. Do you have it installed? It is > recommended by debci.

Re: build-and-upload: autopkgtest fails

Hi all, On 18-04-05 13:18:56, Georg Faerber wrote: > On 18-04-05 08:10:09, Antonio Terceiro wrote: > > On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > > > However, running > > > build-and-upload after this leads to the same result: > > > >

Re: build-and-upload: autopkgtest fails

On 18-04-05 16:47:26, Georg Faerber wrote: > On 18-04-05 13:18:56, Georg Faerber wrote: > > On 18-04-05 08:10:09, Antonio Terceiro wrote: > > > On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > > > > However, running > > > > build-and-

ruby-gettext-setup: FTBFS [Re: RFS: ruby-tzinfo, ruby-gettext, ruby-kgio, ruby-solve]

Hi Hleb, all, On 18-03-21 23:29:33, Hleb Valoshka wrote: > On 3/21/18, Cédric Boutillier wrote: > > Is it "normal" that ruby-gettext-setup tests fail with the new > > ruby-gettext? They seem to pass with the current version on > > ci.debian.net. > > I've checked

Re: build-and-upload: autopkgtest fails

Hi all, Some more findings: $ /usr/bin/autopkgtest -d -u debci /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc -- lxc --sudo autopkgtest-sid 11:32 autopkgtest: DBG: autopkgtest options:

Re: ruby-loofah 2.0.3-2 (stretch) update (CVE-2018-8048)

Hi, @Ruby team: Gentle ping; could someone please take care of the upload? Thanks, cheers, Georg On 18-04-03 12:05:28, Georg Faerber wrote: > On 18-04-03 11:53:08, Salvatore Bonaccorso wrote: > > On Sun, Mar 25, 2018 at 07:10:40PM +0200, Georg Faerber wrote: > > > On 18-03-2

Re: ruby 2.5.1 orig tarball differs from upstream

Hi John, On 18-04-06 17:14:57, John Leach wrote: > I noticed that debian's ruby2.5_2.5.1.orig.tar.gz (sha1 > e95ff19092f2026b161e6e6d7759489d646e10aa) differs from the actual > upstream ruby 2.5.1 release tarball > (93fafd57a724974b951957c522cdc4478a6bdc2e) > > The only difference is some gems

RFS: ruby-factory-bot 4.8.2-2

Hi all, Please review / upload ruby-factory-bot 4.8.2-2. Changes pushed to branch d/4.8.2-2. Thanks, cheers, Georg signature.asc Description: Digital signature

Re: Renaming ruby-factory-girl to ruby-factory-bot

Hi, On 18-03-27 10:03:37, Pirate Praveen wrote: > On March 27, 2018 3:01:33 AM GMT+05:30, Georg Faerber <ge...@riseup.net> > wrote: > >- ruby-factory-girl-rails: @Pirate: If you need help with this, tell > > me. > > If you can do it, that'll be good. I

RFS: ruby-factory-bot 4.8.2-1~bpo9+1

Hi all, Please review / upload ruby-factory-bot 4.8.2-1~bpo9+1. Changes pushed in git to branch backports/stretch. I'm backporting this as a BD of schleuder. Thanks, cheers, Georg signature.asc Description: Digital signature

Re: RFS: ruby-factory-bot 4.8.2-2

On 18-03-27 11:51:36, Georg Faerber wrote: > Please review / upload ruby-factory-bot 4.8.2-2. Changes pushed to > branch d/4.8.2-2. Friendly ping on this, could someone review? Thanks, cheers, Georg signature.asc Description: Digital signature

The future of rails

Hi all, We're developing a web interface for schleuder, to ease administration of schleuder lists for users etc. This is currently using rails 4. We would like to get this into Debian as well. The release notes of rails 5.1.0.rc1 [1], published 2017/03/20, read: "As per our maintenance policy,

Re: The future of rails

Hi Pirate, Thanks for your mail: On 18-03-29 12:00:38, Pirate Praveen wrote: > On March 29, 2018 12:31:29 AM GMT+05:30, Georg Faerber <ge...@riseup.net> > wrote: > > [...] > > > >I didn't found anything more recent, and the above was posted one > >year ago

Re: ruby-loofah 2.0.3-2 (stretch) update (CVE-2018-8048)

Hi all, On 18-03-22 17:21:15, Georg Faerber wrote: > I would like to fix CVE-2018-8048, which is currently present in > ruby-loofah 2.0.3-2 in stretch. Do you prefer an "straight" upload done > by you, or should this be instead an upload via stretch-pu? > > In any c

Re: ruby-loofah 2.0.3-2 (stretch) update (CVE-2018-8048)

On 18-03-24 16:41:17, Georg Faerber wrote: > --- ruby-loofah-2.0.3/debian/changelog2016-01-07 14:22:29.0 > +0100 > +++ ruby-loofah-2.0.3/debian/changelog2018-03-24 16:13:55.0 > +0100 > @@ -1,3 +1,10 @@ > +ruby-loofah (2.0.3-2+deb9u1) stretch-secu

Re: ruby-loofah 2.0.3-2 (stretch) update (CVE-2018-8048)

Hi security team, On 18-03-22 17:23:48, Moritz Muehlenhoff wrote: > On Thu, Mar 22, 2018 at 05:21:15PM +0100, Georg Faerber wrote: > > I would like to fix CVE-2018-8048, which is currently present in > > ruby-loofah 2.0.3-2 in stretch. Do you prefer an "straight" upload &

build-and-upload: autopkgtest fails

Hi all, I'm running into an error if using the build-and-upload script. I'm not sure what this is about, and failed to debug further; maybe someone of you could share some insight? [...] Run the test suite now? [Y/n]Y [sudo] password for georg: I: lxc container autopkgtest-sid-amd64 not found

Re: ruby-loofah 2.0.3-2 (stretch) update (CVE-2018-8048)

Hi security team, Friendly ping on this? Did you had a chance to do a review? Anything I could do to fix ruby-loofah in stretch? Thanks for your work, cheers, Georg On 18-03-25 19:10:40, Georg Faerber wrote: > On 18-03-22 17:23:48, Moritz Muehlenhoff wrote: > > On Thu, Mar 22, 2018

Re: Renaming ruby-factory-girl to ruby-factory-bot

On 18-03-14 16:53:42, Georg Faerber wrote: > On 18-03-14 10:18:24, Antonio Terceiro wrote: > > On Wed, Mar 14, 2018 at 11:36:14AM +0100, Georg Faerber wrote: > > > Reverse dependencies are then able to change their dependency > > > anytime they wish. > > >

Re: RFS: ruby-sequel 5.6.0-1

hi dai, On 18-03-18 13:43:51, d...@debian.org wrote: > On Sun, Mar 18, 2018 at 05:30:37AM +0100, Georg Faerber wrote: > > > * /usr/share/doc/ruby-sequel/doc/release_notes/*.txt > > > Somehow they are compressed or uncompressed. > > > > I don't understand this.

Re: RFS: ruby-sequel 5.6.0-1

Hi dai, On 18-03-18 05:59:05, Georg Faerber wrote: > On 18-03-18 13:43:51, d...@debian.org wrote: > > On Sun, Mar 18, 2018 at 05:30:37AM +0100, Georg Faerber wrote: > > > > * /usr/share/doc/ruby-sequel/doc/release_notes/*.txt > > > > Somehow they are compresse

Re: RFS: ruby-loofah 2.2.1-1 (CVE-2018-8048)

On 18-03-22 01:33:20, Chris Hofstaedtler wrote: > * Georg Faerber <ge...@riseup.net> [180322 01:29]: > > On 18-03-22 01:04:23, Cédric Boutillier wrote: > > > Can you also take care of applying the patch to the version currently > > > in stable and contact the se

MiniDebConf May 2018 Hamburg; Sprint?

Hi all, I'll go to the MiniDebConf in May in Hamburg. I would like to meet some of you in person, and I could imagine to do a sprint over there. Anybody around? Cheers, Georg signature.asc Description: Digital signature

Re: RFS: ruby-factory-bot 4.8.2-1

On 18-03-15 14:50:34, Georg Faerber wrote: > Please review and sponsor ruby-factory-bot 4.8.2-1, find the initial > packaging in branch debian/4.8.2-1. Uploaded by Cédric. Thanks, Georg signature.asc Description: Digital signature

RFS: rake 12.3.0-2

Hi, Please review / sponsor rake 12.3.0-2. Changes pushed to branch debian/12.3.0-2. Thanks, cheers, Georg signature.asc Description: Digital signature

RFS: ruby-loofah 2.2.1-1 (CVE-2018-8048)

Hi all, Please review / upload ruby-loofah 2.2.1-1, which fixes CVE-2018-8048. Changes pushed to git in branch d/2.2.1-1. Thanks, cheers, Georg signature.asc Description: Digital signature

Re: RFS: ruby-loofah 2.2.1-1 (CVE-2018-8048)

On 18-03-22 01:04:23, Cédric Boutillier wrote: > Can you also take care of applying the patch to the version currently > in stable and contact the security team for a proposed update for > stretch? Actually, aren't proposed uploads targeted at point releases? If so, this might take a while, as

Re: RFS: ruby-tzinfo, ruby-gettext, ruby-kgio, ruby-solve

On 18-03-21 23:34:50, Cédric Boutillier wrote: > On Wed, Mar 21, 2018 at 11:29:33PM +0300, Hleb Valoshka wrote: > > On 3/21/18, Cédric Boutillier wrote: > > > > Is it "normal" that ruby-gettext-setup tests fail with the new > > > ruby-gettext? They seem to pass with the

Re: simple helper scripts: vcs-salsa, standards-version, debhelper-compat

Hi, On 18-03-20 11:25:12, Cédric Boutillier wrote: > I added simple scripts in the meta repo, which automate boring tasks: Nice! :) > standards-version: > update Standards-Version to the latest policy version This breaks if the file is not available. I'll add a check to catch this. > If you

rails-html-sanitizer 1.0.3: Two broken tests with loofah 2.2.1 (CVE-2018-8048)

Hi Kasper, We would like to fix CVE-2018-8048, which was assigned some days ago, to loofah. A fix was released to address a potential XSS vulnerability caused by libxml2. See [1] and below: On 18-03-22 01:04:23, Cédric Boutillier wrote: > On Wed, Mar 21, 2018 at 11:35:57PM +0100, Georg Faer

RFS: ruby-rails-html-sanitizer 1.0.4-1

Hi all, Please review / upload ruby-rails-html-sanitizer 1.0.4-1. Changes pushed to git in branch d/1.0.4-1. Thanks, cheers, Georg signature.asc Description: Digital signature

Re: RFS: ruby-rails-html-sanitizer 1.0.4-1

On 18-03-23 16:03:30, Cédric Boutillier wrote: > On Fri, Mar 23, 2018 at 01:52:57PM +0100, Georg Faerber wrote: > > Please review / upload ruby-rails-html-sanitizer 1.0.4-1. Changes pushed > > to git in branch d/1.0.4-1. > > Uploaded. Thanks! Thank you! > Not

RFS: ruby-sequel 5.6.0-1

Hi all, Please review and sponsor ruby-sequel 5.6.0-1, find the changes in branch debian/5.6.0-1. Note: Lintian complains about application-in-library-section ruby usr/bin/sequel. I didn't touched this yet, but: Should this package be renamed in a upload in the future? Thanks in advance,

Re: Renaming ruby-factory-girl to ruby-factory-bot

Hi, On 18-03-03 16:30:36, Cédric Boutillier wrote: > ruby-factory-girl-rails fails to build because of dependency checking > looking for a factory_girl gemspec file instead of a factory_bot. > > I don't know if it is better to fix factory-girl-rails gemspecs, or to > ship also the

Re: Renaming ruby-factory-girl to ruby-factory-bot

Hi Cédric, Thanks for your review. On 18-03-03 15:05:14, Cédric Boutillier wrote: > I would just propose to include the old changelog from > ruby-factory-girl, so that the history is not gone, when the source > package ruby-factory-girl is removed. Done. > Please keep also the previous

Re: Renaming ruby-factory-girl to ruby-factory-bot

On 18-03-03 15:35:29, Cédric Boutillier wrote: > I think it should be also 'autopkgtest-pkg-ruby' instead of > 'autopkgtest' for Testsuite field in debian/control but the smart > autopkgtest seems to detect that it is indeed a ruby package anyway. Thanks, it worked with 'autopkgtest' as well, but

Re: Renaming ruby-factory-girl to ruby-factory-bot

Hi Hleb, all, On 18-02-19 20:07:44, Georg Faerber wrote: > Thanks a lot for the review, I've created a repo now [1]. > > On 18-02-19 10:53:00, Hleb Valoshka wrote: > > On 2/19/18, Georg Faerber <ge...@riseup.net> wrote: > > > I've worked on this now, and would

RFS: ruby-factory-bot 4.11.1-1

Hi all, Searching for sponsorship as per the subject. .dsc [1], pushed to git in branch debian/4.11.1-1. Thanks, cheers, Georg [1] https://mentors.debian.net/debian/pool/main/r/ruby-factory-bot/ruby-factory-bot_4.11.1-1.dsc signature.asc Description: Digital signature

autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

Hi all, Today I've worked on two packages, ruby-gpgme and ruby-sequel, and ran into the following error for both of them during autopkgtest: Checking Rubygems dependency resolution on ruby2.5 │ /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:161:in ``': No such file or

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

Hi, On 18-12-19 10:12:06, Pirate Praveen wrote: > If you can push your changes, I can upload it. This would be great, I already pushed all the changes to the following branches: ruby-gpgme: debian/2.0.18-1 ruby-sequel: debian/5.15.0-1 In case any changes are necessary, and if you're willing

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

Hi, On 18-12-18 17:05:18, Pirate Praveen wrote: > This is probably a transient failure. I'm not able to reproduce it > today. Did you check one of the two mentioned packages? I'm still running into this error. Cheers, Georg signature.asc Description: Digital signature

Re: RFS: schleuder-gitlab-ticketing 1.0.0-1

Hi all, On 19-02-21 23:06:23, Georg Faerber wrote: > Dear team, > > I've prepared, based on user requests, the initial upload of > schleuder-gitlab-ticketing. > > Could someone review, and possibly upload this? > > Thanks a lot, > cheers, > Georg Could anyone

Re: RFS: schleuder-gitlab-ticketing 1.0.0-1

On 19-03-01 10:20:07, Antonio Terceiro wrote: > debian/tests/* is redundant; that is exactly what `Testsuite: > autopkgtest-pkg-ruby` will do for you. > > other than that, LGTM Thanks, fixed. signature.asc Description: Digital signature

RFS: schleuder-gitlab-ticketing 1.0.0-1

Dear team, I've prepared, based on user requests, the initial upload of schleuder-gitlab-ticketing. Could someone review, and possibly upload this? Thanks a lot, cheers, Georg signature.asc Description: Digital signature

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

Hi all, On 18-12-16 18:32:50, Georg Faerber wrote: > Checking Rubygems dependency resolution on ruby2.5 > > /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:161:in ``': No such file or > directory - dpkg-parsechangelog (Errno::ENOENT) > from /usr/lib/ruby/vendor_ruby/gem2deb/

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

Hi all, On 19-02-03 14:10:40, Georg Faerber wrote: > Any ideas? This was due to dpkg-parsechangelog not being available in the container. It's shipped via dpkg-dev; gem2deb depends on devscripts, which in turn depends on dpkg-dev, so I'm unsure why was / is that. IIRC, I've just encounte

ruby-factory-bot 5.0.0-1 prepared

Hi all, As per the subject, I've prepared the new upstream version. Pushed to git in branch debian/v5. Please note: The upload should be done in conjunction with the new version of ruby-factory-bot-rails, as the current version would be broken. Cheers, Georg signature.asc Description: Digital

Re: team repo configuration on salsa

Hi Utkarsh, all, On 19-08-14 03:44:02, Utkarsh Gupta wrote: > But FWIW, we have CI enabled for every package under the Ruby team now. That's really great, thanks to everyone involved! > Over the next few days, I'll integrate a couple of things in gem2deb > as well (if no one does by then). I

Re: reducing volument of KGB notifications on IRC

On 19-08-18 22:57:29, Cédric Boutillier wrote: > Having a dedicated channel for notifications would be a nice solution > to get all the information we want and keep a sane place for human > interactions. +1

Re: Ruby team sprint(s)

Hi Cédric, all, On 19-08-11 17:27:16, Cédric Boutillier wrote: > I maintain my proposition to hold a Ruby sprint in Paris. Do we plan > to have a 5-day sprint as the last two times? I think it was a good > format to have a lot of things done. > > If we aim for December or January, I can propose

Re: reducing volument of KGB notifications on IRC

Hi all, On 19-08-17 13:02:44, Antonio Terceiro wrote: > fair enough. I noticed that the python team has two channels: > #debian-python for humans, and #debian-python-changes for > notifications. maybe we could do something similar? This seems like the way to go given all the mails in response,

Re: reducing volument of KGB notifications on IRC

On 19-08-27 08:44:47, Georg Faerber wrote: > Also, Antonio, I think consensus is reached regarding your initial > proposal, minus squashing the commits, so I think you're good to go > ahead. If possible, I would like to not receive build notifications for tags, but just for commits. In

Re: Ruby team sprint(s)

Dear team, all, On 19-08-11 17:27:16, Cédric Boutillier wrote: > I maintain my proposition to hold a Ruby sprint in Paris. > Do we plan to have a 5-day sprint as the last two times? I think it was > a good format to have a lot of things done. > > If we aim for December or January, I can propose

Re: reducing volument of KGB notifications on IRC

On 19-08-27 08:44:47, Georg Faerber wrote: > Also, Antonio, I think consensus is reached regarding your initial > proposal, minus squashing the commits, so I think you're good to go > ahead. As per discussion on IRC, this is now live: KGB notifications for commits and CI pipeline stat

Re: RFS: vagrant-librarian-puppet

On 19-08-29 15:09:28, Gabriel Filion wrote: > ah good! it's been uploaded last sunday so maybe unattended-upgrades > has not run yet. I'm still on 0.43 Are you on buster or bullseye? I'm thinking about if it would make sense to get gem2deb into b-bp. Cheers, Georg

Re: RFS: vagrant-librarian-puppet

tl;dr: Uploaded, now in NEW. On 19-08-29 13:50:07, Gabriel Filion wrote: > > - git tags: > > - Please sign your tags -- not sure which tooling you're using, but in > > case it's gbp, that's quite easy to accomplish: create ~/.gbp.conf > > with the following content: > > > >

Re: team repo configuration on salsa

On 19-08-28 10:13:53, Utkarsh Gupta wrote: > Perfecto. > I just did add a metadata file to include d/upstream/metadata (as we > discussed in the BoF); rest in on you :D :) > Also, if possible, I'd love to see gem2deb using the correct upstream > tarballs in d/watch *somehow* instead of what it

Re: team repo configuration on salsa

Hi, On 19-08-12 11:48:32, Cédric Boutillier wrote: > This is a list of packages I noticed already used ci, but not with > debian/salsa-ci.conf. > the ci config file is still pointing to the original file. > > [...] > ruby-gpgme > ruby-mail-gpg > schleuder > schleuder-gitlab-ticketing I've fixed

Re: team repo configuration on salsa

On 19-08-28 13:26:40, Utkarsh Gupta wrote: > The upstream code is mostly hosted on GitHub, but that's not the case > always, no? Yes. > I am not sure how to do this d/watch thingy because though the > homepage mentioned is mostly the URL where the source code is hosted > but sometimes it refers

Re: RFS: ruby-*

On 19-08-28 10:07:34, Utkarsh Gupta wrote: > I did complete fixing the pending test failures (as an attempt to > enable tests in all the packages), thus requesting you to review and > upload the same (since they are NEW). > > ruby-benchmark-memory > ruby-ammeter > ruby-arbre (thanks to terceiro

Re: reducing volument of KGB notifications on IRC

Hi, This topic is two fold, in my opinion: On 19-08-28 08:25:06, Utkarsh Gupta wrote: > It doesn't make much sense to run CI on the tags :/ Yes, I agree. That's why I created [1] some time ago, more recently [2] was created, both tickets asking to disable CI by default for tags. However, so

Re: RFS: ruby-*

Hi, On 19-08-28 10:07:34, Utkarsh Gupta wrote: > ruby-benchmark-memory Doesn't build for me, the last log lines read: Reading package lists... Building dependency tree... Reading state information... Reading extended state information... Initializing package states... Writing extended state

Re: RFS: ruby-*

On 19-08-28 11:06:07, Antonio Terceiro wrote: > What's obsolete/unnecessary is `Testsuite: autopkgtest`, when you have > debian/tests/control, because dpkg-source will add `Testsuite: > autopkgtest` for you. > > Any other value of `Testsuite:`, including but not limited to >

Re: RFS: vagrant-librarian-puppet

Hi, On 19-08-28 23:36:41, Gabriel Filion wrote: > I've just pushed a tag and "dch -r" for my first release the > vagrant-librarian-puppet package. Great, congratulations! :) > I've tested install and functionality of the vagrant plugin, and I > believe I'm ready for reviews before the package

Re: RFS: ruby-*

On 19-08-28 10:07:34, Utkarsh Gupta wrote: > ruby-benchmark-memory > ruby-ammeter > ruby-arbre (thanks to terceiro :D) All uploaded, now in NEW.

Re: reducing volument of KGB notifications on IRC

On 19-08-28 08:27:26, Georg Faerber wrote: > Still, we could at least disable notifications for the pipelines which > are triggered if tags are pushed. I didn't test this yet, but > disabling the hook for "Tag push events" should do the trick. This > way, the pipeline wou

Re: reducing volument of KGB notifications on IRC

Hi all, On 19-08-29 01:01:08, Georg Faerber wrote: > I'll follow-up to see if consensus can be formed within the Salsa CI > team to disable the pipeline for tags. Just for the record: this change was done upstream now [1]: By default, the pipeline is not run anymore if pushing tags.

Re: Introduction and request for help packaging a ruby app

Hi, On 19-07-16 01:15:42, Gabriel Filion wrote: > I'm somewhat new to debian packaging, although I'm currently already > co-maintaining the smokeping package, and I would like to create a new > debian package for a ruby app (or rather plugin?): > vagrant-librarian-puppet > > I already have an

  1   2   >