[DRE-maint] Bug#1069616: rc-buggy, not needed anymore

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: ruby-...@packages.debian.org Control: affects -1 + src:ruby-eye User: ftp.debian@packages.debian.org Control: block -1 by 1069615 rc buggy #1031479 and originally packaged as dependency of diaspora which is now requested to be removed.

[DRE-maint] Bug#1069615: RM: diaspora -- ROM; unmaintained, rc-buggy

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: diasp...@packages.debian.org Control: affects -1 + src:diaspora User: ftp.debian@packages.debian.org Usertags: remove I was hoping to come back to updating diaspora, but I don't think I will be able to find time. It is affected by rc

[DRE-maint] Bug#1025084: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

Control: fixed -1 0.7.0-1 On Wed, 7 Feb 2024 14:03:34 +0530 Praveen Arimbrathodiyil wrote: Control: severity -1 serious On Sun, 18 Jun 2023 13:14:21 +0530 Pirate Praveen wrote: > > Since ruby-faraday-middleware is deprecated, we should update to > graphlient 0.7 ruby-

[DRE-maint] Bug#1063658: drop snowlow-tracker orig tar

Package: gitlab Version: 16.6.6-3 Severity: wishlist snowplow-tracker orig.tar can be removed now, this was included because snowplow-tracker was in vendor in a generated form so providing the corresponding source was required to satisfy dfsg. Now snowplow-tracker is available from npmjs.com

[DRE-maint] Bug#1063655: RM: ruby-graphql-errors -- ROM; unmaintained upstream, incompatible with ruby-graphql 2.x

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-graphql-err...@packages.debian.org Control: affects -1 + src:ruby-graphql-errors Control: block 1063654 by -1 Reported as RC bug 1063654. ruby-graphlient dropped the build

[DRE-maint] Bug#1063654: ruby-graphql-errors - upstream dead and incompatible with ruby-graphql 2.x

Package: ruby-graphql-errors Version: 0.4.0-2 Severity: serious source package has 1 unsatisfiable build dependency Build dependencies in unstable cannot be satisfied on amd64 because: unsatisfied dependency on ruby-graphql (< 2) Last commint was 4 years ago and

[DRE-maint] Bug#1052730: ruby-delayed-job: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:

Control: forwarded -1 https://github.com/collectiveidea/delayed_job/pull/1203 On Tue, 26 Sep 2023 14:40:49 +0200 Lucas Nussbaum wrote: Relevant part (hopefully): > ArgumentError: >Invalid Timezone: US/Eastern Forwarded fix upstream

[DRE-maint] Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

Control: severity -1 important On 9/2/24 6:48 PM, Pirate Praveen wrote: Without libjs-underscore in build depends, the test should fail, but it is passing. ruby-rails-assets-underscore source package includes underscore.js and it is replaced by symlink to libjs-underscore only in dh_install

[DRE-maint] Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

Control: severity -1 serious On Fri, 9 Feb 2024 00:30:03 +0530 Pirate Praveen wrote: For majority of packages that wraps javascript assets, the actual assets are shipped in a libjs-* package and ruby-* package only include a symbolic link. Testing further with ruby-rails-assets-underscore

[DRE-maint] Bug#1063478: gem2deb rails assets smoke test should handle links or skip the test during build

Package: gem2deb Version: 2.2.1 Sevrity: important For majority of packages that wraps javascript assets, the actual assets are shipped in a libjs-* package and ruby-* package only include a symbolic link. At present, this means, the test will always fail in such cases since dh_link step is

[DRE-maint] Bug#1063389: Find out which dependency causes these failures with ruby-grape 2.0

Package: ruby-grape severity: wishlist I'm going to patch this to match the extected outcome, but we should figure out which dependency is causing a mismatch and ideally sync with upstream. Failures: 1) Grape::Http::Headers is expected to eq "location" Failure/Error: it {

[DRE-maint] Bug#1063198: gitlab: GraphQL returns 500 when moving issues on issue board

On 05/02/24 11:06 pm, Jakob Haufe wrote: On Mon, 5 Feb 2024 22:39:41 +0530 Pirate Praveen wrote: One thing I can think of is newer graphql gem. See if manually installing [1] graphql 2.0.27 fixes it. Yes, you are right. Downgrading graphql to 2.0.27 fixes it. Sad fact: Even 16.8 still

[DRE-maint] Bug#1063198: gitlab: GraphQL returns 500 when moving issues on issue board

On 05/02/24 10:10 pm, Jakob Haufe wrote: - GraphQL::RequiredImplementationMissingError (GitlabSchema.resolve_type(type, obj, ctx) must be implemented to use Union types, Interface types, or `loads:` (tried to resolve: Types::BoardType)): One thing I can think of is newer graphql gem.

