Bug 1916039 - usbguard-1.0.0 is available
Summary: usbguard-1.0.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: usbguard
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zoltan Fridrich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-14 01:40 UTC by Upstream Release Monitoring
Modified: 2021-03-01 17:01 UTC (History)
3 users (show)

Fixed In Version: usbguard-1.0.0-1.fc34 usbguard-1.0.0-1.eln108 usbguard-1.0.0-1.fc32 usbguard-1.0.0-1.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-14 12:00:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 1.0.0 (#1916039) (983 bytes, patch)
2021-01-14 01:40 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2021-01-14 01:40:00 UTC
Latest upstream release: 1.0.0
Current version/release in rawhide: 0.7.8-5.fc34
URL: https://usbguard.github.io/

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

Comment 1 Upstream Release Monitoring 2021-01-14 01:40:04 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-01-14 01:40:05 UTC
Created attachment 1747275 [details]
[patch] Update to 1.0.0 (#1916039)

Comment 3 Upstream Release Monitoring 2021-01-14 01:44:55 UTC
the-new-hotness/release-monitoring.org's scratch build of usbguard-1.0.0-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=59657239

Comment 4 Fedora Update System 2021-01-14 12:00:08 UTC
FEDORA-2021-238a116415 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2021-01-14 12:24:13 UTC
FEDORA-2021-9d3b0750c8 has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2021-01-14 14:59:38 UTC
FEDORA-2021-7d75c755f2 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7d75c755f2

Comment 7 Fedora Update System 2021-01-14 15:01:18 UTC
FEDORA-2021-6a5da9174e has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6a5da9174e

Comment 8 Fedora Update System 2021-01-15 02:07:34 UTC
FEDORA-2021-7d75c755f2 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-7d75c755f2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7d75c755f2

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

Comment 9 Fedora Update System 2021-01-15 02:15:33 UTC
FEDORA-2021-6a5da9174e 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-6a5da9174e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6a5da9174e

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

Comment 10 Fedora Update System 2021-01-15 11:49:52 UTC
FEDORA-2021-7d75c755f2 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7d75c755f2

Comment 11 Fedora Update System 2021-01-15 11:50:20 UTC
FEDORA-2021-6a5da9174e has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6a5da9174e

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

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

Comment 13 Fedora Update System 2021-01-16 02:17:43 UTC
FEDORA-2021-6a5da9174e 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-6a5da9174e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6a5da9174e

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

Comment 14 Fedora Update System 2021-01-24 01:21:53 UTC
FEDORA-2021-7d75c755f2 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2021-03-01 17:01:12 UTC
FEDORA-2021-6a5da9174e has been pushed to the Fedora 33 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.