devel/py-x-wr-timezone: Update to 2.0.1 Changes: https://github.com/niccokunzmann/x-wr-timezone/commits/main77f5e3071f
Port details
devel/py-x-wr-timezone 2.0.1
Python module and program to convert calendars using X-WR-TIMEZONE to standard ones
Port info
- Maintainer
- sunpoet@FreeBSD.org
- Packages
- latest: 2.0.1
- Upstream
- up to date
- Last update
- to 2.0.1 · 77f5e3071f
- Quarterly
- 2026Q4: 2.0.1
- WWW
- https://github.com/niccokunzmann/x-wr-timezone
- Links
- cgit · VuXML
Install
- Package
# pkg install py312-x-wr-timezoneinstalls 2.0.1 fromlatest; fromquarterly(2026Q4) 2.0.1- Port
# cd /usr/ports/devel/py-x-wr-timezone && make install clean- Size
- 16 KiB download · 58 KiB installed
- Depends on
- devel/py-click 8.5.0, devel/py-icalendar 6.1.1, devel/py-tzdata 2026.5, lang/python312 3.12.15
- License
- LGPL3+
Packages by version and architecture
latest
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 16 | 2.0.1 | 2.0.1 | – |
| FreeBSD 15 | 2.0.1 | 2.0.1 | – |
| FreeBSD 14 | 2.0.1 | 2.0.1 | 2.0.1 |
quarterly (2026Q4)
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 15 | 2.0.1 | 2.0.1 | – |
| FreeBSD 14 | 2.0.1 | 2.0.1 | 2.0.1 |
version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by
pkg audit for the packaged version 2.0.1.Fixed (0)
No VuXML entries for this package.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (8)
devel/py-x-wr-timezone: Update to 1.0.1 Changes: https://github.com/niccokunzmann/x-wr-timezone/commits/main61e7950756
devel/py-x-wr-timezone: Update to 0.0.7 - Convert to USE_PYTHON=pep517 Changes: https://github.com/niccokunzmann/x-wr-timezone/commits/main156983317a
devel/py-x-wr-timezone: Update to 0.0.6 Changes: https://github.com/niccokunzmann/x-wr-timezone/commits/master412ea4316a
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++ -DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable -Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi -Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings -Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x -MT _quickfix_la-QuickfixPython.lo -MD -MP -MF .deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o .libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>3d9a815d9cdevel/py-x-wr-timezone: Update WWW859fd79f8d
*/py-: Fix MASTER_SITES after CHEESESHOP to PYPI trasitiona58124c5ff
devel/py-x-wr-timezone: Add py-x-wr-timezone 0.0.5 Some calendar providers introduce the non-standard X-WR-TIMEZONE parameter to ICS calendar files. Strict interpretations according to RFC 5545 ignore the X-WR-TIMEZONE parameter. This causes the times of the events to differ from those which make use of X-WR-TIMEZONE. This module aims to bridge the gap by converting calendars using X-WR-TIMEZONE to a strict RFC 5545 calendars. So, let's put our heads together and solve this problem for everyone!a379947660