[DRE-maint] Bug#1060797: Swutch to caddy from nginx+certbot

Package: diaspora-common version: 0.7.18.2+debian1 severity: wishlist caddy has built in support for https certificate management so less code for us to manage. caddy configuration file is simpler and has good defaults for security. ___

[DRE-maint] Bug#1059710: [ruby-octokit 6 transition] Could not find 'o, ctokit' (~> 4.0, != 4.4.0) - did find: [octokit-6.1.1]

Package: ruby-jekyll-github-metadata Version: 2.15.0-1 Severity: important User: debian-r...@lists.debian.org Usertags: octokit6 Control: tags -1 fixed-upstream ruby-jekyll-gist autopkgtest and rebuild fails with ruby-octokit 6 from experimental Could not find 'octokit' (~> 4.0, != 4.4.0) -

[DRE-maint] Bug#1059707: [ruby-octokit 6 transition] Could not find 'octokit' (~> 4.2) - did find: [octokit-6.1.1]

Package: ruby-jekyll-gist Version: 1.5.0-2 Severity: important User: debian-r...@lists.debian.org Usertags: octokit6 Control: forwarded -1 https://github.com/jekyll/jekyll-gist/issues/99 ruby-jekyll-gist autopkgtest fails with ruby-octokit 6 from experimental

[DRE-maint] Bug#1059338: Update database config for 15.9 -> 16.0 upgrade (current config is deprecated)

Package: gitlab Version: 16.4.4+ds1-1 severity: important Currently gitlab shows a warning during installation ██ ██  █  ██  ███  ██ ██ ███  ██  ██  ██ ██ ██   ██ ██   ██   ██ ██   ██ ██   ██  █  ██ ███ ██  ██ ██  ██ ██ 

[DRE-maint] Bug#1049343:

On 15/08/23 1:08 am, Nicolas Godet wrote: Hi,  Same bug during Debian upgrade from 11 to 12 today. Could be linked to google protobuf 3.24.0. Another user on IRC

[DRE-maint] Bug#1025090: ruby-gh fails to rebuild on updating ruby-faraday

On Sun, 18 Jun 2023 15:28:38 +0530 Pirate Praveen wrote: > Reported upstream https://github.com/travis-ci/gh/issues/46 I'm planning to upload ruby-faraday 2.0 to unstable around 1st August. ___ Pkg-ruby-extras-maintainers mailing list Pkg-r

[DRE-maint] Bug#1041067: RM: ruby-ms-rest -- ROM; unmaintained upstream, rc buggy

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-ms-r...@packages.debian.org Control: affects -1 + src:ruby-ms-rest Control: block -1 by 1041065 It is unmaintained upstream and incompatible with ruby-faraday 2.0. This was

[DRE-maint] Bug#1041065: RM: ruby-ms-rest-azure -- ROM; unmaintained upstream, rc buggy

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-ms-rest-az...@packages.debian.org Control: affects -1 + src:ruby-ms-rest-azure ruby-ms-rest-azure is affected by rc bug #1037994 (incompatible with ruby-faraday 2.0) and is

[DRE-maint] Bug#1037994: retitle and add forwarded

Control: reassign -1 ruby-ms-rest-azure On Sun, 18 Jun 2023 12:31:50 +0530 Pirate Praveen wrote: > Control: forwarded -1 > https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/issues/3 > Control: retitle -1 ruby-ms-rest-azure ftbfs with ruby-faraday 2.0 Also

[DRE-maint] Bug#1034565: fixed in 0.23

Control: fixed -1 0.23.1-3 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#1040819: gitlab postinst fails with gem version number parsing error

On 11/07/23 10:34 am, Jakob Bohm wrote: Package: gitlab Version: 15.10.8+ds1-1~fto12+1 Severity: normal Dear Maintainer, When trying to install gitlab (fasttrack) in a mostly blank bookworm VM, postinst fails with the following messages: Setting up gitlab (15.10.8+ds1-1~fto12+1) ...

[DRE-maint] Bug#1040834: RM: ruby-fission -- ROM; rc buggy, abandoned upstream

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-fiss...@packages.debian.org Control: affects -1 + src:ruby-fission Control: block 1040054 by -1 Control: block -1 by 1040831 Control: affects ruby-cfpropertylist This is affected

