Re: The 'udebn' problem
- To: debian-boot@lists.debian.org
- Subject: Re: The 'udebn' problem
- From: stappers@stappers.nl (Geert Stappers)
- Date: Sat, 13 Sep 2003 14:59:05 +0200
- Message-id: <[🔎] 20030913145905.A17887@macwheel.xs4all.nl>
- In-reply-to: <87adaa3yo3.wl@badger.wordzoo.com>; from jared@wordzoo.com on Fri, Aug 15, 2003 at 11:27:08PM -0700
- References: <87d6fa8zt5.wl@badger.wordzoo.com> <87isoz4ept.wl@badger.wordzoo.com> <3F3CEBCB.2040904@beamnet.de> <87adaa3yo3.wl@badger.wordzoo.com>
On Fri, Aug 15, 2003 at 11:27:08PM -0700, Jared Rhine wrote:
> [Thomas == tv@beamnet.de on Fri, 15 Aug 2003 16:18:51 +0200]
>
> >> Any response would be appreciated. Is this a bug or not? Does
> >> this issue not hit anyone else when building from a fresh CVS?
>
> Thomas> This is not strictly a bug, but a build-dependence on
> Thomas> sed/unstable. However, I'd say a space instead of \n would do
> Thomas> as well in most cases.
>
> Ok, thanks. Leaving it as is seems fine; nobody serious is going to
> run into this problem, and now there's an explanation in the list
> archives for the next newbie to find.
>
> I can't confirm the fix currently, due to cvs.debian.org issues.
>
upgrading 'sed' does fix the problem.
Thanks for having it the list archives ;-)
Geert Stappers
Reply to: