From nobody Thu Jul 11 16:26:29 2024 X-Original-To: dev-commits-ports-main@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 4WKg8y64CRz5QxNr; Thu, 11 Jul 2024 16:26:42 +0000 (UTC) (envelope-from bsdkaffee@gmail.com) Received: from mail-yw1-f178.google.com (mail-yw1-f178.google.com [209.85.128.178]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WKg8y4LGyz3wj4; Thu, 11 Jul 2024 16:26:42 +0000 (UTC) (envelope-from bsdkaffee@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-f178.google.com with SMTP id 00721157ae682-64b0d45a7aaso11039167b3.0; Thu, 11 Jul 2024 09:26:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720715201; x=1721320001; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=oDTIlcm1tydMwe4yPK1TbJXclPmnRJanxlmks8cByY4=; b=TxUxh+jvksE68tu+zbMeenbNDXmcN9y0pBRyBpMFjSilC2HP0+82A7Vc6aVmwjFH+y WNigqG6EJFxrWGFiM1kiJT+TAp4Lpc+Toyr1zUEc5ayassmQpEsWWEX31dk6MNwhsF/Q dSqn4k/oXXFYLS2jU9MOQj/IsOdrHR3uR1Vh1z2eMs0o3DhGPSPa4sa69xEo7RD4AYvb abxZelalOuEKA/o/atlZ558LfhzeHMr3QcKh/Atps/L3pU+mQTuXvczbF3Eh7rjp/UXu CMbRSiXjv0c4Skq83iPT7qfpWXm3+iNoDyLVSUXrVUuLJWwm0RTJeJo2lcaoVFphd8dI lKAQ== X-Forwarded-Encrypted: i=1; AJvYcCXErytn6WHAoz6vtyJYQuMNhY6HriS8gG0r8iNwfirNu22nvKrhiW8dDRf3zTtveH4A1fgCRYiC6babMxXFkdG7ulZxhXowci+ToXe5X47iDeONcpu1pO0mAN+JYXbms7DQHowFvddHaMQHBsujryM1EVVm9xHxydKEcR4nFes5GWHCcFyxFox45W3827D9P6xTnPU= X-Gm-Message-State: AOJu0Yz/OlKYtJkbA2D1a9SVhlrFDHbTuhfsg61MD0SZ9Fvjysxw39Gr /YdO3C+3pxSlfi1ekM+E2QlD2YmQaXvyG54fEi2LCxAO/9uwkaulU3Uu7M7yPquaT7Sq1fdYmo1 NCD7wELZCgzJ52zBy//nMxYO8NPG8gQ== X-Google-Smtp-Source: AGHT+IEXumZa4/pjui28Wgsg8g31WL+ERmxdMEd7vDp6NgrctsSrMS+9VLNGGIaucYkyhxvSJgFhYX5QnmAd3yZzNmo= X-Received: by 2002:a0d:e386:0:b0:64a:e9bf:4378 with SMTP id 00721157ae682-658eec68cddmr90284257b3.18.1720715200900; Thu, 11 Jul 2024 09:26:40 -0700 (PDT) List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: dev-commits-ports-main@freebsd.org Sender: owner-dev-commits-ports-main@FreeBSD.org MIME-Version: 1.0 References: <202407080512.4685CQIk061407@gitrepo.freebsd.org> <09935039-a2af-4892-b367-88a9a42488ce@app.fastmail.com> In-Reply-To: <09935039-a2af-4892-b367-88a9a42488ce@app.fastmail.com> From: "Jason E. Hale" Date: Thu, 11 Jul 2024 12:26:29 -0400 Message-ID: Subject: Re: git: c1dda71dec4c - main - */*: Chase security/libassuan shlib bump To: Dan Langille Cc: "Jason E. Hale" , ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org, umq@ueo.co.jp Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4WKg8y4LGyz3wj4 On Thu, Jul 11, 2024 at 9:33=E2=80=AFAM Dan Langille wro= te: > > Not sure it's entirely related, but security/dirmngr is now giving me con= figuration errors. See also, fallout: > > https://portsfallout.com/fallout?port=3Dsecurity%2Fdirmngr%24 > > This is not personally affecting me. Just saying. > Thanks for the heads up! I'll mark it BROKEN. GNU Pth support was removed in libassuan 3.x and porting to npth would not be worth the effort IMHO. Since dirmngr has been part of security/gnupg for the last 14 years, keeping this ancient standalone version seems unnecessary. I would suggest to the maintainer that we also mark it DEPRECATED and set an EXPIRATION_DATE. - Jason