awk error reported on initial install of adjtimex package in lucid

Bug #883517 reported by FactTech
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
adjtimex (Ubuntu)
New
Undecided
Unassigned

Bug Description

When first installing the adjtimex package, the following errors were generated:

Setting up adjtimex (1.28-1) ...
update-rc.d: warning: adjtimex start runlevel arguments (S) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: adjtimex stop runlevel arguments (none) do not match LSB Default-Stop values (0 1 6)
Regulating system clock...done.
Comparing clocks (this will take 70 sec)...done.
awk: BEGIN{print ((to-10000)*100 + override)./65536.)*.0864}
awk: ^ syntax error
awk: BEGIN{print ((to-10000)*100 + override)./65536.)*.0864}
awk: ^ unterminated regexp
awk: cmd. line:1: BEGIN{print ((to-10000)*100 + override)./65536.)*.0864}
awk: cmd. line:1: ^ unexpected newline or end of string
Adjusting system time by sec/day to agree with CMOS clock...done.

Note that I retyped the message above, so the spacing of the carets may not be correct if displayed in a fixed-width font. In order of appearance, the carets were pointing at:

1. the '.' in 'override)./65536'
2. the first '6' in 'override)./65536'
3. the space after the ending curly brace (i.e. end of the entire command)

The package seems to work correctly when executing adjtimex commands, it just seems that autoconfiguration failed when the package was first installed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.