perl/perl-Time-Piece
SHA256
8
0
Fork 1
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

WIP: Automatic update to v1.380.0 (1.38) #2

Closed
cpanmirror wants to merge 1 commits from cpanmirror/perl-Time-Piece:autoupdate into main
pull from: cpanmirror/perl-Time-Piece:autoupdate
merge into: perl:main
Conversation 2 Commits 1 Files Changed 4 +27 -4
4 changed files with 27 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
Time-Piece-1.3701.tar.gz (Stored with Git LFS)
View File

Binary file not shown.

BIN
Time-Piece-1.38.tar.gz (Stored with Git LFS) Normal file
View File

Binary file not shown.

12
perl-Time-Piece.changes
View File

@@ -1,3 +1,15 @@
-------------------------------------------------------------------
Mon Oct 20 20:09:23 UTC 2025 - Tina Müller <timueller+perl@suse.de>
- updated to 1.38
see /usr/share/doc/packages/perl-Time-Piece/Changes
1.38 2025-10-18
- Doc updates
- Fix Windows-2025 crash with %P
- XS clean up
- strptime: %z and %Z fixes (GH52,32,73,RT93095,168828)
-------------------------------------------------------------------
Thu Oct 9 20:50:41 UTC 2025 - Tina Müller <timueller+perl@suse.de>

13
perl-Time-Piece.spec
View File

@@ -18,7 +18,7 @@
%define cpan_name Time-Piece
Name: perl-Time-Piece
Version: 1.3701
Version: 1.38
okurz commented 2025-10-21 07:26:16 +02:00
Review
Copy Link

The PR title says v1.380.0 but here this still references 1.38, why?

The PR title says v1.380.0 but here this still references 1.38, why?
tinita commented 2025-10-21 11:11:26 +02:00
Review
Copy Link

Ah right, I have hardcoded to use the normalized version in the autoupdate script, but only cpanspec knows.
Maybe I can reference the tarball name in the commit message.

Ah right, I have hardcoded to use the normalized version in the autoupdate script, but only cpanspec knows. Maybe I can reference the tarball name in the commit message.
tinita commented 2025-10-21 11:14:02 +02:00
Review
Copy Link

And the reason why it's not the normallized version is that Time::Piece is also a core perl module, which we need to treat differently for now

And the reason why it's not the normallized version is that Time::Piece is also a core perl module, which we need to treat differently for now
tinita commented 2025-10-22 16:32:54 +02:00
Review
Copy Link

See #3

See #3
Release: 0
License: Artistic-1.0 OR GPL-1.0-or-later
Summary: Object Oriented time objects
@@ -40,6 +40,17 @@ The module actually implements most of an interface described by Larry Wall
on the perl5-porters mailing list here:
https://www.nntp.perl.org/group/perl.perl5.porters/2000/01/msg5283.html
After importing this module, when you use 'localtime' or 'gmtime' in a
scalar context, rather than getting an ordinary scalar string representing
the date and time, you get a 'Time::Piece' object, whose stringification
happens to produce the same effect as the 'localtime' and 'gmtime'
functions.
The primary way to create Time::Piece objects is through the 'localtime'
and 'gmtime' functions. There is also a 'new()' constructor which is the
same as 'localtime()', except when passed a Time::Piece object, in which
case it's a copy constructor.
%prep
%autosetup -n %{cpan_name}-%{version} -p1