Bug 1927265 - subversion-1.14.1 is available
Summary: subversion-1.14.1 is available
Alias: None
Product: Fedora
Classification: Fedora
Component: subversion
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-10 12:17 UTC by Upstream Release Monitoring
Modified: 2021-02-20 01:34 UTC (History)
2 users (show)

Fixed In Version: subversion-1.14.1-1.fc33
Doc Type: ---
Doc Text:
Clone Of:
Last Closed: 2021-02-12 01:43:04 UTC
Type: ---

Attachments (Terms of Use)
[patch] Update to 1.14.1 (#1927265) (1009 bytes, patch)
2021-02-10 12:17 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2021-02-10 12:17:13 UTC
Latest upstream release: 1.14.1
Current version/release in rawhide: 1.14.0-12.fc34
URL: https://subversion.apache.org/

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/4905/

Comment 1 Upstream Release Monitoring 2021-02-10 12:17:19 UTC
One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.

Comment 2 Upstream Release Monitoring 2021-02-10 12:17:23 UTC
Created attachment 1756197 [details]
[patch] Update to 1.14.1 (#1927265)

Comment 3 Upstream Release Monitoring 2021-02-10 12:24:19 UTC
the-new-hotness/release-monitoring.org's scratch build of subversion-1.14.1-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=61706785

Comment 5 Joe Orton 2021-02-10 14:49:30 UTC
Package: subversion-1.14.1-1.fc34
Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1705901

Comment 6 Joe Orton 2021-02-10 17:15:15 UTC
Package: subversion-1.14.1-1.fc35
Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1705898

Comment 7 Joe Orton 2021-02-10 17:44:25 UTC
Package: subversion-1.14.1-1.fc33
Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1705903

Comment 8 Fedora Update System 2021-02-11 08:30:48 UTC
FEDORA-2021-a3a0273cb2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a3a0273cb2

Comment 9 Fedora Update System 2021-02-11 08:32:02 UTC
FEDORA-2021-16e51e39a6 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-16e51e39a6

Comment 10 Fedora Update System 2021-02-12 01:43:04 UTC
FEDORA-2021-a3a0273cb2 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2021-02-12 02:25:46 UTC
FEDORA-2021-16e51e39a6 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-16e51e39a6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-16e51e39a6

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

Comment 12 Fedora Update System 2021-02-20 01:34:18 UTC
FEDORA-2021-16e51e39a6 has been pushed to the Fedora 32 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.