Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-11-22 Thread Colin Watson
On Thu, Oct 26, 2006 at 03:25:33AM +0200, Frans Pop wrote: On Wednesday 25 October 2006 23:12, Sven Luther wrote: It seems that nobootloader uses still devfs paths for some reason. The following line : That is not so strange as that line is using the exact same variable $bootfs_devfs as

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-11-22 Thread Sven Luther
On Wed, Nov 22, 2006 at 09:32:27AM +, Colin Watson wrote: On Thu, Oct 26, 2006 at 03:25:33AM +0200, Frans Pop wrote: On Wednesday 25 October 2006 23:12, Sven Luther wrote: It seems that nobootloader uses still devfs paths for some reason. The following line : That is not so

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-11-22 Thread Colin Watson
On Wed, Nov 22, 2006 at 12:05:45PM +0100, Sven Luther wrote: On Wed, Nov 22, 2006 at 09:32:27AM +, Colin Watson wrote: Don't be misled by the variable name. It's called $bootfs_devfs because it's the path before calling mapdevfs; if you aren't using devfs paths then $bootfs_devfs and

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-10-26 Thread Sven Luther
On Thu, Oct 26, 2006 at 03:25:33AM +0200, Frans Pop wrote: On Wednesday 25 October 2006 23:12, Sven Luther wrote: It seems that nobootloader uses still devfs paths for some reason. The following line : That is not so strange as that line is using the exact same variable $bootfs_devfs as

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-10-26 Thread Frans Pop
On Thursday 26 October 2006 09:10, Sven Luther wrote: That said, please also apply the first hunk of the attached patch, which bumps the check to 1.4, as my colegues released a 1.3 firmware from an older tree, and i had to bump the version of the version with the correct disk numbering. No

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-10-26 Thread Frans Pop
On Thursday 26 October 2006 09:10, Sven Luther wrote: That said, please also apply the first hunk of the attached patch, which bumps the check to 1.4, as my colegues released a 1.3 firmware from an older tree, and i had to bump the version of the version with the correct disk numbering.

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-10-26 Thread Sven Luther
On Thu, Oct 26, 2006 at 01:33:55PM +0200, Frans Pop wrote: On Thursday 26 October 2006 09:10, Sven Luther wrote: That said, please also apply the first hunk of the attached patch, which bumps the check to 1.4, as my colegues released a 1.3 firmware from an older tree, and i had to bump the

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-10-26 Thread Frans Pop
On Thursday 26 October 2006 19:39, you wrote: Did you see the new version i attached : No, initially I did not see this. Reason is simple: I had already applied your original patch and closed the BR, so I looked in the original bug report instead of in your new mail. Is that my mistake, maybe.

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-10-25 Thread Sven Luther
Package: nobootloader Version: 1.12 Severity: grave Tags: patch Justification: renders package unusable It seems that nobootloader uses still devfs paths for some reason. The following line : part=$(($(echo $bootfs_devfs | sed 's/[^0-9]*//') - $partition_offset)) will fail on paths like this

Bug#395259: nobootloader: [powerpc/pegasos] bad sed invocation breaks devfs style paths (division by zero)

2006-10-25 Thread Frans Pop
On Wednesday 25 October 2006 23:12, Sven Luther wrote: It seems that nobootloader uses still devfs paths for some reason. The following line : That is not so strange as that line is using the exact same variable $bootfs_devfs as its base that the old code did... Should it be using something