vcswatch reports that
this package seems to have a new changelog entry (version
0.104007-1, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit e493ee66883d73adf920ea661e5b72de6420ed67
Author: gregor herrmann <gregoa@debian.org>
Date: Sat May 10 03:32:18 2025 +0200
update changelog / add WAITS-FOR: trixie
Gbp-Dch: Ignore
commit f9f97daaa21783996a94bb3a45ed70843259cced
Author: gregor herrmann <gregoa@debian.org>
Date: Sat May 10 03:28:19 2025 +0200
Update debian/changelog
Gbp-Dch: Ignore
commit 31d9f74e0523b4eea6ca5836edc8a1c2da971431
Merge: d02dd95 257cdb6
Author: gregor herrmann <gregoa@debian.org>
Date: Sat May 10 03:28:18 2025 +0200
Update upstream source from tag 'upstream/0.104007'
Update to upstream version '0.104007'
with Debian dir f166505d672c52d63417f30a2894c5dd624b4200
commit 257cdb61105bc17d04aeaa9067432931c9d05db5
Merge: 4566cf1 36967ff
Author: gregor herrmann <gregoa@debian.org>
Date: Sat May 10 03:28:18 2025 +0200
New upstream version 0.104007
commit 36967ff8682fdc9f497319655bcfd2e742828dec
Author: Leon Timmermans <fawaka@gmail.com>
Date: Sun May 4 10:08:47 2025 +0200
v0.104007
- update GPL v1 text to current version
- CPAN::Meta v1 "gpl" license is explicitly GPL v2
- Improve recognition for Apache 1.1 & 2.0
commit 73894eda174b93c724d8f7889cf7548ae4b96622
Author: Graham Knop <haarg@haarg.org>
Date: Wed Aug 21 08:34:55 2024 +0200
CPAN::Meta v1 "gpl" license is explicitly GPL v2
In version 1.0 through 1.4, the license "gpl" refers the GPL v2 license.
It should not be used for code licensed as GPL v1 or GPL v3. There is a
fixed list of allowed license values for meta v1, so the only fitting
option for GPLv1 or GPLv3 is "open_source", referring to any OSI
approved license.
commit 67f3101d23ebe666e0d203351d00d6f4c15b1db5
Author: Flavio Poletti <flavio@polettix.it>
Date: Sun Aug 25 11:37:19 2024 +0000
Improve recognition for Apache 1.1 & 2.0
Add more test inputs for the two Apache licenses, taking into account
what is presented as example or suggested in the official web pages
about the two licenses:
- https://www.apache.org/licenses/LICENSE-1.1
- https://www.apache.org/licenses/LICENSE-2.0#apply
This should hopefully cover the "actual" request in GH #72
(https://github.com/Perl-Toolchain-Gang/Software-License/issues/72).
The added tests both fail, hence the proposed changes to the relevant
`@phrases` inside Software::LicenseUtils, as well as a cleanup.
commit 38215c7ee837a489767243d07828614caf9309fb
Merge: 42bafc0 82d5689
Author: Leon Timmermans <fawaka@gmail.com>
Date: Thu May 1 19:05:24 2025 +0200
Merge pull request #90 from Perl-Toolchain-Gang/haarg/update-gpl-v1
update GPL v1 text to current version
commit 82d5689a24c190a3b761dd614baf398e7d472036
Author: Graham Knop <haarg@haarg.org>
Date: Thu May 1 18:19:00 2025 +0200
update GPL v1 text to current version
The GPL v1 license has had some minor updates to it, removing an out of
date mailing address and a minor change to some example text.
commit 42bafc07f7616a3ebf362a7faa461b33096110d2
Author: Ricardo Signes <rjbs@semiotic.systems>
Date: Tue Sep 3 19:08:31 2024 -0400
.github/workflows/dzil-matrix.yaml: create
![[bug history graph]](https://qa.debian.org/data/bts/graphs/libs/libsoftware-license-perl.png){kind=link}