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

Automatic update to v1.202.508.50 (1.20250805) #1

Merged
okurz merged 1 commits from cpanmirror/perl-Mail-DMARC:autoupdate into main 2025-09-01 16:05:28 +02:00
Conversation 2 Commits 1 Files Changed 4 +17 -11
cpanmirror commented 2025-08-28 12:55:05 +02:00
Contributor
Copy Link
No description provided.
cpanmirror added 1 commit 2025-08-28 12:55:05 +02:00
Automatic update to v1.202.508.50 (1.20250805) 764c773d69
autogits-devel requested review from dstoecker 2025-08-28 12:55:18 +02:00
autogits-devel requested review from kraih 2025-08-28 12:55:18 +02:00
autogits-devel requested review from okurz 2025-08-28 12:55:18 +02:00
autogits-devel requested review from rjschwei 2025-08-28 12:55:18 +02:00
autogits-devel requested review from smithfarm 2025-08-28 12:55:18 +02:00
autogits-devel requested review from tinita 2025-08-28 12:55:19 +02:00
tinita approved these changes 2025-08-28 15:29:19 +02:00
okurz requested changes 2025-09-01 10:19:44 +02:00
perl-Mail-DMARC.spec
@@ -19,3 +19,3 @@
%define cpan_name Mail-DMARC
Name: perl-Mail-DMARC
Version: 1.202.506.100
Version: 1.202.508.50
okurz commented 2025-09-01 10:19:38 +02:00
Owner
Copy Link

I think the version in before was already bad. 20250805 is clearly a timestamp. Turning that into this is both obfuscated as well as leads to problems as 20250810 will be parsed a as lower version compared to 20250805 @tinita

I think the version in before was already bad. 20250805 is clearly a timestamp. Turning that into this is both obfuscated as well as leads to problems as 20250810 will be parsed a as *lower* version compared to 20250805 @tinita
okurz commented 2025-09-01 10:33:26 +02:00
Owner
Copy Link

An example of good handling of the timestamp based version is https://src.opensuse.org/perl/perl-IPC-Run/pulls/1/files

An example of good handling of the timestamp based version is https://src.opensuse.org/perl/perl-IPC-Run/pulls/1/files
tinita commented 2025-09-01 11:09:02 +02:00
Owner
Copy Link

I know it looks confusing, but I can't make my script rely on the fact that a version looks like a timestamp.
The timestamp in the version for IPC-Run is before the dot, btw, so that I don't touch at all.

First of all, 1.202.508.50 will be seen as a newer version than 1.202.506.100 because 508 is newer than 506.

So let's have a look how versions are normalized.
I added 1.20250810 to better compare with 1.20250805, so that we have both timestamps in august, to show that it is actually smaller.

So here we have three dates in ascending order:
For normalizing they are split up in triplets:

1.20250610 -> 1.202.506.10 -> 1.202.506.100
1.20250805 -> 1.202.508.05 -> 1.202.508.050 -> 1.202.508.50
1.20250810 -> 1.202.508.10 -> 1.202.508.100

So the normalized versions consist of triplets, that means the last triplet will be filled with zeroes, e.g. 1.202.508.10 is turned into 1.202.508.100. (because it is a decimal number it is originally 1.20250810000000 and so on).
For 1.202.508.05 it will be 1.202.508.050 and the leading zero in the 050 is superfluous now in the new format.

If perl module authors want timestamps as version numbers after the comma, they should rather use the dotted format in the first place, e,g. 1.2025.8.5.

I know it looks confusing, but I can't make my script rely on the fact that a version looks like a timestamp. The timestamp in the version for IPC-Run is before the dot, btw, so that I don't touch at all. First of all, `1.202.508.50` will be seen as a newer version than `1.202.506.100` because 508 is newer than 506. So let's have a look how versions are normalized. I added `1.20250810` to better compare with `1.20250805,` so that we have both timestamps in august, to show that it is actually smaller. So here we have three dates in ascending order: For normalizing they are split up in triplets: ``` 1.20250610 -> 1.202.506.10 -> 1.202.506.100 1.20250805 -> 1.202.508.05 -> 1.202.508.050 -> 1.202.508.50 1.20250810 -> 1.202.508.10 -> 1.202.508.100 ``` So the normalized versions consist of triplets, that means the last triplet will be filled with zeroes, e.g. `1.202.508.10` is turned into `1.202.508.100`. (because it is a decimal number it is originally `1.20250810000000` and so on). For `1.202.508.05` it will be `1.202.508.050` and the leading zero in the `050` is superfluous now in the new format. If perl module authors want timestamps as version numbers *after* the comma, they should rather use the dotted format in the first place, e,g. `1.2025.8.5`.
okurz merged commit 764c773d69 into main 2025-09-01 16:05:28 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
rjschwei
smithfarm
dstoecker
kraih
tinita
okurz
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adamm autogits-devel kraih mlschroe okurz rjschwei smithfarm tinita
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: perl/perl-Mail-DMARC#1
No description provided.
Delete Branch "cpanmirror/perl-Mail-DMARC:autoupdate"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?