Your message dated Tue, 18 Oct 2022 23:40:53 +0200 with message-id <Y08dZQfCq8LXpZ38@aurel32.net> and subject line Re: Bug#1021977: Fwd: Tzdata timezone files corruption after clean debian 11 installation has caused the Debian Bug report #1021977, regarding Tzdata timezone files corruption after clean debian 11 installation 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.) -- 1021977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021977 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Cc: owner@bugs.debian.org
- Subject: Tzdata timezone files corruption after clean debian 11 installation
- From: Satish Binda <satishbinda83@gmail.com>
- Date: Tue, 18 Oct 2022 10:04:23 +0200
- Message-id: <[🔎] CAA8HVAwg-S-g91AfvARBtNori4zVY3OXM5xmEsYAdtdHX3=p=w@mail.gmail.com>
Package: tzdataVersion: 2021a-1+deb11u7Dear Debian,I wanted to change my timezone from europe/amsterdam to utc.when i viewed the europe/amsterdam timezone file. I got corruption or malwareas I included in this email.All zone files as I can see contain either corruption or malware.This is on a fresh install of debian 11.I am going to reinstall the tzdata package if possible; but it is quite a breach.Yours truly,Satish BindaThe Netherlands(ultra violence / agent 1 / kick some dust)
--- End Message ---
--- Begin Message ---
- To: Satish Binda <satishbinda83@gmail.com>, 1021977-done@bugs.debian.org
- Subject: Re: Bug#1021977: Fwd: Tzdata timezone files corruption after clean debian 11 installation
- From: Aurelien Jarno <aurel32@debian.org>
- Date: Tue, 18 Oct 2022 23:40:53 +0200
- Message-id: <Y08dZQfCq8LXpZ38@aurel32.net>
- In-reply-to: <[🔎] CAA8HVAx2bNpdyhc1R-NeKwR4u-7KsDt=Zhy8JnygtAwYAV2YAQ@mail.gmail.com>
- References: <[🔎] CAA8HVAwg-S-g91AfvARBtNori4zVY3OXM5xmEsYAdtdHX3=p=w@mail.gmail.com> <CAA8HVAwTBCRHF8F=djrZXzmvFwqJzeR3Fi6_Vppom4hUYF2Dig@mail.gmail.com> <[🔎] Y072CNBFtK9WHbwQ@aurel32.net> <CAA8HVAy7mgCzjvyvoU9Xr3UYH9TWKN0Q4VrpnU-BSiK8VSNMbA@mail.gmail.com> <[🔎] Y08Lk7A1FveEbTZ1@aurel32.net> <[🔎] CAA8HVAwg-S-g91AfvARBtNori4zVY3OXM5xmEsYAdtdHX3=p=w@mail.gmail.com> <[🔎] CAA8HVAx2bNpdyhc1R-NeKwR4u-7KsDt=Zhy8JnygtAwYAV2YAQ@mail.gmail.com>
Ok, thanks for your answer, closing the bug On 2022-10-18 22:56, Satish Binda wrote: > Thank you for the clarification. > > On Tue, Oct 18, 2022, 22:24 Aurelien Jarno <aurel32@debian.org> wrote: > > > Dear Satish, > > > > On 2022-10-18 22:17, Satish Binda wrote: > > > because normally it is just one line ascii or ansi or utf-8, perhaps > > utf-16 > > > but not an easy to digest binary file, at length, that no one knows about > > > > That is not correct. The file format is described by RFC8536 [1] and is > > a binary format. > > > > Regards > > Aurelien > > > > [1] https://datatracker.ietf.org/doc/html/rfc8536 > > > > -- > > Aurelien Jarno GPG: 4096R/1DDD8C9B > > aurelien@aurel32.net http://www.aurel32.net > > -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
--- End Message ---