python-caldav-1.3.9-bp156.1.2

- enabled %{?sle15_python_module_pythons}

- deleted patches
  - drop-python2-support.patch (upstreamed)

- update to 1.3.9
  [1.3.9] - 2023-12-12
  * Some bugfixes.
  [1.3.6] - 2023-07-20
  * One of the tests has been partially disabled, ref #300 , #320 and #321
  [1.3.3] - 2023-07-19
  * Support for very big events, credits to github user @aaujon in #301
  * Custom HTTP headers was added in v1.2, but documentation and unit test is added in v1.3
  * More test code in #308
  * Add props parameter to search function, credits to github user @ge-lem in #315
  * Set an id field in calendar objects when populated through CalendarSet.calendars()
  * get_relatives-method, #294
  * get_dtend-method

- Add drop-python2-support.patch to remove python-six dependency
  gh#python-caldav/caldav#228
- Remove python_module macro definition
- Update to 0.10.0
  [#]# Quick summary
  * Work on a universal search method
  * Refactoring, consolidated lots of slightly duplicated code into one
    method to rule them all
  * Support for things needed by the calendar-cli utility, like search by
    categories
  * Support for completion of recurring tasks
  * More utilities for tasks
  * Uncomplete-method ... for undoing the complete (recurrences not supported
    though)
  * get/set duration/dtstart/dtend (arguably this belongs to vobject and/or
    icalendar)
  * Other improvements:
  * picklable URLs
  * display_name convenience method
  * possible to set child/parent relationships
  * Potential bugfix: sequence number may need to be increased when saving
    something to the calendar (not backported, this may have side effects)
  [#]# Search method
  Calendar now has a method search.  Here is some information from the
  docstring:
  Parameters supported:
  * xml - use this search query, and ignore other filter parameters
  * comp_class - set to event, todo or journal to restrict search to this
    resource type.  Some server implementations require this to be set.
  * todo - sets comp_class to Todo, and restricts search to pending tasks,
    unless the next parameter is set ...
  * include_completed - include completed tasks
  * event - sets comp_class to event
  * text attribute search parameters: category, uid, summary, omment,
    description, location, status
  * expand - do server side expanding of recurring events/tasks
  * start, stop: do a time range search
  * filters - other kind of filters (in lxml tree format)
  * sort_keys - list of attributes to use when sorting
  not supported yet:
  * negated text match
  * attribute not set
  [#]# Completed tasks
  While the RFCs do support recurring tasks, they are not very clear on the
  details.  In v0.10 there are three different ways to complete a task.  The
  first one is to ignore the RRULE property and mark the task as completed.
  This is the backwards-compatibility mode - though, according to my
  understanding of a "recurring task" this is the wrong way to do it.
  The two other modes considers the task to be "interval based" is no BY-rules
  are specified in the RRULE - meaning that if a task is supposed to be done
  weekly, then a week should pass from it was completed and until one needs to
  start with it again - no matter the DTSTART of the original instance - but
  the standards may also be interpreted so that if the original task was to be
  started at a Tuesday 10:00, then all recurrences should be started at a
  Tuesday 10:00.
  Both the modes stores a copy of the completed task, for the record.  The
  "safe" mode stores the copy as a completely independent task, and modifies
  the DTSTART/DUE of the original task - so the completed task is not linked up
  to the recurring task.  (One may eventually try to make a link by
  establishing a "parent task").
  The "thisandfuture"-mode will establish the completed task as a separate
  recurrence in a recurrence set.  The non-completed task is also duplicated
  with a new DTSTART set and range set to THISANDFUTURE. As I understand the
  RFC, this is the way to handle interval-based tasks, future recurrences will
  then base their starting time on the DTSTART of the THISANDFUTURE task.  For
  fixed tasks the THISANDFUTURE recurrence is moot, so I'm considering to
  create a third mode as well.

- version 0.9.2
  no changelog

- Update to v0.9.1
  [#]# Quick summary
  * Tweaks to support the DAVMail server implementation
  * v0.9.0 broke for python 3.5 and lower, due to usage of fstrings.  v0.9.1 has been tested with python 3.5.
  * Discovery of some cases of broken support of recurring events on the server side, and logging of errors (optionally raising of errors)
  * New method .close on the DAVClient object.
  [#]# Minor changes
  * Quite some users are complaining because recurring events aren't supported - which is intentional, because the server is supposed to take
    care of that.  Unfortunately quite some servers doesn't.  Thanks to cos, at least we now have some code in place to log an error
    (or optionally raising an error) when recurrences aren't taken care of (though, it only works if the server is returning non-expanded
    recurring events - if searching for a recurrence and the server doesn't find it, then ... no error logged).
    The error message is referring to https://github.com/python-caldav/caldav/issues/157
  * New method `.close` on the DAVClient object
  [#]# Documentation fixes
  * Added the fastmail caldav URL to the documentation - including note that they are picky on the trailing slash
  - ref https://github.com/home-assistant/core/issues/66599
  * Keeping the changelog up-to-date
  [#]# Bugfixes
  * v0.9.0 broke on elder python versions due to an f"string".  The f-format was introduced in python 3.6.  Anything below is actually
    End of Life versions, but still ... it's a very small effort here to preserve compatibility with elder python versions.
  * The library had some difficulties with the DAVMail server - at one point it does not return a calendar home set property, and at
    another point the calendar home set URL is the same as the calendar URL.
  * The `URL.canonical()` method should rewrite variants of the same URL into something that will be equal - some work has been put making it more robust.
  Issues: https://github.com/python-caldav/caldav/issues/189.  f-strings discussed outside github.
  [#]# Linting
  Removal of some extra white space
  [#]# Testing framework and incompatibility matrix
  * The testTodoDatesearch is pesky - because every server has different visions on how (or weather) to support recurring tasks.
    Added yet more complexity to allow the test code to pass on different servers.
  * Removed some silly test code in testSetCalendarProperties - seems to be just recreating a calendar, which we do in the setup of any test
    unless the `unique_calendar_ids`-flag is given.
-Update to v0.9
  [#]# API changes
  * `save_todo`, `save_event` and `save_journal` now takes extra parameters, assumed to be equivalent with ical attributes as defined in the icalendar library, and may build icalendar data from scratch or enhance on the given icalendar data.
  * Added a context manager, so one can do `with DAVClient(foo) as client: ...`
  [#]# Refactoring
  * The digest vs basic auth is solved a bit differently in 0.8.2 and 0.9.  It has been fixed very carefully but inelegantly in 0.8.2, 0.9 contains a complete rewrite.  It was later shown that the logic in 0.8.2 broke for some servers, hence I've decided to discontinue support for the 0.8-branch.
  [#]# Bugfixes and test framework
  This release does not fix a reported regression at https://github.com/home-assistant/core/issues/65588 (and probably some other places)
  that iCloud caldav URLs pointing directly to a calendar won't work.  I'm not sure if this is a regression in the caldav library or in Home Assistant.
  I've written up test code to catch this issue, but didn't have an iCloud account available to test with while releasing.
  This release does not fix a reported possible regression in Home Assistant that public ICS feeds does not work anymore as the "caldav URL".
  I don't think such an URL ever was working with the caldav library, I believe it's needed with some extra logic in the Home Assistant module if
  public ics feeds are to be supported.  (issues https://github.com/home-assistant/core/issues/70205 https://github.com/home-assistant/core/issues/65941)
  * Quite some problems fixed with the authentication code
  * The string representation of any error class was hardcoded as "AuthorizationError".
  * Concatinating an empty unicode string with an empty byte string will cause an exception.  The python_utilities.to_wire method would return an empty
    unicode string if given an empty unicode string.
  * the flags no_overwrite and no_create in save_todo and save_journal didn't work
  * scheduling still doesn't work very well, but one bug has been fixed
  * tests and compatibility lists: some tweaks to let tests pass on the test servers (including fastmail)
  * tests: make sure to delete the test calendar properly
  * tests: test that non-base-urls still work
  * tests: working around some issues on xandrikos startup, allows newer xandrikos version to be used
  * tests: added flag "enable" in the test server config file

- update to 0.8.2:
  * urllib.quote on uuids before including it in a new URL on object creation
  * Principal.calendar (and CalendarSet.calendar) now accepts an URL as "cal_id"
  * Minor workaround for problem with cloud.global/e.email: urllib.quote the
    calendar_home_set_url if it's a path and it contains the character '@'
  * Minor fixes to improve support for SOGo
  * Bugfix for non-ascii in the password
  * timezones ... the API of tzlocal was changed for a short while,
    pytz is deprecated, but icalendar only supports timestamps localized with pytz.  What a mess!
  * Added supported-report-set to the tags (but so far no code for using it)
  * Multiget didn't work
  * Silly spelling mistake in one of the error classes
  * Attempts to resolve broken ical issues with X-APPLE-STRUCTURED-EVENT
    and X-APPLE-STRUCTURED-LOCATION (#37, ...)
  * Compatibility issue with e.email

- Update to 0.8.0
  * Support for WebDAV sync-tokens
  * Work on support for RFC6635, scheduling/RVSP (partially done)
  * Improved support for iCloud, Google
  * Calendar API improvements
  * Improvement of the documentation, examples and inline
    docstrings and comments
  * Bugfixes
- Use fdupes to remove duplicate files.
- Remove shebangs from various non-executable Python files.

- Update to 0.7.1:
  * Some tweaks to support newer versions of Zimbra and other caldav server implementations with slightly twisted support for the RFC.
  * API change: add_event, add_todo and add_journal methods are now deprecated and aliases of save_. New attributes no_create and no_overwrite if one wants to be sure the save_-methods does the right thing.
  * Calendars can now be created without a display name
  * Quite some minor bugfixes
  * Some code refactoring, removing some duplicated code
  * library will gracefully create an UID if fed with caldav data missing the UID field
  * the code for calendar searches has been reorganized making it possible for "power users" to do custom calendar searches.
- Drop nose from BuildRequires/Requires, we don't run the testsuite, and it
  isn't listed in the requirements.

- update to 0.6.2
  * caldav/lib/error.py - ProppatchError was not defined, ref https://github.com/python-caldav/caldav/issues/54.
    Also added a common base class DAVError, and made sure the error
    referenced in #54 will never reappear, even if new methods are
    added to DAVClient.
  * caldav/elements/cdav.py - fixing a retention problem - the
    timezone fixes done recently was not compatible with python 2.7 nor 3.5.
  * setup.py - reintroducing dependencies pytz and tzlocal - but only for old python versions
  * README.md - proper documentation of the dual licensing, ref
    https://github.com/python-caldav/caldav/issues/60
  * caldav/objects.py - fixes (or workarounds?) that solves real-world
    issues with iCloud and MS Exchange.  Ref https://github.com/python-caldav/caldav/pull/56

- version update to 0.6.1
  * bugfix: accept text/calendar (required for fetching calendar items from the xandikos server, ref https://github.com/python-caldav/caldav/issues/40

- version update to 0.6.0
  * caldav/elements/cdav.py - proper timezone support
  * caldav/elements/dav.py - add GetEtag
  * caldav/elements/cdav.py - allow Expand tag to be used with open-ended
    start
  * caldav/objects.py - enhancement: add the ability to add events to
    calendar using directly a vobject object, and not necessarily an ical
    string.
  * caldav/objects.py - bugfix: uid handling while fetching
    elements
  etc. see https://github.com/python-caldav/caldav/blob/master/ChangeLog
- almost all tests are online, do not run

- Remove superfluous devel dependency for noarch package

- Drop history lesson and future goal wording from description.

- Update to 0.5.0
- Convert spec file to singlespec

- Update to 0.4.0
  * No upstream changelog
- Clean up spec file

- Initial package ( version 0.1.12 )