Hi Salvatore,
On Tue, 20 Feb 2018, Salvatore Bonaccorso wrote:
So affected persons could already install the fixed packages via
proposed-updates,
aah, ok, I didn't thought of that, so everything is fine and sorry for the
noise.
Thorsten
On Tue, Feb 20, 2018 at 10:49:36PM +0100, Moritz Mühlenhoff wrote:
> On Tue, Feb 20, 2018 at 01:56:12PM -0600, Benjamin Kaduk wrote:
> >
> > It's probably also worth noting that this is not the first time that
> > a linux security update caused an openafs regression,
>
> The only sane way to
On Tue, Feb 20, 2018 at 01:56:12PM -0600, Benjamin Kaduk wrote:
> On Tue, Feb 20, 2018 at 08:51:16PM +0100, Salvatore Bonaccorso wrote:
> > Hi Thorsten,
> >
> > On Tue, Feb 20, 2018 at 02:45:48PM +0100, Thorsten Alteholz wrote:
> > > Hi everybody,
> > >
> > > the latest security update of the
On Tue, Feb 20, 2018 at 08:51:16PM +0100, Salvatore Bonaccorso wrote:
> Hi Thorsten,
>
> On Tue, Feb 20, 2018 at 02:45:48PM +0100, Thorsten Alteholz wrote:
> > Hi everybody,
> >
> > the latest security update of the kernel to version 3.2.0-5 in Jessie
> > resulted in #886768 [1] for openafs.
> >
Hi Thorsten,
On Tue, Feb 20, 2018 at 02:45:48PM +0100, Thorsten Alteholz wrote:
> Hi everybody,
>
> the latest security update of the kernel to version 3.2.0-5 in Jessie
> resulted in #886768 [1] for openafs.
>
> Wouldn't it be better to do the openafs upload via security as well?
> At the
Hi everybody,
the latest security update of the kernel to version 3.2.0-5 in Jessie
resulted in #886768 [1] for openafs.
Wouldn't it be better to do the openafs upload via security as well?
At the moment openafs in Jessie is just broken until the next point
release.
Thorsten
[1]
6 matches
Mail list logo