[DRE-maint] Bug#1040831: RM: ruby-fog-vmfusion -- ROM; abandoned upstream, leaf package

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-fog-vmfus...@packages.debian.org Control: affects -1 + src:ruby-fog-vmfusion This was originally packaged for gitlab, but no longer required. It is abandoned upstream (last

[DRE-maint] Bug#1034565: ftbfs tests fail on ppc64el and mips64el

On Tue, 18 Apr 2023 17:08:34 +0530 Pirate Praveen wrote: > Failures: > >1) Prometheus::Client::Helper::MmapedFile file does not exist creates > a file with minimum initial size > Failure/Error: expect(File.size(subject.filepath)).to > eq(subject.send(:init

[DRE-maint] Bug#1039916: ruby-derailed-benchmarks: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0)

On Thu, 29 Jun 2023 16:03:13 +0200 Paul Gevers wrote: > ┌──┐ > 19s │ Checking Rubygems dependency resolution on ruby3.1 > │ > 19s >

[DRE-maint] Bug#1039915: ruby-benchmark-memory: autopkgtest needs update for new version of ruby-memory-profiler: Could not find 'memory_profiler' (~> 0.9)

Control: fixed -1 0.2.0-1 On Thu, 29 Jun 2023 16:01:57 +0200 Paul Gevers wrote: > Currently this regression is blocking the migration of > ruby-memory-profiler to testing [1]. Of course, ruby-memory-profiler > shouldn't just break your autopkgtest (or even worse, your package), but > it

[DRE-maint] Bug#961595: ruby-gollum-lib: please package new upstream release 5.x

Control: block 1040461 by -1 On Tue, 26 May 2020 14:55:28 +0200 Jonas Smedegaard wrote: > gollum-lib 5.x has been out for a few months, with several exciting new > features. > > Please consider upgrading to that new release. ruby-gollum-lib was originally packaged as a dependency of gitaly

[DRE-maint] Bug#1040405: ruby-gollum-lib: incompatible with newer ruby-rouge

On Wed, 5 Jul 2023 16:44:31 +0200 Gianfranco Costamagna wrote: > Can you please have a look? We no longer need ruby-gollum-lib for gitaly, so requested removal of ruby-gollum-lib in #1040461. ___ Pkg-ruby-extras-maintainers mailing list

[DRE-maint] Bug#1040461: RM: ruby-gollum-lib -- ROM; incompatible with newer ruby-rouge

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-gollum-...@packages.debian.org Control: affects -1 + src:ruby-gollum-lib Control: block 1040405 by -1 Please remove ruby-gollum-lib from the archive. It is affected by rc bug

[DRE-maint] Bug#1025075: faraday-typhoeus adapter to support faraday 2.0

Control: forwarded -1 https://github.com/typhoeus/typhoeus/issues/717 On Sat, 10 Dec 2022 00:33:23 +0530 Vinay wrote: > Since this is an upstream issue we need to wait until typhoeus updates > to faraday 2.0 > > https://github.com/typhoeus/typhoeus/issues/686 > > faraday-typhoeus 2 adapter

[DRE-maint] Bug#1035307: Update ruby-ruby-parser to 3.20.x

Control: clone -1 -2 Control: retitle -2 update ruby-sexp-processor to 4.17 Control: reassign -2 ruby-sexp-processor On Sun, 30 Apr 2023 20:35:00 +0530 Praveen Arimbrathodiyil wrote: > Package: ruby-ruby-parser > Version: 3.19.2-1 > Severity: important > > Gitlab 15.11.0 needs

[DRE-maint] Bug#1037963: rabbit ftbfs/autopkgtest failure with ruby-faraday 2.7 in experimental

Control: forwarded -1 https://github.com/rabbit-shocker/rabbit/issues/151 On Thu, 15 Jun 2023 01:18:17 +0530 Pirate Praveen wrote: > > Started >

[DRE-maint] Bug#1025090: ruby-gh fails to rebuild on updating ruby-faraday

Control: forwarded -1 https://github.com/travis-ci/gh/issues/46 On Tue, 29 Nov 2022 23:56:38 +0530 Vinay wrote: > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in > block in activate_dependencies': Could not find 'faraday' (~> 1.0) among Reported upstream

[DRE-maint] Bug#1025085: ruby-google-cloud-translate breaks after updating ruby-faraday

On Tue, 29 Nov 2022 23:38:44 +0530 Vinay wrote: > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: ruby-googleauth (< 0.10.0) > but 0.13.0-3 is to be installed This is a leaf package and we can remove it. Seems to be replaced by

[DRE-maint] Bug#1025095: ruby-azure-storage-common fails to rebuild after new upstream of ruby-faraday

Control: forwarded -1 https://github.com/Azure/azure-storage-ruby/issues/227 Control: tags -1 patch On Wed, 30 Nov 2022 00:12:19 +0530 Vinay wrote: > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in > block in activate_dependencies': Could not find 'faraday' (~> 1.0)

[DRE-maint] Bug#1025084: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

On Sun, Jun 18 2023 at 01:09:36 PM +05:30:00 +05:30:00, Pirate Praveen wrote: On Tue, 29 Nov 2022 23:33:01 +0530 Vinay wrote: > `raise_if_conflicts': Unable to activate faraday_middleware-1.0.0, > because faraday-2.7.1 conflicts with faraday (~> 1.0) (Gem::ConflictError) T

[DRE-maint] Bug#1025084: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream

On Tue, 29 Nov 2022 23:33:01 +0530 Vinay wrote: > `raise_if_conflicts': Unable to activate faraday_middleware-1.0.0, > because faraday-2.7.1 conflicts with faraday (~> 1.0) (Gem::ConflictError) This seems to be caused by ruby-faraday-middleware.

[DRE-maint] Bug#1037994: retitle and add forwarded

Control: forwarded -1 https://gitlab.com/gitlab-org/ruby/gems/gitlab-fog-azure-rm/-/issues/3 Control: retitle -1 ruby-ms-rest-azure ftbfs with ruby-faraday 2.0 this is unmaintained so should be removed (along with ruby-ms-rest). See

[DRE-maint] Bug#1037465: redmine autopkgtest fails with ruby-rouge 4.1 in experimental

On Tue, 13 Jun 2023 13:03:19 +0530 Pirate Praveen wrote: > Package: redmine > Version: 5.0.4-5 > Severity: important > > Redmine is not compatible with ruby-rouge 4.1 in experimental. > autopkgtest fails with > > Could not find gem 'rouge (~> 3.28)' in cached

[DRE-maint] Bug#1037992: ruby-ms-rest-azure fails similarly

Control: clone 1037992 -1 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#1037992: ruby-ms-rest ftbfs with ruby-faraday 2.x in experimental

Package: ruby-ms-rest Version: Severity: important The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: ruby-faraday (< 2.0.0) but 2.7.1-1 is to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. I'd like to upload

[DRE-maint] Bug#1025097: ruby-asana fails to rebuild after new upstream of ruby-faraday

On Wed, 30 Nov 2022 00:16:43 +0530 Vinay wrote: > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': > Could not find 'faraday' (>= 0.8, < 2.0) - did find: [faraday-2.7.1] > (Gem::MissingSpecVersionError) There is an upstream PR that adds faraday 2.0 support

[DRE-maint] Bug#1037963: rabbit ftbfs/autopkgtest failure with ruby-faraday 2.7 in experimental

Package: rabbit Version: 3.0.0-5 Severity: important Full log attached Started E === Error: test_upload(TestSlideShare): Faraday::Error: :multipart is

[DRE-maint] Bug#1037469: ruby-kramdown-parser-gfm ftbfs with ruby-rouge 4.1 in experimental

Package: ruby-kramdown-parser-gfm Version: 1.1.0-2 Severity: important I'd like to upload ruby-rouge 4.1 to unstable soon. 1) Failure: TestFiles#test_gfm_codeblock_fenced_to_html [/tmp/autopkgtest-lxc.r0kgad0i/downtmp/build.yfB/src/test/test_files.rb:32]: --- expected +++ actual @@ -16,6

[DRE-maint] Bug#1037467: ruby-gollum-lib not compatible with ruby-rouge 4.1

Package: ruby-gollum-lib Version: 4.2.7.10~gitlab.2+dfsg-1 Severity: important /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'rouge' (~> 3.1) - did find: [rouge-4.1.0] full log attached. I'd like to reupload ruby-rouge 4.1 to unstable soon. autopkgtest

Re: [DRE-maint] ruby-aliyun-sdk_0.8.0-1_amd64.changes REJECTED

On Sun, Apr 9 2023 at 06:00:09 PM +00:00:00 +00:00:00, Thorsten Alteholz wrote: Hi, please also mention Mark Adler in your debian/copyright. Fixed and reuploaded. (your Upstream-Contact: looks a bit strange) Missed in the upload, but fixed in git, so will be fixed in next source

Re: [DRE-maint] Comments regarding ruby-ruby-openai_3.7.0-2_amd64.changes

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

[DRE-maint] Bug#1035307: Update ruby-ruby-parser to 3.20.x

Control: reassign ruby3.1 Control: affects ruby-ruby-parser On Thu, 4 May 2023 23:12:08 +0530 Praveen Arimbrathodiyil wrote: > > > On 04/05/23 11:05 pm, Praveen Arimbrathodiyil wrote: > > > > > > On 04/05/23 10:44 pm, Pirate Praveen wrote: > >> Running the

[DRE-maint] Bug#1035307: Update ruby-ruby-parser to 3.20.x

On Sun, 30 Apr 2023 20:35:00 +0530 Praveen Arimbrathodiyil wrote: > Package: ruby-ruby-parser > Version: 3.19.2-1 > Severity: important > > Gitlab 15.11.0 needs ruby-ruby-parser 3.20 and while trying to update > it, the build fails with > > 13) Failure: >

[DRE-maint] Bug#1034565: ftbfs tests fail on ppc64el and mips64el

Package: ruby-prometheus-client-mmap Version: 0.17.0+spec-1 Severity: serious Control: forwarded -1 https://gitlab.com/gitlab-org/ruby/gems/prometheus-client-mmap/-/issues/43 Version in testing is not affected as we did not have tests enabled. Failures: 1)

[DRE-maint] Bug#1032070: fixed in ruby3.1 3.1.2-7~exp

On Wed, 15 Mar 2023 01:05:14 +0530 Pirate Praveen wrote: > Are you planning to upload this to bookworm? We are starting to test > gitlab on bookworm to be able to provide gitlab via bookworm-fasttrack > when bookworm releases. I hit this issue today when testing gitlab on > bookwo

[DRE-maint] Bug#1033374: pre-unblock: ruby-rack/2.2.6.4-1

-2023-27530, CVE-2023-27539) + + -- Pirate Praveen Fri, 24 Mar 2023 01:32:43 +0530 + ruby-rack (2.2.4-3) unstable; urgency=high * Team upload diff -Nru ruby-rack-2.2.4/debian/patches/Fix-ReDoS-in-Rack-Utils.get_byte_ranges.patch ruby-rack-2.2.6.4/debian/patches/Fix-ReDoS-in-Rack

