[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#750639: marked as done (installing adjtimex gives syntax error message)

Your message dated Sun, 29 Nov 2015 16:24:58 +0900
with message-id <CAEQ9gE=jWD0_vufbtyzvb8KkKPu+mTXHsXrSW-=Me2b28wW8ug@mail.gmail.com>
and subject line Re: Bug#750639: installing adjtimex gives syntax error message
has caused the Debian Bug report #750639,
regarding installing adjtimex gives syntax error message
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
750639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750639
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: adjtimex
Version: 1.29-2.2
Severity: minor


Installing adjtimex gives the following syntax error
Setting up adjtimex (1.29-2.2) ...
egrep: character class syntax is [[:space:]], not [:space:]



-- System Information:
Debian Release: 6.0.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.32-5-kirkwood
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages adjtimex depends on:
ii  debconf [debconf-2.0]     1.5.49         Debian configuration management sy
ii  libc6                     2.13-38+deb7u1 Embedded GNU C Library: Shared lib

adjtimex recommends no packages.

Versions of packages adjtimex suggests:
pn  ntpdate                       <none>     (no description available)

-- debconf information:
  adjtimex/compare_rtc: true
  adjtimex/run_daemon: true

--- End Message ---
--- Begin Message --- 
This bug is the same as #630812, and is fixed in 1.29-3.
I'm trying to merge the two bugs, since #630812 is already closed,
#750639 need to be closed before the merging.

Cheers,
Roger

--- End Message ---
Reply to: