Date: Tue, 11 Dec 2018 19:21:36 +0100 From: Stefan Esser <se@freebsd.org> To: "Janky Jay, III" <jankyj@unfs.us>, freebsd-ports@freebsd.org Cc: yasu@utahime.org Subject: Re: ClamAV Port Version Regression? Message-ID: <26ea4ed4-1f2d-de32-2a39-43ab28cff189@freebsd.org> In-Reply-To: <7971a617-6aa9-c18e-d53e-fbd8985bb043@unfs.us> References: <7971a617-6aa9-c18e-d53e-fbd8985bb043@unfs.us>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ZMBxwG1WmDTE3m324zI35SZ5JUqIiGJbM
Content-Type: multipart/mixed; boundary="dmBa9YDiPMqLHjZ2EBtehPUQHbW9G8Eaq";
protected-headers="v1"
From: Stefan Esser <se@freebsd.org>
To: "Janky Jay, III" <jankyj@unfs.us>, freebsd-ports@freebsd.org
Cc: yasu@utahime.org
Message-ID: <26ea4ed4-1f2d-de32-2a39-43ab28cff189@freebsd.org>
Subject: Re: ClamAV Port Version Regression?
References: <7971a617-6aa9-c18e-d53e-fbd8985bb043@unfs.us>
In-Reply-To: <7971a617-6aa9-c18e-d53e-fbd8985bb043@unfs.us>
--dmBa9YDiPMqLHjZ2EBtehPUQHbW9G8Eaq
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Am 11.12.18 um 18:51 schrieb Janky Jay, III:
> Hi All,
>=20
> After a portsnap to pull ${latest), I'm seeing the following:
>=20
> clamav-0.101.0_2 < needs updating (index has 0.100.=
2,1)
>=20
> The version that is claiming to be the latest appears to be a version
> regression. Am I wrong here? I checked the ClamAV site and it appears
> version 0.101.0 is, in fact, the latest. So, I'm wondering if there was=
> possibly a revision issue that's causing this?
The ,1 at the end of the port to be installed indicates a new port epoch,=
which is used to enforce an "upgrade" to a lower version number.
This is typically done if a port upgrade has been revoked due to problems=
with the new version.
In this particular case the commit log says:
r487064 | antoine | 2018-12-09 18:33:26 +0100 (Sun, 09 Dec 2018) | 6 line=
s
Downgrade to 0.100.2
Upstream plans to release version 0.101.1 which fixes header issues in Ja=
nuary
2019
Regards, STefan
--dmBa9YDiPMqLHjZ2EBtehPUQHbW9G8Eaq--
--ZMBxwG1WmDTE3m324zI35SZ5JUqIiGJbM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAlwQADEACgkQR+u171r9
9UQ1VQgAw1Pwsj7205aWTOAAthVASapL3dWjLpBASN+EHY2kptR+wPraVqPkjCOV
bY0sZz9loMG9rJeRYXkfBBXZ7SuG+ylBK/wJ/+2HeHzgFt2w+9rGEalNGmY8zofw
k3OlIxg1NbIf+TMmdBo83zOu60mrIUKWPLwjMvoMQJz5GNMQvBunwjHftVgGT+pB
iCEjUIAuQfpKjAGQKWT2spcIdmlX+u2PR813EieMZ6kTPRPEHFP4Ot16keUCK7RQ
KQjOnFS4ZvJB6XihKmBrTTNzkSjXZmXWuK4lJgOF279aisslvZO3xNsWRvp6K5uc
Ovq6ZgEvXtm2nGgQtuuulQL5c3DHgA==
=Oome
-----END PGP SIGNATURE-----
--ZMBxwG1WmDTE3m324zI35SZ5JUqIiGJbM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26ea4ed4-1f2d-de32-2a39-43ab28cff189>