[DRE-maint] Bug#1033331: RM: ruby-omniauth-shibboleth -- ROM; rc-buggy, unmaintained upstream, leaf package

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-omniauth-shibbol...@packages.debian.org Control: affects -1 + src:ruby-omniauth-shibboleth Control: block 999726 by -1 It is affected by rc bug #999726 (incompatible with

[DRE-maint] Bug#999726: ruby-omniauth-shibboleth: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: Failure/Error: expect(last_response.status).to eq(302)

On Tue, 10 May 2022 01:14:01 +0530 Mohd Bilal wrote: > If you feel there's any other > workaround for this please suggest. The upstream hasn't been active and > I dont think they'll have new version anytime soon as discussed in

[DRE-maint] Bug#1019643: ruby-omniauth-oauth2-generic: FTBFS with ruby3.1: ERROR: Test "ruby3.0" failed: Failure/Error: expect(last_response.headers["Location"]).to match(%r{redirect_uri=https%3A%2F%2

Control: forwarded -1 https://gitlab.com/satorix/omniauth-oauth2-generic/-/issues/37 On Mon, 12 Sep 2022 22:08:30 -0300 Antonio Terceiro wrote: > We are about to start the ruby3.1 transition in unstable. While trying to > rebuild ruby-omniauth-oauth2-generic with ruby3.1 enabled, the build

