166103 – The init script provided by the fcron package doesn't work because is not bsd-sed compatible

Bug 166103 - The init script provided by the fcron package doesn't work because is not bsd-sed compatible

Summary: The init script provided by the fcron package doesn't work because is not bsd...

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo/Alt
Classification:	Unclassified
Component:	FreeBSD (show other bugs)
Hardware:	x86 FreeBSD

Importance:	High normal
Assignee:	Gentoo/BSD Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-02-09 17:33 UTC by Emanuele A. Bagnaschi (Zephyrus)
Modified:	2007-02-13 16:45 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
/etc/init.d/fcron patch (init-fcron.patch,816 bytes, patch) 2007-02-09 17:34 UTC, Emanuele A. Bagnaschi (Zephyrus)	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Emanuele A. Bagnaschi (Zephyrus) 2007-02-09 17:33:52 UTC

The init script installed by the fcron package is not compatible with the bsd sed because it uses escape sequences in the substitution command.

A possibile workaround is to replace the escape sequence '\s', used in the script, with '[[:space:]]'. This seems to work with both bsd-sed and gsed.
Note: This solution was find by exg.


Reproducible: Always

Comment 1 Emanuele A. Bagnaschi (Zephyrus) 2007-02-09 17:34:24 UTC

Created attachment 109656 [details, diff]
/etc/init.d/fcron patch

Comment 2 Wolfram Schlich (RETIRED) gentoo-dev

2007-02-13 16:45:38 UTC

Thanks, fixed in CVS *sigh*