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

Bug#436140: marked as done (cdrom: Most of the system's files have a future timestamp causing at least update/config problems.)

Your message dated Sat, 13 Dec 2008 16:10:01 -0500
with message-id <7eec34120812131310g3d7c386dtdb5f0cab45866460@mail.gmail.com>
and subject line Re: Bug#436140: cdrom: Most of the system's files have a future timestamp causing at least update/config problems.
has caused the Debian Bug report #436140,
regarding cdrom: Most of the system's files have a future timestamp causing at least update/config problems.
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.)


-- 
436140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436140
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cdrom
Severity: grave


I cannot determine the exact extend of the problem, but a "ls -la" in "/" reveals this:

drwxr-xr-x  23 root root  4096 2008-01-02 21:14 .
drwxr-xr-x  23 root root  4096 2008-01-02 21:14 ..
drwxr-xr-x   2 root root  4096 2008-01-02 21:13 bin
drwxr-xr-x   3 root root  4096 2007-06-10 13:50 boot
lrwxrwxrwx   1 root root    11 2008-01-02 19:57 cdrom -> media/cdrom
drwxr-xr-x  14 root root  4340 2007-08-05 17:49 dev
drwxr-xr-x 108 root root  4096 2007-08-05 18:35 etc
drwxr-xr-x  16 root root  4096 2007-06-10 16:00 hdb
drwxr-xr-x   5 root root  4096 2007-06-10 17:01 home
drwxr-xr-x   2 root root  4096 2008-01-02 19:58 initrd
lrwxrwxrwx   1 root root    28 2008-01-02 20:00 initrd.img ->
boot/initrd.img-2.6.18-4-486
drwxr-xr-x  15 root root  4096 2008-01-02 21:12 lib
drwx------   2 root root 16384 2008-01-02 19:57 lost+found
drwxr-xr-x   3 root root  4096 2007-07-17 00:55 media
drwxr-xr-x   2 root root  4096 2006-10-28 16:06 mnt
drwxr-xr-x   2 root root  4096 2008-01-02 19:58 opt
dr-xr-xr-x 111 root root     0 2007-08-05 17:48 proc
-rw-------   1 root root  1024 2008-01-02 21:14 .rnd
drwxr-xr-x   8 root root  4096 2007-06-10 16:30 root
drwxr-xr-x   2 root root  4096 2008-01-02 21:43 sbin
drwxr-xr-x   2 root root  4096 2007-03-07 23:56 selinux
drwxr-xr-x   2 root root  4096 2008-01-02 19:58 srv
drwxr-xr-x  11 root root     0 2007-08-05 17:48 sys
drwxrwxrwt  12 root root  4096 2007-08-05 18:50 tmp
drwxr-xr-x  11 root root  4096 2008-01-02 21:08 usr
drwxr-xr-x  15 root root  4096 2008-01-02 21:41 var
lrwxrwxrwx   1 root root    25 2008-01-02 20:00 vmlinuz ->
boot/vmlinuz-2.6.18-4-486

As you can see, for what reason ever, this installation produced future timestamps on vital directories causing update mechanisms to fail and to
complain *all the time*.

Installation history:

- CD-ROM debian-40r0-i586-netinst
- Updates taken as indicated by notifier icon

The first symptom was the notorious "ttf-opensymbol" update failure, probably caused by various font directories tagged with future
timestamps (/usr/share/fonts, /usr/X11R6/lib/X11/fonts/, ...) but this bug's effects are obviously not restricted to these places.

Since the update infrastructure fails, security fixes can no longer be applied. This however makes the system unusable.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message --- 
Hi,

I was unable to reproduce this with the current netinst
(debian-40r5-i386-netinst.iso). In my fresh (minimal) installation,
all of the timestamps were correct.

In the original reporter's output, the future timestamps are all on
files that are autogenerated by the installer. This leads me to
suspect that the reporter's system clock was just incorrect at
installation time, and that things are actually fine.

--- End Message ---
Reply to: