Bug 1942096 - dconf-editor-43.beta is available
Summary: dconf-editor-43.beta is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dconf-editor
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-23 16:16 UTC by Upstream Release Monitoring
Modified: 2022-09-22 01:46 UTC (History)
1 user (show)

Fixed In Version: dconf-editor-43.0-1.fc37
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-22 01:46:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 43.beta (#1942096) (1.15 KB, patch)
2022-07-27 16:53 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2021-03-23 16:16:43 UTC
Latest upstream release: 3.38.3
Current version/release in rawhide: 3.38.2-2.fc34
URL: https://wiki.gnome.org/action/show/Projects/dconf

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

Comment 1 Upstream Release Monitoring 2021-03-23 16:16:47 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 2 Upstream Release Monitoring 2022-07-13 18:54:49 UTC
Releases retrieved: 43.alpha
Upstream release that is considered latest: 43.alpha
Current version/release in rawhide: 3.38.3-3.fc36
URL: https://wiki.gnome.org/action/show/Projects/dconf

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


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

Comment 3 Upstream Release Monitoring 2022-07-13 18:54:52 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-2avzc_60/dconf-editor.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./dconf-editor-43.alpha.tar.xz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/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.10/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 Upstream Release Monitoring 2022-07-27 16:53:22 UTC
Releases retrieved: 43.beta
Upstream release that is considered latest: 43.beta
Current version/release in rawhide: 43~alpha-2.fc37
URL: https://wiki.gnome.org/action/show/Projects/dconf

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


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

Comment 5 Upstream Release Monitoring 2022-07-27 16:53:27 UTC
Created attachment 1899734 [details]
Update to 43.beta (#1942096)

Comment 6 Upstream Release Monitoring 2022-07-27 17:53:36 UTC
the-new-hotness/release-monitoring.org's scratch build of dconf-editor-43.beta-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=90140603

Comment 7 Fedora Update System 2022-09-20 21:20:29 UTC
FEDORA-2022-0bd68bbb43 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0bd68bbb43

Comment 8 Fedora Update System 2022-09-21 02:34:46 UTC
FEDORA-2022-0bd68bbb43 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-0bd68bbb43`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0bd68bbb43

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

Comment 9 Fedora Update System 2022-09-22 01:46:23 UTC
FEDORA-2022-0bd68bbb43 has been pushed to the Fedora 37 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.