Re: Next Kernel update for Buster

2020-07-28 Thread Nicholas D Steeves
vincent.deb...@free.fr writes:

> On 2020-07-28T17:47+0200, gianluca wrote:
>>On 7/28/20 3:35 PM, Salvatore Bonaccorso wrote:

Have a look at: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/nilfs2?h=v4.19.129&id=1b6f42200b8313d3895c26f6553bbc8380bf1c35

>>>The next point release for buster (10.5) will contain an update of
>>>src:linux to 4.19.132, see
>>>https://lists.debian.org/debian-stable-announce/2020/07/msg1.html
>>
>>that's a very good news to know. What about timeline for 10.5??
>>;-)
>
> It should be available on Saturday August 1st.

Gianluca, P.S. if you're interested in participating in testing packages
queued for the next point release, see

  https://www.debian.org/releases/proposed-updates

If you're exclusively interested in testing kernel proposed-updates,
then you can use APT pinning to configure this:

  https://wiki.debian.org/AptConfiguration

To get this effect I'd add a rule to pin proposed-updates to a lower
priority than stable, stable-updates, and debian-security, and then add
a rule to make kernel-related packages from proposed-updates evaluate to
a higher priority.  There might be better ways, and this is just the
method I'd use ;-)


Cheers,
Nicholas


signature.asc
Description: PGP signature


Re: Next Kernel update for Buster

2020-07-28 Thread vincent . debian

On 2020-07-28T17:47+0200, gianluca wrote:

On 7/28/20 3:35 PM, Salvatore Bonaccorso wrote:


Have a look at: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/nilfs2?h=v4.19.129&id=1b6f42200b8313d3895c26f6553bbc8380bf1c35


The next point release for buster (10.5) will contain an update of
src:linux to 4.19.132, see
https://lists.debian.org/debian-stable-announce/2020/07/msg1.html


that's a very good news to know. What about timeline for 10.5??
;-)


It should be available on Saturday August 1st.


signature.asc
Description: PGP signature


Re: Next Kernel update for Buster

2020-07-28 Thread gianluca

On 7/28/20 3:35 PM, Salvatore Bonaccorso wrote:


Have a look at: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/nilfs2?h=v4.19.129&id=1b6f42200b8313d3895c26f6553bbc8380bf1c35


The next point release for buster (10.5) will contain an update of
src:linux to 4.19.132, see
https://lists.debian.org/debian-stable-announce/2020/07/msg1.html


that's a very good news to know. What about timeline for 10.5??
;-)

Regards,
--
Eurek s.r.l.  |
Electronic Engineering| http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy  | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377  | Fax:   +39-(0)542-609212



Re: Next Kernel update for Buster

2020-07-28 Thread Salvatore Bonaccorso
Ciao Gianluca,

On Tue, Jul 28, 2020 at 02:58:53PM +0200, gianluca wrote:
> Hello,
> I was wondering if there is any chance to have a better kernel from the
> 4.19.129 or greater.
> 
> I am asking this, mainly because of the BUG correction on NILFS2 Garbage
> Collector as my systems are using NILFS2 as rootfs and at the moment they
> are unable to boot off a nilfs2-formatted disk.
> 
> Have a look at: 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/nilfs2?h=v4.19.129&id=1b6f42200b8313d3895c26f6553bbc8380bf1c35
> 
> 
> At the moment the only workaround I have found is using an ext4-formatted
> disk, but it is merely temporary.

The next point release for buster (10.5) will contain an update of
src:linux to 4.19.132, see
https://lists.debian.org/debian-stable-announce/2020/07/msg1.html
.

Regards,
Salvatore



Next Kernel update for Buster

2020-07-28 Thread gianluca

Hello,
I was wondering if there is any chance to have a better kernel from the 
4.19.129 or greater.


I am asking this, mainly because of the BUG correction on NILFS2 Garbage 
Collector as my systems are using NILFS2 as rootfs and at the moment 
they are unable to boot off a nilfs2-formatted disk.


Have a look at: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/nilfs2?h=v4.19.129&id=1b6f42200b8313d3895c26f6553bbc8380bf1c35



At the moment the only workaround I have found is using an 
ext4-formatted disk, but it is merely temporary.


Best regards,
Gianluca Renzi
--
Eurek s.r.l.  |
Electronic Engineering| http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy  | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377  | Fax:   +39-(0)542-609212