Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-04-01 Thread James McCoy
On Sat, Apr 01, 2017 at 02:21:25PM -0400, PICCORO McKAY Lenz wrote: > 2017-04-01 13:53 GMT-04:00 James McCoy : >   makes the package in question unusable or mostly so, or causes data >   loss, or introduces a security hole allowing access to the accounts of >  

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-04-01 Thread PICCORO McKAY Lenz
2017-04-01 13:53 GMT-04:00 James McCoy : > On Sat, Apr 01, 2017 at 10:28:34AM -0400, PICCORO McKAY Lenz wrote: > > 2017-04-01 8:33 GMT-04:00 James McCoy : > > > > Given that there's an easy workaround (set http-chunked-requests to > > off) I'm

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-04-01 Thread James McCoy
On Sat, Apr 01, 2017 at 10:28:34AM -0400, PICCORO McKAY Lenz wrote: > 2017-04-01 8:33 GMT-04:00 James McCoy : > > Given that there's an easy workaround (set http-chunked-requests to > off) I'm lowering the severity of the bug. > > > u lowering, but this issue

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-04-01 Thread PICCORO McKAY Lenz
2017-04-01 8:33 GMT-04:00 James McCoy : > Given that there's an easy workaround (set http-chunked-requests to > off) I'm lowering the severity of the bug. > u lowering, but this issue afected many users in the internet! but due are not close to the distributions (thei'r not

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-04-01 Thread James McCoy
Control: severity -1 normal On Wed, Mar 29, 2017 at 08:21:23AM -0400, PICCORO McKAY Lenz wrote: > 2017-03-28 23:04 GMT-04:00 James McCoy : > > This discussion is specifically talking about when a 411 status is > returned, not a 413. > > the document only cited 411

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-03-29 Thread PICCORO McKAY Lenz
2017-03-28 23:04 GMT-04:00 James McCoy : > This discussion is specifically talking about when a 411 status is > returned, not a 413. > the document only cited 411 error as example, could not cover all the cases due there are more, if u understand how to work http 1.1 vs other

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-03-28 Thread James McCoy
On Tue, Mar 28, 2017 at 10:50:20PM -0400, PICCORO McKAY Lenz wrote: > I cited why must be set for 1.8 and q.9 until 1.10 released: > > Users who wish to avoid the additional request may set that option to yes or  > no >  in order to short-circuit the additional request and avoid making it. This

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-03-28 Thread PICCORO McKAY Lenz
I cited why must be set for 1.8 and q.9 until 1.10 released: Users who wish to avoid the additional request may set that option to yes or no in order to short-circuit the additional request and avoid making it. later we have: The Serf-based HTTP access library would use chunked transfer

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-03-28 Thread James McCoy
On Tue, Mar 28, 2017 at 07:34:46PM -0400, PICCORO McKAY Lenz wrote: > Package: subversion > Version: 1.8.10-6+deb8u4 > Severity: grave > Justification: renders package unusable > > Dear Maintainer,the current package in debian are broken > i upgrade clients to jeesie > and now could'n chekout

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

2017-03-28 Thread PICCORO McKAY Lenz
Package: subversion Version: 1.8.10-6+deb8u4 Severity: grave Justification: renders package unusable Dear Maintainer,the current package in debian are broken i upgrade clients to jeesie and now could'n chekout working copies from external networks, only internal local network but when i conpiled