On Fri, Jul 22, 2016 at 08:54:38PM +1000, Brian May wrote:
> Bastian Blank writes:
> > Did you get the chance to look at this source?
> I think I need to see Debian sources to look at...
Here you go:
https://korte.credativ.com/~bbl/xen/xen_4.1.6.lts1~e98efe58-1.dsc
> Actually I suspect you are
On Fri, Jul 22, 2016 at 10:24:27AM +0200, Raphael Hertzog wrote:
> Why does
> https://github.com/credativ/xen-lts/blob/lts-status/security-status.md
> still have lots of question marks?
> What are we waiting to get a security release out?
Because the large backport is in the state "works for me"
Hi,
2016-07-19 23:12 GMT+02:00 Brian May :
> Maximiliano Curia writes:
>
>> I just did the upload to unstable, with the karchive fix from upstream and an
>> modified version of that one for kde4libs. The second one needs some test,
>> sadly adding the (binary) test file used in karchive is a bit
Hi Chris,
On Fri, Jul 22, 2016 at 06:48:55PM +0200, Chris Lamb wrote:
> If you don't want to take care of this update, it's not a problem, we
> will do our best with your package. Just let us know whether you would
> like to review and/or test the updated package before it gets released.
We're pr
Hi Bastian,
On Mon, Jul 25, 2016 at 01:04:52PM +0200, Bastian Blank wrote:
> On Fri, Jul 22, 2016 at 10:24:27AM +0200, Raphael Hertzog wrote:
> > Why does
> > https://github.com/credativ/xen-lts/blob/lts-status/security-status.md
> > still have lots of question marks?
> > What are we waiting to ge
Hi Maximiliano,
2016-07-25 15:41 GMT+02:00 Bálint Réczey :
> Hi,
>
> 2016-07-19 23:12 GMT+02:00 Brian May :
>> Maximiliano Curia writes:
>>
>>> I just did the upload to unstable, with the karchive fix from upstream and
>>> an
>>> modified version of that one for kde4libs. The second one needs so
Hi Craig,
I have prepared a security update for Wordpress in Wheezy and pushed my
work to
https://anonscm.debian.org/cgit/collab-maint/wordpress.git/commit/?h=wheezy&id=d1f7bfa1d5109509bb4ab7ab23d0e7e7dc8736cc
I intend to release it soon but I haven't found the changeset / fix for
CVE-2016-5836