Your message dated Mon, 19 Aug 2019 17:11:46 -0700 with message-id <capqicoxuf_0o5nqlms5wourwjaazbnr-bxo0o+s6xzv2ocg...@mail.gmail.com> and subject line Closing as not reproducible currently has caused the Debian Bug report #899307, regarding ruby-sequel-pg: All SELECT ::Dataset methods fails with FrozenError 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.) -- 899307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: ruby-sequel-pg Version: 1.6.16-1+b2 Severity: grave Justification: renders package unusable All SELECT methods like all,first,each,... fails with FrozenError. Example: irb(main):007:0> DB => #<Sequel::Postgres::Database: {:adapter=>"postgres", :database=>"xxx", :user=>"xxx", :password=>"xxx", :host=>"127.0.0.1"}> irb(main):008:0> DB[:events].first Traceback (most recent call last): 16: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:688:in `single_record' 15: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:700:in `single_record!' 14: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:947:in `with_sql_first' 13: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:939:in `with_sql_each' 12: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:569:in `fetch_rows' 11: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:1085:in `execute' 10: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:273:in `execute' 9: from /usr/lib/ruby/vendor_ruby/sequel/database/connecting.rb:269:in `synchronize' 8: from /usr/lib/ruby/vendor_ruby/sequel/connection_pool/threaded.rb:91:in `hold' 7: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:273:in `block in execute' 6: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:477:in `check_database_errors' 5: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:273:in `block (2 levels) in execute' 4: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:455:in `_execute' 3: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:135:in `execute' 2: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:569:in `block in fetch_rows' 1: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:569:in `yield_hash_rows' FrozenError (can't modify frozen Sequel::Postgres::Dataset) But irb(main):017:0> DB[:events].delete => 0 P.S. * With mysql2 apapter it is ok. * In Debian 9 Stretch, too, everything is fine, both mysql2 and postgres. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-sequel-pg depends on: ii libc6 2.27-3 ii libgmp10 2:6.1.2+dfsg-3 ii libpq5 10.3-2 ii libruby2.5 2.5.1-1+b1 ii ruby 1:2.5.1 ii ruby-pg 0.19.0-2+b1 ii ruby-sequel 5.6.0-1 ruby-sequel-pg recommends no packages. ruby-sequel-pg suggests no packages.
--- End Message ---
--- Begin Message ---Control: notfound -1 ruby-sequel-pg/1.6.16-1+b2 Hi, As we're not able to reproduce that bug currently in Debian, I'm going to go ahead and close it. I'm currently preparing the upload of the latest version of that package so I don't really want what looks like an old conflict with a dependency prevent the new version from going to testing. If the bug is still there in Ubuntu it would be interesting to see what difference of versions you have there for ruby-sequel and pg. And also it would be good to test with that new version once it reaches Ubuntu. Do you have a similar bug report open in Ubuntu? Thanks, Joseph
--- End Message ---
