search for: f38

Dear R-core, I just received notification of CVE-2024-27322 [1] in RedHat's Bugzilla. We updated R to v4.4.0 in Fedora rawhide, F40, EPEL9 and EPEL8, so no problem there. However, F38 and F39 will stay at v4.3.3, and I was wondering if there's a specific patch available, or if you could point me to the commits that fixed the issue, so that we can cherry-pick them for F38 and F39. Thanks. [1] https://nvd.nist.gov/vuln/detail/CVE-2024-27322 Best, -- I?aki ?car [[alternati...

...gt; On 30 Apr 2024, at 11:28 , I?aki Ucar <iucar at fedoraproject.org> wrote: > > Dear R-core, > > I just received notification of CVE-2024-27322 [1] in RedHat's Bugzilla. We > updated R to v4.4.0 in Fedora rawhide, F40, EPEL9 and EPEL8, so no problem > there. However, F38 and F39 will stay at v4.3.3, and I was wondering if > there's a specific patch available, or if you could point me to the commits > that fixed the issue, so that we can cherry-pick them for F38 and F39. > Thanks. > > [1] https://nvd.nist.gov/vuln/detail/CVE-2024-27322 > >...

...r 2024, at 11:28 , I?aki Ucar <iucar at fedoraproject.org> wrote: | > | > Dear R-core, | > | > I just received notification of CVE-2024-27322 [1] in RedHat's Bugzilla. We | > updated R to v4.4.0 in Fedora rawhide, F40, EPEL9 and EPEL8, so no problem | > there. However, F38 and F39 will stay at v4.3.3, and I was wondering if | > there's a specific patch available, or if you could point me to the commits | > that fixed the issue, so that we can cherry-pick them for F38 and F39. | > Thanks. | > | > [1] https://nvd.nist.gov/vuln/detail/CVE-2024-27322...

...r at fedoraproject.org> wrote: > | > > | > Dear R-core, > | > > | > I just received notification of CVE-2024-27322 [1] in RedHat's > Bugzilla. We > | > updated R to v4.4.0 in Fedora rawhide, F40, EPEL9 and EPEL8, so no > problem > | > there. However, F38 and F39 will stay at v4.3.3, and I was wondering if > | > there's a specific patch available, or if you could point me to the > commits > | > that fixed the issue, so that we can cherry-pick them for F38 and F39. > | > Thanks. > | > > | > [1] https://nvd.nist.go...

...881e-05 7.413345e-07 -1.532306e-05 week4 4.880167e-04 -7.139705e-05 1.360150e-05 -2.548684e-04 Residual Deviance: 143.6754 AIC: 257.6754 -------------- next part -------------- > nose126s2.mu <- multinom(Spoilage ~ F25 + F26 + F27 + F28 + F29 + F30 + F31+ F32 + F33 + F34 + F35+ F36 + F37 + F38 + F39+ F40 + F41 + F42 +F43 + F44 + F45 + F46 + F47 + F48 + F49 + F50 + F51 + F52 + F53 + F54 + F55 + F56 + F57 + F58 + F59 + F60 + F61 + F62 + F63 + F64 + F65 + F66 + F67 + F68 + F69 + F70 + F71 + F72 + F73 + F74 + F75 + F76 + F77 + F78 + F79 + F80 + F81 + F82 + F83 + F84 + F85 + F86 + F87 + F88 +...

On Fri, Jul 21, 2023 at 4:37?AM Dmitry Belyavskiy <dbelyavs at redhat.com> wrote: > > On Thu, Jul 20, 2023 at 3:53?AM Damien Miller <djm at mindrot.org> wrote: > > > > > > > > On Wed, 19 Jul 2023, Dmitry Belyavskiy wrote: > > > > > Dear Damien, > > > > > > Could you please clarify which versions are vulnerable? > >

Hi, I am trying to boot the PXEclient via pxeserver and I am getting an error "file not found", following are me setup in the /tftpboot: /tftpboot: initrd.img linuz pxelinux.0 /tftpboot/pxelinux.cfg default (lower case) in the default file: # This is the default pxelinux config file. LABEL test KERNEL vmlinuz APPEND

Debian Lenny Samba 3.2.3 LOOX N560 with Windows Mobile 5 Hello, ?my PDA LOOX N560 could connect via WLAN to SAMBA under Etch. Meanwhile I upgraded to Debian Lenny and now may PDA cannot connect anymore to the server. Error 1223 or 1222. Connecting to XP-Clients via WLAN is okay. Connecting to Samba Wireshark tells me: malformed packet: No. ? ? Time ? ? ? ?Source ? ? ? ? ? ? ?

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking