Age | Commit message (Collapse) | Author | Files | Lines |
|
Based on version 2016a of the IANA Time Zone Database
(https://mm.icann.org/pipermail/tz-announce/2016-January/000035.html).
|
|
ocaml.mk. It was becoming more trouble than it was worth: only a minority
of packages used it, and it only made Makefiles more confusing.
(I've left out some packages: these will be updated forthwith)
|
|
Version 0.8.1
=============
*released on 30 January 2016*
- Fix error messages when invalid parameter fetching strategy is used. This is
important because users would receive awkward errors for using deprecated
``keyring`` fetching.
Version 0.8.0
=============
*released on 27 January 2016*
- Keyring support has been removed, which means that ``password.fetch =
["keyring", "example.com", "myuser"]`` doesn't work anymore.
For existing setups: Use ``password.fetch = ["command", "keyring", "get",
"example.com", "myuser"]`` instead, which is more generic. See the
documentation for details.
- Now emitting a warning when running under Python 2. See :gh:`219`.
|
|
1.95 2016-01-27
- This release is based on version 2016a of the Olson database. This release
includes contemporary changes for the Cayman Islands, Iran, and Chrita,
Russia.
|
|
BUILD_DEPENDS+= p5-Package-Stash-[0-9]*:../../devel/p5-Package-Stash
|
|
BUILD_DEPENDS+= p5-Package-Stash-[0-9]*:../../devel/p5-Package-Stash
|
|
BUILD_DEPENDS+= p5-Package-Stash-[0-9]*:../../devel/p5-Package-Stash
BUILD_DEPENDS+= p5-Test-Warnings-[0-9]*:../../devel/p5-Test-Warnings
|
|
Upstream changes:
0.52 2015.04.16
The type of the Time::NVtime pointer is NV ()() not double ()(), as can be seen from looking at the Time::HiRes source.
On Linux x86_64 on a uselongdouble build when you replace the Time::NVtime entry with a
double (*)() pointer calls to that function end up leaving an entry on the FPU stack,
eventually causing the failure seen at https://rt.perl.org/Ticket/Display.html?id=123879
This minimal commit fixes that issue and allows DBIX::Class::TimeStamp to pass its tests.
(Tony Cook)
|
|
1.31 2015-10-20
- No Changes since 1.30_01
1.30_01 2015-09-01
- Ignore some tests on non *nix platforms
- fix compile warnings
- Inherit from Dynaloader (fix static build issues)
- Fix windows mem corruption
1.30 2015-05-16
- Stable release. Overview from 1.29:
- Make strftime more portable + fix %z %z
- Add many more tests
- Clean inheritance
1.29_05 2015-05-02
- Combine multiple 'use constant' statements (saves 0.5ms at runtime)
- Don't leave c_epoch undef
- deprecate parse() function
- More constructor tests
- export() calls Exporter::export
1.29_04 2015-04-09
- Clean inheritance of Exporter and DynaLoader (Thanks dolmen!)
- Refactor _strftime to use localtime/gmtime to generate tm struct
1.29_03 2015-04-04
- Don't mix gmtime and mktime in _strftime
- Clean whitespace at end of lines
- Add more tests for DST issues and also strptime parsing
1.29_02 2015-04-04
- Fix handling of %Z and %z in strftime (hopefully)
- Remove compile warnings for int cast
1.29_01 2015-03-30
- Fix handling of %Z and %z in strftime (in progress)
- Remove unused constants from Time::Seconds (Thanks Xaerxess!)
- _strftime: use system mktime to better support past/future dates
- Relicense strptime as BSD 2-clause http://git.io/vfNSg
|
|
|
|
|
|
TZInfo::Data contains data from the IANA Time Zone database packaged as Ruby
modules for use with TZInfo.
TZInfo::Data is the public domain [IANA Time Zone
Database](http://www.iana.org/time-zones) packaged as a set of Ruby modules
for use with [TZInfo](http://tzinfo.github.io).
If TZInfo::Data is installed, TZInfo will automatically use it as its source
of time zone data. If TZInfo::Data is not available, TZInfo will attempt to
use the system zoneinfo files instead. Please refer to the [TZInfo
documentation](http://rubydoc.info/gems/tzinfo/frames) for further details.
|
|
Version 1.2.2 - 8-Aug-2014
--------------------------
* Fix an error with duplicates being returned by Timezone#all_country_zones
and Timezone#all_country_zone_identifiers when used with tzinfo-data
v1.2014.6 or later.
* Use the zone1970.tab file for country timezone data if it is found in the
zoneinfo directory (and fallback to zone.tab if not). zone1970.tab was added
in tzdata 2014f. zone.tab is now deprecated.
Version 1.2.1 - 1-Jun-2014
--------------------------
* Support zoneinfo files generated with zic version 2014c and later.
* On platforms that only support positive 32-bit timestamps, ensure that
conversions are accurate from the epoch instead of just from the first
transition after the epoch.
* Minor documentation improvements.
Version 1.2.0 - 26-May-2014
---------------------------
* Raise the minimum supported Ruby version to 1.8.7.
* Support loading system zoneinfo data on FreeBSD, OpenBSD and Solaris.
Resolves #15.
* Add canonical_identifier and canonical_zone methods to Timezone. Resolves #16.
* Add a link to a DataSourceNotFound help page in the TZInfo::DataSourceNotFound
exception message.
* Load iso3166.tab and zone.tab files as UTF-8.
* Fix Timezone#local_to_utc returning local Time instances on systems using UTC
as the local time zone. Resolves #13.
* Fix == methods raising an exception when passed an instance of a different
class by making <=> return nil if passed a non-comparable argument.
* Eliminate "require 'rational'" warnings. Resolves #10.
* Eliminate "assigned but unused variable - info" warnings. Resolves #11.
* Switch to minitest v5 for unit tests. Resolves #18.
Version 1.1.0 - 25-Sep-2013
---------------------------
* TZInfo is now thread safe. ThreadSafe::Cache is now used instead of Hash
to cache Timezone and Country instances returned by Timezone.get and
Country.get. The tzinfo gem now depends on thread_safe ~> 0.1.
* Added a transitions_up_to method to Timezone that returns a list of the times
where the UTC offset of the timezone changes.
* Added an offsets_up_to method to Timezone that returns the set of offsets
that have been observed in a defined timezone.
* Fixed a "can't modify frozen String" error when loading a Timezone from a
zoneinfo file using an identifier String that is both tainted and frozen.
Resolves #3.
* Support TZif3 format zoneinfo files (now produced by zic from tzcode version
2013e onwards).
* Support using YARD to generate documentation (added a .yardopts file).
* Ignore the +VERSION file included in the zoneinfo directory on Mac OS X.
* Added a note to the documentation concerning 32-bit zoneinfo files (as
included with Mac OS X).
Version 1.0.1 - 22-Jun-2013
---------------------------
* Fix a test case failure when tests are run from a directory that contains a
dot in the path (issue #29751).
Version 1.0.0 - 2-Jun-2013
--------------------------
* Allow TZInfo to be used with different data sources instead of just the
built-in Ruby module data files.
* Include a data source that allows TZInfo to load data from the binary
zoneinfo files produced by zic and included with many Linux and Unix-like
distributions.
* Remove the definition and index Ruby modules from TZInfo and move them into
a separate TZInfo::Data library (available as the tzinfo-data gem).
* Default to using the TZInfo::Data library as the data source if it is
installed, otherwise use zoneinfo files instead.
* Preserve the nanoseconds of local timezone Time objects when performing
conversions (issue #29705).
* Don't add the tzinfo lib directory to the search path when requiring 'tzinfo'.
The tzinfo lib directory must now be in the search path before 'tzinfo' is
required.
* Add utc_start_time, utc_end_time, local_start_time and local_end_time instance
methods to TimezonePeriod. These return an identical value as the existing
utc_start, utc_end, local_start and local_end methods, but return Time
instances instead of DateTime.
* Make the start_transition, end_transition and offset properties of
TimezonePeriod protected. To access properties of the period, callers should
use other TimezonePeriod instance methods instead (issue #7655).
|
|
|
|
|
|
|
|
Version 0.7.5
=============
*released on 23 December 2015*
- Fixed a bug in :storage:`remotestorage` that would try to open a CLI browser
for OAuth.
- Fix a packaging bug that would prevent vdirsyncer from working with newer
lxml versions.
|
|
Version 0.7.4
=============
*released on 22 December 2015*
- Improved error messages instead of faulty server behavior, see :gh:`290` and
:gh:`300`.
- Safer shutdown of threadpool, avoid exceptions, see :gh:`291`.
- Fix a sync bug for read-only storages see commmit
`ed22764921b2e5bf6a934cf14aa9c5fede804d8e`.
- Etag changes are no longer sufficient to trigger sync operations. An actual
content change is also necessary. See :gh:`257`.
- :storage:`remotestorage` now automatically opens authentication dialogs in
your configured GUI browser.
- **Packagers:** ``lxml>=3.1`` is now required (newer lower-bound version).
|
|
0.7.0
=====
released on 2015-11-24
There are no new or dropped dependencies.
* most of the internal representation of events was rewritten, the current
benefit is that floating events are properly represented now, hopefully more
is to come (Christian Geier)
* `printformats` uses a more sensible date now (John Shea)
* khal and ikhal can now highlight dates with events, at the moment, enabling it
does noticably slow down (i)khal's start; set *[default] highlight_event_days
= True* and see section *[highlight_days]* for further configuration (Dominik
Joe Pantůček)
* fixed line wrapping for `at` (Thomas Schape)
* `calendar` and `agenda` optionally print location and description of all
events, enable with the new --full/-f flag (Thomas Schaper)
* updated and improved zsh completion file (Oliver Kiddle)
* FIX: deleting events did not always work if an event with the same filename existed
in an other calendar (but no data lost incurred) (Christian Geier)
ikhal
-----
* events are now displayed nicer (Thomas Glanzmann)
* support for colorschemes, a *light* and *dark* one are currently included,
help is wanted to make them prettier and more functional (config option
*[view] theme: (dark|light)*) (Christian Geier)
* ikhal can now display frames around some user interface elements, making it
nicer to look at in some eyes (config option *[view] frame: True*) (Christian
Geier)
* events can now be duplicated (default keybinding: *p*) (Christian Geier)
* events created while time ranges are selected (default keybinding to enable date range
selection: *v*) will default to that date range (Christian Geier)
* when trying to delete recurring events, users are now asked if they want to
delete the complete event or just this instance (Christian Geier)
|
|
|
|
1.02 2015-12-09
- Make the DateTime::Locale->load method accept a locale in any non-canonical
casing, such as "en-us". Reported by Shawn Moore. RT #110244.
|
|
== Version 0.3.46 (tzdata v2015g) - 02-Dec-2015
* From version 2015e, the IANA time zone database uses non-ASCII characters in
country names. Backport the encoding handling from TZInfo::Data to allow
TZInfo 0.3.x to support Ruby 1.9 (which would otherwise fail with an invalid
byte sequence error when loading the countries index). Resolves #41.
|
|
It doesn't make sense to let the user configure the XAW_TYPE when only
one specific setting (XAW_TYPE=3d) works at all.
Thanks, joerg
|
|
use php-mysql package.
|
|
|
|
|
|
pyRFC3339 parses and generates RFC 3339-compliant timestamps
using Python datetime.datetime objects.
|
|
BUILD_DEPENDS+= p5-File-Slurp-[0-9]*:../../devel/p5-File-Slurp
|
|
* 0.02:
Fix Makefile.PL (by motemen)
* 0.03:
miss
* 0.04:
Add prototypes to overriden time and sleep (by naturalist)
|
|
http://www.tryton.org/news/index.html
Major changes for the developer
The progress bar widget works with float between 0 and 1 to ease usage as
percentage.
The rich text widget uses now a subset of HTML to allow its implementation
in sao.
The Many2One has a new option target_search which define the kind of query
to use for dereferenced search. The options are subquery and the new join
(which is the default). The join method generate a faster query in most
cases.
The SQL constraints use a similar syntax to python-sql. This gives more
flexibility to implement backend for other databases.
Trying to create/write/delete on a Model based on a table_query raises an
exception instead of a silent error.
The table name of a ModelSQL can be overridden with a configuration file.
This allows to work around database limitations on the length of table
names.
The new StateReport has been added to wizards, to simplify the code of
wizards that run a report.
The style on reports has been removed, experience show that this feature
was not used.
The PostgreSQL backend manages now schema. This allows different instances
of Tryton sharing the same database.
The generic foreign key to create/write user on all ModelSQL has been
replaced by a rule that prevent to delete users. This greatly improves
scalability in some circumstances.
The Property field supports now float and integer values.
A subdirectory locale/override is supported for modules that override
translations of other modules.
Accounting
The charts of account are no longer translatable. Instead we provide
translated charts via a template using XSLT.
The invoice doesn't set a unit price on the line. For this feature the
purchase or sale module must be used.
Some fields of the invoice like the note and the origin are editable after
posting the invoice.
Product
Conversion between units no longer results in silent failures but an
explicit error is risen.
The volume property has been added to the products.
Project
The tree structure of the project and the time sheet have been separated,
each object has its own one.
The price list uses the same decimal precision as the product.
The cost price of the employee is stored on the time sheet line for the
date of the line. This allows to sum the costs of time sheet faster
Purchase
The state of the purchase request is now searchable.
The purchase requests are generated even if the rounded quantity is zero
to allow the user to still decide to purchase more.
Stock
Many unnecessary restrictions on the edition of move fields have been
removed.
The expected quantity of the inventory lines is always computed even if
they are added manually.
It is possible to create staging and draft moves using view locations.
Those locations will have to be changed to really do the move.
The inventory uses the grouping feature to create the moves. This allows
to easily support the lot (or any other extra field).
|
|
Changes from https://github.com/ygale/timezone-olson
0.1.7
- Bump time to 1.5.
0.1.6
- Update link in package description.
- Update comment to indicate support for version 3 format.
|
|
Changes from https://github.com/ygale/timezone-series
0.1.5
- Bump time to 1.5.
|
|
Update DEPENDS
Upstream changes:
1.61 2015-11-13
[BUG FIXES]
- If you loaded this module with warnings globally enabled ("perl -w", which
you should never do), then you'd get a warning about the import subroutine
being redefined. This broke the Package::DeprecationManager API for turning
off deprecation warnings. This has been fixed in
Package::DeprecationManager 0.15. Reported by Martin. RT #108871.
1.60 2015-11-07
- This release is identical to the prior trial release. The changes for the
trial releases are reproduced below for convenience.
[BACKWARDS INCOMPATIBILITIES]
- The error messages for various types of failures have changed.
- The never-documented diagnostic parameter for the constructor has been
removed.
- The never-documented feature to allow you to use arbitrary DateTime.pm
methods in the parsing pattern has been removed. This never made much sense
anyway, since most DateTime.pm methods are not constructor params, but they
were used that way.
- Using the pattern, locale, and time_zone to set the respective attribute is
now deprecated. Make a new object instead of changing one of these values.
[BUG FIXES]
- Fixed a warning from the tests with newer Perl versions. RT #107620.
- Clarified docs to note that %Y and %G require 4-digit years. Reported by
Karen Etheridge. RT #103147.
- Using the 24-hour token (%H) with an AM/PM specifier (%p) now leads to an
error if you try to parse something like "23:01 AM". Reported by Ric
Signes. RT #92445.
1.59 2015-10-25 (TRIAL RELEASE)
- The previous release accidentally included an old version of Strptime.pm in
the root dir, causing all sorts of chaos and test failures.
1.58 2015-10-18 (TRIAL RELEASE)
- This release is a substantial rewrite. Please test it and file bugs for any
unintentional breakage.
* The error messages for various types of failures have changed.
* The never-documented diagnostic parameter for the constructor has been
removed.
* The never-documented feature to allow you to use arbitrary DateTime.pm
methods in the parsing pattern has been removed. This never made much sense
anyway, since most DateTime.pm methods are not constructor params, but they
were used that way.
* Using the pattern, locale, and time_zone to set the respective attribute is
now deprecated. Make a new object instead of changing one of these values.
- Fixed a warning from the tests with newer Perl versions. RT #107620.
- Clarified docs to note that %Y and %G require 4-digit years. Reported by
Karen Etheridge. RT #103147.
1.57 2015-10-04
- Make all tests pass with both the current DateTime::Locale and the upcoming
new version (currently still in trial releases).
|
|
Add test dependency and fix test target.
Changes:
Update README for release and add more pythons for testing
Remove debug logging
Add support for , as separator for fractional part
Add pypy 3 into tox test config
Add python 3.4 to tox tests and update doc links
|
|
Remove duplicate depends, add test dependencies.
1.01 2015-11-07
- Prevent CPAN from indexing the tools directory, which is just for the
author's use.
1.00 2015-11-07
* All of these changes were originally released in previous trial releases,
but I'm repeating them here for clarity.
[ENHANCEMENTS]
- This release uses the locale data from CLDR version 28. The last major
update of the locale data used CLDR 1.7.1, released in 2009, so this is a
big change. Many things have changed in terms of locale data.
- Some locales are no longer available because they are not in the CLDR data.
- The CLDR data no longer includes default date and time format lengths. This
is now "medium" for every locale, simply to provide some level of backwards
compatibility.
- Loading DateTime::Locale itself is now quite a bit faster. The whole locale
registration system has been removed entirely, except for custom
locales. This fixes RT #78794. Requested by Michael Conrad.
- A long-standing issue with the Austrian locale not using the Austrian name
for January has been fixed. RT #52337. Reported by Thomas Klausner.
[BACKWARDS INCOMPATIBILITIES]
- This is a big new release, and includes a number of backwards-incompatible
changes. However, most users should be unaffected by this change. If you
only use this module via DateTime.pm, you are unlikely to notice any changes
other than changes to the locale data.
- The old API deprecated since 0.40 has been removed (almost) entirely.
- We now refer to things as "code" in the docs and method names where we used
to call them ids. This includes locale, language, script, territory, and
variant codes. This is more in line with the various ISO standards and the
CLDR packages.
- All the $locale->*_id methods (including $locale->id) are deprecated. Use
the relevant $locale->*_code method instead.
- The canonical form of the locale codes now uses dashes (-) instead of
underscores (_). Loading a locale with an underscore in the name
(e.g. en_US) still works.
- The way that locale data is packaged has changed quite a bit. We no longer
package each locale in its own class. Instead, all locale data is in a
single module (mostly in a __DATA__ section) and loaded into memory as
needed. If you have any code that checks $locale->isa, that code may
break.
- Locales are no longer subclasses of DateTime::Locale::Base. This module is
still included in the distribution in case someone has a custom locale that
inherits from this module. However, this module will go away in a future
release.
z
- The "ii-*" aliases for the "he-*" locales have been removed.
- The "no-*" aliases for the "nn-*" locales have been removed.
- The value of $locale->code no longer reflects the value passed to
DateTime::Locale->load. This only affects aliases and non-canonical forms of
the code. For example, if you load "en_US" then $locale->code will return
"en-US". If you load "C" or "POSIX" the returned code will be "en-US-POSIX".
- All of the documentation related to creating aliases and registering custom
locales has been removed. All of these methods still work, but I don't think
this system got much use, so I don't want to emphasize it in the docs. (But
let me know if you are using this and want to see these docs restored).
0.96 2015-10-04 (TRIAL RELEASE)
- Locale data with characters in the 0x80-0xFF range was not marked as UTF-8
by Perl. This could cause all sorts of weirdness and was generally bad.
0.95 2015-09-30 (TRIAL RELEASE)
- Added .pod files for each locale that document the data for that locale.
0.94 2015-09-30 (TRIAL RELEASE)
- Restored the datetime_format method to individual locale objects for
backwards compatibility.
0.93 2015-09-28 (TRIAL RELEASE)
- Really release a trial release this time. I'm not kidding. See 0.90 for the
interesting changes.
|
|
|
|
Version 0.7.3
=============
*released on 05 November 2015*
- Make remotestorage-dependencies actually optional.
Version 0.7.2
=============
*released on 05 November 2015*
- Un-break testsuite.
Version 0.7.1
=============
*released on 05 November 2015*
- **Packagers:** The setuptools extras ``keyring`` and ``remotestorage`` have
been added. They're basically optional dependencies. See ``setup.py`` for
more details.
- Highly experimental remoteStorage support has been added. It may be
completely overhauled or even removed in any version.
- Removed mentions of old ``password_command`` in documentation.
Version 0.7.0
=============
*released on 27 October 2015*
- **Packagers:** New dependencies are ``click_threading``, ``click_log`` and
``click>=5.0``.
- ``password_command`` is gone. Keyring support got completely overhauled. See
:doc:`keyring`.
|
|
|
|
Problems found with mismatching existing digests for:
distfiles/asclock-classic-1.0.tar.gz
distfiles/asclock-gtk-2.1.10beta.tar.gz
distfiles/asclock-xlib-2.0.11.tar.gz
distfiles/emiclock-2.0.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
|
1.94 2015-10-21
- This release is based on version 2015g of the Olson database. This release
includes contemporary changes for Turkey, Norfolk, Fiji, and Fort Nelson.
|
|
|
|
Adapt some packages so they build with that.
Bump their PKGREVISIONs.
|
|
== Version 0.3.45 (tzdata v2015g) - 03-Oct-2015
* Updated to tzdata version 2015g
(http://mm.icann.org/pipermail/tz-announce/2015-October/000034.html).
|
|
|
|
No changelog available.
|
|
## Version 1.2.3 2015-09-13
* Release new fatbinary version for windows
* Update README to indicate duration units
* Provide a more friendly error message if the gem is not installed correctly
|
|
1.21 2015-09-30
- Make all tests pass with both the current DateTime::Locale and the upcoming
new version (currently still in trial releases).
|
|
0.92 2015-09-27
- I accidentally released 0.90 as a non-trial release. This release is the
same as 0.46, so that the newest non-trial release does not break the
DateTime.pm tests.
0.91 2015-09-27
- Released the changes in 0.90 as a trial release.
0.90 2015-09-27
[ENHANCEMENTS]
- Updated based on version 28 of the CLDR data. The last update was based on
the CLDR 1.7.1 release from 2009, so this is a big change. Many things have
changed in terms of locale data.
- Some locales are no longer available because they are not in the CLDR data.
- The CLDR data no longer includes default date and time format lengths. This
is now "medium" for every locale, simply to provide some level of backwards
compatibility.
- The old API deprecated since 0.40 has been removed (almost) entirely.
- Loading DateTime::Locale itself is now quite a bit faster. The whole locale
registration system has been removed entirely, except for custom
locales. This fixes RT #78794. Requested by Michael Conrad.
- A long-standing issue with the Austrian locale not using the Austrian name
for January has been fixed. RT #52337. Reported by Thomas Klausner.
[BACKWARDS INCOMPATIBILITIES]
* This is a big new release, and includes a number of backwards-incompatible
changes. However, most users should be unaffected by this change. If you
only use this module via DateTime.pm, you are unlikely to notice any changes
other than changes to the locale data.
* We now refer to things as "code" in the docs and method names where we used
to call them ids. This includes locale, language, script, territory, and
variant codes. This is more in line with the various ISO standards and the
CLDR packages.
* All the $locale->*_id methods (including $locale->id) are deprecated. Use
the relevant $locale->*_code method instead.
* The canonical form of the locale codes now uses dashes (-) instead of
underscores (_). Loading a locale with an underscore in the name
(e.g. en_US) still works.
* The way that locale data is packaged has changed quite a bit. We no longer
package each locale in its own class. Instead, all locale data is in a
single module (mostly in a __DATA__ section) and loaded into memory as
needed. If you have any code that checks $locale->isa, that code may
break.
* Locales are no longer subclasses of DateTime::Locale::Base. However, this
module is still included in the distribution in case someone has a custom
locale that inherits from this module. However, this module will go away in
a future release.
* The "ii-*" aliases for the "he-*" locales have been removed.
* The "no-*" aliases for the "nn-*" locales have been removed.
* The value of $locale->code no longer reflects the value passed to
DateTime::Locale->load. This only affects aliases and non-canonical forms of
the code. For example, if you load "en_US" then $locale->code returns
"en-US". If you load "C" or "POSIX" the code is "en-US-POSIX".
* All of the documentation related to creating aliases and registering custom
locales has been removed. All of these methods still work, but I don't think
this system got much use, so I don't want to emphasize it in the docs (but
let me know if you are using this and want to see these docs restored).
|
|
|
|
|