[Touch-packages] [Bug 1986984] Re: [FFe] tzdata 2022c update
We've tried this with the Chile timezone and it worked fine.
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date -s "10 SEP 2022 23:59:00"
Sat Sep 10 23:59:00 -04 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date
Sat Sep 10 23:59:03 -04 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date
Sun Sep 11 01:00:02 -03 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date -s "3 SEP 2022 23:59:00"
Sat Sep 3 23:59:00 -04 2022
root@DESKTOP-1F8JISS:/opt/tzdata-cl# date
Sun Sep 4 00:00:18 -04 2022
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Released
Bug description:
New timezone data, with the following timezones impacted:
- Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
- Iran no longer observes DST (Asia/Tehran)
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v America/Santiago | grep 'Sep.*2022'
-> should indicate Sep 11, not Sep 4
2) zdump -v Asia/Tehran | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022a.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
[Original report]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968007] Re: $HOME/.local/bin not added to PATH env variable
Stumbled upon this bug when installing openstack client, on a brand new Ubuntu 22.04 installation. ``` ➜ ~ openstack zsh: command not found: openstack ➜ ~ find / -name openstack /home/jvleminckx/.local/lib/python3.10/site-packages/openstack /home/jvleminckx/.local/bin/openstack ... ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1968007 Title: $HOME/.local/bin not added to PATH env variable Status in bash package in Ubuntu: Confirmed Bug description: Although the path $HOME/.local/bin exists, it is not added to the path environment variable in Ubuntu 22.04. Re-logging or rebooting does not fix the problem. Manually running if [ -d "$HOME/.local/bin" ] ; then PATH="$HOME/.local/bin:$PATH" fi works as expected. The aboth lines ARE included in the .profile script. I know that there were already some issued with the mentioned path in previous versions of Ubuntu, however, until now installing some program with pip install --user and re-logging always fixed the issue. I'm running Ubuntu jammy in a VirtualBox (Version 6.1.32 r149290), but I don't think this is of any relevance. Output of ubuntu-bug bash: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:11:13 2022 Dependencies: base-files 12ubuntu3 bash-completion 1:2.11-5ubuntu1 debianutils 5.5-1ubuntu2 gcc-12-base 12-20220319-1ubuntu1 libc6 2.35-0ubuntu3 libcrypt1 1:4.4.27-1 libgcc-s1 12-20220319-1ubuntu1 libidn2-0 2.3.2-2build1 libtinfo6 6.3-2 libunistring2 1.0-1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Package: bash 5.1-6ubuntu1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor: 3 vendor_id: GenuineIntel cpu family : 6 model: 158 model name : Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz stepping : 10 cpu MHz : 2904.002 cache size : 12288 KB physical id : 0 siblings : 4 core id : 3 cpu cores: 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception: yes cpuid level : 22 wp : yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase avx2 invpcid rdseed clflushopt md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips : 5808.00 clflush size : 64 cache_alignment : 64 address sizes: 39 bits physical, 48 bits virtual power management: ProcEnviron: LC_TIME=de_DE.UTF-8 LD_LIBRARY_PATH= LC_MONETARY=de_DE.UTF-8 TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LC_ADDRESS=de_DE.UTF-8 LANG=en_US.UTF-8 LC_TELEPHONE=de_DE.UTF-8 SHELL=/usr/bin/zsh LC_NAME=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 SourcePackage: bash Tags: wayland-session jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1968007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
