Processed: Re: Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15
Processing control commands: > reassign -1 dbconfig-common Bug #1021791 [src:redmine] Testsuite needs updated permissions with PostgreSQL 15 Bug reassigned from package 'src:redmine' to 'dbconfig-common'. No longer marked as found in versions redmine/5.0.2-2. Ignoring request to alter fixed versions of bug #1021791 to the same values previously set > affects -1 src:redmine Bug #1021791 [dbconfig-common] Testsuite needs updated permissions with PostgreSQL 15 Added indication that 1021791 affects src:redmine -- 1021791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15
Control: reassign -1 dbconfig-common Control: affects -1 src:redmine On Fri, 14 Oct 2022 21:37:02 +0200 Christoph Berg wrote: Re: To Debian Bug Tracking System > redmine needs updating for this; one workaround for the testsuite > would be to "grant create on schema public to public;" to revert to > the old default. It's not the testsuite failing; it's already the postinst failing to install redmine. I think it's pretty clear that this should be solved in dbconfig-common. I'm already working on a fix. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15
Re: To Debian Bug Tracking System > redmine needs updating for this; one workaround for the testsuite > would be to "grant create on schema public to public;" to revert to > the old default. It's not the testsuite failing; it's already the postinst failing to install redmine. Christoph
Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15
Source: redmine
Version: 5.0.2-2
Severity: serious
PostgreSQL 15 restricts the CREATE privilege on the default "public"
schema in each database to the database owner; previous all users were
allowed to create new objects.
redmine needs updating for this; one workaround for the testsuite
would be to "grant create on schema public to public;" to revert to
the old default.
https://ci.debian.net/data/autopkgtest/testing/arm64/r/redmine/27072176/log.gz
Setting up redmine (5.0.2-2) ...
[33mDon't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.[0m
dbconfig-common: writing config to
/etc/dbconfig-common/redmine/instances/default.conf
creating postgres user redmine/instances/default: already exists.
resetting password: success.
creating database redmine_default: already exists.
dbconfig-common: flushing administrative password
rake aborted!
ActiveRecord::StatementInvalid: PG::InsufficientPrivilege: ERROR: permission
denied for schema public
LINE 1: CREATE TABLE "schema_migrations" ("version" character varyin...
^
/usr/share/rubygems-integration/all/gems/activerecord-6.1.7/lib/active_record/connection_adapters/postgresql/database_statements.rb:49:in
`exec'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.7/lib/active_record/connection_adapters/postgresql/database_statements.rb:49:in
`block (2 levels) in execute'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies/interlock.rb:48:in
`block in permit_concurrent_loads'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/concurrency/share_lock.rb:187:in
`yield_shares'
(Possibly this might need fixing in dbconfig-common.)
Christoph
