Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
aports
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
alpine
aports
Commits
cea6afcd
Commit
cea6afcd
authored
1 month ago
by
Andy Postnikov
Browse files
Options
Downloads
Patches
Plain Diff
community/php83-pecl-timezonedb: upgrade to 2025.2
parent
d8f64162
No related branches found
No related tags found
1 merge request
!82007
php8?-pecl-timezonedb: upgrade to 2025.2
Pipeline
#311207
skipped
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
community/php83-pecl-timezonedb/APKBUILD
+2
-2
2 additions, 2 deletions
community/php83-pecl-timezonedb/APKBUILD
with
2 additions
and
2 deletions
community/php83-pecl-timezonedb/APKBUILD
+
2
−
2
View file @
cea6afcd
...
...
@@ -2,7 +2,7 @@
# Maintainer: Andy Postnikov <apostnikov@gmail.com>
pkgname
=
php83-pecl-timezonedb
_extname
=
timezonedb
pkgver
=
2025.
1
pkgver
=
2025.
2
pkgrel
=
0
pkgdesc
=
"Timezone Database to be used with PHP's date and time functions."
url
=
"https://pecl.php.net/package/timezonedb"
...
...
@@ -34,5 +34,5 @@ package() {
}
sha512sums
=
"
9062e3a543551dc939ffacc531e7912a05e83ad3302d0a02bbf400c21b7c422164078a0d09563403be226ffb4c6b1f657b361523de9eb587c9c3a232c9ae17fc
php-pecl-timezonedb-2025.
1
.tgz
ad9f57c7b0181a9507a2f886facda993248fb11539eaaf3e23d6596a639814f947a96aeb77604acf3222e571df967010bad2b0764b2dc44aaa16064da10e6ace
php-pecl-timezonedb-2025.
2
.tgz
"
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment