Your message dated Mon, 15 Dec 2025 23:20:44 +0000
with message-id <[email protected]>
and subject line Bug#605834: fixed in tzdata 2025c-2
has caused the Debian Bug report #605834,
regarding tzdata update stomps preseeded timezone (breaks Oracle connections)
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.)


-- 
605834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605834
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tzdata
Version: 2010o-0lenny1
Severity: important


Our 2000+ servers are preseeded to UTC during auto-installs via

        d-i time/zone string UTC

But when the tzdata package is updated, and our development servers
auto-update, tzdata's config script stomps on the d-i preseeded value
of "UTC", tragically changing it to "Etc/UTC" in /etc/timezone :

This has the unfortunate side effect of killing all subsequent connections
to our databases due to an Java vs. Oracle bug (irony alert) :

        http://forums.oracle.com/forums/thread.jspa?threadID=958265
          Java's Timezone.getDefaultTimezone() returns 'Etc/UTC', and
        this is apparently not a valid timezone in Oracle. ...
          But I still think this is abug in Oracle's Timezone data, as  
        'Etc/UTC' is indeed a valid timezone ID.

On our killed clients, and in the ( http://squirrel-sql.sourceforge.net/ )
squirrel-sql UI, this manifests as

        configdb: ORA-00604: error occurred at recursive SQL level 1
        ORA-01882: timezone region not found


Had this happened in our production environment, it would have killed the site,
which I'm told is a Very Bad Thing (TM) in some circles.  As it was, it caused
lots of testing to abort, and made for a bad day for me.

I'd posit that the tzdata config script should respect d-i preseeded (or 
manually set) choices of timezone, as long as the timezone is valid/exists.
Secondarily, it should be able to represent all available timezone choices
(eg; UTC vs Etc/UTC).

If I get a chance this weekend I'll take a stab at a patch, but I at
least need to get the issue on the radar now.

-- System Information:
Debian Release: 5.0.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]         1.5.24     Debian configuration management sy

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Australia:
  tzdata/Zones/Asia:
  tzdata/Zones/SystemV:
  tzdata/Zones/Pacific:
  tzdata/Zones/Atlantic:
* tzdata/Zones/Etc: GMT
  tzdata/Zones/Arctic:
  tzdata/Zones/Antarctica:
  tzdata/Zones/Europe:
  tzdata/Zones/Africa:
* tzdata/Zones/America: Denver
* tzdata/Areas: America
  tzdata/Zones/Indian:



--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2025c-2
Done: Aurelien Jarno <[email protected]>

We believe that the bug you reported is fixed in the latest version of
tzdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <[email protected]> (supplier of updated tzdata package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 15 Dec 2025 23:51:19 +0100
Source: tzdata
Architecture: source
Version: 2025c-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers <[email protected]>
Changed-By: Aurelien Jarno <[email protected]>
Closes: 605834 813226 822733
Changes:
 tzdata (2025c-2) unstable; urgency=medium
 .
   * Remove /etc/timezone on upgrade (Closes: #605834, #813226, #822733)
Checksums-Sha1:
 b8ba71d91a0329fe6edadfdad6defd3bb05e40f2 2434 tzdata_2025c-2.dsc
 23c4e535a0f3443cf7611e95522243fcf8ad0be4 127516 tzdata_2025c-2.debian.tar.xz
 63df9f7d950ba65df58031e0a5d38cda8440b75d 5423 tzdata_2025c-2_source.buildinfo
Checksums-Sha256:
 7f1abb4db7b93dab93c5aa35cdc748b1f5cf7c80c32097f319ec7620fa789a68 2434 
tzdata_2025c-2.dsc
 02779eb9b01d2e2ec9418387d42db06ef1fccb5454486dbda16a6603483cde63 127516 
tzdata_2025c-2.debian.tar.xz
 f61931f012f776da766c1bf7e879b1ad6dd02bb6315d63ed27b040102eb5e625 5423 
tzdata_2025c-2_source.buildinfo
Files:
 b57067e7bd38c345f0e6d237cdc650ec 2434 localization required tzdata_2025c-2.dsc
 98c58bd3d6630693a9a1098e586605ae 127516 localization required 
tzdata_2025c-2.debian.tar.xz
 0a74673cf4df05b3ae00a28ee330cd40 5423 localization required 
tzdata_2025c-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmlAk+oACgkQE4jA+Jno
M2sc+hAAoBqyO55VVttUtvo7788DNpbHLU9qPNp1eqWMrMQYW9xwDWOPgtPggPzV
yVw032/du6P7L4KGlxRxiNdvdpww2HDgjSkJoLwZh9xnxGiPbAjGbZSGyqxLj3k+
QRDE+12aBlx+r8BDyHkE1TpP5tTPy6gEuL3+m4BF6Y7jYTF1q/JvlxwBWUg3zTBf
aU4g4tZ3j76WX3rYzbp97+Y7k5kz+iEB+ZCnH0FhA8FGqh/hO/U4/jIMp/686FEp
Gkfaos5nIYyIvm0ygW54Keyg10Ay/xZPavzPsOa346Yryd/Cc1CCfkyRbv0hfsuk
oY38NbcEIN1QN9ViNWBLqH6H6gGaFhcxFS2EdE3sPeoXA44LJqfb+FmrwgJZW5Dd
rrFKo/Fy1nOKcX0W8ylNqJcSVxNMelvf7TIC6WnyZS+lXdpyql4yDQ+hq4RqDXRI
z/wJuiFlVM45fQN8X+kDopdEQ+OAdcigbXlxy6OXTo8SxsmFARpAeP/NmbPj8Q6n
enlenQ+VXmoAWaazjuDC09O7OD6nv7HSaxSOAsNM9C9OBp0hQw5i6aSgX5sH6v/k
ByttIIXpISupEqq2OYd5dqF9pYaqzNymgk2pelEdgpxJ4XUYG9ThHAw5i8ZK74km
7r418doy0XxFI8+dVKHSig20vJieyUx7CPT3BVkpyqoWZKi/zVE=
=sX7D
-----END PGP SIGNATURE-----

Attachment: pgpLSQIXRnWs0.pgp
Description: PGP signature


--- End Message ---

Reply via email to