[DRE-maint] ruby-gitlab is marked for autoremoval from testing
ruby-gitlab 4.17.0-3 is marked for autoremoval from testing on 2022-12-13 It (build-)depends on packages with these RC bugs: 1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019631 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-httparty is marked for autoremoval from testing
ruby-httparty 0.20.0-1 is marked for autoremoval from testing on 2022-12-13 It is affected by these RC bugs: 1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019631 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-flowdock is marked for autoremoval from testing
ruby-flowdock 0.7.1-1 is marked for autoremoval from testing on 2022-12-13 It (build-)depends on packages with these RC bugs: 1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019631 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-mobile-fu is marked for autoremoval from testing
ruby-mobile-fu 1.4.0+github-4 is marked for autoremoval from testing on 2022-12-13 It (build-)depends on packages with these RC bugs: 1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019631 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-otr-activerecord is marked for autoremoval from testing
ruby-otr-activerecord 2.0.3-3 is marked for autoremoval from testing on 2022-11-29 It is affected by these RC bugs: 1019645: ruby-otr-activerecord: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: [31mArgumentError:[0m https://bugs.debian.org/1019645 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-heapy is marked for autoremoval from testing
ruby-heapy 0.2.0-1 is marked for autoremoval from testing on 2022-12-13 It is affected by these RC bugs: 1019629: ruby-heapy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019629 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-gitlab-flowdock-git-hook is marked for autoremoval from testing
ruby-gitlab-flowdock-git-hook 1.0.1-4 is marked for autoremoval from testing on 2022-12-13 It (build-)depends on packages with these RC bugs: 1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019631 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-hipchat is marked for autoremoval from testing
ruby-hipchat 1.5.2-3.1 is marked for autoremoval from testing on 2022-12-13 It (build-)depends on packages with these RC bugs: 1019631: ruby-httparty: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019631 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-grape is marked for autoremoval from testing
ruby-grape 1.6.2-1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019626 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-fog-google is marked for autoremoval from testing
ruby-fog-google 1.15.0-3 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-derailed-benchmarks is marked for autoremoval from testing
ruby-derailed-benchmarks 1.7.0-2 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019629: ruby-heapy: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019629 1019638: ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. https://bugs.debian.org/1019638 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-google-api-client is marked for autoremoval from testing
ruby-google-api-client 0.50.0-2 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-memoizable is marked for autoremoval from testing
ruby-memoizable 0.4.2-2 is marked for autoremoval from testing on 2022-11-23
It is affected by these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] ruby-grape-entity is marked for autoremoval from testing
ruby-grape-entity 0.10.1-3 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019626 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-sixarm-ruby-unaccent is marked for autoremoval from testing
ruby-sixarm-ruby-unaccent 1.2.0-2 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019668: ruby-sixarm-ruby-unaccent: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in `start': coverage measurement is already setup (RuntimeError) https://bugs.debian.org/1019668 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-grape-path-helpers is marked for autoremoval from testing
ruby-grape-path-helpers 1.7.1-1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019626 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-uniform-notifier is marked for autoremoval from testing
ruby-uniform-notifier 1.13.0-2 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019673: ruby-uniform-notifier: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: require 'ruby-growl' https://bugs.debian.org/1019673 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-ice-cube is marked for autoremoval from testing
ruby-ice-cube 0.16.4-1 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019632: ruby-ice-cube: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(YAML.load(symbol_yaml)).to eq(YAML.load(string_yaml)) https://bugs.debian.org/1019632 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-icalendar is marked for autoremoval from testing
ruby-icalendar 2.8.0-1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019632: ruby-ice-cube: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(YAML.load(symbol_yaml)).to eq(YAML.load(string_yaml)) https://bugs.debian.org/1019632 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-grape-logging is marked for autoremoval from testing
ruby-grape-logging 1.8.4-1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019626 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-kitchen-docker is marked for autoremoval from testing
ruby-kitchen-docker 2.10.0-1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019683: test-kitchen: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: "#". https://bugs.debian.org/1019683 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-kitchen-salt is marked for autoremoval from testing
ruby-kitchen-salt 0.7.0-1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019683: test-kitchen: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: "#". https://bugs.debian.org/1019683 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-proc-to-ast is marked for autoremoval from testing
ruby-proc-to-ast 0.1.0-2 is marked for autoremoval from testing on 2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] ruby-memory-profiler is marked for autoremoval from testing
ruby-memory-profiler 0.9.14-4 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019638: ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. https://bugs.debian.org/1019638 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-morpher is marked for autoremoval from testing
ruby-morpher 0.2.6-2 is marked for autoremoval from testing on 2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] ruby-countries is marked for autoremoval from testing
ruby-countries 3.0.0-2 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019668: ruby-sixarm-ruby-unaccent: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in `start': coverage measurement is already setup (RuntimeError) https://bugs.debian.org/1019668 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-representable is marked for autoremoval from testing
ruby-representable 3.0.4-1.1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-active-model-serializers is marked for autoremoval from testing
ruby-active-model-serializers 0.10.12-1 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019626 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-rspec-parameterized is marked for autoremoval from testing
ruby-rspec-parameterized 0.4.2-2 is marked for autoremoval from testing on
2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] ruby-benchmark-memory is marked for autoremoval from testing
ruby-benchmark-memory 0.1.2-3 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019638: ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. https://bugs.debian.org/1019638 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-omniauth-auth0 is marked for autoremoval from testing
ruby-omniauth-auth0 2.0.0-1 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019641: ruby-omniauth-auth0: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(last_response.status).to eq(302) https://bugs.debian.org/1019641 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-unparser is marked for autoremoval from testing
ruby-unparser 0.4.7-2 is marked for autoremoval from testing on 2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] ruby-virtus is marked for autoremoval from testing
ruby-virtus 1.0.5-3.1 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-twitter is marked for autoremoval from testing
ruby-twitter 7.0.0-1 is marked for autoremoval from testing on 2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] test-kitchen is marked for autoremoval from testing
test-kitchen 1.23.2-6 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019683: test-kitchen: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: "#". https://bugs.debian.org/1019683 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-adamantium is marked for autoremoval from testing
ruby-adamantium 0.2.0-3 is marked for autoremoval from testing on 2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] ruby-bullet is marked for autoremoval from testing
ruby-bullet 6.1.0-2 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019673: ruby-uniform-notifier: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: require 'ruby-growl' https://bugs.debian.org/1019673 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-anima is marked for autoremoval from testing
ruby-anima 0.3.2-1 is marked for autoremoval from testing on 2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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] ruby-api-pagination is marked for autoremoval from testing
ruby-api-pagination 4.8.2-2 is marked for autoremoval from testing on 2022-11-23 It (build-)depends on packages with these RC bugs: 1019626: ruby-grape-entity: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: https://bugs.debian.org/1019626 1019676: ruby-virtus: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Expected \"not a hash, really\" to respond to #to_hash", got #https://bugs.debian.org/1019676 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-invisible-captcha is marked for autoremoval from testing
ruby-invisible-captcha 1.1.0-5 is marked for autoremoval from testing on 2022-11-23 It is affected by these RC bugs: 1019633: ruby-invisible-captcha: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp https://bugs.debian.org/1019633 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl ___ 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] ruby-concord is marked for autoremoval from testing
ruby-concord 0.1.5-3 is marked for autoremoval from testing on 2022-11-23
It (build-)depends on packages with these RC bugs:
1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
https://bugs.debian.org/1019637
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
___
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#1004654: marked as done (ruby-rack-mount: FTBFS with ruby-rack 2.2.3 "http://josh.backpackit.com/host">(UTF-8) expected but was <"http://example.org/host">(ASCII-8BIT))
Your message dated Wed, 16 Nov 2022 01:18:46 +
with message-id
and subject line Bug#1018910: Removed package(s) from unstable
has caused the Debian Bug report #1004654,
regarding ruby-rack-mount: FTBFS with ruby-rack 2.2.3
"http://josh.backpackit.com/host";>(UTF-8) expected but was
<"http://example.org/host";>(ASCII-8BIT)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1004654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rack-mount
Version: 0.8.3-3
Severity: serious
ruby-rack-mount now ftbfs and fails autopkgtest with ruby-rack 2.2.3
test_generate_host: F
===
Failure: test_generate_host(TestGeneration)
/<>/test/test_generation.rb:74:in `test_generate_host'
71: assert_equal ['josh.backpackit.com', {}], @app.generate(:host,
:controller => 'account', :account => 'josh')
72: assert_equal [{:host => 'josh.backpackit.com', :path_info =>
'/host'}, {}], @app.generate(:all, :controller => 'account', :account
=> 'josh')
73: assert_equal [{:request_method => 'GET', :path_info =>
'/login'}, {}], @app.generate(:all, :login)
=> 74: assert_equal 'http://josh.backpackit.com/host', @app.url(@env,
:controller => 'account', :account => 'josh')
75: end
76:
77: def test_generate_full_url
<"http://josh.backpackit.com/host";>(UTF-8) expected but was
<"http://example.org/host";>(ASCII-8BIT)
diff:
? http://j osh.backpackit.com/host
? example. rg
? Encoding: UTF -8
? ASCII BIT
===
: (0.007321)
full log
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-rack-mount/18822994/log.gz
(same error in clean build too)
This is now a leaf package, the package that build dependended on it no
longer use it and it is not maintained upstream.
I think we can safely request its removal if no one wants to fix this
bug
https://lists.debian.org/debian-ruby/2022/01/msg00019.html
--- End Message ---
--- Begin Message ---
Version: 0.8.3-3+rm
Dear submitter,
as the package ruby-rack-mount has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1018910
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
___
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#1018910: Removed package(s) from unstable
Version: 0.8.3-3+rm Dear submitter, as the package ruby-rack-mount has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1018910 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) ___ 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#1018910: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: ruby-rack-mount |0.8.3-3 | source, all --- Reason --- ROM; abandoned upstream -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1018...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1018910 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain) ___ 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#1024177: cannot use plugin due to incompatibility?
Package: ruby-jekyll-feed Version: 0.15.1-2 I'm using jekyll with those plugins in `_config.yml`: plugins: - jekyll-sitemap - jekyll-feed I get this error: Dependency Error: Yikes! It looks like you don't have jekyll-feed or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. The full error message from Ruby is: 'Unable to activate jekyll-3.9.0, because liquid-5.4.0 conflicts with liquid (~> 4.0), mercenary-0.4.0 conflicts with mercenary (~> 0.3.3)' If you run into trouble, you can find helpful resources at https://jekyllrb.com/help/! jekyll 3.9.0 | Error: jekyll-feed /usr/lib/ruby/vendor_ruby/jekyll/external.rb:68:in `rescue in block in require_with_graceful_fail': jekyll-feed (Jekyll::Errors::MissingDependencyException) from /usr/lib/ruby/vendor_ruby/jekyll/external.rb:56:in `block in require_with_graceful_fail' from /usr/lib/ruby/vendor_ruby/jekyll/external.rb:55:in `each' [snip backtrace] /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in `raise_if_conflicts': Unable to activate jekyll-3.9.0, because liquid-5.4.0 conflicts with liquid (~> 4.0), mercenary-0.4.0 conflicts with mercenary (~> 0.3.3) (Gem::ConflictError) [snip backtrace] /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in `raise_if_conflicts': Unable to activate jekyll-3.9.0, because liquid-5.4.0 conflicts with liquid (~> 4.0), mercenary-0.4.0 conflicts with mercenary (~> 0.3.3) (Gem::ConflictError) [snip backtrace] :85:in `require': cannot load such file -- jekyll-feed (LoadError) Did you mean? jekyll [snip backtrace] This is what's installed: jekyll 3.9.0+dfsg-5 ruby-jekyll-feed 0.15.1-2 ruby-jekyll-sass-converter 1.5.2-3 ruby-jekyll-sitemap 1.4.0-2 ruby-jekyll-watch2.2.1-1 ruby-liquid 5.4.0-2 ruby-mercenary 0.4.0-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#1024174: ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1)
Source: ruby-omniauth-dingtalk-oauth2 Version: 1.0.0-2 Severity: serious X-Debbugs-CC: ruby-omniauth-oau...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-omniauth-oauth2 Dear maintainer(s), With a recent upload of ruby-omniauth-oauth2 the autopkgtest of ruby-omniauth-dingtalk-oauth2 fails in testing when that autopkgtest is run with the binary packages of ruby-omniauth-oauth2 from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-omniauth-oauth2from testing1.8.0-1 ruby-omniauth-dingtalk-oauth2 from testing1.0.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby-omniauth-oauth2 to testing [1]. Of course, ruby-omniauth-oauth2 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-omniauth-oauth2 was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-omniauth-oauth2 should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-omniauth-oauth2 https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-omniauth-dingtalk-oauth2/28323424/log.gz ┌──┐ │ Checking Rubygems dependency resolution on ruby3.0 │ └──┘ GEM_PATH= ruby3.0 -e gem\ \"omniauth-dingtalk-oauth2\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'omniauth-oauth2' (~> 1.7.1) among 105 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' at: /usr/share/rubygems-integration/all/specifications/omniauth-dingtalk-oauth2-1.0.0.gemspec, execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'omniauth-oauth2' (~> 1.7.1) - did find: [omniauth-oauth2-1.8.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' , execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' abbrev (default: 0.1.0) base64 (default: 0.1.0) benchmark (default: 0.1.1) bigdecimal (default: 3.0.0) bundler (default: 2.2.33) cgi (default: 0.2.1) csv (default: 3.1.9) date (default: 3.1.3) dbm (default: 1.1.0) debug (default: 0.2.1) delegate (default: 0.2.0) did_you_mean (default: 1.5.0) digest (default: 3.0.0) drb (default: 2.0.5) english (default: 0.7.1) erb (default: 2.2.0) etc (
[DRE-maint] Processed: ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1
Processing control commands: > affects -1 src:ruby-omniauth-oauth2 Bug #1024175 [src:ruby-omniauth-gitlab] ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1 Added indication that 1024175 affects src:ruby-omniauth-oauth2 -- 1024175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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#1024175: ruby-omniauth-gitlab: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1
Source: ruby-omniauth-gitlab Version: 4.0.0-1 Severity: serious X-Debbugs-CC: ruby-omniauth-oau...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-omniauth-oauth2 Dear maintainer(s), With a recent upload of ruby-omniauth-oauth2 the autopkgtest of ruby-omniauth-gitlab fails in testing when that autopkgtest is run with the binary packages of ruby-omniauth-oauth2 from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-omniauth-oauth2 from testing1.8.0-1 ruby-omniauth-gitlab from testing4.0.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of ruby-omniauth-oauth2 to testing [1]. Of course, ruby-omniauth-oauth2 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-omniauth-oauth2 was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-omniauth-oauth2 should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-omniauth-oauth2 https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-omniauth-gitlab/28323425/log.gz ┌──┐ │ Checking Rubygems dependency resolution on ruby3.0 │ └──┘ GEM_PATH= ruby3.0 -e gem\ \"omniauth-gitlab\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'omniauth-oauth2' (~> 1.7.1) among 119 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' at: /usr/share/rubygems-integration/all/specifications/omniauth-gitlab-4.0.0.gemspec, execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'omniauth-oauth2' (~> 1.7.1) - did find: [omniauth-oauth2-1.8.0] (Gem::MissingSpecVersionError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0' , execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' OpenPGP_signature Description: OpenPGP digital signature ___ 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] Processed: ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1)
Processing control commands: > affects -1 src:ruby-omniauth-oauth2 Bug #1024174 [src:ruby-omniauth-dingtalk-oauth2] ruby-omniauth-dingtalk-oauth2: autopkgtest needs update for new version of ruby-omniauth-oauth2: Could not find 'omniauth-oauth2' (~> 1.7.1) Added indication that 1024174 affects src:ruby-omniauth-oauth2 -- 1024174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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#1024143: gitlab: postinst fails silently within rake-tasks, if /var/lib/gitlab/.cache/yarn/v6 does not exist
Package: gitlab
Version: 15.2.3+ds1-2~fto11+1
Severity: normal
Tags: patch
Dear Maintainer,
during gitlab's package installation, the following line in
`rake-tasks.sh` causes a failure of the postinst processing:
> -runuser -u ${gitlab_user} -- sh -c 'test -d "/var/lib/gitlab/.cache/yarn/v6"
> && find /var/lib/gitlab/.cache/yarn/v6/ -name .yarn-metadata.json -perm -a=w
> -exec chmod 644 {} \;'
The above fails, if the directory does not exists.
Due to the shell's exit-on-error (`set -e`), this failure is fatal.
Attached you find a patch, which ensures the proper exitcode for the
line above.
Cheers,
Lars
--- /usr/lib/gitlab/scripts/rake-tasks.sh.orig 2022-11-15 05:16:06.185030967
+0100
+++ /usr/lib/gitlab/scripts/rake-tasks.sh 2022-11-15 05:16:32.504552974
+0100
@@ -45,7 +45,7 @@
runuser -u ${gitlab_user} -- sh -c 'if ! grep nodeLinker .yarnrc.yml
>/dev/null; then echo "nodeLinker: \"node-modules\"" >>.yarnrc.yml; fi'
runuser -u ${gitlab_user} -- sh -c 'yarnpkg install'
# Remove write permissions of .yarn-metadata.json files
-runuser -u ${gitlab_user} -- sh -c 'test -d "/var/lib/gitlab/.cache/yarn/v6"
&& find /var/lib/gitlab/.cache/yarn/v6/ -name .yarn-metadata.json -perm -a=w
-exec chmod 644 {} \;'
+runuser -u ${gitlab_user} -- sh -c 'if test -d
"/var/lib/gitlab/.cache/yarn/v6"; then find /var/lib/gitlab/.cache/yarn/v6/
-name .yarn-metadata.json -perm -a=w -exec chmod 644 {} \;; fi'
cd /usr/share/gitlab
___
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
