Bug 1833338 - rcssmonitor-16.1.0 is available
Summary: rcssmonitor-16.1.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rcssmonitor
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hedayat Vatankhah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-08 13:23 UTC by Upstream Release Monitoring
Modified: 2022-03-26 15:24 UTC (History)
1 user (show)

Fixed In Version: rcssmonitor-16.1.0-1.fc34 rcssmonitor-16.1.0-1.fc35 rcssmonitor-16.1.0-1.fc36
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-25 22:05:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2020-05-08 13:23:31 UTC
Latest upstream release: 16.0.0
Current version/release in rawhide: 15.1.1-29.fc32
URL: https://github.com/rcsoccersim/rcssmonitor

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

Comment 1 Upstream Release Monitoring 2020-05-08 13:23:34 UTC
The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you.  Please use URLs in your Source declarations if possible.

- rcssmonitor.desktop

Comment 2 Upstream Release Monitoring 2022-01-22 08:52:19 UTC
Latest upstream release: 16.1.0
Current version/release in rawhide: 16.0.0-7.fc35
URL: https://github.com/rcsoccersim/rcssmonitor

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

Comment 3 Upstream Release Monitoring 2022-01-22 08:52:24 UTC
Scratch build failed. Details bellow:

BuilderException: Build started, but failure happened during post build operations:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-o2962cey/rcssmonitor.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./rcssmonitor-16.1.0.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.9/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.9/site-packages/hotness/builders/koji.py", line 188, 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 4 Fedora Update System 2022-03-17 21:45:59 UTC
FEDORA-2022-0b94d155fd has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0b94d155fd

Comment 5 Fedora Update System 2022-03-17 21:46:00 UTC
FEDORA-2022-9f9674af28 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9f9674af28

Comment 6 Fedora Update System 2022-03-18 15:53:25 UTC
FEDORA-2022-9f9674af28 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9f9674af28`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9f9674af28

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

Comment 7 Fedora Update System 2022-03-18 19:33:04 UTC
FEDORA-2022-0b94d155fd 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-2022-0b94d155fd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0b94d155fd

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

Comment 8 Fedora Update System 2022-03-18 20:08:32 UTC
FEDORA-2022-629077e197 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-629077e197`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-629077e197

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

Comment 9 Fedora Update System 2022-03-25 22:05:22 UTC
FEDORA-2022-0b94d155fd has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-03-25 23:16:12 UTC
FEDORA-2022-629077e197 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2022-03-26 15:24:51 UTC
FEDORA-2022-9f9674af28 has been pushed to the Fedora 36 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.