[DRE-maint] Bug#1033218: unblock: ruby-kubeclient/4.9.3-2

/changelog 2023-03-20 12:34:36.0 +0530 @@ -1,3 +1,9 @@ +ruby-kubeclient (4.9.3-2) unstable; urgency=medium + + * Disable tests that checks expired certificates (Closes: #1032551) + + -- Pirate Praveen Mon, 20 Mar 2023 12:34:36 +0530 + ruby-kubeclient (4.9.3-1) unstable; urgency=medium

[DRE-maint] Bug#1033216: unblock: ruby-globalid/0.6.0-2

) unstable; urgency=medium + + * Team Upload + + [ Debian Janitor ] + * Remove constraints unnecessary since buster (oldstable): ++ Build-Depends: Drop versioned constraint on ruby-activesupport. + + [ Pirate Praveen ] + * Fix CVE-2023-22799 (Closes: #1029851) + * Bump Standards-Version

[DRE-maint] Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ruby-asciidoctor-include-...@packages.debian.org Control: affects -1 + src:ruby-asciidoctor-include-ext Please unblock package ruby-asciidoctor-include-ext [ Reason ] This

[DRE-maint] Bug#1033094: RM: ruby-github-api -- ROM; blocks ruby-oauth2 testing migration

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-github-...@packages.debian.org Control: affects -1 + src:ruby-jeweler Control: block 1031441 by -1 ruby-github-api is affected by rc bug #1031441 and incompatible with

[DRE-maint] Bug#1033093: RM: ruby-github-api -- ROM; rc buggy blocks ruby-oauth2 testing migration

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: ruby-github-...@packages.debian.org Control: affects -1 + src:ruby-github-api Control: block 1031441 by -1 This is affected by rc bug #1031441 and incompatible with ruby-oauth2 2.x

[DRE-maint] Bug#1031441: Potential RM candidate ?

On Mon, 13 Mar 2023 23:17:02 +0530 Mohd Bilal wrote: > Hello, > > The upstream[1] for ruby-github-api has been inactive for over 2 years > now and this is affecting other packages like ruby-oauth2[2] and > ruby-faraday[3] from migrating. > > $ reverse-depends -b ruby-github-api >

[DRE-maint] Bug#1032070: fixed in ruby3.1 3.1.2-7~exp

On Sun, 05 Mar 2023 23:35:28 + Debian FTP Masters wrote: > Format: 1.8 > Date: Sun, 05 Mar 2023 17:13:36 -0300 > Source: ruby3.1 > Architecture: source > Version: 3.1.2-7~exp > Distribution: experimental > Urgency: medium > Maintainer: Debian Ruby Team > Changed-By: Antonio Terceiro >

[DRE-maint] Bug#1032070: seems this is included only on 3.2.1

On Mon, 27 Feb 2023 16:53:19 +0530 Pirate Praveen wrote: > Control: affects -1 gitlab Since gitlab is in contrib, as a workaround we are installing openssl 3.0.2 gem in postinst. https://salsa.debian.org/ruby-team/gitlab/-/commit/08fe0d965d01db3f4ece15c664b54c169890eda7 We can rem

[DRE-maint] Bug#1029523: ruby-net-http-persistent want Ruby (~> 2.1)

Control: severity -1 important On Thu, 23 Feb 2023 21:33:31 +0100 Paul Gevers wrote: > Hi, > > On Tue, 24 Jan 2023 00:21:06 +0530 Pirate Praveen > wrote: > > net-http-persistent (~> 3.0, >= 3.0.0) was resolved to 3.1.0, > > which depends on > >

[DRE-maint] Bug#1032070: seems this is included only on 3.2.1

Control: affects -1 gitlab As per https://github.com/ruby/ruby/commit/cd83f5b961dfb5401d601c3b08ff3db9f02a5793 this looks like merged in ruby 3.2.1 Can we cherry-pick this change? ___ Pkg-ruby-extras-maintainers mailing list

[DRE-maint] Bug#1032070: Update openssl gem to 3.0.1 to fix Exception: EVP_PKEY_new_mac_key: malloc failure

Package: libruby3.1 Severity: important Version: 3.1.2-6 While testing gitlab 15.6.8 on experimental, gitlab-rake gitlab:check command failed with following error, Checking Gitaly ... Gitaly: ... Exception: EVP_PKEY_new_mac_key: malloc failure Checking Gitaly ... Finished Looking around

[DRE-maint] Bug#1031518: gem2deb: prefer github.com tarballs in watch file when available

Package: gem2deb severity: wishlist npm2deb does this already and we could do it too when gemspec mentions it the homepage as github. We might have to use the rubygems.org api to find homepage, like npm2deb does. Also using api.github.com can help getting all tags instead of only the latest

[DRE-maint] Bug#1030873: ruby-coffee-script is deprecated, please remove the dependency

Package: ruby-jekyll-coffeescript Version: 1.2.2-3 severity: serious Control: block 1019927 by -1 ruby-coffee-script is deprecated #1019927 and we are trying to remove it from bookworm. coffee command line provided by coffeescript package still works (and using node version via webpack is

[DRE-maint] Bug#1030870: Drop unneeded dependency on ruby-coffee-script

Package: tdiary-core Version: 5.2.3-1 Severity: serious Justification: ruby-coffee-script is deprecated and we want to remove it in bookworm Control: block 1019927 by -1 ruby-coffee-script is deprecated (#1019927) and we'd like to remove it from bookworm (this and ruby-jekyll-coffeescript are

[DRE-maint] Bug#1019927: Remove ruby-coffee-script - deprecated upstream

On Fri, 16 Sep 2022 16:38:52 +0530 Pirate Praveen wrote: > As per upstream [1], this project is deprecated and last release was on > Apr 7, 2015 (7 years ago), so I think we should try to remove it from > bookworm, but if we can't get there close to freeze, we can ask for > boo

[DRE-maint] Bug#1019924: Remove build dependency on ruby-blade

Control: rettile -1 remove ruby-coffee-script* dependencies Control: reassign -1 src:ruby-blade On Fri, 16 Sep 2022 16:13:41 +0530 Pirate Praveen wrote: > Package: src:rails > Version: 2:6.1.7+dfsg-1 > Severity: important > Control: forwarded -1 https://github.com/rails/rail

[DRE-maint] Bug#1019731: Suggested fix

Utkarsh suggested this change will fix this bug, we need to test it before we add to the gitlab package. diff --git a/config/application.rb b/config/application.rb index 249db9c6a6..e7481e12e1 100644 --- a/config/application.rb +++ b/config/application.rb @@ -234,6 +234,12 @@ class Application

[DRE-maint] Bug#1005628: add fixed version info

Control: fixed -1 5.2.0+dfsg-2 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#1030774: ruby-omniauth-auth0: Update to new upstream version 3.1.0

Package: ruby-omniauth-auth0 Version: 2.0.0-1 severity: wishlist Control: forwarded -1 https://github.com/auth0/omniauth-auth0/issues/162 One test is failing but can't figure out why yet, asking upstream at https://github.com/auth0/omniauth-auth0/issues/162

[DRE-maint] Bug#981878: ruby-gitlab-pg-query downloads from the internet during the build

On Tue, 22 Feb 2022 21:16:22 +0100 Paul Gevers wrote: > Hi Pirate, > > On Sun, 07 Mar 2021 00:47:46 +0530 Pirate Praveen > wrote: > > Once ruby-pg-query is accepted > > and its reverse dependencies switch to the new package, I will request > > removal of this

[DRE-maint] Bug#1019927: Remove ruby-coffee-script - deprecated upstream

May be with rails 7.1, we may be able to remove coffee_script https://github.com/rails/rails/issues/46292#issuecomment-1332882941 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net

[DRE-maint] Bug#1030692: RM: ruby-coffee-rails -- ROM; unmaintained upstream (recommends using the node module directly via webpack)

Package: ftp.debian.org Control: affects -1 + src:ruby-coffee-rails X-Debbugs-Cc: ruby-coffee-ra...@packages.debian.org User: ftp.debian@packages.debian.org Usertags: remove Severity: normal ruby-coffee-script is deprecated (rc bug #1019927) and ruby-coffee-rails is a leaf package depending

[DRE-maint] Bug#1029523: there is a new upstream major version that relaxes ruby requirement

so updating to 4.0.1 could fix this https://github.com/drbrain/net-http-persistent/blob/75574f2546a08aa2663b06a2e005bcf2ee304f13/Rakefile#L16 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net

[DRE-maint] Bug#1029523: ruby-net-http-persistent want Ruby (~> 2.1)

Package: ruby-net-http-persistent Severity: grave Justification: unable to install gitlab or use with bundler Just add this to Gemfile. gem "telesign" and run, bundle install --local Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will

[DRE-maint] Bug#1029498: gem2deb should simplify the copy and symlink of assets

Package: gem2deb Severity: wishlist Currently for many ruby packages (rails engines) that ships a javascript asset, we have to manually copy the asset before build and replace it with a symlink after install. It'd be nice if gem2deb can automate these manual steps with a mapping file. This

[DRE-maint] Bug#964607: Massive update necessary

On Thu, 25 Nov 2021 18:54:24 +0100 Daniel Leidert wrote: > This gem is out-of-date. Upstream is at 3.2.2, which requires packaging for > google-cloud-translate-v2 and google-cloud-translate-v3 and updating google- > cloud-core to >= 1.6. The tests require packageing google-style. This is a

[DRE-maint] Bug#1020913: looks like a temporary issue during ruby 3.1 transition

Control: fixed -1 2.2.0-1 likely caused by ruby-google-protobuf in experimental not being rebuilt with ruby 3.1. This built fine in buildd after ruby-google-protobuf was reuploaded to unstable. ___ Pkg-ruby-extras-maintainers mailing list

[DRE-maint] Bug#1028730: fixed in last upload and built on buildd

Control: fixed -1 1.7.0+dfsg-6 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#1029387: Fix smoke-test for ruby-leaflet-rails

Package: ruby-leaflet-rails Version: 1.6.0+dfsg-3 Severity: important + bundle exec rake assets:precompile config.eager_load is set to nil. Please update your config/environments/*.rb files accordingly: * development - set it to false * test - set it to false (unless you use a tool that

[DRE-maint] Bug#799058: libjs-jquery-fullscreen-plugin should be in section 'web', not 'ruby'

Control: fixed -1 0.5.0+dfsg-2 On Tue, 15 Sep 2015 11:05:14 + Damyan Ivanov wrote: > Package: libjs-jquery-fullscreen-plugin > Version: 0.5.0+dfsg-1 > Severity: minor > Tags: patch > > Hi, > > libjs-jquery-fullscreen-plugin containt a jQuery plugin, but is in section > 'ruby', perhaps

[DRE-maint] Bug#925554: this was fixed long ago

Control: fixed -1 0.5.0+dfsg-2 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#1005631: new restriction in rubygems: installing symlink pointing to parent path not allowed - causes ruby-handlebars-assets to ftbfs

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.

[DRE-maint] Bug#1028285: ruby-aws-sdk-core version is broken

Package: ruby-aws-sdk-core Version: 3.168.1-1 Severity: grave Control: forwarded -1 We don't need this patch, this was likely created before gem-install layout.

[DRE-maint] Bug#1024627: Acknowledgement (gitlab: Fails to install)

On Tue, Nov 22 2022 at 02:39:40 PM +01:00:00 +01:00:00, Kurt Roeckx wrote: fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version from backports is too new it seems, and it what gets installed when you just do: apt install gitlab Some of the version requirements for

[DRE-maint] Bug#1024631: gitlab: preinst: invalid number 9.1

On Tue, Nov 22 2022 at 02:27:05 PM +01:00:00 +01:00:00, Kurt Roeckx wrote: Package: gitlab Version: 15.4.2+ds1-1~fto11+3 On install I get: /var/lib/dpkg/tmp.ci/preinst: 7 [: Illagal number: 9.1 I have several postgresql clusters, 9.1, 9.6, 12, 14. Not all of them are used. 9.1 is using

Re: [DRE-maint] Redmine ActionView::Template::Error after recent Rails security update

On വ്യാ, സെപ്റ്റം 8, 2022 at 12:30 വൈകു, Lucas Kanashiro wrote: Thanks for all the information you provided. The rails maintainer is working to fix that, this issue is not impacting only redmine but some other packages. So let's wait for them before thinking about any redmine specific

[DRE-maint] Bug#1015302: Upgrading 14.10.5 to 15.0.4 aborts on db:migrate

2022, ജൂലൈ 19 12:05:37 PM GMT+02:00, "Patrick Matthäi" ൽ എഴുതി >Package: gitlab >Version: 15.0.4+ds1-1 >Severity: serious > >Hey, > >on upgrading gitlab I always end up with this error: > >(1055 rows) = Did not find any relations. ] >+ echo gitlab_production database is not empty, skipping

Re: [DRE-maint] ruby-gitlab-license-finder_6.14.2.1-1_amd64.changes REJECTED

2022, ജനുവരി 22 11:30:08 PM IST, Thorsten Alteholz ൽ എഴുതി > >Hi, > >please mention Twitter as copyright holder for bootstrap in your >debian/copyright. Fixed and reuploaded. >Thanks! > Thorsten > > > >=== > >Please feel free to respond to this email if you don't understand why >your files

Re: [DRE-maint] ruby-mdurl-rb_1.0.5-1_amd64.changes REJECTED

On വ്യാ, ഒക്ടോ 7 2021 at 11:06:47 രാവിലെ + +, VIVEK K J wrote: ‐‐‐ Original Message ‐‐‐ On Wednesday, October 6th, 2021 at 10:38 PM, Pirate Praveen wrote: On 6 October 2021 11:54:51 am IST, VIVEK K J vive...@protonmail.com wrote: > Hi, > > Pushed the

Re: [DRE-maint] ruby-uc.micro-rb_1.0.5-1_amd64.changes REJECTED

On 6/10/21 11:48 AM, VIVEK K J wrote: > Hi, > > Thank you for pointing the issue. They've using WTFPL license in the > gemspec file. But in their source code (i.e. GitHub Repository) they are > using license text of expat[1] and they updated their gemspec file to use MIT > expat license[2]

Re: [DRE-maint] ruby-mdurl-rb_1.0.5-1_amd64.changes REJECTED

On 6 October 2021 11:54:51 am IST, VIVEK K J wrote: >Hi, > >Pushed the requested changes. I think you should mention the files where these notices are found as well. >Thanks, >Vivek K J >‐‐‐ Original Message ‐‐‐ > >On Tuesday, October 5th, 2021 at 11:30 PM, Thorsten Alteholz > wrote:

[DRE-maint] Bug#995906: gitlab: Upgrading buster to bullseye needs some more gitlab-apt-pin-preferences adjustments

On 8 October 2021 11:23:05 am IST, "Patrick Matthäi" wrote: >Package: gitlab >Version: 14.1.7+ds1-2~fto11+1 >Severity: important > >Hi, > >I am just upgrading our buster gitlab (13.12.8+ds1-1~fto10+1) to bullseye >(14.1.7+ds1-2~fto11+1) >along with the whole system. >On upgrading I get some

  1   2   3   4   5   >