Your message dated Mon, 10 Mar 2025 07:00:34 -0700
with message-id <12354070.zAa99ISigo@soren-desktop>
and subject line redmine: sql_for_field returns bad result for a user lives in
different timezone against a server.
has caused the Debian Bug report #891959,
regarding redmine: sql_for_field returns bad result for a user lives in
different timezone against a server.
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.)
--
891959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891959
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: redmine
Version: 3.3.1-4
Severity: minor
Tags: l10n
Dear Maintainer,
My redmine server is in Japan, and an user is in Taiwan.
When an user in Taiwan (his timezone is CTT, Feb 10 23h30, and my server is Feb
11 0h30 JST) tried to use a custom query to find his issues,
a query calls sql_for_field method with parameters below,
> oparator = { "due_date" => "<t-"}
> v = {"due_date" => ["0"]}
> sql_for_field("due_date", oparator, v, db_table,"due_date",false)
and that returns a SQL like this,
> (issues.due_date <= '2018-02-11 00:59:59.999999')
But, I think sql_for_field method has to return a SQL like this.
> (issues.due_date <= '2018-02-10 23:59:59.999999')
and also, sql_for_custom_field might have same problems.
thank you.
-- System Information:
Debian Release: 9.3
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (99, 'testing'), (9,
'unstable'), (1, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8),
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages redmine depends on:
ii dbconfig-common 2.0.8
ii debconf [debconf-2.0] 1.5.61
ii redmine-mysql 3.3.1-4
ii ruby 1:2.3.3
ii ruby-actionpack-action-caching 1.1.1-4
ii ruby-actionpack-xml-parser 1.0.2-2
ii ruby-bundler 1.13.6-2
ii ruby-coderay 1.1.1-1
ii ruby-i18n 0.7.0-2
ii ruby-jquery-rails 4.2.1-2
ii ruby-mime-types 2.6.1-1
ii ruby-mimemagic 0.3.0+dfsg-1
ii ruby-net-ldap 0.12.1-2
ii ruby-openid 2.7.0debian-1
ii ruby-protected-attributes 1.1.3-2
ii ruby-rack 1.6.4-4
ii ruby-rack-openid 1.4.2-1
ii ruby-rails 2:4.2.7.1-1
ii ruby-rails-observers 0.1.2-1
ii ruby-rbpdf 1.19.0-1
ii ruby-redcarpet 3.3.4-2
ii ruby-request-store 1.3.0-1
ii ruby-rmagick 2.16.0-2+b1
ii ruby-roadie-rails 1.1.0-1
ii ruby2.1 [ruby-interpreter] 2.1.5-2+deb8u3
Versions of packages redmine recommends:
ii passenger 5.0.30-1+b1
Versions of packages redmine suggests:
pn bzr <none>
pn cvs <none>
pn darcs <none>
ii git 1:2.11.0-3+deb9u2
pn mercurial <none>
ii ruby-fcgi 0.9.2.1-2+b1
ii subversion 1.9.5-1+deb9u1
-- debconf information excluded
--- End Message ---
--- Begin Message ---
I am going to close this bug report as it was filed against an old
version of the package, it isn’t clear if it affects current versions of
Redmine, and there has been no response from the original bug
reporter.
Anyone should feel free to reopen the bug report if they can confirm
the problems still exists in the current version of Redmine.
--
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
