Bug 1932000 - perl-Test-NoBreakpoints-0.17 is available
Summary: perl-Test-NoBreakpoints-0.17 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Test-NoBreakpoints
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-23 18:17 UTC by Upstream Release Monitoring
Modified: 2021-03-19 19:55 UTC (History)
1 user (show)

Fixed In Version: perl-Test-NoBreakpoints-0.17-1.fc35 perl-Test-NoBreakpoints-0.17-1.fc32 perl-Test-NoBreakpoints-0.17-1.fc33 perl-Test-NoBreakpoints-0.17-1.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-04 19:56:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2021-02-23 18:17:16 UTC
Latest upstream release: 0.16
Current version/release in rawhide: 0.15-26.fc34
URL: http://search.cpan.org/dist/Test-NoBreakpoints/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/3406/

Comment 1 Upstream Release Monitoring 2021-02-23 18:17:20 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://cpan.metacpan.org/authors/id/J/JF/JFITZ/Test-NoBreakpoints-0.16.tar.gz to ./Test-NoBreakpoints-0.16.tar.gz

Comment 2 Upstream Release Monitoring 2021-02-24 04:40:42 UTC
Latest upstream release: 0.17
Current version/release in rawhide: 0.15-26.fc34
URL: http://search.cpan.org/dist/Test-NoBreakpoints/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/3406/

Comment 3 Upstream Release Monitoring 2021-02-24 04:40:52 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://cpan.metacpan.org/authors/id/J/JF/JFITZ/Test-NoBreakpoints-0.17.tar.gz to ./Test-NoBreakpoints-0.17.tar.gz

Comment 4 Petr Pisar 2021-02-24 16:38:30 UTC
An enhancement release suitable for all Fedoras.

Comment 5 Fedora Update System 2021-02-24 17:14:06 UTC
FEDORA-2021-1c0d2f1002 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1c0d2f1002

Comment 6 Fedora Update System 2021-02-24 17:14:14 UTC
FEDORA-2021-357d14f43c has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-357d14f43c

Comment 7 Fedora Update System 2021-02-24 17:14:20 UTC
FEDORA-2021-6600f6c532 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6600f6c532

Comment 8 Fedora Update System 2021-02-24 19:18:57 UTC
FEDORA-2021-1c0d2f1002 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1c0d2f1002`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1c0d2f1002

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2021-02-24 21:42:09 UTC
FEDORA-2021-6600f6c532 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-6600f6c532`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6600f6c532

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2021-02-24 21:58:00 UTC
FEDORA-2021-357d14f43c has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-357d14f43c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-357d14f43c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2021-03-04 19:56:12 UTC
FEDORA-2021-6600f6c532 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2021-03-04 20:09:48 UTC
FEDORA-2021-357d14f43c has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2021-03-19 17:37:37 UTC
FEDORA-2021-1c0d2f1002 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2021-03-19 19:55:11 UTC
FEDORA-2021-1c0d2f1002 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.