Your message dated Wed, 10 Sep 2008 12:11:15 +0200 with message-id <[email protected]> and subject line closing this bugreport has caused the Debian Bug report #495659, regarding base: prevent unix 2038 oveflow 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 [email protected] immediately.) -- 495659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495659 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---
- To: Debian Bug Tracking System <[email protected]>
- Subject: base: prevent unix 2038 oveflow
- From: public_debian <[email protected]>
- Date: Tue, 19 Aug 2008 23:45:07 +1000
- Message-id: <20080819134507.11719.48277.reportbug@majora_lenny.lan>
Package: base Severity: critical Tags: security Justification: breaks the whole system it should be made impossible to reach the unix overflow upcoming in 2038. There should be a facility to block entering such a date and ignoring ntp servers or other items that may influence he system clock that would cause the date to pass 2038. This should be altered when there is a patch / solution to the problem on a given system. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
- To: [email protected]
- Subject: closing this bugreport
- From: Holger Levsen <[email protected]>
- Date: Wed, 10 Sep 2008 12:11:15 +0200
- Message-id: <[email protected]>
Hi, I'm closing this bugreport as its quite useless: foremost it's a upstream issue in several packages (so if you really care about this, please file bug_s_ upstream), second, it's still 30 years and third, this is a well known issue (which wont be dealt with any better or faster just because of this bugreport). So in summary, leaving this bug open just prevents real issues to be visible. As usual, if you object, please speak up, we might listen ;-) regards, HolgerAttachment: pgpXwuxVLETol.pgp
Description: PGP signature
--- End Message ---