Bug 2260777 - matrix-synapse-1.100.0 is available
Summary: matrix-synapse-1.100.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: matrix-synapse
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kai A. Hiller
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-28 19:04 UTC by Upstream Release Monitoring
Modified: 2024-02-11 05:38 UTC (History)
5 users (show)

Fixed In Version: matrix-synapse-1.100.0-1.fc39 matrix-synapse-1.100.0-1.fc38
Clone Of:
Environment:
Last Closed: 2024-02-10 01:25:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 1.100.0rc3 (#2260777) (703 bytes, patch)
2024-01-28 19:04 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2024-01-28 19:04:08 UTC
Releases retrieved: 1.99.0rc1, 1.99.0, 1.100.0rc1, 1.100.0rc2, 1.100.0rc3
Upstream release that is considered latest: 1.100.0rc3
Current version/release in rawhide: 1.99.0-1.fc40
URL: https://github.com/element-hq/synapse

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://docs.fedoraproject.org/en-US/package-maintainers/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/15283/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/matrix-synapse

Comment 1 Upstream Release Monitoring 2024-01-28 19:04:14 UTC
Created attachment 2011271 [details]
Update to 1.100.0rc3 (#2260777)

Comment 2 Upstream Release Monitoring 2024-01-28 19:15:07 UTC
the-new-hotness/release-monitoring.org's scratch build of matrix-synapse-1.100.0rc3-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=112511363

Comment 3 Upstream Release Monitoring 2024-01-31 17:13:37 UTC
Releases retrieved: 1.100.0
Upstream release that is considered latest: 1.100.0
Current version/release in rawhide: 1.99.0-3.fc40
URL: https://github.com/element-hq/synapse

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://docs.fedoraproject.org/en-US/package-maintainers/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/15283/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/matrix-synapse

Comment 4 Upstream Release Monitoring 2024-01-31 17:13:40 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['git', 'commit', '-a', '-m', 'Update to 1.100.0 (#2260777)']' returned non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

nothing to commit, working tree clean


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 185, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 5 Fedora Update System 2024-02-01 01:22:50 UTC
FEDORA-2024-c90c189914 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c90c189914

Comment 6 Fedora Update System 2024-02-01 01:23:21 UTC
FEDORA-2024-74c5570dc3 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-74c5570dc3

Comment 7 Fedora Update System 2024-02-02 02:11:27 UTC
FEDORA-2024-74c5570dc3 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-74c5570dc3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-74c5570dc3

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

Comment 8 Fedora Update System 2024-02-02 02:16:49 UTC
FEDORA-2024-c90c189914 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c90c189914`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c90c189914

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

Comment 9 Fedora Update System 2024-02-10 01:25:16 UTC
FEDORA-2024-c90c189914 (matrix-synapse-1.100.0-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2024-02-11 05:38:58 UTC
FEDORA-2024-74c5570dc3 (matrix-synapse-1.100.0-1.fc38) has been pushed to the Fedora 38 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.