ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: ALTLinux devel <devel@altlinux.ru>
Subject: Re: [devel] %__subst changes?
Date: Wed, 3 Mar 2004 20:48:06 +0300
Message-ID: <20040303174806.GE18379@master.mivlgu.local> (raw)
In-Reply-To: <m38yihg7iv.fsf@mrkooll.tdr.pibhe.com>

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]

On Wed, Mar 03, 2004 at 07:33:28PM +0200, Maxim Tyurin wrote:
> Просветите plz какие изменения в subst (sed) произошли?
> Перестал обрабатывать такую конструкцию в спеке:
>  %__grep -r /etc/ipsec.secrets * \
> | %__awk '{ print $1 }' \
> | %__sed -e 's|:.*$|\1|' \
> | xargs %__subst 's|/etc/ipsec.conf|/etc/super-freeswan/ipsec.conf|';
> 
> Ругается 
> + /bin/grep -r /etc/ipsec.secrets BUGS CHANGES CHANGES.AggressiveMode CHANGES.SUPERFS CHANGES.X509 CHANGES.ipsec_alg COPYING CREDITS INSTALL Makefile Makefile.inc Makefile.ver README README.AggressiveMode README.DPD README.NAT-Traversal README.SUPERFS README.ipsec_alg README.selectors README.x509 contrib doc klips lib libcrypto libdes packaging pluto rpm.in testing utils zlib
> + gawk '{ print $1 }'
> + /bin/sed -e 's|:.*$|\1|'
> /bin/sed: -e expression #1, char 10: Invalid reference \1 on `s' command's RHS
> ошибка: Неверный код возврата из /home/mrkooll/tmp/rpm-tmp.44577 (%prep)

Так он не на subst дохнет, а на предыдущем sed.  И правильно делает - что
может обозначать ссылка '\1' в правой части, если в левой части нет
'\(..\)'?

В старом sed это, похоже, работало как 's|:.*$||' - предполагалось именно
это?

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-03-03 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 17:33 Maxim Tyurin
2004-03-03 17:48 ` Sergey Vlasov [this message]
2004-03-03 17:59   ` Maxim Tyurin
2004-03-03 18:17     ` Sergey Vlasov
2004-03-03 18:24       ` Maxim Tyurin
2004-03-03 22:05 ` Dmitry V. Levin
2004-03-04  7:33   ` Maxim Tyurin
2004-03-04  8:03     ` [devel] " Michael Shigorin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040303174806.GE18379@master.mivlgu.local \
    --to=vsu@altlinux.ru \
    --cc=devel@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git