During last weekend's rollover from Daylight Saving Time, a job scheduled for 02:10 each day was run twice: once at 01:10 GMT and again at 02:10 GMT. The first one would have been at 02:10 BST, but by then BST had finished and we were once again on GMT (a.k.a. UTC). The first run should not have taken place. The jobs were scheduled from the root crontab. My emerge info reads: Gentoo Base System version 1.6.13 Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13-gentoo-r3 i686) ================================================================= System uname: 2.6.13-gentoo-r3 i686 Unknown CPU Type dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.8.1-r1, 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-mp -mmmx -m3dnow -msse -mfpmath=387 -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-mp -mmmx -m3dnow -msse -mfpmath=387 -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.mirrorservice.org/sites/www.ibiblio.org/gentoo/ ftp://mirror.switch.ch/mirror/gentoo ftp://ftp.solnet.ch/mirror/Gentoo" LINGUAS="en_GB" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/lib/portage/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 3dnow X ada alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl doc dvd eds emboss encode esd f77 fam flac foomaticdb fortran gcj gd gdbm gif gnome gpm gstreamer gtk gtk2 imagemagick imlib ipv6 java jpeg junit kde libg++ libwww mad mikmod mmx motif mozilla mp3 mpeg ncurses nls nptl nptlonly objc odbc ogg oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline sdl slang spell sqlite ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts udev vorbis xine xml2 xmms xv zlib linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Have you tried contacting upstream regarding that observed behaviour?
(In reply to comment #1) > Have you tried contacting upstream regarding that observed behaviour? Given that there are 5 later releases in the Gentoo repository, I expect that the initial reply from upstream will be "Try a later release." I guess it's time to do just that, as November is coming around again. The difficulty is that I can seriously test it only once a year.
See changes.txt: From version 2.9.5.1 to 2.9.6 * fixed the bug which made jobs run an hour too early after a daylight saving time change. Added detailed explanations about when a job will run when there is a DST change in the FAQ. Thus this bug depends on bug 149376.
Apparently FIXED.
