Bug#776246: Processed: severity of 776246 is grave

2019-02-23 Thread Ivo De Decker
Control: tags -1 buster-ignore Hi, On Tue, Feb 19, 2019 at 10:18:19PM +0100, Moritz Mühlenhoff wrote: > On Wed, Feb 20, 2019 at 02:12:55AM +0500, Andrey Rahmatullin wrote: > > On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote: > > > If a transition (even though it's marginal in si

Bug#776246: Processed: severity of 776246 is grave

2019-02-21 Thread Valentin Vidic
On Tue, Feb 19, 2019 at 10:26:09AM +0100, Christoph Martin wrote: > What can we do to not loose these packages (burp in my case)? > > librsync 2.0.2-1~exp1 was uploaded to experimental three days ago. csync2 seems to build fine with librsync2 from experimental so if you can upload that to unstab

Bug#776246: Processed: severity of 776246 is grave

2019-02-19 Thread Moritz Mühlenhoff
On Wed, Feb 20, 2019 at 02:12:55AM +0500, Andrey Rahmatullin wrote: > On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote: > > If a transition (even though it's marginal in size) isn't an option at this > > point > That's not for me to decide. Should we ask the RT? Sounds like a pla

Bug#776246: Processed: severity of 776246 is grave

2019-02-19 Thread Andrey Rahmatullin
On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote: > If a transition (even though it's marginal in size) isn't an option at this > point That's not for me to decide. Should we ask the RT? -- WBR, wRAR signature.asc Description: PGP signature

Bug#776246: Processed: severity of 776246 is grave

2019-02-19 Thread Moritz Mühlenhoff
On Sat, Feb 16, 2019 at 10:35:05PM +0500, Andrey Rahmatullin wrote: > On Sat, Feb 16, 2019 at 12:33:08PM +, Debian Bug Tracking System wrote: > > Processing commands for cont...@bugs.debian.org: > > > > > severity 776246 grave > > Bug #776246 [librsync1] MD4 collision/preimage attacks (CVE-201

Bug#776246: Processed: severity of 776246 is grave

2019-02-19 Thread Valentin Vidic
On Tue, Feb 19, 2019 at 10:26:09AM +0100, Christoph Martin wrote: > What can we do to not loose these packages (burp in my case)? > > librsync 2.0.2-1~exp1 was uploaded to experimental three days ago. I guess librsync2 would need to go into unstable and testing. Than we can try to update our app

Bug#776246: Processed: severity of 776246 is grave

2019-02-19 Thread Christoph Martin
What can we do to not loose these packages (burp in my case)? librsync 2.0.2-1~exp1 was uploaded to experimental three days ago. Am 18.02.19 um 18:34 schrieb Valentin Vidic: > Hi, > > Not sure why grave so late in the release process that we lose > some packages (csync2 in my case)? grave after

Bug#776246: Processed: severity of 776246 is grave

2019-02-18 Thread Valentin Vidic
Hi, Not sure why grave so late in the release process that we lose some packages (csync2 in my case)? grave after the release would give us more time to move to librsync2. -- Valentin

Bug#776246: Processed: severity of 776246 is grave

2019-02-16 Thread Andrey Rahmatullin
On Sat, Feb 16, 2019 at 12:33:08PM +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > severity 776246 grave > Bug #776246 [librsync1] MD4 collision/preimage attacks (CVE-2014-8242) > Severity set to 'grave' from 'important' > > thanks > Stopping proce