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

Bug#764410: marked as done (wheezy-pu: package tzdata/2014h-0wheezy1)

Your message dated Sat, 18 Oct 2014 12:06:31 +0100
with message-id <E1XfRqB-0002UF-7X@jacala>
and subject line Closing bugs for updates in 7.7
has caused the Debian Bug report #764410,
regarding wheezy-pu: package tzdata/2014h-0wheezy1
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.)


-- 
764410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764410
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian.org@packages.debian.org
Usertags: pu

As discussed on IRC, I have uploaded a new upstream version of tzdata
to wheezy, matching the one we have in jessie/sid. It has updates for
historical and future changes. The changelog lists the future changes:

| tzdata (2014h-0wheezy1) stable; urgency=medium
| 
|   * New upstream version.
|     - New DST for Russia (closes: #761267).
|     - Timezone change for Turks & Caicos.
| 
|  -- Aurelien Jarno <aurel32@debian.org>  Tue, 07 Oct 2014 22:54:07 +0200

The above change will happen after October 18th, so there is no need to
go through wheezy-updates.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Version: 7.7

The upload discussed in this bug was included in the 7.7 point release.

Regards,

Adam

--- End Message ---
Reply to: