Your message dated Tue, 11 Feb 2025 14:54:04 -0700
with message-id <2711391.CFs8Y8CuNP@soren-desktop>
and subject line Re: Bug#606983: redmine: needs a way to run as a separate user
per instance
has caused the Debian Bug report #606983,
regarding redmine: needs a way to run as a separate user per instance
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 [email protected]
immediately.)
--
606983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606983
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: redmine
Version: 1.0.1-1
Severity: normal
I have configured redmine to use a specific instance, separate of the "default"
one. It is named "koumbit" and has configuration in /etc/redmine/koumbit
During the upgrade, it seems that the session configuration is not updated
properly. I was getting an error similar to this one:
http://www.redmine.org/boards/2/topics/11085
To work around the issue, I did the following steps:
# chown redmine /etc/redmine/koumbit/session.yml
# su -s /bin/sh redmine
$ env X_DEBIAN_SITEID=koumbit RAILS_ENV=production rake generate_session_store
(in /usr/share/redmine)
$ env X_DEBIAN_SITEID=koumbit RAILS_ENV=production rake db:migrate
(in /usr/share/redmine)
== AddIndexOnChangesetsScmid: migrating ======================================
[...]
$ exit
# chown root /etc/redmine/koumbit/session.yml
Once that was done, the errors went away. Note that the session.yml was
readable and accessed by the web interface, so that wasn't the problem. It just
wasn't generated properly (even though debconf prompted me to replace the
file).
Also note that I chown redmine and su redmine because I isolated my redmine
instance using passenger user switching, so this could be "www-data" instead of
"redmine" for you.
-- System Information:
Debian Release: 5.0.7
APT prefers stable
APT policy: (500, 'stable'), (2, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-vserver-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages redmine depends on:
ii dbconfig-common 1.8.39 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libactionmailer-ruby 2.3.5-1~bpo50+1 Framework for generation of custom
ii libactionpack-ruby 2.3.5-1~bpo50+1 Controller and View framework used
ii libactiveresource-ruby 2.3.5-1~bpo50+1 Connects objects and REST web serv
ii libactivesupport-ruby 2.3.5-1~bpo50+1 utility classes and extensions (Ru
ii libjs-scriptaculous 1.8.3-1~bpo50+1 JavaScript library for dynamic web
ii rails 2.3.5-1~bpo50+1 MVC ruby based framework geared fo
ii redmine-mysql 0.9.1-1~bpo50+1 metapackage providing MySQL depend
ii ruby 4.2 An interpreter of object-oriented
ii ruby1.8 1.8.7.72-3lenny1 Interpreter of object-oriented scr
redmine recommends no packages.
Versions of packages redmine suggests:
ii libopenid-ruby 2.1.2debian-1 Ruby library for verifying and ser
pn librmagick-ruby <none> (no description available)
pn libsvn-ruby <none> (no description available)
-- debconf information:
redmine/instances/default/db/app-user: redmine
redmine/instances/default/passwords-do-not-match:
redmine/instances/default/remote/newhost:
redmine/instances/default/db/basepath:
redmine/notify-migration:
redmine/old-instances:
redmine/instances/default/upgrade-error: abort
redmine/instances/default/pgsql/changeconf: false
redmine/instances/default/missing-db-package-error: abort
redmine/instances/default/db/dbname: redmine_default
redmine/instances/default/purge: false
redmine/current-instances: default
redmine/instances/default/remote/host:
redmine/default-language: ${defaultLocale}
redmine/instances/default/dbconfig-upgrade: true
redmine/instances/default/pgsql/no-empty-passwords:
redmine/instances/default/internal/reconfiguring: false
redmine/instances/default/upgrade-backup: true
redmine/instances/default/pgsql/method: unix socket
redmine/instances/default/install-error: abort
redmine/instances/default/mysql/admin-user: root
redmine/instances/default/database-type:
redmine/instances/default/pgsql/manualconf:
redmine/instances/default/pgsql/authmethod-admin: ident
redmine/instances/default/mysql/method: unix socket
redmine/instances/default/internal/skip-preseed: true
redmine/instances/default/pgsql/admin-user: postgres
redmine/instances/default/remove-error: abort
redmine/instances/default/dbconfig-remove:
redmine/missing-redmine-package:
redmine/instances/default/remote/port:
redmine/instances/default/pgsql/authmethod-user: password
* redmine/instances/default/dbconfig-install: false
redmine/instances/default/dbconfig-reinstall: false
--- End Message ---
--- Begin Message ---
Antoine,
On Tuesday, February 11, 2025 2:52:22 PM MST Antoine Beaupré wrote:
> I don't really use redmine anymore, so I can't speak to that issue or
> any other issue in the redmine debian package, I'm sorry.
Thank you for your quick response.
I am going to close this bug for now, but if someone else has this issue they
should feel free to reopen it or to create a new bug report.
--
Soren Stoutner
[email protected]
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
