From nobody Fri Jan 05 23:00:13 2024 X-Original-To: freebsd-stable@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 4T6Jp4571Vz56J83 for ; Fri, 5 Jan 2024 23:00:28 +0000 (UTC) (envelope-from alfix86@gmail.com) Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T6Jp43CChz4Zxw; Fri, 5 Jan 2024 23:00:28 +0000 (UTC) (envelope-from alfix86@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-28c075ad8e7so88217a91.2; Fri, 05 Jan 2024 15:00:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704495626; x=1705100426; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vNI2CaNw7+S66hItx74u8eEqVHha/229BnCdxSR/lws=; b=BWsCgKc0yY2TS1dpGfm5z1pyOOQ1RJHFkgf9uTNiA+iNpsu22M42+gJGBsVKPF9l/y Z30lqzwibz0ATqqYDwozvMY+AAsp6EcRAM25ASjNqGxuZKm5ASXpXA7HA3b4SpdVLuqn sMsFoX2c0PNxnvp86FBJbDGMWQSJQJSQRwYcRQFKZx/J2gl64SqwqJc0RV0ZwYSTXoyU uxwSMKSiNTOpZnxe/VFbTPRMfvU1Oy67pVhYnWpBTvZB/zu98kjXmBf+eRtqKFbUA4BA OzS5zsIMYskrgtgbCeoHVaCiJ7wk6GKlEClwehBkBvJrXDHBdenibPePHNE3iNU+HJxU ZB+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704495626; x=1705100426; h=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=vNI2CaNw7+S66hItx74u8eEqVHha/229BnCdxSR/lws=; b=OrR/oEcIYEsaz4KTjCWiRUQ9vo6AyVZ6v0ahSnBptEyo5K7ZWWG2iGDi1u3uIR351/ xLXK72pqxX/PYm7HzM+D/ns95R2Pdz10x3pDGRaBWn/9LC88SFMBM/dELKq214rev1U8 ht7JysYQndzu9aavnVfDk7zxuLKoTAcZLhIw+8odMf7ryRacnYuIO7YhtbGw6CWUHcvP DodY9OJV4Qg8qkLgevxXffn9QXBGlnMSbGLXJ79nUcr+VRZqXbS0JeYbKCKpq4iUghNy Jxoa/KOrWoDIJ1+X/qiIsvFdx+WpUnEkRYgdeQqkVu1KItBCJAfLhZaZoDqItqKEAH3E ccLQ== X-Gm-Message-State: AOJu0YyU6hx4g0lRPKV63JGjWcojQxSO27F/PpiUT8Lr24g7wWU8l3fP JVgtgx8EK/RJMsQ7jSN4Cecolc16SNyUlvrwqwkNctfA X-Google-Smtp-Source: AGHT+IE8iPs994kpxleKmyJ/w5342z+t8HbYk/kITWOElkUn6jT/somRw7r2SCl8P3DibxTz43YILBxXHa+Ec/Yd2Gs= X-Received: by 2002:a17:90a:9b0a:b0:28d:15a:4c05 with SMTP id f10-20020a17090a9b0a00b0028d015a4c05mr167505pjp.94.1704495626210; Fri, 05 Jan 2024 15:00:26 -0800 (PST) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Alfonso Sabato Siciliano Date: Sat, 6 Jan 2024 00:00:13 +0100 Message-ID: Subject: Re: ports-mgmt/portconfig surprize To: Peter Cc: freebsd-stable@freebsd.org, Baptiste Daroussin , "Alfonso S. Siciliano" Content-Type: multipart/alternative; boundary="000000000000525371060e3ad0d1" X-Rspamd-Queue-Id: 4T6Jp43CChz4Zxw 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:2607:f8b0::/32, country:US] --000000000000525371060e3ad0d1 Content-Type: text/plain; charset="UTF-8" On Fri, Jan 5, 2024, 00:45 Peter wrote: > Folks, > > somebody got the idea to replace the dialog4ports options > configuring interface by something named 'ports-mgmt/portconfig'. > (And they did not even find it worth mentioning this in the > UPGRADING file.) > > Now this one looks terrible, the screen is garbled, and it is > quite unintellegible which line is currently entered. > See pictures here (old and new): > > https://forums.freebsd.org/threads/2024q1-portbuild-trouble.91770/post-636816 > > What is happening: > I am starting a shell script. That fires up a bhyve. In the bhyve 'make' > is run with stdio connected to the second COM. > In the script on the host, bhyve is put in background, 'cu' is started > and connected to that second COM. There the dialog appears. > Since the script on the host is run from remote, it is run within > tmux. > Point is: it did work before. > > disappointed, > PMc > Thank you for the report I am in a rural place far from my laptop. I'll investigate the problem on Monday. However you could run: # pkg install dialog4ports and adding DIALOG4PORTS=${LOCALBASE}/bin/dialog4ports to /etc/make.conf you can use the previous utility instead of portconfig to set up ports options via a TUI. Please next time open a new issue to https://gitlab.com/alfix/portconfig to report a problem about portconfig. Alfonso --000000000000525371060e3ad0d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Fri, Jan 5, 2024, 00:45 Peter <pmc@citylink.dinoex.sub.org> wrote:
Folks,

=C2=A0 somebody got the idea to replace the dialog4ports options
configuring interface by something named 'ports-mgmt/portconfig'. (And they did not even find it worth mentioning this in the
UPGRADING file.)

Now this one looks terrible, the screen is garbled, and it is
quite unintellegible which line is currently entered.
See pictures here (old and new):
https://foru= ms.freebsd.org/threads/2024q1-portbuild-trouble.91770/post-636816

What is happening:
I am starting a shell script. That fires up a bhyve. In the bhyve 'make= '
is run with stdio connected to the second COM.
In the script on the host, bhyve is put in background, 'cu' is star= ted
and connected to that second COM. There the dialog appears.
Since the script on the host is run from remote, it is run within
tmux.
Point is: it did work before.

disappointed,
PMc



Thank you for the report=C2=A0

I am in a rural place far from my laptop.
= I'll investigate the problem on Monday.

However you could run:
# pkg ins= tall dialog4ports
and adding
= DIALOG4PORTS=3D${LOCALBASE}/bin/dialog4ports
to /etc= /make.conf you can use the previous utility instead of portconfig to set up= ports options via a TUI.

Please next time open a new issue to https://gitlab.com/alfix/portconfig to report a problem abo= ut portconfig.

Alfonso

--000000000000525371060e3ad0d1--