Bug#933961: gitlab: Viewing diff of a commit results in error 500

2019-08-11 Thread Pirate Praveen
On Fri, 9 Aug 2019 12:09:46 +0200 Claudius Steinhauser wrote: > On 08.08.2019 19:22, Pirate Praveen wrote: > > I can provide packages for unstable too via the same repo. > > That would be great if it's not too much work for you. Thanks. Just uploaded gitlab 11.11.7 to experimental. Check wiki a

Bug#933961: gitlab: Viewing diff of a commit results in error 500

2019-08-09 Thread Claudius Steinhauser
On 08.08.2019 19:22, Pirate Praveen wrote: > I can provide packages for unstable too via the same repo. That would be great if it's not too much work for you. Thanks. Regards, Claudius

Bug#933961: gitlab: Viewing diff of a commit results in error 500

2019-08-08 Thread Pirate Praveen
On 2019-08-08 22:06, Claudius Steinhauser wrote: Oh I see that is pretty cool. Would that also work with sid/unstable? Our system is not public so it's not security critical. It might, but it is a not a good idea to mix buster and sid. Updating via packages is just very convenient and usin

Bug#933961: gitlab: Viewing diff of a commit results in error 500

2019-08-08 Thread Claudius Steinhauser
On 07.08.2019 21:15, Pirate Praveen wrote: > > On 2019, ഓഗസ്റ്റ് 5 8:20:46 PM IST, Claudius Steinhauser > wrote: >> Package: gitlab >> Version: 11.8.10+dfsg-1 >> Severity: normal >> >> Dear Maintainer, >> >> * What led up to the situation? >> >> Some update to the unstable packages in the last

Bug#933961: gitlab: Viewing diff of a commit results in error 500

2019-08-07 Thread Pirate Praveen
On 2019, ഓഗസ്റ്റ് 5 8:20:46 PM IST, Claudius Steinhauser wrote: >Package: gitlab >Version: 11.8.10+dfsg-1 >Severity: normal > >Dear Maintainer, > > * What led up to the situation? > >Some update to the unstable packages in the last two weeks I recommend using buster backports /buster fast t

Bug#933961: gitlab: Viewing diff of a commit results in error 500

2019-08-05 Thread Claudius Steinhauser
Package: gitlab Version: 11.8.10+dfsg-1 Severity: normal Dear Maintainer, * What led up to the situation? Some update to the unstable packages in the last two weeks * What exactly did you do (or not do) that was effective (or ineffective)? This bug is fixed upstream: https://gitlab