similar to: updating tzdata on CentOS 7

On 3/30/2015 9:12 PM, Dulmandakh wrote: > Government of Mongolia decided to adopt DST from this 28th March 2015. It?s changes are submitted and accepted by IANA. It seems that update to tzdata (2015b) issued for CentOS 6, but not for CentOS 7. Could you please tell when an update for CentOS 7 will be issued? I believe all 7 updates are on hold til 7.1 releases, 'any day now'. --

Hello, > I believe all 7 updates are on hold til 7.1 releases, 'any day now?. We?re having a bit of mess in here :D

CentOS Errata and Enhancement Advisory 2015:0717 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-0717.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2b56f79674b637d07220a872a862ed34f89b7cfe02b91f5487e50d7bf1b46f96 tzdata-2015b-1.el6.noarch.rpm

CentOS Errata and Enhancement Advisory 2015:0717 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-0717.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6cd1206807384458d156a57a5bc991da98c00fbd612346d52cb4e5b972036bbf tzdata-2015b-1.el5.i386.rpm

My current version is supermin 5.1.8-1 > > If the tests *don't* run successfully, then you've most likely found a > bug in supermin. That has to be fixed before continuing. > tests failed. See the log below. ========================================== supermin 5.1.9: tests/test-suite.log ========================================== # TOTAL: 8 # PASS: 5 # SKIP: 0 # XFAIL:

CentOS Errata and Enhancement Advisory 2015:0717 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-0717.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 818c1d17d5adb9ab3d6757430050e8070e06e2af4ee54a1d8bdfb0cb460722ee tzdata-2015b-1.el7.noarch.rpm

Sorry for the extra info required, but I had digest mode turned on and wouldn't have received the mailing till tomorrow. I have since updated the data manually, but after 'yum update tzdata' was run, the zdump -v for EST5EDT and America/New_York all still showed a date of April 1, instead of March 11. After manually fixing, it is correct. This was mostly a question about why yum

I might be stupid and ask an idiot or offensive question, but here it is: "Why was tzdata-2007h [RHEA-2007:0928-05] only released for CentOS 2, when upstream has released it for all the versions?" The guys from X/OS have released it for 5.0 along with the other updates (on Oct. 9). Are the "enhancements"... "not important" as long as they're not "security

I read a few days back on the list where the tzdata rpm was to take care of the new DST rules. I run CentOS 3 servers, and did a 'yum update tzdata' , but received a 2006a update of the rpm. Is this proper? It sure didn't fix anything. Thanks Steve Campbell campbell at cnpapers.com Charleston Newspapers

I am installed CENTOS 5.5 on X86. After finish, I tried to apply latest patches. Rpm patch manager say need "dependency" "tzdata-java-20101-1.e15". I search CENTOS 5.5 CD and can NOT find this file. I also search Internet and no result. Can anyone tell me where to download "tzdata-java-20101-1.e15" RPM? Thanks.

Previously the packages were built 6 Dec 2022 published 13 Dec 2022. Now the download packages are rebuilt 30 Mar 2023 published 03 Apr 2023. http://mirror.centos.org/centos/7/updates/x86_64/Packages/tzdata-2022g-1.el7.noarch.rpm http://mirror.centos.org/centos/7/updates/x86_64/Packages/tzdata-java-2022g-1.el7.noarch.rpm Why would a previously published package be re-published with different

I don't see the tzdata updates for 2006m in the centos 3 mirrors ?!? http://mirror.centos.org/centos-3/3/updates/i386/RPMS/ its here for centos4... http://mirror.centos.org/centos-4/4/updates/i386/RPMS/tzdata-2006m-3.el4.noarch.rpm and here for 2.1, http://mirror.centos.org/centos-2/updates/noarch/tzdata-2006m-3.el2_1.noarch.rpm so where is it for centos3 ?!? my RHN connected RHEL3 system

Hi! It appears that there have been some changes to tzdata recently. We run an application that needs the server to stay at GMT. Previously, we used the Casablanca timezone but now there seems to be a 1 hour difference to GMT. I checked the London zone and they seem to change time too. I tried to change the zone to GMT with system-config-date (i'm using command line remotely) but

Hi All, I guess this is a political question rather than technical. New Zealand is probably extending daylight saving time with a bill currently being drafted. It will (most likely) change the end data of dst by pushing it out ~3 weeks. My question; AFAIK CentOS/whitebox/et. al. should not make any changes to tzdata - it is an upstream issue, but how do we ensure that 'upstream'

http://lists.digium.com/pipermail/asterisk-users/2003-March/008088.html "why is there such a delay in getting ipv6 rolled out when it solves all these problems ?" === There are many reasons... 1. Leasing Address Space from the I* society (small s...aka the Big Lie Society) is not desirable by all people... 2. The IPv6 Privacy Problem...that is especially important in the area of computer

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi list. Does "yum update tzdata" update /etc/localtime or does this need to be done manually? [this is part of the hwclock problem, a guy from sage-au has given me a hint] Jobst -- Keyboard not found - please clean up desktop! | |0| | Jobst Schmalenbach, jobst at barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0|

Just idly watching * in console mode and saw that someone from 50.49.54.102 tried to register with my *. whois gives:- OrgName: Internet Assigned Numbers Authority OrgID: IANA Address: 4676 Admiralty Way, Suite 330 City: Marina del Rey StateProv: CA PostalCode: 90292-6695 Country: US NetRange: 50.0.0.0 - 50.255.255.255 CIDR: 50.0.0.0/8 NetName: RESERVED-50

After reading this article: http://www.theregister.co.uk/2005/08/31/blocking_chinese_ip_addresses/ I got to thinking that there is really no reason for *any* traffic to hit my servers that comes from anywhere outside North America. So I wrote the perl script at the end of this posting to extract selected IP ranges posted at iana.org and convert them into iptables rules blocking any traffic

> > I suspect that you could fix this by running the following command as > before the build: > > sudo pacman -Sy I always sue -Syu to install packages, and I already installed/reinstalled some packages today. Now one thing comes to my mind : lots of pacman stuff are NOT in the usal place. $ cat /etc/pacman.conf ----------------------------------- [options] # The following