Bug 1818634

Summary: Missing Require: foliate should require gjs
Product: [Fedora] Fedora Reporter: Aleksei Bavshin <alebastr89>
Component: foliateAssignee: Artem <ego.cordatus>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ego.cordatus
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foliate-1.5.3-3.fc32 foliate-1.5.3-3.fc31 foliate-1.5.3-3.fc30 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-04 00:45:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aleksei Bavshin 2020-03-29 20:55:23 UTC
Description of problem:
foliate rpm does not have dependency from gjs. Please, add 'Require: gjs' to the package spec.

% com.github.johnfactotum.Foliate
zsh: /usr/bin/com.github.johnfactotum.Foliate: bad interpreter: /usr/bin/gjs: no such file or directory

% rpm -qR foliate
/usr/bin/python3
hicolor-icon-theme
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsZstd) <= 5.4.18-1

Version-Release number of selected component (if applicable):
Version     : 1.5.3
Release     : 2.fc32

Comment 1 Fedora Update System 2020-03-30 09:10:23 UTC
FEDORA-2020-046d70f5db has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-046d70f5db

Comment 2 Fedora Update System 2020-03-30 09:16:12 UTC
FEDORA-2020-f9c05dca9a has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f9c05dca9a

Comment 3 Fedora Update System 2020-03-30 09:22:54 UTC
FEDORA-2020-87efe769d8 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-87efe769d8

Comment 4 Fedora Update System 2020-03-31 01:52:03 UTC
FEDORA-2020-046d70f5db has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-046d70f5db`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-046d70f5db

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

Comment 5 Fedora Update System 2020-03-31 02:25:32 UTC
FEDORA-2020-f9c05dca9a has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f9c05dca9a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f9c05dca9a

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

Comment 6 Fedora Update System 2020-03-31 03:34:20 UTC
FEDORA-2020-87efe769d8 has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-87efe769d8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-87efe769d8

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

Comment 7 Fedora Update System 2020-04-04 00:45:37 UTC
FEDORA-2020-046d70f5db has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2020-04-08 05:06:46 UTC
FEDORA-2020-f9c05dca9a has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2020-04-08 05:28:16 UTC
FEDORA-2020-87efe769d8 has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.