Your message dated Tue, 20 Nov 2018 23:58:54 +0900
with message-id <[email protected]>
and subject line Re: Redmine bad path
has caused the Debian Bug report #838555,
regarding Redmine bad path
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.)
--
838555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838555
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: redmine
Version: 3.0~20140825-8~deb8u3
When using apt-get update && apt-get dist-upgrade to update the system I
have an error on redmine update :
Setting up redmine (3.0~20140825-8~deb8u3) ...
chown: cannot access ‘/var/lib/redmine/Gemfile.lock’: No such file or
directory
dpkg: error processing package redmine (--configure):
subprocess installed post-installation script returned error exit status 1
The default path for Gemfile.lock is /usr/share/redmine
I suggest that the default path of redmine installation and update is
/usr/share/redmine.
I am using Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
Quack,
We do not have such problem anymore, the autopkgtests would have
detected that.
This was reported for a version which is not part of a release either.
I'm thus closing this BR. Thanks for your report.
\_o<
--
Marc Dequènes
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
