sed trouble when UNAME_* is set in jail (fwd)
- Reply: Sysadmin Lists : "Re: sed trouble when UNAME_* is set in jail (fwd)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 24 Jan 2022 19:45:11 UTC
Sorry for resend colleagues, seem to lost my subscription list -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] --------------------------------------------------------------------------- *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- woozle@woozle.net *** --------------------------------------------------------------------------- ---------- Forwarded message ---------- Date: Mon, 24 Jan 2022 22:29:35 From: Dmitry Morozovsky <marck@rinet.ru> To: bdrewery@FreeBSD.org Cc: freebsd-ports@FreeBSD.org Subject: sed trouble when UNAME_* is set in jail Bryan, colleagues, I understand that building for obsoleted systems is not supported at all, but there are *cases* -- you all know! ;) I have a jail on my build system, nested-built on a previous major; on the case, it's stable/10; for a poudriere, it is defined as null-mounted from the build jail: 10-amd64 stable/10 amd64 null 2022-01-20 13:10:41 /X/j10a for some other reasons, there're definition in login.conf like :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,UNAME_r=10.4-STABLE,UNAME_v=FreeBSD 10.4-STABLE #0:\ however, bulk.sh/common.sh are unhappy with this breaking with sed: 1: "s/,UNAME_r.*:/:/ ; s/:\ ...": bad flag in substitute command: ',' I tracked this down to update_version_env() in common.sh, but then stuck did I miss something trivial? Thank you in advance! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] --------------------------------------------------------------------------- *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- woozle@woozle.net *** ---------------------------------------------------------------------------