From nobody Thu Nov 4 09:53:23 2021 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5E8E41840087 for ; Thu, 4 Nov 2021 09:53:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HlJqR1RDJz4cFG for ; Thu, 4 Nov 2021 09:53:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1209729CF0 for ; Thu, 4 Nov 2021 09:53:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1A49rNIV007711 for ; Thu, 4 Nov 2021 09:53:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1A49rNLY007710 for ports-bugs@FreeBSD.org; Thu, 4 Nov 2021 09:53:23 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 259641] security/clamav: Update to new bugfix release 0.103.4 (Direct commit to 2021Q4 branch) Date: Thu, 04 Nov 2021 09:53:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yasu@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform bug_file_loc op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259641 Bug ID: 259641 Summary: security/clamav: Update to new bugfix release 0.103.4 (Direct commit to 2021Q4 branch) Product: Ports & Packages Version: Latest Hardware: Any URL: https://blog.clamav.net/2021/11/clamav-01034-and-01041 -patch-releases.html OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: yasu@freebsd.org CC: ports-secteam@FreeBSD.org Attachment #229264 maintainer-approval+ Flags: Created attachment 229264 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D229264&action= =3Dedit Patch file @ports-secteam I would like to request approval to make direct commit of attached patch to 2021Q4 branch. The patch updates security/clamav to new bugfix release 0.10= 3.4. The reason I request direct commit rather than MFH is as following. * On September upstream changed their release and support policy as followi= ng. - They release Regular Feature Release (=3D x.y.0 release) more frequentl= y. And x.y.z releases are supported until 4 months after the release of x.(y+1).0. - To compensate for the short lifetime of Regular Feature Releases, Long = Term Support (LTS) Feature Release is introduced. A new LTS Feature Release will= be identified approximately every two years and be supported for at least three years from the initial publication date of that LTS feature version. * Version 0.103.3 was identified as first LTS Feature Release. * After 2021Q4 branch was created, on main brach security/clamav was update= d to 0.104.0 and security/clamav-lts was added. * Version 0.104.0 is first Regular Feature Release that new upstream policy= is applied. There are large chages between 0.103.3 and 0.104.0 as upstream refactored their code base. * On November 3rd new bugfix releases 0.104.1 and 0.103.4 were released. On main branch I already updated both security/clamav and security/clamav-lts = to their latest releases. * As is exlained above lifetime of 0.104.x isn't so long and there is large difference between 0.103.x and 0.104.x. Furthermore there isn't security/clamav-lts in 2021Q4 branch that can be selected as alternative for those who look for longer lifetime. * So merging 0.104.x to 2021Q4 isn't appropriate in this case and I select = to update security/clamav to 0.103.3 --=20 You are receiving this mail because: You are the assignee for the bug.=