pkgsrc-Changes archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
CVS commit: pkgsrc/time/py-icalendar
Module Name: pkgsrc
Committed By: wiz
Date: Wed Aug 19 16:53:26 UTC 2026
Modified Files:
pkgsrc/time/py-icalendar: Makefile PLIST distinfo
Log Message:
py-icalendar: update to 7.3.0.
Removals and deprecations
obj is deprecated in favor of bytes. It is retained as a lossy
string view of the value for backward compatibility, and will
be removed in icalendar 8. The
test_ical_value_rejects_non_base64_characters test was removed
because vBinary.ical_value no longer validates or decodes
Base64. @uwezkhan (Issue #1356)
Issue #1362
New features
Created an example() method for the Journal component and an
example() method for the FreeBusy component, added the RFC 5545
examples that they load, and documented their usage in both
class docstrings. AI assistance: Kiro CLI with the claude-opus-5
model was used to draft this change. @Souptik96 (Issue #743)
Add Alarm.new_display(), Alarm.new_audio(), and Alarm.new_email()
factory methods for creating RFC 5545 Section 3.6.6 VALARM
components. @klouds27 (Issue #865)
vBinary now stores the raw bytes of the value internally, so
non-UTF-8 binary data round-trips losslessly. With the release
of icalendar 7.1.0, and previous to this bug fix, vBinary.ical_value
Base64-decoded the raw stored bytes and raised ValueError for
non-Base64 input. vBinary.ical_value now returns the raw stored
bytes instead of Base64-decoding them, and no longer raises
ValueError for non-Base64 input. @uwezkhan (Issue #1356)
Added icalendar.prop.binary.vBinary.bytes, exposing the raw
binary value of a BINARY property. @uwezkhan (Issue #1356)
Added the ICalParsingError exception as a public API for
programmatic handling of iCalendar parsing failures. AI
assistance: ChatGPT was used to help debug terminal errors
encountered during development. @GAUTAMSANSWAL (Issue #1536)
Created a script to automatically generate the windows_to_olson
module from the Unicode Consortium's CLDR GitHub repository.
Added lxml as a new development dependency. Added the target
wo to the Makefile to generate the file from the root of the
repository with make wo. @stevepiercy (Issue #1548)
Added vBinary.base64data, a getter/setter for the Base64 string
view of a BINARY property's value, so callers no longer need
to call base64.b64encode() or base64.b64decode() manually.
@gagana2023 (Issue #1550)
Added Alarm.ACTION and AlarmTime.action access to the RFC 5545
Section 3.8.6.1 ACTION property. I used OpenAI Codex with GPT-5
to assist with this change, then reviewed and tested the result.
@bm1016bm-svg (Issue #1569)
Record the exact CLDR commit used to generate the Windows-to-Olson
timezone mapping and fetch the mapping from that pinned revision.
I used AI to assist me with this change. @patrickswedish (Issue
#1575)
Used vBinary.from_ical() in Image.data for consistent Base64
validation, removing the manual base64.b64decode() call.
@klouds27 (Issue #1638)
Added REQUEST_STATUS property to Event, Todo, Journal, and
FreeBusy with request_status parameter in new() constructors
per RFC 5545 Section 3.8.8.3. I used AI to assist with this
change. @SemTiOne (Issue #1666)
Improved ICalParsingError by including optional value, line,
and line number information in exception messages for more
consistent iCalendar parsing error reporting. AI assistance:
ChatGPT was used to help debug terminal errors encountered
during development. @GAUTAMSANSWAL
Made JCalParsingError inherit from InvalidCalendar for consistency
with ICalParsingError. AI assistance: ChatGPT was used to help
debug terminal errors encountered during development. @GAUTAMSANSWAL
Bug fixes
Resolve the timezone of a "globally unique" RFC 5545 Section
3.2.19 TZID such as /freeassociation.sourceforge.net/Europe/Berlin,
which is emitted by some clients, including libical and Evolution.
TZP.timezone now strips the leading vendor prefix and resolves
the trailing Olson identifier, so the value is parsed as
timezone-aware instead of being silently treated as naive.
Prepared with AI assistance. @vjsai (Issue #313)
Fixed the equivalent_timezone_ids.py script after the call to
generate the timezone Python code was removed. @gjabell (Issue
#1392)
Values of unrecognized properties and X- properties without a
VALUE parameter were altered by escaping when parsed, serialized,
or converted to and from jCal, so they did not round-trip
unchanged as RFC 7265 specifies. These values are now preserved
verbatim. Additionally, the PROXIMITY property (RFC 9074) was
treated as an unknown value type instead of TEXT and is now
recognized correctly. AI disclosure: I used Claude Code
(Anthropic's Claude Opus) to draft and refine this change and
its tests; I reviewed the output and validated the change
locally. @lcampanella98 (Issue #1445)
Ship funding.json in PyPI source distributions so packaging
and test runs from the sdist no longer fail with FileNotFoundError.
@Hishamkhashman1 (Issue #1493)
Avoid folding content lines between escape prefixes and their
escaped characters. AI disclosure: I used GPT-5 Codex to help
draft and refine this change and its tests; I reviewed and
validated the output locally. @kingrubic (Issue #1501)
Preserve URI value parameters on a jCal round-trip. vUri.from_jcal
previously passed the parameters positionally, but vUri.__new__
takes encoding as its second positional parameter. As a result,
the URI value parameters were consumed as encoding and dropped.
For example, ATTACH;FMTTYPE=... or CONFERENCE;FEATURE=... lost
their parameters. They are now passed as the params keyword.
Prepared with the assistance of an AI coding agent (Anthropic's
Claude Opus 4.8). @gaoflow (Issue #1526)
Updated the Windows timezone mapping for Mountain Standard Time
(Mexico) to America/Mazatlan, so dates after Mexico's 2022
timezone changes use the correct UTC-7 offset instead of UTC-6.
Prepared with AI assistance. @RobHannay (Issue #1546)
IMAGE properties now use their explicitly declared VALUE type
instead of always being parsed as unknown, while IMAGE without
a VALUE parameter remains unknown. I used OpenAI Codex with
GPT-5 to assist with this change. @floze-the-genius (Issue
#1561)
Removed ATTACH from Alarm.singletons. An "email" VALARM may
carry more than one ATTACH per RFC 5545 Section 3.6.6, so ATTACH
belongs in multiple only; it was previously listed in both
singletons and multiple. Added a regression test that singletons
and multiple are disjoint for every registered component.
Prepared with the assistance of an AI coding agent (Anthropic's
Claude Opus 4.8). @vtino17 (Issue #1569)
Alarm.REPEAT, Alarm.repeat, Event.sequence, and Event.priority
now reject non-integers (including booleans) with TypeError
and negative values with InvalidCalendar. @heyncth (Issue #1594)
Added the missing BINARY member to icalendar.enums.VALUE, per
RFC 5545 Section 3.2.20. VALUE.BINARY previously raised
AttributeError. Prepared with the assistance of an AI coding
agent (Anthropic's Claude Opus 4.8). @vtino17 (Issue #1607)
A PERIOD value written with dates instead of datetimes, such
as RDATE;VALUE=PERIOD:19970101/19970102, was accepted when a
calendar was parsed and then raised an AttributeError when it
was written out again, or a TypeError where only one half was
a date. Such a value is now read as midnight, in the timezone
of the other half where it has one. I used AI to assist me with
this change. @lcampanella98 (Issue #1633)
When icalendar.use_pytz() was in effect, a date parsed with a
TZID, such as RDATE;TZID=America/New_York;VALUE=DATE:19970101,
was given the timezone's oldest known offset, its local mean
time, so the value was minutes off. It is now read with the
offset that applied on that date. Calendars read with zoneinfo,
the default, were not affected. I used AI to assist me with
this change. @lcampanella98 (Issue #1633)
Escape a lone \r as \n in icalendar.parser.string._escape_char(),
used by vText.to_ical. A carriage return not followed by a line
feed was previously left raw in the serialized content line,
so a SUMMARY or DESCRIPTION built from untrusted text could
carry a control character into the iCalendar stream and split
the line for lenient consumers. \r\n and \n were already escaped,
and the parameter escaper already mapped \r to ^n. @alhudz
(Pull Request #1462)
Reject non-ASCII digits in the ordwk part of vWeekday (BYDAY,
BYWEEKDAY, and WKST). The value validation regular expression
\d matches non-ASCII digits, such as the Arabic-Indic ١٢. A
value such as ١٢MO was silently accepted as relative == 12,
instead of being rejected, as required by RFC 5545 Section
3.3.10 (ordwk = 1*2DIGIT). This mirrors the earlier vMonth fix.
Drafted with AI assistance (Claude Opus 4.8); reviewed, tested,
and verified by the author. @Labib-Bin-Salam
Reject raw CR and LF in vUri, vCalAddress, vInline, and
vXmlReference. These value types are not escaped on serialization,
so a lone \r in the value was written straight into the content
line, slipping past the newline-only assertion in Contentline
and reparsing as a separate property. This was reachable from
untrusted jCal via URL, ATTENDEE, and ORGANIZER. @alhudz
jCal property names, parameter names, and RRULE part names are
now validated as lowercase iCalendar tokens when parsing jCal
(RFC 7265 sections RFC 7265 Section 3.4, RFC 7265 Section 3.5,
and RFC 7265 Section 3.6.10). They were kept verbatim and
re-emitted into the content line on serialization, so a name
containing :, ;, or a lone carriage return could inject parameters
or a new content line for consumers that treat a bare \r as a
break. @alhudz
To generate a diff of this commit:
cvs rdiff -u -r1.64 -r1.65 pkgsrc/time/py-icalendar/Makefile
cvs rdiff -u -r1.36 -r1.37 pkgsrc/time/py-icalendar/PLIST
cvs rdiff -u -r1.55 -r1.56 pkgsrc/time/py-icalendar/distinfo
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: pkgsrc/time/py-icalendar/Makefile
diff -u pkgsrc/time/py-icalendar/Makefile:1.64 pkgsrc/time/py-icalendar/Makefile:1.65
--- pkgsrc/time/py-icalendar/Makefile:1.64 Mon Jul 27 15:06:49 2026
+++ pkgsrc/time/py-icalendar/Makefile Wed Aug 19 16:53:26 2026
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.64 2026/07/27 15:06:49 wiz Exp $
+# $NetBSD: Makefile,v 1.65 2026/08/19 16:53:26 wiz Exp $
-DISTNAME= icalendar-7.2.2
+DISTNAME= icalendar-7.3.0
PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
CATEGORIES= time python
MASTER_SITES= ${MASTER_SITE_PYPI:=i/icalendar/}
@@ -24,8 +24,8 @@ REPLACE_SH+= src/icalendar/tests/fuzzed
REPLACE_PYTHON+= src/icalendar/cli.py
PY_RENAME_BINARIES= icalendar
-# as of 7.2.2
-# 22 failed, 15560 passed, 28 skipped, 6 errors
+# as of 7.3.0
+# 24 failed, 18102 passed, 28 skipped, 527 xfailed, 47 warnings
# https://github.com/collective/icalendar/issues/731
# https://github.com/collective/icalendar/issues/1493
Index: pkgsrc/time/py-icalendar/PLIST
diff -u pkgsrc/time/py-icalendar/PLIST:1.36 pkgsrc/time/py-icalendar/PLIST:1.37
--- pkgsrc/time/py-icalendar/PLIST:1.36 Mon Jul 27 15:06:49 2026
+++ pkgsrc/time/py-icalendar/PLIST Wed Aug 19 16:53:26 2026
@@ -1,4 +1,4 @@
-@comment $NetBSD: PLIST,v 1.36 2026/07/27 15:06:49 wiz Exp $
+@comment $NetBSD: PLIST,v 1.37 2026/08/19 16:53:26 wiz Exp $
bin/icalendar-${PYVERSSUFFIX}
${PYSITELIB}/${WHEEL_INFODIR}/METADATA
${PYSITELIB}/${WHEEL_INFODIR}/RECORD
@@ -235,12 +235,18 @@ ${PYSITELIB}/icalendar/tests/attr/__init
${PYSITELIB}/icalendar/tests/attr/test_alarm.py
${PYSITELIB}/icalendar/tests/attr/test_alarm.pyc
${PYSITELIB}/icalendar/tests/attr/test_alarm.pyo
+${PYSITELIB}/icalendar/tests/attr/test_alarm_factory_methods.py
+${PYSITELIB}/icalendar/tests/attr/test_alarm_factory_methods.pyc
+${PYSITELIB}/icalendar/tests/attr/test_alarm_factory_methods.pyo
${PYSITELIB}/icalendar/tests/attr/test_component.py
${PYSITELIB}/icalendar/tests/attr/test_component.pyc
${PYSITELIB}/icalendar/tests/attr/test_component.pyo
${PYSITELIB}/icalendar/tests/attr/test_exdates.py
${PYSITELIB}/icalendar/tests/attr/test_exdates.pyc
${PYSITELIB}/icalendar/tests/attr/test_exdates.pyo
+${PYSITELIB}/icalendar/tests/attr/test_issue_1594.py
+${PYSITELIB}/icalendar/tests/attr/test_issue_1594.pyc
+${PYSITELIB}/icalendar/tests/attr/test_issue_1594.pyo
${PYSITELIB}/icalendar/tests/attr/test_rdate.py
${PYSITELIB}/icalendar/tests/attr/test_rdate.pyc
${PYSITELIB}/icalendar/tests/attr/test_rdate.pyo
@@ -275,6 +281,7 @@ ${PYSITELIB}/icalendar/tests/calendars/e
${PYSITELIB}/icalendar/tests/calendars/example.ics
${PYSITELIB}/icalendar/tests/calendars/fuzz_testcase_0_char_in_component_name.ics
${PYSITELIB}/icalendar/tests/calendars/fuzz_testcase_invalid_month.ics
+${PYSITELIB}/icalendar/tests/calendars/fuzz_testcase_vtimezone_lone_cr.ics
${PYSITELIB}/icalendar/tests/calendars/invalid_duration.ics
${PYSITELIB}/icalendar/tests/calendars/issue_104_broken_calendar.ics
${PYSITELIB}/icalendar/tests/calendars/issue_1050_all_components.ics
@@ -300,8 +307,13 @@ ${PYSITELIB}/icalendar/tests/calendars/i
${PYSITELIB}/icalendar/tests/calendars/issue_127_categories_with_commas.ics
${PYSITELIB}/icalendar/tests/calendars/issue_1426.ics
${PYSITELIB}/icalendar/tests/calendars/issue_1426_value_parameters.ics
+${PYSITELIB}/icalendar/tests/calendars/issue_1549_binary_attachment.ics
+${PYSITELIB}/icalendar/tests/calendars/issue_1561_image_value.ics
${PYSITELIB}/icalendar/tests/calendars/issue_156_RDATE_with_PERIOD_TZID_khal.ics
${PYSITELIB}/icalendar/tests/calendars/issue_156_RDATE_with_PERIOD_TZID_khal_2.ics
+${PYSITELIB}/icalendar/tests/calendars/issue_1633_freebusy_with_dates.ics
+${PYSITELIB}/icalendar/tests/calendars/issue_1633_rdate_with_dates.ics
+${PYSITELIB}/icalendar/tests/calendars/issue_1633_rdate_with_dates_and_tzid.ics
${PYSITELIB}/icalendar/tests/calendars/issue_165_missing_event.ics
${PYSITELIB}/icalendar/tests/calendars/issue_168_expected_output.ics
${PYSITELIB}/icalendar/tests/calendars/issue_168_input.ics
@@ -312,6 +324,7 @@ ${PYSITELIB}/icalendar/tests/calendars/i
${PYSITELIB}/icalendar/tests/calendars/issue_237_fail_to_parse_timezone_with_non_ascii_tzid.ics
${PYSITELIB}/icalendar/tests/calendars/issue_27_multiple_periods_in_freebusy_multiple_freebusies.ics
${PYSITELIB}/icalendar/tests/calendars/issue_27_multiple_periods_in_freebusy_one_freebusy.ics
+${PYSITELIB}/icalendar/tests/calendars/issue_313_globally_unique_tzid.ics
${PYSITELIB}/icalendar/tests/calendars/issue_321_assert_dst_offset_is_not_false.ics
${PYSITELIB}/icalendar/tests/calendars/issue_322_expected_calendar.ics
${PYSITELIB}/icalendar/tests/calendars/issue_348_exception_parsing_value.ics
@@ -403,6 +416,7 @@ ${PYSITELIB}/icalendar/tests/events/rfc_
${PYSITELIB}/icalendar/tests/events/rfc_9074_example_3.ics
${PYSITELIB}/icalendar/tests/events/rfc_9074_example_4.ics
${PYSITELIB}/icalendar/tests/events/rfc_9074_example_proximity.ics
+${PYSITELIB}/icalendar/tests/freebusy/example.ics
${PYSITELIB}/icalendar/tests/fuzzed/__init__.py
${PYSITELIB}/icalendar/tests/fuzzed/__init__.pyc
${PYSITELIB}/icalendar/tests/fuzzed/__init__.pyo
@@ -413,6 +427,7 @@ ${PYSITELIB}/icalendar/tests/fuzzed/test
${PYSITELIB}/icalendar/tests/hypothesis/test_fuzzing.py
${PYSITELIB}/icalendar/tests/hypothesis/test_fuzzing.pyc
${PYSITELIB}/icalendar/tests/hypothesis/test_fuzzing.pyo
+${PYSITELIB}/icalendar/tests/journals/example.ics
${PYSITELIB}/icalendar/tests/prop/__init__.py
${PYSITELIB}/icalendar/tests/prop/__init__.pyc
${PYSITELIB}/icalendar/tests/prop/__init__.pyo
@@ -425,6 +440,9 @@ ${PYSITELIB}/icalendar/tests/prop/test_c
${PYSITELIB}/icalendar/tests/prop/test_constructors.py
${PYSITELIB}/icalendar/tests/prop/test_constructors.pyc
${PYSITELIB}/icalendar/tests/prop/test_constructors.pyo
+${PYSITELIB}/icalendar/tests/prop/test_crlf_in_values.py
+${PYSITELIB}/icalendar/tests/prop/test_crlf_in_values.pyc
+${PYSITELIB}/icalendar/tests/prop/test_crlf_in_values.pyo
${PYSITELIB}/icalendar/tests/prop/test_date_and_time.py
${PYSITELIB}/icalendar/tests/prop/test_date_and_time.pyc
${PYSITELIB}/icalendar/tests/prop/test_date_and_time.pyo
@@ -527,6 +545,9 @@ ${PYSITELIB}/icalendar/tests/rfc_7265_jc
${PYSITELIB}/icalendar/tests/rfc_7265_jcal/test_section_5_3_examples.py
${PYSITELIB}/icalendar/tests/rfc_7265_jcal/test_section_5_3_examples.pyc
${PYSITELIB}/icalendar/tests/rfc_7265_jcal/test_section_5_3_examples.pyo
+${PYSITELIB}/icalendar/tests/rfc_7265_jcal/test_uri_parameters_round_trip.py
+${PYSITELIB}/icalendar/tests/rfc_7265_jcal/test_uri_parameters_round_trip.pyc
+${PYSITELIB}/icalendar/tests/rfc_7265_jcal/test_uri_parameters_round_trip.pyo
${PYSITELIB}/icalendar/tests/rfc_9253_icalendar_relationships/__init__.py
${PYSITELIB}/icalendar/tests/rfc_9253_icalendar_relationships/__init__.pyc
${PYSITELIB}/icalendar/tests/rfc_9253_icalendar_relationships/__init__.pyo
@@ -573,6 +594,9 @@ ${PYSITELIB}/icalendar/tests/test_create
${PYSITELIB}/icalendar/tests/test_custom_components.py
${PYSITELIB}/icalendar/tests/test_custom_components.pyc
${PYSITELIB}/icalendar/tests/test_custom_components.pyo
+${PYSITELIB}/icalendar/tests/test_docstrings.py
+${PYSITELIB}/icalendar/tests/test_docstrings.pyc
+${PYSITELIB}/icalendar/tests/test_docstrings.pyo
${PYSITELIB}/icalendar/tests/test_encoding.py
${PYSITELIB}/icalendar/tests/test_encoding.pyc
${PYSITELIB}/icalendar/tests/test_encoding.pyo
@@ -594,9 +618,15 @@ ${PYSITELIB}/icalendar/tests/test_free_b
${PYSITELIB}/icalendar/tests/test_funding_json.py
${PYSITELIB}/icalendar/tests/test_funding_json.pyc
${PYSITELIB}/icalendar/tests/test_funding_json.pyo
+${PYSITELIB}/icalendar/tests/test_generate_windows_to_olson_mapping.py
+${PYSITELIB}/icalendar/tests/test_generate_windows_to_olson_mapping.pyc
+${PYSITELIB}/icalendar/tests/test_generate_windows_to_olson_mapping.pyo
${PYSITELIB}/icalendar/tests/test_ghsa_qjcq_q7h7_r74v_repeat_dos.py
${PYSITELIB}/icalendar/tests/test_ghsa_qjcq_q7h7_r74v_repeat_dos.pyc
${PYSITELIB}/icalendar/tests/test_ghsa_qjcq_q7h7_r74v_repeat_dos.pyo
+${PYSITELIB}/icalendar/tests/test_ical_parsing_error.py
+${PYSITELIB}/icalendar/tests/test_ical_parsing_error.pyc
+${PYSITELIB}/icalendar/tests/test_ical_parsing_error.pyo
${PYSITELIB}/icalendar/tests/test_icalendar.py
${PYSITELIB}/icalendar/tests/test_icalendar.pyc
${PYSITELIB}/icalendar/tests/test_icalendar.pyo
@@ -648,6 +678,15 @@ ${PYSITELIB}/icalendar/tests/test_issue_
${PYSITELIB}/icalendar/tests/test_issue_1436_implicit_file_read.py
${PYSITELIB}/icalendar/tests/test_issue_1436_implicit_file_read.pyc
${PYSITELIB}/icalendar/tests/test_issue_1436_implicit_file_read.pyo
+${PYSITELIB}/icalendar/tests/test_issue_1445.py
+${PYSITELIB}/icalendar/tests/test_issue_1445.pyc
+${PYSITELIB}/icalendar/tests/test_issue_1445.pyo
+${PYSITELIB}/icalendar/tests/test_issue_1569_singletons_multiple_consistency.py
+${PYSITELIB}/icalendar/tests/test_issue_1569_singletons_multiple_consistency.pyc
+${PYSITELIB}/icalendar/tests/test_issue_1569_singletons_multiple_consistency.pyo
+${PYSITELIB}/icalendar/tests/test_issue_1633.py
+${PYSITELIB}/icalendar/tests/test_issue_1633.pyc
+${PYSITELIB}/icalendar/tests/test_issue_1633.pyo
${PYSITELIB}/icalendar/tests/test_issue_165_missing_event.py
${PYSITELIB}/icalendar/tests/test_issue_165_missing_event.pyc
${PYSITELIB}/icalendar/tests/test_issue_165_missing_event.pyo
@@ -669,6 +708,9 @@ ${PYSITELIB}/icalendar/tests/test_issue_
${PYSITELIB}/icalendar/tests/test_issue_301_add_rrule_as_string.py
${PYSITELIB}/icalendar/tests/test_issue_301_add_rrule_as_string.pyc
${PYSITELIB}/icalendar/tests/test_issue_301_add_rrule_as_string.pyo
+${PYSITELIB}/icalendar/tests/test_issue_313_globally_unique_tzid.py
+${PYSITELIB}/icalendar/tests/test_issue_313_globally_unique_tzid.pyc
+${PYSITELIB}/icalendar/tests/test_issue_313_globally_unique_tzid.pyo
${PYSITELIB}/icalendar/tests/test_issue_315_uid_required.py
${PYSITELIB}/icalendar/tests/test_issue_315_uid_required.pyc
${PYSITELIB}/icalendar/tests/test_issue_315_uid_required.pyo
@@ -798,6 +840,9 @@ ${PYSITELIB}/icalendar/tests/test_parsin
${PYSITELIB}/icalendar/tests/test_period.py
${PYSITELIB}/icalendar/tests/test_period.pyc
${PYSITELIB}/icalendar/tests/test_period.pyo
+${PYSITELIB}/icalendar/tests/test_prop_org_coverage.py
+${PYSITELIB}/icalendar/tests/test_prop_org_coverage.pyc
+${PYSITELIB}/icalendar/tests/test_prop_org_coverage.pyo
${PYSITELIB}/icalendar/tests/test_property_params.py
${PYSITELIB}/icalendar/tests/test_property_params.pyc
${PYSITELIB}/icalendar/tests/test_property_params.pyo
@@ -810,6 +855,9 @@ ${PYSITELIB}/icalendar/tests/test_recurr
${PYSITELIB}/icalendar/tests/test_repr_recursion.py
${PYSITELIB}/icalendar/tests/test_repr_recursion.pyc
${PYSITELIB}/icalendar/tests/test_repr_recursion.pyo
+${PYSITELIB}/icalendar/tests/test_request_status.py
+${PYSITELIB}/icalendar/tests/test_request_status.pyc
+${PYSITELIB}/icalendar/tests/test_request_status.pyo
${PYSITELIB}/icalendar/tests/test_rfc_6868.py
${PYSITELIB}/icalendar/tests/test_rfc_6868.pyc
${PYSITELIB}/icalendar/tests/test_rfc_6868.pyo
@@ -852,6 +900,9 @@ ${PYSITELIB}/icalendar/tests/test_unit_c
${PYSITELIB}/icalendar/tests/test_unit_parser_tools.py
${PYSITELIB}/icalendar/tests/test_unit_parser_tools.pyc
${PYSITELIB}/icalendar/tests/test_unit_parser_tools.pyo
+${PYSITELIB}/icalendar/tests/test_windows_to_olson_version.py
+${PYSITELIB}/icalendar/tests/test_windows_to_olson_version.pyc
+${PYSITELIB}/icalendar/tests/test_windows_to_olson_version.pyo
${PYSITELIB}/icalendar/tests/test_with_doctest.py
${PYSITELIB}/icalendar/tests/test_with_doctest.pyc
${PYSITELIB}/icalendar/tests/test_with_doctest.pyo
Index: pkgsrc/time/py-icalendar/distinfo
diff -u pkgsrc/time/py-icalendar/distinfo:1.55 pkgsrc/time/py-icalendar/distinfo:1.56
--- pkgsrc/time/py-icalendar/distinfo:1.55 Mon Jul 27 15:06:49 2026
+++ pkgsrc/time/py-icalendar/distinfo Wed Aug 19 16:53:26 2026
@@ -1,5 +1,5 @@
-$NetBSD: distinfo,v 1.55 2026/07/27 15:06:49 wiz Exp $
+$NetBSD: distinfo,v 1.56 2026/08/19 16:53:26 wiz Exp $
-BLAKE2s (icalendar-7.2.2.tar.gz) = 6ba49d1ebfee5e72d57f8e63ac54c9b4db38633922b672f9f11f5eda09076df4
-SHA512 (icalendar-7.2.2.tar.gz) = dd809f2b3b71269d06e07543407f9a769c2662385b1da9a81a4f031657fb624b783ad443a09a4faa35980c748f9a45d89c64e1a3e76e039abed5d83b4b101aad
-Size (icalendar-7.2.2.tar.gz) = 491618 bytes
+BLAKE2s (icalendar-7.3.0.tar.gz) = 9d9a2258063642120fb5075a43da2e34b61877703677c98ad5dc71bb0e97b827
+SHA512 (icalendar-7.3.0.tar.gz) = 8680e4b4bdf568e2d3a976ff6cd61558c4ad968cef64bb1d2716e4ccb3a989fb01a730ab73c12b8081ef3078e4e4b304bf6f5835600aa86ffe3fb435d07f4467
+Size (icalendar-7.3.0.tar.gz) = 525811 bytes
Home |
Main Index |
Thread Index |
Old Index