Hi Antonio,
> The help I need is
>
> 1) confirmation that this does still happen with the packages in jessie
yes, I can confirm that this still happens with the packages in jessie.
> 2) identifying exactly which commit on the upstream source, between 2.5
> and 3.0, fixes it.
It seems the fix w
On Mon, Jul 25, 2016 at 03:33:47PM +0200, Daniel Scharon wrote:
> Hi Antonio,
>
> > > can we still expect an update for stable that fixes this?
> >
> > we could, but I need help as I explained earlier in this bug report.
>
> unfortunatly I am not quite sure about the specifics of the help need
Hi Antonio,
> > can we still expect an update for stable that fixes this?
>
> we could, but I need help as I explained earlier in this bug report.
unfortunatly I am not quite sure about the specifics of the help needed.
Do you mean testing the packages in your repo at
https://people.debian.org
On Mon, Jul 04, 2016 at 11:25:34AM +0200, Daniel Scharon wrote:
> Hi,
>
> can we still expect an update for stable that fixes this?
we could, but I need help as I explained earlier in this bug report.
> Or do we have to wait for a backport of the version in stretch (if that
> is in any way feasi
Hi,
can we still expect an update for stable that fixes this?
Or do we have to wait for a backport of the version in stretch (if that
is in any way feasible)?
Kind regards,
Dan
I'm also seeing this.
We've got a bunch of other things running on this system, so I'm hesitant in
upgrading to Redmine 3.x, has anyone actually fixed this?
(This issue is driving my project manager absolutely bonkers.)
On Thu, 26 Nov 2015 13:24:05 +0100 Michael Probst wrote:
> Hi,
>
> we hav
Hi,
we have exactly the same issue with Redmine 2.5.2 on Jessie.
After installing the packages from your repository nothing changed.
Environment:
Redmine version2.5.2.devel
Ruby version 2.1.5-p273 (2014-11-13) [i386-linux-gnu]
Rails version
On Wed, Sep 09, 2015 at 11:30:45AM -0400, Guillaume ! wrote:
> Hi !
>
> We have to get this fixed, so in the next couple of weeks we should be
> coming up with some way of running redmine 3.0.4 with the debian patches.
> We'd be happy to submit our work to make a new version of this package,
> or
o submit further information on this problem, please
> send it to 793...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 793387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79
on this problem, please
> send it to 793...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 793387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793387
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
Package: redmine
Version: 3.0~20140825-5
Severity: normal
Dear Maintainer,
We're having a production instance of redmine running and user have complained
that whey you create issues with parent task set, those give a 500 error, but
the issue is created anyway. I haven't checked upstream to see if
11 matches
Mail list logo